SOH_UPDATE_DATETIME In ITEM_LOC_SOH Not Updated In Specific Scenario Of Reconciliation
(Doc ID 3062813.1)
Last updated on DECEMBER 09, 2024
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 24.1 to 24.1 [Release 24.1]Information in this document applies to any platform.
Symptoms
Creating a transfer for an item from WH to WH (the second one is not ranged for the item), approve and ship the transfer.
Then, go to the reconciliation screen and affect the loss at the receiving location.
We can see that the qty from IN_TRANSIT_QTY in ITEM_LOC_SOH is cancel but the field SOH_UPDATE_DATETIME is not updated at the receiving location.
The issue can be reproduced at will with the following steps:
1. Create a tsf from a location to another location : in your case, it was WH to WH with 1 item. This item has no item loc link for the WH2.
2. Approve the tsf (item loc is created automatically)
3. Ship the tsf => The qty is now in transit
4. Do not receive the tsf. Go to the reconciliation screen and affect the loss at the receiving location.
5. The qty in transit is cancel but the field SOH_UPDATE_DATETIME in ITEM_LOC_SOH is not updated at the receiving location
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 |