Operational Planning
Comparing Order Versus Shipment Commitment Lane Object Types
This is an example to understand the difference between a Commitment Lane Object Type of Order versus Shipment.
An order has an origin of Chicago and a destination of Brussels.
You have Planned Allocations defined with both an Order and Shipment Commitment Lane Object Type.
There can be different types of shipments built in Oracle Transportation Management to accommodate this order based on data defined, such as itineraries, rates, etc. In this example, three different shipments could be built.
Example 1:
For this shipment, it is marked Primary:
- Lane Object Type = Order
This will count towards Capacity Commitment Allocation when the lane is Chicago > Brussels.
- Lane Object Type = Shipment
This will count towards Capacity Commitment Allocation when the lane is Chicago > Brussels.
Example 2:
Shipment 2 is marked Primary:
- Lane Object Type = Order
This will count towards Capacity Commitment Allocation when the lane is Chicago > Brussels.
- Lane Object Type = Shipment
This will count towards Capacity Commitment Allocation when the lane is NYC > Antwerp.
For Shipment 3 and Shipment 4:
- Lane Object Type = Order
Neither are primary shipments so neither will be accounted for in Allocations.
- Lane Object Type = Shipment
This will count towards Capacity Commitment Allocation only.
Example 3:
Shipment 5 is marked Primary:
- Lane Object Type = Order
This will count towards Capacity Commitment Allocation when the lane is Chicago > Brussels.
- Lane Object Type = Shipment
This will count towards Capacity Commitment Allocation when the lane is Chicago > Antwerp.
For Shipment 6:
- Lane Object Type = Order.
It is not a primary shipment so it will be accounted for in Allocations.
- Lane Object Type = Shipment
This will count towards Capacity Commitment Allocation only.