| Subject: | Add validation to prevent duplicate UPC or barcodes |
| Summary: | 1. ISSUE: - When a UPC code is saved, we need to ensure that it is unique across all items.
- We are using additional text 1-5 for additional barcodes, this allows users to create duplicate barcodes
The above 2 issues cause uncertainty when a product is scanned, as we are unable to determine which product to use. 2. SOLUTION: - When saving inventory master, raiserror if UPC is duplicated
- Add a new table LBS_Inventory_Barcodes
- Add a maintenance form in POS-WEB to maintain barcodes in 2.2 above
- Perform data conversion to move barcodes from additional text 1-5 to 2.2 above.
- Change procedures to use new tables.
|
| Audit Notes: | |
| 28 Aug 2017 | 10:35AM Comment 1 by Alvis (Link Technologies) Case 8782 added to project 8.18 |
| 11 Sep 2017 | 03:34PM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 11-09-2017 03:34 PM Time Taken: 16.00 |
| Development work for this case has been completed. The change will be available in version: 8.18 Documentation update required(Yes/No. Add change details below): Yes QA required(Yes/No.Include areas that require testing): Yes
1. The following changes were made(Include Database object names, Program classes and any other relevant information):| - Added the ability to assign multiple barcodes to a product. New button on inventory maintenance form called barcodes.
- Added validation on PRODUCT CODE
- Added validation on UPC CODE
- Added validation on BARCODE
- Converted inventory maintenance save to SQL procedure
Important notes: - When upgrading customers, if you have used additional fields for barcode, you must insert the additional field data into LT_INV_InventoryBarcode table
|
|
| 21 Sep 2017 | 07:59AM Comment 3 by Vineshwar Prasad (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 21-09-2017 12:00 AM Time Taken: 1.00 |
| QA for product and Patch Releases Step 1 - Developer to system test changes until not issues are found - Alvis and Sanjay to sign off on System Test Step 2 - Product expert allocated by Consulting Manager for Product QA. Consulting Manager to allocate resource Consulting Manager to sign off on UAT and Generic Test
STEP 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below. Table 1 - Summarised list of issues | No | Issue Description | Resolved? | | 1 | Validate Product Code | Pass | | 2 | Validate UPC | Pass | | 3 | Validate Barcode | Pass | | 4 | Validate change Product Code with same Product Code | Pass | | 5 | Validate change Product Code with same UPC | Fail - changed successfully | | 6 | Validate change Product Code with same Barcode | Fail - changed successfully | | 7 | Validate Product Code from Excel upload template when uploading inventory | Pass | | 8 | Validate UPC from Excel upload template when uploading inventory | Fail - uploaded successfully | | 9 | Validate Barcode from Excel upload template when uploading inventory | Fail - uploaded successfully |
WORKFLOW: - Original case assigned to Development
- When the product is ready for release, System test details are entered into comments and the CASE HEADER Table updated.
- If system test passes, assign case to Consulting Manager for UAT
- If UAT Passes, Assign case for Documentation or close case
|
|
| 21 Sep 2017 | 02:35PM Comment 4 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 21-09-2017 02:35 PM Time Taken: 2.00 |
| Completed the following: - Added product code validation in "change part number" process.
- Changed back-office code to display exact message returned from the procedure.
For excel template changes a case is already logged for migration to the new framework. Refer to case 8808. |
|
| 28 Sep 2017 | 12:16PM Comment 5 by Vineshwar Prasad (Edge Business Solutions) Assigned To: Rashna (Edge Business Solutions) Followup Date: 28-09-2017 12:00 AM Time Taken: 1.00 |
| QA for product and Patch Releases Step 1 - Developer to system test changes until not issues are found - Alvis and Sanjay to sign off on System Test Step 2 - Product expert allocated by Consulting Manager for Product QA. Consulting Manager to allocate resource Consulting Manager to sign off on UAT and Generic Test
STEP 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below. Table 1 - Summarised list of issues | No | Issue Description | Resolved? | | 1 | Validate Product Code | Pass | | 2 | Validate UPC | Pass | | 3 | Validate Barcode | Pass | | 4 | Validate change Product Code with same Product Code | Pass | | 5 | Validate change Product Code with same UPC | Pass | | 6 | Validate change Product Code with same Barcode | Pass |
WORKFLOW: - Original case assigned to Development
- When the product is ready for release, System test details are entered into comments and the CASE HEADER Table updated.
- If system test passes, assign case to Consulting Manager for UAT
- If UAT Passes, Assign case for Documentation or close case
|
|
| 09 Oct 2019 | 08:14AM Comment 6 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - This case was created before quality check was implemented in version 11 on 30/06/2019 |