Merging Shipments Created from Network Route Not Removing Replaced Shipments
(Doc ID 1642509.1)
Last updated on MARCH 05, 2019
Applies to:Oracle Transportation Operational Planning - Version 6.3.2 to 6.3.4 [Release 6.3]
Information in this document applies to any platform.
When merging 2 shipments (first leg) on a network route, the change is propagated to the rest of the shipments on the route so that the orders are now together on 1 shipment for each leg , the following issue occurs.
However, OTM is not removing the previous shipments, resulting in the order being planned on duplicate shipments.
The issue can be reproduced at will with the following steps.
Orders: both have same source/dest and same pickup times.
Parameter set id: NETWORK_1
LEG_HW1: optimize, sequence: -1 -REGION_1 -> PORT1_hw
LEG_HW3: re-use equipment, sequence 0, primary - PORT1 -> PORT2
LEG_HW5: re-use equipment, sequence: 1 – PORT2 -> REGION_2
Select each order and bulk plan it using the parameter set id Network_1
Each order will be planned on 3 shipments as the route
Query for the 6 shipments associated with the orders
Select the 2 shipments going from ORIGIN -> PORT1 and use action Operational Planning-> Change Shipment Route-> Merge shipments
Select parameter of NETWORK_1
Check the “ consolidate” box and click “optimize”
The 2 shipments will be merged
Re-query for the shipments associated with the orders
Notice that you now have 5 shipments (looking at the tree view):
1 shipment with both orders going from REGION1 to PORT1
1 shipment with order merge1 going from PORT1 -> PORT2
1 shipment with both orders going from PORT1 -> PORT2
1 shipment with both orders going from PORT2 -> DESTINATION
1 shipment with order merge1 going from PORT2 -> DESTINATION
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