Route Instance Leg

This page is accessed via Operational Planning > Cooperative Route Management > Route Instance Leg.

From the Route Instance Manager, only the View page is accessible. An instance leg is automatically created when its parent instance is created. Manual creation is not allowed. Once a route instance leg is associated with a shipment, no edits are allowed.

1. Instance ID: From the route instance.
2. Leg ID: is a unique identifier of the leg.
3. Leg Number: Must be a unique number and sequential with no gaps.
4. Equipment Group Profile ID: If different from the equipment group profile ID on the instance, this one overrides the other.
5. Start/End Region ID: Copied from the route template leg. The regions must have a representative location.
6. Start Distance Threshold: is the radius distance from the representative location of the start region.
7. Early/Late Departure/Arrival Time: All departure times must fall within the instances start and end dates. The early departure time for the first leg and the late departure time for the last leg are required. This determines the start and end date of the generated instance.
8. Time Phased Planning Threshold: If the duration between the system time and the instance leg's early departure time is within this threshold, and no shipments fall within the regions of the instance leg, Oracle Transportation Management will try to match shipments that are outside the region but within the time threshold.
9. Min/Max Time to Next Leg: indicates the minimum or maximum duration between the current leg's shipment end time and the next leg's shipment start time.
10. Match Shipment to Leg: indicates whether this leg should be matched to a shipment and if so, how to match. The allowable values are "Always", "When available" and Never". When a leg is marked "Never", planning will never match a shipment to this leg.
11. Assigned Shipment ID: The shipment ID. You can click it and drill down for details.
12. Assignment Type: indicates how well this shipment is assigned to the route instance from a geographical point. MOST SPECIFIC is within the region. WITHIN THRESHOLD is outside the region but within the threshold. NON STANDARD is outside the region and the threshold.
13. Assignment Source: Either SYSTEM or MANUAL: SYSTEM - assignment of shipment was made by Bulk Plan or Build Shipment Direct. MANUAL - assignment of shipment was made via manual action.
14. Warn for Missing Leg: indicates whether an alert should be sent out when the leg is marked missed.
15. Deviation Reason: shows the reason for the deviation.

Location Incompatibility

This section allows you define locations that are NOT compatible. Enter the Location ID and Activity for the incompatibility.

Order Compatibility

This section allows you define orders that are compatible. Enter the Order Reference Number Qualifier and the Order Reference Number to define the compatibility. Click Save after adding each compatibility.

Shipment Compatibility

This section allows you define shipments that are compatible. Enter the Shipment Reference Number Qualifier and the Shipment Reference Number to define the compatibility. Click Save after adding each compatibility.

Reference Numbers

Use this section of the page to assign reference numbers to the route instance leg.

You can define reference sequence numbers to define the display order of reference numbers and reference number qualifiers.

Remarks

The Remarks section provides a place for you to log any extraneous information you may want to keep with the route instance leg.

Involved Party

Use this section of the page to assign Involved Party contacts to the route instance leg.