Distributed Organization: Delivery Name From Process Shipment Advice Changes During Processing (Doc ID 2276535.1)

Last updated on JUNE 13, 2017

Applies to:

Oracle Shipping Execution - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Ship Confirm

Context: Distributed Organization
The Process Shipment Advice includes the delivery name generated by 3rd party.
This delivery name is KEY as it is delivery number received by the customer.

Unfortunately, there is an issue: this delivery name is not populated into delivery name in EBS Shipping.
During the processing the delivery name changes and then is passed to Shipping.

For the sample order , the delivery name is S2B201702281445 from the 3rd party.

This is seen in the Process Shipment Advices log file:

Near the top of the log it shows the delivery name is S2B201702281445, which is correct
  Entering WSH_PROCESS_INTERFACED_PKG.DERIVE_IDS (WSHINPSB_mod.pls 120.4.12010000.7) (02/28/2017 03:10:04 PM)
  DELIVERY_INTERFACE_ID ==> 73010
  l_del_count ==> 1
  Inside Delivery Rec Loop ==>
  Delivery Attributes ==>
  Delivery Name ==> S2B201702281445
  Org Code ==> DW1
  Initial pickup ==> DW1_LOC

In the middle of the log it shows the delivery name is the same as the delivery id ....68356:
  Exiting WSH_INTERFACE_COMMON_ACTIONS.CREATE_UPDATE_TRIP_FOR_DLVY (02/28/2017 03:10:09 PM, .98 seconds)
  Return status from create-update-trip ==> S
  Delivery Name ==> 68356
  Entering WSH_PROCESS_INTERFACED_PKG.DELETE_INTERFACE_RECORDS (WSHINPSB_mod.pls 120.4.12010000.7) (02/28/2017 03:10:09 PM)
  DELIVERY INTERFACE ID ==> 73010

 It is observed that the delivery name changes from (S2B201702281445) to (68356)


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Create Sales Order 
2) Submit Request : Create Shipment Batches For Fulfillment
3) Submit the Process Shipment Advices
4) See the results in Shipping Transactions form (Delivery)
5) Delivery name is 68356 instead of S2B201702281445



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