Late Posted Transfer Shipment Of A New Item Does Not Create Entry In STAKE_SKU_LOC
(Doc ID 2984473.1)
Last updated on NOVEMBER 07, 2023
Applies to:
Oracle Retail Merchandising System - Version 15.0.3 to 15.0.3 [Release 15.0]Information in this document applies to any platform.
Symptoms
On : 15.0.3 version, Inventory Movement
ACTUAL BEHAVIOR
---------------
When a late posted transfer shipment comes for a store having an unprocessed stock count, it does not create entry in STAKE_SKU_LOC.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a stock count wfor a store ith STOCKTAKE_DATE as VDATE+0.
2. Run refeodinventory.sh, stkxpld, stkupd etc so as to populate STAKE_SKU_LOC.
3. Move VDATE to VADTE+1.
3. Create an EG transfer shipment to the store with a new item where the item is not ranged to the store before having SHIP_DATE same as STOCKTAKE_DATE.
4. Item is ranged to the store but there is no entry in STAKE_SKU_LOC for the newly ranged item.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |