Contract and Rate Management

The External Rating Engine

Note: Support for on-premise SMC3 RateWare applications have been deprecated as of 6.4.2 release and will be removed from a future release.

To use RatewareXL, select LTL-SMC as your Offering Type. Keep the following requirements in mind when creating orders or shipments using these rates:

  • Orders using these rates must either have items that belong to a PUBLIC NMFC Class (e.g. 50.0, 70.0, etc.), or they must have ship units that specify an NMFC Class.
  • Source and destination locations for orders using these rates must have United States postal codes.
  • Shipments using these rates must have a weight greater than zero.
  • If you enter a DIM Rate Factor, Oracle Transportation Management provides the external rating engine with the greater value of true weight or DIM weight.

Before you can use an external rating engine, you must set the RatingEngine properties:

  1. Set the following properties in a property set:
    • glog.RatingEngine.Rateware.URL=<ratingengine_name>
    • glog.RatingEngine.Rateware.Port=<ratingengine_port>
  1. Replace <ratingengine_name> with the name of the server on which the rating engine runs.
  2. Replace <ratingengine_port> with the port number on which the rating engine listens (This is often 23700.).

Note: A new RatewareWithCarrierConnect external rating engine is added to calculate rates and transit days of a shipment. This replaces the old way of specifying a property that enables OTM know that CarrierConnect is installed over the Rateware. Hence, you can use both Rateware that provides rating for an LTL shipment and Rateware With CarrierConnect that provides both rating of the LTL shipment and the transit days with the help of CarrierConnect.

Note: When using SMC3 rates, distance is not required to calculate cost.

Tiered (Freight All Kinds) FAK Rating

If you rate ranges of National Motor Freight Classification (NMFC) classes as one NMFC class, you can either specify the ranges and their substitute values on your rate offering or your rate record. For example, classes 100-150 rate as class 100.

Note: The data is cached, so if you change any entries for a particular rate offering while the server is running, you will have to restart the Oracle Transportation Management server.

Related Topics