How To Prevent Orphan Deliveries Which are not associated To Any Lines
(Doc ID 1086057.1)
Last updated on OCTOBER 06, 2023
Applies to:
Oracle Order Management - Version 12.0.6 and laterOracle Shipping Execution - Version 12.0.6 and later
Information in this document applies to any platform.
Form:WSHFSCDL.FMB - Ship Confirm Deliveries
Symptoms
Via the following the steps customer is encountering Orphaned Deliveries which are not associated to any lines .
1) Via an API the lines of an order are assigned a delivery number by the reserve program
2) The order is sent to OTM and then to WMS
3) The order is not able to ship for one reason or another and the order comes back into EBS Order Management as a backordered line and the delivery is removed from the lines
4)The backorder is accepted and a new delivery is assigned to these lines via the autocreate delivery process
5)The original delivery header still remains in an open status without any lines associated
This happens any time all lines are unassigned from a delivery and a new delivery is auto-created.
If any rows are returned, a data fix will need to be logged with Oracle Support to remove these records.
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 |