Configuration Guide For Outsourced Transportation PDF

SAP Transportation Management
Configuration Guide for Outsourced Transportation
PUBLIC
Document Version: 3.0 – September 2012
Copyright
© Copyright 2012 SAP AG. All rights reserved.
SAP Library document classification: PUBLIC

No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be changed
without prior notice.
No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered
trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture,
Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC,
BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF,
Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are
trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered
trademarks of Adobe Systems Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems Inc.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide
Web Consortium, Massachusetts Institute of Technology.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina,
Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.
(C) SAP AG 2
IOS is a registered trademark of Cisco Systems Inc.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch,
BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are
trademarks or registered trademarks of Research in Motion Limited.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google
Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google
Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or
registered trademarks of Google Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG in Germany and other
countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks of
Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of
Crossgate AG in Germany and other countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies.
Data contained in this document serves informational purposes only. National product
specifications may vary.
(C) SAP AG 3
These materials are subject to change without notice. These materials are provided by SAP AG
and its affiliated companies ("SAP Group") for informational purposes only, without representation
or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to
the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any.
Nothing herein should be construed as constituting an additional warranty.
(C) SAP AG 4
Icons in Body Text
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Additional icons are used in SAP Library documentation to help you identify different types of
information at a glance. For more information, see Help on Help  General Information Classes
and Information Classes for Business Information Warehouse on the first page of any version of
SAP Library.
Typographic Conventions
Type Style Description
Example text Words or characters quoted from the screen. These include field names, screen
titles, pushbuttons labels, menu names, menu paths, and menu options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, graphic titles, and table titles.
EXAMPLE TEXT Technical names of system objects. These include report names, program
names, transaction codes, table names, and key concepts of a programming
language when they are surrounded by body text, for example, SELECT and
INCLUDE.
Example text Output on the screen. This includes file and directory names and their paths,
messages, names of variables and parameters, source text, and names of
installation, upgrade and database tools.
Example text Exact user entry. These are words or characters that you enter in the system
exactly as they appear in the documentation.
<Example text> Variable user entry. Angle brackets indicate that you replace these words and
characters with appropriate entries to make entries in the system.
EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.
(C) SAP AG 5
Table of Contents
Configuration Guide for Outsourced Transportation ....................................................................... 8
The Scenario ................................................................................................................................ 9
Before You Start......................................................................................................................... 11
Master Data................................................................................................................................ 13
Master Data in SAP Enterprise Resource Planning ............................................................... 14
Maintaining Organizational Objects .................................................................................... 15
Assigning Organizational Objects ....................................................................................... 17
Assigning Pricing Determination Procedures ..................................................................... 18
Assigning Shipping Points .................................................................................................. 19
Creating Customer Masters ................................................................................................ 20
Creating Vendor Masters .................................................................................................... 22
Defining Products ............................................................................................................... 24
Maintaining Price Conditions for Materials ......................................................................... 27
Master Data in SAP Transportation Management ................................................................. 28
Transferring Master Data from SAP ERP to SAP TM ........................................................ 29
Creating Integration Models ............................................................................................ 30
Activating Integration Models .......................................................................................... 33
Defining Organizational Units ............................................................................................. 35
Editing Locations ................................................................................................................ 41
Defining Transportation Zones ........................................................................................... 42
Maintaining Transportation Zone Hierarchies ..................................................................... 44
Defining Means of Transport .............................................................................................. 45
Defining Transportation Lanes............................................................................................ 46
Creating Contact Persons for Carriers ............................................................................... 48
Creating Business Partners for Shipping Points................................................................. 50
Configuration .............................................................................................................................. 51
Sales Order Management in SAP ERP .................................................................................. 52
Defining and Identifying Sales Orders ................................................................................ 53
Activating Transfer of Sales Documents ............................................................................ 54
Text Determination in Sales Orders ................................................................................... 55
Creating Output .................................................................................................................. 56
ERP Invoicing ......................................................................................................................... 57
Mapping Organizational Units............................................................................................. 58
Order-Based Transportation Requirements ........................................................................... 59
Defining Conditions for Quantity Tolerances ...................................................................... 60
(C) SAP AG 6
Defining Conditions for Change Controller Strategies ........................................................ 61
Defining Text Schemas....................................................................................................... 62
Assigning ERP Text Types to TM Text Types for OTR ...................................................... 63
Defining Service Levels ...................................................................................................... 64
Defining Freight Unit Building Rules ................................................................................... 65
Defining OTR Types ........................................................................................................... 67
Defining Conditions for OTR Type Determination .............................................................. 70
Creating Delivery Profiles ................................................................................................... 72
Defining Tendering Profiles ................................................................................................ 73
Defining General Settings for Tendering ............................................................................ 76
Defining Conditions for Incompatibilities ............................................................................. 80
Creating Incompatibilities.................................................................................................... 82
Configuring Incompatibility Settings ................................................................................... 84
Defining Carrier Selection Settings ..................................................................................... 85
Defining Freight Order Types ............................................................................................. 89
Defining Freight Settlement Document Types .................................................................... 96
Charge Management .............................................................................................................. 97
Defining Scales ................................................................................................................... 98
Defining Rate Tables ........................................................................................................ 100
Defining Calculation Sheets.............................................................................................. 106
Defining Freight Agreement Types ................................................................................... 110
Defining Freight Agreements ............................................................................................ 111
Defining Settlement Profiles ............................................................................................. 113
Defining Charge Calculation Profiles ................................................................................ 114
Configuring Organizational Settings for Charge Elements ............................................... 115
Transportation Allocation ......................................................................................................... 116
Defining Transportation Allocations ..................................................................................... 117
(C) SAP AG 7
Configuration Guide for Outsourced Transportation
About this Document
This configuration guide describes a scenario for Outsourced Transportation. You must
implement this scenario as described, and once you have verified the functionality, you can
modify the data to suit your own environment and operating conditions.
Change History
Version Date Description
1.0 December 2010 Initial release
Harmonized configuration and master data; scenarios based

1.1 April 2011
on IDES
Added chapter Defining Charge Calculation Profiles

2.0 July 2011
Updated chapter Configuring Organizational Settings for
Charge Elements
The following chapters have been updated form TM 9.0

setup:
 Editing Locations [Page 41]
 Defining OTR Types [Page 67]

3.0 September 2012
 Defining Freight Order Types [Page 89]
 Defining Rate Tables [Page 100]
 Configuring Organizational Settings for Charge

Elements [Page 115]
(C) SAP AG 8
The Scenario
This configuration guide explains how to configure the Outsourced Transportation scenario
manually.
If you want to configure the scenario automatically using Business Configuration Sets and similar
tools, see the information in the SAP Best Practices Quick Guide.
This scenario requires your SAP ERP system to be configured to run the following processes:
 SD: Order-to-cash process:
o Sales order entry
o Delivery creation
o Posting goods issue
o Billing document creation
o Transfer to accounting
 MM: Purchase order process
o Purchase order entry
o Posting goods receipt
o Invoice document creation (ERS settlement)
o Transfer to accounting
 FI/CO
o Supporting the processes listed above
o Country-specific legal requirements (such as tax calculation)
Geography
The Outsourced Transportation scenario assumes a transportation network in the United States
with a plant/shipping point in Chicago. To use the transportation network as described this
document, you must ensure that the plant used in the customer system is located in the same
vicinity.
The following organizational structures and document types are used by default and must be
adapted to customer-specific organizational structures as required:
Company code 3000
Controlling area 3000
Plant 3100
Storage location 0001
Shipping point 3100
(C) SAP AG 9
Sales organization 3000
Distribution channel 10
Division 00
Sales document type OTTL
More Information
For more information about the prerequisites for this scenario, see Before You Start [Page 11].
(C) SAP AG 10
Before You Start
Prerequisites
Before you start to configure the Outsourced Transportation scenario, you must have configured
the settings in the following guides in SAP Solution Manager under SAP Transportation
Management Configuration Structures Basic Settings for SAP TM 9.0 :
 Basic Settings and Integration for ERP
 Integration of SAP TM and SAP Event Management
 Output Management Configuration Guide
 Visual Business Configuration with SAP TM
 Basic Settings for SAP TM
Some settings in this guide can be copied from the existing SAP ERP configuration. In particular,
SAP ERP Customizing settings can be reused for the following:
 Enterprise structure definition and relevant assignments
 Financial Accounting
 Controlling
If you require a scenario-specific enterprise structure, we recommend that you copy the existing,
standard configuration settings (such as Country Template for Company Codes incl. G/L
Accounts) and change them as necessary (such as addresses).
Business system groups, logical systems, RFC connections, and system connections
used throughout this guide are examples only. Replace these with your own data.
This guide also assumes the use of Business Add-Ins (BAdIs), which add a prefix or suffix to
master data objects transferred from SAP ERP to SAP TM (see SAP Note 458914). An overview
of the prefixes and suffixes used is provided in the table below:
Business Object Prefix Suffix
Carrier CA– None
Customer CU– None
Plant PL– None
Shipping Point SP– None
Supplier SU– None
System None –@QV5750
Example:
(C) SAP AG 11
Shipping point name in SAP ERP: 3100
Shipping point name in SAP TM: SP3100@QV5750
If you have not implemented the corresponding BAdI in your system, the names of the objects are
not changed.
(C) SAP AG 12
Master Data
Master data is used throughout a number of business transactions in both SAP Enterprise
Resource Planning (ERP) and SAP Transportation Management (TM). Before you can start to
work with SAP Transportation Management, you must configure the master data accordingly.
For more information, see:
 Master Data in SAP Enterprise Resource Planning [Page 14]
 Master Data in SAP Transportation Management [Page 28]
(C) SAP AG 13
Master Data in SAP Enterprise Resource Planning
SAP Transportation Management (TM) is integrated into SAP Enterprise Resource Planning
(ERP), and so you must configure the settings in SAP ERP and enter master data. The following
procedures explain this process in more detail:
 Maintaining Organizational Objects [Page 15]
 Assigning Organizational Objects [Page 17]
 Assigning Pricing Determination Procedures [Page 18]
 Creating Customer Masters [Page 20]
 Creating Vendor Masters [Page 22]
 Defining Products [Page 24]
(C) SAP AG 14
Maintaining Organizational Objects
Procedure
1. In Customizing for SAP ERP, check that the organizational structure has been defined.
A sample structure is provided in the table below.
Organizational Object Value Navigation Path
Enterprise Structure
3000 Definition Financial
Company code Accounting Edit, Copy,
(currency USD) Delete, Check Company
Code
Definition Sales and
Sales organization 3000 Distribution Define, copy,
delete, check sales
organization
Distribution channel 10 Distribution
Define, copy, delete, check

distribution channel
Sales office 3000
Distribution Maintain Sales
Office
Sales group 300
Distribution Maintain Sales
Group
Definition Plant
Plant 3100 Maintenance Maintain
Maintenance Planning Plant
Definition Materials
Storage location 0001
Management Maintain
Storage Location
Shipping point 3100 Definition Logistics
Execution Define, Copy,
Delete, Check Shipping Point
(C) SAP AG 15
Organizational Object Value Navigation Path
Purchasing organization 3000
Management Maintain
Purchasing Organization
Purchasing group P01 Management Purchasing
Create Purchasing Groups
Definition Logistics -
Division 00
General Define, Copy,
Delete, Check Division
2. Assign these objects in enterprise structure. For more information, see Assigning
Organizational Objects [Page 17].
3. Check and assign the pricing procedure determination in SAP ERP for sales orders
based on the organizational structure above. For more information, see Assigning Pricing
Determination Procedures [Page 18].
(C) SAP AG 16
Assigning Organizational Objects
Once you have defined and checked your organizational objects, you must specify assignments
in the SAP ERP system.
Procedure
1. In Customizing for SAP ERP, choose SAP Customizing Implementation Guide
Enterprise Structure Assignment Logistics – General Assign Plant to Company
Code .
2. Enter the relevant information to assign your plant to your company code.

Enterprise Structure Assignment Sales and Distribution .
4. Maintain the following Customizing activities:
o Assign sales organization to company code
o Assign distribution channel to sales organization
o Assign division to sales organization
o Set up sales area
o Assign sales office to sales area
o Assign sales group to sales office
o Assign sales organization – distribution channel – plant

Enterprise Structure Assignment Materials Management .
6. Maintain the following Customizing activities:
o Assign purchasing organization to company code
o Assign purchasing organization to plant

Enterprise Structure Assignment Logistics Execution .
8. Maintain the Customizing activity Assign shipping point to plant.
(C) SAP AG 17
Assigning Pricing Determination Procedures
Procedure
1. Check and assign the pricing determination procedure in SAP ERP as specified below.
2. In Customizing for SAP ERP, choose SAP Customizing Implementation Guide Sales
and Distribution Basic Functions Pricing Pricing Control Define and Assign
Pricing Procedures Define Pricing Procedure Determination . Alternatively, enter
transaction OVKK in the command field.
3. Enter your data based on the following:
Field Description Value
SOrg. Sales organization 3000
DChl Distribution channel 10
Dv Division 00
DoPr Document procedure A
CuPP Customer pricing procedure 1
PriPr. Pricing procedure in pricing RVCXUS
CTyp Condition type PR00
(C) SAP AG 18
Assigning Shipping Points
Procedure
1. Assign a shipping point in Customizing for Logistics Execution under Shipping Basic
Shipping Functions Shipping Point and Goods Receiving Point Determination Assign
Shipping Points .
2. Create a new entry and enter the details contained in the following table:
Field Value
SC 01
LGrp 0001
Plnt 3100
PrShP 3100
(C) SAP AG 19
Creating Customer Masters
You must create customer masters in the SAP ERP system.
Procedure
1. On the SAP Easy Access screen, choose SAP menu Logistics Sales and
Distribution Master Data Business Partner Customer Create Total .
Alternatively, enter transaction XD01 in the command field.
2. To create the customer master, enter your data based on the following table:
Field Value
Account Group TM: Customer Account Group
Customer OT-CU-01
Company Code 3000
Sales Organization 3000
Distribution Channel 10
Division 00
3. Choose Continue and enter the following data:
Field Value
Shipping Conditions 01
Delivering Plant 3100
4. On the Sales tab page, enter your data based on the following table:
Field Value
Currency USD
Cust.pric.proc 1
Sales Office 3000
Sales Group 300
5. Choose the Billing Documents tab page and enter your data based on the following table:
Field Value
Incoterms FH
Terms of Payment 0002
Tax Classification Use 1 for U.S. states. Use 0 for other
(C) SAP AG 20
Field Value
countries.
6. On the Account Management tab page, in the Recon. Account field, enter 144003.
(C) SAP AG 21
Creating Vendor Masters
You must create vendor masters in the SAP ERP system.
Procedure
1. On the SAP Easy Access screen, choose SAP menu Logistics Logistics Execution
Master Data Partner Service Agent Create . Alternatively, enter transaction
XK01 in the command field.
2. Enter your data for the carriers based on the following table:
Vendor OT-CR-01 OT-CR-02 OT-CR-03 OT-CR-04
Company Code 3000 3000 3000 3000
Purchase Org 3000 3000 3000 3000
Account Group 0005 0005 0005 0005
3. Choose Enter.
4. On the Create Vendor: Address screen, enter your data based on the following table:
Fast
PGI Truck National Green
Name Trucking &
Lines Trucking Transport
Logistics
Search Term OT Carrier OT Carrier OT Carrier OT Carrier
Windgap Durand Spring Port Jersey

Street
Avenue Avenue Street Blvd
City Pittsburgh Trenton Reading Jersey City
Region PA NJ PA NJ
Ctry US US US US
Postal Code 15204 08611 19601 07305
Time Zone CST CST CST CST
5. Choose Next Screen or press F8 until you reach the Create Vendor: Accounting
Information Accounting screen.
6. Enter your data based on the following table:
Reconciliation
164003 164003 164003 164003
Account
(C) SAP AG 22
Cash
Management A1 A1 A1 A1
Group
7. Choose Next Screen or press F8 until you reach the Create Vendor: Purchasing Data
screen.
Order Currency USD USD USD USD
Terms of
0001 0001 0001 0001
Payment
GR-Based Inv.
Selected Selected Selected Selected
Verif.
Serv.-Based
Selected Selected Selected Selected
Inv. Ver.
9. Choose Next Screen or press F8 to open the Create Vendor: Partner Functions screen.
Partner
VN VN VN VN
Function
Number OT-CR-01 OT-CR-02 OT-CR-03 OT-CR-04
11. Save your entries.
(C) SAP AG 23
Defining Products
Procedure
1. On the SAP Easy Access screen of the SAP ERP system, choose SAP menu
Logistics Materials Management Material Master Material Create (General)
Immediately . Alternatively, enter transaction MM01 in the command field.
2. Enter your data based on the following:
o Material OT-PROD-01
o Industry sector Mechanical engineering
o Material type Semifinished product
o Storage location 0001
o Sales organization 3000
o Distribution channel 10
3. Choose Select View(s) and select the following views:
o Basic Data 1
o Sales: Sales Org. Data 1
o Sales: Sales Org. Data 2
o Sales: General/Plant Data
o Purchasing
4. On the Accounting 1 view, enter the following organizational levels:
o Plant 3100
o Storage location 0001
o Sales organization 3000
o Distribution channel 10
5. On the Basic Data 1 view:
Field Value
Material Group 001
Base Unit of Measure BAG
Gross Weight 100
Net Weight 95
(C) SAP AG 24
Field Value
Weight Unit LB
Volume 10
Volume Unit FT3
Matl Grp Pack.Matls 0002 or blank
6. On the Sales: Sales Org. Data 1 view, enter –1 as the tax classification for all assigned
countries.
7. On the Sales: Sales Org. Data 2 view:
Field Value
Item category group NORM
8. On the Sales: General/Plant Data view:
Field Value
Availability Check KP-no check
Trans. Grp 0001
LoadingGrp 0001
9. On the Purchasing view:
Field Value
Material Freight Grp 02
10. On the Accounting 1 view:
Field Value
Price Control S
Standard Price 100
Valuation Class 7900
Moving Price 100
After creating the material you need to make it available in your storage location.
Therefore follow the following steps:
1. In ERP, enter transaction MB1C.
2. Enter the following data:
(C) SAP AG 25
Field Value
Movement Type 561
Plant 3100
Storage Location 0001
3. Choose the Enter pushbutton.
4. On the Items screen enter the following data:
Item 1 Value
Material OT-PROD-01
Quantity 10000
UnE BAG
5. Choose the Enter pushbutton.
6. Choose the Enter pushbutton again (ignoring the warning message).
(C) SAP AG 26
Maintaining Price Conditions for Materials
Procedure
1. On the SAP Easy Access screen of the SAP ERP system, choose SAP Menu
Logistics Sales and Distribution Material Master Conditions Select (Using
Condition Type) Create . Alternatively, enter transaction VK11 in the command field.
2. Enter condition type PR00 and choose enter.
3. Select key combination Material with release Status.
4. Enter the following header data:
o Sales Organization: 3000
o Distribution Channel: 10
5. Enter the following item data:
o Material: OT-PROD-01
o Amount: 100
o Unit: USD
o Per: 1
o UoM: BAG
o Calculation Rule: C
(C) SAP AG 27
Master Data in SAP Transportation Management
Since this scenario setup assumes that SAP Transportation Management (TM) is connected to
SAP Enterprise Resource Planning (ERP), some data such as plants and customers must be
transferred to SAP TM from SAP ERP.
The following processes explain how to enter and maintain the remaining data:
 Defining Means of Transport [Page 45]
 Defining Transportation Lanes [Page 46]
 Creating Contact Persons for Carriers [Page 48]
(C) SAP AG 28
Transferring Master Data from SAP ERP to SAP TM
Procedure
1. Transfer the following data from SAP ERP to SAP Transportation Management (SAP
TM):
Field Value
Shipping Point 3100
Customer code (in SAP ERP and SAP TM) OT-CU-01
OT-CR-02
OT-CR-02
Carrier code (in SAP ERP and SAP TM)
OT-CR-03
OT-CR-04
Materials OT-PROD-01
For more information about transferring data from SAP ERP to SAP TM, see Integration
of SAP TM with SAP ERP. In particular, pay attention to the information regarding
selecting an integration model
(C) SAP AG 29
Creating Integration Models
In this procedure, you create integration models, which specify which data objects are to be
selected from the total dataset in SAP ERP for the transfer to SAP TM. You do not need all
available master data and transaction data in SAP ERP for planning in SAP TM.
To create the integration model, first mark the object types (for example, customer masters) to be
selected on the Create Integration Model selection screen. Next, you select specific selection
criteria that further restrict the object types you have already selected.
For this scenario you need to transfer the following master data types from SAP ERP to SAP TM:
 Customer master
 Carriers
 Shipping point
 Plant
The transfer of transaction data is not required.
In SAP TM, you create business partners and/or locations based on the settings when activating
the integration models (see Activating Integration Models [Page 33]).
Working with Variants

Since the system does not save the selection options you make when creating an integration
model, you have to save the settings as a variant on the selection screen. By working with
variants you can reuse the settings you have saved whenever you want. If you want to re-create
an integration model at a later point in time, you can call up the required variant by choosing the
Select Variant symbol in the toolbar at the top of the selection screen.
Integration Model Versions

If you regenerate an integration model, the system automatically generates a new version of this
model. Different versions of an integration model are distinguished by their date and time of
creation, as well as by the filter objects that they contain. You can create as many versions of an
integration model as you wish. However, only one version may be active at one time.
Changing an Integration Model

We recommend that you change an existing variant of the integration model, generate a new
version using transaction CFM1, and then delete the variant.
Structure of an Integration Model

The structure of an integration model influences performance. When it integrates transaction
data, the system checks whether the data concerned is contained in the active integration model.
At the same time, the system loads and interprets all active integration models for the object type
concerned to determine any target systems that may be affected. The greater the number of
integration models per object type, the longer the runtime for the determination for target
systems.
(C) SAP AG 30
For performance reasons, we recommend that you use only one object type for each
integration model.
Prerequisites
You have completed the Customizing and default settings for integration in both SAP TM and
SAP ERP.
You have maintained the relationship between the source and target system in both systems.
Procedure
Create Integration Model for Customers
1. On the SAP Easy Access screen for SAP ERP, choose Logistics Central Functions
Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer
Integration Model Create CFM1 .
2. Define an integration model with the following data:
Model Name Logical System APO Application
Logical system of the target

TM System as defined in Core
OT-IM-001 TM MD
Interface Settings in SAP ERP
(for example, B1TCLNT910).
3. In the Material Independent Objects screen area, activate the indicator Customers,
Vendors and Shipping points.
4. Choose the Special Restrictions for each object and enter the master data relevant for
your scenario:
Selection Object Special Restriction Objects Create Loc./BP
Customers OT-CU-01 2
OT-CR-01
OT-CR-02
Vendors 1
OT-CR-03
OT-CR-04
Shipping points 3100 None
Plant 1200 None
5. Choose Execute to close the special restriction screen.
6. Save the Create Integration Model screen to create a selection variant for your
integration model.
7. Name the variant OT-IM-001, description OT – MD for OT Scenario.
(C) SAP AG 31
8. Choose Execute to create the integration model.
9. Choose Generate IM.
10. Choose Back.
(C) SAP AG 32
Activating Integration Models
In this procedure, you activate integration models.
Activating an integration model causes an initial transfer of master data from SAP ERP to SAP
TM. The integration models to be activated are compared with the integration models that are
already active. In this way, the transfer restricts itself to differences. In other words, the system
transfers only data for filter objects that are not contained in any active integration models.
To transfer all data records again, you have to deactivate and then reactivate all active integration
models.
When activating the integration model, you must define whether you want to create a business
partner, a business partner and a location, or only a location in SAP TM. Business partners are
necessary for the commercial part of the business, whereas locations are necessary for planning
and executing transportation. This means that whenever cargo needs to be picked up or
delivered, a location is necessary. In this scenario, you create business partners and locations for
the customers. Since the carriers are external, you only create business partners. If the distances
and transportation times from the depot of the carrier are important, then you need to create a
location for the carrier.
Procedure
Activate Integration Model for Customers
1. On the SAP Easy Access screen for SAP ERP, choose Logistics Central Functions
Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer
Integration Model Activate CFM2 .
2. Make the following settings:
Field Selection Value Remark
Model OT-IM-001 None
Logical system of the target

SAP TM System as defined in
Logical System Logic System
Core Interface Settings in
SAP ERP.
APO Application TM-MD None
3. Choose Execute.
The selection screen displays the available integration models for the model name you
have specified.
Versions: If several integration models exist with the same name, they are displayed in
chronological order (according to date and time).
4. Activate the required model by double-clicking it or by choosing the Active/Inactive

pushbutton.
An OK icon displayed to the left of the model generation date and time shows that the
integration model has been activated.
(C) SAP AG 33
If you want to deactivate the integration model, repeat the above procedure and ensure
that the OK icon is no longer displayed.
5. Choose the Start pushbutton to begin the data transfer.
The system transfers the data in the background.
6. You can use the Check pushbutton to carry out a consistency check on the status of the
integration model.
The system tests all active models, including those models scheduled for activation, but
excluding those models scheduled for deactivation.
(C) SAP AG 34
Defining Organizational Units
Organizational units (purchasing organizations and purchasing groups) are used when a freight
order is created.
The following organizational units have to be created in SAP TM:
 Sales Organization
 Sales Group
 Purchasing Organization
 Purchasing Group
 Planning & Execution Organization
 Planning & Execution Group
You can also transfer organizational units from SAP ERP to SAP TM using transaction
/SCMTMS/ORG_INT. As this scenario makes use of order integration and invoice
integration, it is recommended to use this automatic integration approach.
Procedure
1. On the SAP Easy Access screen, choose or enter transaction /scmtms/org_int in the
command field.
2. Enter the following data:
Field Value
<logical system name of your ERP

Source System
system>
Company Code 3000
Sales Organization 3000
Purchase Organization 3000
1. On the SAP Easy Access screen, choose SAP menu Master Data Organization
Create Organization and Staffing or enter transaction PPOCE in the command field.
2. When prompted, enter the validity dates for the organizational unit.
3. On the following screen, enter your data based on the following tables.
On the Basic Data tab page:
Organizational Unit Specifies the organizational OT-PORG-1
(C) SAP AG 35
unit to be created
OT: Purchasing
Description Description
Organization
On the Org. Data tab page:
<Organizational unit
Organizational unit ID. This is
Org. ID that you previously
an internal number. defined>
Specifies the type of

Org. Unit Function 2 - Purchasing
organizational unit
Specifies the role of the

Org. Unit Role 1 - Organization
organizational unit
On the Address tab page:
Subtype Defines the type of address Main Address
Street Street in the address Industrial Parkway
City City in the address Philadelphia
Postal Code Postal code of the address 19088
Country Country of the address U.S.
5. Repeat the procedure to create a purchasing group:
Specifies the organizational

Organizational Unit “OT-PGRP-1”
unit to be created
Description Description OT:Purchasing Group
Org. Unit Function Specifies the type of 2 - Purchasing
(C) SAP AG 36
organizational unit

Org. Unit Role 3 - Group
organizational unit
Street Street in the address Industrial Parkway
Postal Code Postal code of the address 19088
Create sales organization and group
Specifies the organizational OT-SORG-1

Organizational Unit
unit to be created
Description Description OT: Sales Organization
an internal number defined>

Org. Unit Function 4 – Sales
organizational unit

Org. Unit Role 1 – Organization
organizational unit
(C) SAP AG 37
Specifies the organizational OT-SGRP-1

Organizational Unit
unit to be created
Description Description OT:Sales Group
an internal number.
defined>

Org. Unit Function 4 – Sales
organizational unit

Org. Unit Role 3 – Group
organizational unit
10. Create planning and execution organization and group
Specifies the organizational OT-PEORG-1

Organizational Unit
unit to be created
OT: Planning &

Organization
Organizational unit ID. This is <Organizational unit

Org. ID
an internal number. that you previously
(C) SAP AG 38
defined>
Unit Function Specifies the

Org. 13 – Planning and Execution
type of organizational unit

Org. Unit Role 1 – Organization
organizational unit
Specifies the organizational OT-PGRP-1

Organizational Unit
unit to be created
OT: Planning &

Description Description Execution Group

Org. Unit Function 13 – Planning & Execution
organizational unit

Org. Unit Role 3 – Group
organizational unit
(C) SAP AG 39
Result
You have defined a purchasing organization and group, sales organization and group, planning
and execution organization and group.
(C) SAP AG 40
Editing Locations
Procedure
1. Refine the geographical coordinates of the following locations in case IGS is not used.
On the SAP Easy Access screen for SAP TM, choose Transportation Management
Master Data Transportation Network Locations Define Location .
2. Enter the respective location and choose the Change pushbutton.
3. On the General Data tab page enter the following coordinates:
Location Longitude Latitude
SP3100@ <logical system> -87,59,59 +41,59,59
CUOT-CU-01@ <logical
-122,19,48 +47,59,59
system>
(C) SAP AG 41
Defining Transportation Zones
Procedure
1. Create a zone in SAP Transportation Management. To do so, open the SAP Easy
Access screen and choose SAP menu Master Data Transportation Network
Transportation Zones Define Transportation Zone . Alternatively, enter transaction
/SCMTMS/ZONE in the command field.
2. Choose Create and enter the following data:
Field Value
Zone OT-US
Zone Type M
Description OT US Zone
3. On the Zone Region tab page add the following country key: US.
5. Create OT-US-MIDWEST zone in the header area and modify it as follows:
Country Key Country Name Region Region Name
US USA IA Iowa
US USA IL Illinois
US USA IN Indiana
US USA MI Michigan
US USA MN Minnesota
US USA ND North Dakota
US USA NE Nebraska
US USA OH Ohio
US USA SD South Dakota
US USA WI Wisconsin
6. Choose the Calculate Coordinates pushbutton.
8. Create the zone OT-US-WEST in the header area, and on the Zone-Region tab, modify it
as follows:
(C) SAP AG 42
US USA CA California
US USA ID Idaho
US USA NV Nevada
US USA OR Oregon
US USA WA Washington
9. Choose the Calculate Coordinates pushbutton.
(C) SAP AG 43
Maintaining Transportation Zone Hierarchies
You must maintain a transportation zones hierarchy to organize your locations in such a way that
you can run vehicles from the start location to the destination location via hubs, ports or
transshipment locations. Furthermore, if you do not maintain the transportation zone hierarchy
correctly, you are not able to preselect the right vehicles as defined in your planning profile.
You create the transportation zone hierarchy with the following data:
Hierarchy Has as subordinate
RELH_ZONE OT-US
OT-US-MIDWEST
OT-US
OT-US-WEST
Procedure
1. On the SAP Easy Access screen for SAP TM, choose Transportation Management
Master Data Transportation Network Transportation Zones Define Transportation
Zone Hierarchy .
2. In the Hierarchy group box, enter RELH_ZONE in the Name field.
3. In the Hierarchy Structure group box, enter RELHS_ZONE in the Name field.
4. Choose the Change pushbutton.
5. In the lower screen area, in the hierarchy tree, double-click RELH_ZONE.
6. In the Hierarchy Fast Entry group box on the top right-hand side of the screen,
RELH_ZONE appears in Hierarchy Node field.
7. Enter OT-US in the Transportation Zone column.
8. Save your entries and agree to update hierarchy tree.
9. In the lower screen area, the updated hierarchy tree, double-click OT-US.
10. In the Hierarchy Fast Entry group box on the top right-hand side of the screen, OT-US
appears in the Hierarchy Node field,
11. Make the following entries in the Transportation Zone column:
o OT-US-MIDWEST
o OT-US-WEST
12. Save your entries and agree to update hierarchy tree.
(C) SAP AG 44
Defining Means of Transport
Procedure
You define the means of transport in Customizing for SAP Transportation Management.
1. Choose SAP Customizing Implementation Guide SAP Transportation Management

Transportation Management Master Data Resources Define Means of Transport
.
2. Choose New Entries and enter your data based on the following table:
Field Value
Means of Trans. OT-FTL
MTr Description Full Truckload Trailer
Transp. Mode 01 – Road
Multiresource Selected
No. of Indiv. Res. 999
Average Speed 70,000
Distance Factor 1,000
(C) SAP AG 45
Defining Transportation Lanes
Procedure
1. On the SAP Easy Access screen for SAP Transportation Management, choose SAP
menu Master Data Transportation Network Transportation Lanes Define
Transportation Lane or enter transaction /SAPAPO/SCC_TL5 in the command field.
2. Define your lanes based on the following table:
Start Location/Zone SP3100@<logical system>
Destination Location/Zone OT-US-WEST
3. On the Means of Transport screen create new entries. Enter the following data in the
dialog:
Field Value
Means of Transport OT-FTL
Start Date Today
End Date 3000–12–31
Fix Transp. Duration Deselected
Trsp. Duration N/A (determined by the system)
Transptn Distance Deselected
Trsp. Dist. N/A (determined by the system)
Mns of Trsp. Costs 0.932
Relevant to Carrier Selection Selected
Use Business Share Deselected
Use Trsp. Allocations Deselected
Cost Origin I – Internal Costs
Strategy for TSP Selection X – Neither Costs Nor Priority
4. Mark the means of transport line and create the following new entries on the Carrier
screen:
BP Number OT-CR-01 OT-CR-02 OT-CR-03 OT-CR-04
Means of
OT_FTL OT_FTL OT_FTL OT_FTL
Transportation
Start Date 2000–01–01 2000–01–01 2000–01–01 2000–01–01
(C) SAP AG 46
End Date 2099–12–31 2099–12–31 2099–12–31 2099–12–31
Use TCM costs Use TCM costs Use TCM costs Use TCM costs
Transportation (when the (when the (when the (when the
Costs maintained value maintained value maintained value maintained value
is 0.0) is 0.0) is 0.0) is 0.0)
Priority 1 2 3 4
TM Tendering:
Consider TSP
X Blank X Blank
for P2P
Tendering
TM Tendering:
Consider TSP
Blank X Blank X
for Broadcast
Tendering
(C) SAP AG 47
Creating Contact Persons for Carriers
Procedure
1. On the SAP Easy Access screen, choose SAP menu Master Data General
Define Business Partner or enter transaction BP in the command field.
2. Create your business partners based on the following tables.
Create the Business Partner (General) role:
Field Value
BP OT-CP-01 (external Number Assignment)
First name PGI Truck Lines
Last name OT-CP-01
Correspondence lang. EN
Street / House Number Windgap Ave 16
Postal Code 15204
City Pittsburgh
Country U.S.
Region PA
US cell phone number (ensure that the SMS-

Enab. checkbox is selected. To display the
Mobile Phone (optional)
checkbox, choose the arrow icon next to the
mobile phone field.)
E-mail ID of the carrier contact person. This is

important since RFQ correspondence is sent
E-Mail
to this e-mail address during the tendering
process.
Standard Comm. Method INT e-mail
3. Create the Contact Person and Internet User roles for the same contact person.
4. On the Internet User tab page, enter your data based on the following table:
Field Value
Internet User OT-CP-01
User name OT-CP-01
Password initial
(C) SAP AG 48
Field Value
Role /SCMTMS/SERVICE_PROVIDER
Logon language EN
5. Choose Relationships
1. Choose Relationships Category: Is Contact person for.
2. In the Relationship to BP field, enter OT-CR-01.
3. Choose Create.
4. Choose Save.
6. Maintain the other contact persons for your carriers. These are:
Contact Person Carrier
OT-CP-02 US-CR-02
OT-CP-03 US-CR-03
OT-CP-04 US-CR-04
(C) SAP AG 49
Creating Business Partners for Shipping Points
If a GeoServer is not installed, business partners for the shipping points are not automatically
generated by transferring master data from SAP ERP to SAP TM. If a business partner is not
assigned to the transferred location, you have to create and assign a business partner manually.
Procedure
1. On the SAP Easy Access screen, choose SAP menu Master Data General
Define Business Partner . Alternatively, you can enter transaction BP in the command
field.
2. Create your business partners based on the following Business Partner (General) role:
OT-SP-3100 - BP for Shipping Point.
4. On the SAP Easy Access screen, choose SAP menu Master Data Transportation
Network Define Locations .
5. Enter Location SP3100@<logical system>.
6. Select Change.
7. On the General tab page in the Partner screen enter BP number OT-SP-3100.
(C) SAP AG 50
Configuration
This section provides information about the settings that you must configure in both Customizing
(transaction SPRO) and the SAP NetWeaver Business Client. For more information about the
configuration settings that are required, see:
 Sales Order Management [Page 52]
 ERP Invoicing [Page 57]
 Order-Based Transportation Requirements [Page 59]
 Charge Management [Page 97]
(C) SAP AG 51
Sales Order Management in SAP ERP
You configure sales order management in your SAP Enterprise Resource Planning (ERP)
system. For more information about the configuration settings that are required for sales order
management, see:
 Defining and Identifying Sales Orders [Page 53]
 Activating Transfer of Sales Documents [Page 54]
 Text Determination in Sales Orders [Page 55]
 Creating Output [Page 56]
(C) SAP AG 52
Defining and Identifying Sales Orders
There are two ways in which you can use this integration procedure:
 Use an existing sales order type
 Create a new sales order type
In the standard SAP system, scenarios usually include a standard sales order type (order type
OR) or a rush order (order type RO).
Procedure
and Distribution Sales Sales Documents Sales Document Header Define Sales
Document Types . Alternatively, enter transaction VOV8 in the command field.
2. Copy order type OR to new order type OTTL and retain all of the field values.
3. Choose Copy (enter) and confirm the Dependent entries for copying control dialog box.
4. Save your settings.
5. Choose Back (F3).
Result
You have created order type OTTL.
(C) SAP AG 53
Activating Transfer of Sales Documents
In this Customizing activity, you activate the transfer of sales documents to an external
transportation management system (TMS) by assigning a control key to the necessary sales
document types. The sales documents can be sales orders or returns orders. The control key
determines whether a sales document and the corresponding outbound delivery are transferred
to an external TMS, and also whether sales order scheduling is to be carried out in SAP ERP or
in the external TMS.
When you create a sales document for which the transfer has been activated, the system assigns
the control key to the sales document (parameter TM_CONTROL_KEY) and to all relevant
documents in the document chain (for example, the outbound delivery). This is a fixed parameter
that cannot be subsequently changed in the sales document.
Procedure
Integration with Other SAP Components Transportation Management Order
Integration Activate Transfer of Sales Documents .
2. On the Sales Document Transfer screen, enter your data based on the following table:
SOrg. Applicable sales organization 3000
Applicable distribution 10
DChl
channel
Dv Applicable division 00
Sales order type required to

SaTy OTTL
integrate the TM system
SC Shipping conditions 01
Ctrl Key Control key 0001
Client number of the target <custom 4-digit code>

TM No. TM system (consult with your
(for example, B750)
Basis expert)
Result
The order type is now activated and can be integrated with the TM system.
(C) SAP AG 54
Text Determination in Sales Orders
Procedure
and Distribution Basic Functions Text Control Define Text Types or enter
transaction VOTXN in the command field.
2. Select the Header checkbox for the Sales Document.
3. Choose Text Types.
4. Enter text type TM01 and description Driver Text.
5. Choose Save.
7. Select the Header checkbox for the Sales Document and choose Change to add the new
text type to the text procedure.
8. Select text procedure 01.
9. In the tree menu on the left, double-click Text IDs in Text Procedure.
10. Choose New Entries.
11. Enter the correct sequence number and the text type created in step 4 (TM01).
In accordance with the current

SeqNo Sequence number
sequencing
ID Identification TM01
Refer/Duplicate Reference Deselected
Text is obligat. Text is obligatory Text is not obligatory
Access seq. Access sequence 1
(C) SAP AG 55
Creating Output
Procedure
1. On the SAP Easy Access screen, choose SAP menu Logistics Materials
Management Purchasing Master Data Subsequent Settlement Customer Rebate
Arrangements Environment Customer Messages Sales Document Create .
Alternatively, enter transaction VV11 in the command field.
2. In the Output Type field, specify the type of output that is to be produced. In our scenario,
the output type is TRS0.
3. Choose Enter.
Field Value Description
SalesDocTy OTTL Sales document type
Medium 8 Special function
Send immediately (when

Date/Time 4
saving the application)
EN Language in which the output

Language
is to be produced
(C) SAP AG 56
ERP Invoicing
(C) SAP AG 57
Mapping Organizational Units
Procedure
Integration with Other SAP Components Transportation Management Invoice
Integration Invoicing Mapping of Organizational Units Assign Organizational Units
for Purchasing .
3. Enter the data based on the following table:
Field Value
<Logical name of the connected TM

Logical System
system>
<Number of purchasing organization

TM Pur. Organization
/ OT-PORG-1>
<Number purchasing group / OT-

TM Purchasing Group
PGRP-1>
Purchasing Org. 3000
Purch. Group P01
Plant 3100
Company Code 3000
(C) SAP AG 58
Order-Based Transportation Requirements
You configure the settings for order-based transportation requirements (OTR) in your SAP
Transportation Management system.
For more information, see the process descriptions below.
(C) SAP AG 59
Defining Conditions for Quantity Tolerances
Procedure
1. On the SAP Easy Access screen, call transaction NWBC to open the SAP NetWeaver
Business Client.
2. Choose Application Administration General Settings Conditions Create Condition

.
3. In the Condition Type field, enter /SCMTMS/CC_QUAN_TOL.
4. Choose Continue.
5. On the New Condition Definition screen, enter your data based on the following table:
Field Value
Condition OT_QTOL_01
Description Quantity Tolerance for OT Scenario
6. On the Data Access Definition tab page, choose Create.
7. In the Data Access Definition for Conditions column, enter /SCMTMS/TORQTYCHGWEI.
8. Choose the Decision Table tab page.
9. Choose Insert New Row.
10. In the Weight Chg column, click the icon and choose Direct Value Input.
11. Use the comparison options dropdown box to create a row whereby:
Greater than 4,000 or less than -4,000 is true.
12. Repeat the process to insert a row whereby:
Between -4,000 and 4,000 is false. Save your entries.
(C) SAP AG 60
Defining Conditions for Change Controller
Strategies
Procedure
1. On the SAP Easy Access screen, call transaction NWBC to open SAP NetWeaver
Business Client.

.
3. On the New Condition Definition screen, enter your data based on the following table:
Field Value
Condition OT-CSDC-01
OT: Condition for Change

Description
Controller Strategy
Condition Type /SCMTMS/CC_TOR_STRAT
Origin of Condition Condition based on BRFplus Decision Table
4. Choose Continue.
5. Choose Data Access Definition.
6. In the Data Access Definition for Conditions column, enter /SCMTMS/TOR_QUAN_UPD.
7. On the Decision Table tab page, choose Insert New Row.
Field Value Comment
If quantity change is equal to

Qty Change True “X”, return value is true;
otherwise it is false
CC Strat. Start tend CC Strat: START TEND
(C) SAP AG 61
Defining Text Schemas
Procedure
1. In Customizing for SAP Transportation Management, choose SAP Customizing
Implementation Guide Cross-Application Components Processes and Tools for
Enterprise Applications Reusable Objects and Functions for BOPF Environment
Dependent Object Text Collection Maintain Text Schema .
2. Double-click Text Type in the navigation tree and enter your data based on the following
table:
Field Value
Text Type TM01
Description Driver Notes
3. Double-click Text Schema in the navigation tree and enter your data based on the
following table:
Field Value
Txt Schema OT0001
Description Text schema for OT
4. Select the entry that you created in step 3 and double-click Text Type to Text Schema
Assignment in the navigation tree.
Field Value
Text Type TM01 and A0001
Mandatory Deselected
Internal Deselected
Lang. Text Deselected
6. Double-click Assign Text Schema to BO and Node in the navigation tree and enter your
data based on the following table:
Business Object Name Node Name Txt Schema
/SCMTMS/TOR ROOT OT0001
/SCMTMS/TOR TENDERING OT0001
/SCMTMS/TRQ ROOT OT0001
(C) SAP AG 62
Assigning ERP Text Types to TM Text Types for OTR
Procedure
Implementation Guide SAP Transportation Management Transportation Management
Integration ERP Logistics Integration Order-Based Transportation Requirement
Assign ERP Text Types to TM Text Types for OTR .
ERP Doc. ERP document Sales Document Header
ERP Text ERP text TM01
TM Text TM text TM01
Not TM-Rel Not relevant to TM Deselected
(C) SAP AG 63
Defining Service Levels
Procedure
1. In Customizing for Transportation Management, choose Forwarding Order
Management Define Transportation Service Level Codes .
Field Value
Service Level Code TM
Description TM Service Level
(C) SAP AG 64
Defining Freight Unit Building Rules
The freight unit building rule (FUBR) is assigned and applied at the level of the OTR type. It
specifies how freight units are to be built when the OTR is created.
Prerequisites
 You have defined an OTR type.
 You have assigned the OTR document type to the freight unit building rule.
Procedure
1. On the SAP Easy Access screen, call transaction NWBC to open the SAP Business Client.
2. Choose Application Administration Planning General Settings Freight Unit

Building Rule Create Freight Unit Building Rule .
3. On the New Freight Unit Building Rule screen, enter your data based on the following
tables:
On the General Data tab page:
Specifies the FUBR to be

Freight Unit Building Rule OT_FUBR_01
created
OT: Freight Unit

Description Description of the FUBR
Building Rule
Document Type Freight order type OTTL
Specifies how consolidation is Consolidate per Request

Freight Unit Building Strategy
carried out (Compatible parts)
Process Controller Strategy Strategy that defines how to FUB_AUTO

(Advanced Settings tab page) build FUs
Incompatibility Settings Not used Blank
Defines the weight/volume

Critical Quantity Gross Weight
limits for the freight unit
Indicator that specifies

whether item quantities can
Item Split Allowed Selected
be split across different freight
units
On the Planning Quantities tab page:
Field Description Row 1 Row 2 Row 3
Planning Specifies the

Quantity for parameter for Gross Weight Gross Volume Pieces
Freight Unit the planning
(C) SAP AG 65
Field Description Row 1 Row 2 Row 3
Building quantity
Unit of Measure
Unit of measure LB FT3 BAG
of Split Quantity
Quantity limit for

the item that
Split Quantity forms the basis 40,000 0 0
for building
freight weights
Rounding Any rounding

1 1 1
Quantity quantity applied
Result
You have created a freight unit building rule.
(C) SAP AG 66
Defining OTR Types
Order-based transportation requirements (OTR) that are received from SAP ERP are mapped
using OTR document types.
Prerequisites
You have defined a freight unit building rule or intend to do so.
Procedure
Integration ERP Logistics Integration Order-Based Transportation Requirement
Define Order-Based Transportation Requirement Types .
2. On the Order-Based Transportation Requirement Types: Overview screen, choose New

Entries.
3. Enter the necessary data based on the following tables.
In the header area:
OTR Type ID of the OTR document type OTTL
Description of the OTR type to Truck Load Order

Description
be defined
Only one OTR type can be

defined as the default OTR
Default Type type. Select this checkbox if Deselected
there is only one OTR type
defined in the system.
In the Number Range Settings screen area:
Number range used to assign

the numbers to the OTR
Number Range Interval 02
types. We use the number
range as indicated.
In the Process Control / Business Object Mode screen area:
Indicates whether the

BW Relevance document type is relevant for Selected
BW
Automatic Freight Unit Indicates whether the freight

units are built automatically. If Selected
Building
you select this checkbox, you
(C) SAP AG 67
must specify an FU building
rule.
Indicates that the approval

Enable Approval Workflow Deselected
workflow is activated.
Specifies whether the

business documents of
forwarding order management
Automatic Block are blocked automatically. Deselected
Only special creation
channels are taken into
consideration.
Specifies that changes are to

Track Changes Selected
be tracked
EM Integration Active Selected
Logical system of the EM

Event Manager
system.
Specifies the object that is to

EM Web Interface
be processed in SAP Event ODT20_FU
Transaction
Management
Retention period (in days)

Retention Period 30
before archiving
Print profile used for this

Output Profile /SCMTMS/TRQ_FWO_PRINT
document type
Add. Output Profile Additional output profile Blank
Specifies how information is

to be transferred if changes B – Synchronous Propagation
Propagate Changes are made to the document of Changes, Fallback to
(such as changes to Asynchronous
quantities, and so on)
In the Default Values screen area:
Default unit of measure for the

Default Weight UoM LB
weight for this document type
Default unit of measure for the FT3

Default Volume UoM
volume for this document type
Planning indicator that

specifies the quantities 01 – Plan on Requested
Plan on Req/Cnf Qty
(planned or confirmed) to be Quantities
taken into account during
(C) SAP AG 68
planning
Specifies the planning profile

that is used by the system
when performing planning
Planning Profile runs and creating Blank
transportation proposals for
business documents of this
type
Rule used when building

freight units (if the Autom. FU
Building checkbox is selected)
Freight Unit Building Rule OT_FUBR_01
For information about defining
the FUB rule, see Defining
Freight Unit Building Rules.
[Page 65]
You can specify a condition

for determining a freight unit
building rule that is used when
FU Building Rule Condition None
freight units are created for
business documents of this
type.
(C) SAP AG 69
Defining Conditions for OTR Type Determination
When the SAP TM system receives a sales order, it creates an order-based transportation
requirement (OTR). This requirement must be mapped to a document in the SAP TM system,
which then determines the subsequent workflow process.
In this configuration step, the OTR type is determined when an order transferred from SAP ERP
to SAP TM.
Prerequisites
You have defined the OTR document types.
Procedure

/ Edit Condition .
3. Choose Continue.
If the system issues a message stating that the condition already exists, continue
this process from the point at which you maintain values on the Decision Table
tab page.
4. On the New Condition Definition screen, enter the relevant data based on the tables
below.
In the General Data screen area:
Condition type supplied by the

Condition ZOTR_TYPE
system
Description of the condition OTR Type Determination

Description
type Condition
In the Settings screen area:
Condition type supplied by the

Condition Type /SCMTMS/OTR_TYPE
system
Source of the condition Condition based on BRFplus

Origin of Condition
information Decision Table
5. In the Decision Table of the Data Access Definition tab page, enter the following data:
(C) SAP AG 70
Parameter: “is equal to”

BseDoc. Ty. Incoming base document type
Value: 114 – Sales Order
Proc Type
OTTL (the document type for
the incoming order defined
Procedure type (incoming above)
This respective parameter)
Parameter: “is equal to”
column is available
after saving the Value: OTTL
condition.
Specify the data for integration

here – the document type that OTTL (defined in a previous
OTR Type
is identified and used in SAP step)
TM for OTR.
To enter values on the Decision Table tab page, you may have to switch to edit mode
and choose Insert New Row..
6. Save your changes.
Result
You have configured the integration settings between the incoming sales document and the OTR
document type.
(C) SAP AG 71
Creating Delivery Profiles
Procedure
1. In your SAP Transportation Management system, call transaction NWBC to open the SAP
NetWeaver Business Client.
2. Choose Application Administration Planning General Settings Delivery Profile

Create Delivery Profile .
Field Value
Delivery Profile OT_DELV_PRFL_STAN
Delivery Profile for Outsourced

Description
Transportation
Fix Planning Results Selected
Delivery Creation Per OTR
(C) SAP AG 72
Defining Tendering Profiles
You use tendering profiles to define the process settings. For more information, see step 9 in
Defining General Settings for Tendering. [Page 76]
Procedure
1. On the SAP Easy Access screen, choose Application Administration Tendering
Tendering Profiles Create Tendering Profile .
2. In the General Data screen area, enter a unique ID for the profile in the Tendering Profile
field (for example, OT-TEND-PROF).
3. Choose Insert Step.
The system enters a sequential step number in the Step/Carrier column.
4. Enter your data for Step 1 based on the following table:
Peer-to-Peer Tendering,
Response Required
Determines how tendering is
Tendering Type
carried out Tender is sent to one carrier
and a confirmation is required
from this carrier
RFQ-Based, Award
Tendering Process Tendering process mode
Automatically
Carrier Carrier Blank
Freight RFQ Sequence Freight RFQ sequence

Blank
Number number
Get Carriers from Ranking

List
Determines how carriers are
Carrier Assignment Method
assigned to the freight order
A ranking list is provided from
which carriers are selected
Relative Price Limit Relative price 100
Carrier-Specific Freight Carrier-specific freight

Selected
Agreement agreement
2:00
The RFQ is confirmed in the

Maximum time within which freight order when the
Maximum Response Duration the carrier must respond to an program that checks the
RFQ responses is executed.
(C) SAP AG 73
If you want to run this

report manually, on
the SAP Easy Access
screen choose
Application
Administration
Background
Reports
Background
Processing of
Tendering .
Defines the visibility setting for

OT_VIS_SET
RFQ, that is, whether prices
Visibility Settings are displayed, whether the This setting is defined in the
carrier can change the prices, next chapter.
and so on
5. Choose Insert Step.
The system enters a second step in the column.
6. Enter your data for Step 2 based on the following table:
Broadcast Tendering – Best

Offer
Determines how tendering is
Tendering Type
carried out Tender is sent to all carriers
and a confirmation is required
from each carrier
RFQ-Based, Award
Tendering Process Tendering process mode
Automatically
Carrier Carrier Blank
Freight RFQ Sequence Freight RFQ sequence

Blank
Number number
Get Carriers from Ranking

List
Determines how carriers are
Carrier Assignment Method
assigned to the freight order
A ranking list is provided from
which carriers are selected
Relative Price Limit Relative price 100%
Carrier-Specific Freight Carrier-specific freight

Deselected
Agreement agreement
0:15
Maximum Response Duration Maximum time within which
the carrier must respond to an The RFQ is confirmed in the
(C) SAP AG 74
RFQ freight order when the
program that checks the
responses is executed.
If you want to run this

report manually, on
the SAP Easy Access
screen choose
Application
Administration
Background
Reports
Background
Processing of
Tendering .
Defines the visibility setting for

OT_VIS_SET
RFQ, that is, whether prices
Visibility Settings are displayed, whether the
This setting is defined in the
carrier can change the prices, next chapter.
and so on
7. Save your entries after maintaining the visibility settings in the next section.
(C) SAP AG 75
Defining General Settings for Tendering
Before tendering can be carried out, you must configure various profile settings. Some of these
profiles and settings are used and assigned when the freight order (FOR) is configured. The
following section explains each of these settings in more detail.
Procedure
Freight Order Management Tendering Define General Settings for Tendering .
2. In the tree structure on the left-hand side, double-click 01 — Visibility Settings and
choose New Entries.
3. Create your entry based on the following table:
Unique name for the profile

Visibility Setting OT_VIS_SET
setting for tendering visibility
Description of the visibility OT: Visibility

Vis. Stngs Desc.
settings profile Settings
Specifies whether the stop

dates are displayed for the
Stop Dates Visib. ER, Editable, Relevant
carrier when the carrier
receives the RFQ
Specifies whether the price

Price Limit limit set for this tender is RO Read Only
displayed for the carrier
Specifies whether the price for

this tender is displayed for the
Subm. Price Visib. ER, Editable Relevant
carrier and whether the carrier
can change the offer
5. Double-click 02 — Rejection Reason Codes and choose New Entries.
01 – No Capacity
Here, a list is created from
Reason which the carrier can select a 02 – No Time
value to reject an RFQ
03 – No Reason to Provide
8. Double-click 04 — Process Settings and choose New Entries.
(C) SAP AG 76
9. Create an entry based on the following table:
Process Settings Process setting ID OT_PROCESS_SETTINGS
Tendering Manager Tendering Manager <Your user ID>
Visibility Settings Visibility settings OT_VIS_SET
Tendering Profile Tendering Profile OT-TEND-PROF
Defines the carrier selection

that you want to use for the
automatic carrier proposal in
Carrier Settings the tendering process. For OT_CARR_SEL_01
more information, see
Defining Carrier Selection
Settings [Page 85].
Defines the maximum period

for the carrier to respond to
Max. Resp. Times [h] the freight request for Blank
quotation (RFQ) in these
process-related settings
Defines whether you want to

BP Calling Hours take the calling hours of your Deselected
business partner into account
Allows the carrier to submit a

price that deviates by the
percentage defined here from
Review Threshold [%] 5%
the price you submitted in the
freight request for quotation
(RFQ)
Defines that the tendering

process is restarted
Restart Tendering Selected
automatically if the awarded
carrier rejects the freight order
Calculate Charges after

None Deselected
Tendering
11. Double-click 05 — Communication Settings and choose New Entries.
12. Create an entry based on the following tables:
Header area:
Name of the communication

Comm. Settings OT_COMM_SET
profile setting to be created
(C) SAP AG 77
05 — Communication Settings screen area:
If you select this checkbox,

alerts are sent to tendering
Trigger Alerts w/o
managers even if they have Selected
Subscription to Alert Category
not subscribed to the alert
category.
Created EDI massages for the

Send EDI Messages Deselected
alerts
E-Mail screen area:
Send RFQ Create RFQ by e-mail Selected
Send Notification for Create notification for

Selected
Canceled Tendering canceled tendering
Send Notification for Sent Send notification e-mails for

Deselected
RFQs sent freight RFQs
Send Notification for Awarded Create notification e-mails for

Selected
Quotation accepted freight quotations
Send Notification for Rejected Create notification e-mails for

Selected
Quotation rejected freight quotations
SMS screen area:
Send RFQ Create RFQ by SMS Deselected
Send Notification for Create notification for

Selected
Canceled Tendering canceled tendering
Send Notification for Sent Send notification SMS for sent

Selected
RFQs freight RFQs
Send Notification for Awarded Create notification SMS for

Selected
Quotation accepted freight quotations
Send Notification for Rejected Create notification SMS for

Selected
Quotation rejected freight quotations
14. Double-click 06 — Carrier-Specific Communication Settings and choose New Entries.
15. Create a new entry based on the following tables:
Header area:
(C) SAP AG 78
Carrier number for which

Carrier specific communication OT-CAR-01
settings are to be created
06 – Carrier-Specific Communication Settings screen area:
Field Value
Create EDI Messages Selected
E-mail for Canceled Tendering Selected
17. Double-click 07 — Default Settings.
Here, you can assign the default settings for process settings and communication
settings.
These settings are used if the system cannot identify any process settings or
communication settings for tendering, or if these settings have not been assigned directly
in the freight order.
In this scenario, these settings are assigned at the level of the appropriate document and
so the settings specified here are ignored.
If required, enter the default settings based on the following table:
Any process setting that you

want to specify as the default
Tendering Process Settings Default process settings
setting (for example,
_DEFAULT)
Any communication setting

Default communication that you want to specify as the
Tendering Comm. Settings
settings default setting (for example,
_DEFAULT)
Result
You have configured the profile settings for tendering.
(C) SAP AG 79
Defining Conditions for Incompatibilities
When you create an incompatibility, you must also create an incompatibility condition. You use
conditions to define incompatibilities between planning data by specifying condition attributes. If
the planning data matches the condition specified, the data is identified as incompatible.
Procedure

.
The New Condition Definition screen appears.
3. Enter your data based on the following settings.
Condition Unique identifier OT_INC_COND_CARR
OT-Incomp cond –
Description Description of condition Carrier
Select the appropriate

Condition Type /SCMTMS/INC_CARRIER
condition type here
Specify the origin of the Direct Business Object

Origin of Condition
condition Access
4. Choose Continue.
5. In the Data Access Definition table, choose Create.
6. Create a new data access definition based on the following entries:
This value is populated

automatically based on your
Data Element Used for Input
entries in Configuring BU_PARTNER
Help
Incompatibility Settings [Page
84].
BO used to obtain the

Name of BO Used in
information about the /SCMTMS/SUPPLIER
Condition
incompatibility
Name of BO Node Used in BO node used to obtain the

ROOT
Condition information
Field used to obtain the value

Name of the Field of BO Node PARTNER
for the incompatibility
(C) SAP AG 80
8. Create the second condition based on the following attributes.
Condition Unique identifier OT_INC_COND_CUST
OT-Incomp cond –
Description Description of condition
Customer
Select the appropriate

Condition Type /SCMTMS/INC_TO
condition type here
Specify the origin of the Direct Business Object

Origin of Condition
condition Access
9. In the Data Access Definition table:
This value is populated

automatically based on your
Data Element Used for Input
entries in Configuring /SCMTMS/PTY_CONSIGNEE
Help
Incompatibility Settings. [Page
84]
BO used to obtain the

Name of BO Used in
information about the /SCMTMS/TOR
Condition
incompatibility
Name of BO Node Used in BO node used to obtain the

ROOT
Condition information
Field used to obtain the value

Name of the Field of BO Node CONSIGNEEID
for the incompatibility
(C) SAP AG 81
Creating Incompatibilities
You use incompatibilities to define the compatibility of planning data that the system uses during
transportation planning. For example:
 Refrigerated goods must only be transported using an appropriate means of transport

(such as refrigerated trucks)
 A certain means of transport cannot be unloaded at a particular location since the

location does not have a suitable loading ramp
 Customers do not want specific carriers to load or unload goods at their locations
Incompatibilities enable you to control the assignment of freight units to transportation plans (that
is, planned transportation activities) and, in turn, the assignment of transportation plans to the
means of transport.
On the following pages, we create an incompatibility between a shipper (OT-VN-01) and a carrier
(OT-CR-01).
Procedure
2. Choose Application Administration Planning General Settings Incompatibility

Definition Create Incompatibility .
3. On the New Incompatibility Definition screen, enter your data based on the following
tables.
Incompatibility Definition screen area:
Incompatibility Name of the incompatibility OT_INCOMP_CAR_CUST
Description of the OT-Carrier-Cust

Description
incompatibility Incompatibility
Incompatibility Area Applicable TM area O5 – Carrier Selection
Further definition of the

81 – Carrier – Transportation
Incompatibility Type incompatibility – where is it
Order
applicable?
Defines how values are

Condition-Based
Determination Method determined for the
Incompatibility
incompatibility
System response if this

incompatibility is violated due Warning If Incompatibility Is
Manual Violation
to a manual assignment of Violated
values
Automatic Violation System response if this

Incompatibility Must Not Be
incompatibility is violated due
(C) SAP AG 82
to an automatic assignment of Violated
values
Conditions screen area:
First condition:
Incompatibility condition to be
used. The condition can be
Condition OT_INC_COND_CARR
created directly from the link in
this field.
Incompatibility setting
Relevant Condition Result OT-CR-01
outcome
Second condition:
Incompatibility condition to be
used. The condition can be
Condition OT_INC_COND_CUST
created directly from the link in
this field.
Incompatibility setting
Relevant Condition Result OT-CU-01
outcome
More Information
For more information, see Defining Conditions for Incompatibilities [Page 80].
(C) SAP AG 83
Configuring Incompatibility Settings
Incompatibility settings are used to inform SAP Transportation Management of the current
conditions for the incompatibility.
Procedure
2. Choose Application Administration Planning General Settings Incompatibility

Settings Create Incompatibility Settings .
3. On the New Incompatibility Settings screen, enter your data based on the following table:
Unique ID for the

Incompatibility Settings OT_INCOMP_SET_001
incompatibility settings
Description of the
Description OT Incomp. Settings
incompatibility settings
Area in which the

Incompatibility Area Carrier Selection
incompatibility is to be applied
If you select this checkbox,

Default Incompatibility
the system uses the default Deselected
Settings
incompatibility settings.
4. Choose Insert.
Incompatibility Incompatibility defined above OT_INCOMP_CAR_CUST
Action to be carried out if the

incompatibility is violated and According to Incompatibility
Violation in Manual Planning
the location from which to Definition
derive the follow-on actions
Action to be carried out if the

Violation in Automatic incompatibility is violated and According to Incompatibility
Planning the location from which to Definition
derive the follow-on actions
Result
The setting is assigned to the carrier selection setting.
(C) SAP AG 84
Defining Carrier Selection Settings
You use carrier settings to define the process settings. For more information, see step 15 in
Defining General Settings for Tendering. [Page 76] This profile setting determines how carriers
are selected.
Procedure
1. On the SAP Easy Access screen, choose SAP menu Application Administration
Planning Planning Profile Settings Carrier Selection Settings Create Carrier
Selection Settings .
2. On the New Carrier Selection Settings screen, enter the settings for a general carrier
based on the following tables:
Unique ID of the settings

Carrier Selection Settings OT_CAR_SEL_02
profile
OT: General Carrier

Description Carrier selection description Selection Profile
Indicates that incompatibilities

Check Incompatibilities are to be taken into account Selected
when selecting a carrier
OT_INCOMP_SET_001
Enter a profile if
Incompatibility Settings incompatibilities are to be (For more information, see
checked Configuring Incompatibility
Settings [Page 84])
Type of Carrier Selection

Type of carrier General Carrier Selection
Settings
In the Other Settings screen area:
Specify whether the

transportation allocation Use Transportation
Trsp. Alloc. Usage
usage is to be activated when Allocations
the carrier is selected

business share (BS) settings
BS Usage for the carrier are to be taken Do Not Use Business Shares
into account when selecting
carriers
Strategy Which strategy is to be used Costs

to select the carrier?
(C) SAP AG 85
Strategies can be based on
costs, priorities, or a
combination of the two.
If the strategy is cost-based,

Use Transportation Charges
Carrier Cost Origin this field specifies the cost
from TCM
origin for selecting the carrier
On the Advanced Settings tab page:
Planning strategy for selecting

Planning Strategy TSPS_DEF
carriers
Runtime for the optimizer run

used to select the carrier. This
Optimizer Runtime 6
prevents processes from
running indefinitely.
Consider this assignment as

Consider Manual Assignment
the final carrier assigned to Deselected
as Fixed
the freight order
Specifies whether the manual

planning list can be entered
Action for Manual Rankings during the planning process Remove
and how the manual entries
are to be handled
Overall Carrier Availability Overall carrier availability Deselected
Currency used to calculate

Common Currency USD
costs
Action that is to be performed

Action After Carrier Selection
once the carriers have been Automatic Tendering
Run
selected
Specifies how carriers are to

be selected based on the Do Not Create Continuous
Continuous Move Type
continuous move Move
opportunities
Specifies whether continuous

Continuous Move Information move possibilities are to be Selected
considered
Reaction to CM Removal Reaction to CM removal Blank
Determines whether the

distance of the locations and
Check Dist. and Dur. Deselected
the duration of the trip are to
be taken into consideration
(C) SAP AG 86
Determines whether
continuous move means of
Continuous Move MTr. Check Deselected
transport are to be taken into
consideration
CM Cost Recalculation for Active if continuous move is No Recalculation

TCM used to select carriers
Use Tendered Objects for Use tendered objects for

Deselected
Optimization optimization
Tender Without Optimizer Tender without optimizer

Deselected
Result result
<User ID of the
Tendering Manager User ID of the manager
tendering manager>
Tendering profile to be used

Tendering Profile OT-TEND-PROFILE
in automatic tendering
4. Repeat this process to create settings for the tendering profile based on the following
tables.
Unique ID of the settings

Carrier Selection Settings OT_CARR_SEL_01
profile
Description Carrier selection description OT: CS Profile for Tendering
Indicates that incompatibilities

Check Incompatibilities are to be taken into account Selected
when selecting a carrier
OT_INCOMP_SET_001
Enter a profile if
Incompatibility Settings incompatibilities are to be (For more information, see
checked Configuring Incompatibility
Settings [Page 84])
Type of Carrier Selection Carrier Selection for

Type of carrier
Settings Tendering
In the Other Settings screen area:
Specify whether the Use Transportation

Trsp. Alloc. Usage transportation allocation Allocations
usage is to be activated when
(C) SAP AG 87
the carrier is selected
On the Advanced Settings tab page:
Planning strategy for selecting

Planning Strategy TSPS_DEF
carriers
Overall Carrier Availability Overall carrier availability Deselected
(C) SAP AG 88
Defining Freight Order Types
Freight orders (FOR) are used for planning, tendering, and subcontracting. They also define the
major process settings.
Prerequisites
 You have configured the Default FSD Type.
 You have configured the tendering-related process settings and communication settings.
You can also configure the tendering-related process settings and

communication settings at a later time. If you do so, you must remember to
update them here.
Procedure
Freight Order Management Freight Order Define Freight Order Types or enter
transaction /SCMTMS/C_FOR in the command field.
2. Switch to change mode and choose New Entries.
 On the New Entries: Details of Added Entries screen, enter your data based on the
following tables.
In the Freight Order Types screen area:
Unique 4-character ID of the OTTL

Freight Order Type
FOR that is to be defined
Description of the FOR to be

Description Truck Load Order
defined
In the Basic Settings screen area:
Indicator that specifies

Freight Order Can Be 01 – Relevant for
whether this FOR type can
Subcontracted Subcontracting
use subcontracting processes
P – Determine Based on
Determines how the shipper
Shipper/Consignee Predecessor Documents (if
and consignee partners are
Determination these are not unique, use the
determined for this FOR
setting for locations)
Fix Document When Saving Selected
(C) SAP AG 89
Specifies whether the FOR

Freight Order Can Be Deleted can be deleted once it has Selected
been created
Enable Settelment Enables settlement Selected
Enable Charge Calculation Enables charge calclation Selected
In the Number Range Settings screen area:
Specifies the time at which a

Draw Number When Saving
Time for Drawing number is assigned to the
Document
FOR document
Number range that is to be 02

Number Range Interval
used for this document type
In the Change Controller Settings screen area:
Default strategy used for

tendering behavior when
Default Change Strategy changes are made to the FOR DEF_CHACO
key fields, such as partners,
quantities, and so on
Specifies the condition that

the system is to use to
determine a change controller
strategy at runtime.
If you have defined several

Change Strategy change controller strategies, OT-CSDC-01
Determination Cond. you can use a condition to
determine the appropriate
change controller strategy.
The condition type of this

condition is
/SCMTMS/CC_TOR_STRAT.
Specifies the tolerances for a

quantity change in a business
document.
Quantity Tolerance Condition OT_QTOL_01
The condition type of this
condition is
/SCMTMS/CC_QUAN_TOL.
Date Tolerance Condition Specifies the tolerances for a Blank

date change in a business
(C) SAP AG 90
document
In the Additional Strategies screen area:
Specifies tasks that the

change controller is to
perform when you create one
of the following business
documents:
Creation Strategy Freight order CARR_SEL
Freight booking
Transportation unit
Freight unit

perform when you save the
Save Strategy freight order.
Blank
The strategy definition is
explained in a separate step
below.

Deletion Strategy CANCEL_CAP
perform when you delete the
freight order.
In the Execution Settings screen area:
Controls how documents are

tracked.
If you want to track certain

types of documents, choose 2
(Execution Tracking) or 3
(Execution Tracking with
External Event Management). 3 – Execution Tracking with
Execution Track. Relev. The system then sets the External Event Management
initial document execution
status to Not Started.
If you do not want to track

certain types of documents,
choose 1 (No Execution
Tracking). The system then
sets the initial document
(C) SAP AG 91
execution status to Not
Relevant.
Indicator that sets the status

In Process immediately as
Immediate Processing Selected
soon as the document is
created and saved
Check Condition “Ready for

Not used Blank
Exec”
Propagates the execution

Propagate Execution Info information to the Deselected
predecessor document
In the Event Management Settings screen area:
Type of application object to

be tracked in the application
system (required to determine
whether an application object
Application Object Type is relevant for Event ODT20_TO
Management). The event
manager processes only the
event messages for these
objects.
Last expected event for a

Last Exp. Event document, for example, the POD
Unload_End.
In the Service Level Determination screen area:
Default service level code for

Default Service Level Blank
the business document type
Condition for service level

Service Level Cond. Blank
determination
In the Default MTr Determination screen area:
Specifies the default means of

Default MTr for Type transport for this freight order OT-FTL
type
Name of the condition for the

Condition for Def MTr Blank
default means of transport
In the Tendering Settings screen area:
(C) SAP AG 92
Indicates that the Customizing

settings for tendering are
Use Default Settings Deselected
determined in accordance
with the default settings
Use Condition for Sett. Indicates that the Customizing

Determ. Tendering Condition settings for tendering are Deselected
Definition determined using conditions.
Enables you to further define

the FOR-type-specific
Use Type Specific Settings processes for process Selected
settings and communication
settings.
Specifies the tendering

process settings.
Identifies process-related
settings, for example:
o Default
tendering manager
Process Settings OT_PROCESS_SETTINGS
o Maximum
response duration
o Tendering
profile
The section below explains

this setting in more detail.
Indicates the strategy for

tendering communication.
Communication Settings OT_COMM_SET
This profile is defined in a
separate stage below.
In the Default Units of Measure screen area:
Weight Weight US Pound
Volume Volume Cubic Foot
In the Output Options screen area:
Output Profile Output profile /SCMTMS/TOR_PRINT_ROAD
Add. Output Profile Additional output profile Blank
(C) SAP AG 93
Text Schema Text schema OT0001
Dynamic Determination of Dynamic determination of

Deselected
Output output profile
In the Additional Settings screen area:
Defines the dangerous goods

Dangerous Goods Profile Blank
profile
Customs Profile Defines the customs profile Blank
Enter the FSD type that you

defined in Defining Freight
Default FSD Type Default FSD type
Settlement Document Types
[Page 96]
Indicates the number range

interval for the freight order
HBL Number Range type, freight booking type, Blank
freight unit type, or
transportation unit type.
Carrier selection profile

Default Carrier Selection
determined when the save OT_CAR_SEL_02
Profile
strategy is triggered
Default Carrier Selection Condition for defining the

Blank
Condition default carrier selection profile
Shipment Creation Relevance Shipment creation relevance No shipment creation in ERP
BW Relevance BW relevance Selected
Track Changes Track changes Selected
Archiving Retention Period in Retention period in days

Zero
Days before archiving
Defines the Web Dynpro

application configuration that
Web Dynpro Application is loaded if a business
Blank
Config. document of forwarding order
management is opened with
this type
In the Organizational Unit Determination screen area:
ID of the organizational unit <Your organizational

Execution Org.
that is defined as: unit>(OT-PORG-1)
(C) SAP AG 94
Unit function 13 – planning

and execution
Unit role 1 – organization
ID of the organizational unit

that is defined as: <Your purchasing
Purchase Org. organization>(OT-
Unit function 2 – purchasing
PEORG-1)
Unit role 1 – organization

that is defined as:
<Your execution
Execution Group Unit function 13 – planning
group>(OT_PEGRP-1)
and execution
Unit role 3 – group

that is defined as:
<Your purchasing
Purchasing Group
Unit function 2 – purchasing group>(OT-PGRP-1)
Unit role 3 – group
Specifies that the

Consider Organization Unit of
organizational unit of the user Deselected
User
is to be taken into account
Condition Condition Blank
Result
You have defined the new freight order type.
(C) SAP AG 95
Defining Freight Settlement Document Types
Procedure
Settlement Freight Settlement Define Freight Settlement Document Types .
Field Value
FSD Type OTTL
Description Carrier Settlement Document
FSD Category Freight Settlement Document
No. Range Interval 01
BW Relevance Selected
Output Profile /SCMTMS/TOR_INV_PREP
Add. Output Profile /SCMTMS/SFIR_PRINT
Dynamic Determination of Output Profile Deselected
(C) SAP AG 96
Charge Management
Process
To configure charge management, complete the following steps:
1. Defining Scales [Page 98]
2. Defining Rate Tables [Page 100]
3. Defining Calculation Sheets [Page 106]
4. Defining Freight Agreement Types [Page 110]
The charge elements used in our scenario are:
 Line haul charge – based on point-to-point (location-to-location)
 Fuel surcharge – based on distance (per mile rate and index-based)
 Detention charges – manual charge (flat rate)
(C) SAP AG 97
Defining Scales
Scales are parameters that you can use to specify freight rates when they are assigned to freight
conditions.
Procedure
1. To create a scale, open your user menu on the SAP Easy Access screen and choose
Master Data Charge Management Scales Create Scale .
3. Enter the data for your scale based on the following table:
Tab Page Field Description Value
Scale Scale ID OT-SCALE-LOC
Description of the OT – Origin

Description
scale Location Scale
General Data
Defines the basis of
scale, for example,
Scale Base LOC – Location
location, distance,
duration, and so on.
Absolute
Defines how the scale
Calculation Type
values are read (values are read
Items directly)
Define Location SP3100@<logical

Internal Location
relevant for scale system>
5. Create a new scale:
OT-SCALE-
Scale Scale ID CUSTOMER
Description of the OT – Customer

Description
scale base scale
General Data
scale, for example,
Scale Base BP – Business partner
location, distance,
Define Business
Items BP Number Partner relevant for OT-CU-01
scale
(C) SAP AG 98
Defines how the scale Absolute

Calculation Type
values are read
7. Create a new scale:
Scale Scale ID OT-SCALE-REGION
Description of the
Description OT – Regions
scale
General Data
scale, for example,
Scale Base Region
location, distance,
Defines the region WA

Region
relevant to the scale
Items
Defines how the scale Absolute
Calculation Type
values are read
(C) SAP AG 99
Defining Rate Tables
Rates are maintained in rate tables, which use the scales specified in Defining Scales. [Page 98]
In our scenario, the following scales are assigned to the rate tables:
Rate Table Used Scales Charge Type Assigned
OT-RATE-CR-01
OT-RATE-CR-02 OT-SCALE-LOC
FB00 – Base Freight
OT-RATE-CR-03 OT-SCALE-REGION
OT-RATE-CR-04
OT-RATE-FUEL OT –SCALE-REGION FUEL – Fuel Surcharge
OT-RATE-LMPR OT-SCALE-CUSTOMER LMPR – Lumper Charges
Procedure
1. On the SAP Easy Access screen in SAP Transportation Management, choose SAP
menu Master Data Charge Management Rate Tables Create Rate Table
Definition .
2. Choose Continue.
3. On the New Table Rate Definition screen, enter a new table rate based on the following
table:
Unique identifier for the rate OT-RATE-CR-01

Rate Table
table
OT – FTL Rate from

Description Description of the table Location to Region
Specifies the scenario in

which the rate table can be
used, for example, for
Charge Usage Service Provider
customer billing integration,
supplier invoice integration, or
none
Here, the charge type is

Charge Type linked for integration with SAP FB00 – Base Freight
ERP.
Value Type Absolute value
4. Choose the Scales tab page.
5. Enter the scales based on the following table:
(C) SAP AG 100

Enter the scales defined in

Defining Scales [Page 98]. 1: OT_SCALE_LOC
Scale Reference This activates the entries in
the rate table as specified by 2: OT_SCALE_REGION
the relevant sequence.
Determines how the values

are stored and calculated for 1: SOURCELOC
Calculation Base this dimension. Sources of
information are predefined 2: DESTLOC_REG
based on the object.
6. Select each line and choose Create Scales.
8. Choose the Dates and Values tab page.
The date as of which the rate

Valid From Today
table is valid
The date to which the rate 2099–12–31

Valid To
table is valid
Currency that is applicable for

Currency USD
this rate table
Source Location:
SP3100@<logical
system>
Once you have entered the Destination Region: WA

validity dates, you can create
table entries for the Value:
Values in Table
dimension. To do so, select
1.48 (for OT-RATE-CR-01)
the row containing the validity
dates.
10. On the Calculation Rules tab page, enter your data based on the following table:
Provides the calculation base

Calculation Base for this rate. In our rate table, ACTUAL_DIST
the rates are specified as
per/mile from source to
(C) SAP AG 101

destination locations.
However, the calculation base
must be determined to apply
these rates. In this case, the
calculation base is distance.
There are various bases such

as business partner role,
weight, destination location,
and so on.
Defines the multiplier for the

calculation base. For
Quantity example, the applicable rate 1
can be per mile or per 100
miles.
The unit of measure specifies

Unit of Measure the unit to which the multiplier MI
is applied.
11. Release and save your data.
12. Repeat the process to define all of your carrier-specific rate tables for the various
carriers. In our scenario, these are:
o OT-RATE-FB00-CAR-02 (for carrier OT-CR-02)
13. For the fuel surcharge, add another table based on the following data:
Unique identifier for the rate OT-RATE-FUEL

Rate Table
table
OT – Destination
Description Description of the table Dependent Fuel
Surcharge

none

Charge Type linked for integration with SAP FUEL – Fuel Surcharge
ERP.
Value Percentage Value
(C) SAP AG 102

Defines a row (x-axis) or

column (y-axis) in the rate
Dimension 1 for the first scale
table. A rate table can contain
multiple scales (up to 9).

Defining Scales [Page 98].
Scale Reference This activates the entries in 1: OT-SCALE-REGION
the rate table as specified by

are stored and calculated for
Calculation Base this dimension. Sources of 1: DESTLOC_REG
information are predefined
The date as of which the rate 2010–01–01

Valid From
table is valid
The date to which the rate

Valid To 2012–12–31
table is valid
Once the rate table is fully

The system sets the value
defined, it must be set to
based on the follow-up action
Released so that it can be
Life Cycle Status using the following menu:
used further. If the rate table
is still in process, you can
Set Status Released
leave it as Deactivated.
Currency that is applicable for USD

Currency
this rate table
Once you have entered the

validity dates, you can create Destination Region Location:
table entries for the WA
Values in Table
the row containing the validity Value: 0.05
dates.
19. For the lumper charges, add another table based on the data below:
(C) SAP AG 103

Unique identifier for the rate OT-RATE-LMPR

Rate Table
table
Description Description of the table OT – Lumper Rates

none

Charge Type linked for integration with SAP LMPR – Lumper Charges
ERP.
Value Percentage Value
Defines a row (x-axis) or

column (y-axis) in the rate
Dimension 1 for the first scale
table. A rate table can contain
multiple scales (up to 9).

Defining Scales [Page 98].
Scale Reference This activates the entries in 1: OT_SCALE_CUSTOMER
the rate table as specified by

are stored and calculated for
Calculation Base this dimension. Sources of SHIP_TO_PARTY
information are predefined
The date as of which the rate 2010–01–01

Valid From
table is valid
The date to which the rate

Valid To 2012–12–31
table is valid
Life Cycle Status Once the rate table is fully The system sets the value
defined, it must be set to based on the follow-up action
(C) SAP AG 104

Released so that it can be using the following menu:
used further. If the rate table
is still in process, you can Set Status Released
leave it as Deactivated.
Currency that is applicable for

Currency USD
this rate table
Once you have entered the

validity dates, you can create
Ship-to Party: OT-CU-01
table entries for the
Values in Table
Value: 50.00
the row containing the validity
dates.
(C) SAP AG 105

Defining Calculation Sheets
Within a freight order or forwarding order, the applicable charges are calculated on the basis of
the calculation sheet.
Procedure
menu Master Data Charge Management Calculation Sheets Create Calculation
Sheet .
2. Choose Continue.
3. On the New Calculation Sheet screen, enter your data based on the following tables.
In our scenario, we create four calculation sheets (one for each carrier).
On the General Data tab page:
OT-TCCS-CR-01
Unique identifier for the OT-TCCS-CR-02

Calculation Sheet calculation sheet to be
defined OT-TCCS-CR-03
OT-TCCS-CR-04
OT-TCCS for CR01
OT-TCCS for CR 02
Description of the calculation
Description
sheet OT-TCCS for CR 03
OT-TCCS for CR 04

calculation sheet is used for
customers, vendors (carriers),
both, or neither. Furthermore,
Charge Usage 2 – Service Provider
indicates whether the
calculation sheet is used only
for decision making during
tendering, and so on.
Items screen area:
Indicates the levels of the Enter your items by choosing

charge elements in the Insert. In our scenario, we use
Item calculation sheet as well as the following values:
the descriptions derived from
the assigned charge types Base freight (FB00)
(C) SAP AG 106

Fuel surcharge (FUEL)
Lumper charges (LMPR)
Defines the sequence in

Line No. which the charge types are Entered by the system
executed
Defines the relationship

between charge types and
FB00: Standard
how the charges are to be
calculated for each charge
Instruction Type FUEL: Standard
type. For example, you can
specify whether the item LMPR: Standard
represents a total or a direct
calculation of the charge.
FB00
Specify the TM charge type
Charge Type FUEL
for each item.
LMPR
This is a freely definable

description and is
subsequently displayed in the
Description documents. We recommend -
that you use descriptions that
make sense in a number of
contexts.
Denotes the charge type as Deselected (for all of our

Mandatory
mandatory charge types)
USD (Not applicable for

Currency Applicable currency
charge types FUEL and LMPR)
4. Select the line for FB00.
5. In the area of the bottom of the screen, enter your data based on the following
information:
Rule to indicate how the

Instruction Type charge item is applied for the Standard
calculation
Description of the charge item Base Freight – Dist

Description
in the calculation sheet Based
Charge Type Assigned charge type FB00
(C) SAP AG 107

Line No. Line number of the item 20
Indicates the level at which

the calculation sheet is to be ROOT
applied. For example, it can
Calculation Resolution Base
be applied at the header level The calculation sheet applies
for the whole freight order or to the whole document.
at a particular stage only.
Calculation Method Type Calculation method type Standard
On the Rate tab page:
OT-RATE-CR-01
OT-RATE-CR-02
Rate Table Assigned rate table
OT-RATE-CR-03
OT-RATE-CR-04
6. Choose Save.
7. Select the line for the fuel surcharge.
information:

calculation
Description of the charge item

Description Fuel Surcharge
in the calculation sheet
Charge Type Assigned charge type FUEL
Reference item that forms the

Reference-From Line No. basis of the calculation for this 20
row
(C) SAP AG 108

Rate Table Assigned rate table OT-RATE-FUEL
9. Choose Save.
10. Select the line for the lumper charges.
information:

calculation
Description of the charge item

Description Lumper Charges
in the calculation sheet
Charge Type Assigned charge type LMPR
Rate Table Assigned rate table OT-RATE-LMPR
12. Choose Save.
(C) SAP AG 109

Defining Freight Agreement Types
Procedure
Master Data Agreements and Service Products Define Freight Agreement Settings
.
Type Freight agreement type OTTL
Short Desc. Short description (free text) Truck Load FA Type
FA No. Range Number range interval 03
4. Leave the default entries as shown.
(C) SAP AG 110

Defining Freight Agreements
Freight agreements contain all of the information that you require to calculate freight charges.
Prerequisites
You have defined a freight agreement type. [Page 110]
Procedure
menu Master Data Charge Management Freight Agreements Create Freight
Agreement .
2. On the New Freight Agreement screen, enter the relevant freight agreement type in the
Agreement Type field. In our scenario, this is OTTL.
3. If the freight agreement is applicable to both carriers and customers, select the Mutual
Agreement checkbox. In our scenario, this remains deselected.
4. Choose Continue.
5. On the following screen, enter your data based on the following table:
Agreement Agreement ID OT-FA-CR-01
Description of the freight

Description FA: OT-CR-01
agreement
Default purchasing <Your purchasing

Purchasing Organization
organization organization>
Carrier for which this freight

Carrier OT-CR-01
agreement is to be defined
Valid From Validity date range 2010–01–01
Valid To Validity date range 9999–12–31
Agreement Priority Priority of the agreement 5
Document currency Agreement currency USD
6. In the Items screen area, enter your item data based on the following table:
Item Number Item number 10
Assign the calculation sheet

once only. The details from
Calculation Sheet OT-TCCS-CR-01
this sheet are copied for each
item.
(C) SAP AG 111

7. Once you have entered your data, release the freight agreement by choosing Set
Status Released .
8. Choose Save.
In our scenario, we need to create separate freight agreements for the other carriers. The
table below shows the values for these carriers. Values for any fields not contained in this
table are the same as those entered in the freight agreement above.
Name of Freight
Description Carrier Calculation Sheet
Agreement
OT-FA-CR-02 FA: OT-CR-02 OT-CR-02 OT-TCCS-CR-02
(C) SAP AG 112

Defining Settlement Profiles
In this Customizing activity, you define the profile for creating invoices. The settlement profile
comprises a set of parameters that you can use to control how the system creates invoices.
You can assign the specified settlement profile to an organizational unit in transaction
/SCMTMS/TCM_FASET.
If you do not specify a settlement profile, the system uses standard default settings to create
settlement documents.
Procedure
Settlement Define Settlement Profile .
Settlement Prof Settlement profile OT_SP_01
Medium Desc. Medium description Settlement Profile
Identifies the data source to

Data Source be used when creating Planned Data
settlement documents
Defines the split /

consolidation criteria for
Split/Cons. FSD_CREAT
generating settlement
documents
Specifies how the values are

calculated when the invoice is
A Copy Fixed Charges and
Calculation Option created. You can copy fixed
Redetermine Others
charges and recalculate
others, or copy all charges.
Collective Invoice Collective invoice Selected
(C) SAP AG 113

Defining Charge Calculation Profiles
Procedure
1. In Customizing for SAP TM, choose Transportation Management Basic Functions
Charge Calculation Basic Settings for Charge Calculation Define Calculation Profile
.
2. Choose New Entries to create a new entry with the following data:
Calculation Profile Calcution Profile OT_CLCPRF
OT: Charge Calculation

Profile
EET_DATE (Expected End

Calc. Date Ty. Calcuation Date Type
Date of Complete Carriage)
1 (Calculation on Header
Calculation Level Calculation Level
Level)
Freight Agreement
Agr. Det. Rule Blank
Determination Rule
Calculation Sheet
Calc Sheet Det. Rule Blank
Determination Rule
Through Rate Through Rate Not selected
Dim Wt Profile Dimensional Weight Profile Blank
Dimal Wt Cond. Dimensional Weight Condition Blank
Exch. Rate Type Exchange Rate Type Blank
Data Source Data Source Actual Route
Airway Printing Airway Printing Blank
Airway Settlement Airway Settlement Blank
(C) SAP AG 114

Configuring Organizational Settings for Charge
Elements
Procedure
Basic Functions Charge Calculation Basic Settings for Charge Calculation Define
General Settings .
Internal ID of OT-PORG-1 (for

Org. Unit Purchasing organization unit
example, 500000627)
Default purchasing
Default Purch. Org. Blank
organization
Default Carrier Carrier OT-CR-03
Settlement Prof Settlement profile OT_SP_01
Prof. Det. Cond Determination condition Blank
Dim Wt Profile Dimensional weight profile Blank
Sales Calculation Profile Calculation profile OT_CLCPRF
Pur. Calculation Profile Calculation profile
Local Currency Local currency USD
(C) SAP AG 115

Transportation Allocation
In this section, we create transportation allocations for carriers assigned to a specific lane.
Allocation is considered to be a hard constraint within planning in this scenario. If an assigned
quantity exceeds the maximum allocation quantity of a carrier within a specific planning period,
the carrier is not considered in tendering (see the carrier selection settings).
(C) SAP AG 116

Defining Transportation Allocations
Procedure
2. Choose Planning Transportation Allocation Create Transportation Allocation .
3. Enter your data based on the following tables:
In the Creation Options screen area:
Transportation Lane Corresponding Transportation

Transportation lane reference
Reference Lane Must Exist
Overwrite Existing Buckets Overwrite existing buckets Deselected
Display Type Display type Display all
In the Trade Lanes screen area:
Defines the transportation

Orientation Along
lane
Source Type Source type Location
Source Source SP3100<logical system>
Destination Type Destination type Zone
Destination Destination OT-US-WEST
Means of Transport Means of transport OT-FTL
Transportation Mode Code Transportation mode code No entry
In the Transportation Allocation Scope screen area:
OT-CR-01
OT-CR-02
Carrier Carrier
OT-CR-03
OT-CR-04
Planning Period Planning period Monthly
Start Date Start date Actual month
(C) SAP AG 117

End Date End date Year end
Time Zone Time zone EST
Cover Full Calendar

Cover full calendar units Selected
Units
In the Buckets screen area:
Sub-Bucket Distribution Sub-bucket distribution No Distribution
Unit of Measure Unit of measure LB
Minimum TAL Quantity Minimum quantity 40000
Quantity that should/must not

Maximum TAL Quantity be exceeded within planning 120000
period
4. Choose Start.
Allocations are created accordingly.
5. Change the Maximum TAL Quantity of OT-CR-04 up to 500000 carrier in each planning
period.
6. Choose the Save pushbutton.
(C) SAP AG 118

Configuration Guide For Outsourced Transportation PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Configuration Guide For Outsourced Transportation PDF

Hochgeladen von

Copyright:

Verfügbare Formate

SAP Transportation Management

Configuration Guide for Outsourced Transportation

SAP Library document classification: PUBLIC

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

1.0 December 2010 Initial release

Harmonized configuration and master data; scenarios based

Added chapter Defining Charge Calculation Profiles

The following chapters have been updated form TM 9.0

 Editing Locations [Page 41]

 Defining OTR Types [Page 67]

 Defining Rate Tables [Page 100]

 Configuring Organizational Settings for Charge

 SD: Order-to-cash process:

o Sales order entry

o Posting goods issue

o Billing document creation

 MM: Purchase order process

o Purchase order entry

o Posting goods receipt

o Invoice document creation (ERS settlement)

o Supporting the processes listed above

o Country-specific legal requirements (such as tax calculation)

Company code 3000

Controlling area 3000

Storage location 0001

Shipping point 3100

Sales document type OTTL

 Basic Settings and Integration for ERP

 Integration of SAP TM and SAP Event Management

 Output Management Configuration Guide

 Visual Business Configuration with SAP TM

 Basic Settings for SAP TM

 Enterprise structure definition and relevant assignments

Business Object Prefix Suffix

Carrier CA– None

Customer CU– None

Plant PL– None

Shipping Point SP– None

Supplier SU– None

System None –@QV5750

Shipping point name in SAP TM: SP3100@QV5750

For more information, see:

 Master Data in SAP Enterprise Resource Planning [Page 14]

 Master Data in SAP Transportation Management [Page 28]

 Maintaining Organizational Objects [Page 15]

 Assigning Organizational Objects [Page 17]

 Assigning Pricing Determination Procedures [Page 18]

 Creating Customer Masters [Page 20]

 Creating Vendor Masters [Page 22]

 Defining Products [Page 24]

A sample structure is provided in the table below.

Organizational Object Value Navigation Path

Define, copy, delete, check

3. In Customizing for SAP ERP, choose SAP Customizing Implementation Guide

4. Maintain the following Customizing activities:

o Assign sales organization to company code

o Assign distribution channel to sales organization

o Assign division to sales organization

o Set up sales area