outsourced tm

8/12/2019 Outsourced TM

http://slidepdf.com/reader/full/outsourced-tm 1/118

SAP Transportation ManagementConfiguration 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 purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registeredtrademarks 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 aretrademarks 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 registeredtrademarks 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 aretrademarks or registered trademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World WideWeb 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 aretrademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, GoogleMobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, GoogleUpdater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks orregistered 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 theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and othercountries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks ofBusiness Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybaseproducts and services mentioned herein as well as their respective logos are trademarks orregistered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks ofCrossgate 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 productspecifications may vary.



(C) SAP AG 4

These materials are subject to change without notice. These materials are provided by SAP AGand its affiliated companies ("SAP Group") for informational purposes only, without representationor warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect tothe materials. The only warranties for SAP Group products and services are those that are setforth 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 TextIcon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types ofinformation at a glance. For more information, see Help on Help General Information Classesand Information Classes for Business Information Warehouse on the first page of any version ofSAP Library .

Typographic ConventionsType Style Description

Example text Words or characters quoted from the screen. These include field names, screentitles, 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, programnames, transaction codes, table names, and key concepts of a programminglanguage when they are surrounded by body text, for example, SELECT andINCLUDE.

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 ofinstallation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the systemexactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace these words andcharacters 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 ContentsConfiguration 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 TransportationAbout this Document

This configuration guide describes a scenario for Outsourced Transportation . You mustimplement 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 basedon IDES

2.0 July 2011

Added chapter Defining Charge Calculation Profiles

Updated chapter Configuring Organizational Settings forCharge Elements

3.0 September 2012

The following chapters have been updated form TM 9.0setup:

Editing Locations [Page 41]

Defining OTR Types [Page 67]

Defining Freight Order Types [9]

Defining Rate Tables [Page 100]

Configuring Organizational Settings for ChargeElements [Page 115]



(C) SAP AG 9

The ScenarioThis configuration guide explains how to configure the Outsourced Transportation scenariomanually.

If you want to configure the scenario automatically using Business Configuration Sets and similartools, 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 Stateswith a plant/shipping point in Chicago. To use the transportation network as described thisdocument, you must ensure that the plant used in the customer system is located in the samevicinity.

The following organizational structures and document types are used by default and must beadapted 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 StartPrerequisites

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 TransportationManagement 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 connectionsused 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 tomaster data objects transferred from SAP ERP to SAP TM (see SAP Note 458914). An overviewof 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 arenot changed.



(C) SAP AG 13

Master DataMaster data is used throughout a number of business transactions in both SAP EnterpriseResource Planning (ERP) and SAP Transportation Management (TM). Before you can start towork 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 PlanningSAP 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 followingprocedures 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 ObjectsProcedure

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 code3000

(currency USD)

Enterprise Structure Definition Financial

Accounting Edit, Copy,Delete, Check CompanyCode

Sales organization 3000

Enterprise Structure Definition Sales and

Distribution Define, copy,delete, check salesorganization

Distribution channel 10


Distribution

Define, copy, delete, checkdistribution channel

Sales office 3000


Distribution Maintain SalesOffice

Sales group 300


Distribution Maintain SalesGroup

Plant 3100

Enterprise Structure Definition Plant

Maintenance MaintainMaintenance Planning Plant

Storage location 0001 Enterprise Structure Definition Materials

Management MaintainStorage 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 MaintainPurchasing 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 AssigningOrganizational Objects [Page 17] .

3. Check and assign the pricing procedure determination in SAP ERP for sales ordersbased on the organizational structure above. For more information, see Assigning PricingDetermination Procedures [Page 18] .



(C) SAP AG 17

Assigning Organizational ObjectsOnce you have defined and checked your organizational objects, you must specify assignmentsin the SAP ERP system.

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

Enterprise Structure Assignment Logistics – General Assign Plant to CompanyCode .

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 ProceduresProcedure

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 Salesand Distribution Basic Functions Pricing Pricing Control Define and AssignPricing Procedures Define Pricing Procedure Determination . Alternatively, entertransaction 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 20

Creating Customer MastersYou must create customer masters in the SAP ERP system.

Procedure

1. On the SAP Easy Access screen, choose SAP menu Logistics Sales andDistribution 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 MastersYou 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:


Name PGI TruckLines

NationalTrucking

FastTrucking &Logistics

GreenTransport

Search Term OT Carrier OT Carrier OT Carrier OT Carrier

Street WindgapAvenue DurandAvenue SpringStreet Port JerseyBlvd

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:


ReconciliationAccount 164003 164003 164003 164003



(C) SAP AG 23


CashManagementGroup

A1 A1 A1 A1

7. Choose Next Screen or press F8 until you reach the Create Vendor: Purchasing Data screen.



Order Currency USD USD USD USD

Terms ofPayment 0001 0001 0001 0001

GR-Based Inv.Verif. Selected Selected Selected Selected

Serv.-BasedInv. Ver. Selected Selected Selected Selected

9. Choose Next Screen or press F8 to open the Create Vendor: Partner Functions screen.



PartnerFunction 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 ProductsProcedure

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 assignedcountries.

7. On the Sales: Sales Org. Data 2 view:

Field Value

Item category group NORM

8. On the Sales: General/Plant Data view:

Field Value

Availability Check KP-no check

Trans. Grp 0001

LoadingGrp 0001

9. On the Purchasing view:

Field Value

Material Freight Grp 02

10. On the Accounting 1 view:

Field Value

Price Control S

Standard Price 100

Valuation Class 7900

Moving Price 100


After creating the material you need to make it available in your storage location.Therefore follow the following steps:

1. In ERP, enter transaction MB1C.

2. Enter the following data:



(C) SAP AG 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).




(C) SAP AG 27

Maintaining Price Conditions for MaterialsProcedure

1. On the SAP Easy Access screen of the SAP ERP system, choose SAP Menu Logistics Sales and Distribution Material Master Conditions Select (Using

Condition Type) Create . Alternatively, enter transaction VK11 in the command field.

2. Enter condition type PR00 and choose enter.

3. Select key combination Material with release Status .

4. Enter the following header data:

o Sales Organization: 3000

o Distribution Channel: 10

5. Enter the following item data:

o Material: OT-PROD-01

o Amount: 100

o Unit: USD

o Per: 1

o UoM: BAG

o Calculation Rule: C




(C) SAP AG 29

Transferring Master Data from SAP ERP to SAP TMProcedure

1. Transfer the following data from SAP ERP to SAP Transportation Management (SAPTM):

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 Integrationof SAP TM with SAP ERP. In particular, pay attention to the information regardingselecting an integration model



(C) SAP AG 30

Creating Integration ModelsIn this procedure, you create integration models, which specify which data objects are to beselected from the total dataset in SAP ERP for the transfer to SAP TM. You do not need allavailable 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 beselected on the Create Integration Model selection screen. Next, you select specific selectioncriteria 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 activatingthe 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 integrationmodel, you have to save the settings as a variant on the selection screen. By working withvariants you can reuse the settings you have saved whenever you want. If you want to re-createan integration model at a later point in time, you can call up the required variant by choosing theSelect 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 thismodel. Different versions of an integration model are distinguished by their date and time ofcreation, as well as by the filter objects that they contain. You can create as many versions of anintegration 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 newversion using transaction CFM1, and then delete the variant.

Structure of an Integration Model

The structure of an integration model influences performance. When it integrates transactiondata, 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 typeconcerned to determine any target systems that may be affected. The greater the number ofintegration models per object type, the longer the runtime for the determination for targetsystems.



(C) SAP AG 31

For performance reasons, we recommend that you use only one object type for eachintegration model.

Prerequisites

You have completed the Customizing and default settings for integration in both SAP TM andSAP 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 targetTM System as defined in CoreInterface 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 foryour 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 yourintegration 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 ModelsIn 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 arealready active. In this way, the transfer restricts itself to differences. In other words, the systemtransfers 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 integrationmodels.

When activating the integration model, you must define whether you want to create a businesspartner, a business partner and a location, or only a location in SAP TM. Business partners arenecessary for the commercial part of the business, whereas locations are necessary for planningand executing transportation. This means that whenever cargo needs to be picked up ordelivered, a location is necessary. In this scenario, you create business partners and locations forthe customers. Since the carriers are external, you only create business partners. If the distancesand transportation times from the depot of the carrier are important, then you need to create alocation 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 targetSAP TM System as defined inCore Interface Settings inSAP ERP .

APO Application TM-MD None

3. Choose Execute .

The selection screen displays the available integration models for the model name youhave specified.

Versions: If several integration models exist with the same name, they are displayed inchronological 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 theintegration model has been activated.



(C) SAP AG 34

If you want to deactivate the integration model, repeat the above procedure and ensurethat 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 theintegration model.

The system tests all active models, including those models scheduled for activation, butexcluding those models scheduled for deactivation.



(C) SAP AG 35

Defining Organizational UnitsOrganizational units (purchasing organizations and purchasing groups) are used when a freightorder 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 invoiceintegration, 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 thecommand field.

2. Enter the following data:

Field Value

Source System <logical system name of your ERPsystem>

Company Code 3000

Sales Organization 3000

Purchase Organization 3000

1. On the SAP Easy Access screen, choose SAP menu Master Data Organization Create Organization and Staffing or enter transaction PPOCE in the command field.

2. When prompted, enter the validity dates for the organizational unit.

3. On the following screen, enter your data based on the following tables.

On the Basic Data tab page:


Organizational Unit Specifies the organizational OT-PORG-1



(C) SAP AG 36


unit to be created

Description Description OT: PurchasingOrganization

On the Org. Data tab page:


Org. ID Organizational unit ID. This isan internal number.

<Organizational unitthat you previouslydefined >

Org. Unit Function Specifies the type oforganizational unit 2 - Purchasing

Org. Unit Role Specifies the role of theorganizational unit 1 - Organization

On the Address tab page:


Subtype Defines the type of address Main Address

Street Street in the address Industrial Parkway

City City in the address Philadelphia

Postal Code Postal code of the address 19088

Country Country of the address U.S.


5. Repeat the procedure to create a purchasing group:



Organizational Unit Specifies the organizationalunit to be created “OT-PGRP- 1”

Description Description OT:Purchasing Group





Org. Unit Function Specifies the type of 2 - Purchasing



(C) SAP AG 37


organizational unit

Org. Unit Role Specifies the role of theorganizational unit 3 - Group




Street Street in the address Industrial Parkway


Postal Code Postal code of the address 19088



Create sales organization and group



Organizational Unit Specifies the organizationalunit to be created OT-SORG-1

Description Description OT: Sales Organization



Org. ID Organizational unit ID. This isan internal number


Org. Unit Function Specifies the type oforganizational unit 4 – Sales

Org. Unit Role Specifies the role of theorganizational unit 1 – Organization








(C) SAP AG 38


8. Repeat the procedure to create a purchasing group:



Organizational Unit Specifies the organizationalunit to be created OT-SGRP-1

Description Description OT:Sales Group





Org. Unit Function Specifies the type oforganizational unit 4 – Sales

Org. Unit Role Specifies the role of theorganizational unit 3 – Group







10. Create planning and execution organization and group



Organizational Unit Specifies the organizationalunit to be created OT-PEORG-1

Description Description OT: Planning &Organization




<Organizational unitthat you previously



(C) SAP AG 39


defined >

Org. Unit Function Specifies thetype of organizational unit 13 – Planning and Execution

Org. Unit Role Specifies the role of theorganizational unit 1 – Organization






11. Save your entries.12. Repeat the procedure to create a purchasing group:



Organizational Unit Specifies the organizationalunit to be created OT-PGRP-1

Description Description OT: Planning &Execution Group





Org. Unit Function Specifies the type oforganizational unit 13 – Planning & Execution

Org. Unit Role Specifies the role of theorganizational unit 3 – Group








(C) SAP AG 40


Result

You have defined a purchasing organization and group, sales organization and group, planningand execution organization and group.



(C) SAP AG 41

Editing LocationsProcedure

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@ <logicalsystem> -122,19,48 +47,59,59



(C) SAP AG 42

Defining Transportation ZonesProcedure

1. Create a zone in SAP Transportation Management. To do so, open the SAP Easy Access screen and choose SAP menu Master Data Transportation Network

Transportation Zones Define Transportation Zone . Alternatively, enter transaction/SCMTMS/ZONE in the command field.

2. Choose Create and enter the following data:

Field Value

Zone OT-US

Zone Type M

Description OT US Zone

3. On the Zone Region tab page add the following country key: US.


5. Create OT-US-MIDWEST zone in the header area and modify it as follows:

Country Key Country Name Region Region Name

US USA IA Iowa

US USA IL Illinois

US USA IN Indiana

US USA MI Michigan

US USA MN Minnesota

US USA ND North Dakota

US USA NE Nebraska

US USA OH Ohio

US USA SD South Dakota

US USA WI Wisconsin

6. Choose the Calculate Coordinates pushbutton.


8. Create the zone OT-US-WEST in the header area, and on the Zone-Region tab, modify itas follows:




(C) SAP AG 43


US USA CA California

US USA ID Idaho

US USA NV Nevada

US USA OR Oregon

US USA WA Washington

9. Choose the Calculate Coordinates pushbutton.




(C) SAP AG 44

Maintaining Transportation Zone HierarchiesYou must maintain a transportation zones hierarchy to organize your locations in such a way thatyou can run vehicles from the start location to the destination location via hubs, ports ortransshipment locations. Furthermore, if you do not maintain the transportation zone hierarchycorrectly, 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-USOT-US-MIDWEST

OT-US-WEST

Procedure

1. On the SAP Easy Access screen for SAP TM, choose Transportation ManagementMaster Data Transportation Network Transportation Zones Define TransportationZone 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 46

Defining Transportation LanesProcedure

1. On the SAP Easy Access screen for SAP Transportation Management, choose SAPmenu Master Data Transportation Network Transportation Lanes DefineTransportation 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 thedialog:

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 ofTransportation 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

TransportationCosts

Use TCM costs(when themaintained valueis 0.0)




Priority 1 2 3 4

TM Tendering:Consider TSPfor P2PTendering

X Blank X Blank

TM Tendering:Consider TSPfor BroadcastTendering

Blank X Blank X



(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 PointsIf a GeoServer is not installed, business partners for the shipping points are not automaticallygenerated by transferring master data from SAP ERP to SAP TM. If a business partner is notassigned to the transferred location, you have to create and assign a business partner manually.

Procedure

1. On the SAP Easy Access screen, choose SAP menu Master Data General Define Business Partner . Alternatively, you can enter transaction BP in the command

field.

2. Create your business partners based on the following Business Partner (General) role:OT-SP-3100 - BP for Shipping Point .


4. On the SAP Easy Access screen, choose SAP menu Master Data Transportation

Network Define Locations .5. Enter Location SP3100@< logical system > .

6. Select Change .

7. On the General tab page in the Partner screen enter BP number OT-SP-3100 .




(C) SAP AG 51

ConfigurationThis 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 theconfiguration 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 ERPYou configure sales order management in your SAP Enterprise Resource Planning (ERP)system. For more information about the configuration settings that are required for sales ordermanagement, 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 OrdersThere 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 typeOR) or a rush order (order type RO).

Procedure

1. In Customizing for SAP ERP, choose SAP Customizing Implementation Guide Salesand Distribution Sales Sales Documents Sales Document Header Define SalesDocument 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 55

Text Determination in Sales OrdersProcedure

1. In Customizing for SAP ERP, choose SAP Customizing Implementation Guide Salesand Distribution Basic Functions Text Control Define Text Types or entertransaction VOTXN in the command field.

2. Select the Header checkbox for the Sales Document.

3. Choose Text Types.

4. Enter text type TM01 and description Driver Text .

5. Choose Save.


7. Select the Header checkbox for the Sales Document and choose Change to add the newtext 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).


SeqNo Sequence number In accordance with the currentsequencing

ID Identification TM01

Refer/Duplicate Reference Deselected

Text is obligat. Text is obligatory Text is not obligatory

Access seq . Access sequence 1




(C) SAP AG 56

Creating OutputProcedure

1. On the SAP Easy Access screen, choose SAP menu Logistics MaterialsManagement Purchasing Master Data Subsequent Settlement Customer Rebate

Arrangements Environment Customer Messages Sales Document Create . Alternatively, enter transaction VV11 in the command field.

2. In the Output Type field, specify the type of output that is to be produced. In our scenario,the output type is TRS0.

3. Choose Enter .


Field Value Description

SalesDocTy OTTL Sales document type

Medium 8 Special function

Date/Time 4 Send immediately (whensaving the application)

Language EN Language in which the outputis to be produced




(C) SAP AG 57

ERP Invoicing



(C) SAP AG 58

Mapping Organizational UnitsProcedure

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 Unitsfor Purchasing .


3. Enter the data based on the following table:

Field Value

Logical System <Logical name of the connected TMsystem >

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




(C) SAP AG 59

Order-Based Transportation RequirementsYou configure the settings for order-based transportation requirements (OTR) in your SAPTransportation Management system.

For more information, see the process descriptions below.



(C) SAP AG 60

Defining Conditions for Quantity TolerancesProcedure

1. On the SAP Easy Access screen, call transaction NWBC to open the SAP NetWeaverBusiness 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 ControllerStrategiesProcedure

1. On the SAP Easy Access screen, call transaction NWBC to open SAP NetWeaverBusiness Client.


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 ChangeController 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 SchemasProcedure

1. In Customizing for SAP Transportation Management, choose SAP CustomizingImplementation Guide Cross-Application Components Processes and Tools forEnterprise 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 followingtable:

Field Value

Text Type TM01

Description Driver Notes

3. Double-click Text Schema in the navigation tree and enter your data based on thefollowing table:

Field Value

Txt Schema OT0001

Description Text schema for OT

4. Select the entry that you created in step 3 and double-click Text Type to Text Schema Assignment in the navigation tree.


Field Value

Text Type TM01 and A0001

Mandatory Deselected

Internal Deselected

Lang. Text Deselected

6. Double-click Assign Text Schema to BO and Node in the navigation tree and enter yourdata based on the following table:

Business Object Name Node Name Txt Schema

/SCMTMS/TOR ROOT OT0001

/SCMTMS/TOR TENDERING OT0001

/SCMTMS/TRQ ROOT OT0001




(C) SAP AG 63

Assigning ERP Text Types to TM Text Types for OTRProcedure

1. In Customizing for SAP Transportation Management, choose SAP CustomizingImplementation Guide SAP Transportation Management Transportation Management

Integration ERP Logistics Integration Order-Based Transportation Requirement Assign ERP Text Types to TM Text Types for OTR .




ERP Doc. ERP document Sales Document Header

ERP Text ERP text TM01

TM Text TM text TM01

Not TM-Rel Not relevant to TM Deselected




(C) SAP AG 64

Defining Service LevelsProcedure

1. In Customizing for Transportation Management, choose Forwarding OrderManagement Define Transportation Service Level Codes .

2. Choose New Entries .


Field Value

Service Level Code TM

Description TM Service Level




(C) SAP AG 65

Defining Freight Unit Building RulesThe freight unit building rule (FUBR) is assigned and applied at the level of the OTR type. Itspecifies 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 UnitBuilding Rule Create Freight Unit Building Rule .

3. On the New Freight Unit Building Rule screen, enter your data based on the followingtables:

On the General Data tab page:


Freight Unit Building Rule Specifies the FUBR to becreated OT_FUBR_01

Description Description of the FUBR OT: Freight UnitBuilding Rule

Document Type Freight order type OTTL

Freight Unit Building Strategy Specifies how consolidation iscarried out

Consolidate per Request(Compatible parts)

Process Controller Strategy ( Advanced Settings tab page)

Strategy that defines how tobuild FUs FUB_AUTO

Incompatibility Settings Not used Blank

Critical Quantity Defines the weight/volumelimits for the freight unit Gross Weight

Item Split Allowed

Indicator that specifieswhether item quantities canbe split across different freightunits

Selected

On the Planning Quantities tab page:

Field Description Row 1 Row 2 Row 3

PlanningQuantity forFreight Unit

Specifies theparameter forthe planning

Gross Weight Gross Volume Pieces



(C) SAP AG 66

Field Description Row 1 Row 2 Row 3

Building quantity

Unit of Measureof Split Quantity Unit of measure LB FT3 BAG

Split Quantity

Quantity limit forthe item thatforms the basisfor buildingfreight weights

40,000 0 0

RoundingQuantity

Any roundingquantity applied 1 1 1


Result

You have created a freight unit building rule.



(C) SAP AG 67

Defining OTR TypesOrder-based transportation requirements (OTR) that are received from SAP ERP are mappedusing OTR document types.

PrerequisitesYou have defined a freight unit building rule or intend to do so.

Procedure


Integration ERP Logistics Integration Order-Based Transportation Requirement Define Order-Based Transportation Requirement Types .

2. On the Order-Based Transportation Requirement Types: Overview screen, choose NewEntries.

3. Enter the necessary data based on the following tables.

In the header area:


OTR Type ID of the OTR document type OTTL

Description Description of the OTR type tobe defined Truck Load Order

Default Type

Only one OTR type can bedefined as the default OTR

type. Select this checkbox ifthere is only one OTR typedefined in the system.

Deselected

In the Number Range Settings screen area:


Number Range Interval

Number range used to assignthe numbers to the OTRtypes. We use the numberrange as indicated.

02

In the Process Control / Business Object Mode screen area:


BW Relevance Indicates whether thedocument type is relevant forBW

Selected

Automatic Freight UnitBuilding

Indicates whether the freightunits are built automatically. Ifyou select this checkbox, you

Selected



(C) SAP AG 68


must specify an FU buildingrule.

Enable Approval Workflow Indicates that the approvalworkflow is activated. Deselected

Automatic Block

Specifies whether thebusiness documents offorwarding order managementare blocked automatically.Only special creationchannels are taken intoconsideration.

Deselected

Track Changes Specifies that changes are tobe tracked Selected

EM Integration Active Selected

Event Manager Logical system of the EMsystem.

EM Web InterfaceTransaction

Specifies the object that is tobe processed in SAP EventManagement

ODT20_FU

Retention Period Retention period (in days)before archiving 30

Output Profile Print profile used for thisdocument type /SCMTMS/TRQ_FWO_PRINT

Add. Output Profile Additional output profile Blank

Propagate Changes

Specifies how information isto be transferred if changesare made to the document(such as changes toquantities, and so on)

B – Synchronous Propagationof Changes, Fallback to

Asynchronous

In the Default Values screen area:


Default Weight UoM Default unit of measure for the

weight for this document typeLB

Default Volume UoM Default unit of measure for thevolume for this document type FT3

Plan on Req/Cnf Qty Planning indicator thatspecifies the quantities(planned or confirmed) to betaken into account during

01 – Plan on RequestedQuantities



(C) SAP AG 69


planning

Planning Profile

Specifies the planning profilethat is used by the systemwhen performing planningruns and creatingtransportation proposals forbusiness documents of thistype

Blank

Freight Unit Building Rule

Rule used when buildingfreight units (if the Autom. FUBuilding checkbox is selected)

For information about definingthe FUB rule, see DefiningFreight Unit Building Rules. [Page 65]

OT_FUBR_01

FU Building Rule Condition

You can specify a conditionfor determining a freight unitbuilding rule that is used whenfreight units are created forbusiness documents of thistype.

None




(C) SAP AG 70

Defining Conditions for OTR Type DeterminationWhen the SAP TM system receives a sales order, it creates an order-based transportationrequirement (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 ERPto SAP TM.

Prerequisites

You have defined the OTR document types.

Procedure


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, continuethis 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 tablesbelow.

In the General Data screen area:


Condition Condition type supplied by thesystem ZOTR_TYPE

Description Description of the conditiontype

OTR Type DeterminationCondition

In the Settings screen area:


Condition Type Condition type supplied by thesystem /SCMTMS/OTR_TYPE

Origin of Condition Source of the conditioninformation

Condition based on BRFplusDecision Table

5. In the Decision Table of the Data Access Definition tab page, enter the following data:




(C) SAP AG 71


BseDoc. Ty. Incoming base document typeParameter: “is equal to”

Value: 114 – Sales Order

Proc Type

This respectivecolumn is availableafter saving thecondition.

Procedure type (incomingparameter)

OTTL (the document type forthe incoming order definedabove)

Parameter: “is equal to”

Value: OTTL

OTR Type

Specify the data for integrationhere – the document type thatis identified and used in SAPTM for OTR.

OTTL (defined in a previousstep)

To enter values on the Decision Table tab page, you may have to switch to edit modeand choose Insert New Row ..

6. Save your changes.

Result

You have configured the integration settings between the incoming sales document and the OTRdocument type.



(C) SAP AG 72

Creating Delivery ProfilesProcedure

1. In your SAP Transportation Management system, call transaction NWBC to open the SAPNetWeaver Business Client.

2. Choose Application Administration Planning General Settings Delivery Profile Create Delivery Profile .


Field Value

Delivery Profile OT_DELV_PRFL_STAN

Description Delivery Profile for OutsourcedTransportation

Fix Planning Results Selected

Delivery Creation Per OTR




(C) SAP AG 73

Defining Tendering ProfilesYou use tendering profiles to define the process settings. For more information, see step 9 inDefining General Settings for Tendering. [Page 76]

Procedure1. 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:


Tendering Type Determines how tendering iscarried out

Peer-to-Peer Tendering,Response Required

Tender is sent to one carrierand a confirmation is requiredfrom this carrier

Tendering Process Tendering process mode RFQ-Based, Award Automatically

Carrier Carrier Blank

Freight RFQ SequenceNumber

Freight RFQ sequencenumber Blank

Carrier Assignment Method Determines how carriers areassigned to the freight order

Get Carriers from RankingList

A ranking list is provided fromwhich carriers are selected

Relative Price Limit Relative price 100

Carrier-Specific Freight Agreement

Carrier-specific freightagreement Selected

Maximum Response Duration Maximum time within whichthe carrier must respond to anRFQ

2:00

The RFQ is confirmed in thefreight order when theprogram that checks theresponses is executed.



(C) SAP AG 74


If you want to run thisreport manually, onthe SAP Easy Accessscreen choose

Application Administration

BackgroundReports

BackgroundProcessing ofTendering .

Visibility Settings

Defines the visibility setting forRFQ, that is, whether pricesare displayed, whether thecarrier can change the prices,and so on

OT_VIS_SET

This setting is defined in thenext 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:


Tendering Type Determines how tendering iscarried out

Broadcast Tendering – BestOffer

Tender is sent to all carriersand a confirmation is required

from each carrier

Tendering Process Tendering process mode RFQ-Based, Award Automatically

Carrier Carrier Blank

Freight RFQ SequenceNumber

Freight RFQ sequencenumber Blank

Carrier Assignment Method Determines how carriers areassigned to the freight order

Get Carriers from RankingList

A ranking list is provided fromwhich carriers are selected

Relative Price Limit Relative price 100%

Carrier-Specific Freight Agreement

Carrier-specific freightagreement Deselected

Maximum Response Duration Maximum time within whichthe carrier must respond to an

0:15

The RFQ is confirmed in the



(C) SAP AG 75


RFQ freight order when theprogram that checks theresponses is executed.

If you want to run thisreport manually, onthe SAP Easy Accessscreen choose

Application Administration

BackgroundReports

BackgroundProcessing ofTendering .

Visibility Settings

Defines the visibility setting forRFQ, that is, whether pricesare displayed, whether thecarrier can change the prices,and so on

OT_VIS_SET

This setting is defined in thenext chapter.

7. Save your entries after maintaining the visibility settings in the next section.



(C) SAP AG 76

Defining General Settings for TenderingBefore tendering can be carried out, you must configure various profile settings. Some of theseprofiles and settings are used and assigned when the freight order (FOR) is configured. Thefollowing section explains each of these settings in more detail.

Procedure


Freight Order Management Tendering Define General Settings for Tendering .

2. In the tree structure on the left-hand side, double-click 01 — Visibility Settings andchoose New Entries.

3. Create your entry based on the following table:


Visibility Setting Unique name for the profilesetting for tendering visibility OT_VIS_SET

Vis. Stngs Desc. Description of the visibilitysettings profile

OT: VisibilitySettings

Stop Dates Visib.

Specifies whether the stopdates are displayed for thecarrier when the carrierreceives the RFQ

ER, Editable, Relevant

Price Limit Specifies whether the pricelimit set for this tender is

displayed for the carrier

RO Read Only

Subm. Price Visib.

Specifies whether the price forthis tender is displayed for thecarrier and whether the carriercan change the offer

ER, Editable Relevant


5. Double-click 02 — Rejection Reason Codes and choose New Entries.



Reason Here, a list is created fromwhich the carrier can select avalue to reject an RFQ

01 – No Capacity

02 – No Time

03 – No Reason to Provide


8. Double-click 04 — Process Settings and choose New Entries.



(C) SAP AG 77

9. Create an entry based on the following table:


Process Settings Process setting ID OT_PROCESS_SETTINGS

Tendering Manager Tendering Manager <Your user ID >

Visibility Settings Visibility settings OT_VIS_SET

Tendering Profile Tendering Profile OT-TEND-PROF

Carrier Settings

Defines the carrier selectionthat you want to use for theautomatic carrier proposal inthe tendering process. Formore information, seeDefining Carrier SelectionSettings [Page 85] .

OT_CARR_SEL_01

Max. Resp. Times [h]

Defines the maximum periodfor the carrier to respond tothe freight request forquotation (RFQ) in theseprocess-related settings

Blank

BP Calling Hours Defines whether you want totake the calling hours of yourbusiness partner into account

Deselected

Review Threshold [%]

Allows the carrier to submit aprice that deviates by thepercentage defined here fromthe price you submitted in thefreight request for quotation(RFQ)

5%

Restart Tendering

Defines that the tenderingprocess is restartedautomatically if the awardedcarrier rejects the freight order

Selected

Calculate Charges afterTendering None Deselected


11. Double-click 05 — Communication Settings and choose New Entries. 12. Create an entry based on the following tables:

Header area:


Comm. Settings Name of the communicationprofile setting to be created OT_COMM_SET



(C) SAP AG 78

05 — Communication Settings screen area:


Trigger Alerts w/o

Subscription to Alert Category

If you select this checkbox,alerts are sent to tenderingmanagers even if they havenot subscribed to the alertcategory.

Selected

Send EDI Messages Created EDI massages for thealerts Deselected

E-Mail screen area:


Send RFQ Create RFQ by e-mail Selected

Send Notification for

Canceled Tendering

Create notification for

canceled tenderingSelected

Send Notification for SentRFQs

Send notification e-mails forsent freight RFQs Deselected

Send Notification for AwardedQuotation

Create notification e-mails foraccepted freight quotations Selected

Send Notification for RejectedQuotation

Create notification e-mails forrejected freight quotations Selected

SMS screen area:


Send RFQ Create RFQ by SMS Deselected

Send Notification forCanceled Tendering

Create notification forcanceled tendering Selected

Send Notification for SentRFQs

Send notification SMS for sentfreight RFQs Selected

Send Notification for AwardedQuotation

Create notification SMS foraccepted freight quotations Selected

Send Notification for RejectedQuotation

Create notification SMS forrejected freight quotations Selected


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 80

Defining Conditions for IncompatibilitiesWhen you create an incompatibility, you must also create an incompatibility condition. You useconditions to define incompatibilities between planning data by specifying condition attributes. Ifthe planning data matches the condition specified, the data is identified as incompatible.

Procedure



The New Condition Definition screen appears.

3. Enter your data based on the following settings.


Condition Unique identifier OT_INC_COND_CARR

Description Description of condition OT-Incomp cond – Carrier

Condition Type Select the appropriatecondition type here /SCMTMS/INC_CARRIER

Origin of Condition Specify the origin of thecondition

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:


Data Element Used for InputHelp

This value is populatedautomatically based on yourentries in ConfiguringIncompatibility Settings [Page84] .

BU_PARTNER

Name of BO Used inCondition

BO used to obtain theinformation about the

incompatibility

/SCMTMS/SUPPLIER

Name of BO Node Used inCondition

BO node used to obtain theinformation ROOT

Name of the Field of BO Node Field used to obtain the valuefor the incompatibility PARTNER




(C) SAP AG 81

8. Create the second condition based on the following attributes.


Condition Unique identifier OT_INC_COND_CUST

Description Description of conditionOT-Incomp cond – Customer

Condition Type Select the appropriatecondition type here /SCMTMS/INC_TO

Origin of Condition Specify the origin of thecondition

Direct Business Object Access

9. In the Data Access Definition table:


Data Element Used for InputHelp

This value is populated

automatically based on yourentries in ConfiguringIncompatibility Settings. [Page84]

/SCMTMS/PTY_CONSIGNEE

Name of BO Used inCondition

BO used to obtain theinformation about theincompatibility

/SCMTMS/TOR

Name of BO Node Used inCondition

BO node used to obtain theinformation ROOT

Name of the Field of BO Node Field used to obtain the valuefor the incompatibility CONSIGNEEID




(C) SAP AG 82

Creating IncompatibilitiesYou use incompatibilities to define the compatibility of planning data that the system uses duringtransportation 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 thelocation 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 (thatis, planned transportation activities) and, in turn, the assignment of transportation plans to themeans of transport.

On the following pages, we create an incompatibility between a shipper (OT-VN-01) and a carrier(OT-CR-01).

Procedure


2. Choose Application Administration Planning General Settings IncompatibilityDefinition Create Incompatibility .

3. On the New Incompatibility Definition screen, enter your data based on the followingtables.

Incompatibility Definition screen area:

Field Description ValueIncompatibility Name of the incompatibility OT_INCOMP_CAR_CUST

Description Description of theincompatibility

OT-Carrier-CustIncompatibility

Incompatibility Area Applicable TM area O5 – Carrier Selection

Incompatibility Type Further definition of theincompatibility – where is itapplicable?

81 – Carrier – TransportationOrder

Determination Method Defines how values aredetermined for theincompatibility

Condition-BasedIncompatibility

Manual Violation

System response if thisincompatibility is violated dueto a manual assignment ofvalues

Warning If Incompatibility IsViolated

Automatic Violation System response if thisincompatibility is violated due Incompatibility Must Not Be



(C) SAP AG 83


to an automatic assignment ofvalues

Violated

Conditions screen area:


First condition:

Condition

Incompatibility condition to beused. The condition can becreated directly from the link inthis field.

OT_INC_COND_CARR

Relevant Condition Result Incompatibility settingoutcome OT-CR-01

Second condition:

Condition

Incompatibility condition to beused. The condition can becreated directly from the link inthis field.

OT_INC_COND_CUST

Relevant Condition Result Incompatibility settingoutcome OT-CU-01


More Information

For more information, see Defining Conditions for Incompatibilities [Page 80] .



(C) SAP AG 84

Configuring Incompatibility SettingsIncompatibility settings are used to inform SAP Transportation Management of the currentconditions for the incompatibility.

Procedure1. On the SAP Easy Access screen, call transaction NWBC to open the SAP Business Client.

2. Choose Application Administration Planning General Settings IncompatibilitySettings Create Incompatibility Settings .

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



Incompatibility Settings Unique ID for theincompatibility settings OT_INCOMP_SET_001

Description Description of theincompatibility settings OT Incomp. Settings

Incompatibility Area Area in which theincompatibility is to be applied Carrier Selection

Default IncompatibilitySettings

If you select this checkbox,the system uses the defaultincompatibility settings.

Deselected

4. Choose Insert.



Incompatibility Incompatibility defined above OT_INCOMP_CAR_CUST

Violation in Manual Planning

Action to be carried out if theincompatibility is violated andthe location from which toderive the follow-on actions

According to IncompatibilityDefinition

Violation in AutomaticPlanning

Action to be carried out if theincompatibility is violated andthe location from which toderive the follow-on actions

According to IncompatibilityDefinition


Result

The setting is assigned to the carrier selection setting.



(C) SAP AG 85

Defining Carrier Selection SettingsYou use carrier settings to define the process settings. For more information, see step 15 inDefining General Settings for Tendering. [Page 76] This profile setting determines how carriersare 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 carrierbased on the following tables:



Carrier Selection Settings Unique ID of the settingsprofile OT_CAR_SEL_02

Description Carrier selection description OT: General CarrierSelection Profile

Check Incompatibilities Indicates that incompatibilitiesare to be taken into accountwhen selecting a carrier

Selected

Incompatibility Settings Enter a profile ifincompatibilities are to be

checked

OT_INCOMP_SET_001

(For more information, see

Configuring IncompatibilitySettings [Page 84] )

Type of Carrier SelectionSettings Type of carrier General Carrier Selection

In the Other Settings screen area:


Trsp. Alloc. Usage

Specify whether thetransportation allocationusage is to be activated whenthe carrier is selected

Use Transportation Allocations

BS Usage

Indicates whether thebusiness share (BS) settingsfor the carrier are to be takeninto account when selectingcarriers

Do Not Use Business Shares

Strategy Which strategy is to be usedto select the carrier?

Costs



(C) SAP AG 86


Strategies can be based oncosts, priorities, or acombination of the two.

Carrier Cost Origin If the strategy is cost-based,this field specifies the costorigin for selecting the carrier

Use Transportation Chargesfrom TCM

On the Advanced Settings tab page:


Planning Strategy Planning strategy for selectingcarriers TSPS_DEF

Optimizer Runtime

Runtime for the optimizer runused to select the carrier. Thisprevents processes from

running indefinitely.

6

Consider Manual Assignmentas Fixed

Consider this assignment asthe final carrier assigned tothe freight order

Deselected

Action for Manual Rankings

Specifies whether the manualplanning list can be enteredduring the planning processand how the manual entriesare to be handled

Remove

Overall Carrier Availability Overall carrier availability Deselected

Common Currency Currency used to calculatecosts USD

Action After Carrier SelectionRun

Action that is to be performedonce the carriers have beenselected

Automatic Tendering

Continuous Move Type

Specifies how carriers are tobe selected based on thecontinuous moveopportunities

Do Not Create ContinuousMove

Continuous Move Information

Specifies whether continuous

move possibilities are to beconsidered Selected

Reaction to CM Removal Reaction to CM removal Blank

Check Dist. and Dur.

Determines whether thedistance of the locations andthe duration of the trip are tobe taken into consideration

Deselected



(C) SAP AG 87


Continuous Move MTr. Check

Determines whethercontinuous move means oftransport are to be taken intoconsideration

Deselected

CM Cost Recalculation forTCM

Active if continuous move isused to select carriers No Recalculation

Use Tendered Objects forOptimization

Use tendered objects foroptimization Deselected

Tender Without OptimizerResult

Tender without optimizerresult Deselected

Tendering Manager User ID of the manager<User ID of thetendering manager >

Tendering Profile Tendering profile to be usedin automatic tendering OT-TEND-PROFILE


4. Repeat this process to create settings for the tendering profile based on the followingtables.



Carrier Selection Settings Unique ID of the settingsprofile OT_CARR_SEL_01

Description Carrier selection description OT: CS Profile for Tendering

Check Incompatibilities Indicates that incompatibilitiesare to be taken into accountwhen selecting a carrier

Selected

Incompatibility Settings Enter a profile ifincompatibilities are to bechecked

OT_INCOMP_SET_001

(For more information, seeConfiguring IncompatibilitySettings [Page 84] )

Type of Carrier Selection

Settings Type of carrier

Carrier Selection for

Tendering

In the Other Settings screen area:


Trsp. Alloc. Usage Specify whether thetransportation allocationusage is to be activated when

Use Transportation Allocations



(C) SAP AG 88


the carrier is selected

On the Advanced Settings tab page:


Planning Strategy Planning strategy for selectingcarriers TSPS_DEF

Overall Carrier Availability Overall carrier availability Deselected




(C) SAP AG 89

Defining Freight Order TypesFreight orders (FOR) are used for planning, tendering, and subcontracting. They also define themajor 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 andcommunication settings at a later time. If you do so, you must remember toupdate them here.

Procedure


Freight Order Management Freight Order Define Freight Order Types or entertransaction /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 thefollowing tables.

In the Freight Order Types screen area:


Freight Order Type Unique 4-character ID of theFOR that is to be defined OTTL

Description Description of the FOR to bedefined Truck Load Order

In the Basic Settings screen area:


Freight Order Can BeSubcontracted

Indicator that specifieswhether this FOR type can

use subcontracting processes

01 – Relevant forSubcontracting

Shipper/ConsigneeDetermination

Determines how the shipperand consignee partners aredetermined for this FOR

P – Determine Based onPredecessor Documents (ifthese are not unique, use thesetting for locations)

Fix Document When Saving Selected



(C) SAP AG 90


Freight Order Can Be Deleted Specifies whether the FORcan be deleted once it hasbeen created

Selected

Enable Settelment Enables settlement Selected

Enable Charge Calculation Enables charge calclation Selected

In the Number Range Settings screen area:


Time for Drawing Specifies the time at which anumber is assigned to theFOR document

Draw Number When SavingDocument

Number Range Interval Number range that is to beused for this document type 02

In the Change Controller Settings screen area:


Default Change Strategy

Default strategy used fortendering behavior whenchanges are made to the FORkey fields, such as partners,quantities, and so on

DEF_CHACO

Change StrategyDetermination Cond.

Specifies the condition thatthe system is to use to

determine a change controllerstrategy at runtime.

If you have defined severalchange controller strategies,you can use a condition todetermine the appropriatechange controller strategy.

The condition type of thiscondition is/SCMTMS/CC_TOR_STRAT.

OT-CSDC-01

Quantity Tolerance Condition

Specifies the tolerances for aquantity change in a businessdocument.

The condition type of thiscondition is/SCMTMS/CC_QUAN_TOL.

OT_QTOL_01

Date Tolerance Condition Specifies the tolerances for adate change in a business

Blank



(C) SAP AG 91


document

In the Additional Strategies screen area:


Creation Strategy

Specifies tasks that thechange controller is toperform when you create oneof the following businessdocuments:

Freight order

Freight booking

Transportation unit

Freight unit

CARR_SEL

Save Strategy

Specifies tasks that thechange controller is toperform when you save thefreight order.

The strategy definition isexplained in a separate stepbelow.

Blank

Deletion Strategy

Specifies tasks that thechange controller is toperform when you delete the

freight order.

CANCEL_CAP

In the Execution Settings screen area:


Execution Track. Relev.

Controls how documents aretracked.

If you want to track certaintypes of documents, choose 2(Execution Tracking) or 3(Execution Tracking withExternal Event Management). The system then sets theinitial document executionstatus to Not Started.

If you do not want to trackcertain types of documents,choose 1 (No ExecutionTracking). The system thensets the initial document

3 – Execution Tracking withExternal Event Management



(C) SAP AG 92


execution status to NotRelevant.

Immediate Processing

Indicator that sets the statusIn Process immediately assoon as the document iscreated and saved

Selected

Check Condition “Ready forExec” Not used Blank

Propagate Execution Info Propagates the executioninformation to thepredecessor document

Deselected

In the Event Management Settings screen area:


Application Object Type

Type of application object tobe tracked in the applicationsystem (required to determinewhether an application objectis relevant for EventManagement). The eventmanager processes only theevent messages for theseobjects.

ODT20_TO

Last Exp. Event Last expected event for adocument, for example, theUnload_End.

POD

In the Service Level Determination screen area:


Default Service Level Default service level code forthe business document type Blank

Service Level Cond. Condition for service leveldetermination Blank

In the Default MTr Determination screen area:


Default MTr for Type Specifies the default means oftransport for this freight ordertype

OT-FTL

Condition for Def MTr Name of the condition for thedefault means of transport Blank

In the Tendering Settings screen area:



(C) SAP AG 93


Use Default Settings

Indicates that the Customizingsettings for tendering aredetermined in accordancewith the default settings

Deselected

Use Condition for Sett.Determ. Tendering ConditionDefinition

Indicates that the Customizingsettings for tendering aredetermined using conditions.

Deselected

Use Type Specific Settings

Enables you to further definethe FOR-type-specificprocesses for processsettings and communicationsettings.

Selected

Process Settings

Specifies the tenderingprocess settings.

Identifies process-relatedsettings, for example:

o Defaulttendering manager

o Maximumresponse duration

o Tenderingprofile

The section below explainsthis setting in more detail.

OT_PROCESS_SETTINGS

Communication Settings

Indicates the strategy fortendering communication.This profile is defined in aseparate stage below.

OT_COMM_SET

In the Default Units of Measure screen area:


Weight Weight US Pound

Volume Volume Cubic Foot

In the Output Options screen area:


Output Profile Output profile /SCMTMS/TOR_PRINT_ROAD

Add. Output Profile Additional output profile Blank



(C) SAP AG 95


Unit function 13 – planningand execution

Unit role 1 – organization

Purchase Org.

ID of the organizational unitthat is defined as:

Unit function 2 – purchasing

Unit role 1 – organization

<Your purchasingorganization >(OT-PEORG-1)

Execution Group


Unit function 13 – planningand execution

Unit role 3 – group

<Your executiongroup >(OT_PEGRP-1)

Purchasing Group


Unit function 2 – purchasing

Unit role 3 – group

<Your purchasinggroup >(OT-PGRP-1)

Consider Organization Unit ofUser

Specifies that theorganizational unit of the useris to be taken into account

Deselected

Condition Condition Blank



Result

You have defined the new freight order type.



(C) SAP AG 96

Defining Freight Settlement Document TypesProcedure


Settlement Freight Settlement Define Freight Settlement Document Types .

2. Choose New Entries .


Field Value

FSD Type OTTL

Description Carrier Settlement Document

FSD Category Freight Settlement Document

No. Range Interval 01

BW Relevance Selected

Output Profile /SCMTMS/TOR_INV_PREP

Add. Output Profile /SCMTMS/SFIR_PRINT

Dynamic Determination of Output Profile Deselected




(C) SAP AG 97

Charge ManagementProcess

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 ScalesScales are parameters that you can use to specify freight rates when they are assigned to freightconditions.

Procedure1. To create a scale, open your user menu on the SAP Easy Access screen and choose

Master Data Charge Management Scales Create Scale .


3. Enter the data for your scale based on the following table:

Tab Page Field Description Value

General Data

Scale Scale ID OT-SCALE-LOC

Description Description of thescale

OT – OriginLocation Scale

Scale Base

Defines the basis ofscale, for example,location, distance,duration, and so on.

LOC – Location

Items

Calculation Type Defines how the scalevalues are read

Absolute

(values are readdirectly)

Internal Location Define Location

relevant for scale

SP3100@< logicalsystem

> 4. Save your entries.

5. Create a new scale:


General Data

Scale Scale ID OT-SCALE-CUSTOMER

Description Description of thescale

OT – Customerbase scale

Scale Base Defines the basis ofscale, for example,location, distance,duration, and so on.

BP – Business partner

Items BP Number Define BusinessPartner relevant forscale

OT-CU-01



(C) SAP AG 99


Calculation Type Defines how the scalevalues are read Absolute


7. Create a new scale:


General Data

Scale Scale ID OT-SCALE-REGION

Description Description of thescale OT – Regions

Scale Base

Defines the basis ofscale, for example,location, distance,duration, and so on.

Region

Items

Region Defines the regionrelevant to the scale WA

Calculation Type Defines how the scalevalues are read Absolute




(C) SAP AG 100

Defining Rate TablesRates 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-REGIONFB00 – 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 SAPmenu Master Data Charge Management Rate Tables Create Rate TableDefinition .

2. Choose Continue.

3. On the New Table Rate Definition screen, enter a new table rate based on the followingtable:


Rate Table Unique identifier for the ratetable OT-RATE-CR-01

Description Description of the table OT – FTL Rate fromLocation to Region

Charge Usage

Specifies the scenario inwhich the rate table can beused, for example, forcustomer billing integration,supplier invoice integration, ornone

Service Provider

Charge Type Here, the charge type islinked for integration with SAPERP.

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


Scale Reference

Enter the scales defined inDefining Scales [Page 98] .This activates the entries inthe rate table as specified by

the relevant sequence.

1: OT_SCALE_LOC

2: OT_SCALE_REGION

Calculation Base

Determines how the valuesare stored and calculated forthis dimension. Sources ofinformation are predefinedbased on the object.

1: SOURCELOC

2: DESTLOC_REG

6. Select each line and choose Create Scales .


8. Choose the Dates and Values tab page.



Valid From The date as of which the ratetable is valid Today

Valid To The date to which the ratetable is valid 2099 –12 –31

Currency Currency that is applicable forthis rate table USD

Values in Table

Once you have entered thevalidity dates, you can createtable entries for thedimension. To do so, selectthe row containing the validitydates.

Source Location:SP3100@ <logicalsystem >

Destination Region: WA

Value:

1.48 (for OT-RATE-CR-01 )




10. On the Calculation Rules tab page, enter your data based on the following table:


Calculation Base Provides the calculation basefor this rate. In our rate table,the rates are specified asper/mile from source to

ACTUAL_DIST



(C) SAP AG 102


destination locations.However, the calculation basemust be determined to applythese rates. In this case, thecalculation base is distance.

There are various bases suchas business partner role,weight, destination location,and so on.

Quantity

Defines the multiplier for thecalculation base. Forexample, the applicable ratecan be per mile or per 100miles.

1

Unit of Measure

The unit of measure specifies

the unit to which the multiplieris applied.

MI

11. Release and save your data.

12. Repeat the process to define all of your carrier-specific rate tables for the variouscarriers. In our scenario, these are:

o OT-RATE-FB00-CAR-02 (for carrier OT-CR-02 )



13. For the fuel surcharge, add another table based on the following data:


Rate Table Unique identifier for the ratetable OT-RATE-FUEL

Description Description of the tableOT – DestinationDependent FuelSurcharge

Charge Usage

Specifies the scenario inwhich the rate table can be

used, for example, forcustomer billing integration,supplier invoice integration, ornone

Service Provider


FUEL – Fuel Surcharge

Value Percentage Value



(C) SAP AG 103




Dimension

Defines a row (x-axis) orcolumn (y-axis) in the ratetable. A rate table can containmultiple scales (up to 9).

1 for the first scale

Scale Reference

Enter the scales defined inDefining Scales [Page 98] .This activates the entries inthe rate table as specified bythe relevant sequence.

1: OT-SCALE-REGION

Calculation Base

Determines how the valuesare stored and calculated forthis dimension. Sources of

information are predefinedbased on the object.

1: DESTLOC_REG




Valid From The date as of which the ratetable is valid 2010 –01 –01


Life Cycle Status

Once the rate table is fullydefined, it must be set toReleased so that it can beused further. If the rate tableis still in process, you canleave it as Deactivated.

The system sets the valuebased on the follow-up actionusing the following menu:

Set Status Released


Values in Table

Once you have entered thevalidity dates, you can create

table entries for thedimension. To do so, selectthe row containing the validitydates.

Destination Region Location:

WA Value: 0.05


19. For the lumper charges, add another table based on the data below:




(C) SAP AG 104


Rate Table Unique identifier for the ratetable OT-RATE-LMPR

Description Description of the table OT – Lumper Rates

Charge Usage

Specifies the scenario inwhich the rate table can beused, for example, forcustomer billing integration,supplier invoice integration, ornone

Service Provider


LMPR – Lumper Charges

Value Percentage Value




Dimension

Defines a row (x-axis) orcolumn (y-axis) in the ratetable. A rate table can containmultiple scales (up to 9).

1 for the first scale

Scale Reference

Enter the scales defined inDefining Scales [Page 98] .

This activates the entries inthe rate table as specified bythe relevant sequence.

1: OT_SCALE_CUSTOMER

Calculation Base

Determines how the valuesare stored and calculated forthis dimension. Sources ofinformation are predefinedbased on the object.

SHIP_TO_PARTY




Valid From The date as of which the ratetable is valid 2010 –01 –01


Life Cycle Status Once the rate table is fullydefined, it must be set to

The system sets the valuebased on the follow-up action



(C) SAP AG 105


Released so that it can beused further. If the rate tableis still in process, you canleave it as Deactivated.

using the following menu:

Set Status Released


Values in Table

Once you have entered thevalidity dates, you can createtable entries for thedimension. To do so, selectthe row containing the validitydates.

Ship-to Party: OT-CU-01

Value: 50.00




(C) SAP AG 106

Defining Calculation SheetsWithin a freight order or forwarding order, the applicable charges are calculated on the basis ofthe calculation sheet.

Procedure1. On the SAP Easy Access screen for SAP Transportation Management, choose SAP

menu Master Data Charge Management Calculation Sheets Create CalculationSheet .

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:


Calculation Sheet Unique identifier for thecalculation sheet to bedefined

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 thecalculation sheet is used forcustomers, vendors (carriers),both, or neither. Furthermore,indicates whether thecalculation sheet is used onlyfor decision making duringtendering, and so on.

2 – Service Provider

Items screen area:


Item

Indicates the levels of thecharge elements in thecalculation sheet as well asthe descriptions derived fromthe assigned charge types

Enter your items by choosingInsert. In our scenario, we usethe following values:

Base freight ( FB00 )



(C) SAP AG 107


Fuel surcharge ( FUEL)

Lumper charges ( LMPR)

Line No. Defines the sequence inwhich the charge types areexecuted

Entered by the system

Instruction Type

Defines the relationshipbetween charge types andhow the charges are to becalculated for each chargetype. For example, you canspecify whether the itemrepresents a total or a directcalculation of the charge.

FB00 : Standard

FUEL: Standard

LMPR: Standard

Charge Type Specify the TM charge typefor each item.

FB00

FUEL

LMPR

Description

This is a freely definabledescription and issubsequently displayed in thedocuments. We recommendthat you use descriptions thatmake sense in a number ofcontexts.

-

Mandatory Denotes the charge type asmandatory Deselected (for all of ourcharge types)

Currency Applicable currency USD (Not applicable forcharge 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 followinginformation:



Instruction Type Rule to indicate how thecharge item is applied for thecalculation

Standard

Description Description of the charge itemin the calculation sheet

Base Freight – DistBased

Charge Type Assigned charge type FB00



(C) SAP AG 108


Line No . Line number of the item 20

Calculation Resolution Base

Indicates the level at whichthe calculation sheet is to be

applied. For example, it canbe applied at the header levelfor the whole freight order orat a particular stage only.

ROOT

The calculation sheet appliesto the whole document.

Calculation Method Type Calculation method type Standard

On the Rate tab page:


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 followinginformation:




Standard

Description Description of the charge itemin the calculation sheet Fuel Surcharge

Charge Type Assigned charge type FUEL

Line No. Line number of the item 30


Reference-From Line No .Reference item that forms thebasis of the calculation for thisrow

20





(C) SAP AG 109


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:




Standard

Description Description of the charge item

in the calculation sheetLumper Charges

Charge Type Assigned charge type LMPR

Line No. Line number of the item 40




Rate Table Assigned rate table OT-RATE-LMPR

12. Choose Save.



(C) SAP AG 111

Defining Freight AgreementsFreight 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 SAPmenu Master Data Charge Management Freight Agreements Create Freight

Agreement .

2. On the New Freight Agreement screen, enter the relevant freight agreement type in the Agreement Type field. In our scenario, this is OTTL.

3. If the freight agreement is applicable to both carriers and customers, select the Mutual Agreement checkbox. In our scenario, this remains deselected.

4. Choose Continue.

5. On the following screen, enter your data based on the following table:


Agreement Agreement ID OT-FA-CR-01

Description Description of the freightagreement FA: OT-CR-01

Purchasing Organization Default purchasing

organization

<Your purchasing

organization >

Carrier Carrier for which this freightagreement 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:


Item Number Item number 10

Calculation Sheet

Assign the calculation sheetonce only. The details fromthis sheet are copied for eachitem.

OT-TCCS-CR-01



(C) SAP AG 112

7. Once you have entered your data, release the freight agreement by choosing SetStatus Released .

8. Choose Save.

In our scenario, we need to create separate freight agreements for the other carriers. Thetable below shows the values for these carriers. Values for any fields not contained in thistable are the same as those entered in the freight agreement above.

Name of FreightAgreement Description Carrier Calculation Sheet

OT-FA-CR-02 FA: OT-CR-02 OT-CR-02 OT-TCCS-CR-02





(C) SAP AG 113

Defining Settlement ProfilesIn this Customizing activity, you define the profile for creating invoices. The settlement profilecomprises 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 createsettlement documents.

Procedure


Settlement Define Settlement Profile .




Settlement Prof Settlement profile OT_SP_01

Medium Desc. Medium description Settlement Profile

Data Source Identifies the data source tobe used when creatingsettlement documents

Planned Data

Split/Cons.

Defines the split /

consolidation criteria forgenerating settlementdocuments

FSD_CREAT

Calculation Option

Specifies how the values arecalculated when the invoice iscreated. You can copy fixedcharges and recalculateothers, or copy all charges.

A Copy Fixed Charges andRedetermine Others

Collective Invoice Collective invoice Selected




(C) SAP AG 114

Defining Charge Calculation ProfilesProcedure

1. In Customizing for SAP TM, choose Transportation Management Basic Functions Charge Calculation Basic Settings for Charge Calculation Define Calculation Profile .

2. Choose New Entries to create a new entry with the following data:


Calculation Profile Calcution Profile OT_CLCPRF

Description Description OT: Charge CalculationProfile

Calc. Date Ty. Calcuation Date Type EET_DATE (Expected EndDate of Complete Carriage)

Calculation Level Calculation Level 1 (Calculation on HeaderLevel)

Agr. Det. Rule Freight AgreementDetermination Rule Blank

Calc Sheet Det. Rule Calculation SheetDetermination 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




(C) SAP AG 115

Configuring Organizational Settings for ChargeElementsProcedure


Basic Functions Charge Calculation Basic Settings for Charge Calculation DefineGeneral Settings .




Org. Unit Purchasing organization unitInternal ID of OT-PORG-1 (forexample, 500000627 )

Default Purch. Org. Default purchasingorganization 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




(C) SAP AG 117

Defining Transportation AllocationsProcedure

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:


Transportation LaneReference 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:


Orientation Defines the transportationlane 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:


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




End Date End date Year end

Time Zone Time zone EST

Cover Full CalendarUnits Cover full calendar units Selected

In the Buckets screen area:


Sub-Bucket Distribution Sub-bucket distribution No Distribution

Unit of Measure Unit of measure LB

Minimum TAL Quantity Minimum quantity 40000

Maximum TAL Quantity Quantity that should/must notbe exceeded within planningperiod

120000

4. Choose Start .

Allocations are created accordingly.

5. Change the Maximum TAL Quantity of OT-CR-04 up to 500000 carrier in each planningperiod.

6. Choose the Save pushbutton.