Shipment Ship Unit Count Downstream Propagation Action Doesn't Create An Order Movement On The Downstream Shipment.
(Doc ID 1417003.1)
Last updated on JULY 09, 2014
Applies to:Oracle Transportation Management - Version: 6.2.0 to 6.2.5 - Release: 6.2 to 6.2
Information in this document applies to any platform.
Propagate Downstream shipment's action does not create an Order Movement for the second leg shipment with the changed s_ship_units count as same to what happens on the first leg shipment.
The issue can be reproduced at will with the following steps:
1. Creates an OR.
2. Plan the Order on three Order Movements.
3. Plan the first and second OMs on shipments with two leg itinerary and change the Ship Unit count on the first shipment, then run the Propagate Downstream action. OTM will create an OM with the changed Ship Unit count for the first shipment, but there is no another OM created with the changed Ship Unit count for the second shipment.
OM1 > SH1 > Change SU count > Propagate downstream > OM4 created (taken off SUs)
OM2 > SH2 > (taken off SUs) propagated to SH2 > expects OM5 to be created (taken off SUs)
In case 2 shipment built on 2 legs itinerary, you expects another order movement (OM5) to be created off the second (downstream) shipment with the propagated ship units as same as what happened on the first shipment.
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