Shipment Ship Unit IDs are not Unique for Multi-Leg Ground Schedule Shipments
(Doc ID 2641485.1)
Last updated on MARCH 02, 2020
Applies to:Oracle Transportation Management Cloud Service - Version 19.3 and later
Oracle Transportation Operational Planning Cloud Service - Version 19.3 and later
Information in this document applies to any platform.
When planning an order release using an itinerary with multiple legs (where each leg is assigned a ground schedule), the resulting shipments are assigned the same s_ship_unit_gid. For example, bulk planning a single order which plans onto 2 ground schedule shipments results in both shipments using the same shipment ship unit ID although the shipment equipment is unique for each shipment. Bulk planning the generated order movements for this order does not result in this issue and each shipment retains its own unique s_ship_unit_gid .
It is expected that each shipment be linked to a unique shipment ship unit ID since the shipment equipment is unique for each shipment.
The issue can be reproduced with the following steps:
1. Using a multi-leg itinerary (where each leg of the itinerary is assigned a ground schedule), plan an order release to multiple ground shipments
2. The resulting shipments will each be linked to the same shipment ship unit ID
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