You are on page 1of 36

Items are things that you manufacture and sell such as chemicals,

finished goods, raw materials, and parts. You can create an inventory of
items that you typically ship from one destination to another. Once items
are defined, they can be used on orders based on bulk data or any order
base or order release. An item is the lowest level of detail that you can
describe on an order. It identifies the specific goods or materials that you
are shipping.
You can create an item by adding each item individually, or you can
import your entire item master from an external system via integration.
Once the item is imported, you can make modifications to the data or add
new items as necessary. You can also create a packaged item and specify
details on how the item is packaged and handled so it can be stored and
transported properly.
Adding an Item:
1. Enter an Item ID. The item ID uniquely identifies the item. You
also use this item ID to assign an item to an order.
2. Enter an Item Name as additional information for the item.
3. Select a Domain from the drop-down list.
4. Enter a Description for the item.
5. Enter an Effective Date and an Expiration Date. The effective
and expiration dates are used to create a time window for when an
item can be used on orders.
6. You can supplant an item with another item by identifying that item
in the Superceded by Item ID field. This is for information only
and it does not affect an order's status that is on hold due to an
expired item.
Note: The following fields can be used to classify the item as a
commodity or any of the listed industry classifications. Below are
your options and links to their detailed descriptions.
7. Enter a Commodity ID.

8. Enter an NMFC Article ID.


9. Enter an STCC ID.
10.

Enter an IATA SCR Code.

11.

Enter an SITC ID.

12.

Enter an NMFC Class ID.

13.
Enter a User Defined Commodity ID.
OR
Enter a User Defined Commodity List ID.
Note: Do not populate both the User Define Commodity ID field
and the User Defined Commodity List ID field. Only one of the
two should be used, otherwise rates may be deemed invalid if you
have any conflicts between the two fields.
14.

Enter an HTS ID.

Note: If you are working in Global Trade Management, you will not
see this field.
15.
For informational purposes enter the Brand Name of the
item.
16.
Enter the location where the line item was produced in
the Manufactured Country Code field.
17.
Select the Drawback check box if this item was imported into
a country and then re-exported. You mark items for drawback to
reclaim duties paid on the item when it was imported. This check
box is for information only.

Packaged Items
Use this information to define how packages are shipped. If you skip this
section, then a default packaging record is created where the hazmat
packaged item ID is the same as the item ID.
ORDER MANAGEMENT

Packaged Item

This page is accessed via Order Management > Material Management


> Packaged Item.
Packaged Item is where you define the classification hierarchy between
the items, packaged items, and packaging units. This information is used
to properly package and ship items.
Note: Due to the flexibility presented to you in defining your packaged
items, it is important to carefully read this entire topic before creating
them.

Getting Started
There is some flexibility in how you can define the relationship between
items, packaged items, and packaging units. Before defining these
relationships, you need to consider how you connect items and packaged
items.
After creating a new item, you can consider the item and the packaged
item the same thing. This means you consider the item and the way it is
packaged as the same thing. At some point, as described below, you will
need to specify how these items/packaged items are shipped.
You can also consider the item and the packaged item as different things.
This requires you to set up a packaged item for each way the item is
packaged, and then define how each of these packaged items are
shipped.
Regardless of which approach you take, you end up with the same result it is just a matter of perspective. Do you look at items and packaged
items as the same thing or do you consider an item and all the ways it
can be packaged as separate entities?
The different ways you can define these relationships are described below
in the Examples section.

Header
1. Enter a Packaged Item ID. This uniquely identifies the packaged
item and tracks it throughout the order and shipment process. It
specifies how an item is packaged and loaded into ship units. The ID
can be alphanumeric.
2. Enter a description for the packaged item in the Description field.
3. If the packaged item contains a hazardous material, select
the Hazardous option. The hazardous state of an item can be
determined by the item itself, its packaging, its mode of transport,
or the country of destination. See Hazardous Material Settings and
Implications.
4. Enter an Item ID. This uniquely identifies the item and tracks it
throughout order and shipment process.

5. Enter a Hazmat Package Type ID. This can be used to give the
packaged item a special description. If you are defining a hazardous
material, use this field to describe it.
6. Select a packaging unit from the Packaging Unit drop-down list.
This list contains all the values you have defined under Ship Unit
Specifications in Power Data. The value that you select from the
drop-down list identifies the physical characteristics of this
packaged item.
Note: Selecting a packaging unit is not required, however, you
must define it in both Inner Packing Info and in the Ti-Hi sections.
7. Select the Mixable option if the packaged item can be packed into
a ship unit with other mixable packaged items.
8. Enter a package weight and select a unit of measure from the dropdown list beside it.
9. Enter a unit volume and select a unit of measure from the dropdown list beside it.
Note: Use either the Unit Volume field or the Unit Length, Unit
Width, and Unit Height fields. If the volume field is populated,
Oracle Transportation Management will use that value as the
packaged item volume. If not, then Oracle Transportation
Management will use the length, width, and height values and
calculate the packaged item volume. If all four fields are populated,
it will use the volume field only.
10.
If this is the default packaging for this item, select
the Default Packaging option.
11.
If the item has a cylindrical shape, record the diameter in
the Diameter per Ship Unit field.
12.
If the item has a cylindrical shape, enter the diameter of the
inner packaging of the packaged item in the Core Diameter field.
13.

If applicable, enter a Packaged Item Type ID.

14.

Enter the item's Transport Handling Profile ID.

15.

Type a value in the Load Config Rule Rank field.

16.
Select an inner pack packaging unit from the Inner Pack
Packaging Unit drop-down list. For example, if your packaged item
is a case of soda, the inner pack packaging unit is Can. This dropdown list contains all the values you have defined under Ship Unit
Specifications in Power Data. This field is optional and is for
information only.

17.
Enter a value in the Inner Pack Size field. In the soda
example, the inner pack size could be 12 (a 12 ounce can). This
field is optional, and is for information only.
18.
Enter a UOM Code in the Inner Pack Size UOM field. In the
soda example, the inner pack size UOM code would be ounces. This
field is optional, and is for information only.

Reference Numbers
Use these fields to assign reference numbers to the packaged item.
1. Enter a Reference Number Qualifier ID.
2. Enter a value in the Reference Number field.
3. Click Save.
Note: You can add multiple reference numbers. Remember to
click Save after entering each one.

Equipment Reference Units


You can select Equipment Reference Units (ERU) to limit the number of
specific units being loaded on a specific equipment group. If any ERU level
information is provided on the ship unit, it overrides any defined on the
ship unit specification.
Note: Values entered in this section are used to populate the ERU section
on the Shipment Ship Unit Manager.
1. Enter an Equipment Reference Unit ID.
2. Enter the number of reference units in the Number of Reference
Units field.
3. Click Save for each equipment reference unit you enter.
Note: You can add multiple lines of equipment reference unit
information. Remember to click Save after entering each one.

Inner Packing Info


Use this section to define multiple packaging units for an item. For
example you could package soda in a 12 pack box as well as a 24 pack
box.
1. Select a packaging unit from the Packaging Unit drop-down list.
2. Enter a quantity in the Inner Pack Count field.
3. Click Save.
Note: You can add multiple instances of inner pack information.
Remember to click Save after entering each one.

Ti/High

Ti/-High is a term used in the Logistics industry. It refers to the number of


boxes/cartons stored on a layer (the Ti or tier) and the number of layers
high that these will be stacked on the pallet (the High or height). The
information that appears here is read-only. To record new Ti/High
information, click New Ti/High.

Hazmat Items
Use this section to add any Hazmat information that applies to the
packaged item.
1. Enter a Hazmat Item ID
2. Enter the Hazmat Generic ID.

Examples
These examples demonstrate two ways you can use the Packaged Item
page.
Example 1
For this example you will be defining the packaged item with a fixed
package unit.
1. Enter a Packaged Item ID such as 12PACK_COKE.
2. Choose an Item ID, that is, the item for which you are defining a
package unit. In this example, choose COKE.
3. In the Packaging Unit drop-down list, select a packaging unit. For
this example, choose 12PACK. After you have made your choice,
notice that the Inner Packing Info section disappears as well as
the Packaging Unit column in the Ti-Hi section.
4. Enter the package weight, unit volume, unit
length/width/height/diameter/diameter core and any other needed
data in the header section.
5. In the Ti-Hi section, click New Ti-Hi, select a Transport Handling
Unit, and enter values in the Number of Layers and Quantity per
Layer fields. For this example, enter PALLET as the transport
handling unit, 4 as the number of layers, and 6 as the quantity per
layer.
6. The Inner Pack Count field gives you a place to enter how many
of the item is packaged in this packaging unit. This information is
for informational purposes only and will only be visible if you select
Packaging Unit in the header section.
7. Enter any other relevant information in the other page sections.
Example 2
These steps are used to define a packaged item with a choice of
packaging units, and how it will be packed on Transport handling unit. In

this example you are shipping a box of pencils which contains a number of
10 piece packs of pencils. This box can be packaged in a small carton
(with 100 boxes of pencils per carton) or a mid-sized carton (with 160
boxes of pencils). A 4X4 pallet can hold 4 layers with 6 small cartons per
layer, or 2 layers with 4 mid-sized cartons per layer.
1. Enter a Packaged Item ID such as BOX_OF_PENCIL.
2. Choose an Item ID, that is, the item for which you are defining a
package unit. In this example, choose PACK_OF_PENCIL.
3. Allow the Packaging Unit field to remain empty. This means you
are defining a packaged item which can be packed in several
packaging units. You will need to define packaging unit in the
following sections.
4. Enter the package weight, unit volume, unit
length/width/height/diameter/diameter core and any other needed
data in the header section.
Note: The weight/volume, etc. you enter for this example is for one
box of pencils.
5. In Inner Packing Info section, select a packaging unit (use small
carton in this example), give an inner pack count (for this example,
use 100), and save it.
6. In the Ti-Hi section, click New Ti-Hi, select a Packaging Unit (in
this case SMALL CARTON), a Transport Handling Unit (in this
example, 4X4 PALLET), and enter values in the Number of
Layers (use 4 for this example) and Quantity per Layer (use 6)
fields. Remember that you can use this page to define different
combinations of packaging units and transport handling units.
7. Enter any other relevant information in the other page sections.

Consumption in Packaging Reference Units


1. Enter a Packaging Unit.
2. Enter a Packaging Reference Unit ID.
3. Enter a value in the Packaging Reference Unit Count field. This
value may have up to 6 decimal places.
4. Click Save.
5. Repeat the process to add additional packaging units.
6. Click Finished.

Location Manager: Identification

Finder | Identification | Reference Numbers | Address | Related


Topics
This page is accessed via:

Shipment Management > Location Manager

Operational Planning > Appointment Management > Dock


and Yard Managers

Use the Location Manager to record and store information about locations
that have not been predefined.
Locations are required when you:

Plan for a shipment

Establish rates for a shipment

Define itineraries

Create orders

Create a location template

Each location must be associated with a corporation and defined


geographically. Store information about the type of transportation role the
location fills, any accessorial or special services required, ways of
communicating with that location, performing a credit check on an order
against the location, and how transportation to and from that location can
be routed.
Locations represent physical places to which an order can be delivered or
from which an order can be picked up. They include airports, ports, rail
ramps/yards, container pool locations, distributors, assembly points,
plants, vendors, and more. A customer or a buyer can also be a location.
Note: Alternatively, you can enter locations automatically via integration.
Adding a location:
Identification defines basic location information such as ID, name
and address. Also associate the location with a corporation.

Roles define the purpose of the location, as well as any associated


accessorial charges or special services.

Routing specifies equipment groups or service providers associated


with the location.

Communication and Remarks lists all contacts assigned this


location and lets you enter any additional comments or remarks
about the location for informational purposes.

Load/Unload Points are specific loading and unloading points


assigned to a location. It provides a detailed view of the location
giving the precise point to load and unload cargo.

Resource specifies the resources available for the location.

In order to provide accurate calculations, enter as much information as


possible about a location.

Using the Location Finder


In OTM, 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 serving service provider ID and equipment
group ID filtering attributes.

Identification
Create a location so that rates, itineraries, and orders are accurate. In
addition, the information you enter can be used to send notifications
about shipments, establish rate qualifications for a shipment, determine
routing capabilities, and more.
1. Location ID uniquely identifies this location. For instance, if XYZ
Corporation has three Pennsylvania locations, you may assign
Location IDs of PA-01, PA-02 and PA-03 to them, or even PAPhiladelphia, PA-Pittsburgh, and PA-Allentown.
Alternatively, Oracle Transportation Management can automatically
generate a Location ID for you. Leave the Location ID field blank,
and the Business Number Generator creates an ID when you click
the Finish button.
Note: You may want to include the name of the location in the
Location ID so that it can be easily identified in other areas.
Note: Oracle Transportation Management assumes that a location
with the same GID as a corporation is the master location for that
corporation.
2. Location Name describes this Location.

3. The Corporation ID uniquely identifies this Corporation.


Note: A single Corporation ID may be linked to multiple locations.
4. The Location Description is the description you enter for a specific
location.
5. Domain: Choose in which Domain you want to create the location
from the drop-down list.
6. The Use As A Template checkbox should be checked if you plan to
use the location as a location template.
7. The Known Shipper check box indicates if a shipper is known or
unknown. Shippers are considered unknown if they have not filed
the appropriate paperwork and gained permission to ship goods on
passenger flights. Goods transported by these shippers must be
placed on cargo flights. Select Known Shipper if orders coming
from this location can be qualified as known, and therefore
transported on passenger flights.
8. Temporary: You can set up a temporary location to use for a short
time. Select the check box to have all subsequent result pages
display the location as temporary. This field is currently used for
informational purposes only.
9. Status: The External Status Type and Status Value for this location
are populated based on information assigned in Power Data. For
locations, use external (status types and values to assign
credit status and enable data transmission via integration). This
only displays in Edit mode.
10.
Select the Exclude from Route Execution check box if you
do not want this shipment included when on route instance legs.
11.
Region ID: If you are creating a consolidation pool or
deconsolidation pool location, select or create the Pool Region this
location covers. A region is a user-defined geographic area. The
region may be any size area you want that has meaning for your
business.
Orders with destination locations in the region associated with a
pool are candidates for the pool. They are sent to the pool and deconsolidated for delivery to the destination.
12.
LTL Split: This check box indicates whether orders from or to
this location are permitted to apply the LTL splitting logic. If the
check box is not selected, the LTL splitting is disallowed for orders
associated with this location.
13.
Clear the Active check box to make this location inactive.
This impacts planning order releases and order movements. When
building shipments, the status of both the source and destinations

locations are checked. Shipments will only be created when both


locations of the order movement are active. If a source or
destination location becomes inactive after the shipment is created,
you will not be able to tender the shipment with an inactive stop
location. The tendering actions that have location validation are
Secure Resources, Secure Resources by Planner, Tender Shipment,
Broadcast Tender and Spot Bid Tender.

Reference Numbers
Use this section of the page to assign reference numbers to the location.

Address
The Address section is where you define the specific address information
of the location. This information is used when calculating itineraries,
defining lanes, qualifying rates and shipping goods.
1. The Address Lines field contains the street level information for
the location's address.
2. The Address Line Number field designates which line of the
address text box contains the actual street address so when using
the External Distance Engine, the correct street address is used.
For example, if you had this address in the text box, the line
number would be 2.
Care of Someone
1234 Main St.
If you have this in the text box, the line number would need to be
1.
1234 Main St.
Suite 350
3. The Address Fixed checkbox is used when the address has been
validated and known to be accurate. When selected, the address
portion of the location will not be overwritten.
4. The City field contains the name of the of city that the location is in.
5. The Province Code field contains its abbreviated name of a state
or province.
6. The Postal Code field contains the postal code of the location. In
the United Sates, this would be the 5 or 5+ zip code of the location.
Oracle Transportation Management will only read the number of
digits defined in the Postal Code Length field in the Country Codes
screen in Power Data.
Note: If using SMC (RateWare), note that Mexican zip/postal codes
can be the same as US postal codes so you have to pass an "M" in

front of the Mexican postal code so RateWare knows to use the


Mexican rates.
7. County Qualifier is used when calling an external distance engine
and using an address type of city instead of postal code. Often,
there are two cities or towns with the same name in one state. For
example, in Pennsylvania there is more than one town with the
name "Newtown". If you do not combine the town with a postal
code or a county, you may not get the result you want.
You can manually add values; however, you probably want to import
them from the external distance engine that you are using. The
county qualifier needs to correspond with the distance engine that
you are using.
8. Zone: You can also define zones that are specific to a location and
used to help qualify rates. For instance, a service provider may offer
one rate for transport from the location to any of the southwestern
states, and another rate for transport to the northeastern states.
For the location, you could define Zone 1 to include all southwestern
states. Alternatively, you could define Zone 1 to include specific
SPLC (Standard Location Code) codes that may be used for rail
transportation.
9. Note: To use the zone information, the same zone must be
assigned in a rate record. If a match is found between a source or
destination location and a rate lane (and other factors also match),
the rate would qualify for a shipment.
10.
The Country Code is the standard three-letter abbreviation, as
defined by ISO 3166 standards, to identify countries. The Country
Code is required to ensure that rate offerings and web tendering
functions work correctly.
11.
The Address Valid field will contain an "N," "Y," or "U," and
will only appear after the location has been created. If the value is
"N," it means the Country Code, City, and Postal Code combination
you entered is invalid. Oracle Transportation Management allowed it
to be entered anyway because your Postal Code Validate Type is set
to Warning. If the value is "Y," it means the Country Code, City, and
Postal Code combination is valid. If the value is "U," it means that
no validation took place because the validation process was not
activated.
Note: The Location Manager includes functionality to validate the
location data entered based on user-defined Country Code, City,
and Postal Code combinations. These combinations are defined in
the Postal Code Validate screen in Power Data. They are validated
only if the Validate Postal Code check-box is checked in the Country

Codes screen in Power Data, and the domain for each location has a
Postal Code Validate Type set for it in the Domain Manager.
12.
Time Zone: If you leave the Time Zone blank, Oracle
Transportation Management determines what time zone a location is
in and auto-populates it based on the address (country,
state/province, city, postal code). Oracle Transportation
Management has a database of worldwide time zones and the
geography they cover. This includes differences in how some locales
handle daylight savings time (Arizona does not honor it).
You can also select a time zone to ensure that all time restrictions
are met. From the Time Zone drop-down menu, first find the region
associated with the location you are trying to establish. For
example, you know that Atlanta, Georgia is part of America. In this
example, America would be your region and Atlanta would be your
city. Alternatively, you may select a general time zone instead of a
specific city, or leave the Time Zone field blank and allow Oracle
Transportation Management to select the time zone automatically
when you save the record.
Note: The difference between a general time zone such as EST and
a specific city such as New York is that the New York time zone
takes into account daylight savings time. To ensure accuracy, a
location's time zone should be set to a nearby city.
13.
The Province field contains the name of the state/province
that the location is in. For example, in the United States, you can
enter the full state name in the Province field (PENNSYLVANIA) and
its abbreviated state name in the Province Code field (PA).
14.

Enter a postal SPLC.

15.

Enter a rail SPLC.

16.

Enter a rail station code.

17.

Enter a rail junction code.

18.

Enter an ERPC.

19.
Assign Latitude and Longitude (in degrees) for the location.
Once assigned, these values are used to estimate distance from or
to the location. If these values are not entered, Oracle
Transportation Management uses latitude and longitude positions
assigned to the specific US postal code, city, state, province or
country entered when calculating distances to and from the
location. If these do not populate automatically, you can run
a planning process to populate them.
Note: For non-US locations, you need to enter latitude and
longitude to calculate distance.

Rate Offering
This page is accessed via Contract and Rate Management > Contract Management >
Rate Offering.
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.
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.

A rate offering is a general contract with a service provider. It may include multiple
charges that provide for a variety of possible requirements. A single service provider
may have several different rate offerings.
Once the rate offering is created, you can modify the data in any section without
having to go through the entire step sequence.
Note: Settings in rate records override settings in a rate offering.
Rate Header
1. Enter an offering ID.

Note: Use Offering IDs starting with ' PLANNING_' when creating simulated
Planning Rates for multi-stop shipments. Oracle Transportation Management only
uses such rate offerings for finding the best route for a multi-stop shipment.
2. Select an offering type from the drop-down list. The offering type need not
reflect the transport mode of the shipment.
3. Enter a service provider for which this rate offering applies.

Note: Unless you are defining a rate offering with an offering type of LTL-Base or
LTL-SMC, specify a service provider.
4. Enter a region group.
5. Enter a domain profile if you want to specify a domain profile as a
constraint on the rate offering.

If none of the rate offerings have a customer domain profile


constraint, then all rate offerings are returned.

If some of the rate offerings have customer domain profiles, the


rate offerings are grouped by service provider. For each service
provider, only the offerings whose domain profile constraint is
satisfied are returned. So, given two rate offerings, one with a
constraint, and one without a constraint: if the order release
domain list is compatible with the constraint, only the rate offering
with the constraint is returned, otherwise, only the offering without
the constraint is returned.

6. Enter a rate service to identify how transit times are calculated.


7. Enter a rate group to let you group together your rate offering and
associated rates with other rate offerings and their associated rates.
8. Select a transport mode to define how goods will be transported.
9. Specify whether the Perspective is:

Buy - Set up rates for a shipment.

Sell - Set up rates for billing purposes. Typically, the sell perspective
is used by Third-party Logistics (3PL) firms who are offering a
package of several possible transportation legs at a single price to
the customer.

All - Choose this option if you are setting up rates for both shipping
and billing.

10.Select the Currency used for this rate offering to effectively compare rates.
In order for shipments to show the shipments in the same currency as the
currency used in the rates, you need to copy the existing SHIPMENT
Manager layout and select the Display UOM as Entered check box on the

first tab. Then you need to assign this Manager layout to the screen set
you are using so that the changes will take effect. For pages that can be
customized, such as Shipment, you need to copy the Manager Layout and
select the Display UOM as Entered check box on the first tab.
11.Enter a version. A rate offering defines a rate or a cost for a particular
period of time. Because a single service provider may have several similar
offerings over a long period of time, you must specify a version that
provides the offering's effective date and expiration date. When you enter
a Version identifier, Oracle Transportation Management populates the
Effective and Expiration Date fields - you cannot edit these fields. If a
shipment falls outside the date range, the offer is not valid and a different
rate offering may apply. You may also need to mark the Active check box.
12.Enter an equipment group profile determines the kind of equipment that
can be used with rates attached to this offering.

Note: If the shipment requires a particular piece of equipment and the Equipment
Group Profile does not include that equipment, the offering won't qualify for the
shipment. If the Profile field is blank and the shipment requires a certain piece of
equipment, the rate offering can qualify for the shipment.
13.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.
14.To effectively compare rates, you must select an exchange rates.
15.Enter up to four descriptions for the rate.
16.The Expiration Mark ID identifies if the rate offering is flagged for a version
change or expiration.
17.To create an Oracle Transportation Sourcing rate record template, select
the Sourcing Template check box on the rate offering.

Then, you can create a rate record based on this Oracle


Transportation Sourcing rate offering.

You specify this Oracle Transportation Sourcing-specific rate record


as the rate record template on the CRT configuration.

Note: When creating an Oracle Transportation Sourcing rate offering template, you
should only associate a single rate record with a rate offering. A rate offering is an
Oracle Transportation Sourcing rate template if you select the Sourcing Template
check box on the rate offering.
Note: Once a rate record template is attached to a CRT Configuration, you cannot edit
either the rate offering or rate record.
2. When viewing rate offerings created by the Oracle Transportation Sourcing
upload bid response action, you see the read-only Sourcing Rate check

box selected. You cannot edit any rate offerings which have this option
selected. Sourcing rates are temporary rates used by Oracle
Transportation Sourcing to cost bids.

Note: Rate offerings marked as sourcing templates or sourcing rates will ONLY be
used for Oracle Transportation Sourcing. They will not be used by Oracle
Transportation Management for shipment building or execution. This includes any
rate records associated with these rate offerings.
3. 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.
4. The Active check box more efficiently evaluates if a rate offering is active
than the effective and expiration dates. Ineffective rates are cached in
memory and are still evaluated by the Planning logic (dates are compared)
in order to determine if the rate is valid for a given shipment. This affects
both memory and performance. The Active flag was added to allow an
ineffective rate to be flagged as "Inactive". In this case the rate will not be
loaded into memory.
5. For some time-based rates, the shipment cost calculated during bulk plan
and build shipment process may not be accurate. You can use the
Recalculate Cost check box to force recalculating cost after a shipment is
built. This check box works in conjunction with the Rerate All Shipments
After Bulk Plan parameter as follows. If the Recalculate Cost is set,
planning logic will make sure to account for service time-based rating
costs when making planning decisions, and that this has the potential for
increasing run-time.

If Rerate All Shipments After Bulk Plan is TRUE, shipments will be rerated regardless of the Recalculate Cost check box.

If Rerate All Shipments After Bulk Plan is FALSE and the Recalculate
Cost check box is selected, then the system recalculates the
shipment cost keeping the same service provider and equipment.

If Rerate All Shipments After Bulk Plan is FALSE and the Recalculate
Cost option check box is cleared, then the shipment cost is not
recalculated.

Choose a capacity group to associate this rate offering with other


rates that have the same equipment constraints. If you leave this
field blank, the capacity for this rate offering is unlimited. The
capacity groups in this list are limited to the ones that share the
service provider entered above.

Use the Track Capacity Usage check box if you plan to run the
Capacity Commitment report and you do not want the planning
process constrained by capacity limit/capacity usage. This check
box only has effect when Capacity Group field is populated.

If the Track Capacity check box is selected and the Capacity Group
field has a value in it, Oracle Transportation Management tracks
capacity usage during the planning process.

If the Track Capacity check box is cleared, or the Capacity Group


field is blank, Oracle Transportation Management does not track
capacity usage during the planning process.

The Contract Rate check box indicates that a rate is a client-specific


rate and by configuring an Action check in User Access Manager,
you can prevent users from booking (running the Secure Resources
action) a sell shipment that uses a rate that has this check box
selected. The Action Check must have a saved query to prevent the
user from running secure resources on a sell shipment which does
not have a client-specific rate.
After this is configured, when a user initiates the booking process by
selecting a sell shipment that does not have a client specific rate,
and running the Secure Resources or Secure Resources Manually
actions, a message appears informing the user that booking must
be initiated from the buy shipment.

If the rate offering applies to direct shipments only, then select this
check box. This ensures the rate offering is only used for shipments
with order releases that have no consolidation type specified.

Select the Route Execution Rate check box if the rate is used for the
cooperative routing route execution.

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 Max Num of Shipment Segments field determines the maximum


number of segments on a shipment. A segment is defined as
starting when product is loaded on the equipment and ending when
the equipment is completely emptied.

The Effective and Expiration Date fields are automatically populated


with the dates defined in the Rate Version assigned to the Rate
Offering.

Enter a description for the rate offering.

If Depot Applicable is selected, then the depot stops (source and/or


destination locations) will be saved to the shipment If it is not
selected, the depot stops will not be saved to the shipment, but
they will be charged and saved to the shipment financials if it is
defined in the itinerary.

General guidelines for minimum and maximum Weight and Volume


are used when trying to match offerings with shipments. If a
shipment's requirements exceed the minimum and maximum

values, this rate offering does not qualify for the shipment in
question.
o

General guidelines for minimum and maximum Length, Width,


Height, and Dimensional Girth are used when trying to match
offerings with ship units. If a ship units' requirements exceed the
minimum and maximum values, this rate offering does not qualify
for the ship unit in question.

Note: Dimensional girth is calculated as length + (2xWidth + 2xHeight).


o

General guidelines for minimum and maximum Distance are used


when trying to match offerings with shipments. OTM gets the source
and destination address of the shipment and then calculates the
distance between both the addresses and then compares it with the
Minimum and Maximum Distance fields.

Ship unit weight maximum is used to match with ship units. If any
ship unit on the shipment exceeds the maximum ship unit weight,
this rate offering does not qualify for the shipment in question.

Ship unit line weight maximum is used to match with ship unit lines.
This field represents the maximum value allowed by this contract
for the weight of a single package.

Enter an average package weight maximum. Allows you to define


the maximum weight allowed for the calculated average package
weight of ship unit lines. The average package weight is determined
by dividing the total weight of the ship unit line by the total number
of packages.

Minimum Tender Lead Time and Maximum Tender Lead Time define
ranges for tender lead times. If the tender lead time of a shipment
does not fall within this range, the rate is invalid and will not be
assigned to the shipment. The tender lead time is the difference
between a shipment's start time and the time the shipment is
tendered to the service provider. The paperwork time for the
shipment is also factored. When building a shipment, the system
estimates start time based on the latest early pickup date of all the
orders being picked up and the first stop. Subsequent re-rates of a
shipment will use the shipment's actual start date to compare to
tender lead time.
Oracle Transportation Management adds the system time and
paperwork time as defined by the parameter Paperwork Time After
Batch End. It then checks the early pick up date on the order
release. If the tender lead time of a shipment is in the range, the
rate will be assigned.
Additionally, you may define two rate offerings; the one with the
shorter tender lead time being more expensive, to compensate for
rushing to meet the earlier time constraint. For example, Rate
Offering 1 has a minimum tender lead time of 6 hours and a

maximum of 12. Rate Offering 2 has a minimum tender lead time of


12 hours and the maximum is null (no maximum defined). If a
shipment's estimated tender lead time is less than 6 hours, neither
would be assigned; between 6 and 12 hours, Rate Offering 1 would
be assigned (the more expensive one); and after 12 hours, Rate
Offering 2 would be assigned (standard rates).
o

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

Select a flex commodity type:

Flex Commodity Independent: the rate is based on something other


than commodity. A commodity-independent rate can be based on a
flat fee, a discount or some other rating scheme.

Flex Commodity Based: the rate is based on a commodity and you


must choose a commodity profile for the rate. The profile is
comprised of one or more commodity classifications used to further
refine the commodity. If you choose Flex Commodity Based, any
rate record associated with this rate offering includes choices for
the commodity code based on the commodity profile you select.

Rate Service
Rate Service Header | Related Topics
This page is accessed via Contract and Rate Management > Contract Management >
Rate Service.
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. The rate service determines how to calculate the time in
transit based on the rate service type and taking into account other factors that may
come into play (such as rest periods).
Note: Alternatively, you can enter rates automatically via integration.
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 service determines the time required to transport goods from one point to
another. Rate service depends on the service type you choose.
Creating a rate service using the Rate Manager consists of two steps:

Rate Service Header defines basic information such as the Service ID, rate
service type, and other basic information for the rate service. The type of
service you select determines the attribute fields you see in Rate Service
Details.

Rate Service Details depend upon the Rate Service Type you choose.
Oracle Transportation Management presents options and fields to establish
the exact parameters of this rate service based on type.

After the rate service is created, you can modify the data in any section without
having to go through the entire step sequence.
Rate Service Header
The Header section contains general information about the service.
1. Rate Service ID uniquely identifies this rate service. After a rate service is
created, you can assign it to any rate offering.
2. Rate Service Name describes this rate service and is for informational and
searching purposes only.
3. Driving Penalty is the per hour cost for driving time. It is not for shipment
cost purposes. It is only used in the rate service scheduling routing to
reduce the overall driving cost in conjunction with waiting penalty.
4. Domain Name specifies the domain in which the rate service is used.

5. Rate Service Type: The type determines the attribute options presented on
the Rate Service Details tab. The Rate Service Type that you select
depends on the method of transportation you plan to use and how you
want to determine distance and service time.
6. Calendar: Enter a Calendar ID to associate specific activities, as well as the
days and times that they are available, to this rate service. For example,
you can define the days and hours that a facility accepts trucks for
unloading. This is used during shipment planning to determine if a rate
service is a viable candidate.

Note: In rate service, the calendar is only used with DAYDURATION,


DISTANCEDURATION, and time based accessorials.
In your calendar, use the PICKUP and DROPOFF activities. The PICKUP time is the
latest pickup time and the RECEIVE time is the guaranteed delivery time. For
example, an overnight service may have a pickup time of 5:00PM and a drop off time
of 10:30AM.
If the activity is PICKUP, then the system assigns the time from the END time on the
calendar PICKUP activity.
If the activity is DROPOFF, then they system assigns the time from the START time
on the calendar DROPOFF activity.
The start time of the shipment (Activity PICKUP) should be the end of the Calendar
activity window and the end time of the shipment (Activity DROPOFF) should be
start of the Calendar activity window.
If the arrival time at your first stop is earlier than the pickup window's start time, then
a wait time is automatically created that is equal to the time between the arrival time
and the pickup window's start time. The departure time at the stop is reset to the
pickup window's start time. This wait time can be removed by setting the parameter
MINIMIZE WAIT TIME IN RATE SERVICE CALCULATION.
7. Waiting Penalty is the per hour cost for waiting time. It is not for shipment
cost purposes. It is only used in the rate service scheduling routing to
reduce the overall driving cost in conjunction with driving penalty. This
does not apply to Air Schedule, Ground Schedule or Voyage Schedule.

8. Ignore Delivery Location Calendar: When selected, the drive routing ignores the
delivery location calendar. This only applies to Day Duration and Distance Duration.
9. Time Window Tolerance: Enter a numeric value for the number of hours
you want to add to the pickup and delivery times for shipments. The value
you enter adds to the allowable late times established for pickup and
delivery at shipment locations. For example, if you enter a 1, all pickup
and delivery times have an additional hour. If you are required to be at a
location between 2 and 3 p.m., and you arrive between 2 and 4 p.m., your
arrival is on time.

10.Max Wait Time Per Stop is the maximum time allowed to wait to pickup or
drop off goods. For example, if the Max Wait Time per Stop is set to 15
minutes, a drop-off location opens for business at 7 a.m. and a driver
arrives at a stop at 6:30 a.m., the driver is not allowed to wait that extra
15 minutes and must return. When the glog.appointment.WaitTimeOption
property is set to TRUE, this wait time is added to the estimated arrival
time when building a shipment.
11.Use Max Longhaul Wait Time to configure a wait time associated with the
first delivery stop after a long haul. There can be a large amount of time
between the last pickup and the first delivery stop so use this field to
accommodate a wait time for the long haul move. This field applies to the
first delivery location only.

If the Max Longhaul Wait Time is not set, then the Max Wait Time Per Stop is used
for the first delivery stop (as well as every other stop).
12.Use Rush Hour: When selected, rush hour is added to drive time, if
defined. This only applies to Lookup, Simulation and External.

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.
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.
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 sourcing rates
will ONLY be used for Oracle Transportation Sourcing. They 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.
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 not valid and a different rate record may
apply.
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:
o

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.
10.Enter a Description for the rate record.

Reference Number
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.
Note: If a rate offering has two or more rate records, you define what should happen
in your glog.properties file.
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.
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.
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.

Equipment Group
Equipment Group Details | Obstructions | Capacity in Reference Units | Equipment
Types | Axles | Related Topics
This page is accessed via Shipment Management > Equipment Management >
Equipment Group.
Equipment Groups identify the different kinds of equipment (such as dry vans,
flatbed trucks, container cars, hoppers, tankers, box cars, and so on) that are used to
transport shipments from one destination to another. An equipment group is defined
by an ID and description as well as other attributes that describe the capacity of the
equipment (for example, a 28 foot dry van that can handle up to 30,000 pounds).
Note: The Equipment Group finder page will not give you access to combination
equipment groups. They can only be accessed via the Combination Equipment
Group finder.
Note: If you are creating an equipment group with planes as equipment types, you
must create a vehicle type to associate with this equipment group.
Note: There must be a 1 to 1 relationship between equipment groups and equipment
types when defining them for rail transactions.

1. Enter the Equipment Group ID. This is the alpha-numeric string that
identifies the equipment group being created (for example, 28FT Dry Van).
The Equipment Group Name is the alpha-numeric name of the group. This
could be the same as the ID.
2. Select the domain where this group will be active from the Domain Name
drop-down list.
3. Enter the Effective Volume. This is the maximum volume that the
equipment group can accommodate. Click the icon to calculate volume by
entering length, width, and height.
4. Enter the Effective Weight. This is the maximum weight that the
equipment group can accommodate.
5. Mark the Container check box to identify that this equipment group is a
container. Equipment groups with this check box marked are considered
during the unitization process that can occur when running the Build Buy
Shipment on Primary Leg action for an order release.
6. Select the Allow LIFO Only check box to indicate whether the equipment is
for LIFO only. If not selected, may still allow LIFO depending on parameter
settings. If selected allows only LIFO.
7. Enter the Length, Width, and Height of the equipment in the equipment
group. These dimensions are used in planning and optimization
calculations.

Note: When you add values to these fields, you also need to choose an appropriate
unit of measure from the drop-down list.
8. In many cases, the height of the door is not equal to the actual height of
the equipment, which can lead to loading limitations. Use the Door Height
field to specify the height of the door so the planning logic can take this
under consideration.
9. If the equipment has a curved roof, use the Curve ID field to define its
curved dimensions. The dimensions and shape of the curved roof are
defined in Power Data and assume that the curve in the roof is
symmetrical from left to right.

Note: Door Height and Curve definitions for Equipment are only considered when
using the load configuration functionality. This functionality must be set to run using
the PERFORM LOAD CONFIGURATION planning parameter.
10.You can assign a Temperature Control ID to the equipment group to define
the minimum/maximum temperature settings that the equipment can
provide during transportation. Temperate Controls are defined on the
Temperature Control page in the Equipment Manager.

Note: If there is no temperature control specified on the equipment, it means no


constraint and is considered compatible.

11.Define the TEU Equivalents or the FEU Equivalents associated with the
equipment. TEU is the Twenty-foot Equivalent Unit and the FEU is the
Forty-foot Equivalent Unit. They are used to describe containers for ocean
vessel shipments. A forty-foot container would be described as 2 TEU's or
2 FEU. These fields are for information only.
12.Define the Max Left Side Weight and Max Right Side Weight to specify the
maximum weight allowed on that side of the equipment. In the Max Side
Difference Weight field, specify the maximum weight difference allowed
between the two sides of the equipment to prevent load imbalance.
13.Enter the Max Length per Ship Unit, Max Width per Ship Unit, Max
Height per Ship Unit per unit.
14.Enter the exterior length, width, and height.

Equipment Group Details


Add equipment compartment information for this equipment group by clicking the
Add a Compartment button.
Obstructions
Add obstructions for this equipment group by clicking the Add Obstruction button.
This allows you to configure equipment groups and compartments that do not have a
uniform rectangular cross-section.
Capacity in Reference Units
Select Equipment Reference Units (ERUs) to define the specific transport handling
units being loaded on the equipment. You can select multiple ERUs. Since you can
have multiple ship units on an order, you can have multiple ERUs.
1. Enter a Compartment Number for compartment level ERU. If the ERU is for
the equipment group, it can be left blank or set to zero. A value of zero or
null means that ERU is specified on the equipment group itself.
2. You can specify a Limit as well as a Maximum Number of Reference Units.
In addition to defining the maximum, this allows you to restrict or set an
artificial limit to allow the placement of up to a certain number of ERUs
and then allows the equipment to be filled with other ERUs.
3. For the Compartment Number field, if the ERU is for the equipment group,
it can be left blank or set to zero. For compartment level ERU, you need to
enter the compartment number in this field. For example, when loading
automobiles, the number of units that fits depends on the size of the
vehicle. You may want to define it as follows:

Large car

Medium car

5
7

Small car

10

4. Click Save.

Note: Continue to add as many equipment reference units as you need. Remember to
click Save after entering each unit.
Equipment Type
1. Enter an Equipment Type ID to associate with this equipment group. If the
equipment group on the shipment does not have any equipment types
associated with it, it is open to be assigned to any equipment type.
2. Click Save.

Note: You can add multiple equipment types. Remember to click Save after adding
each type.
3. Enter a numeric value to indicate the axle sequence.
4. Enter an axle name.
5. Enter the axle distance. This is the distance from the nose of the
equipment and an indication of where maximum weight can be loaded.
6. Enter the maximum weight allowed.
7. Click Save.

Note: You can add multiple axles. Remember to click Save after adding each axle.
8. Enter a vehicle type ID in the Vehicle Type ID field.
9. Click Save.

Note: You can add multiple vehicle types. Remember to click Save after adding each
type.
10.Click Finished.

Axles
This section allows you to specify axle details such as the axle sequence number and
weight allocation. Enter a numeric value to indicate the axle sequence. Enter an axle
name. Enter the axle distance. This is the distance from the nose of the equipment
and an indication of where maximum weight can be loaded. Enter the maximum
weight allowed.
OTM uses equipment status to indicate feasibility. In order to view axle weight
feasibility, check the equipment status. The status type is
AXLE_WEIGHT_FEASIBILITY and the statuses are

AXLE_WEIGHT_FEASIBILITY_FEASIBLE and
AXLE_WEIGHT_FEASIBILITY_INFEASIBLE respectively to indicate feasibility
and infeasibility.
Order Release
Reference Numbers | Specific Equipment to Be Ordered | Related Topics
This page is accessed via Order Management > Order Release > Order Release.
An order release can be created from the release instructions specified on an order
base or independently of an order base. An order release always contains at least one
ship unit and one line item. Some details are copied from the order base. Other field
values can be entered to control shipment planning and while some values are
calculated during the order release process.
Oracle Transportation Management provides you with the ability to use a template to
create a new order release. In order to do so, you must set the property
glog.order_release.show_template to true. Oracle Transportation Management will
ask you to specify a template before it opens the Order Release manager.
An order release can inherit most of its data from the order base from which it was
created such as the order base ID, source/destination locations, pickup/delivery
dates, and some of the ship unit or line item data.
Note: Order release modifications to ship units or ship unit lines that are on the
original order base automatically update the released quantities on the order base
ship unit or order base line respectively.
Deleting order releases also updates the appropriate values on the order base.
Ship units or ship unit lines that are added to an order release are not reflected on the
original order base and these new records do not impact the order base.
1. The Order Release ID is assigned when the order release is created and
cannot be changed. The Order Release ID is generated by the Business
Number Generator (BNG).
2. Enter an Order Release Name to describe the order release.
3. Select a Release Attribute for purposes of identification and searching.
4. Select the Splittable check box to allow splitting of the order. This check
box has priority over the Splittable check boxes on the Ship Unit tab. If not
selected, the order cannot be split at all. The default value of the check
box is controlled by the glog.webserver.order.IsSplittableDefault property.
5. Click the Status button to display the current status types and status
values that are assigned to the order release. You can create your own
status types and values that you can assign to an order release.

6. Select the Use as a Template check box to treat this order release as a
template for re-use. Orders that have this check box selected will not be
bulk planned.
7. Select the Template Type if you are setting up an order release as a
template. The following template types exist:

Buyer: Designating the order release as a buyer template makes the


template available when choosing a template in the Buyer Manager.

Customer: Designating the order release as a customer template


makes the template available when choosing a template in the
Customer Manager.

Domain: Allows you to create templates for domains.

Service: Select Service to create a service template and


automatically assign services to orders. Service template is based
on buyer (destination) and service and can be further constrained
by a source location and/or packaged item.

Note: When defining a service template, you will not be able to save the
template if ship units and/or services are defined on the template.

Standard: If the template is not specific to buyer, customer or


service, choose standard.

Schedule: This sets a shipment's schedule.

8. Enter a Priority if you want to differentiate some order releases as a high,


medium or low priority for planning purposes. Valid values are 1-999, the
higher the number, the higher the priority. You can define it's use as well
as the upper limit of the low priority and medium priority by using
parameters. This field can either be manually assigned or automatically
assigned based on auto assignment rule with user defined criteria. The
priority is copied to the order movement during the building of order
movements. If no priority is entered, the lowest priority is assigned. Note
that when a priority of an order release is updated from one priority to
another, existing priorities on order movements are not updated. Also
when the priority of the order movement is changed, this change does not
change the priority of the order release. There are additional parameters
to determine weighting and use of priority.
9. Click Set Load/Unload Points to assign a specific load or unload point to
the source or destination location on the order release.
10.Use the Early and Late Pickup/Delivery dates to establish the appropriate
pickup and delivery time window for the order. The early and late
pickup/delivery dates can also be used to set appointments. You can
perform mass updates of pickup and delivery dates for multiple order
releases using the Change Pickup and Delivery Dates action.

11.If the order release was created from a quote, then the Quote ID it was
created from will appear here.
12.Make a selection from the Payment Method drop-down list.
13.Select terms in the Commercial Payment Terms drop-down list.
14.The Latest Estimated Delivery Date is read-only. It shows the latest
delivery date from the last leg shipments. It is displayed in the time zone
of the destination location.
15.Select a configuration from the Order Configuration drop-down list;
however, if you checked the Template option, this field is not required. You
will not be able to add ship unit or line information if you do not select an
order configuration.
16.If you are setting up a blind pickup, check the Pre-entered Pickup Order
option.
17.The Source and Destination Location fields are automatically populated
with the locations that you entered on the original order base, if
applicable. You can change these locations on the order release without
having to change them on the order base. When building shipments, if the
Plan From/To Locations are not populated, then these locations are used. If
these locations are used, then the status of both locations must be active
or the shipment will not be created.
18.Plan From/To Location fields let you override the default alternate location
from which an order will be sourced/delivered for transportation planning
purposes. The fields also serve as override locations when running the
Move Order to Existing Shipment action. This default is defined as the
Substitute Location in the Location Manager. It allows you to specify an
alternate location based on the Source/Destination Location that you
record for the order. If you specify a source location and not a plan from
location, the Plan From Location field will be automatically populated when
you save, with the substitute location from the Location Manager. Although
if you manually specify the plan from location it will not be cleared or
changed to the substitute location value.
For example, you may order goods from a supplier at one location but the
goods may actually ship from a different location. For any location that you
define in Location Manager, you can record a substitute location. This
substitute location is copied to the Plan From Location field on the order
release when the order is released. However, you can use this field to
override the substitution location that is mapped to the source location
you entered on the order.
If these locations are populated, the locations must be active or the
shipment will not be created.
Note: Oracle Transportation Management uses the plan from/to locations
on the order release as the source/destination location during shipment

planning. If these fields are blank, Oracle Transportation Management uses


the Source/Destination Location fields to plan a shipment.
19.Primary Leg Source and Destination Locations are used for international
shipments where the entire movement, from the original source to the
final destination, is defined as one leg in the itinerary manager. These
fields identify where the ocean carrier is picking the shipment up from and
delivering it to.
If a Primary Leg Source or Destination Location is defined for an order
release, then for an itinerary to be valid, it must have a matching source
or destination respectively.
20.When building shipments, Oracle Transportation Management will use the
Port of Load and the Port of Discharge to find itineraries with matching VIA
locations. Port of load is the source port for an international shipment
where the entire movement is defined as one leg in the itinerary manager.
Similarly, the port of discharge is its destination port.
If a port of load or port of discharge is defined for an order release, then
for an itinerary to be valid, it must have a matching VIA Source or VIA
Destination Location respectively.
For example, if an order begins in Maastricht, Netherlands, is shipped via
truck to Rotterdam, then shipped via vessel to Philadelphia where it is then
shipped via truck to Pittsburgh, PA, then the primary leg source is
Maastricht, the port of load is Rotterdam, the port of discharge is
Philadelphia, and the primary leg destination is Pittsburgh.

Reference Numbers
Use this section to assign reference numbers.

Specific Equipment to Be Ordered


Use this section if you want to constrain the order release to ship on specific
equipment. The equipment that you enter here overrides any equipment specified on
either the parent order base or itinerary (in the equipment group profile). Any
equipment specified here must be assigned to a ship unit via the Order Release
Equipment field on the ship unit.
1. Enter a Sequence for the equipment. This number precedes the equipment
group choices that appear in the Order Release Equipment ID field on the
Ship Unit tab.
2. Enter an Equipment Group. When you identify equipment on the order,
Oracle Transportation Management skips container optimization process
when building shipments.
3. Specify an Equipment Type. Specifying an Equipment Type is useful if you
assign more than one of the same Equipment Group. For example, if you
assign two 53FT containers, you may want to uniquely identify one
container from the other using the Equipment Type.

4. Enter an Equipment ID.


5. Enter the Equipment Initial. If the Equipment Initial/Number field is blank
and this field is populated, then the Equipment Initial/Number field with be
filled with concatenated data from the Equipment Initial and Equipment
Number fields.
6. Enter the Equipment Number. If the Equipment Initial/Number field is
blank and this field is populated, then the Equipment Initial/Number field
with be filled with concatenated data from the Equipment Initial and
Equipment Number fields.
7. Enter the Equipment Initial/Number. The Equipment Initial/Number field is
usually a concatenation of the Equipment Initial and Equipment Number
fields. If this field is left blank, but the Equipment Initial and Equipment
Number fields are populated, then this field will be populated with a
concatenation of the values of the other two fields. This field identifies the
carrier who owns the equipment. This is standard alpha code (also known
as a "mark") that is uniquely assigned to the carrier and is associated with
their SCAC code (Standard Carrier Alpha Code).
8. Click Save for each equipment group you specify

You might also like