Prévia do material em texto

Best Practices Guide | PUBLIC
SAP S/4HANA 1909
2020-10-02
Transportation Management in SAP S/4HANA: 
General Configuration Guide
©
 2
02
0 
SA
P 
SE
 o
r a
n 
SA
P 
affi
lia
te
 c
om
pa
ny
. A
ll r
ig
ht
s 
re
se
rv
ed
.
THE BEST RUN 
Content
1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Supported Deployments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3 Activities/Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
3.1 Create Active Version and Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2 Defining Basic Settings for Creating the System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.3 Activate HR Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.4 Defining Shipping Condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
3.5 Defining Number Range Intervals for Freight Order Management. . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.6 Defining Transportation Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.7 Define Transportation Activities for Tracking and Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.8 Defining Freight Order Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.9 Defining Freight Unit Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
3.10 Defining Freight Unit Building Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
3.11 Defining Control Keys for Document Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.12 Defining Logistics Integration Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
3.13 Defining Business Partner Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.14 Defining Partner Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.15 Assigning BP Roles to Partner Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.16 Define POWL Queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.17 Category Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.18 Category Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
2 PUBLIC
Transportation Management in SAP S/4HANA: General Configuration Guide
Content
1 Purpose
The purpose of this document is to describe the general configuration steps required to manually set up the 
configuration within the system landscape that has already been installed using the corresponding installation 
or configuration guides for installation.
If you want to install SAP S/4HANA locally (on-premise) and if you do not want to configure manually and 
prefer an automated installation process, use BC Sets delivered.
Transportation Management in SAP S/4HANA: General Configuration Guide
Purpose PUBLIC 3
2 Preparation
2.1 Prerequisites
BD9_US – needs to be configured. For more information about the prerequisite building blocks for this 
scenario, see Prerequisites Matrix and Software and delivery requirements on the SAP Best Practices Explorer 
pages: SAP S/4HANA On-Premise SAP Best Practices for SAP S/4HANA (on premise) Accelerators. 
For automated installation process using BC Sets and other tools, you can set up a best-practice client and 
activate the implementation content. For more information, see the Administration Guide for the 
Implementation of SAP S/4HANA, on premise edition which is linked in the content library (included in the 
documentation package).
2.2 Supported Deployments
The configuration guide provides the implementation content for SAP S/4HANA – (OP) installed locally (on-
premise), full scope and content coverage.
Depending on the use case/deployment option/ S/4HANA product version, you need to implement the 
required scope/content starting with the Public cloud chapter and proceed with the next required sections.
• For the full scope of the on premise scope & content – PC and OP are required
4 PUBLIC
Transportation Management in SAP S/4HANA: General Configuration Guide
Preparation
3 Activities/Settings
3.1 Create Active Version and Model
 Note
Configuration settings in this section are not part of the BC Sets delivered together with the documentation 
guides and need to be configured manually.
1. Access the transaction using one of the following navigation path:
IMG Path Transportation Management Master Data Create 
Active Version and Model
2. Create a new entry for Model and Planning Version using the following data:
Model Name Planning Version
000 000
3. Save your entries.
3.2 Defining Basic Settings for Creating the System 
Landscape
Context
 Note
Configuration settings in this section are not part of the BC Sets delivered with the documentation guides; 
you must configure them manually.
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings PUBLIC 5
Procedure
1. To name the logical system, in Customizing, choose:
SCM Extended Warehouse Management SCM Basis Integration Basic Settings for Creating the 
System Landscape Name Logical Systems .
2. Insert a line and create an entry using the data in the following table:
Logical System Name
<System>CLNT<Client> <System>CLNT<Client>
3. Save your entries.
4. To Assign Logical System to Client, choose:
5. SCM Extended Warehouse Management SCM Basis Integration Basic Settings for Creating the 
System Landscape Assign Logical Systems to Client
6. Insert a line and create an entry using the data in the following table:
Client Description Logical System Currency Client Role
<Client> Client Description <System>CLNT<Clien
t>
USD e.g. Demo
7. Save your entries.
8. To maintain the business system group, in Customizing, choose:
SCM Extended Warehouse Management SCM Basis Integration Basic Settings for Creating the 
System Landscape Maintain Business System Group .
9. Insert a line and create an entry using the data in the following table:
Business System Group Description
BSG BSG for <System>CLNT<Client>
10. Save your entries.
11. To assign the logical system and queue type, in Customizing, choose:
SCM Extended Warehouse Management SCM Basis Integration Basic Settings for Creating the 
System Landscape Assign Logical System and Queue Type .
12. Insert a line and create an entry using the data in the following table:
Business System Group Logical System SAP Ind. Queue Type
BSG <System>CLNT<Client> X I Inbound Queries
13. Save your entries.
6 PUBLIC
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings
14. To define SLD Data of Business Systems choose:
Transportation Management Basic Functions Integration Define SLD Data of Business Systems
15. Insert Line and create a new entry using the following data:
BusinessSystem Group Logical System SAP Ind.
<System> <System>CLNT<Client> X Flag set. Event has occurred.
16. Save your entries.
3.3 Activate HR Integration
 Note
Configuration settings in this section are not part of the BC Sets delivered together with the documentation 
guides and need to be configured manually.
1. Access the transaction using one of the following navigation path:
IMG Path Personnel Management Organizational Management
Integration Integration with SAP Business Partner
Activate Integration
2. Make sure following entry is existing:
Group Sem. Abbr. Value Abbr. Description
HRALX HRAC X Activate HR Integration
3. Save your entries.
3.4 Defining Shipping Condition
Context
You define shipping conditions in this step. You enter the shipping conditions defined here in the customer 
master record in the sales data for each sales area. The SAP system copies the shipping condition into the 
sales document header.
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings PUBLIC 7
Procedure
1. Access the transaction using one of the following navigation path:
IMG Path Logistics Execution Shipping Basic Shipping 
Functions Shipping Point and Goods Receiving Point 
Determination Define Shipping Conditions
2. Create an entry using the following data:
Field Value
Shipping Conditions Y1
Description TM Outbound Road
3. Save your entries
3.5 Defining Number Range Intervals for Freight Order 
Management
Define number range intervals for freight order and freight unit business documents.
Procedure
1. In Customizing for SAP TM, choose:
Transportation Management Freight Order Management Define Number Range Intervals for Freight 
Order Management
2. Insert a line and create an entry using the data in the following table:
Field Freight Unit Value Freight Order Value
Number Range Number FU FO
From No. 00000000004100000000 00000000006100000000
To Number 00000000004199999999 00000000006199999999
3. Save your entries.
8 PUBLIC
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings
3.6 Defining Transportation Modes
Define transportation modes and assign a default means of transport for each transportation mode, if required. 
The default is only used if a specific means of transport cannot be provided, for example, if there is no resource 
or equipment type.
Procedure
1. In Customizing for SAP TM, choose:
Transportation Management Master Data Transportation Network Transportation Lane Define 
Transportation Mode
2. Check if the following entries are maintained:
Transportation Mode (TM-Specific) Value
Mode of Transport 01
Description Road
Mode-of-Transport Category 1
Transportation Mode Category (TM-Specific) 1 Road
Main Carriage
3. Save your entries.
3.7 Define Transportation Activities for Tracking and 
Tracing
Context
In this Customizing activity you define transportation activities for tracking and tracing.
You also define events. You can assign the events to the business objects in which they are used. Moreover, you 
can assign the events to your document types.
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings PUBLIC 9
Procedure
1. Access the transaction using one of the following navigation path:
Transportation Management Integration Tracking and Tracing of Processes and Documents Define 
Transportation Activities for Tracking and Tracing
2. Select Event for Business Document in Dialog Structure and create a new entry using the following data:
Event Description Transp Act Stop Cat Internal
Last_Departure Last Departure 04 Arrival I Stop with Change of 
Main Resource - In­
bound
Deselect
3. Mark just created entry and select Assignment of Events to Business Objects in Dialog Structure and create 
a new entry using following data:
Event Assignment of Events to Business Object
Last_Departure TO Freight Order
4. Save your entries.
3.8 Defining Freight Order Types
Define your freight order types and assign valid item types and event codes to them
Procedure
1. In Customizing for SAP TM, choose:
Transportation Management Freight Order Management Freight Order Define Freight Order Types
2. Create an entry using the data in the following table:
Field Description Value
Freight Order Type Unique freight order type ID (four 
characters)
YRO1
Description Freight order type description Road Freight Order with 
Subcontracting
10 PUBLIC
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings
Field Description Value
Default Type Default freight order type Select
(If no default freight order type exists 
in the system.)
Number Range Settings
Time for Drawing Specifies when a number is assigned 
to freight order.
S Draw Number When Saving 
Document
Number Range Interval Number range to be used for this 
document type.
FO
Basic Settings
Transportation Mode Method of transporting a product, for 
example, by road, rail, sea, or air.
O1
Freight Order Can Be Subcontracted Defines whether freight order type 
can use subcontracting processes.
01 Relevant for 
SubcontractingSequence Type 
of Stops
Sequence Type of Stops Sequence Type of structure to be 
used to link stages to one another.
01 Defined and Linear
Shipper/Consignee Determination Defines how shipper and consignee 
are identified for this freight unit type.
L Determination Based on 
First and Last Location
Fix Document When Saving None Not selected
Freight Order Can Be Deleted Specifies whether this type of freight 
order can be deleted.
Select
Planning Settings
Distance/Duration Determination Controls whether distance and net du­
ration are to be determined in the 
business document.
Use Default for Document 
Category
Execution Settings
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings PUBLIC 11
Field Description Value
Execution Track. Relevant Defines document tracking, as fol­
lows:
○ 1 (no execution tracking)
Initial document execution status 
set to Not Relevant.
○ 2 (execution tracking)
Initial document execution status 
set to Not Started.
○ 3 (execution tracking with exter­
nal event management)
Initial document execution status 
set to Not Started.
2 Execution Tracking
Check Condition “Ready for Exec.” Not used. Blank
Display Mode for Execution Tab Actual Events from TM and EM
Expected Events from EM 
Immediate Processing Determines whether In Process status 
is set as soon as a document is cre­
ated and saved.
Select
Execution Propagation Mode Controls how execution information is 
propagated between different related 
freight documents.
Standard Propagation
Output Options
Output Profile Specifies possible outputs of a busi­
ness document.
Blank
Add. Output Profile /SCMTMS/TOR_PRINT_ROAD
Text Schema Blank
Dynamic Determination of Output Blank
Organizational Unit Determination
Default Org Unit
Execution Organization Organizational unit ID defined as fol­
lows:
○ Unit Function 13 – Planning and 
Execution
○ Unit Role 1 – Organization
Blank
12 PUBLIC
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings
Field Description Value
Purchasing Organization Organizational unit ID defined as fol­
lows:
○ Unit Function 2 – Purchasing
○ Unit Role 1 – Organization
Blank
Execution Group Organizational unit ID defined as fol­
lows:
○ Unit Function 13 – Planning and 
Execution
○ Unit Role 3 – Group
Blank
Purchasing Group Organizational unit ID defined as fol­
lows:
○ Unit Function 2 – Purchasing
○ Unit Role 3 – Group
Blank
Determination Rules
Consider Organization Unit of User Specifies whether the system consid­
ers the organizational unit that is as­
signed to the user in the organiza­
tional unit determination.
Select
Condition Blank
Charge Calculation and Settlement Document Settings
Enable Charge Calculation Select
Automatic Charge Calculation Specifies whether transportation 
charges for business documentsin­
volving freight orders or freight book­
ings are calculated automatically.
Select
Enable Settlement Select
Residence Periods
Completeness Criteria Defines how the system checks com­
pleteness of a freight document.
Execution and Settlement 
Complete
Res. Time (Compl.) Minimum time in days between date 
when a business object instance was 
completed and date when it can be 
moved from current data store to his­
torical data store.
Blank
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings PUBLIC 13
Field Description Value
Res. Time (Canc.) Minimum time in days between date 
when a business object instance was 
cancelled and date when it can be 
moved from current data store to his­
torical data store.
Blank
Integration Settings
Application Object Type Type of application object to be 
tracked in the application system. 
This is required for determining event 
management relevance for an applica­
tion object.
The event manager only processes 
event messages for these objects.
ODT30_TO
Last Exp. Event Last expected event for a document LAST_DEPARTURE
Driver Settings
Number of Required Drivers Number of drivers required in a freight 
order.
0 - Not Relevant for Driver 
Planning
Driver Assignment Type Indicates if driver is responsible for 
one or several transportation stages 
of a freight order, or for the entire 
freight order.
Per Freight Order
Tendering Settings
Use Default Settings Select if you want to use default set­
tings.
Select
Use Condition for Sett. Determ. Use condition for settlement determi­
nation
Not selected
Use Type-Specific Settings Select if you want to further define 
process settings and communication 
settings specific to this freight order 
type.
Not selected
Process Setting Controls the tendering process set­
tings
Blank
Communication Setting Specifies strategy for tendering com­
munication.
Blank
Change Controller Settings
14 PUBLIC
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings
Field Description Value
Default Change Strategy Default strategy used for tendering 
when changes are made to key fields 
in the freight order (for example, part­
ners and quantities).
DEF_CHACO
Change Strategy Det. Cond. Condition that determines the change 
controller strategy at runtime.
If you have defined several change 
controller strategies, you can use a 
condition to determine the correct 
strategy.
The condition type of this condition 
is /SCMTMS/CC_TOR_STRAT.
Blank
Quantity Tolerance Cond. Tolerances used when a quantity is 
changed in the freight order.
Blank
/
Date Tolerance Condition Tolerances used when a date is 
changed in the freight order.
Blank
Additional Settings
HBL or HAWB Strategy Blank
Draw Bill of Lading Number Draw Manually
3. Save your entries.
3.9 Defining Freight Unit Types
Define your freight unit types and assign valid event codes to them. The freight unit type defines parameters 
that influence how the system processes the freight unit.
Context
The system uses either the freight unit type from the freight unit building rule or the default freight unit type 
you define in this Customizing activity.
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings PUBLIC 15
Procedure
1. In Customizing for SAP TM, choose:
Transportation Management Planning Freight Unit Define Freight Unit Types
2. Create an entry using the data in the following table:
Freight Unit Type Value
Freight Unit Type YFU1
Description YFU1: Freight Unit Type 
Number Range Settings
Time for Drawing I Draw Number Immediately
Number Range Interval FU
Basic Settings
Freight Order Can Be Deleted Selected
Planning Settings
Rule for PU/DLV Window Pickup and Delivery as Defined in FWO, FWQ, 
OTR, or DTR
Condition for PU/DLV Window Determ. Blank
Distance/Duration Determination Use Default for Document Category
Execution Settings
Execution Track. Relevance 2 Execution Tracking
Display Mode for Execution Tab 1 Actual Events from TM Only
Expected Events from EM 
Execution Propagation Mode Standard Propagation
Last Expected Event UNLOAD_END
Immediate Processing Select
Change Controller Settings
Default Change Strategy DEF_CHACO
Change Strategy Det. Cond. Blank
16 PUBLIC
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings
Freight Unit Type Value
Quantity Tolerance Cond. Blank
/
Date Tolerance Condition Blank
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
DSO Result Rule Convert to Freight Order for Direct Shipment
Freight Order Determination
Freight Order Type Blank
Freight Order Type Condition Blank
3. Save your entries.
3.10 Defining Freight Unit Building Rules
Define your freight unit building types.
Procedure
1. Access the transaction using one of the following navigation path::
SAP Fiori Launchpad
Profiles and Settings Create Freight Unit Building Rule 
2. On the New Freight Unit Building Rule screen, enter the data in the following table:
Field Description Value
General Data
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings PUBLIC 17
Field Description Value
Freight Unit Building Rule Freight Unit Building Rule 
(FUBR) identification
TM-FUBR-Standard
Description FUBR description TM-FUBR-Standard 
Document Type Freight unit type to be used 
for freight unit.
YFU1
Doc. Type Det. Cnd. Not used Blank
Incompatibility Setting Not used Blank
Freight Unit Building 
Strategy
Strategy for consolidation Consolidate per Item
Freight Unit Update Strategy Item Swap Allowed 
(Standard Behavior)
Critical Quantity Weight/volume limits for 
freight unit
Gross Weight
Item Split Allowed Specifies whether item 
quantities can be split 
across different freight 
units.
Select
Apply Default Route If you select this checkbox, 
the system automatically 
applies the default route 
when creating freight units.
Blank
Advanced Settings
Process Controller Strategy Strategy for building freight 
units
FUB_AUTO
Planning Quantities
Planning Quantity for Freight 
Unit Building
Planning quantity parame­
ter
Gross Weight Gross Volume
Unit of Measure of Split 
Quantity
Unit of measure KG M3
Split Quantity Quantity limit for item, 
based on which freight units 
are built.
25000
18 PUBLIC
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings
Field Description Value
Rounding Quantity Rounding quantity applied, 
if any.
1
3. Save your entries.
3.11 Defining Control Keys for Document Transfer
Define the control keys that determine which documents in a document chain are to be transferred to SAP TM.
Context
In this Customizing activity, you define control keys that determine which documents in a document chain are 
to be transferred to SAP TM. You can define as many control keys as required, with different combinations of 
relevant documents. For sales orders, you can also specify whether sales order scheduling is to take place in 
SAP TM.
The following documents can be transferred to SAP TM: sales orders, purchase orders, stock transport orders, 
returns orders (for example, sales returns, vendor returns, and store returns), outbound deliveries, and 
inbound deliveries.
Procedure
1. In Customizing for SAP TM, choose:
Integration with Other SAP Components Transportation Management Logistic Integration Define 
Control Keys for Document Transfer
2. Check if the data in the following table is maintained:
Control Key
Integration 
Mode
Transfer Sales 
Orders to TM
Transfer Pur­
chase Orders 
to TM
Transfer Out­
bound Deliver­
ies to TM
Transfer In­
bound Deliver­
ies to TM
Requirement 
Class – Short 
Description
0053 Internal TM 
component
Blank Blank Set flag. Blank Integrate 
Outbound 
Delivery
3. Save your entries.Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings PUBLIC 19
3.12 Defining Logistics Integration Profile
Procedure
1. Access the transaction using one of the following navigation path:
Transportation Management Integration Logistics Integration Define Logistics Integration 
Profile
2. Create a new entry using the following data:
Logistics Integration Profile Value
Profile Y001
Description Log. Integration profile for Outbound
Freight Unit Building Rule TM-FUBR-Standard
FU Building Rule Condition Blank
Autom. FU Building Selected
Stage Profile Blank
Stage Profile Condition Blank
Incoterm Loc. Stage Bldng 02 Source Location to Incoterm Location – Type 2
Plan on Requested or Confirmed QTY 02 Plan on Confirmed Quantities
Integration Based on Actual Quantity Not selected
3. Save your entries
20 PUBLIC
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings
3.13 Defining Business Partner Roles
Define your business partner (BP) roles and their attributes.
Procedure
1. In Customizing for SAP TM, choose:
Cross-Application Components SAP Business Partner Business Partner Basic Settings Business 
Partner Roles Define BP Roles
2. Create entries using the data in the following table:
BP Role Title Description
000000 Business Partner (Gen.) Business Partner (General)
FLCU00 FI Customer Business Partner FI Customer
FLCU01 Customer Business Partner Customer
FS0000 Financial Services BP Financial Services Business Partner
CRM010 Carrier Carrier
BUP004 Organizational Unit Organizational Unit
3. Save your entries.
3.14 Defining Partner Functions
In this step, you define the partner functions. You specify the functions involved: supplier, customer, own 
employee, for example.
1. Access the transaction using one of the following navigation path:
IMG Menu
Transportation Management Master Data Business Partners Define Partner Functions
2. Create new entries using the following data:
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings PUBLIC 21
Partner Function Name Type of Partner Number
Uniqueness in the Master 
Data
SP Sold-to party KU Select
PE Payee LI Not selected
PI Invoicing Party LI Not selected
T4 Goods Seller LI Not selected
T5 Addtnl. Notify Part AP Not selected
T6 Prepaid Agrmt. Party KU Not selected
TA Collect Agrmt. Party KU Not selected
TG Addtnl. Agrmt. Party LI Not selected
TJ Executing Carrier LI Not selected
TN Notify Party AP Not selected
TP Collect Invoicing O Not selected
TQ Supplying Company O Not selected
U3 Carrier LI Not selected
U5 Goods Buyer KU Not selected
U6 Shipper KU Not selected
U7 Prepaid Invoicing O Not selected
U8 Receiving Company O Not selected
U9 IssuingCarrier's Agt O Not selected
SH Ship-to party KU Not selected
3. Save your entries
22 PUBLIC
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings
3.15 Assigning BP Roles to Partner Functions
Assign business partner roles to business document party roles to determine the documents available for a 
particular business role.
Context
The system uses these assignments in business documents to do the following:
● Check whether a specific business partner can be used for a specific party role.
● Ensure that the search results only return business partners who can be used for a party role.
If you do not specify a business partner role for a business document party role, the system returns all 
business partners.
Procedure
1. In Customizing for SAP TM, choose:
Transportation Management Master Data Business Partners Assign BP Roles to Partner 
Functions
2. Create entries using the data in the following table:
Partner Function Name BP Role Description
SP Sold-to Party FLCU00 Business Partner FI Cus­
tomer
PE Payee CRM010 Carrier
PI Invoicing Party CRM010 Carrier
T4 Goods Seller 000000 Business Partner (General)
T5 Addtnl. Notify Part 000000 Business Partner (General)
T6 Prepaid Agrmt. Party FLCU00 Business Partner FI Cus­
tomer
TA Collect Agrmt. Party FLCU00 Business Partner FI Cus­
tomer
TG Addtnl. Agrmt. Party CRM010 Carrier
TJ Executing Carrier CRM010 Carrier
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings PUBLIC 23
Partner Function Name BP Role Description
TN Notify Party 000000 Business Partner (General)
TP Collect Invoicing BUP004 Organizational Unit
TQ Supplying Company BUP004 Organizational Unit
U3 Carrier CRM010 Carrier
U5 Goods Buyer 000000 Business Partner (General)
U6 Shipper 000000 Business Partner (General)
U7 Prepaid Invoicing BUP004 Organizational Unit
U8 Receiving Company BUP004 Organizational Unit
U9 IssuingCarrier's Agt BUP004 Organizational Unit
SH Ship-to Party FLCU01 Business Partner Customer
3. Save your entries.
3.16 Define POWL Queries
Procedure
1. Logon to the below app
SAP GUI
Execute transaction POWL_QUERY.
2. Create new entries using the following data:
Query ID Description POWL Type ID Sync. Call
Y_TOR_FO_LOADED Road Freight Orders - 
loaded
SCMTMS_TOR_TO Select
Y_TOR_FO_LOAD_PL_NOT_
LOADED
Road Freight Orders - load­
ing planned, not loaded
SCMTMS_TOR_TO Select
24 PUBLIC
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings
Query ID Description POWL Type ID Sync. Call
Y_TOR_FO_LOAD_UNPL Road Freight Orders – load­
ing unplanned
SCMTMS_TOR_TO Select
Y_TOR_FO_SETTLEMENT Road Freight Orders - for 
settlement
SCMTMS_TOR_TO Select
Y_TOR_FO_SUBCONTR Road Freight Orders - for 
subcontracting
SCMTMS_TOR_TO Select
Y_TOR_FO_TRUCK_AR­
RIVAL
Road Freight Orders - truck 
arrival
SCMTMS_TOR_TO Select
Y_TOR_FO_TRUCK_DEPAR­
TURE
Road Freight Orders - truck 
departure
SCMTMS_TOR_TO Select
Y_TOR_FU_NOT_PLANNED Delivery-Based Freight 
Units - unplanned
SCMTMS_TOR_FU_DTR Select
3. Select Queries one after the other, select Query Parameters and do the following entries:
 Note
Following settings are not part of the BC-Sets delivered and need to be done manually.
Y_TOR_FO_LOADED
Field Value
Subcontracting Status 04
Confirm. Status 04
Load Plan Status (Stop) 20
Execution Status 07
Handling Execution Status 18
Y_TOR_FO_LOAD_PL_NOT_LOADED
Field Value
Subcontracting Status 04
Confirm. Status 04
Load Plan Status (Stop) 20
Execution Status 07
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings PUBLIC 25
Y_TOR_FO_LOAD_PL_NOT_LOADED
Field Value
Handling Execution Status 14
Y_TOR_FO_LOAD_UNPL
Field Value
Subcontracting Status 04
Confirm. Status 04
Load Plan Status (Stop) 00
Execution Status 02
Handling Execution Status 14
Y_TOR_FO_SETTLEMENT
Field Value
Invoicing Status 01, 03, 06
Execution Status 03, 04, 07, 09, 05
Y_TOR_FO_SUBCONTR
Field Value
Subcontracting Status 01
Y_TOR_FO_TRUCK_ARRIVAL
Field Value
Subcontracting Status 04
Confirm. Status 04
Unload Plan Status 00
Execution Status 03
Handling Execution Status 20
Src Stop Hndlg Exe 20
26 PUBLIC
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings
Y_TOR_FO_TRUCK_DEPARTURE
Field Value
Subcontracting Status 04
Confirm. Status 04
Load Plan Status (Stop) 20
Execution Status 07
Handling Execution Status 18
Src Stop Hndlg Exe 18
Y_TOR_FU_NOT_PLANNED
Field Value
Planning Status 01
4. Save your entries.
3.17 Category Definition
SAP GUI
Execute transaction POWL_CAT.
1. Create new entries using the following data:
Query ID Description POWL Type ID
YTM_EXECUTION Execution YTM_EXECUTION
YTM_SETTLEMENT Settlement YTM_SETTLEMENT
YTM_SUBCONTRACTING Subcontracting YTM_SUBCONTRACTING
2. Save your entries.
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings PUBLIC 27
3.18 Category Definition
SAP GUI
Execute transaction POWL_QUERYR.
1. Create new entries using the following data:
Application Query ID Category
Category Se­
quence No
Query Se­
quence No
Tab SequenceNo Activate
SCMTMS_PO
WL_FU
Y_TOR_FU_NO
T_PLANNED
SCMTMS_TOR
_FU
1 1 1 Select
SCMTMS_PO
WL_FRO
Y_TOR_FO_LO
ADED
YTM_EXECU­
TION
2 3 1 Select
SCMTMS_PO
WL_FRO
Y_TOR_FO_LO
AD_PL_NOT_L
OADED
YTM_EXECU­
TION
2 2 1 Select
SCMTMS_PO
WL_FRO
Y_TOR_FO_LO
AD_UNPL
YTM_EXECU­
TION
2 1 1 Select
SCMTMS_PO
WL_FRO
Y_TOR_FO_SE
TTLEMENT
YTM_SETTLE­
MENT
3 1 1 Select
SCMTMS_PO
WL_FRO
Y_TOR_FO_SU
BCONTR
YTM_SUB­
CONTRACT­
ING
1 1 1 Select
SCMTMS_PO
WL_FRO
Y_TOR_FO_TR
UCK_ARRIVAL
YTM_EXECU­
TION
2 5 1 Select
SCMTMS_PO
WL_FRO
Y_TOR_FO_TR
UCK_DEPAR­
TURE
YTM_EXECU­
TION
2 4 1 Select
2. Save your entries.
28 PUBLIC
Transportation Management in SAP S/4HANA: General Configuration Guide
Activities/Settings
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your 
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any 
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such 
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this 
information.
Videos Hosted on External Platforms
Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any 
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within 
the control or responsibility of SAP.
Beta and Other Experimental Features
Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by 
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use 
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your 
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax 
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of 
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
Transportation Management in SAP S/4HANA: General Configuration Guide
Important Disclaimers and Legal Information PUBLIC 29
www.sap.com/contactsap
© 2020 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. The information contained herein may be changed 
without prior notice.
Some software products marketed by SAP SE and its distributors 
contain proprietary software components of other software vendors. 
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for 
informational purposes only, without representation or warranty of any 
kind, and SAP or its affiliated companies shall not be liable for errors or 
omissions with respect to the materials. The only warranties for SAP or 
SAP affiliate company products and services are those that are set forth 
in the express warranty statements accompanying such products and 
services, if any. Nothing herein should be construed as constituting an 
additional warranty.
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 https://www.sap.com/about/legal/trademark.html for 
additional trademark information and notices.
THE BEST RUN 
https://www.sap.com/about/legal/trademark.html
	Transportation Management in SAP S/4HANA: General Configuration Guide
	Content
	1 Purpose
	2 Preparation
	2.1 Prerequisites
	2.2 Supported Deployments
	3 Activities/Settings
	3.1 Create Active Version and Model
	3.2 Defining Basic Settings for Creating the System Landscape
	3.3 Activate HR Integration
	3.4 Defining Shipping Condition
	3.5 Defining Number Range Intervals for Freight Order Management
	3.6 Defining Transportation Modes
	3.7 Define Transportation Activities for Tracking and Tracing
	3.8 Defining Freight Order Types
	3.9 Defining Freight Unit Types
	3.10 Defining Freight Unit Building Rules
	3.11 Defining Control Keys for Document Transfer
	3.12 Defining Logistics Integration Profile
	3.13 Defining Business Partner Roles
	3.14 Defining Partner Functions
	3.15 Assigning BP Roles to Partner Functions
	3.16 Define POWL Queries
	3.17 Category Definition
	3.18 Category Definition
	Important Disclaimers and Legal Information
	Copyright / Legal Notice