Lane Definitions: Header

This page is accessed via Shipment Management > Power Data > Geography > Lane Definition.

A lane connects two geographic points. The geographic points can be specific, such as a street address, or more general, such as a city, state, country, or region. Lanes are associated with rate records to help establish the costs associated with traveling between particular locations or areas. Lanes are required for rates and itineraries. They provide the basic geographic framework for shipment activity.

A lane is defined by its source and destination geographic points. Lanes are used for rates when determining cost and by itineraries when determining routes.

You can specify the source and destination of a lane by geo hierarchies or by regions. A geo hierarchy is a set of specifiers for a geographical unit (for example, country, city, location). A region identifies a geographic area.

You can also associate tender timeout information for a lane and have that used instead of service provider-specific tender timeouts.

If you specify the source and destination by geo hierarchies, you can mix and match their specificity. For example, define the source as a city and the destination as a country.

You can also associate a lane with a specific distance between its source and destination.

The property glog.xlane.alwaysCreateNew determines if Oracle Transportation Management should modify the current XLane or create a new XLane each time a rate record or itinerary is modified. The default is to modify the lane.

Note: Although lanes can be shared by different business objects, the planning logic does not use this relationship when searching by lane. For instance, you could setup a single "PA-> CA" lane and use it for both a rate record and a lane based rate service. The planning logic independently queries the rate record and rate service using the best matching lane.

Lane Header

Use this tab to specify the source and destination by geo hierarchies or by regions, but not by both.

1. Enter a unique Lane ID to identify the lane.
2. If applicable, you will see a link for the Sourcing Lane ID. This link opens the Sourcing Lane Definition page which contains all Sourcing related attributes for this lane. You will only see this link if Sourcing attributes are specified for the lane.
3. Specify a Source Geo Hierarchy ID or a Source Region ID to identify the source of the lane. The options you choose affect the fields available on the next tab.
4. Specify a Destination Geo Hierarchy ID or a Destination Region ID to identify the destination.
5. Click Lane Definitions to view the next tab.

Note: For Sourcing, make sure that all ocean lanes are unique based on the following: lane ID, equipment group, source & destination arbitrary lane, and source & destination arbitrary region.

If the combination of ocean lane, arbitrary lanes, arbitrary regions, and equipment group matches another lane in your lane summary, you cannot save your changes. To resolve this, change one of the fields to make the combination unique and save again.