Replacing an Order Release Planned into a Multistop Shipment Via "ShipmentActual" Integration Creates Wrong Stops for the Related Order Movement
(Doc ID 2068776.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Transportation Operational Planning - Version 6.3.2 to 6.3.8 [Release 6.3]
Information in this document applies to any platform.
When trying to replace an Order Release planned into a multistop shipment via "ShipmentActual" integration, OTM creates wrong stops for the related Order movement.
Test case scenario
1. Plan 2 Order Releases with same source and different destination into a multistop shipment.
2. Update shipment via integration using "ShipmentActual" to replace first order with a new one.
3. Review the newly related Order Movement for the new order. Notice the stops are wrongly updated, the Order Movement has the right source, but the destination is the one of the secondary Order Release that is part of the same multistop.
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