Shipmodviaordersumatch Processing Uses Data From Unrelated Stop
(Doc ID 754992.1)
Last updated on FEBRUARY 26, 2019
Applies to:Oracle Transportation Management - Version 5.5.04 to 5.5.04.06 [Release 5.5]
Information in this document applies to any platform.
This problem can occur on any platform.
-- Problem Statement:
On 5.5.04, When sending ShipModViaOrderSUMatch element in an Actual Shipment for a Shipment with 2 Orders, and the element is sending in details in such a way that one of the order is being split into two, the destination location of the second order is being set as the destination location of the split off order from the first one
Expect that destination location of the order that is split, maintains the original destination
-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Create two orders with different destination locations but the same source
2. Create Order Movements from them and bulk plan them into a multistop shipment
3. Then send in an Actual Shipment XML that has a ShipModViaOrderSUMatch element which is set with
a quantity less than the original quantity ( i.e. implicitly indicating that the order is being
4. When the XML is processed see that the destination location on the second order movement that
is created due to the split of the order release is set as the destination location of the second
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