Subject: | "Inventory Movement" report should only show returns that have "Return to Stock" ticked. |
Summary: | "Inventory Movement" report shows history transactions after "Return to STock" is enabled for a "Return Reason" . Steps to Replicate Process an adjustment for an item (TESTCASE1) with quantity as 100. Process a sale with quantity as 15. Process the return of the sale with reason "Undercooked". "Return to Stock" is disabled. Return Quantity is 10. - 519 and "Inventory Movement" report should show instock as 85.
Process another sale with quantity as 10.
Process the return of the sale with reason "Undercooked". "Return to Stock" is ENABLED. Return Quantity is 2 - 519 and "Inventory Movement" report should show instock as 77. Fails. Inventory Movement report shows in stock as 87, the report includes both the returns. The report should only show the return of quantity 2.
Setup Version - 10.141 Database - LINKSOFT_REPORTNOTES Server - 10.0.0.14 |
Audit Notes: | Edited by sanjay on 11/09/19 15:17. Edited by alvis on 01/03/19 11:32. Edited by sanjay on 28/02/19 14:53. |
22 Feb 2019 | 10:11AM Comment 1 by Rashna (Edge Business Solutions) Case 10194 added to project 11.0 |
25 Feb 2019 | 02:02PM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 25-02-2019 02:02 PM Time Taken: 2.50 |
| The following change is required in POS Reason Maintenance: - Do not allow "Return To Stock" edit once the code is used.
- The workaround is to create a new reason code if "return to stock" needs to be changed.
|
|
04 Mar 2019 | 04:42PM Comment 3 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 04-03-2019 04:42 PM Time Taken: 3.50 Notes: Edited by sanjay on 04/03/19 16:42. |
| Development work for this case has been completed. The change will be available in version: 11.0.2 1. The following changes were made(Include Database object names, Program classes and any other relevant information):| - Change validation on UPDATE to prevent the user from changing "Return to stock" if the reason code has been used.
2. The issue was caused by: - Improvement requested
3. Next Step: - UAT
|
|
06 Mar 2019 | 02:48PM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 06-03-2019 02:48 PM Time Taken: 2.00 |
| Hi Alvis, If a reason has been used and a user enables "Return to Stock" for that reason and "Saves" the record, nothing happens. Please prompt a message to the user to advise that "Return to Stock" cannot be enabled for a reason that has been used. Steps to Replicate - Process a "Cash In" with reason "Undercooked".
- Enable "Return to Stock" for the reason and save.
|
|
08 Mar 2019 | 08:36AM Comment 5 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 08-03-2019 08:36 AM Time Taken: 2.50 |
| Development work for this case has been completed. The change will be available in version: 11.0.0308 1. The following changes were made(Include Database object names, Program classes and any other relevant information):| - Added "raiserror" when "return to stock" is used and the user is changing the value.
2. The issue was caused by: - Improvement
3. Next Step: - UAT
4. Notes: |
|
11 Mar 2019 | 11:17AM Comment 6 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 11-03-2019 11:17 AM Time Taken: 2.50 |
| Hi Sanjay QA Results Tests carried out according to requirements specified on the case header Test Results Summary Table 1 - Summarised list of issues No | Test Description | Pass/Fail | 1 | The system should prompt message when a user tries to check "Return To Stock" for a reason that has been used in previous transactions | Pass |
Notes Documentation updated under POS - Maintenance - Reason Environment Details - OS version: Windows Server 2012
- Application version: 11.0.308
- Setup: Demo
- Server : 10.0.0.14
- Database: LINKSOFT_REPORTNOTES
Steps to reproduce failed scenarios: N/A Next Step: for closure
|
|
11 Mar 2019 | 01:33PM Comment 7 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 11-03-2019 01:33 PM Time Taken: 1.50 |
| Thanks Rashna |
|
09 Oct 2019 | 08:14AM Comment 8 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 |