Professional Documents
Culture Documents
HowToGuide - TM - Yard Logistics - S4HANA - Integration - ASR - Final
HowToGuide - TM - Yard Logistics - S4HANA - Integration - ASR - Final
How-To Guide
Document Version: 1.0 – Final
Date: September 20, 2021
Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
EXAMPLE Technical names of system objects. These include report names, program names, transaction
codes, table names, and key concepts of a programming language when they are surrounded
by body text, for example, SELECT and INCLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as they
appear in the documentation.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with
appropriate entries to make entries in the system.
2 OVERVIEW........................................................................................................................................6
2.1 Business Process Example ............................................................................................................6
2.2 Integration Scenario – System Landscape....................................................................................7
7 APPENDIX.......................................................................................................................................28
7.1 Related Information .......................................................................................................................28
This guide provides a detailed introduction to setting up the integration between SAP Transportation Management
(TM)-modeled Advanced Shipping & Receiving (ASR) and SAP Yard Logistics for SAP S/4HANA.
Target Groups
• Technical Consultants
• Support Specialists
• System Administrators
• Solution Consultants
The integration between SAP Yard Logistics for SAP S/4HANA (YL) and SAP Transportation Management Modeled
Advanced Shipping & Receiving (TM ASR) in an SAP S/4HANA system is based on the direct integration scenario.
The focus of this current document is to describe the functionality related to the interaction between the TM and YL
solutions.
Prerequisites:
You have installed and correctly configured the following application:
• SAP S/4 HANA 2020
• SAP Yard Logistics
For more information, see the documentation for SAP Yard Logistics for SAP S/4HANA on SAP Help Portal at
https://help.sap.com/yl_s4hana.
A typical business process example would require multiple means of transport; for example, when you make an
online purchase on an eCommerce website like Amazon.com, your order goods from multiple locations where some
goods are from a reseller who is connected to a rail network, and also has ready access to pick up by truck. For such
a business requirement the shipment execution may resemble something like the following figure.
Integration between SAP Transportation Management (TM) and SAP Extended Warehouse Management (EWM) has
been enhanced by new approach called Advanced Shipping & Receiving (ASR) starting with SAP S/4HANA 2020.
The new integration scenario described in this document uses the ASR process capabilities to enable direct
integration between SAP TM and SAP YL, both installed in the same client, without the use of SAP EWM as an
mediating system. The technical implementation of YL - TM Integration based on ASR is done in BAdI
/SAPYL/ASR_TM_INTEGRATION.
It is required to maintain one Alternative Location Identifier (ALI) (of a new type) on the origin and destination location
from the Freight Orders sent to SAP YL.
To do so, in Customizing for SAP TM go to: Transportation Management -→ Master Data -→ Transportation Network
-→ Location -→ Configuration for Alternative Location Identifiers. Define the new ALI type and save your changes.
In TM you must assign specific master data objects (location, transportation lane, etc.) to an active version and
model. To do so, in Customizing choose Transportation Management -→ Master Data and select Create Active
Version and Model.
Configuration settings in this section must be done manually. They are located within the Customizing sub node for
SAP Transportation Management.
Alternative Location Identifier types distinguish between several identification schemes that can be used to identify
locations.
You must define number range intervals for freight orders and freight unit business documents. To do so, in
Customizing for SAP TM, go to Transportation Management -→ Freight Order Management -→ Define Number
Range Intervals for Freight Order Management.
Insert a line in the activity and create an entry using the data in the following table and save your changes.
To Number 00000000006199999999
You must 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. To do so, in Customizing for SAP TM, go to Transportation Management -→ Master
Data -→ Transportation Network -→ Transportation Lane -→ Define Transportation Mode and verify whether the
following entries are maintained. Maintain missing values in any as given in the following table and save your
changes.
Mode of Transport 01
Description Road
Mode-of-Transport Category 1
3.2.4 Resources
Transportation unit groups and types, handling resource groups and types and vehicle groups and types are specific
occurrences of equipment groups and types. Equipment Groups can be used to group equipment types into
categories.
In Customizing for SAP TM, go to Transportation Management -→ Master Data -→ Resources -→ general Settings -
→ Define Equipment Groups and Equipment Types. For Vehicle Group, if required, create a new entry with the
values as shown in the following table:
Select the newly created vehicle group. In the dialog structure, choose Vehicle Types. For the different truck types,
you want to use for the integration process, create new entries with the values maintained in the following table if
required:
Means of Transport to define the missing means of transport. After definition of the missing means of transport,
return to complete definition of the vehicle type and save your changes.
Define means of transport 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 types. In Customizing for SAP TM, go to Transportation Management -→ Master Data -→ Resources -→
Means of Transport and Compartment -→ Define Means of Transport. If required, create a new entry with the values
maintained for the fields in the corresponding column and save your changes. Note that only the fields required for
the integration are mentioned in the table:
Resource class
Number of Indiv.
Resources
No capacity
No direct Load
Schedule
GIS Quality
Default MTr
Sustain. Factor
4.1 Location
To be able to map TM data with Yard Logistics data, warehouse ID must be determined. This will be derived from the
location master data of the shipping and / or destination location of the freight order.
Start transaction /SCMTMS/LOC3 and specify a location. The location must be of type Shipping Point. On the
Alternative ID tab, enter the yard number.
Note that when you use one ALI multiple times, the system will issue a warning message. This warning message can
be ignored.
Please make sure this location has been set as ASR relevant on the General Tab.
Field Value
4.2 Resources
Start transaction /SCMTMS/RES01 and enter a resource ID. Optionally, you can assign vehicle group / type and
equipment group / type.
In this section you find all required settings for the integration of the SAP TM business object Freight Order with SAP
Yard Logistics.
The available functionality of a freight order is mainly defined and activated by the settings maintained for the specific
freight order type. Furthermore, the allowed freight assigned to the freight order is fully specified by freight type and
freight category. Such a combination, of freight type and freight category will be represented in the freight order under
the Item tab as Item Type and Category and freight filtering will be governed by the output profile, which is part of the
post processing framework (PPF) as a subcategory of an action profile.
Thus, an important part of the freight order integration from SAP TM to SAP YL will be addressed by:
• Freight Order Type
• PPF Action Profile
• PPF Output Profile
The integration between SAP TM with SAP YL requires adjustments to the PPF adapter settings derived by the
attribute definition of the ABAP class /SAPYL/CL_PPF_SERV_TOR_B2B.
In Customizing under Cross Application Components → Processes and Tools for Enterprise Applications →
Reusable Objects and Functions for BOPF Environment → PPF Adapter for Output Management in the IMG activity
Maintain PPF Settings, the Action Profile and Action Condition Profile will be specified for the solution, which can
be selected from within the value help list in the output options for freight order type. In the activity Maintain Output
Management Adapter Settings, the output profile (which is a subcategory of an action profile) will be specified, that
then will be available in the freight order type as well as in freight order item type.
The action profile with its actions assigned will be always created specific to an application, i.e. in our case for
/SCMTMS/TRANSPORTATION.
In Customizing under Cross Application Components → Reusable Objects and Functions for BOPF Environment -→
PPF Adapter for Output Management -→ Maintain PPF Settings when choosing above Customizing settings, the
following configuration dialog will be offered:
In Customizing under Cross Application Components -→ Reusable Objects and Functions for BOPF Environment -→
PPF Adapter for Output Management -→ Maintain Output Management Adapter Settings, the output profile defined in
the above-mentioned IMG path will be specified together with the customizing activities for a transportation order.
Select the PPF Output agent /SCMTMS/B2B_SERVICES for the Business Object /SCMTMS/TOR with node Root.
Replace the agent class /SCMTMS/CL_PPF_SERV_TOR_B2B with the custom developed class
/SAPYL/CL_PPF_SERV_TOR_B2B.
With the selected entry above, navigate to node Assign PPF Profiles -> Action Settings and add three Action
Definition entries, setting details can be found in the figures below.
o TOR_ASR_DEL_YL
o TOR_ASR_LOAD_YL
o TOR_ASR_REQ_YL
In Customizing under Transportation Management -→ Freight Order Management -→ Define Item Types for Freight
Order Management, maintain the following:
In Customizing under Transportation Management -→ Freight Order Management -→ Freight Order -→ Define
Freight Order Types
Output Options:
Integration Settings:
Process
Mapping of the freight order type from SAP TM to order type in Yard Logistics is needed for the creation of a yard
request. To create the mapping in Customizing for SAP Yard Logistics, go to Yard Logistics → Integration
→Integration to SAP Transportation Management → Map TM Freight Order Types.
This order type is used for the yard request creation.
<your TM FO type→ <your yard no.→ <your order type→ <your hierarchy
mapping→
Process
In Customizing for SAP Yard Logistics, go to Yard Logistics → Integration → Integration to SAP Transportation
Management → Map TM Relevant TU Types for Yard Request.
This table contains the mapping of TM item categories, which are delivered by SAP, and the TM means of transports
to yard logistics TU type and means of transport. Items in the yard request will be created based on this setting.
Process
In customizing for SAP Yard Logistics, go to Yard Logistics → Integration → Integration to SAP Transportation
Management → Map TM Timestamp to Yard Request Time Point. In this Customizing activity, you make settings for
mapping of freight order time points as requested/acceptable (un)loading, departure and arrival time stamps into yard
request relevant dates and times, which are specific for each yard number and yard request type combination. The
following table shows one sample configuration:
Process
In Customizing for SAP Yard Logistics, go to Yard Logistics → Integration → Integration to SAP Transportation
Management → Map TM Business Partner Roles. The following table shows one sample configuration.
1 Buyer 0001
12 Carrier 0004
5 Consignee 0002
6 Shipper 0003
Process
In Customizing for SAP Yard Logistics, go to Yard Logistics → Integration → Integration to SAP Transportation
Management → Map External Reference Documents to YO Header Reference Documents. The following table
shows one sample configuration:
In this activity, you map the external reference document types to the header reference document types for the yard
order.
<Your TM document <Your external <Your Yard <Your Order type→ <Your reference
type→ reference document Number→ document type→
type →
Process
In Customizing for SAP Yard Logistics, go to Yard Logistics → Integration → Integration to SAP Transportation
Management → Map External Reference Documents to YO Item Reference Documents.
The following table shows one sample configuration: In this activity, you assign the external reference documents to
the item reference documents for the yard order.
Process
In NetWeaver Business Client, go to Settings → Integration to SAP Transportation Management → Assign Packaging
Material to TU Type. In this activity, you assign the Packaging Material to a TU Type
<Your Yard <Your Order <Your Equip/Veh Type→ <Your YL TU <Your Packaging
Number→ Type→ Type→ Material→
Process
In NetWeaver Business Client, choose Master Data → General Setting → Maintain Link Between Packaging Material
(TU) and Means of Transport. In this activity, you map the Means of Transport to Packaging Material.
The following table contains links to information relating to the development Guide.
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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality
are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal
obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations.
Readers are cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.
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. See www.sap.com/copyright for additional trademark information and notices.