Master Data Management – MDM POB (Version 1.

1)

INTRODUCTION ON MASTER DATA

Master data management (MDM) is a comprehensive method of enabling an enterprise to link all of its critical data
to one file, called a master file that provides a common point of reference. When properly done, master data
management streamlines data sharing among personnel and departments.

At its core Master Data Management (MDM) can be viewed as a "discipline for specialized quality
improvement" defined by the policies and procedures put in place by a data governance organization. The ultimate
goal being to provide the end user community with a "trusted single version of the truth" from which to base
decisions.

Types of Master Data for OTM

1) LOCATION
2) SERVICE PROVIDER
3) ITEM
4) COMMODITY
5) REGION
6) EQUIPMENT
7) LANE
8) ITINERARY
9) RATES
10) SHARE OF BUSINESS

Sources to obtain of Master Data Information

 Master Data information for Location, service provider and items are received via integration from SAP
except for Item Refnums, Location Refnums as these are maintained directly in OTM and not stored in
SAP.
 Other Master Data information for Equipment, Lane, Region and Rate, the Business provides the
necessary Master Data information.

1) Location:

Location refers to a particular place or position to which orders can be delivered or from where the goods
can be picked up. In other words, any point which either sent goods or receives goods is a location

Note: Even a Transport Service Provider (TSP) will have a location as it has point of contact (Head Office, Agency)

For example: Plants, depot, Rail yards, Airport, Assembly points, distributors, vendors, retail sellers

Unilever locations are classified as below:

  Plants (Factory, Depot, Hub, Warehouse)
 Customer/Retail Seller (SOB customers/RS)
 Supplier/Vendor (PIB suppliers)

Location Related Templates

1.1. LOCATION
1.2. LOCATION ADDRESS
1.3. LOCATION ROLE PROFILE
1.4. LOCATION REFNUM

1.1.LOCATION
Location is the Primary & Independent template for which we define GID, XID, Location name, City,
Province, and Zones.

Location template contains information like Location Code (vendor/Customer/shipping point code from SAP),
Location Name, Location Description, Location Constraints and zone details. Location Primary template is as below.
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Location GID - Concatenation of DOMAIN_NAME+"."+LOCATION_XID

2. Location XID – The location ID or CODE. Ex: U036(POB), HNF (POB), 431602 (SOB), 2000023(PIB)
3. Is Temporary - Default value is always ‘N’ meaning “NO”. A flag to identify if the location is created
temporarily for a certain shipment or order. This location will not be used for other shipments or
processes.
4. Is Make Appt Before Plan - Default value is always ‘N’ meaning “NO”. A true or false flag to identify if
an appointment is required at the location for (example) for pickup, delivery etc.
5. Is Shipper Known - Default value is always ‘N’ meaning “NO”.
6. Is Address Valid - Default value is always ‘Y’ meaning “YES”. Flag to indicate whether the address is
considered valid or not (by checking against the POSTAL_CODE_VALIDATE table).
7. Is LTL Splitable - Default value is always ‘N’ meaning “NO”.
8. BB Is New Store - Default value is always ‘N’ meaning “NO”. Indicates if this location should be treated
as a new store by the Batch Balancer logic. New stores can only be assigned by Batch Balancer to a
DOOR whose LOAD_NEW_STORE field is set to Y.
 9. Exclude From Route Execution - Default value is always ‘N’ meaning “NO”. When = Y, this location is
excluded from any Route Instance Legs.
10. Is Template - Default value is always ‘N’ meaning “NO”.
11. Primary Address Line Seq – - Default value is always ‘1’
12. Attribute1 - To capture Customer Classification details like GT/MT etc.
13. Attribute2 - To capture the zone Id
Both these attribute fields are used in selecting orders for bulk run and for reporting purposes also.
14. Domain Name - Default value is always ‘ULF’ for India

1.2.LOCATION ADDRESS
Location address is the Secondary & dependent template of Location, it contains the complete address for
the location.

Template is as below:

In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Location GID – Location GID is already created in location template, we use the same.
2. Line Sequence - Default value is always ‘1’.Address should be in a single line in address field
3. Domain Name - Default value is always ‘ULF’ for India.

1.3.LOCATION ROLE PROFILE

Location Role Profile is the Secondary & dependent template Location. It defines the role (nature) of the
Location. For actual locations it is SHIPFROM/SHIPTO, for TSP it is defined as CARRIER. Template is as below:
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Location GID - Location GID is already created in location template, we use the same.
2. Location Role GID - For actual locations it is SHIPFROM/SHIPTO, for TSP it is defined as CARRIER.
3. Create Xdock Handling Shipment - Default value is always ‘N’ meaning “NO”.
4. Create Pool Handling Shipment - Default value is always ‘N’ meaning “NO”.
5. Is Allow Mixed Freight - Default value is always ‘N’ meaning “NO”.
6. Domain Name - Default value is always ‘ULF’ for India

1.4. LOCATION REFNUM

Location Refnum is the Secondary & dependent template of location. Location refnum or reference number
variables are custom fields used to assign any particular characteristic or identifier to the locations.

 REFNUM 1 – Direct Dispatch Loadability Percentage

 REFNUM 2 – Secondary Outbound Loadability Percentage
 REFNUM 3 – Primary Inbound Loadability Percentage
 REFNUM 4 – Primary Outbound Loadability Percentage

The Loadability can be captured on basis of various parameters such as weight, volume or number of pallets
depending on different business scenarios. Template is as below:
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Location GID - Location GID is already created in location template, we use the same.
2. Location Refnum Qual GID – Explains element to which we want to any particular characteristic or identifier

E.g.: ULF.ULF_PRIMARY OUTBOUND LOADABILITY %, ULF.ULF_VALUE CAP

3. Location Refnum Value – Standard value set against each element for the particular location on the basis
various parameters such as weight, volume or number of pallets
4. Domain Name - Default value is always ‘ULF’ for India.

2) SERVICE PROVIDER

The service provider or the Transporter Service provider (TSP) is a party who provide service to you in physical
movement of goods between locations. In other words a TSP is someone who places his truck for an agreed material.
In few cases a TSP might also provide additional transport related services like HANDLING (Loading and unloading) of
goods. A TSP can be a Carrier, freight forwarder, customs broker, 3PL or some other type of company that provide
service to you.

Location Role Profile for carriers is defined as CARRIER.

Transport Service Provider Location Related Templates

There are 5 templates for TSP. They are as follows:

2.1. SERVICE PROVIDER

2.2. SERVICE PROVIDER ALIAS

As we consider a TSP as a LOCATION, we are even supposed to maintain the below LOCATION templates:

2.3. LOCATION (TSP)

2.4. LOCATION ADDRESS (TSP)
2.5. LOCATION ROLE PROFILE (TSP)
2.1.SERVICE PROVIDER

The Service Provider template is the Primary template for TSP in which we define the XID, Gid, domain name
etc. The template of Service Provider is as below:

In the above template the fields highlighted in yellow are SYSTEM MANDATORY fields which cannot be left
blank.

SYSTEM Mandatory fields:

 SERVPROV_GID
 SERVPROV_XID
 IS_DISPATCH_BY_REGION
 ALLOW_TENDER
 IS_ACCEPT_BY_SSU_ALLOWED
 IS_COPY_INV_DELTA_BACK_TO_SHIP
 DOMAIN_NAME
 Default Fields and Default value:

 ALLOW_TENDER: default value is always “Y” meaning Yes

 IS_ACCEPT_BY_SSU_ALLOWED: default value is “N” meaning No.
 IS_DISPATCH_BY_REGION: default value is “N” meaning No.
 IS_COPY_INV_DELTA_BACK_TO_SHIP: default value is “N” meaning No.

Descriptions:

 SERVPROV Xid: The service provider id or code. E.g.: X0618, X0266.

 SERVPROV Gid: Concatenation of DOMAIN_NAME+"."+SERVPROV_XID. E.g.: ULF.X0168, ULF.X0266.
 IS_DISPATCH_BY_REGION: A flag to turn on/off the Tender by Locale feature
 ALLOW_TENDER: Will the carrier be allowed to accept or reject tenders?
 Domain: The default Domain name for India is ULF

2.2.SERVICE PROVIDER ALIAS

Alias means “Also called as”. Service provider Alias template is used to add the substituted name if any for the
Service provider. However, in HUL we do not use any such substitute name. So, the Alias is same as the service
provider id or code.

Description:

 SERVPROV_GID: Service provider Gid is already created in Service provider template. We use the same.
 SERVPROV_ALIAS_QUAL_GID: GLOG will be the default for this field.
 ALIAS: Alias will be the same as service provider SERVPROV_GID.
 Domain: The default Domain name for India is ULF
 If a supplier do both supply and handling then it’ll be entered in both Location and TSP template. The
ROLE in Location Roll template will be both CARRIER and SHIPFROM/SHIPTO.

2.3.LOCATION (TSP)

Location is the Primary & Independent template for which we define GID, XID, Location name, City,
Province, and Zones.

Location template contains information like Location Code (vendor/Customer/shipping point code from SAP),
Location Name, Location Description, Location Constraints and zone details. Location Primary template is as below.
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Location GID - Concatenation of DOMAIN_NAME+"."+LOCATION_XID

2. Location XID – The location ID or CODE. Ex: U036(POB), HNF (POB), 431602 (SOB), 2000023(PIB)
3. Is Temporary - Default value is always ‘N’ meaning “NO”. A flag to identify if the location is created
temporarily for a certain shipment or order. This location will not be used for other shipments or
processes.
4. Is Make Appt Before Plan - Default value is always ‘N’ meaning “NO”. A true or false flag to identify if
an appointment is required at the location for (example) for pickup, delivery etc.
5. Is Shipper Known - Default value is always ‘N’ meaning “NO”.
6. Is Address Valid - Default value is always ‘Y’ meaning “YES”. Flag to indicate whether the address is
considered valid or not (by checking against the POSTAL_CODE_VALIDATE table).
7. Is LTL Splitable - Default value is always ‘N’ meaning “NO”.
8. BB Is New Store - Default value is always ‘N’ meaning “NO”. Indicates if this location should be treated
as a new store by the Batch Balancer logic. New stores can only be assigned by Batch Balancer to a
DOOR whose LOAD_NEW_STORE field is set to Y.
9. Exclude From Route Execution - Default value is always ‘N’ meaning “NO”. When = Y, this location is
excluded from any Route Instance Legs.
10. Is Template - Default value is always ‘N’ meaning “NO”.
11. Primary Address Line Seq – - Default value is always ‘1’
12. Attribute1 - To capture Customer Classification details like GT/MT etc.
13. Attribute2 - To capture the zone Id
Both these attribute fields are used in selecting orders for bulk run and for reporting purposes also.
14. Domain Name - Default value is always ‘ULF’ for India

2.4.LOCATION ADDRESS (TSP)

Location address is the Secondary & dependent template of Location, it contains the complete address for
the location.

Template is as below:
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Location GID – Location GID is already created in location template, we use the same.
2. Line Sequence - Default value is always ‘1’.Address should be in a single line in address field
3. Domain Name - Default value is always ‘ULF’ for India

2.5.LOCATION ROLE PROFILE (TSP)

Location Role Profile is the Secondary & dependent template Location. It defines the role (nature) of the
Location. For actual locations it is SHIPFROM/SHIPTO, for TSP it is defined as CARRIER. Template is as below:

In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.
System Mandatory Fields:

1. Location GID - Location GID is already created in location template, we use the same.
2. Location Role GID - For actual locations it is SHIPFROM/SHIPTO, for TSP it is defined as CARRIER.
3. Create Xdock Handling Shipment - Default value is always ‘N’ meaning “NO”.
4. Create Pool Handling Shipment - Default value is always ‘N’ meaning “NO”.
5. Is Allow Mixed Freight - Default value is always ‘N’ meaning “NO”.
6. Domain Name - Default value is always ‘ULF’ for India

3) ITEM

Item refers to the specific goods or materials that are shipped. It can be anything like a raw material, a semi
finished goods or any finished products. It defines the product or goods being shipped.

Item Related Templates

3.1. ITEM
3.2. PACKAGED ITEM
3.3. ITEM REFNUM

3.1.ITEM
Item master is the Primary & Independent template for which we define GID, XID,
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Item Gid - Concatenation of DOMAIN_NAME+"."+

2. Item Xid -
3. Is Drawback -
4. Is Template -
5. Domain Name - Default value is always ‘ULF’ for India

3.2.PACKAGED ITEM
Packaged Item is the Secondary & dependent template of
Template is as below:

In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Location GID – Location GID is already created in location template, we use the same.
2. Line Sequence - Default value is always ‘1’.Address should be in a single line in address field
3. Domain Name - Default value is always ‘ULF’ for India

3.3.ITEM REFNUM
Item Refnum is the Secondary & dependent template
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Packaged Item Gid - Concatenation of DOMAIN_NAME+"."+

2. Packaged Item Xid -
 3. Item Gid -
4. Is Default Packaging -
5. Is Hazardous -
6. Is Handling Unit Stackable -
7. Domain Name - Default value is always ‘ULF’ for India

4) COMMODITY

A commodity is a group of items that have similar shipping characteristics.

Commodity Related Templates

4.1. COMMODITY
4.2. COMMODITY INCOMPATIBILITY

4.1.COMMODITY
Commodity is the Primary & Independent template. Grouping Items into a commodity.

During equipment selection, OTM uses commodities, since commodities group multiple items, your items must be
able to be transported in the same piece of equipment. For e.g. a commodity of snack may include items such as
pretzels, peanuts, and chocolate and cookies.

In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Commodity Gid- Concatenation of DOMAIN_NAME+"."+

2. Commodity Xid -
3. Is Temp Control -
4. Req Eqpmt Group Profile Gid -
5. Domain Name - Default value is always ‘ULF’ for India
 4.2.COMMODITY INCOMPATIBILITY
Commodity Incompatibility is the Secondary & dependent template of Commodity. Taint Category matrix will be
mapped to Commodity in Commodity Incompatibility. In general, Taint Matrix values stored here.
Template is as below:

System Mandatory Fields:

1. Commodity Gid1- Concatenation of DOMAIN_NAME+"."+

2. Commodity Gid2 -
3. Domain Name - Default value is always ‘ULF’ for India

5) REGION

Regions are clustering of various Locations that have same characteristics like

 Locations in same town/city

 Locations having same freight rate from 1 particular DC.

Regions are assigned for the purpose of Optimization and Rating.

Region Related Templates

5.1. REGION
5.2. REGION DETAIL

5.1.REGION
Region is the secondary & dependent template of Location. It is for region definition. Region
definition can be done based on various multistop scenarios.

 MultiPick region
 MultiDrop Region
 Simple Point To Point Region

In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.
 System Mandatory Fields:

1. Region Gid - Concatenation of DOMAIN_NAME+"."+

2. Region Xid -
3. Domain Name - Default value is always ‘ULF’ for India

5.2.REGION DETAIL
Region Detail is the Secondary & dependent template of Region. It is used to assign region to various
Locations.
Template is as below:

System Mandatory Fields:

1. Region Gid -
2. Sequence Num -
3. Geo Hierarchy Gid -
4. Domain Name - Default value is always ‘ULF’ for India
 6) EQUIPMENT

Equipment is a truck or any means of transport which moves goods between locations.

Equipment Related Templates

6.1. EQUIPMENT GROUP
6.2. EQUIPMENT TYPE
6.3. EQUIPMENT TYPE JOINT
6.4. EQUIPMENT GROUP PROFILE
6.5. EQUIPMENT GROUP PROFILE DETAIL
6.6. EQUIPMENT TYPE REMARK

6.1.EQUIPMENT GROUP
Equipment Group is the Secondary & dependent template of Equipment Type. It identifies 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. It also captures attributes that describe the
capacity of the equipment.

Template is as below:
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Equipment Group Gid - Concatenation of DOMAIN NAME+"."+

2. Equipment Group Xid -
3. Effective Weight -
4. Effective Weight Uom Code -
5. Effective Weight Base -
6. Effective Volume -
7. Effective Volume Uom Code -
8. Effective Volume Base -
9. Width -
10. Width Uom Code -
11. Width Base -
12. Length -
13. Length Uom Code -
14. Length Base -
15. Height -
16. Height Uom Code -
17. Height Base -
18. Is Container -
19. Domain Name - Default value is always ‘ULF’ for India

6.2.EQUIPMENT TYPE
Equipment is the Primary & independent template. It defines the characteristics of the equipment
Group.
Template is as below:
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Equipment Type Gid - Concatenation of DOMAIN_NAME+"."+

2. Equipment Type Xid -
3. Gross Weight -
4. Gross Weight Uom Code -
5. Gross Weight Base -
6. Tare Weight -
7. Tare Weight Uom Code -
8. Tare Weight Base -
9. Net Weight -
10. Net Weight Uom Code -
11. Net Weight Base -
12. Volume -
13. Volume Uom Code -
14. Volume Base -
15. Interior Length -
16. Interior Length Uom Code -
17. Interior Length Base -
18. Interior Width -
19. Interior Width Uom Code -
20. Interior Width Base -
 21. Interior Height -
22. Interior Height Uom Code -
23. Interior Height Base -
24. Exterior Length -
25. Exterior Length Uom Code -
26. Exterior Length Base -
27. Exterior Width -
28. Exterior Width Uom Code -
29. Exterior Width Base -
30. Exterior Height -
31. Exterior Height Uom Code -
32. Exterior Height Base -
33. Temperature Control -
34. Domain Name - Default value is always ‘ULF’ for India

6.3.EQUIPMENT TYPE JOINT

Equipment Type Joint is the Secondary & dependent template of Equipment Type. It is a linking
template between equipment group and equipment type.

Template is as below:

In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Equipment Type Gid - Concatenation of DOMAIN NAME+"."+

2. Equipment Group Gid -
3. Domain Name - Default value is always ‘ULF’ for India

6.4.EQUIPMENT GROUP PROFILE

Equipment Group Profile is Secondary & dependent template of Equipment Type. It is used to do
grouping of various Equipment groups by some common attribute or grouping scheme. It can be specified
on: Location, Itinerary, Rates, Physical characteristics, Item etc.

Template is as below:
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Equipment Group Profile Gid - Concatenation of DOMAIN NAME+"."+

2. Equipment Group Profile Xid -
3. Is Compatible -
4. Domain Name - Default value is always ‘ULF’ for India

6.5.EQUIPMENT GROUP PROFILE DETAIL

Equipment Group Profile Detail is the Secondary & dependent template of Equipment Type. It
defines the details about Equipment Group Profile. The equipments which fall under an equipment group
profile are recorded in this template.

Template is as below:

In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Equipment Group Profile Gid - Concatenation of DOMAIN NAME+"."+

2. Equipment Group Gid -
3. Domain Name - Default value is always ‘ULF’ for India

6.6.EQUIPMENT TYPE REMARK

Equipment Type Remark is the Secondary & dependent template of Equipment Type. It is used for
scaling factor and CO2 Emission.

Template is as below:
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Equipment Type Gid - Concatenation of DOMAIN NAME+"."+

2. Remark Sequence -
3. Remark Text -
4. Domain Name - Default value is always ‘ULF’ for India

7) LANE

Lane may be defined as link between a source and a destination. In case of Unilever there are 4 different types of
Lane. They are as follows:

 Point to Point: Shipping Point – Receiving Point combination

 Region to Point: Shipping Point – Receiving Region combination
 Point to Region: Shipping Region – Receiving Point combination
 Region to Region: Shipping Region – Receiving Region combination

Lane Related Templates

A lane has three templates inter-related for capturing Lane, Transit Time and Distance information. These templates
are given below:

7.1. X LANE
7.2. SERVICE TIME
7.3. DISTANCE LOOKUP

7.1.X LANE

Captures Source and destination information for the lane

In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. X Lane Gid - Concatenation of DOMAIN NAME+"."+

2. X Lane Xid -
3. Domain Name – Default value is always ‘ULF’ for India

7.2.SERVICE TIME
 In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. X Lane Gid –
2. Rate Service Gid -
3. Service Time Value -
4. Service Time Value Uom Code -
5. Service Time Value Base -
6. Domain Name - Default value is always ‘ULF’ for India

7.3.DISTANCE LOOKUP

In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. X Lane Gid –
2. Rate Distance Gid -
3. Distance Value -
4. Distance Value Uom Code -
5. Distance Value Base -
6. Domain Name - Default value is always ‘ULF’ for India

8) ITINERARY

Itinerary Related Templates

. These templates are given below:

8.1. ITINERARY
8.2. LEG
8.3. ITINERARY DETAIL
8.1.ITINERARY
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Itinerary Gid -
2. Itinerary Xid -
3. Is Multi Stop -
4. Perspective -
5. Total Cost -
6. Total Cost Gid -
7. Total Cost Base -
8. Total Transit Time -
9. Total Transit Time Uom Code -
10. Total Transit Time Base -
11. Min Tl Usage Percentage -
12. Is Dest Bundle Prefered -
13. Rank -
14. Itinerary Type -
15. Is Rule 11 -
16. Is Match Deconsol Pool To Dest -
17. Is Match Consol Pool To Src -
18. Domain Name - Default value is always ‘ULF’ for India

Business Mandatory Fields:

1. Itinerary Name -
2. Description -
3. Min Weight -
4. Min Weight Uom Code -
5. Max Weight -
6. Max Weight Uom Code -
7. Min Volume -
8. Min Volume Uom Code -
9. Max Volume -
10. Max Volume Uom Code -
11. X Lane Gid -

8.2.LEG
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Leg Gid -
2. Leg Xid -
3. Create Single Shipment -
4. Is Primary -
5. Mode Profile Gid -
6. Expected Transit Time -
7. Expected Transit Time Uom Code -
8. Expected Transit Time Base -
9. Expected Cost -
10. Expected Cost Base -
11. Expected Cost Currency Gid -
12. Equipment Assignment Type -
13. Calculate Contracted Rate -
14. Calculate Service Time -
15. Servprov Assignment Type -
16. Auto Consolidation Type -
17. Interim Point Option -
18. Plan To Operational Loc -
19. Is Temporary -
20. Is Use Consol -
21. Leg Type -
22. Allow Cross Consolidation -
23. Domain Name – Default value is always ‘ULF’ for India

Business Mandatory Fields:

1. Leg Name –
2. Source Location Gid –
3. Dest Location Profile Gid –
4. Source Location Role Gid –
5. Dest Location Gid –
 6. Dest Location Role Gid –
7. Servprov Profile Gid –
8. Equipment Group Profile Gid –
9. Rate Offering Gid –
10. Rate Geo Gid –
11. Equip Group Profile Set Gid –
12. Rate Service Profile Gid –
13. Source Region Gid –
14. Dest Region Gid –

8.3.ITINERARY DETAIL

In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Itinerary Gid–
2. Leg Gid–
3. Sequence No–
4. Domain Name– Default value is always ‘ULF’ for India

9) RATES

In Rate, we define rates for all lanes with a particular Service provider and Truck type. In simple words under Rate
Management we link the Lane with a service provider and Equipment and define a fixed rate for that particular
Equipment of that service provider to move in that Lane. Once an order is planned onto a shipment, it gets rated so
as to arrive at the overall cost of transportation. The cost of transportation, apart from the base freight cost, also
includes various other costs like loading/unloading charges, stop off charges, under load charges, document fees,
storage charges, discounts, etc.

Templates under Rate Management

Under Rate Management there are 17 templates. They are:

9.1. Rate Service

9.2. Rate Version
9.3. Rate Quality
9.4. Dim Rate Factor
9.5. Rate Offering
9.6. Rate Geo
9.7. Rate Geo Cost Group
 9.8. Rate Geo Cost
9.9. Rate Geo Stop
9.10. CM Rule
9.11. Capacity Group
9.12. Capacity Limit
9.13. Mode Profile
9.14. Mode Profile Detail
9.15. Secondary Charge Rule
9.16. Transport Mode
9.17. Accessorial Code

9.1. Rate Service

Rate service is defined to provide correct Lead time corresponding to the mode of transport. Rate Service
determines how to calculate the transit time based on the rate service type and other factors like wait time, rest
period, etc. LOOKUP, ESTIMATE, LOOKUP ELSE ESTIMATE’ are few common Rate Service Types used in defining Rate
Service. The ‘LOOKUP ELSE ESTIMATE’ type of rate service allows us to either define the transit times based on lanes
or estimate the time based on parameters like Latitude & Longitude defined. It will also provide an added flexibility
to use any external search engine (e.g. PC Miller) for calculating Service Time.

The Template of Rate service is as follows:

In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Rate Service GID - Concatenation of DOMAIN_NAME+"."+ RATE_SERVICE_XID

2. Rate Service XID – The Xid will be the lookup of the particular mode.
E.g. for TL mode XID is “ULF_LOOKUP_TL”
3. Rate Service Type – Default will be “LOOKUP”
4. Max Work Time Usage Type - Default will be “REST WHEN TIME EXCEEDED”
5. Is Ignore Delv Loc Calendar - Default will be “Y”
6. Is Use Rush Hour - Default will be “Y”
7. Domain Name - Default will be “ULF”

9.2. RATE VERSION

Rate version master data captures the contract validity dates (start date and End Date) for a particular Service
Provider. This Rate Version is attached at the Rate Offering level and not at Rate Record Level.
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Rate Version GID - Concatenation of DOMAIN_NAME+"."+ RATE_VERSION_XID

2. Rate Version XID – It’s a combination of Effective date and Expiry date
3. Effective Date – It is the date from when the contract is Valid
4. Expiration Date – It is the date on when the contract ends
5. Domain Name - Default value is always ‘ULF’.

9.3. Rate Quality

Rate Quality is used to assign/ change priorities of equipments/ service Providers

A Rate Quality factor makes service provider rates look more or less attractive during the planning process. They
help weigh rates of various service providers and thereby facilitate selection of the preferred one.

For instance, Unilever follows a practice of defining a ‘Primary Carrier’ and a ‘Generic Carrier’ for a particular
lane and prefers a primary carrier over any generic carrier. To achieve this, a Rate quality factor is defined such
that the rate of the primary service provider is decreased by a certain percentage or flat amount so that the
OTM planning logic considers this rate to be cheaper compared to the rates of any generic service providers.

Rate quality factors do not affect the actual cost of a shipment but is only be used for cost comparison purpose
and thereby help qualify primary service provider rates.

In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Rate Quality GID - Concatenation of DOMAIN_NAME+"."+ RATE_QUALITY_XID

2. Rate Quality Xid – Various priorities such as Rate Quality 900, Rate Quality 999, Rate Quality Priority, and
Rate Quality Dedicated
 3. Adjustment Percent – The percentage value such as 900, 999, 0.1 & 0.01 are given here. 999 being the least
priority and 0.01 being the highest priority.
4. Adjustment Flat – Default value is ‘0’
5. Currency GID – currency of the country. Here the default will be ‘INR’
6. Domain Name - Default value is always ‘ULF’.

9.4. Dim Rate Factor

Holds dimensional conversion factor from one class to another. E.g. Conversion from weight to volume. It can be
linked to rate Offering/ Rate Record.

The Dim Rate Factor is used in scenarios where such conversion between different classes is required for doing
to the final rating.

In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Dim Rate Factor Gid - Concatenation of DOMAIN_NAME+"."+ DIM_RATE_FACTOR_XID

2. Dim Rate Factor Xid – Default value is ‘DIM_8_1’
3. Unit 1 - Default value is ‘1’
4. Unit 1 Uom Code - Default value is ‘CUFT’
5. Unit 1 Uom Class - Default value is ‘V’ means Volume
6. Unit 2 - Default value is ‘8’
7. Unit 2 Uom Code - Default value is ‘KG’
8. Unit 2 Uom Class - Default value is ‘W’ means Weight
9. Domain Name - Default value is ‘ULF’

In India, 1CUFT is of 8 KGs.

9.5. Rate Offering

A Rate Offering represents a freight contract with a service provider.

It would capture general contractual details like:

 a. Mode of transport
b. Weight/volume/dimensional constraints
c. Geographical regions supported
d. Item/commodity constraints
e. Equipment constraints

A separate rate offering is defined per actual/physical contract with a service provider so as to realistically
represent the service provider contracts.

Once a rate offering is defined, the OTM planning engine fetches all necessary contract related data from it (in
conjunction with any route level data) for qualifying rates for a shipment.

• Rate offering is the object that defines the overall contract with the carrier.

• This object enlists the contract type, transport mode, validity and distance calculation mode.
In the above template the fields highlighted in YELLOW are system mandatory fields which cannot left blank.

System Mandatory Fields:

1. Rate Offering Xid - Combination of service provider and Equipment

2. Rate Offering Gid - Concatenation of DOMAIN_NAME+"."+ RATE_OFFERING_XID
3. Rate Offering Type Gid – Mode of Transport
4. Currency Gid-Currency of the country. In India it is INR
5. Transport Mode Gid-Mode of transport.
6. Rate Version Gid-Taken from Rate Version
7. Rate Distance Gid-Default value is LOOKUP ELSE ESTIMATE
8. Exchange Rate Gid- Default value is Default
9. Commodity Usage- Default value is ‘F’
10. Fak Rate As- Default value is ‘N”
11. Perspective-Default value is ‘B’
12. Allow Uncosted Line Items- Default value is ‘N’
13. Is Active- Default value is ‘Y’
14. Handles Unknown Shipper - Default value is ‘Y’
15. Is Depot Applicable- Default value is ‘N’
16. Recalculate Cost - Default value is ‘N’
17. Is Contract Rate - Default value is ‘N’
18. Use Tact As Display Rate 1 - Default value is ‘Y’
19. Is Direct Only Rate - Default value is ‘Y’
20. Use Tact As Display Rate 2 - Default value is ‘Y’
21. Use Tact As Display Rate 3 - Default value is ‘Y’
22. Is Route Execution Rate - Default value is ‘N’
23. Package Count Method - Default value is ‘L’
24. Rate Offering Seq – Sequence # is filled in OTM
25. Is Template - Default value is ‘N’
26. Is Sourcing Rate - Default value is ‘N’
27. DOMAIN_NAME - Default value is ‘ULF’

9.6. Rate Geo

Rate Geo is used to capture Lane, Equipment and TSP Information for the rate record. Service Provider can work on a
particular lane with particular equipment and priority to the equipment is also given here. The template of Rate Geo
is given below:
System Mandatory Fields-

1. Rate Geo Gid - Concatenation of DOMAIN_NAME+"."+RATE_GEO_XID

2. Rate Geo Xid - Combination of Lane+Service provider+Transport mode+Equipment+Expiry date
3. Rate Offering Gid - Taken from Rate offering template
4. Allow Uncosted Line Items - Default value is ‘N’
5. Multi Base Groups Rule - Default value is ‘A’
6. Is Master Overrides Base - Default value is ‘N’
7. Is Quote - Default value is ‘N’
8. Is Active - Default value is ‘Y’
9. Rate Geo Seq - Sequence # is filled in OTM
10. Domain Name - Default value is ‘ULF’ for India
 Business Mandatory Fields-

1. X Lane Gid - Taken from X-Lane

2. Equipment Group Profile Gid - Taken from Equipment Group Profile
3. Rate Service Gid - Taken from Rate Service
4. Pickup Stops Constraint – Default Value is ‘1’
5. Delivery Stops Constraint - Default Value is ‘1’
6. Effective Date - It is the date from when the contract is Valid
7. Expiration Date - It is the date on when the contract Ends
8. Hazardous Rate Type - Default value is ‘N’

9.7. Rate Geo Cost Group

Rate Geo Cost Group captures the different Costing groups based on which the cost would be defined.

E.g. Base Freight and Handling is few of the different cost. In this template only the cost groups are recorded.

The template of Rate Geo Cost Group is given below:

System Mandatory Fields:

1. Rate Geo Cost Group Gid - Concatenation of DOMAIN_NAME+"."+ RATE_GEO_COST_GROUP_XID

2. Rate Geo Cost Group Xid - Combination of Lane+Service provider+Transport mode+Equipment+Expiry
Date
3. Rate Geo Gid – Taken from Rate Geo Template
4. Rate Geo Cost Group Seq – Default Value is ‘1’ for Base Freight & ‘2’ for Under load Charges
5. Multi Rates Rule - Default Value is ‘A’ for Base Freight & ‘X’ for Under load Charges
6. Rate Group Type - Default Value is ‘B’ for Base Freight & ‘M’ for Under load Charges
7. Domain Name - Default value is ‘ULF’ for India
 9.8. Rate Geo Cost
It is used to capture the validity period and actual costing details for different cost groups. Service Provider will work
on this rate for this lane and equipment. Template for Rate Geo Cost is as follows:
 System Mandatory Fields:

1. Rate Geo Cost Group Gid - Taken from Rate Geo Cost Group Template
2. Rate Geo Cost Seq – For POB the Seq is ULF.Z501, SOB Base freight is ULF.Z506 & Under load charges is
ULF.Z507
3. Charge Type – Default Value is ‘I’
4. Is Filed As Tariff – Default Value is ‘N’
5. Cost Type – Default Value is ‘N’
6. Domain Name - Default value is ‘ULF’ for India

Business Mandatory Fields:

1. Oper1 Gid – The value may be EQ (Equal), GT (Greater than) & LT (Less than) based upon the scenario
2. Left Operand1 – It is an OTM command and it should be given as it is in OTM E.g.
SHIPMENT.STOPS.SHIPUNITS.ACTIVITY
3. Low Value1 - The Value is ‘D’ mean Drop or ‘P’ mean Pick
4. High Value1 -
5. And Or1 - The Value is ‘A’ mean And or ‘O’ mean Or
6. Left Operand2 - It is an OTM command and it should be given as it is in OTM E.g.
SHIPMENT.ORDERS.DEST.LOCATION
7. Low Value2 – For the Above Operand low value will be Destination Location
8. High Value1 -
9. And Or2 - The Value is ‘A’ mean And or ‘O’ mean Or
10. Charge Amount – Actual Rate Provided by the Business
11. Charge Amount Base – Default value is ‘INR’ for Indian currency
12. Charge Unit Uom Code – The unit of measurement e.g. MTON
13. Charge Unit Count - Default Value is ‘1’
14. Charge Multiplier – It is an OTM command and it should be given as it is in OTM E.g.
SHIPMENT.STOPS.SEL_WEIGHT
15. Charge Action – Default Value is ‘A’
16. Charge Multiplier Option – Default value is ‘I’

9.9. Rate Geo Stop

Rate Geo stop is used for Fixed Stop off Charges. If there transporter has a fixed number of stops on which he will
deliver the goods or if he will charge additional charge after number of stops then we use this template. The
template is given below:
 System Mandatory Fields:

1. Rate Geo Gid – Taken from Rate Geo Template

2. Low Stop – The max point till where the transporter delivers goods without charging anything additional
3. High Stop - The max point till where the transporter delivers goods even after charging additional cost
4. Per Stop Cost – Defined by the business
5. Per Stop Cost Gid - Default value is ‘INR’ for Indian currency
6. Per Stop Cost Base – Same as per stop cost
7. Domain Name - Default value is ‘ULF’ for India

9.10. Capacity Group

Capacity group is used to define a group with constraints at an Equipment and service provider Level. If a service
provider has a capacity to provide limited number of a particular truck, then in this group we put and contains for
that truck. In simple this template is used to define a Group for Capacity.

The template is as follows:

System Mandatory Fields:

1. Capacity Group Gid - Concatenation of DOMAIN_NAME+"."+ CAPACITY_GROUP_XID

2. Capacity Group Xid – GID of the Service provider
3. Domain Name - Default value is ‘ULF’ for India

9.11. Capacity Limit

The capacity limit template captures the value (number) for the constraint defined in the Capacity Group. If a
particular truck type is restricted in capacity group, in this we record the number of trucks of that particular truck
type to be limited.

The template is as follows:

 System Mandatory Fields:

1. Capacity Limit Gid - Concatenation of DOMAIN_NAME+"."+ CAPACITY_LIMIT_XID

2. Capacity Limit Xid – Combination of Service provider+Lane+Mode
3. Capacity Group Gid – Taken from Capacity Group
4. Equipment Type Gid – Taken from Equipment Type
5. X Lane Gid – Taken from X-lane
6. Time Period Type Gid – Period of Occurrence (Daily, Weekly…)
7. Effective Date – Date from when it is effective from
8. Expiration Date - Date on which it Expires
9. Limit – The actual capacity of an equipment that the service provider can provide
10. Domain Name - Default value is ‘ULF’ for India

9.17. Accessorial Code

Templates under accessorial code

 Accessorial code (One time setup).

 Accessorial cost
 Rate geo accessorial

ACCESSORIAL_COST
.csv
I. Create Accessorial cost.

Please see the attached template for accessorial cost setup in OTM system

In this template we will define the accessorial (fuel) cost.

ACCESSORIAL_COD
E.csv
II. Create Accessorial code.

Please see the attached template for accessorial code setup in OTM system.

a) Z514 is code for primary outbound (POB).

b) Z515 is code for direct dispatch (DD).
 RATE_GEO_ACCESS
ORIAL.csv
III. Create Rate Geo Accessorial.

Please see the attached template for rate geo accessorial setup in OTM system.

In this template we will link the accessorial (fuel) cost with associated rate record (base cost) for that particular
lane.