Rate Record

This page is accessed via Contract and Rate Management > Contract Management > Rate Record.

The Rate Manager allows you to manage rates for inbound and outbound goods for all transportation modes, including truckload and less-than-truckload, vessels, rail and air. A rate is considered a contract between the user and a service provider or a user and their clients. The Rate Manager stores information about effective and expiration dates, freight limitations, accessorials, and the rates themselves. Rates can be defined or limited by weight, volume, distance and commodity. In addition, a rate can model most industry practices such as deficit ratings, base and excess discounts, minimums and surcharges.

Note: Alternatively, you may choose to enter rates automatically via integration. See the Integration Guide on the Oracle Help Center.

One or more rate records can be associated with a single rate offering. While the offering provides general contractual details, the record defines a cost for service between one location and another. A record relies on an associated rate offering for much of its information but can override some of the data in the offering, if necessary.

After you define a rate offering or record, you can use the data when qualifying an order. Once pickup and destination locations are provided, an itinerary is chosen and the order is released, the shipment is matched with one or more qualifying rates. Rates qualify when:

• Rate constraints for weight, length and other units are met for the order and the itinerary.
• Time constraints for the order are met.
• Optional constraints, such as those requiring special equipment or services, are met.
• Geographical requirements are met.

Rate Record

Rate Records can only be created based on a rate offering. While the rate offering provides general contract details from a service provider, a rate record provides specific costing or rating data from one place to another. The record inherits much of its data from the offering but the options selected in the offering can be overridden at the record level.  

To create a rate record, first select the rate offering on which the record is to be based, and enter details for the record.

Note: Alternatively, you may enter rates automatically via integration. See the Integration Guide on the Oracle Help Center.

Creating a rate record using the Rate Manager consists of the following steps:

• Select a Rate Offering on the Search page to find a rate offering to use as the basis for the record.  
• Lane Info identifies how the source and destination points are defined for the rate.
• Attributes define the actual geographical points for which the rate is applicable as well as any attributes that may differ from those defined in the rate offering.
• Rate Costs identify how the cost of shipping is calculated, including information about ship units, equipment groups and actual rates.
• Accessorials outline any extra charges that may be applied.
• Special Services define any extra services that may be offered.
• Remarks allows you to add any remarks that are needed.

Note: Information entered in a rate record may override settings established in the associated rate offering.

When the Search rate offering page appears, search for the offering. When the Results page appears, select the rate offering and click Edit.

Oracle Transportation Sourcing Rate Records

You can use the Oracle Transportation Management rating structure for Oracle Transportation Sourcing. A rate is considered an Oracle Transportation Sourcing rate if you select the Sourcing Template check box on the rate offering.

Note: When creating an Oracle Transportation Sourcing rate offering, you should only associate a single rate record with that rate offering. A rate offering is an Oracle Transportation Sourcing rate if you select the Sourcing Template check box on the rate offering.

Also, when creating your rate costs you can only use a sub-set of the standard Oracle Transportation Management rate costs.

You can use Oracle Transportation Management rating to set up base costs, stop-off charges, accessorials, special services, and LTL weight break discounts. For cost definition, you can select the cost types of charge and discount. The external cost type is by definition not biddable and the cost type of profile is not supported by Oracle Transportation Sourcing.

Once a rate record (rate record template) is attached to a CRT Configuration, you cannot edit either the rate offering or rate record. The rate information is pulled from the rate record template upon creation of the CRT configuration and this information will not be updated if the rate record is changed. To avoid the loss of data, the rate record offering and rate record are both locked when the CRT configuration is created.

Rate records based on rate offerings marked as sourcing templates or read only will not be used by Oracle Transportation Management for shipment building or execution.

Using the Rate Record Finder

When using the Item Classification field for filtering, only one classification field criteria should be specified, because each rate record is linked to one particular type of flex commodity qualifier. For example, if you specified HTS ID criteria as HT-001 - BEGINS WITH and NMFC Class ID criteria as 100 BEGINS, the finder will not find any results. You should either specify Commodity ID, NMFC Article ID, SITC ID, STCC ID, HTS ID, NMFC or User Defined Commodity ID.

In Oracle Transportation Management, there is a general concept of profile that can be defined on different business objects like service provider, equipment group etc. This concept of profile helps you to identify and define groups of business entities/objects that have something in common. As part of this profile definition, it is possible to include or exclude common business entities. The concept of include or exclude (managed via compatibility attribute) is not honored/checked for the Equipment Group ID profile and Flex Commodity profile based filtering attributes.

Rate Record Header

The Header section contains general information about the rate record.

Note: Rate records marked as read only rates will ONLY be used for Rate Maintenance. They will not be used by Oracle Transportation Management for shipment building or execution.

1. Rate Record ID: Enter an identifier to uniquely identify this Rate Record or leave it blank to have Oracle Transportation Management automatically generate an ID when you save the record.
2. Enter a Domain Profile ID in the field if you want to specify a domain profile as a constraint on the rate record.
3. If your rate record is only valid for a particular period of time, specify the rate record's Effective Date and Expiration Date. If a shipment falls outside the date range, the rate record is invalid, and a different rate record may apply. For more information, see the glog.business.rate.rateEngine.validateBaseRateGeoActiveEffExpDate property.
4. Rate Service ID determines how to calculate the time in transit based on the Rate Service Type, taking into account other factors that may come into play (such as rest periods).
5. Expiration Mark ID identifies if the rate record is flagged for expiration.
6. Payment Method Code ID identifies the conditions for payment. This code can be used to populate the payment method code on shipment cost records that are created using this rate record.
7. Select one of the options from the Hazardous Rate Type list to specify whether the rate offering can be used for shipments with or without hazardous materials. The options are:
   • Allows Hazardous Materials
   • Hazardous Materials Only
   • Non-Hazardous Materials Only
8. Select the Quote check box if this is to be used for quoting.
9. Select the Active check box to activate the rate record. For more information, see the glog.business.rate.rateEngine.validateBaseRateGeoActiveEffExpDate property.
10. When viewing rate records created by the Rate Maintenance upload rates action, you see the Read Only check box selected. You cannot edit any rate records which have this option selected.
11. If you select a Corporation Profile ID, it is used as a constraint during the planning process. A Corporation Profile ID is used to group corporations together that have something in common. At the rate record level, it covers a set of corporations. Values at the rate record level override values at the rate offering level. For more information, see the glog.order.rule.pass_corp_profile property page.
12. Enter a Description for the rate record.
13. For Rate Maintenance, enter a Parent Rate Record ID to track versions of your rates during the approval process.

Reference Numbers

1. Enter a Reference Number.
2. Select a Reference Number Qualifier from the drop-down list.
3. Click Save.

Rate Lane Geo Hierarchy

The Source Geo Hierarchy defines the general starting location for this rate record, and the Destination Geo Hierarchy defines the general end point for this rate record. Depending on the information you enter in this section, the lane definitions (on the next page) change (see table below). For example, if you indicate that this rate record is valid from USZIP3 to USZIP3, the next page asks for the actual 3-digit zip codes. However, if you indicate that the rate record is valid if it starts and ends in a particular city, the next page asks for the actual cities.

The relationships are:

If the Geo Hierarchy is...	The Lane Definitions (next page) are...
City	City, Province Code, Country Code
City/Country	City, Country Code
Country	Country Code
Location	User-defined Location
Postal Code	Postal Code
Rail SPLC	Rail SPLC
Rail Station	Rail Station
State/Province	Province Code
USZip3	Postal Code
USZip5	Postal Code
Zones 1 - 4	Zone

In addition to using a Geo Hierarchy, you can define the lane using regions. Search for a user-defined region in the Source and/or Destination Region fields, and attach it to this rate record.

Note: If you selected Parcel as your rate offering Transport Mode or Zone-Based as your rate offering type, select a Rate Zone instead of a Geo Hierarchy.

The above hierarchies are used to determine the rate records based on the source and destination addresses of the shipment.

The searching of the rate records can be of three types:

• By location - When the source and destination locations are the same, then the rate records are searched using the location ID.
• By lane - The rate records are searched based on the matching geo hierarchies of source and destination addresses with that of the lanes defined for the rate record.
• By zone - The rate records are searched based on the matching geo hierarchies of source and destination addresses with that of the lanes defined for the zone profile specified on the rate record.

For source and destination location pairs, you can determine the possible geo hierarchies and search the rate records based on them.

For example, If the source location is PPA (PAMPA) and the destination location is
USOAK (OAKLAND), the hierarchical names are derived as follows:

• For PPA, hierarchical names are derived as 'COUNTRY\USA\', 'STATE/PROVINCE\TX\', 'CITY\PAMPA\TX\USA\', 'CITY/COUNTRY\PAMPA\USA\', 'LOCATION\PPA\'
• For USOAK, hierarchical names are derived as  'COUNTRY\USA\', 'STATE/PROVINCE\CA\', 'USZIP3\946\', 'CITY\OAKLAND\CA\USA\', 'CITY/COUNTRY\OAKLAND\USA\', 'USZIP5\94604\', 'POSTAL_CODE\94604-2064\', 'LOCATION\USOAK\'

The above geo hierarchies are matched with the geo hierarchies of the lane or the lanes of the zone profile defined for the rate record.

The rate record with the most specific geo hierarchy is selected based on the ranking of the geo hierarchy. The ranks for each Geographic hierarchy are specified in the Geography Hierarchy Manager. For example, the following are the ranks defined for few geo hierarchies:

• LOCATION - 1
• CITY/COUNTRY - 3
• STATE/PROVINCE - 5
• COUNTRY - 10

The rank for the rate record is determined using the geo hierarchies of the source and destination addresses using the below formula:

when the destination address rank is less than or equal to the source address rank, then the rank of the rate record is calculated as (source address rank + destination address rank)*2 otherwise it is calculated as (source address rank + destination address rank)*2 + 1.

Often, there can be multiple rate records with the same rank and these rate records are further filtered out using the planning parameter "ALLOW DUPLICATE RATES BY CARRIER".

VIA Locations

VIA Locations are used when rating and routing international shipments. Rates are valid when the data specified here matches the VIA Locations set up on an itinerary.

VIA Locations refer to ports that the shipment must pass through. For example, if an itinerary is set up as Pittsburgh for the source and London as the destination, then New York could be set up as the VIA Source Location because the shipment would go from Pittsburgh to London via New York. In this case, a matching rate record must be set up with New York as the VIA Source Location.

Note: When using a source or destination via point (port of load or port of discharge) on the shipment, you cannot use a rate record that has a source or destination via point that does not match.

Multiple VIA Source and VIA Destination Locations can be set up on the same rate record. In this case, you would set up a profile that would list the possible VIA locations. The VIA Source Location ID field should not be used when a VIA Source Location Profile is used. The same is true for the VIA Destination Location ID field. The planning logic will not read the profile field when location field is populated, narrowing the valid VIA locations to the one in the VIA Location ID field.

• VIA Source Location ID: Used when only a single VIA Source Location is valid.
• VIA Source Location Profile ID: Used when a list of valid source VIA locations are valid.
• VIA Dest Location ID: Used when only a single VIA Destination Location is valid.
• VIA Dest Location Profile ID: Used when a list of valid destination VIA locations are valid.

VIA Points as Shipment Stops

If you set the parameter ADD RATE VIA POINTS AS STOPS to true, the application adds the Port of Load and the Port of Discharge from the rate record as stops to a shipment, provided adding these VIA points do not make the shipment time infeasible.

VIA points can be added as shipment stops only if the following conditions are satisfied:

1. It is not a multi-leg scenario.
2. The rate service must be of type "LOOKUP".
3. If there are multiple port of load/port of discharge defined on the rate record, the first alphabetic ones are picked to be added as stops.
4. If the order has a port of load/port of discharge already constrained, then that must be considered.

Note: Not only source-destination, but also other necessary entries (like source-port of load, port of load-port of discharge, and port of discharge-destination) are required for the shipment to consider this rate.

Rounding and Deficit Calculations

Use the rounding and deficit calculation fields to define the behavior of all numeric fields during the rating process.