STAKE_SKU_LOC Is Not Updated With Correct Qty From The Input File By The Batch
(Doc ID 2765539.1)
Last updated on APRIL 07, 2021
Applies to:Oracle Retail Merchandising Foundation Cloud Service - Version NA and later
Information in this document applies to any platform.
STAKE_SKU_LOC is not updated with correct qty from the input file by the Batch. As part of Physical Inventory, the data in the stake_sku_loc table is not updated with correct quantity. The sign of the quantity is getting reversed in upload in the table.
Steps to reproduce the issue.
1. Create a number of virtual WH's under a physical WH and restrict and protect all of them except for two.
2. Range multiple items to one of the non protected / non restricted VWH's.
3. Range the same items to all of the protected / restricted VWH's.
4. Create an inventory adjustment for a positive qty of 102 units at one of the protected and restricted VWH's.
5. Create a unit and dollar stock count for physical wh.
6. Run stkxpld, move the date forward and then run stkupd to take the snapshot.
7. The snapshot on hand qty is positive 102 for one of the protected / restricted VWH's and all other VWH's are zero.
8. Move the date forward and create an inventory adjustment for -246 units for the protected / restricted VWH in step 4 so that the on hand now moves from +102 to negative -144
9. Create a positive inventory adjustment of 144 units for the non restricted / non protected VWH.
10. The protected / restricted VWH has -144 and the non restricted / non protected VWH has +144
11. Create a stock count upload file for this item with a counted qty of 84 units.
12. Run the stock count upload process.
13. The physical count qty is updated to -18 for the protected / restricted VWH as it has subtracted the snapshot on hand value from the counted qty (84 - 102 = -18). This is incorrect as the physical count qty should be 84 as that what was in the input file from WMS.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document