02 - TM - in - SAPS4HANA - ConfigurationGuide - InboundTransportation
02 - TM - in - SAPS4HANA - ConfigurationGuide - InboundTransportation
1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Supported Deployments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1 Defining Shipping Condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2 Assigning Goods Receiving Points for Inbound Deliveries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.3 Defining Control Keys for Document Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.4 Defining Logistics Integration Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.5 Activating Transfer of Deliveries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.6 Define POWL Queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.7 Category Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
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.
2.1 Prerequisites
● J45_US – Procurement of Direct Materials 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).
● Basic configurations need to be done following the guide Transportation Management in SAP S/4HANA:
General Configuration Guide.
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
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.
IMG Path
Logistics Execution Shipping Basic Shipping Functions Shipping Point and Goods Receiving Point
Field Value
Shipping Conditions Y4
In this menu option, you allocate the shipping points to the desired combinations of shipping condition and
loading group for each plant.
IMG Path
Logistics Execution Shipping Basic Shipping Functions Shipping Point and Goods Receiving Point
Determination Assign Goods Receiving Points for Inbound Deliveries
Plant 1710
In this Customizing activity, you define control keys that determine which documents in a document chain are
to be integrated into Transportation Management (TM). You can define as many control keys as required, with
different combinations of relevant documents.
IMG Path
Transportation Management Integration Logistics Integration Define Control Keys for Document Integration
SO to TM Blank
PO to TM Blank
SO Schedule Blank
PO Confirmations Blank
In this Customizing activity, you specify the settings to control the building of freight units when working with
the internal TM component. You can create profiles and assign these to TM-relevant business document types.
IMG Path
Profile Y002
In this Customizing activity, you can activate the transfer of delivery documents to SAP TM by assigning a
control key to the relevant delivery types. The control key is a fixed parameter (TM_CONTROL_KEY) that
cannot be changed subsequently in the delivery document.
Note that you can also activate the transfer of the delivery using the control key assigned to the preceding
document in the document chain (for example a purchase order). In this case, the delivery inherits the control
IMG Path
Integration with Other SAP Components Transportation Management Logistic Integration Activate Integration
of Delivery Documents
Field Value
Shipping Condition Y4
SAP GUI
Note
Following settings are not part of the BC-Sets delivered and need to be done manually.
Subcontracting Status 04
Confirm. Status 04
Execution Status 07
SAP GUI
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.
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.
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.