1.

Order Management and Master Data

Company
Code C710
Plant C710
TM10/
Slco TM20
Sales C710
DC 10
DIVISION 01
Shipping
Point C710

1.1.Organizational Structure

In TM we will map the org structure, as we have it in ECC. It is important to map the Org Unit

For Exp: Without, a Purchase order in TM Charge calculation will not work

Procedure: From SAP TM using

SPROTransportation ManagementMaster Data Organizational ManagementOrganizational ModelCreate

Organizational Model

Create Organizational Model

Org Unit_TM Org ID BP

C710_CO_COD
E 50000800 17094
C710_SA_ORG 50000802 17095
C710_PO_ORG 50000803 17096
Create and Merge Organizational Hierarchy

 Source system and the Org we have on the ECC side

 Select the company code, click on Expand to open sales offices and groups
 Same for Purchase Org
 Click on Execute
For Exp: in a Company code where we have multiple sales org

1.2.Business Partner
BP are all legal entities or individuals with whom a company maintains business contacts

 Vendors
 Customers
 Shipping Points and Plants
 Carriers’ Contact Person

Carrier contact create manual in TM

1.2.1. Adding carrier role

 BP 28010174 6103
1.2.2. Creating Carrier Contact Person
Carrier contact person user is necessary to be created in TM so that contact persons from Carrier can receive communication
from TM regarding tendering.

Hit the button Relationship

Select the contact person for In Relationship category field

Assign the number of the carrier with whom we want to create the relationship in \” RELATIONSHIP TO BO //

1.3.Define Transportation Service Level Codes

1.3.1. Used in Freight Unit

These service level codes correspond to the ECC shipping conditions. They will be used in the FU in TM

SPRO TM FO Define transportation service level codes

Define Transportation Service Level Codes

1.3.2. Used in Freight Order

In the Transportation service level codes customizing table used for FU, some additional values (C) have been entered to
reflect the loading type at the FO service level

SPRO TM FO Define transportation service level codes

Create New

1.3.3. Additional Customizing to enable service-level Activation

SPRO TM SCM Basis Master Data Define transportation service level codes

Note: this node is not available in HANA

 1.4.RESOURCES

Resources are objects that handle or Transport goods.

 The resource defines the working times and available capacities which is relevant to the planning of order dates
and execution.
 Transportation, loading, and unloading activities on freight units are performed based on resource data.
1.4.1. Define Calendar Resource:
The factory calendar defines which day is a working day, and which day is a non-working day. It usually refers to
wee-ends and public holidays as no-working days

SPRO Transportation Management Master Data Calendar Maintain Factory Calendar

Maintain Factory Calendar

Click on Display Button

And click on Definition you will see the validity period, the workdays, and the holiday calendar which can be defined by
following the same path
 1.4.2. Define Active Variant

The pre-requisite to defining calendar resources is to have an active variant defined. Capacity variants describe the
maximum capacity of the resource. You use capacity variants, for example, if you are working with multiple-shift
operations.

Note: the system a capacity variant into account only if you have defined it as an active variant in the resource
master data.

SPRO Transportation Management Master Data Resources Define Capacity Variants

Define Capacity Variants

1.4.3. Define Operating Hours

SAP Menu Logistics Transportation Management Master Data Resource /SCMTMS/RES01 –

Resource

/SCMTMS/RES01 – Resource

Create a Calendar resource with the resource type “Calendar Resource” this Calendar Resource will be used to set
up the operating times of the final customer’s locations.

One calendar resource per country was created with the following naming convention

CUSTOMER_CALENDARY_XY

DE04_CALENDAR

Location # C710/ Shipping point

Enter the name of the resource, the time zone of the location to which the resource will be assigned, the factory calendar for
the location, and the active variant that has been defined as pre-requisites.

Note: The factory Calendar should be set before in TM. The factory calendar defines the works and the non-workdays of the
resource.

Hit Definitions:
Define Shift under the Shift tab:

The shift is the operating hours in a day. For Exp 8 am to 5 pm

Define the Shift sequence under the shift sequence tab

Shift sequence combination of the different shifts if need be. In this case, one shift will be incorporated into one shift sequence
‘1’

Option “Can start on a non-Workdays” should be chosen on the non-workdays.

Go back to the previous screen and hit capacity variants. Under the capacity variant, we assign the pre-defined shift sequence
to our calendar resource. Therefore, single shift and shift sequence can be utilized for multiple calendar resources.

1.4.4. Assign Calendar Resource to Location

SAP Menu Logistics Transportation Management Master Data Transportation Network Location
/SCMTMS/LOC3 – Location

/SCMTMS/LOC3 – Location

Open the location in Change Mode for Which you want to assign the Calendar resource. Under the resource, the tab assigns
the calendar resource to the “Inbound operating times” fields and saves.

For the SP we have a calendar resources assignment.

 1.4.5. Define Vehicle Resource

Define means of Transport (MTR)

In TM Means of Transportation represent groups of Vehicle resources

Exp Container Ships or Cargo Ships and how the Physical Transportation B/W locations are executed, and the method of
transportation. You assign a means of transportation to each vehicle resource.

The Means of Transportation is also used to differentiate different planning requirements. For instance, dedicated means of
Transport have been created for a thermos.

SPRO Transportation Management Master Data Resources Means of Transport and Compartment Define Means
of Transport

Define Means of Transport

ROAD

OCEAN

SPRO Transportation Management Master Data Transportation Network Transportation Lane Distance and
Duration Determination Define GIS Zone
Define GIS Zone

SPRO Transportation Management Master Data Transportation Network Transportation Lane Distance and
Duration Determination Assign Country to GIS Zone

Distance and Duration Determination

SPRO Transportation Management Master Data Transportation Network Transportation Lane Distance and
Duration Determination

Define Service

SPRO Transportation Management Basic Functions Process Controller Define Service

Define Strategy

SPRO Transportation Management Basic Functions Process Controller Define Strategy

At that are not available the call will be done first on the postal code and then at the country level.

 YTLDD_CUST Strategy is calling the BRF+ table “YTTM_TRANSIT_TIME

 YTDDD_CUST Strategy assigns FTL, Express tank cases calculate the location for the GIS systems.

Define Strategy for Distance and Duration Determination and Geo-routing

SPRO TM Master Data Transportation Network Transportation Lane Distance and Duration Determination
Define Strategy for Distance and Duration Determination and Geo-routing
This is the strategy that will call the GIS system. 1 is the geocoding level on which we would like to retrieve the coordinates to
calculate the distance. If geo- coordinates

1.4.6. Define Vehicle Resource- Manual

A vehicle resource is an instance of a Particular means of Transportation that can provide transportation service and carry the
product. Each vehicle resource is assigned a means of transport, and you can define the capacity for the Vehicle resource.

DEFINE NEW ENTRIES FOR TRUCKLOAD Means of Transportation

/SCMTMS/RES01 – Resource

FTL # YTRUCK_24_FTL (ROAD)

LTL # YTRUCK_24_LTL (ROAD)

Note: Need to assign the Vehicle group & Vehicle type at # Define Equipment Groups and Equipment Types

If you create a new Means of Transportation, remember to assign the strategies for distance and duration determination in
SAP TM customizing.
Resource Class Truck needs to be selected from the list

Means of Transport should be populated with the appropriate means of transport.

Continuous Dim should be Mass and Volume

The factory calendar Should be populated with the relevant factory calendar based on the workdays / non-workdays

Capacity & until should be populated with the relevant capacity and the unit should consider the alternative quantity

The active variant Should remain empty

Then the General Tab completes the following Fields

Multi- resource Checkbox should be ticked together with the Unlimited no of Indiv Res Check box. This will allow this
resource to be used in several freight orders at the same time. When these checkboxes are not ticked the planner will get an
error message in the cockpit that the resource is already in use by a freight Order.

1.5.Transportation Network

A transportation network is used to display transportation network elements.

 Location
 Transportation zones
 Transportation lanes
 Transhipments Locations
 transhipments Location Chains
 Schedules

1.5.1. Locations
A location represents the place where goods are delivered, picked up, or transhipped.
Exp C710 (Locations we have Customers, Vendor, Plants, and Shipping points locations, which are not CIF from ECC
to EWM in Hana System)

/SCMTMS/LOC3 - Location

SAP Menu  Logistics  Transportation Management  Master Data  Transportation Network  Location
/SCMTMS/LOC3 - Location
Shipping point and Ship to party (BP)
 1.5.2. Transportation Zone

A transportation zone represents a group of locations, ZIP -codes, countries, or regions.

/SCMTMS/ZONE - Define Transportation Zones

SAP MenuLogistics Transportation Management Master Data Transportation NetworkTransportation

Zone/SCMTMS/ZONE - Define Transportation Zones

In the lower part specify which location, postal code, or region this zone is made.

1.5.3. Transportation Lanes

A transportation lane is defined as a route connecting two locations, a zone, or a combination of locations and zones for a
specific means of transport.

Create: /SCMTMS/TL5 - Define Transportation Lanes

SAP MenuLogisticsTransportation ManagementMaster Data/SCMTMS/TL5 - Define Transportation Lanes

Click on New create

Step-1 for each lane one by one add the relevant MTRs and define a validity period. Once this is done click on

Step -2 After you maintained the MTR, Double clicks on it, and in the section below, insert one by one all the carriers operating
on the lane for using the previously maintained truck.

Assign FTL and LTL Means of Transportation

Item level Assign Carrier’s

 Each lane has a start location and end location

 Means of Transportation can be defined within the Lane
 All the Means of Transportation available for a particular lane are defined here
 When we define the Means of Transportation, we define the validity dates and also define the duration and
distance calculation rules by checking the flags for fixed transportation. Duration and Fix transportation. Distance
and manually entering the distance and duration.
 Additionally, we clicked on the generate proposal the system generate the distance and duration according to the
distance and duration determination rules.
 Within the Means of Transportation, we can specify the kind of priorities, cost, and movement types we want to
use for that lane during carrier selection.
 For Each Means of Transportation within the lane, there is a set of carriers.
 The set of carriers serving each lane for a Means of Transportation can be maintained here. These carriers must be
defined in the location master.
 Within the carrier militance, we can maintain the start and end dates, carrier costs, priority and business share
rules for the carrier.
 1.6.Define Number Ranges

We need to maintain the number range for an automatic drawing of the correct number for the pre-defined document, such
as OTR/DTR (non-HANA) FU, FO, FSD, etc.

1.6.1. 2.1. Define the number range for OTR and DTR
SPRO Transportation Management Freight Order Management Define Number Range Intervals for Freight Order
Management

Define Number Range Intervals for Freight Order Management

1.6.2. 2.2. Define number range for FU and FO/FB

SPRO Transportation Management Freight Order Management Define Number Range Intervals for Freight
Order Management

1.6.3. 2.3. Define the number range for BP

SPRO Cross-Application Components SAP Business Partner Business Partner Basic SettingsNumber Ranges
and Groupings Define Number Ranges

1.6.4. Define Groupings and Assign Number Ranges

 1.7. Order and Delivery Integration (Hana not required)

OTR is the following business document in TM after the creation of ERP Sales Order or Purchase Order or STO Each TM
relevant ERP order type is mapped with one OTR type.

Prerequisites:

1.7.1. Define Order Type (OTR)

FUBR Freight unit Building rule condition

SPRO Transportation ManagementIntegrationLogistics IntegrationOrder-Based Transportation

RequirementDefine Order-Based Transportation Requirement Types

Order-Based Transportation Requirement-type

3 OTR types have been configuration

 YOT1-SO
 YOT2-STO
 YQT1- For Packed simulation Order

FUBRs and FUBR conditions are assigned:

1.7.2. Define OTR type Determination Condition

One Specific condition YT_OTR_DET_CON is used by the system to identify which TM OTR type needs to be created for any
ERP order Type.
1.7.3. Define DTR type

DTR is the following business Document in TM that offers the creation of ERP Delivery. Each TM relevant ERP delivery type
is to be mapped with a DTR type.

YDTI- Outbound Delivery

YDT2- Cross company Replenishment Del.

Assign to FUBR Condition

1.7.4. Define DTR type Determination Condition

One Specific condition YT_DTR_DET_CON (OR) MT_DTR_CONDITON_TYPE_01 is used by the system to identify
which TM OTR type needs to be created for any ERP order Type.
Hana Logistic Integration Configuration

Integration- Internal TM Component Integration

Define Control Keys for Document Integration

SPRO Transportation Management Integration Logistics Integration Internal TM Component Integration Define
Control Keys for Document Integration

0051 to 0064 Control keys

C710 For all Deliveries and Orders

Define Logistics Integration Profile

 Here Assign the

 FUBRs and FUBR Conditions

 And Select the Automatic FUBR
 Stage profile

Define Transportation-Relevance of Sales Documents

Define Transportation-Relevance of Purchasing Documents

1.8. FU, FO, FB Configuration

1.8.1. Define Freight Order Type

A freight order is an Order for which execution is planned by a carrier / Shipper. The FO contains FUs along with execution
data including dates.

SPRO TM FOFreight OrderDefine Freight Order Types

Click on new entries

Need to Create and Assign into FO type below requirements:

 Dangerous goods profile # YT_DG_00

 Delivery profile # YT_DLV_PF00
 EWM Integration Profile # Y001
 Application Object type # YT0DT40_T01
 Service level condition # YT_SRVLVL_000
 Output profile # /SCMTMS/TOR
 ADD Output Profile # YT_XPS_FO_FB
 Test Schema # YTM_FO
 Process setting # YT_PROCESS_SET_01
 Communication setting # YT_COMM_SET_00
 Determination Condition # YT_ORGUNIT_000
 Default Change Strategy # DEF_CHACO
 Save Strategy # CALC_CHARG
 Partner Determination Profile # YPD0

FO COST CHARGE FREIGHT

TYP SUBCONTRACTIN E DISTRIBUTIO CALCULATIO SETTLEMEN
E G M N N T SHIPMENT CREATION
YF0
1 * * * * * *
YF0
2 * * * * * *
1.8.2. Define Freight Booking Type

SPROTMFreight Order ManagementFreight BookingDefine Freight Booking Types

Freight book YFB1- Ocean and YFB2- Air

Need to be assigned and maintained below the requirement
 No range Interval # FI
 Transportation Mode Category # Sea and Mode # 03
 Condition for determination MTR # DE_CON_OCEAN_MTR
 Output profiles # /SCMTMS/TOR
 Text Schema # YTM_FO
 Purchase organization unit #
 Determination Rules Condition # YT_ORGUNIT_000
 Default FSD # Freight Settlement
 Dangerous Goods Profile # YT_DG_00
  Document Creation relevance# Shipment creation in SAP ERP
 Delivery Profile # YT_DLV_PF_00
 Application Object type # YTODT40_T01
 Default Change strategy # DEF_CHACO
 Creation Strategy # CARR_SEL
 Save Strategy CALC_CHARG
 Carrier Confirmation Required # select
 Partner Profile Determination # YP01
 Container Item Source # Container items are defined in Booking
 Goods Value aggregation # Goods Value are Aggregated
The same is applicable to AIR also

Freight bookings are relevant for:

COST CHARGE FREIGHT

FB SUBCONTRACTIN DISTRIBUTIO CALCULATIO SETTLEMEN SHIPMENT
TYPE G EM N N T CREATION
YFB1   * * * * *
YFB2   * * * * *

1.8.3. Define Freight Unit type

FU is used for the planning process and are the smallest shipment units in TM Multiple FUs can be combined into a single FOR
as a multi-stage shipment etc.

SPRO TM Planning  Freight UnitDefine Freight Unit Types

1.8.4. FU types Overview:

YAI1 – FU Air

YAI1/YFU1/YOCI/YPAI/YQFI/YROD

A pickup delivery time window condition is created and assigned to the FU types.
The Delivery window condition I assigned to the FU type and determine if the dates on the FU need to be filled, based on the
OTR/DTR dates. The dates on the FU are the following for both pick-up and Delivery.

 Acceptable start
 Requested start
 Requested ended
 Acceptable ended

Create Condition Fiori: YT_PUDLV_TIMEWND_CON

1.8.5. Define FU Determination Condition

One specific condition, ZFU_DET is used by the system to identify which FU type should be created for any OTR and DTR type.

1.9.Define FUBR

The FUBR is the next process step after the OTR/DTR document creation in TM.

It can be assigned to the OTR/DTR type in order to trigger the FU creation automatically or it can be run manually. The FUBR
will determine which FU type will be created. Furthermore, we can also specify split quantity rules whereby multiple FUs can
be created against a single OTR/DTR depending on request means of Transport, etc.

There can be one FUBR set for one OTR/DTR type or the rule FUBR to be used can be condition-based. As an example, we can
specify a condition-based.

As an example, we can specify a condition table that contains the FU types that are associated with specific OTR/DTR types.

Transaction Code # NWBC / /UI2/FLP - SAP Fiori Launchpad

Define Condition

FUBR

Freight Unit building Strategy:

Consolidation as much as possible: Items Could come from different transportation request / forwarding order.
These are grouped into FUs

Incapability Setting used in FUBR