Build Shipment on Leg

This page is accessed via Order Management > Order Movement > Order Movement > Actions > Operational Planning > Create Shipment > Build Shipment on Leg.

Order movements must have a status of OM_PLANNING-NEW, OM_PLANNING-UNSCHEDULED, or OM_PLANNING-FAILED.

This action requires your order movement to also have a Leg ID but does not require source and destination locations. With a leg, you can have location profiles and let Oracle Transportation Management determine the best locations to use.

If the orders have different priorities, OTM will not let the bundling go through.

Oracle Transportation Management does the following:

• Builds the cheapest shipment possible after trying all possible source and destination locations while minding the constraints on the leg.
• Sets the status of the order movement to OM_PLANNING-PLANNED-FINAL.
• If your order movement has no Destination Location, Oracle Transportation Management populates it with the Destination Location Oracle Transportation Management chose for the shipment.
• If your order movement has no Source Location, Oracle Transportation Management populates it with the Source Location Oracle Transportation Management chose for the shipment.
• If your downstream order movement has no Source Location, Oracle Transportation Management populates it with the Destination Location of the shipment.
• If your upstream order movement has no Destination Location, Oracle Transportation Management populates it with the Source Location of the shipment.
• Sets Operational Early Pickup of downstream order movement to End Time for the shipment you created + Estimated Transit Time of downstream order movement.
• Sets Operational Late Delivery on upstream order movement to Start Time of the shipment you created.

Validations

• Selected order movements should either contain consol leg or non-consol leg order movements.
• Selected order movements are on a reuse leg and there are more than one consol leg in the reuse legs. This is not a valid setup.
• All order movements on consol leg should be planned first when reusing equipment.
• Selected order movements must have the same travel path to perform this action.

 For example, let’s look at the following order movements with middle leg consol:

1. 1. OM11    ----   OM12 (consol and Reuse) — OM13 (Reuse)
   2. OM21   ----   OM22(consol) ---- OM23(Reuse)
   3. OM31   ----   OM32(consol) ---- OM33

In this example, middle leg order movements (OM12, OM22, and OM32) use consol.  

In the first case, all three legs reuse the same shipment equipment.

In the second case, only middle leg (OM22) and last leg (OM23) reuse the same shipment equipment and there is no reuse of shipment equipment in the third case.

If you select OM12 and OM22 or OM22 and OM32 or OM12 and OM32 or OM12, OM22, and OM32, OTM throws an error because these selected order movements don't have the same travel path.

OTM enables you to select order movements to all types of consol shipment (Flight, Chartered Voyage, and Ocean FCL).

Note: In case of reuse leg order movement, OTM plans order movements on consol leg first and only Ocean FCL consol is applicable. OTM will not consider Flight and Chartered Voyage consol.

Ocean FCL consol shipments contains multiple shipment equipment, so when you add order movement on such shipment, order movement can be split into multiple shipment equipment and additional order movements will be created, i.e, one order movement per shipment equipment.

If the split order movement has reuse leg order movement, this reuse leg order movement will also be split and share the same shipment ship unit with the consol leg order movement.

For example, let's look at consol shipment with reuse equipment:

A consol shipment can be used by multiple legs. You may have a consol shipment with shipment equipment which has different travel paths. For example, the below three itineraries have middle consol leg:

1. Itinerary 1:  Leg 1 – Leg 2(consol, reuse) – Leg 2 (reuse). (all three legs reuse the same shipment equipment)
2. Itinerary 2: Leg 4 – Leg 5(consol) – Leg 6 (reuse).  (middle leg and last leg share the same shipment equipment)
3. Itinerary 3: Leg 7 – Leg 8 (consol) - Leg 9 (no reuse)

When an Ocean FCL has four shipment equipment:  

• Order1 uses Itinerary 1 planned on the consol into shipment equipment 1 then shipment equipment1 has a travel path which goes through all three legs.
• Order2 uses Itinerary 2 planned on the consol into shipment equipment 2 then shipment equipment 2 has a travel path which goes through middle leg and last leg.
• Order3 uses itinerary 3 planned on the consol into shipment equipment 3 then shipment equipment 3 has a travel path which goes through just the middle leg.
• Shipment equipment 4 is empty.

Let’s look at few scenarios, when you run the Build Shipment on Leg action:

Case 1: OM11 —  OM12 (Reuse) — OM13 (Reuse):  When you select OM12 and run this action, the only shipment equipment on this consol that are valid to use is either shipment equipment 1 (with same travel path) or shipment equipment 4(which is empty).

Case2:  OM21 — OM 22 — OM23(Reuse): When you select OM22 and run this action, the only shipment equipment on this consol that are valid to use is either shipment equipment 2 (with same travel path) or shipment equipment 4.           

Case 3:OM31   —  OM32 — OM33: When you select OM32 and run this action, the only shipment equipment on this consol that are valid to use is shipment equipment 3(with same travel path), or shipment equipment 4(empty).