Scenario Configuration Guide CUSTOMER SAP · PDF fileScenario Configuration Guide Document version: 6.0 – 2015-12-01 Configuration Guide for Domestic Outbound Transportation SAP

Scenario Configuration GuideDocument version: 6.0 – 2015-12-01

Configuration Guide for Domestic Outbound TransportationSAP Transportation Management

CUSTOMER

Content

1 Configuration Guide for Domestic Outbound Transportation . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 The Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.1 Master Data Setup in SAP ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Defining Shipping Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Defining Customer Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Mapping Organizational Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Defining Carrier Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Defining Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Defining Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.2 Transferring Organizational & Master Data from SAP ERP to SAP TM . . . . . . . . . . . . . . . . . . . . . . . . 203.3 Master Data Setup in SAP TM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Defining Purchasing Organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Defining Purchasing Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Defining Execution Organizations and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Checking the Transfer of Master Data from SAP ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Defining Contact Persons for Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Defining Geocoordinates for Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Defining Transportation Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Defining Means of Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Defining Transportation Lanes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Assigning Carriers to Transportation Lanes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Defining Vehicle Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4 Order Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.1 Maintaining Allocation Structures (CO-PA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.2 Maintaining Settlement Profiles (CO-PA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.3 Defining or Identifying Sales Document Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.4 Assigning Sales Areas to Sales Document Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.5 Defining Sales Document Item Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424.6 Assigning Item Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424.7 Creating Requirements Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.8 Maintaining Requirements Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.9 Defining Requirement Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.10 Assigning Requirement Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.11 Assigning General Ledger Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.12 Mapping TM Charge Types to ERP Condition Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.13 Assigning Transportation Charge Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.14 Assigning Organizational Units for Purchasing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.15 Activating Transfer of Sales Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.16 Activating Transfer of Outbound Deliveries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.17 Defining Conditions for Automatic Determination of Output Types . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configuration Guide for Domestic Outbound TransportationContent

CUSTOMER© Copyright 2015 SAP SE or an SAP affiliate company.

All rights reserved. 3

4.18 Defining Order-Based Transportation Requirement Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.19 Defining Delivery-Based Transportation Requirement Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.20 Defining Conditions for DTR Type Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.21 Defining Conditions for OTR Type Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.22 Defining Customer Incompatibility with Carrier Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.23 Defining TOR Incompatibility with Consignee Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.24 Defining Quantity Tolerance Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.25 Defining Conditions for Pick-Up Delivery Time Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.26 Agency Business . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Activating Class-Based Accounting Document Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Defining Agency Business Billing Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Defining Agency Business Payment Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Defining Agency Business Condition Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Defining Agency Business Calculation Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Determining Agency Business Calculation Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Defining Agency Business Copy Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Configuring Settings for Creating Agency Business Documents . . . . . . . . . . . . . . . . . . . . . . . . . 73 Assigning Agency Business Company Codes to Plants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

4.27 Defining Application and Posting Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

5 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.1 Creating Incompatibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.2 Creating Incompatibility Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.3 Defining Freight Unit Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775.4 Defining Freight Unit Building Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795.5 Creating Delivery Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805.6 Creating Selection Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815.7 Defining Capacity Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825.8 Defining Optimizer Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835.9 Defining Freight Settlement Document Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845.10 Creating Carrier Selection Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845.11 Creating Planning Costs Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855.12 Creating Planning Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885.13 Creating Page Layouts for Transportation Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

6 Freight Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916.1 Defining Freight Order Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

7 Tendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967.1 Defining General Settings for Tendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967.2 Defining Tendering Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

8 Charge Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018.1 Defining Product Group Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018.2 Defining Source Location Scales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028.3 Defining Destination Region Scales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038.4 Defining Destination Zone Scales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048.5 Defining Less-than-Truckload Break-Weight Scales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058.6 Defining Product Group Scales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068.7 Defining Stop-Off Scales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

4

CUSTOMER© Copyright 2015 SAP SE or an SAP affiliate company.All rights reserved.


8.8 Defining Carrier Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1088.9 Defining Fuel Surcharges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138.10 Defining Stop-Off Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1158.11 Defining Calculation Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1178.12 Defining Freight Agreement Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1208.13 Defining Freight Agreements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1218.14 Defining Settlement Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1228.15 Defining Calculation Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1238.16 Defining Cost Distribution Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1248.17 Defining General Settings for Charge Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1248.18 Defining Cost Distribution Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

9 Strategic Freight Procurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269.1 Defining RFQ Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269.2 Defining Optimizer Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1279.3 Assigning Users to Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1279.4 Defining Commodity Type Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1289.5 Defining Source Location Scale Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1289.6 Defining Destination Region Scale Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299.7 Defining Stop-Off Scale Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1309.8 Defining Rate Table Template for Basic Freight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1309.9 Defining Rate Table Template for Fuel Surcharges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1319.10 Defining Rate Table Templates for Stop-Off Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1339.11 Defining Calculation Sheet Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

10 Assigning Event Manager Role to Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

11 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13811.1 Content for File LTL_Rates_03.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13811.2 Content for File LTL_Rates_04.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140




6

CUSTOMER© Copyright 2015 SAP SE or an SAP affiliate company.All rights reserved. Configuration Guide for Domestic Outbound Transportation

1 Configuration Guide for Domestic Outbound Transportation

About this Document

This configuration guide describes a scenario for Domestic Outbound Transportation . You should implement this scenario as described, and once you have verified the functionality, you can modify the data to suit your own environment and operating conditions.

Change HistoryTable 2

Version Date Description

1.0 December 2010 Initial release

1.1 April 2011 Harmonized configuration and master data; scenarios based on IDES

2.0 July, 2011 Modifications to the following sections:

● Mapping Organizational Units [page 16]

● Activating Transfer of Outbound Deliveries [page 48]

● Defining Order-Based Transportation Requirement Types [page 50]

● Defining Freight Unit Types [page 77]

● Creating Selection Profiles [page 81]

● Defining Freight Order Types [page 91]

● Defining General Settings for Tendering [page 96]

● Defining Carrier Rates [page 108]

● Defining Calculation Profile [page 123]

3.0 September 2012 Updated for SAP TM 9.0

4.0 December 2013 Updated for SAP TM 9.1

5.0 October 2015 Updated for SAP TM 9.3

Configuration Guide for Domestic Outbound TransportationConfiguration Guide for Domestic Outbound Transportation



Important SAP Notes

You must read the following SAP Notes before you start using this test scenario. These SAP Notes contain the most recent corrections required to test the scenario.

Make sure that you have the current version of each SAP Note, which you can find on SAP Service Marketplace at

service.sap.com/notes .

Table 3

SAP Note Number Description

1738013 TM: Integration with ERP Enhancement Packages

1530240 FAQ for ERP-TM integration

2229144 Solution Manager Content Updates for SAP TM 9.3

8


Configuration Guide for Domestic Outbound TransportationConfiguration Guide for Domestic Outbound Transportation

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fnotes

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2F~form%2Fhandler%3F_APP%3D01100107900000000342%26_EVENT%3DREDIR%26_NNUM%3D1738013%26_NLANG%3Den%26_NVERS%3D0



2 The Scenario

This document describes the configuration settings for the Domestic Outbound Transportation scenario of SAP Transportation Management (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).

NoteBusiness system groups, logical systems, RFC connections, and system connections used throughout this guide are examples only. Replace these with your own data.

This guide also assumes the use of Business Add-Ins (BAdIs), which add a prefix or suffix to master data

objects transferred from SAP ERP to SAP TM (see SAP Note 458914 ). An overview of the prefixes and suffixes used is provided in the following table:

Table 4

Business Object Prefix Suffix

Carrier CA– None

Customer CU– None

Plant PL– None

Shipping Point SP– None

Supplier SU– None

System None –@ERP001

For example:

Shipping point name in SAP ERP: 1200

Shipping point name in SAP TM: SP1200@ERP001

If you have not implemented the corresponding BAdI in your system, the names of the objects are not changed.

Prerequisites

Before you begin to configure the Domestic Outbound Transportation scenario, see the following guides in SAP Solution Manager under SAP Transportation Management Configuration Structures Basic Settings for TM <release> :

● Integration of SAP TM with ERP

Configuration Guide for Domestic Outbound TransportationThe Scenario




● Integration of SAP TM and SAP Event Management

● Output Management Configuration Guide

● Visual Business Configuration with SAP TM

You must also ensure that automatic workflow Customizing has been set up and that the workflow has been configured. For more information, see SAP Library for SAP NetWeaver 7.31 under Automatic Workflow

Customizing and also SAP Note 1530240 .

System Prerequisites

The scenario requires an ERP system to be configured for at least the following processes:

● SD: Order-to-cash process

○ Sales order entry

○ Delivery creation

○ Posting goods issue

○ Billing document creation

○ Transfer to accounting

● MM: Purchase order process

○ Purchase order entry

○ Logistics invoice verification

○ Invoice document creation (ERS settlement)

○ Transfer to accounting

● FI/CO

○ The processes listed above

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

Geographic and Organizational Unit Prerequisites

This scenario is based on a transportation network in the United States with a plant and shipping point in Chicago. To use the transportation network as described in the configuration, the plant used in the customer system should be located in the same area.

10




Figure 1: “Domestic Outbound Transportation” Scenario

The following organizational structures and document types are used by default, and need to be adjusted to customer-specific organizational structures as required:

Table 5

Company Code 3000

Controlling Area 2000

Plant 3100

Storage Location 0001

Shipping Point 3100

Sales Organization 3000

Distribution Channel 10

Division 00

Sales Document Type ODOT




3 Master Data

Activities

● Master Data Setup in SAP ERP [page 12]

● Transferring Organizational & Master Data from SAP ERP to SAP [page 20]

● Master Data Setup in SAP TM [page 21]

3.1 Master Data Setup in SAP ERP

Activities

● Defining Shipping Points [page 12]

● Defining Customer Master Data [page 13]

● Mapping Organizational Units [page 16]

● Defining Carrier Master Data [page 16]

● Defining Products [page 17]

3.1.1 Defining Shipping Points

Procedure

1. In Customizing for SAP ERP, choose Enterprise Structure Definition Logistics Execution Define, Copy, Delete, Check Shipping Point.

2. Enter the following data:

Table 6

Field Value

Shipping Point 3100

Street W Cermak Road

Number 1955

City Chicago

Region IL

Country US

Postal Code 60608

12


Configuration Guide for Domestic Outbound TransportationMaster Data

3. Save your entries.

3.1.2 Defining Customer Master Data

Procedure

1. On the SAP Easy Access screen for SAP ERP, choose Logistics Sales and Distribution Master DataBusiness Partner Customer Create Complete or call transaction XD01 .

2. Enter customer master data as in the following:

○ Use account group KUNA: General Customers

○ Reconciliation Account: 140000○ Terms of Payment: 0001○ Price Group: 01○ Cust.-Pricing Procedure: 1○ Delivering Plant: 3100○ Shipping Conditions: 01○ Account Assignment Group: 01○ Tax Classification for All Tax Codes: 0 (tax exempt)

○ Incoterms: FH3. For all of the customers, use the following data:

○ Company Code: 3000○ Sales Organization: 3000○ Distribution Channel: 10○ Division: 00Table 7

Customer ID in ECC System

Name Address Time Zone

DOT-CU-01 Sutherlands

1200 Commerce Drive

Plano

TX 75024

United States

CST

DOT-CU-02

Cedar Supply

1135 W Arkansas Lane

Arlington

TX 76017

United States

CST

DOT-CU-03

Massworks 500 Bryan Avenue

Fort Worth

TX 76104

CST






United States

DOT-CU-04

Creekside 13358 Floyd Cir

Richardson

TX 75080

United States

CST

DOT-CU-05

Midwest Industries

1048 Jacobson Rd

Garland

TX 75040

United States

CST

DOT-CU-06

Chase Supplies

1262 Chase Road

Mesquite

TX 75180

United States

CST

DOT-CU-07

Cary Brands

800 Independence Ave

Evansville

IN 47713

United States

CST

DOT-CU-08

Douglas Corporation

599 Northwestern Parkway

Louisville

KY 40212

United States

EST

DOT-CU-09

Great Divide

10 Highland Ave

Carrollton

KY 41008

United States

EST

DOT-CU-10 Steele Manufacturing

21300 South Fries Avenue

Long Beach

CA 90745

United States

PST

DOT-CU-11 Avelco 300 17th St

Atlanta

GA 30363

United States

EST

DOT-CU-12 Sitton 737 106th Ave.

Bellevue

WA 98004

PST

14





United States

DOT-CU-13 Melc 6760 NW 37th Avenue

Miami

FL 33147

United States

EST

DOT-CU-14 NovaAg 401 Jefferson Hwy

Jefferson

LA 70121

United States

CST

DOT-CU-15 Freeman 4245 Main Ave

Fargo

ND 58103

United States

CST

DOT-CU-16 Delta Pulp and Wood

3899 Jackson Street

Denver

CO 80205

United States

MST

DOT-CU-17 Provomore 1415 State Street

Provo

UT 84604

United States

MST

DOT-CU-18 Salefish 100 Berry Street

San Francisco

CA 94158

United States

PST

DOT-CU-19 Promotory 4727 Union Hills Drive

Phoenix

AZ 85050

United States

MST

DOT-CU-20

VolHaven 6209 Old Rutledge Pike

Knoxville

TN 37924

United States

EST





3.1.3 Mapping Organizational Units

Procedure

1. In Customizing for SAP ERP, choose Integration with Other SAP Components Transportation Management Invoice Integration Invoicing Mapping of Organizational Units Assign Organizational Units for Purchasing .

2. Choose New Entries.


Table 8

Field Value

Logical System <Logical name of the connected TM system>

TM Pur. Organization <Purchasing organization number> DOT-PORG-1

TM Purchasing Group <Purchasing group number/DOT-PGRP-1> DOT-PGRP-1

Settlement Type 001

Purchasing Org . 3000

Purch. Group P01

Plant 3100

Company Code 3000

Document Type NB

Material Group 007


3.1.4 Defining Carrier Master Data

Procedure

1. On the SAP Easy Access screen for SAP ERP, choose Logistics Logistics Execution Master DataPartner Service Agent Create or call transaction XK01 .

2. Enter the following data for account group 0005 (for each carrier):

Press F8 to switch to the next screen.

Table 9

Field Value

SAP TM Code DOT-CR-01 DOT-CR-02 DOT-CR-03 DOT-CR-04

16



Field Value

X PGI Truck Lines National Trucking Fast Trucking & Logistics

Green Transport

Street Windgap Ave Durand Ave Spring Street Port Jersey Blvd

City Pittsburgh Trenton Reading Jersey City

Region PA NJ PA NJ

Ctry US US US US

Postal Code 15204 08611 19601 07305

Time Zone CST CST CST CST

Company Code 3000 3000 3000 3000

Purchase Org . 3000 3000 3000 3000

Recon.Account 151000 151000 151000 151000

Order Currency USD USD USD USD

Incoterm CFR CFR CFR CFR

Cash Mgmnt Group A1 A1 A1 A1

3. Create carrier DOT-CR-05 in the same way that you created carrier DOT-CR-01, and create carrier DOT-CR-06 in the same way that you created carrier DOT-CR-02.

4. Enable GR-Based Inv. Verif. for all carriers.


3.1.5 Defining Products

Procedure

1. On the SAP Easy Access screen for SAP ERP, choose Logistics Materials Management Material Master Material Create (General) Immediately or call transaction MM01 .


○ Material DOT-PROD-01

○ Industry sector Mechanical engineering

○ Material type Semifinished product

3. Choose Select View(s) and select the following views:

○ Basic Data 1

○ Sales: Sales Org. Data 1

○ Sales: Sales Org. Data 2

○ Sales: General/Plant Data

○ Purchasing

○ Accounting 1




4. On the Org. Levels screens, enter the following organizational levels:

○ Plant 3100○ Storage location 0001○ Sales organization 3000○ Distribution channel 10

5. On the Basic Data 1 view:

Table 10

Field Value

Description DOT-PROD-01

Material Group 002

Base Unit of Measure BAG

Gross Weight 100

Net Weight 95

Weight Unit LB

Volume 10

Volume Unit FT3

6. On the Sales: Sales Org. Data 1 view, enter tax data based on the following:

Table 11

Country Tax Category Tax Classification

US USA UTXJ Tax Jurisdict. Code

1 Taxable

US USA UTX2 County Sales Tax 1 No Tax

US USA UTX3 City Sales Tax 1 No Tax

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

Table 12

Field Value

Item Category Group NORM

Material Pricing Grp 01

Acct Assignment Grp 01

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

Table 13

Field Value

Availability Check KP – no check

Trans. Grp 0001

Loading Grp 0001

18



9. On the Purchasing view:

Table 14

Field Value

Material Freight Grp 02

10. On the Accounting 1 view:

Table 15

Field Value

Price Control S

Standard Price 100

Valuation Class 7900


3.1.6 Defining Conditions

Procedure

1. On the SAP Easy Access screen for SAP ERP, choose Logistics Sales and Distribution Master DataConditions Select Using Condition Type Create or call transaction VK11 .

2. On the Create Condition Records screen, enter condition type PR00 and choose Key Combination .

3. In the Key Combination dialog box, select the first entry and press ENTER .

4. On the Create Price Condition (PR00): Fast Entry screen, enter the following data:

Table 16

Field Value

Sales Organization 3000

Distribution Channel 10

Customer DOT-CU-01

Material DOT-Prod-01

Amount 85

Unit USD

per 1

Unit of Measure (UoM) Bag

Valid from 01.01.2012

Valid to 31.12.2012


6. Repeat the above steps for all of your customers.




3.2 Transferring Organizational & Master Data from SAP ERP to SAP TM

In this procedure, you create and activate an integration model, which selects the plant and receiving point data and transfers them to SAP TM, creating, or updating locations and business partners.

In SAP TM, locations of location type 0001 (plant) are created for the plants. Business partners with role BBP000 (vendor) are created automatically for plants and shipping points. The business partner is assigned to the location.

Procedure

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 .


Table 17

Field Value

Model Name DOT-IM-001

Logical System Logical system ID of SAP TM target system, for example, TM1 CLNT 001

APO Application <Logical TM system>

3. In the Material Dependent Objects screen area, select the Materials and Plants checkboxes.

4. In the Material Independent Objects screen area, select the Customers , Vendors , and Shipping Points checkboxes.

NoteWhen you transfer vendors to the SAP TM system, you must ensure that the Create Loc./BP function (create business partners in SAP TM for the location) is set to 2 on the Vendors and Customers tab pages so that business partners and locations are generated for vendors.

5. On the relevant selection screens, enter the following data:

Table 18

Field Value

Plant 3100

Material DOT-PROD-01

Carrier (Vendor) DOT-CR-01 to DOT-CR-06

Customer DOT-CU-01 to DOT-CU-20

Shipping Point 3100

6. Choose Execute to continue. The selected filter objects – plants, materials and shipping points – are displayed on the result screen with the relevant number of filtered objects.

7. Choose Generate IM to create the integration model.

20



8. Leave the transaction.

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


Table 19

Field Value

Model Name DOT-IM-001

Logical System Logical system ID of SAP TM target system, for example, TM1 CLNT 001

APO Application <Logical TM system>

11. Choose Execute to continue. The created version of the selected integration model is listed.

12. Click the red cross in the table (indicating that the integration model version is inactive) in the first row and column New Status . The icon changes to a green check mark (indicating that the integration model is active).

13. Choose Start from the tool bar to start the activation and save.

14. If necessary, confirm all dialog boxes to run the data transfer.

3.3 Master Data Setup in SAP TM

Activities

● Defining Purchasing Organizations [page 21]

● Defining Purchasing Groups [page 22]

● Defining Execution Organizations and Groups [page 23]

● Checking the Transfer of Master Data from SAP ERP [page 25]

● Defining Geocoordinates for Locations [page 27]

● Defining Transportation Zones [page 29]

● Defining Means of Transport [page 31]

● Defining Transportation Lanes [page 32]

● Assigning Carriers to Transportation Lanes [page 34]

● Defining Vehicle Resources [page 36]

3.3.1 Defining Purchasing Organizations

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Organization Create Organization and Staffing .

2. Enter validity dates in the first dialog box.




3. On the Basic Data tab page at the bottom of the screen, enter the following information:

Table 20

Field Description Value

Organizational unit Identifier DOT-PORG-1

Description General description DOT: Purchasing Org US

4. On the Org. Data tab page, choose the Create pushbutton and enter the following information:

Table 21


Organization ID Identifier for the organizational unit DOT-PORG-1

Org. Unit Function Not applicable 2 – Purchasing

Org. Unit Role Role of this organizational unit 1 – Organization

5. On the Address tab page, enter the following information:

Table 22

Field Value

Subtype <Main Address>

Street/House W Cermak Road 155

City Chicago

Postal Code 60608

Country US

Region IL


3.3.2 Defining Purchasing Groups

Procedure




Table 23


Organizational unit Identifier DOT-PGRP-1

Description General description DOT: Purchasing Group US


22



Table 24


Organization ID Identifier for the organizational unit <Next number generated by system>

Org. Unit Function Not applicable 2 – Purchasing

Org. Unit Role Role of this organizational unit 3 – Group


Table 25

Field Value


Street/House W Cermak Road 155

City Chicago

Postal Code 60608

Country US

Region IL


3.3.3 Defining Execution Organizations and Groups

Procedure




Table 26


Organizational unit Identifier DOT-PEORG-1

Description General description DOT: Planning and Organization


Table 27


Organization ID Identifier for the organizational unit <Organizational unit defined previously>

Org. Unit Function Not applicable 13 – Planning and Execution





Org. Unit Role Role of this organizational unit 1 – Organization


Table 28

Field Value


City Chicago

Country US


7. Repeat the procedure to create a purchasing execution group.

8. On the Basic Data tab page, enter the following data:

Table 29


Organizational Unit Specifies the organizational unit to be created

DOT-PEGRP-1

Description General description DOT: Planning & Execution Group

9. On the Org. Data tab page, choose the Create pushbutton and enter the following data:

Table 30


Org. ID Organizational unit identifier. This is an internal number.

<Organizational unit that you previously defined>

Org. Unit Function Specifies the type of organizational unit

13 – Planning and Execution

Org. Unit Role Specifies the role of the organizational unit

3 – Group

10. On the Address tab page, enter the following data:

Table 31


Subtype Defines the type of address Main Address

City City Chicago

Country Country of the address US


24



3.3.4 Checking the Transfer of Master Data from SAP ERP

Master data such as plants and customers can be transferred from SAP ERP to SAP Transportation Management via CIF. Other master data has to be created directly in the SAP TM system.

In this procedure, you check that the master data from SAP ERP has been transferred correctly to SAP TM (for more information, see Transferring Organizational & Master Data from SAP ERP to SAP [page 20] ).

Prerequisites

You have transferred the following data from SAP ERP to SAP TM using CIF:

Table 32

Plant 3100

ERP and TM Code for Customers DOT-CU*

ERP and TM Code for Carriers (Vendors) DOT-CR*

ERP and TM Code for Materials DOT*

Procedure

Checking Products

1. In SAP NetWeaver Business Client, choose Master Data General Define Product or call transaction /SAPAPO/MAT1 .

2. Check that the following data has been transferred successfully to SAP TM:

Table 33

Attribute Value

Product DOT-PROD-01@ERP001

Storage location 0001

Sales organization 3000

Distribution channel 10

Material group 001

Gross weight 100

Net weight 95

Weight unit LB

Volume 10

Volume unit FT3

Transportation group 0001

Item category group NORM




Attribute Value

Price control S

Standard price 100

Storage condition 03

Base unit of measure Bag

Product freight group 100

Packaging material type 0002

Checking Business Partners

1. In SAP NetWeaver Business client, choose Master Data General Define Business Partner .

2. Check that customers DOT-CU-01 to DOT-CU-20 have the business partner roles Ship-to Party ( CRM002 ) and Sold-to Party ( CRM000 ).

3. Check that carriers DOT-CR-01 to DOT-CR-06 have the business partner role Vendor ( BBP000 ).

NoteTo add a new business partner role, select the relevant role from the Display in BP role dropdown box and then save your changes.

3.3.5 Defining Contact Persons for Carriers

Contact persons must be defined for carriers to answer requests for quotations (RFQs) in the collaboration portal.

Prerequisites

● You have defined carriers (vendors) in SAP ERP.

● You have transferred the business partner data to SAP TM.

Procedure

1. In SAP NetWeaver Business Client for SAP Transportation Management, choose Master Data GeneralDefine Business Partner (BP) .

2. Choose the Person pushbutton to create a new business partner of type “person” .

3. Enter the business partner name as DOT-CP-01 .

4. Choose the Relationships pushbutton.

5. Change the relationship category to is contact person for .

6. Enter carrier DOT-CR-01 in the Relationship to BP field, 0101 <current year> and 31122099 as the validity, and then choose Create .

7. Click Continue in the pop-up that appears.

26



8. Switch to the BP role Internet User and navigate to the Internet User tab page.

9. Create additional contact persons for carriers DOT-CR-02 to DOT-CR-06 in the same way.

3.3.6 Defining Geocoordinates for Locations

Once you have defined your locations in the SAP ERP system and transferred the data to SAP TM, you must define geocoordinates for your locations.

Prerequisites

● You have defined the master data for locations in SAP ERP.

● You have transferred the location data to SAP TM.

Procedure

1. On the SAP Easy Access screen for SAP TM, choose Transportation Management Master DataTransportation Network Location .

2. Enter your location as defined in Defining Customer Master Data [page 13] .

3. Choose Change .

4. In the Geographical Data screen area of the General tab page, enter the following longitudes:

Table 34

Customer Location Sign Degrees Minutes Seconds

CU DOT-CU-01 @ERP001

– 96 46 20


– 97 7 16


– 97 19 31


– 96 44 52


– 96 40 17


– 96 39 17


– 87 33 1


– 85 49 5




Customer Location Sign Degrees Minutes Seconds


– 85 11 6


– 118 15 59


– 86 6 59


– 122 11 56


– 80 15 27


– 90 8 4


– 96 49 53


– 104 56 25


– 111 40 10


– 122 23 44


– 111 58 44


– 83 50 36

5. Enter the following latitudes:

Table 35

Customer/Location Sign Degrees Minutes Seconds


+ 33 0 47


+ 32 42 23


+ 32 42 47


+ 32 55 52


+ 32 54 9

28



Customer/Location Sign Degrees Minutes Seconds


+ 32 47 Blank


+ 37 56 41


+ 38 16 19


+ 38 40 50


+ 33 50 7


+ 33 58 24


+ 47 37 1


+ 25 50 7


+ 29 57 54


+ 46 52 34


+ 39 46 16


+ 40 15 12


+ 37 46 26


+ 33 39 18


+ 36 1 33


3.3.7 Defining Transportation Zones

Carriers calculate charges based on different transportation zones. You therefore need to define these transportation zones in the SAP Transportation Management system.




Procedure

1. In SAP NetWeaver Business Client, choose Master Data Transportation Network Transportation Zones Define Transportation Zone .

2. Create zone DOT-US-MIDWEST .

3. On the Zone – Location tab page, choose Create and assign the following data to this transportation zone:

Table 36

Location Description

SP3100 @ERP001 Chicago

4. On the Zone – Region tab page, choose Create and assign the regions as follows:

Table 37

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. Create zones DOT-US- <XXX> accordingly.

7. Assign regions to transportation zones as follows:

Table 38

DOT-US-MIDWEST

DOT-US-SOUTH DOT-US-MOUNTAIN

DOT-US-WEST DOT-US-SOUTHEAST

DOT-US-NORTHEAST

3100 (as described above)

TX CO CA GA KY

… LA UT WA FL …

… … AZ … TN …


9. Create the following transportation zones and select the zone type Postal Code Zone :

Table 39

Transportation Zone Postal Code Range

DOT-ZIP-606 60654 – for the Chicago plant/shipping point

30



Transportation Zone Postal Code Range

DOT-ZIP-303 30300 – 40199

DOT-ZIP-477 47000 – 59999

DOT-ZIP-402 40200 – 40299

DOT-ZIP-410 41000 – 41099

DOT-ZIP-701 70100 – 99999


More Information

Defining Carrier Rates [page 108]

3.3.8 Defining Means of Transport

Procedure

1. In Customizing for Transportation Management , choose Master Data Resources Define Means of Transport .

2. Choose New Entry and enter the following data:

Table 40

Field Value

Means of Transport DOT_FTL

MTr Description Full Truckload Trailer

Transportation Mode 01 - ROAD

Multiresource Select

Number of Individual Resources 999

Average Speed 70,000

Distance Factor 1,000

Table 41

Field Value

Means of Transport DOT_LTL

MTr Description Less-than-Truckload


Multiresource Select




Field Value

Number of Individual Resources 999



Table 42

Field Value

Means of Transport DOT_INML

MTr Description DOT Intermodal


Schedule MTr Checked




NoteSince this scenario does not make use of a geographical information system (GIS), you must enter a distance factor and an average speed. If you have a connection to a GIS provider, select the GIS Quality attribute and enter the three different average speeds instead.

When you save, the system may issue a message stating that the IGS or GIS tool is unavailable. Ignore this message.

3.3.9 Defining Transportation Lanes

Procedure

1. On the SAP Easy Access screen for SAP TM, choose Master Data Transportation Network Define Transportation Lane or call transaction /SAPAPO/SCC_TL5 .

2. Create the following transportation lanes and use the following data for each lane:

○ Start Date: January 1, 2000

○ End Date: December 31, 3000

○ Relevant to Carrier Selection: Selected

○ Priority/Costs: X (Neither costs nor priority)

○ Cost Origin: I (Internal Costs)

○ Continuous Move Type: No Continuous Move

32



Table 43

Start Location or Zone

Destination Location or Zone

Means of Transport

Transportation Costs

Unit for Cost Rate

MTr Costs

SP 3100 @ERP001

DOT-US-WEST DOT_FTL … … 0.932

SP 3100 @ERP001

DOT-US-SOUTHEAST

DOT_FTL … MI 1.25

SP 3100 @ERP001

DOT-US-SOUTH DOT_FTL … MI 1.25

SP 3100 @ERP001

DOT-US-MOUNTAIN

DOT_FTL … MI 1.25

SP 3100 @ERP001

DOT-US-MIDWEST

DOT_FTL … MI 1.25

SP 3100 @ERP001

DOT-US-NORTHEAST

DOT_FTL … MI 1.25

SP 3100 @ERP001

DOT-US-WEST DOT_LTL 0.15 LB …

SP 3100 @ERP001

DOT-US-SOUTHEAST

DOT_LTL 0.15 LB …

SP 3100 @ERP001

DOT-US-SOUTH DOT_LTL 0.15 LB …

SP 3100 @ERP001

DOT-US-MOUNTAIN

DOT_LTL 0.15 LB …

SP 3100 @ERP001

DOT-US-MIDWEST

DOT_LTL 0.15 LB …

SP 3100 @ERP001

DOT-US-NORTHEAST

DOT_LTL 0.15 LB …

DOT-US-NORTHEAST

DOT-US-NORTHEAST

DOT_FTL 1.25 MI …

DOT-US-NORTHEAST

DOT-US-MIDWEST

DOT_FTL 1.25 MI …

DOT-US-MIDWEST

DOT-US-MIDWEST

DOT_FTL 1.25 MI …

DOT-US-SOUTH DOT-US-SOUTH DOT_FTL 1.25 MI …

DOT-US-SOUTHEAST

DOT-US-SOUTHEAST

DOT_FTL 1.25 MI …

DOT-US-WEST DOT-US-WEST DOT_FTL 1.25 MI …

DOT-US-MOUNTAIN

DOT-US-MOUNTAIN

DOT_FTL 1.25 MI …





3.3.10 Assigning Carriers to Transportation Lanes

Procedure

1. On the SAP Easy Access screen for SAP TM, choose Master Data Transportation NetworkTransportation Lanes Define Transportation Lane or call transaction /SCMTMS/TL5 .

2. Open the relevant transportation lane.

3. Assign FTL carriers to the FTL lanes and LTL carriers to the LTL lanes according to the table below.

4. Add the following carriers:

NoteMark all carrier assignments as relevant for P2P Tendering.

Select the Consider Carrier for P2P Tendering checkbox for all carriers.

Table 44: From SP3100@ERP001 to DOT-US-WEST

BP No. Means of Transp. Start Date End Date Prio.

DOT-CR-01 DOT_FTL 1/1/2000 12/31/3000 1

DOT-CR-02 DOT_FTL 1/1/2000 12/31/3000 2

DOT-CR-03 DOT_LTL 1/1/2000 12/31/3000 1

DOT-CR-04 DOT_LTL 1/1/2000 12/31/3000 2

Table 45: From SP3100@ERP001 to DOT-US-SOUTHEAST


DOT-CR-01 DOT_FTL 1/1/2000 12/31/3000 1

DOT-CR-02 DOT_FTL 1/1/2000 12/31/3000 2

DOT-CR-03 DOT_LTL 1/1/2000 12/31/3000 1

DOT-CR-04 DOT_LTL 1/1/2000 12/31/3000 2

Table 46: From SP3100@ERP001 to DOT-US-SOUTH


DOT-CR-01 DOT_FTL 1/1/2000 12/31/3000 2

DOT-CR-02 DOT_FTL 1/1/2000 12/31/3000 1

DOT-CR-03 DOT_LTL 1/1/2000 12/31/3000 1

DOT-CR-04 DOT_LTL 1/1/2000 12/31/3000 2

Table 47: From SP3100@ERP001 to DOT-US-MOUNTAIN


DOT-CR-01 DOT_FTL 1/1/2000 12/31/3000 1

DOT-CR-02 DOT_FTL 1/1/2000 12/31/3000 2

DOT-CR-03 DOT_LTL 1/1/2000 12/31/3000 1

34




DOT-CR-04 DOT_LTL 1/1/2000 12/31/3000 2

Table 48: From SP3100@ERP001 to DOT-US-MIDWEST


DOT-CR-01 DOT_FTL 1/1/2000 12/31/3000 1

DOT-CR-02 DOT_FTL 1/1/2000 12/31/3000 2

DOT-CR-03 DOT_LTL 1/1/2000 12/31/3000 1

DOT-CR-04 DOT_LTL 1/1/2000 12/31/3000 2

Table 49: From SP3100@ERP001 to DOT-US-NORTHEAST


DOT-CR-01 DOT_FTL 1/1/2000 12/31/3000 1

DOT-CR-02 DOT_FTL 1/1/2000 12/31/3000 2

DOT-CR-03 DOT_LTL 1/1/2000 12/31/3000 1

DOT-CR-04 DOT_LTL 1/1/2000 12/31/3000 2

Table 50: From DOT-US-NORTHEAST to DOT-US-NORTHEAST


DOT-CR-01 DOT_FTL 1/1/2000 12/31/3000 1

DOT-CR-02 DOT_FTL 1/1/2000 12/31/3000 2

Table 51: From DOT-US-WEST to DOT-US-WEST


DOT-CR-01 DOT_FTL 1/1/2000 12/31/3000 1

DOT-CR-02 DOT_FTL 1/1/2000 12/31/3000 2

Table 52: From DOT-US-SOUTHEAST to DOT-US-SOUTHEAST


DOT-CR-01 DOT_FTL 1/1/2000 12/31/3000 1

DOT-CR-02 DOT_FTL 1/1/2000 12/31/3000 2

Table 53: From DOT-US-SOUTH to DOT-US-SOUTH


DOT-CR-01 DOT_FTL 1/1/2000 12/31/3000 1

DOT-CR-02 DOT_FTL 1/1/2000 12/31/3000 2

Table 54: From DOT-US-MOUNTAIN to DOT-US-MOUNTAIN


DOT-CR-01 DOT_FTL 1/1/2000 12/31/3000 1

DOT-CR-02 DOT_FTL 1/1/2000 12/31/3000 2




Table 55: From DOT-US-MIDWEST to DOT-US-MIDWEST


DOT-CR-01 DOT_FTL 1/1/2000 12/31/3000 1

DOT-CR-02 DOT_FTL 1/1/2000 12/31/3000 2


3.3.11 Defining Vehicle Resources

Vehicle resources model the trucks that deliver goods from the shipper to the consignee. The trucks are part of the carrier’s own fleet. You define trucks as means of transport, to which you assign the vehicle resource. In this scenario, we assume that the shipper does not have its own fleet.

Procedure

1. On the SAP Easy Access screen for SAP TM, choose Master Data Resources Define Resource or call transaction /SCMTMS/RES01 .

2. Create new entries with the following General Data :

Table 56

Resource Description Means of Transport

Time Zone Factory Calendar Finite Scheduling

DOT_US_FTL_001

DOT_US_FTL_001

DOT_FTL CST 01 Select

DOT_US_FTL_002

DOT_US_FTL_002

DOT_FTL CST 01 Select

DOT_US_LTL_001

DOT_US_LTL_001

DOT_LTL CST 01 Select

DOT_US_LTL_002

DOT_US_LTL_002

DOT_LTL CST 01 Select

3. On the Time-Cont. Capacity tab page, enter the following data for each resource:

Table 57: DOT_US_FTL_001

Dimension Capacity Unit Comment

Mass 40000 LB The maximum weight of the truck

Volume 2500 FT3 The maximum volume of the truck

36



Table 58: DOT_US_LTL_002

Dimension Capacity Unit Comment

Mass 40000 LB The maximum weight of the truck

Volume 2500 FT3 The maximum volume of the truck

4. Enter the remaining resources.





4 Order Management

Activities

● Defining or Identifying Sales Document Type [page 41]

● Assigning Sales Areas to Sales Document Types [page 41]

● Activating Transfer of Sales Documents [page 47]

● Activating Transfer of Outbound Deliveries [page 48]

● Defining Conditions for Automatic Determination of Output Types [page 49]

● Defining Order-Based Transportation Requirement Types [page 50]

● Defining Delivery-Based Transportation Requirement Types [page 51]

● Defining Conditions for OTR Type Determination [page 54]

● Defining Customer Incompatibility with Carrier Condition [page 56]

● Defining TOR Incompatibility with Consignee Condition [page 56]

● Defining Quantity Tolerance Condition [page 57]

● Defining Conditions for a Pick-Up Delivery Time Windows [page 58]

4.1 Maintaining Allocation Structures (CO-PA)

You can either use an existing allocation structure in this step or you can create a new one.

Procedure

1. In Customizing for SAP ERP , choose Controlling Product Cost Controlling Cost Object ControllingProduct Cost by Sales Order Period-End Closing Settlement Create Allocation Structures .

2. If required, create allocation structure TM with the description TM Settlement Sales Orders .

3. Choose the TM entry.

4. Double-click Assignment and choose New Entries to create an assignment with the following data:

Table 59

Assignment Text

11 Total Costs

21 Revenues

5. Press Enter to confirm your entries.

6. Select the assignment 11 Total Costs and double-click Settlement Cost Elements .

7. Select controlling area 2000 – CO N. America.

8. Choose New Entries and enter the following data:

38


Configuration Guide for Domestic Outbound TransportationOrder Management

Table 60

Receiver Cat. By Cost Element Settlement Cost Elem

PSG Not selected 656000

SDI Not selected 656000


10. Double-click Assignment , select 21 Revenues , and double-click Settlement cost elements ALL

11. Choose New Entries and enter the following data:

Table 61

Receiver Cat. By Cost Element Settlement Cost Elem

PSG Not selected 666000

SDI Not selected 666000



14. If the system issues a warning message, press Enter to confirm.

4.2 Maintaining Settlement Profiles (CO-PA)

You can either use an existing settlement profile in this step or you can create a new one.

Procedure

1. In Customizing for SAP ERP , choose Controlling Product Cost Controlling Cost Object ControllingProduct Cost by Sales Order Period-End Closing Settlement Create Settlement Profiles or call transaction OKO7 .

2. If required, create settlement profile TM0001 with the description TM Settlement Sales Orders and the following settings:

In the Actual Costs/Cost of Sales screen area:

Table 62

Field Name Value

To be settled in full Selected

Can be settled Not selected

Not for settlement Not selected

In the Default Values screen area:

Table 63

Field Name Value

Allocation Structure TM




Field Name Value

PA Transfer str, 30

Default object type PSG

In the Indicators screen area:

Table 64

Field Name Value

100% validation Selected

%-Settlement Selected

Equivalence numbers Not selected

Amount Settlement Not selected

Var. to costing based PA Selected

In the Valid Receivers screen area:

Table 65

Field Name Value

G/L account Settlement optional

Cost Center Settlement optional

Order Settlement optional

WBS element Settlement optional

Fixed Asset Settlement optional

Material Settlement optional

Network Settlement not allowed

Profit. Segment Settlement optional

Sales order Settlement optional

Cost objects Settlement optional

Order item Settlement optional

Business proc. Settlement not allowed

Real Est.Object Settlement not allowed

In the Other Parameters screen area:

Table 66

Field Name Value

Document type SA

Max.no.dist. rls 10

Residence time 3


40



4. If the system issues a warning message, press Enter to confirm.

4.3 Defining or Identifying Sales Document Type

An existing sales order type can be used for this integration, or you can create a new sales order type. Common scenarios include a normal sales order type in the standard system (order type: OR) or a rush order (order type: RO).

Procedure

1. In Customizing for SAP ERP , choose Sales and Distribution Sales Sales Documents Sales Document Header Define Sales Document Type or call transaction VOV8 .

2. Use the standard order type (OR) to create an ODOT entry.

3. Press Enter and confirm the Dependent Entries for Copy Control dialog box. Enter DOT Sales Order as the description.


Result

The order type ODOT is created.

4.4 Assigning Sales Areas to Sales Document Types

Procedure

1. In Customizing for SAP ERP , choose Sales and Distribution Sales Sales Documents Sales Document Header Assign Sales Area to Sales Document Types .

2. Choose Assign Sales Order Types Permitted for Sales Area .

3. On the Change view Control Key Parameters , ensure that the following settings exist:

Table 67

Field Description User Action and Values

Ref S Sales organization 3000

RefD Distribution channel 10

Div Divisions 00

SaTy Sales document type ODOT




Result

The order type ODOT is assigned to a sales area.

4.5 Defining Sales Document Item Categories

In this procedure, you can either use an existing sales document item category or you can create a new one. Common scenarios use a standard sales document item category of type TAN .

Procedure

1. In Customizing for SAP ERP , choose Sales and Distribution Sales Sales Documents Sales Document Item Define Item Categories .

2. If required, copy sales document item category TAN and create sales document item category TMAN with the following data (retain all other existing settings):

Table 68

Field Value

Description TM Item w/ CO-PA

Completion Rule B

Pricing X

Business Item Selected

Sched.Line Allowed Selected

Determine Cost Selected

Screen Seq.Grp N

Billing Form Blank

DIP Prof. Blank

Usage Blank


4.6 Assigning Item Categories

In this procedure, you assign the new TMAN item category so that it can be used.

42



Procedure

1. In Customizing for SAP ERP , choose Sales and Distribution Sales Sales Documents Sales Document Item Assign Item Categories .

2. Create the following entry or copy a standard entry and add the following data:

Table 69

Field Value

Sales Document Type ODOT

Item Category Group NORM

Default Item Category TMAN


4.7 Creating Requirements Classes

In this procedure, you create the requirements class TM1 .

Procedure

1. In Customizing for SAP ERP , choose Sales and Distribution Basic Functions Availability Check and Transfer of Requirements Transfer of Requirements Define Requirement Classes or call transaction OVZG .

2. Create the following entry:

Table 70

Field Value

Reqmts class TM1

Description TM: Sales Order w/ CO-PA

Acct Assign. Category E


4.8 Maintaining Requirements Classes

In this procedure, you maintain requirements class TM1 .




Procedure

1. In Customizing for SAP ERP , choose Sales and Distribution Basic Functions Account Assignment/Costing Maintain Requirements Classes For Costing/Account Assignment .

2. Select requirements class TM1 and choose Details .


Table 71

Field Value

Requirement Class TM1

Description TM: Sales Order w/ CO-PA

Costing Variant PCO4

Account assignment category E

Settlement profile TM0001

Results Analysis Key 000004


4.9 Defining Requirement Types

Procedure

1. In Customizing for SAP ERP , choose Sales and Distribution Basic Functions Availability Check and Transfer of Requirements Transfer of Requirements Define Requirement Types .

2. Create an entry using the following data:

Table 72

Requirement Type Requirement Type – Short Description

Requirement Class Requirement Class – Short Description

TM1 TM: Sales Order w/ CO-PA TM1 TM: Sales Order w/ C


4.10 Assigning Requirement Types

Procedure

1. In Customizing for SAP ERP , choose Sales and Distribution Basic Functions Availability Check and Transfer of Requirements Transfer of Requirements Determination of Requirement Types Using Transaction or call transaction OVZI .

2. Choose sales document item category TMAN and configure the following settings:

44



Table 73

Item Category Type Requirement Type Origin Requirement Type

TMAN ND TM1 Blank


4.11 Assigning General Ledger Accounts

In this procedure, you assign general ledger accounts (G/L accounts).

Procedure

1. In Customizing for SAP ERP, choose Sales and Distribution Basic Functions Account Assignment/Costing Revenue Account Determination Assign G/L Accounts or call transaction VKOA .

2. On the Assign G/L Account screen, select table 1 ( Cust.Grp/MaterialGrp/AcctKey ) and click the magnifying glass icon ( Choose ).

3. On the Change View "Cust.Grp/MaterialGrp/AcctKey": Overview screen, enter the following data:

Table 74

App CndTy. ChAc SOrg. AAG AAG ActKy G/L Account

V KOFK CAUS 3000 01 01 ERL 888000

V KOFK CAUS 3000 01 01 ERF 809000


4.12 Mapping TM Charge Types to ERP Condition Types

Procedure

1. In Customizing for SAP ERP, choose Integration with Other SAP Components Transportation Management Invoice Integration Mapping for Cost Distribution Assign Transportation Charge Elements to Condition Types .

2. On the Change View "Map TM Charge Type to ERP Conditions Types": Overview screen, enter the following data:

Table 75

Cat.Code Subcat.Cd. Charge Type Sales Cnd Type. Purchase Cnd Type

004 100000 FB00 Blank FB00

003 103008 FUEL Blank FUEL

002 609102 STOP Blank STOP




Cat.Code Subcat.Cd. Charge Type Sales Cnd Type. Purchase Cnd Type

004 710000 DISC Blank DISC


4.13 Assigning Transportation Charge Types

Procedure

1. In Customizing for SAP ERP, choose Integration with Other SAP Components Transportation Management Invoice Integration Invoicing Assignment of Transportation Charge Elements Assign Service Master Record and Account Assignment Category .

2. On the Change View "Map Transportation Charge Item to Service Master Record": screen, choose New Entries .

3. On the New Entries: Overview of Added Entries screen, enter the following data:

Table 76

Cat.Code Subcat.Cd Charge Type Activity Number A Service Short Text

004 100000 FB00 1000020 F Base Freight

003 103008 FUEL 1000020 F Base Freight

004 710000 DISC 1000020 F Base Freight

002 609102 STOP 1000020 F Base Freight


4.14 Assigning Organizational Units for Purchasing

Procedure

1. In Customizing for SAP ERP, choose Integration with Other SAP Components Transportation Management Invoice Integration Invoicing Mapping of Organizational Units Assign Organizational Units for Purchasing .

2. On the Change View "Map Transportation Charge Item to Service Master Record": screen, choose New Entries .


Table 77

Field Value

Logical System <Your logical system ID> (for example,

CITCLNT700 )

46



Field Value

TM Pur. Organization <Your TM purchasing organization>

TM Purchasing Group Blank

Settlement Type DOT6

Purchasing Org. 3000

Purch. Group Blank

Plant 3100

Company Code 3000

Document Type NB


4.15 Activating Transfer of Sales Documents

In this procedure, you activate the transfer of sales documents to SAP TM by assigning a control key to the required sales document types. The sales documents can be sales orders or returns orders. The control key determines whether a sales document and the corresponding outbound delivery are transferred to SAP TM, and also whether sales order scheduling is to be carried out in SAP ERP or in SAP TM.

When you create a sales document for which the transfer has been activated, the system assigns the control key to the sales document (parameter TM_CONTROL_KEY) and to all relevant documents in the document chain (for example, the outbound delivery). This is a fixed parameter that cannot be changed subsequently in the sales document.

Prerequisites

You have defined the required control keys in the Customizing activity Define Control Keys for Document Transfer .

Procedure

1. In Customizing for SAP ERP, choose Integration with Other SAP Components Transportation Management Order Integration Activate Transfer of Sales Documents .

2. On the Sales Document Transfer screen, add a new entry for the following combinations:

Table 78


Sales Organization Applicable sales organization 3000

Dist. Channel Applicable distribution channel 10





Division Applicable division 00

Sales Document Type Sales order type that we need to integrate to the TM system

ODOT

Control Key Control key combination as defined above

0001

Shipping Condition Shipping condition 01-standard

TM Number Client number of the target SAP TM system. This needs to be worked with your BASIS expert.

XXXX 1

3. Save your entries.1 The TM number is relevant only if you have more than one ERP system connected to your SAP TM system.

Result

The order type is now activated to integrate with SAP TM.

4.16 Activating Transfer of Outbound Deliveries

In this procedure, you activate the transfer of outbound deliveries to SAP TM by assigning a control key to the required document types.

Prerequisites

You have defined the required control keys in the Customizing activity Define Control Keys for Document Transfer .

Procedure

1. In Customizing for SAP ERP, choose Integration with Other SAP Components Transportation Management Order Integration Activate Transfer of Delivery Documents .

2. On the Delivery Document Transfer screen, add a new entry for the following combinations:

Table 79


Shipping Point Applicable shipping point 3100

Delivery Type Delivery type assigned to your order type

LF

48




Shipping Condition Shipping condition Blank

Control Key Control key for document transfer 0005

TM Number Technical SAP TM number XXXX 1

3. Save your entries.1 The TM number is relevant only if you have connected more than one ERP system to your SAP TM system.

Result

The delivery type is activated to integrate with SAP TM.

4.17 Defining Conditions for Automatic Determination of Output Types

In this optional procedure, you define the conditions under which output types can be determined automatically for outbound deliveries. This prevents users from having to enter the output types in the delivery each time the delivery is created. Provided that a condition type has been maintained, the output types are determined automatically.

Prerequisites

You have configured the output type ( TRD0 ).

Procedure

1. On the SAP Easy Access screen, choose Logistics Materials Management Purchasing Master DataSubsequent Settlement Customer Rebate Agreements Environment Customer MessagesShipping Create or call transaction VV21 .

2. Enter the output type TRD0 to maintain the condition and press ENTER .

3. Maintain this condition type with all the relevant data as follows:

Table 80


Del. Type Delivery type LF

Name Defaulted by previous entry Delivery

Funct . Function Blank

Partner Partner Blank





Medium Medium 8

Date/Time Date and time 4

Lang . Language …


4.18 Defining Order-Based Transportation Requirement Types

This document type is used to map the order-based transportation requirement (OTR) that is received from ERP. This document type is used in the step where this mapping is done.

Prerequisites

A freight unit building rule needs to be defined – or can be defined later – and then entered in this configuration procedure.

Procedure

1. In Customizing for SAP TM, choose Transportation Management Integration ERP Logistics Integration Order-Based Transportation Requirement Define Order-Based Transportation Requirement Types .

2. On the Create View Order-Based Transportation Requirement Types: Details of Selected Set screen, enter the following values:

Table 81


OTR Type ID for our OTR document type DOT1

Description Description of the OTR type being defined

Sales Order

Default Type There is only one OTR type that could be defined as a default OTR type. Leave this value blank. Select this value if this is the only OTR type defined in the system.

…

Number Range Interval Number range that is used for assigning the numbers to the OTR types. In our scenario, l use the range as indicated.

01

50




Process Control/Business Object Mode

… …

BW Relevance Indicates if this document type is relevant for BW

Select

Automatic FU Building Indicates if the freight units are to be built automatically. If this is selected, an FU building rule must be defined.

Select

Output Profile Print profile for document type /SCMTMS/TRQ_FWO_PRINT

Propagate Changes This indicates how changes to a document’s information (such as quantities) are passed around.

Synchronous Propagation of Changes, Fallback to Asynchronous

Default Values … …

Default Weight UoM Default UoM for weight for this document type

LB

Default Gross Volume UoM Default UoM for gross volume for this document type

FT3

Plan on Requested/Confirmed Quantity

Indicator for planning that indicates which quantities – Planned or Confirmed – to take into account when planning

01 – Plan on Requested Quantities

Planning Profile Profile for planning the freight unit DOT-PLAN-PROF-01This is created later. Leave blank and update after creating the profile.

Freight Unit Building Rule Rule that is used when building freight units (when the Automatic FU Building indicator above is selected)

DOT-FUBR-STANDARDThis is created later. Leave blank and update after creating the rule.

4.19 Defining Delivery-Based Transportation Requirement Types

This document type is used to map the delivery-based transportation requirement (DTR) that is received from SAP ERP. This document type is used in the step where this mapping is carried out.

Prerequisites

A freight unit building rule needs to be defined – or can be defined later – and then entered in this configuration procedure.




Procedure

1. In Customizing for SAP TM, choose Transportation Management Integration ERP Logistics Integration Delivery-Based Transportation Requirement Define Delivery-Based Transportation Requirement Types .

2. On the Create View Delivery-Based Transportation Requirement Types: Details of Selected Set screen, enter the following values:

Table 82


DTR Type ID for our DTR document type. DOT2

Description Description of the DTR type being defined.

Delivery

Default Type There is only one DTR type that could be defined as a default DTR type. Leave this value blank. Select this value if this is the only DTR type defined in the system.

…

Number Range Interval Number range that will be used for assigning the numbers to the OTR types. In our scenario, use the range as indicated.

02

Process Control/Business Object Mode

… …

BW Relevance Indicates if this document type is relevant for BW.

Select

Automatic FU Building Indicates if the freight units are to be built automatically. If this is selected, a FU building rule must be defined.

Select

Output Profile Print Profile for document type. /SCMTMS/TRQ_FWO_PRINT

Propagate Changes This indicates how the changes to a document’s information (such as quantities) are passed around.

Synchronous Propagation of Changes, Fallback to Asynchronous

Default Values … …

Default Weight UoM Default UoM for gross weight for this document type.

LB

Default Volume UoM Default UoM for gross Volume for this document type.

FT3

Freight Unit Building Rule … DOT-FUBR-STANDARD

52



4.20 Defining Conditions for DTR Type Determination

When the SAP TM system receives a delivery, it creates a delivery-based transportation requirement (DTR). This must be mapped to a document in the SAP TM system to determine the subsequent workflow process.

In this configuration step, the DTR type is determined when a delivery is transferred from SAP ERP to SAP TM.

Prerequisites

You have defined DTR document types.

Procedure

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

2. Choose Application Administration General Settings Conditions Create Condition .

3. Choose Continue.

NoteIf the system issues a message stating that the condition already exists, continue this process using the edit condition entry from the point at which you maintain values on the Decision Table tab page.

4. On the New Condition Definition screen, enter the relevant data based on the tables below:

In the General Data screen area

Table 83


Condition Condition type supplied by the system ZDTR_TYPE

Description Description of the condition type DTR Type Determination Condition

In the Condition Definition screen area:

Table 84


Condition Type Condition type supplied by the system /SCMTMS/DTR_TYPE

Origin of Condition Source of the condition information Condition based on BRFplus Decision Table

5. Choose the Data Access Definition tab page and enter the following data:

Table 85


Line 10 Select this row for further maintenance

Data Access Definition: /SCMTMS/TRQ_DLV_CAT


Data Access Definition: /SCMTMS/TRQ_DLV_TYPE




6. Choose the Decision Table tab page and enter the following data:

Table 86


TR: ERP Delivery Typ Incoming base document type Parameter: Is Equal To LF

DTR Type Specify the data for integration here – the document type that is identified and used in SAP TM for DTR.

DOT2 (defined in a previous step)

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


Result

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

4.21 Defining Conditions for OTR Type Determination

When the SAP TM system receives a sales order, it creates an order-based transportation requirement (OTR). This requirement must be mapped to a document in the SAP TM system, which then determines the subsequent workflow process.

In this configuration step, the OTR type is determined when an order is transferred from SAP ERP to SAP TM.

Prerequisites

You have defined the OTR document types.

Procedure

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

2. Choose Application Administration General Settings Conditions Create Condition .

3. Choose Continue.

NoteIf the system issues a message stating that the condition already exists, continue this process using the edit condition entry from the point at which you maintain values on the Decision Table tab page.

4. On the New Condition Definition screen, enter the relevant data based on the tables below:

54



In the General Data screen area:

Table 87


Condition Condition type supplied by the system ZOTR_TYPE

Description Description of the condition type OTR Type Determination Condition

In the Condition Definition screen area:

Table 88


Condition Type Condition type supplied by the system /SCMTMS/OTR_TYPE

Origin of Condition Source of the condition information Condition based on BRFplus Decision Table

5. Choose the Data Access Definition tab page and enter the following data:

Table 89



Data Access Definition: /SCMTMS/TRQ_ORD_CAT


Data Access Definition: /SCMTMS/TRQ_ORD_TYPE

6. Choose the Decision Table tab page and enter the following data:

Table 90


TR: Original Order C Incoming base document type Parameter: Is Equal To

Value: 114 – Sales Order

TR: ERP Order Type Procedure type (incoming parameter) Parameter: Is Equal To

Value: ODOT

OTR Type Specify the data for integration here – the document type that is identified and used in SAP TM for OTR.

DOT1(defined in a previous step)

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


Result

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




4.22 Defining Customer Incompatibility with Carrier Condition

Procedure

1. In SAP NetWeaver Business Client, choose Application Administration General Settings ConditionsCreate Condition .

2. On the New Condition Definition screen , enter the following data:

Table 91


Condition : Condition DOT-INCOMP-COND-CARR-CUST

Description Description of the condition Carrier and Customer Incompatibility

Condition Type Condition type (this is a system-supplied condition type)

/SCMTMS/INC_CARRIER

Origin of Condition From where the condition information is derived

Direct Business Object Access

3. Choose Continue .

4. In the Data Access Definition table, choose Create and enter the following data:

Table 92

Field Value

Column Position in BRFplus Decision Table 10

Data Access Definition for Conditions /SCMTMS/CARRIER_ID

Data Object Description Carrier ID

Data Element Used for Input Help BU_PARTNER


4.23 Defining TOR Incompatibility with Consignee Condition

You can use this procedure to create a condition to enable the incompatibility of a carrier with a customer.

Procedure


2. Edit or create the condition type that needs to be created.

3. On the Edit Condition Definition or New Condition Definition screen, enter the following values:

56



Table 93


Condition Condition DOT-INCOMP-TOR-INCOM

Description Description of the condition type TOR Incompatibility

Condition Type Condition type (this is a system-supplied condition type)

/SCMTMS/INC_TO

Origin of Condition From where the condition information is derived

Direct Business Object Access

4. Choose Continue .

5. In the Data Access Definition table, choose Create and enter the following data:

Table 94

Field Value

Column Position in BRFplus Decision Table 10

Data Access Definition for Conditions /SCMTMS/TOR_CONSIGNE

Data Object Description Consignee ID

Data Element Used for Input Help /SCMTMS/PTY_CONSIGNEE


4.24 Defining Quantity Tolerance Condition

Procedure


2. Create a condition.

3. On the New Condition Definition screen, enter the following values:

Table 95

Field Value

Condition DOT-QTOL-01

Description Quantity Tolerance

Condition Type /SCMTMS/CC_QUAN_TOL

Origin of Condition Condition Based on BRFplus Decision Table

4. Choose the Continue pushbutton.

5. Choose the Data Access Definition pushbutton and enter the following values in the table:




Table 96

Column Value

Data Access Definition for Conditions /SCMTMS/TOR_TYPE

Data Element Used for Input Help /SCMTMS/TOR_TYPE

6. In the Business Object Based Data Access Definition screen area, enter the following data:

Table 97

Column Value

Name of BO Used in Condition /SCMTMS/TOR

Name of BO Node Used in Condition ROOT

Name of the Field of the BO Node TOR_TYPE

7. In the decision table for row 10, enter the following data:

Table 98

Column Value

TO Type DOT4

Qty Change X

4.25 Defining Conditions for Pick-Up Delivery Time Windows

Procedure


2. Create a condition with the following general data and settings:

Table 99

Condition Name Description Condition Type Origin of Condition

DOT-PUDL-001 NON_DLV_COST /SCMTMS/TOR_TIMEWIND Condition based on BRFplus Decision Table

3. On the Data Access Definition tab page, choose Create and enter the following data:

Table 100

Field Value

Column 00

Data Access Definition for Conditions /SCMTMS/TOR_TYPE

Data Element Used for Input Help /SCMTMS/TOR_TYPE

4. Choose Enter .

5. Choose Insert New Row in the Decision Table area.


58



Table 101

Field Value Remark

TO Type DOT3 Freight unit type

EarlstStay 48:00 Converts to 480,000

Prem. Stay 24:00 Converts to 240,000

Earliness 1 …

Lateness 1 …

Del. Stay 24:00 Converts to 240,000

Lat. Stay 72:00 Converts to 720,000

4.26 Agency Business

4.26.1 Activating Class-Based Accounting Document Creation

In this procedure, you activate the WLF_SR_ACCOUNTING Business Add-In (BAdI), which is used to create accounting documents based on classes (instead of the standard version that uses function group WLFB ) for settlement requests.

Procedure

1. In Customizing for SAP ERP, choose Logistics – General Agency Business Activate Class-Based Accounting Document Creation Settlement Request .

2. Activate BAdI WLF_SR_ACCOUNTING .

4.26.2 Defining Agency Business Billing Types

Procedure

1. In Customizing for SAP ERP, choose Logistics – General Agency Business Billing Billing Document Types .

2. On the Change View: ”Agency Business: Billing Document Types”: Overview screen, choose New Entries .

3. On the New Entries: Details of Added Entries screen, enter billing type TM0C and the description TM Mat Val cancel .

4. In the Number Systems screen area, enter number range internal assignment 01 (agency documents).

5. In the General Control screen area, enter the following data:




Table 102

Field Value

Business Partner Vendor

Billing Category Invoice Reversal

Settlement Type Material Adjustment

Valuation Procedure No New Valuation

Change Documents Inactive

Doc. Type Bar Code Incoming Invoice

Negative Net Value Allowed

Negat. Effective Val Allowed

Items Cannot be configured

Events Called with data container

Context Blank

SMT Context Blank

Distribtn Active No

Main Item Active If Distribution active

Weight/Volume Total Qty

Relevant arrangement Not selected

Enter plant data Selected

Read info record Not selected

Payment curr active Not selected

Zero value allowed Selected

Fill reference doc data Not selected

6. In the Pricing screen area, enter the following data:

Table 103

Field Value

Price change group Blank

Document Schema TM VBD Group

Extra Item data Do not include

Tax Determintn Transfer from Pricing

Hierarchy Cat. Vendor Blank

Hier. Cat. Customer Blank

Application Purchasing

Vendor Country Standard (Billing)

60



Field Value

Customer Country Standard (Billing)

Triangular Deal Ind. No Proposal

FinalProcess. Vendor Yes

FinProc. Customer No

7. In the Default Data screen area, enter the following data:

Table 104

Field Value

Exchange Rate Type Blank

Def. exch. rate date Posting Date

Price date default Posting Date

Default actvy reason Blank

Reference Documents Do Not Display as Standard

Assignment number Reference Number

Reference Number Blank

Payment reference Blank

8. In the Cancellation screen area, enter the following data:

Table 105

Field Value

Reversal bill. Type Blank

FI Cancell. Method Not Cleared automatically

Cancell. Varnt Via Billing Category

Billing type only for Can docs Blank

Item cancellation Allwd Not selected

9. In the Accounting screen area, enter the following data:

Table 106

Field Value

Document type Accounting document

Diff.Doc.Ty.f.Cust. Blank

Negative posting No Negative posting

Vendor payment block Free for Payment

Debtor Payment Block Free for Payment

Profit. analysis Inactive

Item Text FI Text Reason for Transaction Otherwise Text Billing Doc




Field Value

Statist. Conditions Yes (without cash discount)

Check Posting Date Yes

Tax Code Active No

PymtCrcy Amount Recalculation After Aggregation

10. In the Class-Based Accounting Document Creation screen area, enter the following data:

Table 107

Field Value

Partner Lines at Item Level No

Insert Mode (FI Lines Itms) Add and Summarize at the End

11. In the Control of Accounting Determination screen area, enter the following data:

Table 108

Field Value

Acct Determ. Procedure MM Account determination

Acct key settlement Freight Provisions

AccKeyTrfrSetlmtCust Blank

AcctKey VendClearing Blank

Accrual Account Freight purch. acct.

Account Determ.Proc. Blank

Exchange Rate Diff. Blank

Acct Key Mat. Val. Update Blank

12. In the Credit Management screen area, enter the following data:

Table 109

Field Value

Credit Management Not Check active

Document credit grp Blank

Limit Check In Case of Credit Value Change at Header Level and on Saving

13. In the Follow-On Document Creation General screen area, choose Ignore Billing Category Preceding Document .

14. In the Remuneration List screen area, leave the Remuner.list type field blank and in the Custmz RmLstNo. field, choose Reference 1 (BSEG-XREF 1) .

15. In the Partner screen area, enter the following data:

Table 110

Field Value

Header partners Blank

62



Field Value

Item partners Blank

Partner Are Not determined from Master data

16. In the Text Determination screen area, enter the following data:

Table 111

Field Value

TextDetermProcedure 01 Standard

Text ID Blank

Text determ.proc.itm 01 01 Standard

17. In the Control of Statistics Update screen area, choose Update via MSC45VDLST / MC45DLST from the dropdown box.

18. In the Document Index screen area, set the document index update to For Changeable Documents .

19. In the Identification Object screen area, enter the following data:

Table 112

Field Value

Entry – Invoicing Party Direct(ly)

Identification Object Type Vendor Blank

Entry of Invoice Recipient Direct(ly)

Identificatn Object Type Customer Blank

Type Vendor – MatNo. Blank

Entry of Material Direct(ly)

20. In the Partner Roles for Partner Data Determination screen area, enter the following data:

Table 113

Field Value

Invoice Recipient Bill-to-party

Invoicing Party Invoicing Party

Alternative Creditor Blank

21. In the Intrastat Control screen area, set the Intrastat field to Inactive and leave the Goods Flow field blank.

22. In the VAT Registration Number screen area, enter the following data:

Table 114

Field Value

Vendor VAT ID Do Not Propose

Default for Vendor VAT ID Country of Invoicing party

Check for Vendor VAT ID Blank

Customer VAT ID Do Not Propose




Field Value

Default for Customer VAT ID Country of Bill-to Party

Check for Customer VAT ID Blank

Check Availability of Own VAT ID No

23. Save your entries and then repeat the above steps to create billing type TM01 with the description TM Mat. Val. Posting . Use the following data:

Table 115

Field Value

No.range int.assgt 01 Agency documents

Business Partner Vendor

Billing category Invoice

Settlement Type Material Adjustment

Valuation Procedure No New Valuation

Change documents Inactive

Doc. Type Bar Code Incoming Invoice

Negative Net Value Allowed

Negat. Effective Val Allowed

Items Cannot be configured

Events Called with data container

Context Blank

SMT Context Blank

Distribtn Active No

Main Item Active If Distribution active

Weight/Volume Total Qty

Relevant arrangement Selected

Enter plant data Selected

Read info record Selected

Payment curr active Not selected

Zero value allowed Selected

Fill reference doc data Not selected

Price change group Blank

Document Schema TM VBD Group

Extra Item data Do not include

64



Field Value

Tax Determintn Transfer from Pricing

Hierarchy Cat. Vendor Blank

Hier. Cat. Customer Blank

Application Purchasing

Vendor Country Standard (Billing)

Customer Country Standard (Billing)

Triangular Deal Ind. No Proposal

FinalProcess. Vendor Yes

FinProc. Customer No

Exchange Rate Type Blank

Def. exch. rate date Posting Date

Price date default Posting Date

Default actvy reason Blank

Reference Documents Do not Display as Standard

Assignment number Reference Number

Reference Number Blank

Payment reference Blank

Reversal bill. Type TM0C

FI Cancell. Method Not cleared automatically

Cancell. Varnt Via Billing Category

Billing type only for Can docs Blank

Item cancellation Allwd flag

Document type Accounting document

Diff.Doc.Ty.f.Cust. Blank

Negative posting No Negative posting

Vendor payment block Free for Payment

Debtor Payment Block Free for Payment

Profit. analysis Active

Item Text FI Text Reason for Transaction Otherwise Text Billing Doc

Statist. Conditions Yes (without cash discount)

Check Posting Date Yes

Tax Code Active No




Field Value

PymtCrcy Amount Recalculation after Aggregation

Partner Lines at Item Level No

Insert Mode (FI Lines Itms) Add and Summarize at the End

Acct Determ. Procedure MM Account determination

Acct key,settlement Freight Provisions

AccKeyTrfrSetlmtCust Blank

AcctKey VendClearing Blank

Accrual Account Freight purch acct

Account Determ.Proc. Blank

Exchange Rate Diff. Blank

Acct Key Mat. Val. Update Blank

Credit Management Not check active

Document credit grp Blank

Limit Check In Case of Credit Value Change at Header Level and on Saving

Follow-On Doc. Crtn Ignore Billing Category Preceding Document

Remuner.list type Blank

Custmz RmLstNo. Reference 1 (BSEG-XREF 1)

Header partners Blank

Item partners Blank

Partner Are Not Determined from Master data

TextDetermProcedure 01 Standard

Text ID Blank

Text determ.proc.itm 01 01 Standard

BW Cont. Settlemnt Update via MSC45VDLST / MC45DLST

Document Index Update For Changeable Documents

Entry – Invoicing Party Direct(ly)

Identification Object Type Vendor Blank

Entry of Invoice Recipient Direct(ly)

Identificatn Object Type Customer Blank

Type Vendor – MatNo. Blank

Entry of Material Direct(ly)

66



Field Value

Invoice Recipient Bill-to-party

Invoicing Party Invoicing Party

Alternative Creditor Blank

Intrastat Inactive

Goods Flow Blank

Vendor VAT ID Do Not Propose

Default for Vendor VAT ID Country of Invoicing party

Check for Vendor VAT ID Blank

Customer VAT ID Do Not Propose

Default for Customer VAT ID Country of Bill-tp-party

Check for Customer VAT ID Blank

Check Availability of Own VAT ID No


4.26.3 Defining Agency Business Payment Types

Procedure

1. In Customizing for SAP ERP, choose Logistics – General Agency Business Payment Payment Types .

2. Choose New Entries .

3. Enter payment type TM02 .

4. In the Control screen area, enter the following data:

Table 116

Field Value

Payment type Single Document

Entry category With logistics data

Remuner. list recip. Vendor

Condition level Vendor side

Settlement calender Blank

Incompleteness No check

Remuner. list date On the basis of cash discount days 1

Schema determin. type Without customer schema




Field Value

Post sales values Using pricing

Split FI Documents For deferred Tax only

Tax Code From Pricing Determination

Tax Code Missing Error Message

RL Conditions Not checked for Existence

Cross-Company code Inactive

Settlement Procedure Classic Method (Using Posting Status Single Document

Settlement Partner None

5. In the Default Values screen area, set the gross value to Automatically for Single Documents .

6. In the Assigned Billing Document Types screen area, set the billing type to TM01 TM Mat Val Posting .

7. In the Customer-Side Settlement screen area, set the customer settlement generation to On Header Level (Standard) .

8. In the Vendor-Side Settlement screen area, set the generation of vendor settlement to On Header Level (Standard) .


4.26.4 Defining Agency Business Condition Types

Procedure

1. In Customizing for SAP ERP, choose Logistics – General Agency Business Basic Settings Define Price Determination Process Define Condition Types .

2. Choose the Define Condition Type activity.

3. On the Change View "Conditions: Condition Types": Overview screen, choose New Entries .

4. On the New Entries: Details of Added Entries screen, enter condition type FB00 and the description TM Freight Cost .

5. In the Control Data 1 screen area, enter the following data:

Table 117

Field Value

Cond. class A Discount or surcharge

Calculat.type B Fixed Amount

Cond.category F Freight

6. In the Changes which can be made screen area, enter the following data:

68



Table 118

Field Value

Manual entries C Manual entry has priority

Item condition select

Value select

7. In the Master Data screen area, set the delete fr. DB field to Do not delete (set the deletion flag only) .


9. Repeat these steps to create the condition type FUEL with the description TM Fuel Surcharge . Use the following data:

Table 119

Field Value





Item condition Selected

Value Selected

delete fr. DB Do not delete (set the deletion flag only)


11. Repeat these steps to create the condition type DISC with the description TM Discount . Use the following data:

Table 120

Field Value






Value Selected



13. Repeat these steps to create the condition type STOP with the description TM Price per Stop . Use the following data:

Table 121

Field Value





Field Value





Value Selected


4.26.5 Defining Agency Business Calculation Schemas

The following procedure uses accounting key FR2 . If required, you can define your own accounting key and use this instead of accounting key FR2 .

Procedure

1. In Customizing for SAP ERP, choose Logistics – General Agency Business Basic Settings Define Price Determination Process Define Calculation Schema .

2. On the Change View:"Schemas": Overview screen, choose New Entries .

3. Enter procedure TMV002 and the description TM Settlement Request Schema .

4. Select your new entry and choose Control data .

5. On the Change View:"Control data": Overview screen, choose New Entries and enter the following data:

Table 122

Step Counter CType Description Manual SuTot. AccKey Accruals

100 0 FB00 Freight Cost FB00

Select 9 FR2 FR1

200 0 FUEL Freight Cost FB00

Select 9 FR2 FR1

300 0 STOP Freight Cost BAF

Select 9 FR2 FR1

400 0 DISC Freight Cost CAF

Select 9 FR2 FR1


70



4.26.6 Determining Agency Business Calculation Schemas

This procedure is optional.

Procedure

1. In Customizing for SAP ERP, choose Logistics – General Agency Business Basic Settings Define Price Determination Process Calculation Schema Determination .

2. Choose the activity Calculation Schema Determination for Settlement Request .

3. On the Change View Calculation Schema Determination for Settlement Request screen, choose New Entries and enter the following data:

Table 123

POrg Schema Gp Document Schema Schema Grp Vndr Procedure Description

Blank T1 Blank TMV002 TM Settlement Request Schema


5. Repeat the above steps to create another determination rule.

6. Choose the activity Calculation Schema Determination for Settlement Request .

7. On the Change View “Calculation Schema Determination for settlement request” screen, choose New Entries and enter the following data:

Table 124

POrg Schema Gp Document Schema

Schema Grp Vndr

Cust.pric.proc SchemaVend Description

Blank T1 Blank Blank TMV002 TM Settlement Request Schema


4.26.7 Defining Agency Business Copy Control

Procedure

1. In Customizing for SAP ERP, choose Logistics – General Agency Business Basic Settings Copy Control .

2. Choose the activity Agency Document to Agency Document .

3. On the Change View "Copy Control: Agency Document by Agency Document”: Overview screen, choose New Entries .

4. On the New Entries: Details of Added Entries screen, enter the target billing type TM01 and the description TM Mat Val Posting .




5. Enter the source billing type TM01 and the description TM Mat Val Posting .

6. In the Data Transfer screen area, enter the following data:

Table 125

Field Value

Pricing type Blank

PricingExchRate type Blank

Prc Exch Rt Dtrmntn Type f. Copying Copy from Reference Document

Payment exchan. rate Blank

Settlement Type From Billing Document

Posting Rules Take from Preceding Document

Posting Dates Transfer According to Standard

Calculation Schema On Copy Transfer as Preceding Document

Copy VAT ID to Follow-On Document No Copying; Redetermine dependent BillingDocType Customizing

Partner Not copied, Partners are reset

7. Save and go back.

8. Choose the activity Previous Document Category to Agency Document .

9. On the Change View "Copy Control: Preceding Document Category to Agency Document”: Overview screen, choose New Entries .

10. On the New Entries: Details of Added Entries screen, enter target billing type TM01 and the description TM Mat Val posting .

11. Choose preceding document category A (External Transaction).

12. In the Data Transfer screen area, enter the following data:

Table 126

Field Value

Pricing type Copy Price component and redetermine scales

Settlement Type From Preceding Document

Copy item number Selected

13. Save your entry and create another entry using the following data:

Table 127

Field User Action and Values

Target Billing Type TM0C

Description TM Mat Val cancel

Preceding doc.categ A

Pricing type Copy Price component and redetermine scales

Settlement Type From Preceding Document

72




Copy item number Selected


4.26.8 Configuring Settings for Creating Agency Business Documents

Procedure

1. In Customizing for SAP ERP, choose Integration with Other SAP Components Transportation Management Invoice Integration Mapping for Cost Distribution Posting via Agency Business Basic Settings for Creation of Agency Documents .

2. On the Display View: "Application": Details screen, choose the following entry:

Table 128

Field Value

Application 1 – Transportation Management

3. Double-click Data Used for Agency Document Creation and check the following data:

Table 129

Reference Category

Use Case Type

Condition Application

Agency Document Category

Payment Type

Billing Type Procedure Settlement Partner

Sales Order/Contract

31 Freight Distribution on G/L Account

Purchase Settlement TM02 SD Cost Posting

Blank TMV002 None

Delivery 31 Freight Distribution on G/L Account

Purchase Settlement TM02 SD Cost Posting

Blank TMV002 None

NoteThe settlement partner setting here overrides the setting in the payment type. For more information, see Defining Agency Business Payment Types [page 67] .




4.26.9 Assigning Agency Business Company Codes to Plants

Procedure

1. In Customizing for SAP ERP, choose Logistics – General Agency Business Basic Settings Assign Company Code to Plant .

2. On the Change View "Subsequent Settlement/Agency Business: Plant for CoCd” Overview screen, choose New Entries .


Table 130

CoCd Company Name City Plnt Name 1

3000 Blank Blank 3100 Blank


4.27 Defining Application and Posting Type

Procedure

1. In Customizing for SAP ERP, choose Integration with Other SAP Components Transportation Management Invoice Integration Mapping for Cost Distribution Posting via Agency Business Define Application and Posting Type .

2. On the Change View "Application": Details screen, choose New Entries .


Table 131

Field Value

Application 1

Description Transportation Management

Application

Document Flow Reference REF_NUMBER

Container Structure Blank

Condition Structure WZRE_S_EXT_COND_DESCR_TM


74



5 Planning

Activities

● Creating Incompatibilities [page 75]

● Creating Incompatibility Settings [page 76]

● Defining Freight Unit Types [page 77]

● Defining Freight Unit Building Rules [page 79]

● Creating Delivery Profiles [page 80]

● Creating Selection Profiles [page 81]

● Defining Capacity Settings [page 82]

● Defining Optimizer Settings [page 83]

● Defining Freight Settlement Document Types [page 84]

● Creating Carrier Selection Settings [page 84]

● Creating Planning Costs Settings [page 85]

● Creating Planning Profiles [page 88]

5.1 Creating Incompatibilities

You can use this procedure to define the SAP TM settings based on the conditions for the incompatibility.

Procedure

1. In SAP NetWeaver Business Client, choose Application Administration Planning General SettingsIncompatibility Definitions Create Incompatibility .

2. In the Incompatibility Definition screen area, enter the following values:

Table 132


Incompatibility Incompatibility DOT-INCOMP-CARRIER-CUSTOMER

Description Description Carrier Cust. Incompatibility

Determination Method Determination Method Condition-Based Incompatibility

External Determination Strategy External Determination Strategy …

Identical Values Only : Identical Values Only: Deselect

Configuration Guide for Domestic Outbound TransportationPlanning




Incompatibility Area Incompatibility Area 05 – Carrier Selection

Incompatibility Type Incompatibility Type 81 – Carrier – Transportation Order

Manual Violation Manual Violation Warning If Incompatibility Is Violated

Automatic Violation Automatic Violation Incompatibility Must Not Be Violated

3. In the Conditions screen, area, enter the following data:

Table 133


First Condition Incompatibility condition that is to be used. The condition can be created directly from the link in this field. The details of this condition are specified below.

DOT-INCOMP-COND-CARR-CUST

Relevant Condition Result Incompatibility setting outcome DOT-CR-02

Second Condition Incompatibility condition that is to be used. The condition can be created directly from the link in this field. The details of this condition are specified below.

DOT-INCOMP-TOR-INCOM

Relevant Condition Result Incompatibility setting outcome DOT-CU-14


5.2 Creating Incompatibility Settings

You can use incompatibilities to define the compatibility of planning data that the system is to take into account during transportation planning. For example:

● Refrigerated goods must only be transported in an appropriate means of transport (refrigerated trucks).

● A particular means of transport cannot be unloaded at a location, as the location does not have a suitable loading ramp.

● Customers do not want specific carriers to load or unload at their locations.

In this way, you can control the assignment of freight units to transportation plans (in other words, planned transportation activities) and transportation plans to means of transport, for example.

Procedure

1. In SAP NetWeaver Business Client, choose Application Administration Planning General SettingsIncompatibility Settings Create Incompatibility Settings .

2. In the General Data screen area, enter the following data:

76



Table 134


Incompatibility Incompatibility DOT-INCOMP-SET-001

Description Description of the incompatibility Customer Carrier Incompatibility

Incompatibility Area Applicable TM area Carrier Selection

Default Incompatibility Settings Default Incompatibility Settings Not selected

3. In the Incompatibility Selection table, choose Insert and enter the following data:

Table 135


Incompatibility Incompatibility DOT-INCOMP-CARRIER-CUSTOMER

Violation in Manual Planning Violation in Manual Planning According to Incompatibility Definition

Violation in Automatic Planning Violation in Automatic Planning According to Incompatibility Definition


5.3 Defining Freight Unit Types

Procedure

1. In Customizing for SAP TM, choose Transportation Management Planning Freight Unit Define Freight Unit Types .

2. Select an existing freight unit type and copy it to your own value – DOT3 .


Table 136

Freight Unit Types

Freight Unit Type DOT3

Description DOT: Freight Unit Type

Basic Settings

Freight Unit Can Be Deleted Selected

Number Range Settings

Time for Drawing Draw Numbers When Saving Documents

Number Range Interval 04 (Note: should be defined earlier)

Change Controller Settings

Default Change Strategy DEF_CHACO




Freight Unit Types

Change Strategy Determination Condition Blank

Quantity Tolerance Condition Blank

Date Tolerance Condition Blank

Additional Strategies

Creation Strategy Blank

Save Strategy Blank

Deletion Strategy Blank

Execution Settings

Execution Track Relevance Execution Tracking

Immediate Processing Deselect

Event Management Settings

Application Object Type ODT20_FU

Last Exp. Event POD

Direct Shipment Options

Direct Shipment Option Type No Determination of Direct Shipment Options

Carrier Selection Settings Blank

Carrier Selection Condition Blank

Direct Shipment Strategy Blank

Freight Order Determination

Freight Order Type DOT4

Freight Order Type Condition …

Default MTr Definition

Default MTr for Type Blank

Condition for Default MTr Blank

Default Units of Measure

Weight US pound

Volume Cubic Foot

Additional Settings

Dangerous Goods Profile Blank

78



Freight Unit Types

Rule for PU/DLV Window Pick-up and Delivery as Defined in the Forwarding Order, Forwarding Quotation, Order-Based, or Delivery-Based Transportation Request

Condition for PU/DLV Window Determ . Blank

BW Relevance Deselect

Track Changes Deselect

Archiving Retention Period in Days Blank

Web Dynpro Application Conf . Blank

Organizational Unit Determination

Purchasing Organization DOT-PORG-1

Purchasing Group DOT-PGRP-1

Determination Rules

Consider Organization of User Deselect

Condition Blank

4. Press ENTER .


5.4 Defining Freight Unit Building Rules

The freight unit building rule (FUBR) is used and assigned on the OTR type. This defines how the freight units are built while creating an OTR.

Procedure

1. In SAP NetWeaver Business Client, choose Application Administration Planning General SettingsFreight Unit Building Rule Create Freight Unit Building Rule .

2. On the New Freight Unit Building Rule screen, enter the following values on the General Data tab page:

Table 137


Freight Unit Building Rule Identification of the FUBR DOT-FUBR-Standard

Description Description of this FUBR DOT FUB – Standard

Document Type Freight unit type to be used for the freight unit

DOT3

Incompatibility Setting Not used Blank





Freight Unit Building Strategy This strategy defines how to consolidate

Consolidate per Request (Compatible parts)

Critical Quantity Defines the weight/volume limits for the freight unit

Gross Weight

Item Split Allowed Indicator that specifies whether item quantities can be split across different freight units

Select

3. Choose the Advanced Settings tab page and enter the following data:

Table 138


Process Controller Strategy Strategy that defines how to build FUs FUB_AUTO

4. In the Planning Quantities table, enter the following data:

Table 139


Planning Quantity for Freight Unit Building

Defines the parameter for the planning quantity

Gross Weight

Unit of Measure of Split Quantity Unit of measure LB

Split Quantity Quantity limit for the item based on which freight units are built

35,000

Rounding Quantity Any rounding quantity applied 1


5.5 Creating Delivery Profiles

Procedure

1. In SAP NetWeaver Business Client, choose Application Administration Planning General SettingsDelivery Profile Create Delivery Profile .

2. On the New Delivery Profile screen, enter the following values:

Table 140


General Data

Delivery Profile DOT-DEL-PRFL-STANDARD

Description DOT: Std. Delivery Planning

Control

80




Fix Planning Results Deselect

Delivery Creation Per OTR Item

Incompatibility Settings …


5.6 Creating Selection Profiles

Procedure

1. In SAP NetWeaver Business Client, choose Application Administration Planning Selection ProfilesCreate Selection Profile .

2. On the New Selection Profile screen, choose the Selection Profile tab page and enter the following values:

Table 141


Selection Profile DOT-GEN-SEL-01

Description DOT: Selection Profile

Maximum Number of Selected Objects 100 (depends on testing)

3. Choose New beside the Geographical Sel. Attributes field.

4. Enter the following information in the dialog box:

○ Profile Name : DOT-GEO-SEL-01○ Description : DOT: Geographical Sel. Attr.

5. Choose the Geographical Selection Attributes tab and select the Both Locations checkbox.

6. On the Source Locations tab page, enter the following data:

Table 142


Sign Inclusive

Option Pattern

Lower Value *3100*

Upper Value Blank

7. On the Destination Locations tab page, enter the following data:

Table 143


Sign Inclusive

Option Pattern





Lower Value *DOT*

Upper Value …


NoteThe Additional Selection Attributes tab page is not used in this scenario.

5.7 Defining Capacity Settings

You use this procedure to define the resource capacity used during optimization.

Procedure

1. In SAP NetWeaver Business Client, choose Application Administration Planning Planning Profile Settings Capacity Selection Settings Create Capacity Selection Settings .

2. In the General Data screen area, enter the following values:

Table 144

Field Value

Capacity Selection Settings DOT-CAP-SEL-01

Description DOT: Capacity Selection Settings

3. On the Vehicle Resources tab page, enter the following values:

Table 145


Attributes for Vehicle Resource Selection MTRTCO062_I

Sign Inclusive

Option Pattern

Lower Limit DOT*

Upper Limit Blank


82



5.8 Defining Optimizer Settings

Procedure

1. In SAP NetWeaver Business Client, choose Application Administration Planning Planning Profile Settings Optimizer Settings Create Optimizer Settings .

2. On the Change or Create Optimizer Settings view, enter the following values:

Table 146


General Data

Optimizer Settings Self-defined name for optimizer DOT-OPT-SET-01

Description Description DOT: Optimizer Settings

Planning Strategy Planning strategy VSR_1STEP

FO Building Rule FO building rule New FO When Resource Is Empty

Transportation Proposal Settings

Accept Transp. Prop. Accept transport property Save Route and Freight Documents

Planning Strategy for Transp. Prop. Planning Strategy for transport property

VSR_DEF

Max. Number of Trans Proposals Maximum Number of transport proposals

6

Optimizer Performance Settings

Max. No. of Parallel Processes Maximum no. of parallel processes 1

Maximum No. of Transshipment Loc. Maximum no. of transshipment locations

2

Max. Runtime (Seconds) VSR optimizer runtime (seconds) 30

Max. Time w/o Improvement Maximum time without improvement 5

Consider Constraints

Consider Capacities During Optimization

… Consider Capacities During Optimization





5.9 Defining Freight Settlement Document Types

Procedure

1. In Customizing for SAP TM, choose Transportation Management Settlement Freight SettlementDefine Freight Settlement Document Types .



Table 147

Field Value

FSD Type DOT6

Description DOT: Carrier Settlement Document

FSD Category Freight Settlement Document

Track Changes Selected

Bus. Warehouse Selected

Cost Distribution Selected

No. Range Interval 01

Output Profile /SCMTMS/TOR_INV_PREP

Add. Output Profile /SCMTMS/SFIR_PRINT

Dynamic Determination of Output Profile Deselect


5.10 Creating Carrier Selection Settings

You use this procedure to create the carrier selection settings, which direct the carrier selection optimizer to make the proper rules-based decision.

Procedure

1. In SAP NetWeaver Business Client, choose Application Administration Planning Planning Profile Settings Carrier Selection Settings Create Carrier Selection Settings .

2. Create a requirements profile with the following values:

Table 148

General Data User Action and Values

Carrier Selection Settings DOT-CAR-SEL-01

Description DOT: Carrier Selection Setting

84




Check Incompatibilities Select

Incompatibility Settings DOT-INCOMP-SET-001

Type of Carrier Selection Settings General Carrier Selection

Other Settings

Trsp. Alloc. Usage Do Not Use Transportation Allocations

BS Usage Do Not Use Business Shares

Strategy Costs

Carrier Cost Origin Use Transportation Charges from TCM

Advanced Settings

Planning Strategy TSPS_DEF

Optimizer Runtime 10

Consider Manual Assignment as Fixed …

Action for Manual Rankings Keep

Overall Carrier Availability …

Transportation Charge Interpretation Do Not Accept Carriers with Charges of Zero

Common Currency USD

Action After Carrier Selection Run Automatic Tendering

Continuous Move Type Do Not Create Continuous Move

CM Cost Recalculation for TCM No Recalculation

Use Tendered Objects for Optimization Select

Allows orders, which are already in tendering to be canceled and considered in any subsequent optimization run

Tender Without Optimizer Result …

Tendering Manager User ID

Tendering Profile Blank


5.11 Creating Planning Costs Settings

The planning costs settings help to direct the optimizer’s decisions about penalty and transit costs.




Procedure

1. In SAP NetWeaver Business Client, choose Application Administration Planning Planning Profile Settings Planning Costs Settings Create Planning Costs Settings .

2. Create a requirements profile with the following values:

Table 149


Planning Cost Settings DOT-PLAN-COST-SET-01

Description DOT: Planning Costs Settings

Direct Shipment Options

Currency for Direct Shipment Options USD

Freight Unit Costs

Earliness/Delay Cost Basis Earliness/Delay Costs Defined in Planning Costs

Costs for Non-Delivery 999,999,999.000000000000

Costs for Earliness per Day 1.00000000000

Costs for Lateness per Day 1.00000000000

Means-of-Transport Costs

Means of Transport DOT_FTL

Calculation Basis for Costs per Distance: Planning Costs Do Not Take into Account Costs per Distance

Calculation Basis for Costs per Distance: Lane Take into Account Costs per Distance and Distance Unit from Lane

Fixed Means-of Transport Specific Costs 100

Repeat for each MTr …

Means of Transport DOT_LTL

Calculation Basis for Costs per Distance: Planning Costs Do not take into Account Costs per Distance

Calculation Basis for Costs per Distance: Lane Do not take into Account Costs per Distance

Fixed Means-of Transport Specific Costs 0

(Means-of-Transport Specific) Cost per Distance Unit 0.000Taken from lane based on setting above

Unit of Measure …

(Means-of-Transport Specific) Maximum Distance 0.000Taken from lane based on setting above

3. Select the Means-of-Transport line and enter the following values on the Means-of-Transport Cost Details tab page:

86



Table 150

Means-of-Transport Cost Details User Action and Values

General Data DOT_FTLDefaults

Distance Costs Defaults

Quantity Costs

Costs Basis for Quantity Transportation Lane: Distance Independent

Costs per Quantity Grayed out – not changeable

Unit of Measure Grayed out – not changeable

Penalty Costs

Premature Pick-Up 1.000

Delayed Pick-Up 1.000

Premature Delivery 1.000

Delayed Delivery 1.000

Duration Costs Defaults

Additional Stops

Costs per Additional Intermed. Stop 150.0000000000000

Maximum Number of Stops 4.000000000000000

Means-of-Transport Cost Details

General Data DOT_LTLDefaults

Distance Costs Defaults

Quantity Costs

Costs Basis for Quantity Transportation Lane: Distance Independent

Costs per Quantity Grayed out – not changeable

Unit of Measure Grayed out – not changeable

Penalty Costs

Premature Pick-Up 1.000

Delayed Pick-Up 1.000

Premature Delivery 1.000

Delayed Delivery 1.000

Duration Costs Defaults

Additional Stops




Means-of-Transport Cost Details User Action and Values

Costs per Additional Intermed. Stop 0.000000000000000Not applicable for LTL

Maximum Number of Stops 0.0000000000000000Not applicable for LTL


5.12 Creating Planning Profiles

In this procedure, you create a planning profile to determine how freight units are selected based on geography, pick-up dates, and delivery dates.

Procedure

1. In SAP NetWeaver Business Client, choose Application Administration Planning Planning ProfilesCreate Planning Profile .

2. On the New Planning Profile screen, enter the following data in the General Data screen area of the Planning Profile tab page:

Table 151

Field Value

Planning Profile DOT-PLAN-PROF-01

Description DOT: Planning Profile

3. In the Business Document Type screen area, set the type determination rule to Defined per Category in Planning Profile .

The screen changes to display a number of additional fields.

4. Choose any entry as the default type for the road freight order.

NoteOnce you have created the freight order type for the road freight order used in this scenario, you must change this entry to the correct freight order type. For more information, see Defining Freight Order Types [page 91] .

5. In the Planning Horizon screen area, enter the following data:

Table 152

Field Value

Duration in Days 180

Additional Duration (hh:mm) Blank

Offset in Days Blank

88



Field Value

Additional Offset (hh:mm) Blank

Factory Cal. for Offs./Dur. Calc. Blank

Round Horizon to Full Days Select

Time Zone for Rounding the Horizon CST

6. In the Profile Assignments screen area, enter the following data:

Table 153

Field Value

Selection Profile for Freight Orders Blank

Selection Profile for Freight Bookings Blank

Capacity Selection Settings DOT-CAP-SEL-01

Optimizer Settings DOT-OPT-SET-01

Planning Costs Settings DOT-PLAN-COST-SET-01

Incompatibility Settings Blank

Carrier Selection Settings DOT-CAR-SEL-01

7. In the Manual Planning screen area, enter the following data:

Table 154

Field Value

Manual Planning Strategy VSRI_DEF

Consider Fixing Status Warning When Changing Fixed Documents

8. In the Scheduling area, enter the following data:

Table 155

Field Value

Scheduling Strategy VSS_DEF

Consider Freight Unit Dates Consider Freight Unit Dates

Scheduling Direction Backward

9. In the Check screen area, enter the following data:

Table 156

Field Value

Check Strategy VSR_CHECK

Take Capacities into Account Warning

10. In the Loading and Unloading Duration screen area, enter the following data:




Table 157

Field Value

Service Time Definition Freight Unit and MTr Independent

Loading/Unloading Duration 00:30:00


5.13 Creating Page Layouts for Transportation Cockpit

Procedure

In this procedure you create page layouts for the transportation cockpit.

Gantt Chart

1. In SAP NetWeaver Business Client, choose Application Administration Planning General Settings Page Layouts Page Layouts for Transportation Cockpit .

2. Select the Standard Layout and choose the Copy pushbutton.

3. In the General Data section, enter Gantt Chart as the name of your page layout.

4. Set the position of the screen area to Not Visible for the following screen areas:

○ Requirements area

○ Orders area

○ Order details area

○ Resources area

5. For the Gantt chart area, make the following settings:

Table 158

Field Value

Position of Screen Area Top Left

Width 100%

Layout SAP_TRK_BASIC


DOT Standard

1. Select the Standard Layout and choose the Copy pushbutton.

2. In the General Data section, enter DOT Standard as the name of your page layout.

3. In the Visibility Pushbutton section, select the following checkboxes:

○ Update Map - all

○ Update Map - Selected Entries with All Resources

○ Update Map - Selected Entries Only

4. For the order details area, activate the display of the map by selecting the Display checkbox for the Map Display .


90



6 Freight Orders

Activities

Defining Freight Order Types [page 91]

6.1 Defining Freight Order Types

Procedure

1. In Customizing for SAP Transportation Management, choose Transportation Management Freight Order Management Freight Order Define Freight Order Types or call transaction /SCMTMS/C_FOR .

2. On the Freight Order Types: Overview screen, choose the New Entries pushbutton.

3. On the New Entries: Details of Added Entries screen, enter the following data in the header area:

Table 159


Freight Order Type Unique 4-character ID of the freight order type that you want to define

DOT4

Description Description of the freight order type that you want to define

DOT: Freight Order

4. In the Basic Settings screen area, enter the following data:

Table 160


Freight Order Can Be Subcontracted Specifies whether the freight order type can use subcontracting processes

01 Relevant for Subcontracting

Shipper/Consignee Determination Defines how the shipper and consignee are identified for this freight unit type

P Determination Based on Predecessor Documents

Fix Document When Saving None Not selected

Freight Order Can Be Deleted Specifies whether the freight order with this type can be deleted

Select

5. In the Execution Settings screen area, enter the following data:

Configuration Guide for Domestic Outbound TransportationFreight Orders



Table 161


Execution Track. Relevant Controls document tracking.

If you want to track certain types of documents, choose 2 (execution tracking) or 3 (execution tracking with external event management). The system then sets the initial document execution status to Not Started .

If you do not want to track documents, choose 1 (no execution tracking). The system then sets the initial document execution status to Not Relevant .

3 Execution Tracking with External Event Management

Check Condition “Ready for Exec.” Not used. Blank

Immediate Processing Determines whether the status In Process is set as soon as the document is created and saved.

Select

Propagate Execution Info Indicates whether an event that is reported at the document level for the freight order is to be propagated to the predecessor documents.

Not selected

Application Object Type of application object to be tracked in the application system (necessary for determining event management-relevance for an application object). The event manager processes only event messages for these objects.

ODT20_TO

Last Exp. Event Last expected event for a document POD

6. In the Tendering Settings screen area, enter the following data:

Table 162


Use Default Settings Specifies whether default settings are to be used

Not selected

Use Condition for Sett. Determ. Use condition for settlement determination

Not selected

Use Type-Specific Settings Enables you to further define the process settings and communication settings specific to this freight order type.

Select

Process Setting Controls the tendering process settings

DOT_PROCESS_AUTONote that this setting will be created later in this scenario. Select any other

92




setting and change the value once the process setting has been defined.

Communication Setting Specifies the strategy for tendering communication.

DOT_COMM_AUTONote that this setting will be created later in this scenario. Select any other setting and change the value once the communication setting has been defined.

7. In the Additional Settings screen area, enter the following data:

Table 163

Field Value

Dangerous Goods Profile Blank

Customs Profile Blank

Default FSD Type DOT6

Deflt Carrier Selection Settings DOT-CAR-SEL-01

8. In the Number Range Settings screen area, enter the following data:

Table 164


Time for Drawing Specifies when a number is assigned to the freight order

S Draw Number When Saving Document

Number Range Interval Number range that is to be used for this document type

01

9. In the Default Units of Measure screen area, enter the weight as LB US Pound and the volume as FT3 Cubic Foot .

10. In the Additional Strategies screen area, enter creation strategy CARR_SEL .

11. In the Change Controller Settings screen area, enter the following data:

Table 165


Default Change Strategy Specifies the default strategy that is used for tendering if any changes are made to the key fields in the freight order (for example, partners and quantities)

DEF_CHACO

Change Strategy Det. Cond. Specifies the condition that the system is to use to determine a change controller strategy at runtime.

If you have defined several change controller strategies, you can use a

Blank





condition to determine the correct strategy.

The condition type of this condition is /SCMTMS/CC_TOR_STRAT .

Quantity Tolerance Cond. Specifies the tolerances when a quantity is changed in the freight order.

DOT_QTOL_01

Date Tolerance Condition Specifies the tolerances when a date is changed in the freight order.

Blank

12. In the Default MTr Determination screen area, enter the following data:

Table 166

Field Value

Default MTr for Type Blank

Condition for Def MTr Blank

Transportation Mode 01

13. In the Output Options screen area, enter the following data:

Table 167

Field Value

Output Profile /SCMTMS/TOR_PRINT_ROAD

Add. Output Profile Blank

Text Schema Blank

Dynamic Determination of Output Not selected

14. In the Organizational Unit Determination screen area, enter the following information:

Table 168


Execution Organization ID of the organizational unit that is defined:

● As unit function 13 – Planning and Execution

● As unit role 1 – Organization

<Organizational unit number for DOT-PEORG-1>

Purchasing Organization ID of the organizational unit that is defined:

● As unit function 2 – Purchasing

● As unit role 1 – Organization

<Organizational unit number for DOT-PORG-1>

Execution Group ID of the organizational unit that is defined:

● As unit function 13 – Planning and Execution

<Organizational unit number for DOT-PEGRP-1>

94




● As unit role 3 – Group

Purchasing Group ID of the organizational unit that is defined:

● As unit function 2 – Purchasing

● As unit role 3 – Group

<Organizational unit number for DOT-PGRP-1>

Consider Organization Unit of User ID of the organizational unit that is defined

Not selected

Condition ID of the organizational unit that is defined

Blank


More Information

Once you have defined the freight order type, you must enter it in the planning profile. For more information, see Creating Planning Profiles [page 88] .




7 Tendering

Activities

● Defining General Settings for Tendering [page 96]

● Defining Tendering Profile [page 99]

7.1 Defining General Settings for Tendering

Configuration setting is a multiple-step process. Select each folder, as explained below, and configure the settings for each folder.

Procedure

1. In Customizing for SAP TM, choose Transportation Management Freight Order ManagementTendering Define General Settings for Tendering .

2. Select folder 01 – Visibility Settings and create new entries as follows:

Table 169


Freight Order Types … …

Visibility Setting Unique name for the tendering visibility setting profile.

DOT_VIS_AUTO

Settings Description Description of this setting profile. DOT: Automatic Tendering

Visibility Stop Dates Whether the stop dates are visible to the carrier when you send the RFQ to the carrier.

Select Read Only when you want

the carrier to see the dates.

Price Limit Whether the price limit that you have set for this tender is visible to the carrier or not.

Select Hidden when the carriers

would not need to see this information.

Visibility of Submitted Price Whether the price for this tender is visible to the carrier – and if the carrier can make changes to the offer.

Hidden


4. Select folder 02 – Rejection Reason Codes and create new entries as follows:

96


Configuration Guide for Domestic Outbound TransportationTendering

Table 170


Reason A list from which a carrier can choose a value to reject the RFQ.

None - No reason defined

NO_CAP - No capacity available

NO_TIME - Not enough time

Description Reason descriptions See above


6. For folder 03: E-Mail and SMS Content , the pre-delivered settings are used for this scenario.

7. Select folder 04 – Process Settings and create new entries as follows:

Table 171


Process Settings Name of the process setting profile being created

DOT_PROCESS_AUTO

Tendering Manager Name of the user User Name

Visibility Settings Visibility settings for the RFQ DOT_VIS_AUTOThis was created in folder 1 above.

Tendering Profile This is the tendering profile that is defined in a separate step – this controls the behavior for the next steps.

DOT-TEND-PROF-P2P

Carrier Selection Settings This is the carrier selection profile that defines carrier selection strategy. This is defined in a separate step.

DOT-CAR-SEL-01

Maximum Response Time in Hours This defines the maximum time that a carrier is allowed once the RFQ is sent to the carrier and the carrier either accepts or rejects the RFQ.

2 hours

Consider Business Partner Calling Hours

This flag indicates when the maximum time for response is calculated – also consider the carrier’s business hours and adjust the window for response accordingly.

Select

Review Threshold (%) If the carrier is allowed to change the price on the RFQ, this value defines the tolerance. This tolerance defines up to what percentage the price change is acceptable. If the price submitted by carrier is above the tolerance defined here, the FOR will be flagged for review.

Blank





Restart Tendering This flag indicates what is the next step if a RFQ is rejected by a carrier.If this flag is selected, the tendering is restarted.

Select


9. Select folder 05 – Communication Settings and create new entries as follows:

Table 172


Communication Settings Name of the communication setting profile being created

DOT_COMM_AUTO

Trigger Alerts w/o Subscription to Alert Category

Send alerts to tendering managers without subscription. Determines whether tendering managers receive alerts only for the subscribed categories or all alerts.

Select

Send EDI Messages Create EDI messages for the alerts Deselect

Send RFQ … Select

Send Notification E-mail for Canceled Tender

This flag determines if the notification is to be sent to the tendering manager for a canceled tender.

Deselect

Send Notification E-mail for Sent RFQ This flag determines if the notification is to be sent to the tendering manager for a RFQ sent out to the carriers.

Deselect

Send Notification E-mail for Awarded Quotation

This flag determines if the notification is to be sent to the tendering manager for a RFQ that is accepted by the carrier.

Deselect

Send Notification E-mail for Rejected Quotation

This flag determines if the notification is to be sent to the tendering manager for a RFQ that is rejected by the carriers.

Deselect


11. Select folder 06 – Carrier Specific Communication Settings and create new entries as follows:

Table 173


Carrier Carrier number for whom specific communication settings are being created

DOT-VN-01 (refer to master data for

US Carriers. Each should be the same.)

Create EDI Messages Enable EDI messages Select

98




E-Mail

E-mail for Canceled Tendering … Select

E-mail for Sent RFQs … …

E-mail for Awarded RFQ Quotation … …

E-mail for Rejected Freight RFQs … …

Create Freight RFQ for Each E-mail

SMS for Canceled Tendering … …

SMS for Sent Freight RFQs … …

SMS for Awarded Freight RFQs … …

Send Notification for Rejected Quotation

… …

Freight RFQ for Each SMS … …


7.2 Defining Tendering Profile

Procedure

1. In SAP NetWeaver Business Client, choose Application Administration Tendering Tendering ProfilesCreate Tendering Profile .

2. On the New Tendering Profile screen, enter the following values:

Table 174

Field Value

Tendering Profile DOT-TEND-PROF-P2P

Description DOT: Tendering Profile

3. Choose the Insert Step pushbutton and enter the following data in the row for step 1:

Table 175

Field Value

Tendering Type Peer-to-Peer Tendering – Response Required

Tendering Process Direct Tendering, Send Freight Order Directly

Carrier Assignment Method Get Carriers from Ranking List

Relative Price Limit 100%

Maximum Response Duration :05(5 minutes)




Field Value

Carrier-Specific Freight Agreement Select

Visibility Settings DOT_VIS_AUTO


100



8 Charge Management

The charge elements used in this scenario are:

● Line-haul charge

This is point-to-point (location-to-location) based.

● Fuel surcharge

This is based on distance (per mile rate – based on an index).

● Detention charge

This is a manual charge – flat rate.

Activities

● Defining Product Group Codes [page 101]

● Defining Source Location Scales [page 102]

● Defining Destination Region Scales [page 103]

● Defining Destination Zone Scales [page 104]

● Defining Less-than-Truckload Break-Weight Scales [page 105]

● Defining Product Group Scales [page 106]

● Defining Stop-Off Scales [page 107]

● Defining Carrier Rates [page 108]

● Defining Fuel Surcharges [page 113]

● Defining Stop-Off Rates [page 115]

● Defining Calculation Sheets [page 117]

● Defining Freight Agreement Types [page 120]

● Defining Freight Agreements [page 121]

● Defining Settlement Profile [page 122]

● Defining Calculation Profile [page 123]

● Defining Cost Distribution Profiles [page 124]

● Defining General Settings for Charge Calculation [page 124]

● Defining Cost Distribution Methods [page 125]

8.1 Defining Product Group Codes

Procedure

1. In Customizing for SAP TM, choose SAP Transportation Management SCM Basis Master DataTransportation Lane Transportation Service Provider Profile Define Product Freight Groups

Configuration Guide for Domestic Outbound TransportationCharge Management




Table 176


PrdFrtGp … 70 , 77.5 , 100 , 125

Description Description of product freight group NMFC freight class 70

Tr. Grp … 0001 (on pallets)

Ensure that the Transportation Group – 0001 On Pallets is defined in the . SAP TM Customizing configuration: SAP Transportation Management SCM Basis Master Data Product Maintain transportation groups .


8.2 Defining Source Location Scales

Rates are based on source and destination. The source location in this scenario is the shipping point.

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Charge Management and Service Product Catalogs Scales Create Scale .

2. On the Create Scale screen, create scales without a template as follows:

Table 177


General Data

Scale Scale identifier DOT-SCALE-ORIGIN_LOC

Description Description of the scale Source Location

Scale Base This defines the basis of the scale, such as location, distance, or duration.

LOCLocation because this identifies locations (source location).

Scale Type This field defines how the scales need to be maintained.

Same Scale (=)

This value is set automatically. Since the location is non-numeric, the system assumes that the scale type is same scale .

Unit of Measure This defines the unit of measure for the scale base. For example, if the scale base is distance, the unit or measure could be kilometers or miles.

Even though the field is indicated as a required field (with an asterisk), in this scenario with LOC as the scale base, the unit of measure can be left blank.

102




Rounding Profile Rule to round up or down Blank

Items

Calculation Type Defines how the values of the scales are read.

Absolute , which means read the

values directly.

Internal Location Location code SP3100@ERP001 (shipping point

mapped to 3100)


8.3 Defining Destination Region Scales

Truckload rates are represented by origin to state rates. In SAP, region and state are equivalent. In this step, we create the scale to represent the states in the scenario. In this test scenario there are two different scales for charge calculation. Carrier 01 and 02 are region-based. Therefore a destination region scale has to be created. Carrier 03 and 04 are zip-code-based. This is defined through a destination zone scale.

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Charge Management Scales Create Scale .

2. Create the destination region scale as follows:

Table 178


General Data

Scale Scale identifier DOT-SCALE-DEST_REGIO

Description Description of the scale Region-Based Scale


REGION to identify regions


Same Scale (=)

Unit of Measure This defines the unit of measure for the scale base. For example, if the scale base is distance, the unit of measure could be kilometers or miles.

Even though the field is indicated as a required field (with an asterisk), in this scenario with LOC as scale base the unit can be left blank.


Items

Calculation Type Defines how the values of the scales are read


values directly.





Region Destination region IN , UT , ND , CA , KY


NoteYou can add further rows to define more region values, but remember to also add the respective rates.

8.4 Defining Destination Zone Scales

New scales are defined for the LTL scenario, based on zones. The following zones have been defined for this scenario:

● ZN_606: For postal code 60654 – for the Chicago plant/shipping point

● DOT-ZIP-303: For postal code range 30300 - 40199

● ZN_477: For postal code range 47000 – 59999




Procedure


2. On the Create Scales screen, create the following scales:

Table 179


General Data

Scale Scale ID DOT-SCALE-DEST_ZONE

Description Description of the scale 3 digit zones

Scale Base This defines the basis of scale – such as: location, distance, duration, and so on.

TRZONE – Transportation zone


Same Scale (=)

Unit of Measure This defines the unit of measure for the base above. For example, if the base is distance, the unit could be KM, or MI.

Even though the field is indicated as a required field with an asterisk, in this scenario with LOC as base, the unit can be left blank.

Rounding Profile Rule to round-up or down Blank

104




Items


Absolute – means read the values

directly

Transportation zone Transportation zones used in this scenario

DOT-ZIP-303DOT-ZIP-477DOT-ZIP-410DOT-ZIP-402DOT-ZIP-606DOT-ZIP-701


NoteYou can add further rows to define more zone values. Remember to add the respective rate values.

8.5 Defining Less-than-Truckload Break-Weight Scales

Less-than-truckload (LTL) rates are based on break-weights (that is, scales). These must be defined in SAP directly. Standard business practice would represent these break-weights in terms of CWT (hundredweight). This is entirely possible by creating the unit of measure for CWT. However, in this configuration, the following pound break-weights are created:

● 0

● 500

● 1000

● 2000

● 5000

● 10000

● 20000

Procedure


2. On the Create Scale screen, create the following scales:

Table 180


General Data

Scale Scale identifier DOT-SCALE-LTL_WT_BRK





Description Description of the scale LTL break-weight scale

Scale Base This defines the basis of scale, such as location, distance, or duration.

WEIGHT – weight


Base Scale (>=)

Unit of Measure This defines the unit of measure for the scale base. For example, if the scale base is distance, the unit of measure could be kilometers or miles.

LB


Items


Relative

Weight Break-weight scales 0.15001000200050001000020000


8.6 Defining Product Group Scales

SAP represents Product Class using the Product Group in the Material Master. This value is configured as part of Material Master in ERP. There are many Product Classes, but there are only a few materials in this scenario. Create four Product Classes (groups):

● 70

● 70.5

● 100

● 125

Procedure


2. In the Create Scale screen, create the following scale:

106



Table 181


General Data

Scale Scale identifier DOT-SCALE-PRD_GRP

Description Description of the scale PRO Grp Class Scale


PRDGRP – Product Group


Same Scale (=)

Items



values directly.

Charge-Relevant Product Freight Group

This represents the product class used to calculate LTL charges.

7077.5100125


8.7 Defining Stop-Off Scales

Stop-off charges could be flat rates per stop, but also they could increase for each stop. This scenario uses a scale to represent the increase in costs for each additional stop. This would not be required if you wanted to have a flat charge per stop. A flat charge per stop could be represented directly in the TCCS.

Procedure


2. In the Create Scale screen, create the following scale:

Table 182


General Data

Scale Scale identifier DOT-SCALE-STOPOFF

Description Description of the scale Stop-off scale


Number






Base Scale (>=)


Items



values directly.

Scale Value Qty Number of stops 1 – 0.002 – 50.003 – 75.004 – 100.005 – 125.006 – 150.00


8.8 Defining Carrier Rates

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Charge Management Rate Tables Create Rate Table Definition .

2. A different rate table is required for FTL carriers. On the Create Rate Table screen, create an entry with the following values (choose Add Rate once you have maintained the parameters and skip using a rate template):

Table 183


General Data

Rate Table Unique identifier for the rate table DOT-RATE-CR-01DOT-RATE-CR-02

Description Description of the table Rate Table for DOT-CR-01Rate Table for DOT-CR-02

Charge Usage This indicator identifies in which scenario this rate table could be used. This could be used for customer billing integration and/or supplier invoice integration, or none.

Service Provider

Charge Type This is where the charge type is linked for integration with SAP ERP.

FB00 – Basic Freight

108




Charge Category This defaults from the charge type definition above.

004 – Basic Freight

Charge Subcategory This defaults from the charge type definition above.

100000 – Freight Charges

Positive/Negative: This defaults from the charge type definition above.

Positive Value

Value This defaults from the charge type definition above.

Absolute Value

Scales

Scale Base On the rate table – this defines a row (x-axis) or a column (y-axis). You can have multiple scales (up to 9) in a rate table.

1 for the first scale (Location-based)

2 for the second scale (Region-based)

Reference Scale Assign the scales here for carrier 1 and 2, which were defined above. This enables the entries in the rate table according to the sequence.

1: DOT-SCALE-ORIGIN_LOC2: DOT-SCALE-DEST_REGIO

Calculation Base This determines how the values are stored and determined for this dimension. There are predefined sources of information based on the object.

1: SOURCELOC

2: DESTLOC_REG

Choose Add Scale in the table for each value.

Minimum Value … Deselect

Maximum Value … Deselect

Rel. Calc. Method … Deselect

Rounding Profile … Blank

Dates and Values

Valid-From Date The valid-from date for the rate table. 01.01.2010

Valid-To Date The valid-to date for the rate table. 31.12.2099

Currency A currency that is applicable for this rate table.

USD

Values in Table When the Dates row is entered, rate combinations are created in the screen area below. You need to highlight the row of Valid-From Date to be able to enter the values.

Fill in values from the tables below.

Calculation Rules

Calculation Base This provides the calculation base to this rate. In the rate table, the rates

ACTUAL_DIST





are per mile from source to destination locations. however, the basis needs to be determined to apply these rates – which is the distance.

There are various bases like business partner role, weight, or destination location.

Scale Type Not relevant 1: Same Scale

2: Same Scale

Price Unit This describes the multiplier when the base is found. The rate could be applied per 1 mile or per 100 miles. This column identifies the factor.

1

UoM This is the unit of measure, to which the multiplier is to be applied.

MI – Miles

Rounding Profile Rounding to a full mile 0005

Application Level of Calculation Rule Not relevant Rate Table

Table 184: Rate Values for Carrier 01

Destination Location Region Source Location Value

CA SP3100@ERP001 1.40

GA SP3100@ERP001 1.30

IN SP3100@ERP001 1.80

KY SP3100@ERP001 1.60

LA SP3100@ERP001 1.20

ND SP3100@ERP001 1.30

TX SP3100@ERP001 1.90

UT SP3100@ERP001 1.50

Table 185: Rate Values for Carrier 02

Destination Location Region Source Location Value

CA SP3100@ERP001 1.45

IN SP3100@ERP001 1.75

KY SP3100@ERP001 1.65

ND SP3100@ERP001 1.25

UT SP3100@ERP001 1.45


4. On the Dates and Values tab page, choose the Release pushbutton to release the rate table for use.

110



5. For LTL carriers a different rate table is required. For this, use the following values:

Table 186


General Data

Rate Table Unique identifier for the rate table DOT-RATE-CR-03DOT-RATE-CR-04

Description Description of the table Rate Table for DOT-CR-03Rate Table for DOT-CR-04


Service Provider

Charge Type This where the charge type is linked for integration with SAP ERP.

FB00 – Base Freight

Charge Category This defaults from the charge type definition above.

004 – Base Freight

Charge Subcategory This defaults from the charge type definition above.

100000 – Freight Charges

Positive/Negative : This defaults from the charge type definition above.

Positive Value


Absolute Value

Scales

Dimension On the rate table, this defines a row (x-axis) or a column (y-axis). You can have multiple scales (up to 9) in a rate table.

1 for the first scale (Location based)

2 for the second scale (Zone based)

Reference Scale Assign the scales here for carrier 3 and 4, which are defined above. This w enables the entries in the rate table as per the sequence.

1: DOT-SCALE-ORIGIN_LOC2: DOT-SCALE-DEST_ZONE3: DOT-SCALE-PRD_GRP4: DOT-SCALE-LTL_WT_BRK


1: SOURCELOC2: DESTLOC_ZONE3: PRD_FREIGHT_GRP4: GROSS_WEIGHT

Scale Type Not relevant 1: Same Scale

2: Same Scale

3: Same Scale





4: Base Scale




(Select only for scale DOT-SCALE-LTL_WT_BRK )


Dates and Values



Currency A currency that is applicable for this rate table.

USD

Calculation Rules

Calculation Base This provides the calculation base to this rate. In the rate table, the rates are per mile from source to destination locations. However, the basis needs to be determined to apply these rates, which is the distance.

There are various bases like business partner role, weight, or destination location.

GROSS_WEIGHT

Price Unit This describes the multiplier when the base is found. The rate could be applied per 1 mile or per 100 miles. This column identifies the factor.

1

UoM This is the unit of measure, to which the multiplier is to be applied to.

LB


7. Choose the Edit pushbutton.

Excel Integration

Integration with Microsoft Excel takes place in two stages. First, the system creates a blank Excel sheet, which has to be downloaded. Second, you enter the rates directly into the Excel sheet or you can copy and paste them from another Excel or Word file. Proceed as follows:

1. Enter the data as shown in the following table:

112



Table 187


File Download This creates an XML file in MS Excel. The Excel file serves as a template to enter or copy rates from other files from Excel or Word, for example.

Select Rates for All Validity Periods (Scale Ranges Not Included) and choose Download and Save the File

XML Template File This template contains fixed dimensions, which need to be complemented with values.

See rate tables in the Appendix [page 138] [Page 114]. Copy values without dimensions in the XML template file for carrier 03 and 04 and save it.

File Upload Not applicable Choose the Browser pushbutton to select the rate table and upload it.

2. Select the date line on the Dates and Values tab page and choose Release to release the rates.


8.9 Defining Fuel Surcharges

Fuel surcharges are based on a percentage of the base freight from origin to region (region and state are equivalent in this scenario). This can be altered by changing the scale defined earlier. Standard fuel surcharge indexes are not covered in this scenario, but can be also used if configured accordingly.

Procedure


2. Add another table with the following values:

Table 188


General Data

Rate Table Unique identifier for the rate table DOT-RATE-FUEL-SRCHRG

Description Description of the table Fuel Surcharge Rates


Service Provider

Charge Type This where the charge type is linked for integration with SAP ERP through charge type in TM-IMG.

FUEL – Fuel Surcharge





Charge item category This defaults from the charge type definition above.

003 – Transportation Charges +

Additional Charges

Charge Item Subcategory This defaults from the charge type definition above.

103008 – Fuel Surcharge


Positive Value

Value Type This defaults from the charge type definition above.

Percentage

Scales

Dimension On the rate table, this defines a row (x-axis) or a column (y-axis). You can have multiple scales (up to 9) in a rate table.

1 for the First Scale

Scale Assign the scales, which have been defined above. This enables the entries in the rate table according to the sequence.

1: DOT-SCALE-DEST_REGIO


DESTLOC_REG

Description Defaults Destination Location

Scale Type Not applicable Same Scale (=)

Basic Data This step completes the information on the Scale tab page and a number appears in the Scale column. The scale is now defined.

Choose the Add Scale pushbutton in the table showing the different scales.

Dates and Values



Aggregated Rate Description Not relevant Blank

Currency Not relevant %

Rounding Profile Not relevant Blank

3. Choose the line just created and enter the following values into the resulting table:

114



Table 189


Destination Location Region Enter each state region on each line. CA , GA , IN , KY , LA , ND , TX , UT ,

WA

Values Enter percentage value for each destination region.

For example, 3 for 3% (not 0.03).

4. Select the date line, and choose Release to release the rates.


8.10 Defining Stop-Off Rates

Procedure


2. On the Create Rate Table screen, create a new entry with the following values:

Table 190


Rate Table Unique identifier for the rate table DOT-RATE-STOPOFF-CHR

Description Description of the table Stop off charges


Service Provider

Charge Type This is where the charge type is linked for integration with SAP ERP through charge type in Customizing for SAP TM.

STOP

Charge item category This defaults from the charge type definition above.

002 – Additional Charges

Charge Item Subcategory This defaults from the charge type definition above.

609102 – Stop in Transit


Positive or Negative Value


Absolute Value

Table

N/A Insert a new line in the table Choose the Insert pushbutton.





Scale Dimension No. On the rate table, this defines a row (x-axis) or a column (y-axis). You can have multiple scales (up to 9) in a rate table.

1 for the first scale

Defaults

Scale Assign the scales, which have been defined above. This enables the entries in the rate table according to the sequence.

DOT-SCALE-STOPOFF


NUMBER_OF_STOPS

Basic Data This completes the information on the Scale tab page and a number appears in the Scale column. The scale is now defined.

Choose the Add Scale pushbutton in the table showing the different scales.

Description Defaults Number of Stops





Scale Base Defaults Number

Scale Base Description Defaults Number

Dates and Values



Aggregated Rate Description … Blank

Life Cycle status … In Process

Currency … USD


3. Choose the line just created and enter the following values into the resulting table:

Table 191


Number of Stops Enter the number of stops in each line. 1 , 2 , 3 , 4 , 5 , 6

Value Enter the percentage cost for each stop.

0 , 50 , 75 , 100 , 125 , 150

116



4. Choose the first line just created. This should contain the value 1 in the Number of Stops column and value 0.00 in the Value column.

5. Select the Dates and Values tab page and choose Release to release the rates.

8.11 Defining Calculation Sheets

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Charge Management Calculation SheetsCreate Calculation Sheet .

2. On the New Calculation Sheet screen, create a new entry with the following values:

Table 192


General Data

Calculation Sheet Unique identifier for the calculation sheet being defined

DOT-TCCS-CR-01DOT-TCCS-CR-02DOT-TCCS-CR-03DOT-TCCS-CR-04

Description Description of the calculation sheet DOT-CR-01: TCCSDOT-CR-02: TCCSDOT-CR-03: TCCSDOT-CR-04: TCCS

Charge Usage Indicates whether this calculation sheet is used for customers, vendors (carriers), both, or none – and used only for making decisions during tendering.

2 – Service Provider

Items Items are created with the Insert Single Item option at the top of the Items area.

Calculation Resolution Base (on the Basic Data tab page)

This base indicates at what level the calculation sheet is executed. For example, this could be executed at the header level for the whole freight order, or it could be executed for a particular stage only.

ROOT : this means the calculation

sheet applies to the whole document.

Item (Overview of Positions) This shows the levels of the charge elements on this calculation sheet, and the descriptions derived from the assigned charge types.

1. Basic Freight ( FB00 )

2. Fuel Surcharge ( FUEL )

3. Stop-off ( STOP )

4. Discount ( DISC )





Description This is a freely definable description. This appears in documents. We recommend that you use descriptions that make sense in other documents.

Free text

Calculation Sheet Line Number This defines the sequence in which the charge types are executed.

…

Instruction Type This field relates each charge type to each other and how the calculations are made for each charge type. You can define if the item represents a sum, or if it is a direct calculation of the charge.

Standard (for all charge types)

Charge Type Defines the charge type that has been defined above for each item.

FB00FUELSTOP (only for DOT-TCCS-CR-01 and

DOT-TCCS-CR-02)

DISC (only for DOT-TCCS-CR-03 and

DOT-TCCS-CR-04)

Currency Applicable currency or percentage for charge items calculated as percentages

USD (Basic Freight and Stop)

% (Fuel and Disc)

3. Select the line item for Basic Freight .

4. Enter the following values in the details screen below:

Table 193


Rate

Rate Table Assigned rate table for each individual carrier

● DOT-RATE-CR-01

● DOT-RATE-CR-02

● DOT-RATE-CR-03

● DOT-RATE-CR-04

Basic Data

Sheet Line Number Line number of the item 20

Instruction Type Rule to indicate how the charge item is applied for calculation

Standard

Description Description of the charge item on calculation sheet

Line-Haul Charge

Charge Type Assigned charge type FB00

Leading Charge Type Not relevant Select

118




Calculation Resolution Base This base indicates at what level the calculation sheet is to be executed. For example, this could be executed at the header level for the whole freight order, or it could be executed for a particular stage only.

Product

Mandatory This indicator makes the charge type mandatory.

No – for all charge types

Calculation Method Type … Standard

5. Select the line item for Fuel Surcharge .

6. Enter the following values on the details screen below:

Table 194


Rate

Rate Table Assigned rate table DOT-RATE-FUEL-SRCHG

Basic Data



Standard


Fuel Surcharge

Charge Type Assigned charge type FUEL

Reference-From Line No. … 20

Calculation Resolution Base Not relevant Product

Calculation Method Type Calculation Method Type Standard

7. Select the line item for Stop-Off Charge (only for carrier 1 and 2).


Table 195


Rate

Rate Table Assigned rate table DOT-RATE-STOPOFF-CHR

Reference-From Line No. … 0

Basic Data


Standard






…

Charge Type Assigned charge type STOP




9. Select the line item for Discount (only for carrier 3 and 4).


Table 196


Rate

Amount Discount 2%

Reference-From Line No . … 20

Basic Data



Standard


…

Charge Type Assigned charge type DISC

Calculation Resolution Base … Product

Calculation Method



12. Repeat the steps above for calculation sheets DOT-TCCS-CR-02 , DOT-TCCS-CR-03 , and DOT-TCCS-CR-04 .

8.12 Defining Freight Agreement Types

Procedure

1. In Customizing for SAP TM, choose Transportation Management Master Data Agreements and Service Products Define Freight Agreement Types .

2. Enter the following values, which apply for all your freight agreements:

120



Table 197


Type DOT5

Short Description DOT Freight Agreement Type

Dflt Type Deselect

TrackChang Deselect

Multiple Parties Deselect

FA No. Range 02

Txt Schema Blank

Calc. Sheet Template Blank


8.13 Defining Freight Agreements

Prerequisites

You have defined freight agreement DOT5 and number range intervals for freight agreements.

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Charge Management Freight AgreementsCreate Freight Agreement .

2. On the New Freight Agreement screen, enter values as follows:

Table 198


Freight Agreement Type Type defined DOT5

Mutual If this freight agreement is applicable to both carriers and customers

Deselect

Agreement Agreement identifier DOT-FA-CR-01Similarly define for other carriers:

DOT-FA-CR-02DOT-FA-CR-03DOT-FA-CR-04

Description Description of the freight agreement DOT-FA-CR-01DOT-FA-CR-02DOT-FA-CR-03





DOT-FA-CR-04

Purchasing Organization Default purchasing organization DOT-PORG-1

Carrier Carrier for whom this agreement is being defined

DOT-CR-01DOT-CR-02DOT-CR-03DOT-CR-04

Valid From Start of validity date range 01-01-2010

Valid To End of validity date range 31-12-2099

Agreement Priority Priority of the agreement 1

Document Currency Agreement currency USD

Items

Item Number … 10

Calculation Sheet Once you assign this calculation sheet, all the details from this sheet are carried over.

DOT-TCCS-CR-01DOT-TCCS-CR-02DOT-TCCS-CR-03DOT-TCCS-CR-04

3. Release the freight agreement.


8.14 Defining Settlement Profile

You can use this procedure to define the profile for creating invoices. The settlement profile consists of a set of parameters with which you can control how the system creates invoices. You can assign the defined settlement profile to an organizational unit using the transaction /SCMTMS/TCM_FASET . If you do not specify a settlement profile, the system uses standard default settings to create settlement documents.

Procedure

1. In Customizing for Transportation Management , choose Settlement Define Settlement Profile .

2. Enter the following values:

Table 199


Settlement Profile … DOT_SP_01

122




Data Source Identifies the data source to be used during settlement document creation.

Planned Data

Charge Item Level Controls if the settlement document has to be created for each forwarding order (FWO)/freight order (FO) document or if a settlement document has to be created for each FWO/FO item.

Header

Split/Cons . Defines the split consolidation criteria during the generation of settlement document.

FSD_CREAT

Calculation Option Specifies how the calculation should be performed when creating the invoice. You can copy fixed charges and redetermine others, or copy all charges.

Copy Fixed Charges and Redetermine Others

Invoicing Level Specifies whether the invoice should be created by order, by main item of the order, or if the orders should be consolidated based on the split consolidation strategy.

Settlement on Header


8.15 Defining Calculation Profile

Procedure

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



Table 200

Field Value

Calculation Profile DOT_PORG

Description DOT: Charge Calculation Profile

Calc. Date Ty EET_DATE Expected End Date of Complete Carriage

Calculation Level 1 Calculation at Header Level

Agmt Det. Rule




Field Value

Calc Sheet Det. Rule

Through Rate

Dim Wt Profile Deselected

Dimal Wt Cond

Exch. Rate Type

Data Source Actual Route


8.16 Defining Cost Distribution Profiles

Procedure

1. In Customizing for Transportation Management , choose Basic Functions Cost Distribution Define Cost Distribution Profiles .

2. On the Change View “Define Cost Distribution Profiles”: Overview screen, create the following entry:

Table 201

Field Value

Dist. Prf. DIR_ITEM

Description Direct Item Distribution

Distribution Method DIRECT

Distr. Rle Gross Weight

Distr. Lvl ERP item


8.17 Defining General Settings for Charge Calculation

Procedure

1. In Customizing for Transportation Management , choose Basic Functions Charge Calculation Basic Settings Define Organizational Unit Settings .


Table 202

Field Value

Org. Unit DOT-PORG-1

124



Field Value

Org. ID <Internal ID of DOT-PORG-1>

Default Purch. Org. <Internal ID of DOT-PORG-1>

Default Carrier DOT-CR-03

Set.Prof. DOT_SP_01

Profile Det.Condition Blank

Calculation Profile DOT_PORG

Local Currency USD

Hierarchy Category Blank

Default Charges View Blank

Eval. All Agreements Blank

Distribution Profile DIR_ITEM


8.18 Defining Cost Distribution Methods

Procedure

1. In Customizing for Transportation Management , choose Basic Functions Cost Distribution Define Cost Distribution Method .

2. On the Change View “Define Cost Distribution Method”: Overview screen, create the following entry:

Table 203

Field Value

Distribution Method DIRECT

Distribution Class /SCMTMS/CL_TCD_ALLOC_CHRG_DIR





9 Strategic Freight Procurement

Activities

● Defining RFQ Type [page 126]

● Defining Optimizer Strategy [page 127]

● Assigning Users to Organization [page 127]

● Defining Commodity Type Codes [page 128]

● Defining Source Location Scale Template [page 128]

● Defining Destination Region Scale Template [page 129]

● Defining Stop-Off Scale Template [page 130]

● Defining Rate Table Template for Basic Freight [page 130]

● Defining Rate Table Template for Fuel Surcharges [page 131]

● Defining Rate Table Templates for Stop-Off Rates [page 133]

● Defining Calculation Sheet Template [page 134]

9.1 Defining RFQ Type

Procedure

1. In Customizing for SAP Transportation Management, choose Transportation Management Master DataAgreement RFQs and Quotations Define Freight Agreement RFQ Types .

2. Choose the New Entries pushbutton and enter the following data:

Table 204

Field Value

RFQ Type RFQ1

RFQ Master No. Rnge TR

RFQ/Quote No. Range TR

Text Schema Blank

Track Changes Select

Default Type Deselect

Agr. Type DOT5

RFQ Publication Select

Agmt Creation Select

126


Configuration Guide for Domestic Outbound TransportationStrategic Freight Procurement

Field Value

Edit RFQ Blank

Description RFQ type for DOT

Create & Pblsh Deselect


9.2 Defining Optimizer Strategy

Procedure

1. In Customizing for SAP Transportation Management, choose Transportation Management Master DataAgreement RFQs and Quotations Define Target Share Strategies .


Table 205

Field Value

Strategy DOT_RFQ_STR

Description RFQ Strategy for DOT

Max. No. of Carriers 4

Min. No. of Carriers 2

3. Select your strategy and choose Define Conditions from the navigation tree.


Table 206

Partner Max. Share Min. Share Incumbent

Blank 30 10 Deselect

Blank 70 30 Select


9.3 Assigning Users to Organization

Procedure

1. On the SAP Easy Access screen in your SAP Transportation Management system, choose Master DataOrganization Change Organization and Staffing or call transaction PPOME .

2. Select the organization DOT-PORG-1 that you created in the Defining Purchasing Organizations [page 21] step.




3. In the Staff assignments (structure) screen area, open the context menu for organization DOT-PORG-1 and choose Create .

The Choose Relationship dialog box appears.

4. Choose Incorporates .

5. On the Basic data tab page, enter Planner for both the position and the description.

6. Select the Head of own organizational unit checkbox.


8. Select the new position, open the context menu, and choose Assign .

A new Choose Relationship dialog box appears.

9. Choose Holder User .

10. Enter your user name in the following dialog box.

11. Choose Copy .


9.4 Defining Commodity Type Codes

Procedure

1. In Customizing for Transportation Management , choose Master Data Classification of Goods Define Commodity Codes .


Table 207

Code Type Description Maximum Length of Commodity Code

SG SCTG 5

3. Select the new code type and choose Commodity Codes from the tree structure.


Table 208

Commodity Code Description

35110 Electric motors and generators


9.5 Defining Source Location Scale Template

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Charge Management and Service Product Catalogs Scale Templates Create Scale Template .

128



2. On the New Scale Template screen, choose the General Data tab page and enter the following data:

Table 209


Scale Template Scale identifier DOT-SCALE-ORIGIN-LOC

Description Description of the scale Source location


LOC


3. Choose the Items tab page and enter the following data:

Table 210



Absolute

Internal Location Location Code SP3100@ERP001


9.6 Defining Destination Region Scale Template

Procedure



Table 211


Scale Template Scale identifier DOT-SCALE-REGION

Description Description of the scale Region-based scale


REGION



Table 212



Absolute

Region Destination region IN, UT, ND, CA, KY





9.7 Defining Stop-Off Scale Template

Procedure



Table 213


Scale Template Scale identifier DOT-SCALE-STOP_CHG

Description Description of the scale Stop-off scale template


Number

Scale Type This field defines how the scales need to be maintained

Base Scale (>=)



Table 214



Absolute

Scale Value Qty Number of stops 1

2

3

4

5

6


9.8 Defining Rate Table Template for Basic Freight

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Charge Management and Service Product Catalogs Rate Table Templates Create Rate Table Template .

2. On the New Rate Table Template screen, choose the General Data tab page and enter the following information:

130



Table 215


Rate Table Template Unique identifier for the rate table DOT-RATE-FB00

Description Description of the table Rate Table Template for Basic Freight

Charge Usage This indicator identifies the scenario in which the rate table can be used (for example, for customer billing integration or supplier invoice integration).

Service Provider

Charge Type Indicates where the charge type is linked for integration with SAP ERP

FB00 – Basic Freight

Charge Category Defaults from the charge type 004 – Basic Freight

Charge Subcategory Defaults from the charge type 100000 – Freight Charges

Positive/Negative Defaults from the charge type Positive value

Value Defaults from the charge type Absolute value

3. In the Scales table, enter the following data:

Table 216


Scale Template Assign the scale template here that you defined previously. This activates the entries in the rate table according to the sequence.

1: DOT-SCALE-ORIGIN-LOC

2: DOT-SCALE-REGION


2: DESTLOC_REG

Minimum Value N/A Deselect

Maximum Value N/A Deselect

Rel.-Calc. Method N/A Deselect

Capacity Driver N/A Select


9.9 Defining Rate Table Template for Fuel Surcharges

Procedure






Table 217


Rate Table Template Unique identifier for the rate table DOT-RATE-FUEL-SURCHG

Description Description of the table Fuel Surcharge Rates


Service Provider


FUEL – Fuel Surcharge

Charge Category Defaults from the charge type 003 – Transportation Charges & Additional Charges

Charge Subcategory Defaults from the charge type 103008 – Fuel Surcharge

Positive/Negative Defaults from the charge type Positive value

Value Defaults from the charge type Percentage value

3. In the Scales table, enter the following data:

Table 218


Dimension In the rate table, the dimension defines a row (x-axis) or a column (y-axis). A rate table can contain multiple scales (up to 9).

1 for the first scale


1: DOT-SCALE-REGION


DESTLOC_REG

Description Defaults Destination Location

Scale Type N/A Same Scale (=)


132



9.10 Defining Rate Table Templates for Stop-Off Rates

Procedure



Table 219


Rate Table Template Unique identifier for the rate table DOT-RATE-STOPOFF-CHG

Description Description of the table Stop-off charges


Service Provider


STOP

Charge Category Defaults from the charge type 002 – Additional Charges

Charge Subcategory Defaults from the charge type 609102 – Stop in Transit

Positive/Negative Defaults from the charge type Positive or negative value

Value Defaults from the charge type Absolute value

3. In the Scales table, choose the Insert pushbutton and enter the following data:

Table 220



DOT-SCALE-STOP_CHG


NUMBER_OF_STOPS

Description Defaults Number of stops

Minimum Value N/A Deselect

Maximum Value N/A Deselect

Rel.-Calc. Method N/A Deselect





Rounding Profile N/A Blank

Scale Base Defaults Number

Scale Base Description Defaults Number


9.11 Defining Calculation Sheet Template

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Charge Management and Service Product Catalogs Calculation Sheet Templates Create Calculation Sheet Template .

2. On the General Data tab page of the New Calculation Sheet Template screen, enter the following data in the Basic Data screen area:

Table 221


Calculation Sheet Unique identifier for the calculation sheet that you are defining

DOT-TCCS-RFQ

Description Description of the calculation sheet TCCS Template for Freight RFQs

Charge Usage Indicates whether this calculation sheet is used for customers, vendors (carriers), both customers and vendors, or neither customers nor vendors. It is used only for decision making during the tendering process.

2 – Service Provider

3. Switch to the Basic Data tab page below the Items table and set the calculation resolution base to ROOT . This means that the calculation base applies to the entire document.

4. In the Items screen area, choose the Insert pushbutton and the choose the Single Item option.


Table 222


Item (Overview of Positions) Shows the levels of the charge elements on this calculation sheet, and the descriptions derived from the assigned charge types.

0: Basic Freight (FB00)

1: Fuel Surcharge (FUEL)

2: Stop-off (STOP)

Calculation Sheet Line Number Defines the sequence in which the charge types are executed

Blank

Instruction Type This field relates each charge type to each other and determines how the

Standard (for all charge types)

134




calculations are carried out for each charge type. You can specify whether the item represents a sum, or if it is a direct calculation of the charge.

Charge Type Defines the charge type specified above for each item.

FB00

FUEL

STOP

Currency Applicable currency or percentage for charge items calculated as percentages

USD (Basic Freight and Stop)

% (Fuel)

6. Select the line item for Basic Freight .

7. On the Rate tab page in the details area, enter the rate table template DOT-RATE-FB00 .

8. Switch to the Basic Data tab page and enter the following data:

Table 223




Standard


Line-Haul Charge

Charge Type Assigned charge type FB00

Leading Charge Type Not relevant Select

Calculation Resolution Base This base indicates at what level the calculation sheet is to be executed. For example, this could be executed at the header level for the whole freight order, or it could be executed for a particular stage only.

Product

Mandatory This indicator makes the charge type mandatory.

No – for all charge types

Calculation Method Type N/A Standard

9. Select the line item for Fuel Surcharge .

10. On the Rate tab page in the details area, enter the rate table template DOT-RATE-FUEL-SURCHG .


Table 224








Standard


Fuel Surcharge

Charge Type Assigned charge type FUEL

Reference-From Line No. Not relevant 20


Calculation Method Type Calculation method type Standard

12. Select the line item for Stop-Off Charge (only for carriers 1 and 2).

13. Enter the following values on the Rate tab page:

Table 225


Rate Table Assigned rate table DOT-RATE-STOPOFF-CHG

Reference-From Line No. N/A 0


Table 226



Standard

Description Description of the charge item on the calculation sheet

Blank

Charge Type Assigned charge type STOP



Calculation Method Type Not relevant Standard


136



10 Assigning Event Manager Role to Users

This procedure allows you to track freight orders in SAP Event Management and to run SAP Event Management.

Procedure

1. In Customizing for SAP Event Management, choose Event Management Event Messages, Status Queries, and Web Interface Web Interface Assign User Profiles and Web Interface Transactions to Users .

2. Select your user.


Table 227


Web Int. Trans. Web interface transaction ODT20_SHIP_FO

User Profile … ODT20_SHIPPER_FO


Configuration Guide for Domestic Outbound TransportationAssigning Event Manager Role to Users



11 Appendix

Activities

● Content for File LTL_Rates_03.xml [page 138]

● Content for File LTL_Rates_04.xml [page 140]

11.1 Content for File LTL_Rates_03.xml

You can find the XML files in the folder DOT Rates . Replace the source location accordingly.

Table 228

Valid From January 1, 2010

Valid To December 31, 2999

Currency USD

Table 229

Source Location

Destination Location Transportation Zone

Product Freight Group

≥ 0 LB (Gross)

≥ 500 LB (Gross)

≥ 1.000 LB (Gross)

≥ 2.000 LB (Gross)

≥ 5.000 LB (Gross)

≥ 10.000 LB (Gross)

≥ 20.000 LB (Gross)

SP3100@ERP001

DOT-ZIP-303

100 3.00 2.80 2.60 2.40 2.00 1.80 1.30

SP3100@ERP001

DOT-ZIP-303

125 3.75 3.50 3.25 3.00 2.50 2.25 1.62

SP3100@ERP001

DOT-ZIP-303

70 2.10 1.96 1.82 1.68 1.40 1.26 .91

SP3100@ERP001

DOT-ZIP-303

77.5 2.25 2.10 1.95 1.80 1.50 1.35 .97

SP3100@ERP001

DOT-ZIP-402

100 3.00 2.80 2.60 2.40 2.00 1.80 1.30

SP3100@ERP001

DOT-ZIP-402

125 3.75 3.50 3.25 3.00 2.50 2.25 1.62

SP3100@ERP001

DOT-ZIP-402

70 2.10 1.96 1.82 1.68 1.40 1.26 .91

138


Configuration Guide for Domestic Outbound TransportationAppendix

Source Location



≥ 0 LB (Gross)

≥ 500 LB (Gross)

≥ 1.000 LB (Gross)

≥ 2.000 LB (Gross)

≥ 5.000 LB (Gross)

≥ 10.000 LB (Gross)

≥ 20.000 LB (Gross)

SP3100@ERP001

DOT-ZIP-402

77.5 2.25 2.10 1.95 1.80 1.50 1.35 .97

SP3100@ERP001

DOT-ZIP-410

100 3.00 2.80 2.60 2.40 2.00 1.80 1.30

SP3100@ERP001

DOT-ZIP-410

125 3.75 3.50 3.25 3.00 2.50 2.25 1.62

SP3100@ERP001

DOT-ZIP-410

70 2.10 1.96 1.82 1.68 1.40 1.26 .91

SP3100@ERP001

DOT-ZIP-410

77.5 2.25 2.10 1.95 1.80 1.50 1.35 .97

SP3100@ERP001

DOT-ZIP-477

100 3.00 2.80 2.60 2.40 2.00 1.80 1.30

SP3100@ERP001

DOT-ZIP-477

125 3.75 3.50 3.25 3.00 2.50 2.25 1.62

SP3100@ERP001

DOT-ZIP-477

70 2.10 1.96 1.82 1.68 1.40 1.26 .91

SP3100@ERP001

DOT-ZIP-477

77.5 2.25 2.10 1.95 1.80 1.50 1.35 .97

SP3100@ERP001

DOT-ZIP-606

100 3.00 2.80 2.60 2.40 2.00 1.80 1.30

SP3100@ERP001

DOT-ZIP-606

125 3.75 3.50 3.25 3.00 2.50 2.25 1.62

SP3100@ERP001

DOT-ZIP-606

70 2.10 1.96 1.82 1.68 1.40 1.26 .91

SP3100@ERP001

DOT-ZIP-606

77.5 2.25 2.10 1.95 1.80 1.50 1.35 .97

SP3100@ERP001

DOT-ZIP-701

100 3.00 2.80 2.60 2.40 2.00 1.80 1.30

SP3100@ERP001

DOT-ZIP-701

125 3.75 3.50 3.25 3.00 2.50 2.25 1.62

SP3100@ERP001

DOT-ZIP-701

70 2.10 1.96 1.82 1.68 1.40 1.26 .91

SP3100@ERP001

DOT-ZIP-701

77.5 2.25 2.10 1.95 1.80 1.50 1.35 .97




11.2 Content for File LTL_Rates_04.xml

You can find the XML files in the folder DOT Rates . Replace the source location accordingly.

Table 230

Valid From January 1, 2010

Valid To December 31, 2999

Currency USD

Table 231

Source Location



≥ 0 LB (Gross)

≥ 500 LB (Gross)

≥ 1.000 LB (Gross)

≥ 2.000 LB (Gross)

≥ 5.000 LB (Gross)

≥ 10.000 LB (Gross)

≥ 20.000 LB (Gross)

SP3100@ERP001

DOT-ZIP-303

100 3.30 3.08 2.86 2.64 2.20 1.98 14.30

SP3100@ERP001

DOT-ZIP-303

125 4.15 3.85 3.57 3.30 2.75 2.47 1.78

SP3100@ERP001

DOT-ZIP-303

70 2.31 2.15 2.02 1.84 1.54 1.38 1.01

SP3100@ERP001

DOT-ZIP-303

77.5 2.47 2.31 2.14 1.98 1.65 1.48 1.07

SP3100@ERP001

DOT-ZIP-402

100 3.30 3.08 2.86 2.64 2.20 1.98 14.30

SP3100@ERP001

DOT-ZIP-402

125 4.15 3.85 3.57 3.30 2.75 2.47 1.78

SP3100@ERP001

DOT-ZIP-402

70 2.31 2.15 2.02 1.84 1.54 1.38 1.01

SP3100@ERP001

DOT-ZIP-402

77.5 2.47 2.31 2.14 1.98 1.65 1.48 1.07

SP3100@ERP001

DOT-ZIP-410

100 3.30 3.08 2.86 2.64 2.20 1.98 14.30

SP3100@ERP001

DOT-ZIP-410

125 4.15 3.85 3.57 3.30 2.75 2.47 1.78

SP3100@ERP001

DOT-ZIP-410

70 2.31 2.15 2.02 1.84 1.54 1.38 1.01

SP3100@ERP001

DOT-ZIP-410

77.5 2.47 2.31 2.14 1.98 1.65 1.48 1.07

SP3100@ERP001

DOT-ZIP-477

100 3.30 3.08 2.86 2.64 2.20 1.98 14.30

140



Source Location



≥ 0 LB (Gross)

≥ 500 LB (Gross)

≥ 1.000 LB (Gross)

≥ 2.000 LB (Gross)

≥ 5.000 LB (Gross)

≥ 10.000 LB (Gross)

≥ 20.000 LB (Gross)

SP3100@ERP001

DOT-ZIP-477

125 4.15 3.85 3.57 3.30 2.75 2.47 1.78

SP3100@ERP001

DOT-ZIP-477

70 2.31 2.15 2.02 1.84 1.54 1.38 1.01

SP3100@ERP001

DOT-ZIP-477

77.5 2.47 2.31 2.14 1.98 1.65 1.48 1.07

SP3100@ERP001

DOT-ZIP-606

100 3.30 3.08 2.86 2.64 2.20 1.98 14.30

SP3100@ERP001

DOT-ZIP-606

125 4.15 3.85 3.57 3.30 2.75 2.47 1.78

SP3100@ERP001

DOT-ZIP-606

70 2.31 2.15 2.02 1.84 1.54 1.38 1.01

SP3100@ERP001

DOT-ZIP-606

77.5 2.47 2.31 2.14 1.98 1.65 1.48 1.07

SP3100@ERP001

DOT-ZIP-701

100 3.30 3.08 2.86 2.64 2.20 1.98 14.30

SP3100@ERP001

DOT-ZIP-701

125 4.15 3.85 3.57 3.30 2.75 2.47 1.78

SP3100@ERP001

DOT-ZIP-701

70 2.31 2.15 2.02 1.84 1.54 1.38 1.01

SP3100@ERP001

DOT-ZIP-701

77.5 2.47 2.31 2.14 1.98 1.65 1.48 1.07




Typographic Conventions

Table 232

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name> ”.

Example Example Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ● Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

● Cross-references to other documentation or published works

Example ● Output on the screen following a user action, for example, messages

● Source code or syntax quoted directly from a program

● File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

142


Configuration Guide for Domestic Outbound TransportationTypographic Conventions

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sap.com



www.sap.com

© Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

http://www.sap.com

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark