Transactions stuck in Delivery Details with OM Interface = NO, but INV interface = YES
(Doc ID 1537132.1)
Last updated on DECEMBER 10, 2024
Applies to:
Oracle Shipping Execution - Version 12.0.6 and laterInformation in this document applies to any platform.
Symptoms
WSH_DELIVERY_DETAILS shows many deliveries with OM Interfaced flag = N (no), but INV interfaced flag = Y (yes)
This is not an expected state, since Interface Trip Stop processes OM Interface first, and if OM interface fails, INV interface is not attempted.
Customer needs to clean up this data inconsistency.
This issue was disclosed on an SR where many other delivery details were failing in Interface Trip Stop and both interfaced flags were N.
It is unclear whether ITS originally erred out or not, for these delivery details.
This would likely NOT prevent period close activities, since if Inventory Interface has completed successfully, there should not be any unprocessed shipping transactions in Inventory.
Changes
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 |
Changes |
Cause |
Solution |
References |