Move OM To Shipment Action Does Not Trigger Redrive For All Shipments In Shipment Graph
(Doc ID 2599551.1)
Last updated on NOVEMBER 14, 2019
Applies to:Oracle Transportation Management Cloud Service - Version 19 to 19.3 [Release 19]
Information in this document applies to any platform.
This is a Multi-Leg scenario as explained below
OR 1 - Planned on to 2 Shipments
OR 2 - Planned on to 2 Shipments
Both Orders are same in all respects except a difference on EPD:
Order 1 has EPD = 11/12/2019 10:00:00
Order 2 has EPD = 11/12/2019 09:00:00
First Leg Order Movement from Order 1 is moved to shipment with first leg order movement of second order
In other words 1st leg OMs are consolidated
The problem is with Second Leg time. Downstream shipment directly linked with target shipment (the shipment that we moved Order Movement to) is re-driven.
But the other shipment (the one that was initially linked to a shipment that was removed during Move action) is not re-driven:
The issue can be reproduced at will with the following steps:
1. Plan the 2 Orders and then move Order Movement of order 1 to shipment 2
2. Second leg shipment is not re-driven
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