My Oracle Support Banner

Date Update For Order Via XML Does Not Propagate To Shipments Properly For Multi-leg (Doc ID 2848573.1)

Last updated on FEBRUARY 17, 2022

Applies to:

Oracle Transportation Management Cloud Service - Version 21.3 and later
Information in this document applies to any platform.


Date update for Order via XML does not propagate to Shipments properly for multi-leg.

Here is the scenario:
- Order is scheduled to ship in 2 weeks and is already planned in OTM
- 3 Shipments exist for the Order (Multi-leg AND re-use Equipment)
- Order receives update via XML to adjust dates, so Order ships 1 week earlier
- Date Update then gets propagated to related Shipments in OTM
For some reason, the update does not carry correctly to all multi-leg shipments... it only updates Leg 1 correctly. Leg 2 and Leg 3 only get shifted by 3 days instead of 7 days.  Reason is because Order Movement Dates for Leg 2 and Leg 3 are not updating correctly to be aligned with the new Order Release Dates.
Here are the dates :

Before Update:
Order Release Early Pickup = 11/24/2021
Order Release Late Delivery = 12/22/2021
Leg 1 Shipment = 11/24/2021 to 11/27/2021 (3 day transit time)
Leg 2 Shipment = 11/27/2021 to 12/16/2021 (20 day transit time)
Leg 3 Shipment = 12/16/2021 to 12/21/2021 (5 day transit time)

After Update(via XML) Pickup dates moved:
Order Release Early Pickup = 11/17/2021
Order Release Late Delivery = 12/15/2021
Leg 1 Shipment = 11/17/2021 to 11/20/2021 (3 day transit time)
Leg 2 Shipment = 11/24/2021 to 12/13/2021 (20 day transit time)
 -------Should be 11/20/2021 to 12/10/2021
Leg 3 Shipment = 12/13/2021 to 12/18/2021 (5 day transit time)
 -------Should be 12/10/2021 to 12/15/2021




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.