Applies to:

Oracle Transportation Management - Version 6.2.7 and laterInformation in this document applies to any platform.

Symptoms

After merging two shipments, the SHIPMENT_GID field on an Order Movement is 'nulled'.

To reproduce:

1) Order Releases are planned with a single leg XDock itinerarya. Priority planning enabled (USE PRIORITY IN CONOPT SORTING)b. 3D Load Configuration in use

2) The created XDock inbound and outbound shipments are disbanded (Order Movements are retained)a. This is because normal XDock planning as described in (1) doesn’t support priorities for outbound shipments (XDock planning is using multistop algorithm)b. 3D Load Configuration in use

3) The Order Movements from disbanded outbound shipments are replannedin a separate bulk plan:a. This is now direct shipment planning and supports priority planning (within ConOpt, based on raw Priorities)b. Same itinerary used as in (1)c. Shipments are reviewed for approval by Planners who can improve planning results by using the merging Shipments. They will use the standard “Merge Shipment” action with either options:i. using the same Planning Parameter Set that was used for the outbound replanning (3) ORii. Optimize + Consolidate but change the Planning Parameter Set to a non-3D Load Config one which allows them to fit more Ship Units onto the resulting Shipment ORiii. Force Merge action

When using either of the 2 Optimize + Consolidate actions the described issue occurs intermittently.

When using the “Force merge” action the issue occurs every time.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a Million Knowledge Articles and hundreds of Community platforms