How To Prevent Orphan Deliveries Which are not associated To Any Lines
Last updated on NOVEMBER 20, 2016
Applies to:Oracle Order Management - Version 12.0.6 and later
Information in this document applies to any platform.
***Checked for relevance on 20-NOV-2016***
Form:WSHFSCDL.FMB - Ship Confirm Deliveries
Via the following the steps customer is encountering Orphaned Delivery `s 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.
To check for any open deliveries the following script can be run
FROM wsh.wsh_new_deliveries wnd
WHERE wnd.status_code = 'OP'
and NOT exists (select 'Y'
from wsh.wsh_delivery_assignments wda
where wda.delivery_id = wnd.delivery_id);
If any rows are returned - a data fix will need to be logged with Oracle Support to remove these records .
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms