Last updated on JUNE 28, 2016
Applies to:Oracle Transportation Management - Version 6.4.1 to 6.4.2 [Release 6.4]
Information in this document applies to any platform.
When sending in a shipment actual that mixes order releases onto ship units the relationship of Order Movement to S_SHIPUNIT is not correctly formed.
Basically the shipment actual is sent in for the first leg of a multileg movement with a change in ship unit ID, the expectation is that the change be propagated to the downstream shipment.
However running the shipment actual xml in this scenario results in the downstream shipment being corrupted
A Specific example would be as follows:
a. A Delivery from EBS is transmitted to OTM where an Order Release from a Source Location called #1 to Destination Location called #3 is created with Ship Unit ABC.
b. The Order Release is planned using a MultiLeg Itinerary where 2 Shipments are created.
c. Shipment 1 representing Leg 1 from Source Location 1 to Deconsolidation Location 2 is created with S Ship Unit ABC.
d. Shipment 2 representing Leg 2 from Deconsolidation Location 2 to Destination Location 3 is created with S Ship Unit ABC.
e. After Ship Confirmation of Shipment 1 in EBS, the ActualShipment Transmission is sent from EBS to OTM and 3 things happen:
--- The Ship Unit associated to the Order Release is deleted and replaced with Ship Unit DEF
--- The S Ship Unit associated to Shipment 1 is deleted and replaced with S Ship Unit DEF
--- The S Ship Unit associated to Shipment 2 is deleted but not replaced
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