Subject: | Migrate Inventory upload template to use new framework |
Summary: | Migrate Inventory upload template to use new framework as the current template is old and have issues in validating data. |
Audit Notes: | |
12 Sep 2017 | 10:39AM Comment 1 by Alvis (Link Technologies) Case 8808 added to project 8.19 |
01 Nov 2017 | 09:25AM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 01-11-2017 09:25 AM Time Taken: 16.00 |
| The following changes have been made: - Merged inventory upload template with Payroll upload template as new file "LinkSOFT_UploadTemplate.xls"
- Migrated Bin, UOM, UOM Conversion, Category, Sub Category, Supplier, Inventory, Inventory list, Kit Item, Product Price, Location Price.
- Removed "Bulk Cost Update" and "Create Stock Take" sheets. These functionalities should be used from the application.
|
|
16 Nov 2017 | 09:31AM Comment 3 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 16-11-2017 09:31 AM Time Taken: 3.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. Tested case in QA1 with database LINKSOFT. Version 819.Beta 1 Table 1 - Summarised list of issues I No | Issue Description - Inventory Upload Template | Resolved? | 1 | Users should be able to successfully connect with details on the Server Info Sheet | Pass | 2 | Company drop down should list company details at validate on all sheets | Pass | 3 | All codes on Inventory sheets should be validated for special characters and spaces | Pass | 4 | Bin details should be successfully validated and uploaded | Pass | 5 | UOM should be successfully validated and uploaded | Pass | 6 | UOM Conversion, should be successfully validated and uploaded | Failed. When we validate the sheet the description is automatically updated as STD and message is "record already exists". See Figure 1 | 7 | Category should be successfully validated and uploaded | Pass | 8 | Sub Category should be successfully validated and uploaded | Pass | 9 | Supplier should be successfully validated and uploaded | Pass | 10 | Product should be successfully validated and uploaded | Failed, validating product gives a "Type Mismatch" error. See Figure 3. | 11 | Inventory List should be successfully validated and uploaded. Correct Adjustment should be created and user should be able to post adjustment to 519. | Pass | 12 | Kit Item should be successfully validated and uploaded | Pass | 13 | Product Price should be successfully validated and uploaded
| Pass | 14 | Location Price should be successfully validated and uploaded
| Pass |
Table 2 - Summarised list of issues No | Issue Description - Payroll Upload Template | Resolved? | 1 | Users should be able to successfully connect with details on the Server Info Sheet | Pass | 2 | Company drop down should list company details at validate on all sheets | Pass | 4 | Cost Centre should be successfully validated and uploaded | Pass | 5 | Position should be successfully validated and uploaded | Pass | 6 | Direct Bank should be successfully validated and uploaded | Pass | 7 | Allowance and Benefit should be uploaded successfully with both date and value setup | Pass | 8 | Deduction should be uploaded successfully with both date and value setup | Pass | 9 | Leave should successfully validated and uploaded from excel | Data is uploaded, but there are data issues logged Case 8914 | 10 | YTD should be successfully validated and uploaded | Pass | 11 | Timesheet should be successfully validated and uploaded | Pass | 12 | Current Pay Insert details should be successfully validated and uploaded. Leave transaction should be created when selected as Yes. Leave should be marked as SOLD created when selected as Yes
| Pass | 13 | Employee Rate Change should be successfully uploaded. Rate should be included in the pay creation
| Pass | 14 | Position History should be successfully validated and uploaded
| Pass | 15 | Grade History should be successfully validated and uploaded
| Pass | 16 | Employee Shift Change History should be successfully validated and uploaded
| Pass | 17 | Roster should be successfully validated and uploaded
| Pass | 18 | Attendance Summary should be successfully validated and uploaded
| Failed, if we put a taken figure in any leave code, LWOP without pay is updated as negative. We put 8 as the Taken amount for AAL see Figure 3. |
Figure 1: UOM record Already exist.
Figure 2: Inventory upload
Figure 3: Negative LWOP
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
|
|
16 Nov 2017 | 11:30AM Comment 4 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 16-11-2017 11:30 AM Time Taken: 2.00 |
| Hi Rashna, - UOM Conversion is resolved in beta2
- Inventory sheet is resolved in beta2
- Leave Balance sheet is correct. There are some prior transactions for this employee that is showing in the report.
- Attendance summary sheet. You need to use the business process of Hot Bread Kitchen when testing this sheet as it was designed specifically for the client.
|
|
18 Nov 2017 | 09:53AM Comment 5 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 18-11-2017 09:53 AM Time Taken: 2.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 | UOM Conversion, should be successfully validated and uploaded | Failed. Tested UOM conversion for a new product. Error - Record already Exist. Steps to Replicate. - File Copy Record a Product. Product Code Test
- In the excel
- Select Item "Test"
- Enter Description "Box of 36 to Each"
- UOM From set to "Box of 36"
- UOM To set to "EACH"
- Conversion put as 36.
- Validate.
Tried the above with STD code, error is the same. | 2 | Product should be successfully validated and uploaded | Failed. - Type Mismatch Error - Type a Product Code.
- Validate sheet - Type Mismatch Error
- Enter all the details - Type Mismatch Error
|
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
|
|
20 Nov 2017 | 08:09AM Comment 6 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 20-11-2017 08:09 AM Time Taken: 1.00 |
| Hi Rashna, I have updated the excel upload template. regards Alvis |
|
20 Nov 2017 | 01:44PM Comment 7 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 20-11-2017 01:44 PM Time Taken: 1.00 |
| Tested in QA2, working as expected. Proceed with UAT.
|
|
20 Nov 2017 | 03:30PM Comment 8 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 20-11-2017 03:30 PM Time Taken: 1.00 |
| Hi Team, Tested case with 819 Beta 3. - Inventory Upload template is not checking UOM as a mandatory field.
- When we click on upload we get error.
- The INSERT statement conflicted with the FOREIGN KEY constraint "FK_LBS_inventory_LBS_uom". The conflict occurred in database "LINKSOFT", table "dbo.LBS_UOM".
The above has been fixed by Alvis and will be available in the build. Hence case will be retested with build. Regards Rashna |
|
21 Nov 2017 | 07:31AM Comment 9 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 21-11-2017 07:31 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. Tested case in QA1 with database LINKSOFT. Version 819 Beta 3 Table 1 - Summarised list of issues No | Issue Description | Resolved? | 1 | Inventory should uploaded without errors | Pass |
Figure 1
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 10 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 |