SAP Transportation Management
Configuration Guide for Outsourced Transportation
PUBLIC
Document Version: 3.0 – September 2012
(C) SAP AG 2
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 3
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 4
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 5
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 6
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 7
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 8
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
1.1 April 2011 Harmonized configuration and master data; scenarios based on IDES
2.0 July 2011
Added chapter Defining Charge Calculation Profiles
Updated chapter Configuring Organizational Settings for Charge Elements
3.0 September 2012
The following chapters have been updated form TM 9.0 setup:
Editing Locations [Page 41]
Defining OTR Types [Page 67]
Defining Freight Order Types [Page 89]
Defining Rate Tables [Page 100]
Configuring Organizational Settings for Charge Elements [Page 115]
(C) SAP AG 9
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 10
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 11
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 12
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 13
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 14
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 15
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
Company code 3000
(currency USD)
Enterprise Structure Definition Financial
Accounting Edit, Copy, Delete, Check Company
Code
Sales organization 3000
Enterprise Structure Definition Sales and
Distribution Define, copy, delete, check sales
organization
Distribution channel 10
Enterprise Structure Definition Sales and
Distribution
Define, copy, delete, check distribution channel
Sales office 3000
Enterprise Structure Definition Sales and
Distribution Maintain Sales
Office
Sales group 300
Enterprise Structure Definition Sales and
Distribution Maintain Sales
Group
Plant 3100
Enterprise Structure Definition Plant
Maintenance Maintain Maintenance Planning Plant
Storage location 0001
Enterprise Structure Definition Materials
Management Maintain
Storage Location
Shipping point 3100
Enterprise Structure Definition Logistics
Execution Define, Copy, Delete, Check Shipping Point
(C) SAP AG 16
Organizational Object Value Navigation Path
Purchasing organization 3000
Enterprise Structure Definition Materials
Management Maintain
Purchasing Organization
Purchasing group P01
Enterprise Structure Definition Materials
Management Purchasing Create Purchasing Groups
Division 00
Enterprise Structure Definition Logistics -
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 17
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.
3. In Customizing for SAP ERP, choose SAP Customizing Implementation Guide
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
5. In Customizing for SAP ERP, choose SAP Customizing Implementation Guide
Enterprise Structure Assignment Materials Management .
6. Maintain the following Customizing activities:
o Assign purchasing organization to company code
o Assign purchasing organization to plant
7. In Customizing for SAP ERP, choose SAP Customizing Implementation Guide
Enterprise Structure Assignment Logistics Execution .
8. Maintain the Customizing activity Assign shipping point to plant.
(C) SAP AG 18
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 19
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 20
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 21
Field Value
countries.
6. On the Account Management tab page, in the Recon. Account field, enter 144003.
(C) SAP AG 22
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:
Vendor OT-CR-01 OT-CR-02 OT-CR-03 OT-CR-04
Name PGI Truck
Lines National
Trucking
Fast
Trucking &
Logistics
Green
Transport
Search Term OT Carrier OT Carrier OT Carrier OT Carrier
Street Windgap
Avenue Durand
Avenue Spring
Street Port Jersey
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:
Vendor OT-CR-01 OT-CR-02 OT-CR-03 OT-CR-04
Reconciliation Account
164003 164003 164003 164003
(C) SAP AG 23
Vendor OT-CR-01 OT-CR-02 OT-CR-03 OT-CR-04
Cash Management Group
A1 A1 A1 A1
7. Choose Next Screen or press F8 until you reach the Create Vendor: Purchasing Data
screen.
8. Enter your data based on the following table:
Vendor OT-CR-01 OT-CR-02 OT-CR-03 OT-CR-04
Order Currency USD USD USD USD
Terms of Payment
0001 0001 0001 0001
GR-Based Inv. Verif.
Selected Selected Selected Selected
Serv.-Based Inv. Ver.
Selected Selected Selected Selected
9. Choose Next Screen or press F8 to open the Create Vendor: Partner Functions screen.
10. Enter your data based on the following table:
Vendor OT-CR-01 OT-CR-02 OT-CR-03 OT-CR-04
Partner Function
VN VN VN VN
Number OT-CR-01 OT-CR-02 OT-CR-03 OT-CR-04
11. Save your entries.
(C) SAP AG 24
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 25
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
11. Save your entries.
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 26
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).
7. Save your entries.
(C) SAP AG 27
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
6. Save your entries.
(C) SAP AG 28
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 29
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
Carrier code (in SAP ERP and SAP TM)
OT-CR-02
OT-CR-02
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 30
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 31
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
OT-IM-001
Logical system of the target TM System as defined in Core Interface Settings in SAP ERP (for example, B1TCLNT910).
TM MD
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
Vendors
OT-CR-01
OT-CR-02
OT-CR-03
OT-CR-04
1
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 32
8. Choose Execute to create the integration model.
9. Choose Generate IM.
10. Choose Back.
(C) SAP AG 33
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 Logic System
Logical system of the target SAP TM System as defined in 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 34
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 35
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
Source System <logical system name of your ERP
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:
Field Description Value
Organizational Unit Specifies the organizational OT-PORG-1
(C) SAP AG 36
Field Description Value
unit to be created
Description Description OT: Purchasing
Organization
On the Org. Data tab page:
Field Description Value
Org. ID Organizational unit ID. This is an internal number.
<Organizational unit
that you previously
defined>
Org. Unit Function Specifies the type of organizational unit
2 - Purchasing
Org. Unit Role Specifies the role of the organizational unit
1 - Organization
On the Address tab page:
Field Description Value
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.
4. Save your entries.
5. Repeat the procedure to create a purchasing group:
On the Basic Data tab page:
Field Description Value
Organizational Unit Specifies the organizational unit to be created
“OT-PGRP-1”
Description Description OT:Purchasing Group
On the Org. Data tab page:
Field Description Value
Org. ID Organizational unit ID. This is an internal number.
<Organizational unit
that you previously
defined>
Org. Unit Function Specifies the type of 2 - Purchasing
(C) SAP AG 37
Field Description Value
organizational unit
Org. Unit Role Specifies the role of the organizational unit
3 - Group
On the Address tab page:
Field Description Value
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.
6. Save your entries.
Create sales organization and group
On the Basic Data tab page:
Field Description Value
Organizational Unit Specifies the organizational unit to be created
OT-SORG-1
Description Description OT: Sales Organization
On the Org. Data tab page:
Field Description Value
Org. ID Organizational unit ID. This is an internal number
<Organizational unit
that you previously
defined>
Org. Unit Function Specifies the type of organizational unit
4 – Sales
Org. Unit Role Specifies the role of the organizational unit
1 – Organization
On the Address tab page:
Field Description Value
Subtype Defines the type of address Main Address
City City in the address Philadelphia
Country Country of the address U.S.
(C) SAP AG 38
7. Save your entries.
8. Repeat the procedure to create a purchasing group:
On the Basic Data tab page:
Field Description Value
Organizational Unit Specifies the organizational unit to be created
OT-SGRP-1
Description Description OT:Sales Group
On the Org. Data tab page:
Field Description Value
Org. ID Organizational unit ID. This is an internal number.
<Organizational unit
that you previously
defined>
Org. Unit Function Specifies the type of organizational unit
4 – Sales
Org. Unit Role Specifies the role of the organizational unit
3 – Group
On the Address tab page:
Field Description Value
Subtype Defines the type of address Main Address
City City in the address Philadelphia
Country Country of the address U.S.
9. Save your entries.
10. Create planning and execution organization and group
On the Basic Data tab page:
Field Description Value
Organizational Unit Specifies the organizational unit to be created
OT-PEORG-1
Description Description OT: Planning &
Organization
On the Org. Data tab page:
Field Description Value
Org. ID Organizational unit ID. This is an internal number.
<Organizational unit
that you previously
(C) SAP AG 39
Field Description Value
defined>
Org. Unit Function Specifies the type of organizational unit
13 – Planning and Execution
Org. Unit Role Specifies the role of the organizational unit
1 – Organization
On the Address tab page:
Field Description Value
Subtype Defines the type of address Main Address
City City in the address Philadelphia
Country Country of the address U.S.
11. Save your entries.
12. Repeat the procedure to create a purchasing group:
On the Basic Data tab page:
Field Description Value
Organizational Unit Specifies the organizational unit to be created
OT-PGRP-1
Description Description OT: Planning &
Execution Group
On the Org. Data tab page:
Field Description Value
Org. ID Organizational unit ID. This is an internal number.
<Organizational unit
that you previously
defined>
Org. Unit Function Specifies the type of organizational unit
13 – Planning & Execution
Org. Unit Role Specifies the role of the organizational unit
3 – Group
On the Address tab page:
Field Description Value
Subtype Defines the type of address Main Address
City City in the address Philadelphia
Country Country of the address U.S.
(C) SAP AG 40
13. Save your entries.
Result
You have defined a purchasing organization and group, sales organization and group, planning and execution organization and group.
(C) SAP AG 41
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 system>
-122,19,48 +47,59,59
(C) SAP AG 42
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.
4. Save your entries.
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.
7. Save your entries.
8. Create the zone OT-US-WEST in the header area, and on the Zone-Region tab, modify it
as follows:
Country Key Country Name Region Region Name
(C) SAP AG 43
Country Key Country Name Region Region Name
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.
10. Save your entries.
(C) SAP AG 44
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 OT-US-MIDWEST
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 45
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
3. Save your entries.
(C) SAP AG 46
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 Transportation
OT_FTL OT_FTL OT_FTL OT_FTL
Start Date 2000–01–01 2000–01–01 2000–01–01 2000–01–01
(C) SAP AG 47
End Date 2099–12–31 2099–12–31 2099–12–31 2099–12–31
Transportation Costs
Use TCM costs (when the maintained value is 0.0)
Use TCM costs (when the maintained value is 0.0)
Use TCM costs (when the maintained value is 0.0)
Use TCM costs (when the maintained value is 0.0)
Priority 1 2 3 4
TM Tendering: Consider TSP for P2P Tendering
X Blank X Blank
TM Tendering: Consider TSP for Broadcast Tendering
Blank X Blank X
(C) SAP AG 48
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
Mobile Phone (optional)
US cell phone number (ensure that the SMS-Enab. checkbox is selected. To display the 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 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 49
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 50
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.
3. Save your entries.
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.
8. Save your entries.
(C) SAP AG 51
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 52
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 53
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
1. In Customizing for SAP ERP, choose SAP Customizing Implementation Guide Sales 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 54
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
1. In Customizing for SAP ERP, choose SAP Customizing Implementation Guide 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:
Field Description Value
SOrg. Applicable sales organization 3000
DChl Applicable distribution channel
10
Dv Applicable division 00
SaTy Sales order type required to integrate the TM system
OTTL
SC Shipping conditions 01
Ctrl Key Control key 0001
TM No. Client number of the target TM system (consult with your Basis expert)
<custom 4-digit code>
(for example, B750)
3. Save your entries.
4. Choose Back (F3).
Result
The order type is now activated and can be integrated with the TM system.
(C) SAP AG 55
Text Determination in Sales Orders
Procedure
1. In Customizing for SAP ERP, choose SAP Customizing Implementation Guide Sales
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.
6. Choose Back (F3).
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).
Field Description Value
SeqNo Sequence number In accordance with the current sequencing
ID Identification TM01
Refer/Duplicate Reference Deselected
Text is obligat. Text is obligatory Text is not obligatory
Access seq. Access sequence 1
12. Save your entries.
(C) SAP AG 56
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.
4. Enter your data based on the following table:
Field Value Description
SalesDocTy OTTL Sales document type
Medium 8 Special function
Date/Time 4 Send immediately (when saving the application)
Language EN Language in which the output is to be produced
5. Save your entries.
(C) SAP AG 57
ERP Invoicing
(C) SAP AG 58
Mapping Organizational Units
Procedure
1. In Customizing for SAP ERP, choose SAP Customizing Implementation Guide Integration with Other SAP Components Transportation Management Invoice
Integration Invoicing Mapping of Organizational Units Assign Organizational Units
for Purchasing .
2. Choose New Entries.
3. Enter the data based on the following table:
Field Value
Logical System <Logical name of the connected TM
system>
TM Pur. Organization <Number of purchasing organization
/ OT-PORG-1>
TM Purchasing Group <Number purchasing group / OT-
PGRP-1>
Purchasing Org. 3000
Purch. Group P01
Plant 3100
Company Code 3000
4. Save your entries.
(C) SAP AG 59
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 60
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 61
Defining Conditions for Change Controller Strategies
Procedure
1. On the SAP Easy Access screen, call transaction NWBC to open SAP NetWeaver
Business Client.
2. Choose Application Administration General Settings Conditions Create Condition
.
3. On the New Condition Definition screen, enter your data based on the following table:
Field Value
Condition OT-CSDC-01
Description OT: Condition for Change
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
Qty Change True If quantity change is equal to “X”, return value is true; otherwise it is false
CC Strat. Start tend CC Strat: START TEND
(C) SAP AG 62
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.
5. Enter your data based on the following table:
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
7. Save your entries.
(C) SAP AG 63
Assigning ERP Text Types to TM Text Types for OTR
Procedure
1. In Customizing for SAP Transportation Management, choose SAP Customizing 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 .
2. Choose New Entries.
3. Enter your data based on the following table:
Field Description Value
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
4. Save your entries.
(C) SAP AG 64
Defining Service Levels
Procedure
1. In Customizing for Transportation Management, choose Forwarding Order
Management Define Transportation Service Level Codes .
2. Choose New Entries.
3. Enter your data based on the following table:
Field Value
Service Level Code TM
Description TM Service Level
4. Save your entries.
(C) SAP AG 65
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:
Field Description Value
Freight Unit Building Rule Specifies the FUBR to be created
OT_FUBR_01
Description Description of the FUBR OT: Freight Unit
Building Rule
Document Type Freight order type OTTL
Freight Unit Building Strategy Specifies how consolidation is carried out
Consolidate per Request (Compatible parts)
Process Controller Strategy (Advanced Settings tab page)
Strategy that defines how to build FUs
FUB_AUTO
Incompatibility Settings Not used Blank
Critical Quantity Defines the weight/volume limits for the freight unit
Gross Weight
Item Split Allowed
Indicator that specifies whether item quantities can be split across different freight units
Selected
On the Planning Quantities tab page:
Field Description Row 1 Row 2 Row 3
Planning Quantity for Freight Unit
Specifies the parameter for the planning
Gross Weight Gross Volume Pieces
(C) SAP AG 66
Field Description Row 1 Row 2 Row 3
Building quantity
Unit of Measure of Split Quantity
Unit of measure LB FT3 BAG
Split Quantity
Quantity limit for the item that forms the basis for building freight weights
40,000 0 0
Rounding Quantity
Any rounding quantity applied
1 1 1
4. Save your entries.
Result
You have created a freight unit building rule.
(C) SAP AG 67
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
1. In Customizing for SAP Transportation Management, choose SAP Customizing Implementation Guide SAP Transportation Management Transportation Management
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:
Field Description Value
OTR Type ID of the OTR document type OTTL
Description Description of the OTR type to be defined
Truck Load Order
Default Type
Only one OTR type can be defined as the default OTR type. Select this checkbox if there is only one OTR type defined in the system.
Deselected
In the Number Range Settings screen area:
Field Description Value
Number Range Interval
Number range used to assign the numbers to the OTR types. We use the number range as indicated.
02
In the Process Control / Business Object Mode screen area:
Field Description Value
BW Relevance Indicates whether the document type is relevant for BW
Selected
Automatic Freight Unit Building
Indicates whether the freight units are built automatically. If you select this checkbox, you
Selected
(C) SAP AG 68
Field Description Value
must specify an FU building rule.
Enable Approval Workflow Indicates that the approval workflow is activated.
Deselected
Automatic Block
Specifies whether the business documents of forwarding order management are blocked automatically. Only special creation channels are taken into consideration.
Deselected
Track Changes Specifies that changes are to be tracked
Selected
EM Integration Active Selected
Event Manager Logical system of the EM system.
EM Web Interface Transaction
Specifies the object that is to be processed in SAP Event Management
ODT20_FU
Retention Period Retention period (in days) before archiving
30
Output Profile Print profile used for this document type
/SCMTMS/TRQ_FWO_PRINT
Add. Output Profile Additional output profile Blank
Propagate Changes
Specifies how information is to be transferred if changes are made to the document (such as changes to quantities, and so on)
B – Synchronous Propagation
of Changes, Fallback to Asynchronous
In the Default Values screen area:
Field Description Value
Default Weight UoM Default unit of measure for the weight for this document type
LB
Default Volume UoM Default unit of measure for the volume for this document type
FT3
Plan on Req/Cnf Qty
Planning indicator that specifies the quantities (planned or confirmed) to be taken into account during
01 – Plan on Requested
Quantities
(C) SAP AG 69
Field Description Value
planning
Planning Profile
Specifies the planning profile that is used by the system when performing planning runs and creating transportation proposals for business documents of this type
Blank
Freight Unit Building Rule
Rule used when building freight units (if the Autom. FU Building checkbox is selected)
For information about defining the FUB rule, see Defining Freight Unit Building Rules. [Page 65]
OT_FUBR_01
FU Building Rule Condition
You can specify a condition for determining a freight unit building rule that is used when freight units are created for business documents of this type.
None
4. Save your entries.
(C) SAP AG 70
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
1. On the SAP Easy Access screen, call transaction NWBC to open the SAP Business Client.
2. Choose Application Administration General Settings Conditions Create Condition
/ 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:
Field Description Value
Condition Condition type supplied by the system
ZOTR_TYPE
Description Description of the condition type
OTR Type Determination
Condition
In the Settings screen area:
Field Description Value
Condition Type Condition type supplied by the system
/SCMTMS/OTR_TYPE
Origin of Condition Source of the condition information
Condition based on BRFplus Decision Table
5. In the Decision Table of the Data Access Definition tab page, enter the following data:
Field Description Value
(C) SAP AG 71
Field Description Value
BseDoc. Ty. Incoming base document type Parameter: “is equal to”
Value: 114 – Sales Order
Proc Type
This respective column is available after saving the condition.
Procedure type (incoming parameter)
OTTL (the document type for
the incoming order defined above)
Parameter: “is equal to”
Value: OTTL
OTR Type
Specify the data for integration here – the document type that is identified and used in SAP TM for OTR.
OTTL (defined in a previous
step)
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 72
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 .
3. Enter your data based on the following table:
Field Value
Delivery Profile OT_DELV_PRFL_STAN
Description Delivery Profile for Outsourced
Transportation
Fix Planning Results Selected
Delivery Creation Per OTR
4. Save your entries.
(C) SAP AG 73
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:
Field Description Value
Tendering Type Determines how tendering is carried out
Peer-to-Peer Tendering, Response Required
Tender is sent to one carrier and a confirmation is required from this carrier
Tendering Process Tendering process mode RFQ-Based, Award Automatically
Carrier Carrier Blank
Freight RFQ Sequence Number
Freight RFQ sequence number
Blank
Carrier Assignment Method Determines how carriers are assigned to the freight order
Get Carriers from Ranking List
A ranking list is provided from which carriers are selected
Relative Price Limit Relative price 100
Carrier-Specific Freight Agreement
Carrier-specific freight agreement
Selected
Maximum Response Duration Maximum time within which the carrier must respond to an RFQ
2:00
The RFQ is confirmed in the freight order when the program that checks the responses is executed.
(C) SAP AG 74
Field Description Value
If you want to run this report manually, on the SAP Easy Access screen choose
Application Administration
Background Reports
Background Processing of
Tendering .
Visibility Settings
Defines the visibility setting for RFQ, that is, whether prices are displayed, whether the carrier can change the prices, and so on
OT_VIS_SET
This setting is defined in the next chapter.
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:
Field Description Value
Tendering Type Determines how tendering is carried out
Broadcast Tendering – Best Offer
Tender is sent to all carriers and a confirmation is required from each carrier
Tendering Process Tendering process mode RFQ-Based, Award Automatically
Carrier Carrier Blank
Freight RFQ Sequence Number
Freight RFQ sequence number
Blank
Carrier Assignment Method Determines how carriers are assigned to the freight order
Get Carriers from Ranking List
A ranking list is provided from which carriers are selected
Relative Price Limit Relative price 100%
Carrier-Specific Freight Agreement
Carrier-specific freight agreement
Deselected
Maximum Response Duration Maximum time within which the carrier must respond to an
0:15
The RFQ is confirmed in the
(C) SAP AG 75
Field Description Value
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 .
Visibility Settings
Defines the visibility setting for RFQ, that is, whether prices are displayed, whether the carrier can change the prices, and so on
OT_VIS_SET
This setting is defined in the next chapter.
7. Save your entries after maintaining the visibility settings in the next section.
(C) SAP AG 76
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
1. In Customizing for SAP Transportation Management, choose SAP Customizing Implementation Guide SAP Transportation Management Transportation Management
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:
Field Description Value
Visibility Setting Unique name for the profile setting for tendering visibility
OT_VIS_SET
Vis. Stngs Desc. Description of the visibility settings profile
OT: Visibility
Settings
Stop Dates Visib.
Specifies whether the stop dates are displayed for the carrier when the carrier receives the RFQ
ER, Editable, Relevant
Price Limit Specifies whether the price limit set for this tender is displayed for the carrier
RO Read Only
Subm. Price Visib.
Specifies whether the price for this tender is displayed for the carrier and whether the carrier can change the offer
ER, Editable Relevant
4. Save your entries.
5. Double-click 02 — Rejection Reason Codes and choose New Entries.
6. Enter your data based on the following table:
Field Description Value
Reason Here, a list is created from which the carrier can select a value to reject an RFQ
01 – No Capacity
02 – No Time
03 – No Reason to Provide
7. Save your entries.
8. Double-click 04 — Process Settings and choose New Entries.
(C) SAP AG 77
9. Create an entry based on the following table:
Field Description Value
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
Carrier Settings
Defines the carrier selection that you want to use for the automatic carrier proposal in the tendering process. For more information, see Defining Carrier Selection Settings [Page 85].
OT_CARR_SEL_01
Max. Resp. Times [h]
Defines the maximum period for the carrier to respond to the freight request for quotation (RFQ) in these process-related settings
Blank
BP Calling Hours Defines whether you want to take the calling hours of your business partner into account
Deselected
Review Threshold [%]
Allows the carrier to submit a price that deviates by the percentage defined here from the price you submitted in the freight request for quotation (RFQ)
5%
Restart Tendering
Defines that the tendering process is restarted automatically if the awarded carrier rejects the freight order
Selected
Calculate Charges after Tendering
None Deselected
10. Save your settings.
11. Double-click 05 — Communication Settings and choose New Entries.
12. Create an entry based on the following tables:
Header area:
Field Description Value
Comm. Settings Name of the communication profile setting to be created
OT_COMM_SET
(C) SAP AG 78
05 — Communication Settings screen area:
Field Description Value
Trigger Alerts w/o Subscription to Alert Category
If you select this checkbox, alerts are sent to tendering managers even if they have not subscribed to the alert category.
Selected
Send EDI Messages Created EDI massages for the alerts
Deselected
E-Mail screen area:
Field Description Value
Send RFQ Create RFQ by e-mail Selected
Send Notification for Canceled Tendering
Create notification for canceled tendering
Selected
Send Notification for Sent RFQs
Send notification e-mails for sent freight RFQs
Deselected
Send Notification for Awarded Quotation
Create notification e-mails for accepted freight quotations
Selected
Send Notification for Rejected Quotation
Create notification e-mails for rejected freight quotations
Selected
SMS screen area:
Field Description Value
Send RFQ Create RFQ by SMS Deselected
Send Notification for Canceled Tendering
Create notification for canceled tendering
Selected
Send Notification for Sent RFQs
Send notification SMS for sent freight RFQs
Selected
Send Notification for Awarded Quotation
Create notification SMS for accepted freight quotations
Selected
Send Notification for Rejected Quotation
Create notification SMS for rejected freight quotations
Selected
13. Save your settings.
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 79
Field Description Value
Carrier Carrier number for which specific communication settings are to be created
OT-CAR-01
06 – Carrier-Specific Communication Settings screen area:
Field Value
Create EDI Messages Selected
E-mail for Canceled Tendering Selected
16. Save your settings.
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:
Field Description Value
Tendering Process Settings Default process settings
Any process setting that you want to specify as the default setting (for example,
_DEFAULT)
Tendering Comm. Settings Default communication settings
Any communication setting that you want to specify as the default setting (for example,
_DEFAULT)
18. Save your entries.
19. Choose Back (F3).
Result
You have configured the profile settings for tendering.
(C) SAP AG 80
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
1. On the SAP Easy Access screen, call transaction NWBC to open the SAP Business Client.
2. Choose Application Administration General Settings Conditions Create Condition
.
The New Condition Definition screen appears.
3. Enter your data based on the following settings.
Field Description Value
Condition Unique identifier OT_INC_COND_CARR
Description Description of condition OT-Incomp cond –
Carrier
Condition Type Select the appropriate condition type here
/SCMTMS/INC_CARRIER
Origin of Condition Specify the origin of the condition
Direct Business Object 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:
Field Description Value
Data Element Used for Input Help
This value is populated automatically based on your entries in Configuring Incompatibility Settings [Page 84].
BU_PARTNER
Name of BO Used in Condition
BO used to obtain the information about the incompatibility
/SCMTMS/SUPPLIER
Name of BO Node Used in Condition
BO node used to obtain the information
ROOT
Name of the Field of BO Node Field used to obtain the value for the incompatibility
PARTNER
7. Save your entries.
(C) SAP AG 81
8. Create the second condition based on the following attributes.
Field Description Value
Condition Unique identifier OT_INC_COND_CUST
Description Description of condition OT-Incomp cond –
Customer
Condition Type Select the appropriate condition type here
/SCMTMS/INC_TO
Origin of Condition Specify the origin of the condition
Direct Business Object Access
9. In the Data Access Definition table:
Field Description Value
Data Element Used for Input Help
This value is populated automatically based on your entries in Configuring Incompatibility Settings. [Page 84]
/SCMTMS/PTY_CONSIGNEE
Name of BO Used in Condition
BO used to obtain the information about the incompatibility
/SCMTMS/TOR
Name of BO Node Used in Condition
BO node used to obtain the information
ROOT
Name of the Field of BO Node Field used to obtain the value for the incompatibility
CONSIGNEEID
10. Save your entries.
(C) SAP AG 82
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
1. On the SAP Easy Access screen, call transaction NWBC to open the SAP Business Client.
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:
Field Description Value
Incompatibility Name of the incompatibility OT_INCOMP_CAR_CUST
Description Description of the incompatibility
OT-Carrier-Cust
Incompatibility
Incompatibility Area Applicable TM area O5 – Carrier Selection
Incompatibility Type Further definition of the incompatibility – where is it applicable?
81 – Carrier – Transportation
Order
Determination Method Defines how values are determined for the incompatibility
Condition-Based Incompatibility
Manual Violation
System response if this incompatibility is violated due to a manual assignment of values
Warning If Incompatibility Is Violated
Automatic Violation System response if this incompatibility is violated due
Incompatibility Must Not Be
(C) SAP AG 83
Field Description Value
to an automatic assignment of values
Violated
Conditions screen area:
Field Description Value
First condition:
Condition
Incompatibility condition to be used. The condition can be created directly from the link in this field.
OT_INC_COND_CARR
Relevant Condition Result Incompatibility setting outcome
OT-CR-01
Second condition:
Condition
Incompatibility condition to be used. The condition can be created directly from the link in this field.
OT_INC_COND_CUST
Relevant Condition Result Incompatibility setting outcome
OT-CU-01
4. Save your entries.
More Information
For more information, see Defining Conditions for Incompatibilities [Page 80].
(C) SAP AG 84
Configuring Incompatibility Settings
Incompatibility settings are used to inform SAP Transportation Management of the current conditions for the incompatibility.
Procedure
1. On the SAP Easy Access screen, call transaction NWBC to open the SAP Business Client.
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:
In the General Data screen area:
Field Description Value
Incompatibility Settings Unique ID for the incompatibility settings
OT_INCOMP_SET_001
Description Description of the incompatibility settings
OT Incomp. Settings
Incompatibility Area Area in which the incompatibility is to be applied
Carrier Selection
Default Incompatibility Settings
If you select this checkbox, the system uses the default incompatibility settings.
Deselected
4. Choose Insert.
5. Enter your data based on the following table:
Field Description Value
Incompatibility Incompatibility defined above OT_INCOMP_CAR_CUST
Violation in Manual Planning
Action to be carried out if the incompatibility is violated and the location from which to derive the follow-on actions
According to Incompatibility Definition
Violation in Automatic Planning
Action to be carried out if the incompatibility is violated and the location from which to derive the follow-on actions
According to Incompatibility Definition
6. Save your entries.
Result
The setting is assigned to the carrier selection setting.
(C) SAP AG 85
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:
In the General Data screen area:
Field Description Value
Carrier Selection Settings Unique ID of the settings profile
OT_CAR_SEL_02
Description Carrier selection description OT: General Carrier
Selection Profile
Check Incompatibilities Indicates that incompatibilities are to be taken into account when selecting a carrier
Selected
Incompatibility Settings Enter a profile if incompatibilities are to be checked
OT_INCOMP_SET_001
(For more information, see Configuring Incompatibility Settings [Page 84])
Type of Carrier Selection Settings
Type of carrier General Carrier Selection
In the Other Settings screen area:
Field Description Value
Trsp. Alloc. Usage
Specify whether the transportation allocation usage is to be activated when the carrier is selected
Use Transportation Allocations
BS Usage
Indicates whether the business share (BS) settings for the carrier are to be taken into account when selecting carriers
Do Not Use Business Shares
Strategy Which strategy is to be used to select the carrier?
Costs
(C) SAP AG 86
Field Description Value
Strategies can be based on costs, priorities, or a combination of the two.
Carrier Cost Origin If the strategy is cost-based, this field specifies the cost origin for selecting the carrier
Use Transportation Charges from TCM
On the Advanced Settings tab page:
Field Description Value
Planning Strategy Planning strategy for selecting carriers
TSPS_DEF
Optimizer Runtime
Runtime for the optimizer run used to select the carrier. This prevents processes from running indefinitely.
6
Consider Manual Assignment as Fixed
Consider this assignment as the final carrier assigned to the freight order
Deselected
Action for Manual Rankings
Specifies whether the manual planning list can be entered during the planning process and how the manual entries are to be handled
Remove
Overall Carrier Availability Overall carrier availability Deselected
Common Currency Currency used to calculate costs
USD
Action After Carrier Selection Run
Action that is to be performed once the carriers have been selected
Automatic Tendering
Continuous Move Type
Specifies how carriers are to be selected based on the continuous move opportunities
Do Not Create Continuous Move
Continuous Move Information Specifies whether continuous move possibilities are to be considered
Selected
Reaction to CM Removal Reaction to CM removal Blank
Check Dist. and Dur.
Determines whether the distance of the locations and the duration of the trip are to be taken into consideration
Deselected
(C) SAP AG 87
Field Description Value
Continuous Move MTr. Check
Determines whether continuous move means of transport are to be taken into consideration
Deselected
CM Cost Recalculation for TCM
Active if continuous move is used to select carriers
No Recalculation
Use Tendered Objects for Optimization
Use tendered objects for optimization
Deselected
Tender Without Optimizer Result
Tender without optimizer result
Deselected
Tendering Manager User ID of the manager <User ID of the
tendering manager>
Tendering Profile Tendering profile to be used in automatic tendering
OT-TEND-PROFILE
3. Save your entries.
4. Repeat this process to create settings for the tendering profile based on the following tables.
In the General Data screen area:
Field Description Value
Carrier Selection Settings Unique ID of the settings profile
OT_CARR_SEL_01
Description Carrier selection description OT: CS Profile for Tendering
Check Incompatibilities Indicates that incompatibilities are to be taken into account when selecting a carrier
Selected
Incompatibility Settings Enter a profile if incompatibilities are to be checked
OT_INCOMP_SET_001
(For more information, see Configuring Incompatibility Settings [Page 84])
Type of Carrier Selection Settings
Type of carrier Carrier Selection for Tendering
In the Other Settings screen area:
Field Description Value
Trsp. Alloc. Usage Specify whether the transportation allocation usage is to be activated when
Use Transportation Allocations
(C) SAP AG 88
Field Description Value
the carrier is selected
On the Advanced Settings tab page:
Field Description Value
Planning Strategy Planning strategy for selecting carriers
TSPS_DEF
Overall Carrier Availability Overall carrier availability Deselected
5. Save your entries.
(C) SAP AG 89
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
1. In Customizing for SAP Transportation Management, choose SAP Customizing Implementation Guide SAP Transportation Management Transportation Management
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:
Field Description Value
Freight Order Type Unique 4-character ID of the FOR that is to be defined
OTTL
Description Description of the FOR to be defined
Truck Load Order
In the Basic Settings screen area:
Field Description Value
Freight Order Can Be Subcontracted
Indicator that specifies whether this FOR type can use subcontracting processes
01 – Relevant for
Subcontracting
Shipper/Consignee Determination
Determines how the shipper and consignee partners are determined for this FOR
P – Determine Based on
Predecessor Documents (if these are not unique, use the setting for locations)
Fix Document When Saving Selected
(C) SAP AG 90
Field Description Value
Freight Order Can Be Deleted Specifies whether the FOR can be deleted once it has been created
Selected
Enable Settelment Enables settlement Selected
Enable Charge Calculation Enables charge calclation Selected
In the Number Range Settings screen area:
Field Description Value
Time for Drawing Specifies the time at which a number is assigned to the FOR document
Draw Number When Saving Document
Number Range Interval Number range that is to be used for this document type
02
In the Change Controller Settings screen area:
Field Description Value
Default Change Strategy
Default strategy used for tendering behavior when changes are made to the FOR key fields, such as partners, quantities, and so on
DEF_CHACO
Change Strategy Determination Cond.
Specifies the condition that the system is to use to determine a change controller strategy at runtime.
If you have defined several change controller strategies, you can use a condition to determine the appropriate change controller strategy.
The condition type of this condition is /SCMTMS/CC_TOR_STRAT.
OT-CSDC-01
Quantity Tolerance Condition
Specifies the tolerances for a quantity change in a business document.
The condition type of this condition is /SCMTMS/CC_QUAN_TOL.
OT_QTOL_01
Date Tolerance Condition Specifies the tolerances for a date change in a business
Blank
(C) SAP AG 91
Field Description Value
document
In the Additional Strategies screen area:
Field Description Value
Creation Strategy
Specifies tasks that the change controller is to perform when you create one of the following business documents:
Freight order
Freight booking
Transportation unit
Freight unit
CARR_SEL
Save Strategy
Specifies tasks that the change controller is to perform when you save the freight order.
The strategy definition is explained in a separate step below.
Blank
Deletion Strategy
Specifies tasks that the change controller is to perform when you delete the freight order.
CANCEL_CAP
In the Execution Settings screen area:
Field Description Value
Execution Track. Relev.
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). The system then sets the 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
3 – Execution Tracking with
External Event Management
(C) SAP AG 92
Field Description Value
execution status to Not Relevant.
Immediate Processing
Indicator that sets the status In Process immediately as soon as the document is created and saved
Selected
Check Condition “Ready for Exec”
Not used Blank
Propagate Execution Info Propagates the execution information to the predecessor document
Deselected
In the Event Management Settings screen area:
Field Description Value
Application Object Type
Type of application object to be tracked in the application system (required to determine whether an application object is relevant for Event Management). The event manager processes only the event messages for these objects.
ODT20_TO
Last Exp. Event Last expected event for a document, for example, the Unload_End.
POD
In the Service Level Determination screen area:
Field Description Value
Default Service Level Default service level code for the business document type
Blank
Service Level Cond. Condition for service level determination
Blank
In the Default MTr Determination screen area:
Field Description Value
Default MTr for Type Specifies the default means of transport for this freight order type
OT-FTL
Condition for Def MTr Name of the condition for the default means of transport
Blank
In the Tendering Settings screen area:
(C) SAP AG 93
Field Description Value
Use Default Settings
Indicates that the Customizing settings for tendering are determined in accordance with the default settings
Deselected
Use Condition for Sett. Determ. Tendering Condition Definition
Indicates that the Customizing settings for tendering are determined using conditions.
Deselected
Use Type Specific Settings
Enables you to further define the FOR-type-specific processes for process settings and communication settings.
Selected
Process Settings
Specifies the tendering process settings.
Identifies process-related settings, for example:
o Default tendering manager
o Maximum response duration
o Tendering profile
The section below explains this setting in more detail.
OT_PROCESS_SETTINGS
Communication Settings
Indicates the strategy for tendering communication. This profile is defined in a separate stage below.
OT_COMM_SET
In the Default Units of Measure screen area:
Field Description Value
Weight Weight US Pound
Volume Volume Cubic Foot
In the Output Options screen area:
Field Description Value
Output Profile Output profile /SCMTMS/TOR_PRINT_ROAD
Add. Output Profile Additional output profile Blank
(C) SAP AG 94
Field Description Value
Text Schema Text schema OT0001
Dynamic Determination of Output
Dynamic determination of output profile
Deselected
In the Additional Settings screen area:
Field Description Value
Dangerous Goods Profile Defines the dangerous goods profile
Blank
Customs Profile Defines the customs profile Blank
Default FSD Type Default FSD type
Enter the FSD type that you defined in Defining Freight Settlement Document Types [Page 96]
HBL Number Range
Indicates the number range interval for the freight order type, freight booking type, freight unit type, or transportation unit type.
Blank
Default Carrier Selection Profile
Carrier selection profile determined when the save strategy is triggered
OT_CAR_SEL_02
Default Carrier Selection Condition
Condition for defining the default carrier selection profile
Blank
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 Days
Retention period in days before archiving
Zero
Web Dynpro Application Config.
Defines the Web Dynpro application configuration that is loaded if a business document of forwarding order management is opened with this type
Blank
In the Organizational Unit Determination screen area:
Field Description Value
Execution Org. ID of the organizational unit that is defined as:
<Your organizational
unit>(OT-PORG-1)
(C) SAP AG 95
Field Description Value
Unit function 13 – planning and execution
Unit role 1 – organization
Purchase Org.
ID of the organizational unit that is defined as:
Unit function 2 – purchasing
Unit role 1 – organization
<Your purchasing
organization>(OT-PEORG-1)
Execution Group
ID of the organizational unit that is defined as:
Unit function 13 – planning and execution
Unit role 3 – group
<Your execution
group>(OT_PEGRP-1)
Purchasing Group
ID of the organizational unit that is defined as:
Unit function 2 – purchasing
Unit role 3 – group
<Your purchasing
group>(OT-PGRP-1)
Consider Organization Unit of User
Specifies that the organizational unit of the user is to be taken into account
Deselected
Condition Condition Blank
1. Save your entries.
2. Choose Back (F3).
Result
You have defined the new freight order type.
(C) SAP AG 96
Defining Freight Settlement Document Types
Procedure
1. In Customizing for SAP Transportation Management, choose SAP Customizing Implementation Guide SAP Transportation Management Transportation Management
Settlement Freight Settlement Define Freight Settlement Document Types .
2. Choose New Entries.
3. Enter your data based on the following table:
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
4. Save your entries.
(C) SAP AG 97
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 98
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 .
2. Choose New Entries.
3. Enter the data for your scale based on the following table:
Tab Page Field Description Value
General Data
Scale Scale ID OT-SCALE-LOC
Description Description of the scale
OT – Origin
Location Scale
Scale Base
Defines the basis of scale, for example, location, distance, duration, and so on.
LOC – Location
Items
Calculation Type Defines how the scale values are read
Absolute
(values are read directly)
Internal Location Define Location relevant for scale
SP3100@<logical
system>
4. Save your entries.
5. Create a new scale:
Tab Page Field Description Value
General Data
Scale Scale ID OT-SCALE-
CUSTOMER
Description Description of the scale
OT – Customer
base scale
Scale Base
Defines the basis of scale, for example, location, distance, duration, and so on.
BP – Business partner
Items BP Number Define Business Partner relevant for scale
OT-CU-01
(C) SAP AG 99
Tab Page Field Description Value
Calculation Type Defines how the scale values are read
Absolute
6. Save your entries.
7. Create a new scale:
Tab Page Field Description Value
General Data
Scale Scale ID OT-SCALE-REGION
Description Description of the scale
OT – Regions
Scale Base
Defines the basis of scale, for example, location, distance, duration, and so on.
Region
Items
Region Defines the region relevant to the scale
WA
Calculation Type Defines how the scale values are read
Absolute
8. Save your entries.
(C) SAP AG 100
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-RATE-CR-03
OT-RATE-CR-04
OT-SCALE-LOC
OT-SCALE-REGION FB00 – Base Freight
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:
Field Description Value
Rate Table Unique identifier for the rate table
OT-RATE-CR-01
Description Description of the table OT – FTL Rate from
Location to Region
Charge Usage
Specifies the scenario in which the rate table can be used, for example, for customer billing integration, supplier invoice integration, or none
Service Provider
Charge Type Here, the charge type is linked for integration with SAP ERP.
FB00 – Base Freight
Value Type Absolute value
4. Choose the Scales tab page.
5. Enter the scales based on the following table:
(C) SAP AG 101
Field Description Value
Scale Reference
Enter the scales defined in Defining Scales [Page 98]. This activates the entries in the rate table as specified by the relevant sequence.
1: OT_SCALE_LOC
2: OT_SCALE_REGION
Calculation Base
Determines how the values are stored and calculated for this dimension. Sources of information are predefined based on the object.
1: SOURCELOC
2: DESTLOC_REG
6. Select each line and choose Create Scales.
7. Save your entries.
8. Choose the Dates and Values tab page.
9. Enter your data based on the following table:
Field Description Value
Valid From The date as of which the rate table is valid
Today
Valid To The date to which the rate table is valid
2099–12–31
Currency Currency that is applicable for this rate table
USD
Values in Table
Once you have entered the validity dates, you can create table entries for the dimension. To do so, select the row containing the validity dates.
Source Location:
SP3100@<logical
system>
Destination Region: WA
Value:
1.48 (for OT-RATE-CR-01)
1.45 (for OT-RATE-CR-02)
1.40 (for OT-RATE-CR-03)
1.52 (for OT-RATE-CR-04)
10. On the Calculation Rules tab page, enter your data based on the following table:
Field Description Value
Calculation Base
Provides the calculation base for this rate. In our rate table, the rates are specified as per/mile from source to
ACTUAL_DIST
(C) SAP AG 102
Field Description Value
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.
Quantity
Defines the multiplier for the calculation base. For example, the applicable rate can be per mile or per 100 miles.
1
Unit of Measure The unit of measure specifies the unit to which the multiplier is applied.
MI
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)
o OT-RATE-FB00-CAR-03 (for carrier OT-CR-03)
o OT-RATE-FB00-CAR-04 (for carrier OT-CR-04)
13. For the fuel surcharge, add another table based on the following data:
Field Description Value
Rate Table Unique identifier for the rate table
OT-RATE-FUEL
Description Description of the table
OT – Destination
Dependent Fuel
Surcharge
Charge Usage
Specifies the scenario in which the rate table can be used, for example, for customer billing integration, supplier invoice integration, or none
Service Provider
Charge Type Here, the charge type is linked for integration with SAP ERP.
FUEL – Fuel Surcharge
Value Percentage Value
(C) SAP AG 103
14. Choose the Scales tab page.
15. Enter the scales based on the following table:
Field Description Value
Dimension
Defines a row (x-axis) or column (y-axis) in the rate table. A rate table can contain multiple scales (up to 9).
1 for the first scale
Scale Reference
Enter the scales defined in Defining Scales [Page 98]. This activates the entries in the rate table as specified by the relevant sequence.
1: OT-SCALE-REGION
Calculation Base
Determines how the values are stored and calculated for this dimension. Sources of information are predefined based on the object.
1: DESTLOC_REG
16. Choose the Dates and Values tab page.
17. Enter your data based on the following table:
Field Description Value
Valid From The date as of which the rate table is valid
2010–01–01
Valid To The date to which the rate table is valid
2012–12–31
Life Cycle Status
Once the rate table is fully defined, it must be set to Released so that it can be used further. If the rate table is still in process, you can leave it as Deactivated.
The system sets the value based on the follow-up action using the following menu:
Set Status Released
Currency Currency that is applicable for this rate table
USD
Values in Table
Once you have entered the validity dates, you can create table entries for the dimension. To do so, select the row containing the validity dates.
Destination Region Location: WA
Value: 0.05
18. Release and save your data.
19. For the lumper charges, add another table based on the data below:
Field Description Value
(C) SAP AG 104
Field Description Value
Rate Table Unique identifier for the rate table
OT-RATE-LMPR
Description Description of the table OT – Lumper Rates
Charge Usage
Specifies the scenario in which the rate table can be used, for example, for customer billing integration, supplier invoice integration, or none
Service Provider
Charge Type Here, the charge type is linked for integration with SAP ERP.
LMPR – Lumper Charges
Value Percentage Value
20. Choose the Scales tab page.
21. Enter the scales based on the following table:
Field Description Value
Dimension
Defines a row (x-axis) or column (y-axis) in the rate table. A rate table can contain multiple scales (up to 9).
1 for the first scale
Scale Reference
Enter the scales defined in Defining Scales [Page 98]. This activates the entries in the rate table as specified by the relevant sequence.
1: OT_SCALE_CUSTOMER
Calculation Base
Determines how the values are stored and calculated for this dimension. Sources of information are predefined based on the object.
SHIP_TO_PARTY
22. Choose the Dates and Values tab page.
23. Enter your data based on the following table:
Field Description Value
Valid From The date as of which the rate table is valid
2010–01–01
Valid To The date to which the rate table is valid
2012–12–31
Life Cycle Status Once the rate table is fully defined, it must be set to
The system sets the value based on the follow-up action
(C) SAP AG 105
Field Description Value
Released so that it can be used further. If the rate table is still in process, you can leave it as Deactivated.
using the following menu:
Set Status Released
Currency Currency that is applicable for this rate table
USD
Values in Table
Once you have entered the validity dates, you can create table entries for the dimension. To do so, select the row containing the validity dates.
Ship-to Party: OT-CU-01
Value: 50.00
24. Release and save your data.
(C) SAP AG 106
Defining Calculation Sheets
Within a freight order or forwarding order, the applicable charges are calculated on the basis of the calculation sheet.
Procedure
1. On the SAP Easy Access screen for SAP Transportation Management, choose SAP 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:
Field Description Value
Calculation Sheet Unique identifier for the calculation sheet to be defined
OT-TCCS-CR-01
OT-TCCS-CR-02
OT-TCCS-CR-03
OT-TCCS-CR-04
Description Description of the calculation sheet
OT-TCCS for CR01
OT-TCCS for CR 02
OT-TCCS for CR 03
OT-TCCS for CR 04
Charge Usage
Indicates whether the calculation sheet is used for customers, vendors (carriers), both, or neither. Furthermore, indicates whether the calculation sheet is used only for decision making during tendering, and so on.
2 – Service Provider
Items screen area:
Field Description Value
Item
Indicates the levels of the charge elements in the calculation sheet as well as the descriptions derived from the assigned charge types
Enter your items by choosing Insert. In our scenario, we use the following values:
Base freight (FB00)
(C) SAP AG 107
Field Description Value
Fuel surcharge (FUEL)
Lumper charges (LMPR)
Line No. Defines the sequence in which the charge types are executed
Entered by the system
Instruction Type
Defines the relationship between charge types and how the charges are to be calculated for each charge type. For example, you can specify whether the item represents a total or a direct calculation of the charge.
FB00: Standard
FUEL: Standard
LMPR: Standard
Charge Type Specify the TM charge type for each item.
FB00
FUEL
LMPR
Description
This is a freely definable description and is subsequently displayed in the documents. We recommend that you use descriptions that make sense in a number of contexts.
-
Mandatory Denotes the charge type as mandatory
Deselected (for all of our charge types)
Currency Applicable currency USD (Not applicable for
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:
On the Basic Data tab page:
Field Description Value
Instruction Type Rule to indicate how the charge item is applied for the calculation
Standard
Description Description of the charge item in the calculation sheet
Base Freight – Dist
Based
Charge Type Assigned charge type FB00
(C) SAP AG 108
Field Description Value
Line No. Line number of the item 20
Calculation Resolution Base
Indicates the level at which the calculation sheet is to be applied. For example, it can be applied at the header level for the whole freight order or at a particular stage only.
ROOT
The calculation sheet applies to the whole document.
Calculation Method Type Calculation method type Standard
On the Rate tab page:
Field Description Value
Rate Table Assigned rate table
OT-RATE-CR-01
OT-RATE-CR-02
OT-RATE-CR-03
OT-RATE-CR-04
6. Choose Save.
7. Select the line for the fuel surcharge.
8. In the area of the bottom of the screen, enter your data based on the following information:
On the Basic Data tab page:
Field Description Value
Instruction Type Rule to indicate how the charge item is applied for the calculation
Standard
Description Description of the charge item in the calculation sheet
Fuel Surcharge
Charge Type Assigned charge type FUEL
Line No. Line number of the item 30
Calculation Method Type Calculation method type Standard
Reference-From Line No. Reference item that forms the basis of the calculation for this row
20
On the Rate tab page:
Field Description Value
(C) SAP AG 109
Field Description Value
Rate Table Assigned rate table OT-RATE-FUEL
9. Choose Save.
10. Select the line for the lumper charges.
11. In the area of the bottom of the screen, enter your data based on the following information:
On the Basic Data tab page:
Field Description Value
Instruction Type Rule to indicate how the charge item is applied for the calculation
Standard
Description Description of the charge item in the calculation sheet
Lumper Charges
Charge Type Assigned charge type LMPR
Line No. Line number of the item 40
Calculation Method Type Calculation method type Standard
On the Rate tab page:
Field Description Value
Rate Table Assigned rate table OT-RATE-LMPR
12. Choose Save.
(C) SAP AG 110
Defining Freight Agreement Types
Procedure
1. In Customizing for SAP Transportation Management, choose SAP Customizing Implementation Guide SAP Transportation Management Transportation Management
Master Data Agreements and Service Products Define Freight Agreement Settings
.
2. Choose New Entries.
3. Enter your data based on the following table:
Field Description Value
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.
5. Save your entries.
(C) SAP AG 111
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
1. On the SAP Easy Access screen for SAP Transportation Management, choose SAP 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:
Field Description Value
Agreement Agreement ID OT-FA-CR-01
Description Description of the freight agreement
FA: OT-CR-01
Purchasing Organization Default purchasing organization
<Your purchasing
organization>
Carrier Carrier for which this freight agreement is to be defined
OT-CR-01
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:
Field Description Value
Item Number Item number 10
Calculation Sheet
Assign the calculation sheet once only. The details from this sheet are copied for each item.
OT-TCCS-CR-01
(C) SAP AG 112
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 Agreement
Description Carrier Calculation Sheet
OT-FA-CR-02 FA: OT-CR-02 OT-CR-02 OT-TCCS-CR-02
OT-FA-CR-03 FA: OT-CR-03 OT-CR-03 OT-TCCS-CR-03
OT-FA-CR-04 FA: OT-CR-04 OT-CR-04 OT-TCCS-CR-04
(C) SAP AG 113
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
1. In Customizing for SAP Transportation Management, choose SAP Customizing Implementation Guide SAP Transportation Management Transportation Management
Settlement Define Settlement Profile .
2. Choose New Entries.
3. Enter your data based on the following table:
Field Description Value
Settlement Prof Settlement profile OT_SP_01
Medium Desc. Medium description Settlement Profile
Data Source Identifies the data source to be used when creating settlement documents
Planned Data
Split/Cons.
Defines the split / consolidation criteria for generating settlement documents
FSD_CREAT
Calculation Option
Specifies how the values are calculated when the invoice is created. You can copy fixed charges and recalculate others, or copy all charges.
A Copy Fixed Charges and
Redetermine Others
Collective Invoice Collective invoice Selected
4. Save your entries.
(C) SAP AG 114
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:
Field Description Value
Calculation Profile Calcution Profile OT_CLCPRF
Description Description OT: Charge Calculation
Profile
Calc. Date Ty. Calcuation Date Type EET_DATE (Expected End
Date of Complete Carriage)
Calculation Level Calculation Level 1 (Calculation on Header
Level)
Agr. Det. Rule Freight Agreement Determination Rule
Blank
Calc Sheet Det. Rule Calculation Sheet Determination Rule
Blank
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
3. Save your entries.
(C) SAP AG 115
Configuring Organizational Settings for Charge Elements
Procedure
1. In Customizing for SAP Transportation Management, choose SAP Customizing Implementation Guide SAP Transportation Management Transportation Management
Basic Functions Charge Calculation Basic Settings for Charge Calculation Define
General Settings .
2. Choose New Entries.
3. Enter your data based on the following table:
Field Description Value
Org. Unit Purchasing organization unit Internal ID of OT-PORG-1 (for
example, 500000627)
Default Purch. Org. Default purchasing organization
Blank
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
4. Save your entries.
(C) SAP AG 116
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 117
Defining Transportation Allocations
Procedure
1. On the SAP Easy Access screen, call transaction NWBC to open the SAP Business Client.
2. Choose Planning Transportation Allocation Create Transportation Allocation .
3. Enter your data based on the following tables:
In the Creation Options screen area:
Field Description Value
Transportation Lane Reference
Transportation lane reference Corresponding Transportation Lane Must Exist
Overwrite Existing Buckets Overwrite existing buckets Deselected
Display Type Display type Display all
In the Trade Lanes screen area:
Field Description Value
Orientation Defines the transportation lane
Along
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:
Field Description Value
Carrier Carrier
OT-CR-01
OT-CR-02
OT-CR-03
OT-CR-04
Planning Period Planning period Monthly
Start Date Start date Actual month
(C) SAP AG 118
Field Description Value
End Date End date Year end
Time Zone Time zone EST
Cover Full Calendar
Units Cover full calendar units Selected
In the Buckets screen area:
Field Description Value
Sub-Bucket Distribution Sub-bucket distribution No Distribution
Unit of Measure Unit of measure LB
Minimum TAL Quantity Minimum quantity 40000
Maximum TAL Quantity Quantity that should/must not be exceeded within planning period
120000
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.