Subject: | Inventory Movement InStock is not equal to the Inventory Valuation InStock of the same period for clients having Standalone (failsafe) |
Summary: | Bula Vinaka Team, After fixing valuation cost, as per case: 10479, Customer has logged another scenario where the In Stock value in the Inventory Movement Report is not equal to the In Stock value of the Inventory Valuation report. Refer below example: - Product: 1502913 - BEV- FIJI GOLD QUARTS 12 X
- Generated the Inventory Valuation Report for the period 201906 for location "xm"
- The InStock value is -33
- Compared this with the Inventory Movement Report for the period 201906 for location "xm"
- The InStock value is -43
The database has been uploaded in FTP. Please review and advise. Kind Regards Aarti Gayaneshwar |
Audit Notes: | Edited by alvis on 10/09/19 08:32. Edited by alvis on 30/08/19 08:16. |
29 Aug 2019 | 03:56PM Comment 7 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 29-08-2019 03:56 PM Time Taken: 8.00 Notes: Edited by alvis on 30/08/19 08:10. Edited by alvis on 29/08/19 15:57. |
| Development work for this case has been completed. The change will be available in version: 10.150 1. The following changes were made(Include Database object names, Program classes and any other relevant information): - Replication data transmission when standalone servers are configured
2. Affected Areas: - Inventory ~> Valuation: When sales are done in a branch server having standalone setup.
3. The issue was caused by: - When a branch server is configured with standalone machines. This server is a parent and child. This caused data transmission for "Inventory Valuation" to be incorrect at "Head office".
4. Notes: To apply this update, follow these steps:
- Install version 10.150
- Apply the database upgrade to HQ, then Branch and standalone machines.
- Apply the script in HQ to mark entries to recompute valuation:
update LT_INV_Valuation SET Recalculate = 1 WHERE Period >= '201906' --The script will mark all items to recompute after June 2019. The period should be the month when the standalone setup was configured.
5. Next Step: UAT |
|
30 Aug 2019 | 08:08AM Comment 8 by Alvis (Link Technologies) Case 11702 added to project 10.150 |
03 Sep 2019 | 09:46AM Comment 9 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 06-09-2019 12:00 AM Time Taken: 3.00 |
| 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 | Step replication with a standalone server. - HQ - LINKSOFT-HQ
- Branch - LINKSOFT-B1
- Standalone - LINKSOFT-STANDALONE
Create a new product '1001'in the standalone db. Process an adjustment for the product for below dates - 3/09/2019 - 10 @ $7.5
- 1/09/2019 - 5 @ $6.5
Validate that these transactions are replicated to HQ and the valuation is processed to show instock as 15. Movement and Valuation should be 15. | Pass | 2 | Process a sale of the item with quantity as 2. Verify that the valuation and movement stock has been updated to 13. | Pass | 3 | Create an adjustment for product "1001" with date 30/08/2019 and quantity 20. - Validate that the valuation stock is 33 for period 201909.
- Validate that the valuation stock is 20 for period 201908.
Verify that the movement and valuation stock is 33 across all databases. | Pass |
Notes Link Business support team needs to verify the update in the client databases as we do not have full setup of the client. Environment Details - OS version: Windows Server 2012
- Application version: 10.1.150
- Setup: Demo
- Server : 10.0.0.14
- Database:
- HQ - LINKSOFT-HQ
- Branch - LINKSOFT-B1
- Standalone - LINKSOFT-STANDALONE
Next Step: - Closure
|
|
07 Sep 2019 | 02:29PM Comment 10 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 07-09-2019 02:29 PM |
| Thanks Rashna |
|
10 Sep 2019 | 08:32AM Comment 11 by Alvis (Link Technologies) Case 11702 removed from project 10.150 |
10 Sep 2019 | 08:32AM Comment 12 by Sanjay (Link Technologies) Case 11702 added to project 10.150 |