Departure Ship Notice Outbound Errors With No Eligible Delivery for the DSNO (Doc ID 790618.1)

Last updated on JULY 12, 2017

Applies to:

Oracle EDI Gateway - Version 11.5.10.0 and later
Oracle Shipping Execution - Version 11.5.10.2 and later
Information in this document applies to any platform.

Symptoms

When attempting to interface any delivery for an sales order where the SOLD TO customer is different from the SHIP TO customer, the following error occurs. Interface Trip Stop completes successfully, but the expected DSNO file is not generated and sent to the SHIP TO customer:

ERROR
NO ELIGIBLE DELIVERY FOR THE DSNO
TERMINATING PROGRAM

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Order Management super user
2. Enter and book a sales order where the SOLD TO customer is different from the SHIP TO customer. For example:
Order is SOLD to customer Widgets incorporated. Widgets Inc. will be invoiced for the
order.  Order is shipped to a location belonging to XYZ Gadgets incorporated.
3. Pick release and ship confirm this order
4. Run interface trip stop
5. ITS logfile indicates successful completion. However, with respect to DSNO, see the following in the debug log file:

Entering WSH_DSNO.SUBMIT_TRIP_STOP (WSHDSNOB.pls 115.30.11510.2) (01/26/2009 01:32:40 PM)
P_TRIP_STOP_ID ==> 1208228
PROCESSING DSNO IN TRIP STOP 1208228
CHECKING EDI INSTALLATION STATUS
EDI INSTALLED: YES
DSNO PROFILE: ENABLED
NO ELIGIBLE DELIVERY FOR THE DSNO
TERMINATING PROGRAM

6. DSNO file is not generated, and is not delivered to XYZ Gadgets.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms