Itinerary Leg Detail

This page is accessed via Shipment Management > Itinerary Management > Itinerary Manager. From the List Legs tab, click New Leg.

The Leg Detail page defines requirements associated with a particular location. For example, leg details can specify scheduling priorities, rates, intermediate stops, service providers, commodities, and modes of transport. In order to use an itinerary, shipments must be able to adhere to these requirements.

For multi-leg itineraries, enter the Sequence Number of each leg. For example, an itinerary created for shipments from Philadelphia to Paris may be sequenced as follows:
- Leg 1: Truckload from Philadelphia to the Philadelphia International Airport.
- Leg 2: Air from the Philadelphia International Airport to the Charles de Gaulle Airport.
- Leg 3: Truckload from the Charles de Gaulle Airport to Paris.
Note: If creating an itinerary leg from the Itinerary Leg manager, the Sequence Number is not entered, but an Itinerary Leg Name is entered.
Use the Leg Name as a user-specific identification of the leg in addition to the system-generated Leg ID.
Define the Primary Leg for multi-leg itineraries. The primary leg obeys the constraints of order releases that use the itinerary. For example, it uses the transport mode, service provider, and equipment that appear on the order release.
Enter a Rate Offering ID to indicate that a specific rate offering must be used for any shipment that is created for this leg. Oracle Transportation Management then selects an appropriate rate record for that rate offering.
Note: If you decide to use the constraints for rate offerings and itineraries, these entries override the "Active" state of those business objects as well as any effective or expiration dates that have been recorded for the business object. For example, if you specify a rate offering that is marked as inactive in the Rate Manager, Oracle Transportation Management will assign the Rate Offering that you specify regardless of the fact that it is marked inactive. The assumption is that these constraints always take precedence.
Alternatively, you can specify that a Rate Record must be used.
Assign a Leg Classification to label the itinerary or to have order release constraints applied to this leg when building shipments from this leg.
The Ignore Representative Location check box specifies whether Network Routing logic will ignore the representative locations of the source and destination regions of the leg. By default, this field is left unchecked.
If the itinerary is used by shipments carrying hazardous material, enter a Hazmat Region ID. When carrying hazardous material, shipments must obey rules based on the region where the material is going.
The Intermediary Corporation defines a 3PL or other intermediary associated with the leg. An intermediary corporation contracts with a service provider to move freight on behalf of the customer. Use this field to identify the corporation that acts as the intermediary. Oracle Transportation Management copies involved party contacts to shipments and bills based on your entry for this leg.
Enter a Network ID if the itinerary has an embedded network. You cannot specify both a Network ID and a Cross Dock Location.
Use the Cross Dock Location ID to associate the current leg with a cross-dock. Shipments that qualify go to the cross-dock before the destination defined on the leg. Shipments stop at the cross-dock and the orders are re-planned with orders on other shipments before proceeding to the leg destination. Enter details that determine which shipments use the cross-dock on the Step 1: Itineraries Parameters page. You cannot specify both a Network ID and a Cross Dock Location.
During planning, Oracle Transportation Management can assign equipment based on the attributes of the order/shipment (such as weight, size, and volume) and the equipment that is recorded in the database. You can use the following Equipment Assignment Type options on each leg of an itinerary to control how Oracle Transportation Management makes equipment assignments for that leg.
- Optimize Equipment allows Oracle Transportation Management to choose the appropriate equipment for each leg of the shipment. Oracle Transportation Management uses the container optimization algorithm to plan the appropriate equipment for subsequent legs. For example, you may have equipment used for drayage on the first leg of a shipment but different equipment used for ocean legs.
- Re-use Equipment uses the same equipment that was selected for the previous leg (as defined in Scheduling Priority above) of the itinerary. For example, a container may be packed at a stuffing location, taken by truck on one shipment to a port, taken by vessel on a second shipment to another port, and taken by truck on a third shipment to a de-stuffing location. You would typically use this attribute on legs subsequent to the first leg to constrain the use of the same equipment group across legs. When used on the first leg, this works the same as Optimize Equipment.
- No Equipment does not assign any equipment and skips container optimization during shipment planning.
By default, Oracle Transportation Management creates separate shipments for each leg that requires more than one equipment based on the container optimization results. However, you can mark the Create Single Shipment check box to have Oracle Transportation Management create one shipment for the leg and assign multiple equipment. If you want to place multiple equipment on the same shipment, then you must select this check box.
The Payment Method Code identifies the manner in which payment is made on a shipment. The payment method code from the order base is copied to each shipment that is created from the order base unless you have specified payment method codes on the legs of the itinerary that was used to create this shipment. In this case, the payment method code on the leg of the itinerary is copied to the shipment (overriding the code specified on the order).
Auto Consolidation Type defines the way shipments on this leg get consolidated. Choose one of the following options:
- No Auto Consolidation indicates that there is no consolidation or multi-stop planning on this leg.
- Multi-stop into One Equipment indicates that shipments built on this leg are sent to multi-stop algorithm to consolidate into multi-stop shipments with one piece of equipment for each multi-stop shipment. Only the first leg and last leg of an itinerary can have this Auto Consolidation Type.
- Consolidate into One Equipment: indicates that shipments built on this leg with the same Source and Destination Locations are consolidated together if they can fit into one piece of equipment.
- Consolidate into One Shipment/Multiple Equipment indicates that all shipments built on this leg will be consolidated into one shipment (if time window is feasible) with multiple equipment.
The following rules apply for Auto Consolidation, Equipment Type, and Create Single Shipment options:
- Only the first and last leg of an itinerary can have the Multi-stop into One Equipment Auto Consolidation Type.
- The Equipment Assignment Type of the first leg can not be Re-use Equipment
- If a leg's Equipment Assignment Type is Optimize Equipment and its Auto Consolidation Type is either Consolidate into One Equipment or Consolidate into One Shipment/Multiple Equipment, the next leg's Equipment Assignment Type must be Re-use Equipment and all subsequent leg's Auto Consolidation Type cannot be No Auto Consolidation.
- If a leg's Equipment Assignment Type is Optimize Equipment and its Auto Consolidation Type is No Auto Consolidation, its next leg's Equipment Assignment Type must be Re-use Equipment and all subsequent Re-use Equipment legs' Auto Consolidation Type cannot be Consolidate into One Equipment or Multi-stop into One Equipment.
- If Create Single Shipment is marked, the Auto Consolidation type cannot be Consolidate into One Equipment or Multi-stop into One Equipment.
- If a leg's Equipment Assignment Type is Re-use Equipment, this leg's Equipment Group Profile/ Equipment Group Profile Set must be the same as the previous leg.
Mark the Use Consol check box to indicate that this itinerary leg can be used as a candidate for building a consol shipment for a charter voyage or flight.
Enter a Leg Consolidation Group ID.
Enter VIA Locations.
Select a Trans-shipment Arbitraries Search Type.
Enter a Depot Profile ID to override the depot profile on the itinerary for order release and order movement planning.

Destination Location

This section defines the destination location of a leg. Define the destination as a particular location, group of locations, or as a radius where different points within the area can act as a destination. Also, assign a role to the destination describing the type of activity that occurs there.

Note: For the final leg of the itinerary you can leave this section blank. Oracle Transportation Management assumes that the destination of the final leg of the itinerary is the same as the destination on the order. OR, if you leave the destination information blank for any leg, Oracle Transportation Management can create intermediate legs using the destination on the order.

Location Roles determines the type of shipment related activity that occurs at a location.
Note: If you complete this field, you must enter a value in the Location ID, Location Profile, or Location Radius fields.
When the Assign Operational Locations to Stops check box is selected, Oracle Transportation Management uses the Operational Location assigned to the Destination Location for this leg. Operational Locations are used when transporting goods to and from ports, airports, or rail ramps. They allow you to define different points within a location that goods are delivered to or picked up from. They are defined in the Operational Location section of the Location Manager. When this option is selected, Oracle Transportation Management makes the Operational Location the Location for the stop, and makes the main location the Parent Location. This can be seen in the view shipment page after it is planned.
Select a Location ID to identify the destination as a specific location.
The Location Radius field creates a radius around the destination location. The leg can use any location within the radius with the same role as the destination location. Enter a numeric value and a distance measure (miles, kilometers, or nautical miles) to represent size of the area. You can limit the number of locations that are evaluated by the planning logic when building a shipment by using the Max Location Count field.
You can use the Location Radius Emphasis field to determine the location that acts as the geographic center for the location radius. Make a selection from the Location Radius Emphasis drop-down menu: Select Order Source or Order Destination to assign a radius around locations defined on the order, or select Leg Location to assign the location defined on the leg.
Note: For itineraries based on regions, if the Location Radius Emphasis field is valued, but the Location Radius field is not, destination locations are determined based on the region ID and the location role defined on the leg. All locations in the region with the same location role as the one defined on the itinerary can act as the destination. You can use this method to pinpoint locations in a region as destination that have specific roles, such as airports or seaports.
Enter a Location Profile to identify a specific list of locations that can be used for the destination. Location profiles are created in Power Data.

Leg Interim Points

A leg interim point adds one or more stops between the source and destination locations. For example, you can use interim points to identify a border crossing or a stop over during the night. An interim point is a reference point for shipment activity, where nothing is loaded or unloaded from the equipment.

Note: Calendars on interim stops are not considered. Calendars on interim stops do not work with service time calculation and LOAD/RECEIVE calendars are only for pickup and dropoff stops (which interim stops cannot do).

Select an interim point option.
Enter a value in the Sequence Number field that determines the order in which the interim stops occur. The Interim Points are listed in ascending order by their sequence number.
Enter a Location ID for the location of the interim stop.
Click Save for each interim point sequence number you enter.

Cost/Service

This section determines the estimated cost and travel time for the leg.

Select the Calculate Contracted Rate check box if you want Oracle Transportation Management to calculate the cost and service time associated with the leg. When selected, Oracle Transportation Management runs processing to locate a rate for the leg. Oracle Transportation Management searches for a rate based on the lane information and matches that to the source and destination on the leg of the itinerary.
If you clear the Calculate Contracted Rate check box, enter a cost in the Expected Cost field; otherwise, no cost is applied to the leg.
Select the Calculate Service Time check box to allow Oracle Transportation Management to select the service time from the rate offering that applies to the leg. Service time is made up of details such as, drive time, work time, and rest time which are associated with travelling from one location to another. For the transportation modes air, rail, and vessel travel, the service times are calculated based on transportation schedules available for each mode.

Note: If using arbitrary locations on an itinerary, this check box must be selected, otherwise OTM will not be able to calculate a service time for that leg and when trying to plan the order via show routing options, planning will fail.

If you clear the Calculate Service Time check box, complete the Expected Transit Time field, enter a time value, and select a time duration (e.g., days, weeks, months) for travel time; otherwise, no service time applies for the leg. When you select an itinerary, Oracle Transportation Management converts the Expected Transit Time unit of measure to the unit of measure in your user preferences. For example, if you enter 3 days, and your preferred unit of measure for duration is hours, Oracle Transportation Management converts the Expected Transit Time to 72 hours.
Note: Except for the primary leg, all other legs should have an Expected Transit Time which is used to create time windows on the order movements.
During shipment planning, a service provider is assigned to each shipment based on the attributes of the order, itineraries, and rates defined in the database. You can use the following Service Provider Assignment Types on each leg of an itinerary to control how service provider assignments are made.
- Re-use Service Provider uses the same service provider that was selected for the first leg of the itinerary. You would typically use this attribute on legs subsequent to the first leg to constrain the use of the same service provider across legs. When used on the first leg, this works the same as Optimize Equipment.
- Optimize Service Provider allows Oracle Transportation Management to choose the cheapest service provider for each leg of the shipment.

Compatibility

This section defines the mode of transportation, the service provider, and special equipment required for the leg.

Mode Profile IDs are groups of transportation modes that have similar attributes. Only shipments that use transportation modes that are included in the mode profile can use this itinerary. Define mode profile IDs in Power Data.
Note: If the order does not have a transport mode, then Oracle Transportation Management selects one on based on the rate. If Oracle Transportation Management chooses a mode from the rate, then the Mode Profile field on the itinerary is not used.
Use the Service Provider Profile ID field to assign a particular service provider.
You can identify and define a group of rate services that have some similar attributes. This group is called a Rate Service Profile. A Rate Service determines the time required to transport goods from one location to another.
Use the Equipment Group Profile ID to limit the equipment choices allowed for this itinerary leg. For example, you can create a Group Profile called Dry Vans that include the 28 FT Dry Van and 24 FT Dry Van Equipment Groups. Define Equipment Group Profile ID in the Equipment Manager.
Multi-Modal Equipment Sets allows Oracle Transportation Management to evaluate multiple equipment options within an itinerary for both the multi-leg and multi-stop algorithms. You can specify an equipment group profile set on the leg of an itinerary that supports multi-stop planning. You can specify a single equipment group profile or a set containing multiple equipment group profiles and Oracle Transportation Management will select the best fit equipment group from within each profile and rate it. The least-cost feasible option across all these equipment groups will be chosen.

Involved Party

Use this section to assign involved parties to the itinerary.

Commodities

You can define a particular Flex Commodity Profile (e.g., meats, vegetables, or pens) to the leg. Only the commodity you enter can be carried on this leg of the shipment.

Rail

The Rule 11 Instruction field specifies whether the leg of a shipment is governed by the rail industry's Rule 11 provision for interline shipments. If Rule 11 does not apply to the leg, select the default value, NOT RULE 11. If the leg is the tendered first leg of a Rule 11 shipment, select TENDER THIS SHIPMENT. If the leg is the non-tendered second leg of a Rule 11 shipment, select SETTLEMENT ONLY, NO TENDER. The Rule 11 Instruction pertains to Rule 11 shipments, but the other fields can be used for any type of rail shipment.
Note: Rule 11 shipments can be combined with other shipments.
The Rail Intermodal Service Plan Code is a two-digit code identifying the type of intermodal service plan for this leg (for example, 15 for Plan 15, ramp-to-ramp). These codes are determined by the American Association of Railroads (AAR).
Use Customer or Shipper Rate to specify whether the rate for this leg of a shipment was agreed upon between the rail carrier and the customer or the shipper.
Note: Typically, the tendered first leg of a Rule 11 shipment uses a shipper rate, and the non-tendered second leg uses a customer rate.
Use COFC/TOFC to specify the mode of the rail shipment. The options are CONTAINER ON FLAT CAR (COFC), TRAILER ON FLAT CAR (TOFC), and CONTAINER AND CHASSIS ON FLAT CAR. In most cases, rates for COFC shipments are lower than those for TOFC shipments because containers can be double-stacked on flat cars, but trailers cannot.

Schedules

Use this section to assign one or more Static or Dynamic Trip Templates to an itinerary leg. Trip templates are used for creating empty shipments for a predetermined route and then moving order releases on to those shipments.

Capacity Override

Use this section to assign one or more equipment capacity overrides that model weight and volume restrictions for a leg.