HTG Gts Ewm Integration

PUBLIC
How-To Guide
SAP S/4HANA
Document Version: 1.1 - 2022-08-08
Integration of SAP GTS with EWM in SAP S/4HANA

SAP S/4HANA 1610 and Higher
Document History
Document Version Description
1.0 Review version
1.1 First official release of this guide for release SAP S/4HANA OP 1610 and higher
Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC
Business Scenario © 2022 SAP AG or an SAP affiliate company. All rights reserved. 2
Table of Contents
1 Business Scenario .............................................................................................................................. 5
2 Configuration of the System Connection ........................................................................................... 6

2.1 Background Information About System Landscape Settings .................................................... 6
2.2 Prerequisites for the System Connection .................................................................................... 6
2.3 Cross-Client Settings in GTS ......................................................................................................... 7
2.3.1 Configuring Logical Systems in GTS .............................................................................. 7
2.3.2 Configuring a Group of Logical Systems in GTS ........................................................... 7
2.4 Cross-Client Settings in EWM ........................................................................................................ 8
2.4.1 Configuring Logical Systems in EWM ............................................................................. 8
2.5 Client-Specific Settings in GTS...................................................................................................... 8
2.5.1 Assigning an EWM Logical System to an RFC Destination in GTS .............................. 9
2.6 Client-Specific Settings in EWM .................................................................................................... 9
2.6.1 Assigning a GTS Logical System to an RFC Destination in EWM................................. 9
2.7 Configuration of qRFC Communication........................................................................................ 9
2.7.1 Configuring the qRFC Communication in GTS ............................................................ 10
2.7.2 Configuring the qRFC Communication in EWM ........................................................... 11
3 General Setup ....................................................................................................................................12

3.1 General Settings in EWM .............................................................................................................. 12
3.1.1 Defining Business Systems ........................................................................................... 12
3.1.2 Defining the Customs ID ................................................................................................ 12
3.1.3 Warehouse-Specific Settings ........................................................................................ 13
3.2 General Settings in GTS ............................................................................................................... 14
3.2.1 Defining the Organizational Structure.......................................................................... 14
3.2.2 Transfering Material and Business Partner Master Data ........................................... 18
4 EWM Process Setup ..........................................................................................................................19

4.1 Customizing the Outbound Process ........................................................................................... 19
4.1.1 Adjusting Status Profiles for Item Types ..................................................................... 19
4.1.2 Adjusting Status Profiles for Document Types ........................................................... 19
4.1.3 Adjusting Action Profiles ...............................................................................................20
4.1.4 Defining Item Types .......................................................................................................20
4.1.5 Defining Document Types ............................................................................................. 21
4.1.6 Defining Allowed Item Types ......................................................................................... 21
4.1.7 Mapping Document Types from an ERP System ........................................................ 22
4.1.8 Mapping Item Types from an ERP System .................................................................. 22
4.1.9 Mapping Date Types from an ERP System .................................................................. 22
4.1.10 Determining Warehouse Process Types ...................................................................... 23
4.2 Customizing the Outbound Process in the Advanced Shipping and Receiving Scenario ...... 23
4.2.1 Adjusting Document Types ........................................................................................... 23
4.2.2 Adjusting Status Profiles for Document Types ........................................................... 24
4.2.3 Adjusting Status Profiles for Item Types ..................................................................... 24
4.2.4 Adjusting Header Process Profiles ............................................................................... 25
4.3 Customizing the Inbound Process .............................................................................................. 25
4.3.1 Defining Stock Types ..................................................................................................... 25
4.3.2 Defining Previous Document Types ............................................................................. 26
4.3.3 Mapping Previous Document Types............................................................................. 26
4.3.4 Defining Reference Document Categories .................................................................. 27
4.3.5 Adjusting Reference Document Type Profiles............................................................. 27
4.3.6 Adjusting Status Profiles ............................................................................................... 28
4.3.7 Adjusting Action Profiles ............................................................................................... 28
4.4 Customizing the Inbound Process in the Advanced Shipping and Receiving Scenario ......... 29
4.4.2 Adjusting Date/Time Profiles........................................................................................ 29
4.4.3 Defining Item Types for the Correction Process .........................................................30
4.4.4 Defining Document Types for the Correction Process ...............................................30
4.4.5 Defining Allowed Item Types .........................................................................................30
4.4.6 Mapping Document Types from an ERP System ........................................................ 31
4.4.7 Mapping Item Types from an ERP System .................................................................. 31
4.4.8 Mapping Date Types from an ERP System .................................................................. 32
4.5 Customizing the Scrapping Process ........................................................................................... 32
4.5.1 Configuring Message Processing ................................................................................. 32
5 Process Descriptions ........................................................................................................................ 34

5.1 Outbound Process Compliance Checks ..................................................................................... 34
5.2 Outbound Process Transit Procedure ........................................................................................ 35
5.3 Outbound Process in Advanced Shipping and Receiving ......................................................... 35
5.4 Inbound Process Transit Procedure ........................................................................................... 36
5.5 Inbound Process Temporary Storage ......................................................................................... 36
5.6 Inbound Process in Advanced Shipping and Receiving ............................................................ 37
5.7 Inbound Correction Process in Advanced Shipping and Receiving ......................................... 37
5.8 Scrapping Process ........................................................................................................................ 37
Appendix ....................................................................................................................................................... 39
1 Business Scenario
This how-to guide describes the detailed configuration for integrating SAP Extended Warehouse Management
(EWM) based on SAP S/4HANA 1610 (or higher) to an SAP Global Trade Services (GTS) system.
It covers the following aspects of the configuration:
• Configuration of system connection between EWM based on SAP S/4HANA and GTS
• General configuration steps in EWM and in GTS
• Detailed configuration steps in EWM, for the outbound, the inbound, and the scrapping processes
• Description of the different processes from an EWM point of view
A usual system landscape with EWM and GTS contains 3 systems: an enterprise management system (such as
SAP S/4HANA or SAP ERP), an EWM system, and a GTS system. EWM on SAP S/4HANA has two main different
deployment options: embedded and decentralized. In the embedded case the enterprise management system
and EWM are in the same S/4HANA stack, however GTS is always in a separated system.
Note
In this guide, for the sake of simplicity, the enterprise management system is always called ERP
system, independent of it is an SAP ERP or SAP S/4HANA system.
Note
From a GTS point of view, there is always a so-called feeder system in the landscape. In case of a 3-
system landscape, this feeder system is always the ERP system, while in the 2-system landscape,
the feeder system is ERP and EWM in the common S/4HANA stack.
Important
This guide intended primarily for the integration between the EWM and GTS systems. In order to
establish a complete landscape, the integration between the EWM and ERP systems and also
between the ERP and GTS systems are necessary. If you need further information about the
configuration steps for them, you can check the following documentations:
Integration Guide for SAP Global Trade Services
Overview of Guides or Best Practices Documents for Extended Warehouse Management
Prerequisites
Before you continue with this how-to guide, make sure it fits to your EWM deployment option:
• Option 1:
o Decentralized EWM on SAP S/4HANA OP 1909 or higher, linked to
o SAP ERP 6.0 EhP 3 or higher
• Option 2:
o Decentralized EWM on SAP S/4HANA OP 1909 or higher, linked to
o SAP S/4HANA OP 1610 or higher, used as global enterprise management system
• Option 3:
o Embedded EWM on SAP S/4HANA OP 1610 or higher
For the SAP GTS system in your landscape, the minimum release is SAP GTS release 11.0 or higher.
Important
This guide contains steps and customizing options which are not available in all releases. In these
cases, the differences are mentioned explicitly in the text.
2 Configuration of the System Connection
You use this process to configure the system landscape settings required for the queued remote function call
(qRFC) communication between EWM and GTS.
2.1 Background Information About System Landscape

Settings
You use this chapter to gain an overview of the system landscape entities used in the integration of EWM with
GTS.
Overview of System Landscape Entities

The following table provides an overview of system landscape entities required for the integration:
Customizing
Entity Setting Level Comments
Transport
RFC Destination Cross-Client No Technical setting for RFC and qRFC communication;
Example: Naming convention: <SID>CLNT<CLIENT>;
GTSCLNT001
EWMCLNT001
Logical System Cross-Client Yes Technical setting for RFC and qRFC communication;
Example: Naming convention: <SID>CLNT<CLIENT>;
GTSCLNT001 Can be created in the System Landscape Directory;
EWMCLNT001
The logical system is assigned to the RFC destination;
Own logical system assigned to client.
Business System Client No Used in EWM for transactional data;
Example: Naming convention: <SID>_<CLIENT>;
GTS_001 The business system is assigned to a logical system;
EWM_001
Can be created in the System Landscape Directory;
Own business system assigned to client;
Important
Using the System Landscape Directory (SLD) for maintaining logical and business systems is
optional. Without SLD you can locally define the necessary systems.
2.2 Prerequisites for the System Connection

System administrators must make specific settings for the Remote Function Call (RFC) connection between GTS
and EWM before any Customizing activity is carried out.
Contact your system administrator to make sure that the following prerequisites are met:
• An RFC user exists in each target system/client defined as RFC destination.
• RFC destinations exist between the corresponding GTS and EWM clients.
Procedure
...
1. In the EWM system, create an RFC destination (ABAP Connection) for the GTS client in Customizing for
SAP NetWeaver under Application Server → IDoc Interface / Application Link Enabling (ALE) →
Communication → Create RFC Connections using the naming convention <SYS>CLNT<CLIENT>, for
example GTSCLNT001.
Configuration of the System Connection © 2022 SAP AG or an SAP affiliate company. All rights reserved. 6
2. In the GTS system, create an RFC destination (ABAP Connection) for the EWM client in Customizing for
SAP NetWeaver under Application Server → IDoc Interface / Application Link Enabling (ALE) →
Communication → Create RFC Connections using the naming convention <SYS>CLNT<CLIENT>, for
example EWMCLNT001.
2.3 Cross-Client Settings in GTS

You use this process to prepare GTS for the communication with EWM. The settings affect all clients of the GTS
system and require authorizations for cross-client settings on user and client level.
..
...
...
2.3.1 Configuring Logical Systems in GTS

You use this procedure to define the logical systems in GTS.
Procedure
Carry out the first step of the procedure in your GTS customizing client allowing cross-client settings, and
transport the settings to other GTS systems, if necessary (for example, GTS test system, GTS productive
system). Carry out the subsequent step in all GTS systems (in a client allowing cross-client settings) that you
want to connect to EWM.
1. Define a logical system for your GTS client (for example, GTSCLNT001) and a logical system for your EWM
client (for example, EWMCLNT001) in Customizing for SAP Global Trade Services under System
Communication → Define Logical System.
2. Assign the GTS logical system defined in the first step to the GTS client (for example, in system GTS, assign
GTSCLNT001 to client 001) in Customizing for SAP Global Trade Services under System Communication
→ Assign Logical System.
Example
In a landscape with a GTS customizing system (for example GTC, client 001), a GTS test system
(for example GTT, client 001), and a GTS productive system (for example GTP, client 001), you
define multiple logical systems (for example, GTTCLNT001 and GTPCLNT001) in your GTS
customizing system. The same applies to the EWM systems (for example EWTCLNT001 and
EWPCLNT001).
Note
If you have a 3-system landscape, you must configure logical systems for the ERP systems as well.
2.3.2 Configuring a Group of Logical Systems in GTS

You use this procedure to define the group of logical systems in GTS. You must assign every feeder system to a
group of logical systems. One logical system group can contain one or more logical systems of your feeder
systems. Even if you only have one feeder system, you still must create a group of logical systems, and then
assign the logical system for the feeder system to the group in a later step.
If you want to connect several feeder systems with matching or partly matching characteristics to a GTS system,
you can group the feeder systems together into logical system groups. The feeder systems must contain the
same document structures and organization structures. Logical systems groups help you to reduce data
maintenance considerably.
Prerequisites
You have checked the master data and the Customizing between the various feeder systems that you want to
group together for consistency and made any necessary adjustments. If you do not harmonize the master data
Customizing between the feeder systems, the system will transfer an indefinite subset of data to the GTS system.
Procedure
Carry out the first step of the procedure in your GTS customizing client allowing cross-client settings, and
transport the settings to other GTS systems, if necessary (for example, GTS test system, GTS productive
system). Carry out the subsequent step in all GTS systems (in a client allowing cross-client settings) that you
want to connect to EWM.
1. Define a new group of logical systems (for example, for systems EWM and GTS create group EWM_GTS) in
Customizing for SAP Global Trade Services under System Communication → Define Group of Logical
Systems.
2. Assign all logical systems defined in the previous step to the new group of logical systems (for example,
assign GTSCLNT001 and EWMCLNT001 to group EWM_GTS) in Customizing for SAP Global Trade
Services under System Communication → Assign Logical System to a Group of Logical Systems.
Note
If you have a 3-system landscape, you must assign the logical system for the ERP system to the
group of logical systems as well.
2.4 Cross-Client Settings in EWM

You use this process to prepare the EWM system for the communication with GTS. The settings affect all clients
of the EWM system and require authorizations for cross-client settings on user and client level.
2.4.1 Configuring Logical Systems in EWM

You use this procedure to define the logical systems in EWM.
Procedure
Carry out the first step of the procedure in your EWM customizing client allowing cross-client settings, and
transport the settings to other EWM systems, if necessary (for example, EWM test system, EWM productive
system). Carry out the subsequent step in all EWM systems (in a client allowing cross-client settings) that you
want to connect to GTS.
1. Define a logical system for your EWM client (for example, EWMCLNT001) and a logical system for your GTS
client (for example, GTSCLNT001) in Customizing for Extended Warehouse Management under SCM
Basis → Integration → Basic Settings for Setting Up the System Landscape → Name Logical Systems.
2. Assign the EWM logical system defined in the first step to the EWM client (for example, in system EWM,
assign EWMCLNT001 to client 001) in Customizing for Extended Warehouse Management under SCM
Basis → Integration → Basic Settings for Setting Up the System Landscape → Assign Logical Systems to a
Client.
Example
In a landscape with an EWM customizing system (for example EWC, client 001), an EWM test
system (for example EWT client 001), and an EWM productive system (for example EWP, client
001), you define multiple logical systems (for example, EWTCLNT001 and EWPCLNT001) in your
EWM customizing system. The same applies to the GTS systems (for example GTTCLNT001 and
GTPCLNT001).
2.5 Client-Specific Settings in GTS

You use this process to prepare the GTS client for the communication with EWM.
Process
2.5.1 Assigning an EWM Logical System to an RFC
Destination in GTS
You use this procedure to assign the EWM logical system defined in the GTS system to an RFC destination in GTS.
Note
These settings can’t be transported from your GTS customizing client to other GTS systems and
clients. Therefore, you must repeat the steps in every GTS client connected to an EWM.
Procedure
Carry out the following steps in each GTS client you want to connect to an EWM:
...
1. In Customizing for SAP NetWeaver , choose Application Server → IDoc Interface/Application Link Enabling
(ALE) → Communication → Determine RFC Destinations for Method Calls.
2. Select the EWM logical system, for example, EWMCLNT001.
3. Choose Standard BAPI destination.
4. Enter the RFC destination created by your system administrator for the corresponding EWM system and
choose Enter.
5. Save your entries.
2.6 Client-Specific Settings in EWM

You use this process to configure settings at client level in EWM. The settings are valid for all warehouses of the
client.
2.6.1 Assigning a GTS Logical System to an RFC Destination

in EWM
You use this procedure to assign the GTS logical system defined in the EWM system to a RFC destination in EWM.
Note
These settings can’t be transported from your EWM customizing client to other EWM systems and
clients. Therefore, you must repeat the steps in every EWM client connected to a GTS system.
Procedure
Carry out the following steps in each EWM client you want to connect to a GTS system:
...
1. In Customizing for SAP NetWeaver , choose Application Server → IDoc Interface/Application Link Enabling
(ALE) → Communication → Determine RFC Destinations for Method Calls.
2. Select the GTS logical system, for example, GTSCLNT001.
3. Choose Standard BAPI destination.
4. Enter the RFC destination created by your system administrator for the corresponding GTS system and
choose Enter.
5. Save your entries.
2.7 Configuration of qRFC Communication

You use this process to configure the queued remote function call (qRFC) communication between EWM and
GTS. Most of the communication is done by transactional remote function calls (tRFC), but there are 2 cases,
where qRFC calls are used:
1. GTS sends compliance check triggers to EWM
2. EWM sends the final compliance check update to GTS
Since the communication is bi-directional, you not only configure the sending of data to both systems but also the
receiving of data from both systems.
Prerequisites
You have configured the system connection and global settings as described in the previous chapters. RFC
destinations and logical systems exist both in EWM and in GTS. Business systems exist in EWM as well.
2.7.1 Configuring the qRFC Communication in GTS

You use this procedure to set up the qRFC communication in GTS in order to send compliance check triggers to
EWM and to receive updates from EWM.
Procedure
Carry out the following steps in each GTS client you want to connect to EWM:
...
1. Register the RFC destination for EWM in the QOUT scheduler in GTS. This setting is relevant for the qRFC
communication from GTS to EWM.
a. In the GTS system, on the SAP Easy Access screen, call transaction SMQS.
b. On the qRFC Monitor (QOUT Scheduler) screen, choose Registration.
c. Enter the data as shown in the following table:
Field Value
Destination <RFC Destination>, for example, EWMCLNT001
Max.Conn. 10
Max. Runtime 60
W/o tRFC Leave this field empty.
d. Choose Continue.
2. Register the queue names in the QIN scheduler to configure the execution of inbound queues in GTS. This
setting is relevant for the qRFC communication from EWM to GTS.
a. In the SAP GTS system, on the SAP Easy Access screen, call transaction SMQR.
b. On the qRFC Monitor (QIN Scheduler) screen, choose Registration.
Field Value
Queue Name WMGTS* (or you can use *)
Mode D
Max. Runtime 60
USERDEST Leave this field empty.
Attempts 30
Pause 300
d. Choose Continue.
2.7.2 Configuring the qRFC Communication in EWM
You use this procedure to set up the qRFC communication in EWM in order to receive compliance check triggers
from GTS and to send updates to GTS.
Procedure
Carry out the following steps in each EWM client you want to connect to GTS:
...
1. Register the RFC destination for GTS in the QOUT scheduler in EWM. This setting is relevant for the qRFC
communication from EWM to GTS.
a. In the SAP EWM system, on the SAP Easy Access screen, call transaction SMQS.
b. On the qRFC Monitor (QOUT Scheduler) screen, choose Registration.
Field Value
Destination <RFC Destination>, for example, GTSCLNT001
Max.Conn. 10
Max. Runtime 60
W/o tRFC Leave this field empty.
d. Choose Continue.
2. Register the queue names in the QIN scheduler to configure the execution of inbound queues in EWM. This
setting is relevant for the qRFC communication from GTS to EWM:
a. In the SAP EWM system, on the SAP Easy Access screen, call transaction SMQR.
b. On the qRFC Monitor (QIN Scheduler) screen, choose Registration.
Field Value
Queue Name DLVG* (or you can use DLV*)
Mode D
Max. Runtime 60
USERDEST Leave this field empty.
Attempts 30
Pause 300
d. Choose Continue.
3 General Setup
You use this process to configure the EWM and GTS systems, enabling the usage of the EWM-GTS integration.
These settings are not related to the communication itself and they are independent of the processes you are
using.
In EWM, the following steps are described:

• Defining Business Systems
• Defining Customs ID
• Warehouse-specific Settings:
 Assign Business System
 Assign Customs ID
 Assign Sales Organization
In SAP GTS, the following steps are described:

• Defining the Organizational Structure
 Defining and Assigning Legal Units
 Assigning Plants to Legal Units
 Defining Foreign Trade Organizations
 Assigning Partners to Foreign Trade Organizations
 Defining and Assigning Customs IDs
Prerequisites
You have configured the system connection and global settings as described in the previous chapter. RFC
destinations and logical systems exist both in decentralized EWM and in SAP ERP.
3.1 General Settings in EWM
3.1.1 Defining Business Systems

You can use this procedure to name the business system and all systems that are part of the system landscape.
Procedure
Carry out the following steps in your EWM customizing client:
1. In Customizing for Extended Warehouse Management, choose Interfaces → GTS Integration → Define
Business System.
2. Create a new entry for each system that is part of your system landscape and enter the following data:
Field Value
Business System GTS_001
Logical system GTSCLNT001
Manual Maint. ‘ ’ – Flag is Not Set
3. Save the changes.
3.1.2 Defining the Customs ID

You can use this procedure to define the customs ID for the customs warehousing procedure.
General Setup © 2022 SAP AG or an SAP affiliate company. All rights reserved. 12
Procedure
Customs ID.
2. Create a new entry and enter the following data:
Field Value
Customs ID GTS1
Description GTS1 for GTS Client 001
Note
The customs ID that you define here must be the same as the customs ID that is defined in the GTS
system.
3.1.3 Warehouse-Specific Settings

The settings described in this section are specific to one EWM warehouse. It means, that these settings can be
different from one warehouse to another. If you are setting up multiple warehouses, repeat the steps for all
warehouses.
3.1.3.1 Assigning the Business System

You can use this procedure to assign the GTS business system to the relevant warehouse number.
Procedure
GTS System for Warehouse Number.
2. Choose your warehouse number and enter the corresponding GTS business system (for example
GTS_001).
3. You can also enter a Warehouse Process Type for releasing customs blocked stock (optional).
3.1.3.2 Assigning the Customs ID

You can use this procedure to assign the customs ID to your warehouse and the partner or organization that is
entitled to dispose of stock in that warehouse.
Procedure
1. In EWM, on the SAP Easy Access Screen, choose Logistics → SCM Extended Warehouse Management →
Extended Warehouse Management → Settings → Assign Warehouse Number/Party Authorized to
Customs ID or start the transaction /SCWM/GTSMAPWH.
2. Choose your warehouse number and press Enter.
3. Enter the disposal party and the customs ID.
3.1.3.3 Assigning the Sales Organization
You can use this procedure to assign a sales organization to a warehouse number.
Note
This procedure is available only in a decentralized EWM. In an embedded EWM system it is not
necessary to maintain such an assignment.
Important
In some releases, the mentioned Customizing entry can’t be reached. For further information see
SAP Note 3070704.
Procedure
1. In Customizing for Extended Warehouse Management, choose Interfaces → GTS Integration → GTS
Integration for Decentralized EWM → Assign Sales Organization to Warehouse Number.
2. Choose your warehouse number and press Enter.
3. Enter the sales organization.
3.2 General Settings in GTS
3.2.1 Defining the Organizational Structure

To handle foreign trade processes with the GTS system, you need an organizational structure that consists of
foreign trade organizational units and legal units. The foreign trade organization represents the upper hierarchy
level, while the legal unit represents the lower level. You must define this organizational structure for GTS. The
structure that you define has to comply with the legal and customs requirements to allow execution of your
import and export processes. You assign one or more legal units to a foreign trade organizational unit. Note that
while you can assign one or more legal units to a foreign trade organizational unit, you can only assign each legal
unit to a single foreign trade organizational unit. You always define organizational units as business partners in the
GTS system.
The handling of import and export processes is based on data in your logistics feeder systems. The organizational
structure - consisting of foreign trade organizational unit and legal units - enables you to map the organizational
structures in your feeder system and, by assigning the two organizational structures, transfer the necessary data
from the feeder system. You need both master data and transaction data in your GTS system. If the system can’t
determine this assignment in the GTS system when transferring master data or documents from the feeder
system to the GTS system, you can’t perform the desired foreign trade processes.
The monitoring functions in the GTS system are based on foreign trade organizations and legal units. If you use
ERP as a feeder system, for example, you can assign company codes to foreign trade organizations and assign
plants (or combinations of plants and storage locations) to legal units. If the foreign trade organization represents
several company codes, you can assign several company codes to this foreign trade organization. However, you
can only assign a company code to one foreign trade organization. The same applies to the assignment of plants
or plant/storage location combinations to legal units.
In addition to the organizational units that legally represent your company to the authorities, you define the
organizational units for handling specific foreign trade units in your organizational structure. These include the
customs IDs for processing customs procedures with economic impact to identify specific or virtual premises for
which you have received authorization from the customs authorities to store and/or process the products for
these procedures. The organizational structure also defines the organizational units for which you explode and
evaluate bills of material. You use these bills of material, for example, for handling re-exports in legal control, as
well as in preference processing.
Procedure
Set up foreign trade organizations via the following activities:
1. Define foreign trade organizations
2. Transport foreign trade organizations to subsequent systems
3. Assign organizational units (company codes) from feeder systems
4. Set up legal units and assign them to foreign trade organizations
We recommend creating one legal unit for each plant and assigning only one plant to each legal unit. To set up the
legal units, perform the following activities:
1. Define legal units
2. Transport legal units to subsequent systems
3. Assign organizational units (plants or plant/storage location combinations) from feeder systems
If you have defined several feeder systems as a group with the same organizational structure, you can map your
organizational structure and data to the GTS system at feeder system group level.
To configure the additional organizational units, you must configure customs IDs. To enable the use of customs
IDs, you have to perform the following steps in the GTS system:
1. Define customs IDs
2. Assign the customs IDs to the organizational units at your company
3. Activate the customs IDs technically
3.2.1.1 Defining and Assigning Legal Units

A legal unit represents a subunit within your company. To integrate the foreign trade processes with the logistics
processes in feeder systems, the legal unit in GTS reflects a logistics unit in your feeder systems. Legal units are
used as presentation sites, for example, or other authorized locations of goods within GTS. Moreover,
authorizations, import licenses, and export licenses must always be available for the entire premises of a legal
unit.
The legal unit is the lower of the two hierarchy levels in the GTS organizational structure. You define the legal unit
in business partner maintenance: you create a new business partner and assign the role of legal unit. The system
uses the business partner address of a legal unit to determine specific values in the application. In SAP Customs
Management, for example, the system uses the country of the legal unit to determine the country of departure for
exports and the country of destination for imports.
If you use the Preference Processing service, a plant represents the lowest hierarchy level of the organizational
structure. Each plant in Preference Processing represents a plant in the feeder system, for which you want to use
the aggregation of long-term vendor declarations or preference determination. Therefore, first create a legal unit
for each of these plants and then, in a subsequent step, assign the plants in the feeder system to the
corresponding legal units.
Procedure
Carry out the following steps in your GTS system. Make sure that you assign each legal unit to only one foreign
trade organization:
1. In Customizing for SAP Global Trade Services, choose General Settings → Organizational Structure →
Define Legal Units.
2. Choose Organization to maintain legal units as organizations with the role “Legal Unit” (SLLSIT).
3. Assign your legal units to the relevant foreign trade organization by choosing General Settings →
Organizational Structure → Assign Legal Unit to the Foreign Trade Organization.
3.2.1.2 Assigning Plants from the Feeder System to Legal

Units
To enable the data transfer between GTS and the feeder systems, you have to assign the appropriate plant in the
feeder system to the legal unit in SAP GTS.
You can assign plants to legal units at two levels:
• Feeder system level
If only one feeder system exists, or if several feeder systems have different organizational structures, you
can assign the plants at feeder system level.
• Feeder system group level
If several feeder systems have the same organizational structure, you can assign the plants at feeder
system group level.
If the system cannot determine an organizational unit in GTS when a document is posted in the feeder system,
you can’t perform any further actions on that document.
Procedure
Carry out the following steps in your GTS system:
Assignment of Organizational Units from Feeder System to Legal Unit.
2. You can assign plants either at the feeder system or feeder system group level.
3. You can assign plants either manually or with automatic transfer.
3.2.1.3 Defining Foreign Trade Organizational Units

The foreign trade organizational unit represents you company as the legal person to the authorities. To enable
integration between your foreign trade processes with the logistics processes in feeder systems, the foreign trade
organization in the GTS represents the independent financial unit in your feeder systems. Accordingly, the foreign
trade organizational unit models the organizational unit at your company that has its own VAT registration
number. Within the GTS system, the foreign trade organizational unit acts as the authorization owner, for
example, and the applicant for import and export licenses, securities, and CAP licenses.
The foreign trade organizational unit is the higher level of the two hierarchy levels for the organizational structure
in the GTS system. You define the foreign trade organizational unit in business partner maintenance: Create a new
business partner and assign the corresponding role for the foreign trade organization. When doing so, you must
make sure that you assign the foreign trade organization to only one country. The system uses the country key for
the foreign trade organization business partner for the specific determination routines in the application. In the
Customs Management, for example, the system uses the country of a foreign trade organizational unit to find the
legal regulation for the processes. You also model the customs representatives within a corporate structure, for
example, at the level of the foreign trade organizational unit.
After you define the foreign trade organizational unit, you assign it to the corresponding unit in the feeder system
(or group of feeder systems) in a subsequent step. Therefore, you must define at least one foreign trade
organizational unit to represent your company and comply with statutory requirements and customs regulations.
The administrative unit represents the highest hierarchy level in the organizational structure for preference
processing. The administrative unit and the foreign trade organization can be identical, however. Therefore, check
whether the requirements for an administrative unit match those of your foreign trade organizational unit, and if
they do, assign the role for the administrative unit to your foreign trade organizational unit as well.
Procedure
Assignment of Organizational Units from Feeder System to Foreign Trade Org.
2. The Maintain Business Partner screen appears.
3. Choose Organization to create your foreign trade organizational unit as a business partner with role
Foreign Trade Org. (SLLFTO).
3.2.1.4 Assigning Partner Numbers to the Foreign Trade

Organization
To enable the data transfer between GTS and the feeder systems, you have to assign the appropriate
organizational unit in the feeder system to the foreign trade organizational unit in GTS. The mapping between
partner numbers in the feeder system and the foreign trade organizations in GTS is available for the generic
assignment of these units.
You can assign partner numbers to foreign trade organizations at two levels:
• Feeder system level
If only one feeder system exists, or if several feeder systems have different organizational structures, you
can assign the partner numbers at feeder system level.
• Feeder system group level
If several feeder systems have the same organizational structure, you can assign the partner numbers at
feeder system group level.
If the system cannot determine an organizational unit in GTS when a document is posted in the feeder system,
you can’t perform any further actions on that document.
Procedure
Assignment of Organizational Units from Feeder System to Foreign Trade Org.
2. Choose Assign Partner Number at Feeder System Level.
a. Choose New Entries.
b. Select the feeder system in the Logical system field and assign a business partner role.
c. Choose Partner Number Mapping to assign a logical system to a business partner.
d. Choose New Entries.
e. Enter an external business partner number in the feeder system and the foreign trade
organization to which you want to map the business partner data in GTS.
f. Save your entries.
3. Choose Assign Partner Number at Feeder System Group Level.
a. Choose New Entries.
b. Select a logical system from your group of feeder systems and assign a business partner role.
c. Choose Partner Number Mapping to assign a logical system group to a business partner.
d. Choose New Entries.
e. Enter an external business partner number and the foreign trade organization to which you want
to map the business partner data in GTS.
f. Save your entries.
3.2.1.5 Defining the Customs ID

A customs ID is a key that you use to flag products that require customs procedures with economic impact. You
must assign a customs ID to a product to assign the additional, more specific attributes for the customs
procedures with economic impact. These attributes include relevance indicators for inward processing and
customs warehousing, for example.
The customs ID also serves as a reference to a repository at your company where you store the products that are
part of a customs procedure with economic impact. If products are present that must be handled using these
special customs procedures, they are subject to separate monitoring by the customs procedures, which you can
carry out based on the customs ID.
Note
If you store products for customs procedures with economic impact at different locations –
because you have several customs warehouses, for example – you must create a separate ID for
each such repository. Note that you need a separate authorization for each customs warehouse,
and therefore for each defined customs ID.
Procedure
Define Customs ID for Customs Procedures with Economic Impact.
2. Enter a customs ID and a description.
3.2.1.6 Assigning the Customs ID

You define the same customs IDs in your feeder system as in your system for GTS. You assign the special storage
locations for customs procedures with economic impact in both systems. Since you have also assigned all the
storage locations to a company code, the organizational data is replicated through the transfer of master data to
the GTS system and the assignment of foreign trade organizations (company code) and legal units (such as
storage locations).
Therefore, to uniquely identify your storage locations for products in customs procedures with economic impact,
you assign the customs ID to a foreign trade organization and a group of logical systems.
Procedure
Control Customs ID for Customs Procedures with Economic Impact.
Field Value
Customs ID GTS1
Logical System Group EWMERPGTS
Foreign Trade Organization FTO_001
3.2.2 Transfering Material and Business Partner Master Data

The processes in the EWM-GTS integration are based on the master data from the ERP system. This master data
– including business partners and materials – must be transferred to the GTS system. For detailed information,
see the SAP Help Portal page for SAP Global Trade Services at http://help.sap.com/gts. In the Application Help,
choose System Administration for SAP Global Trade Services → Data Transfer from the Feeder System.
4 EWM Process Setup
4.1 Customizing the Outbound Process
You use this procedure to configure your EWM system to process export outbound deliveries.
Prerequisites
You must define outbound delivery document and item types in the ERP system that will be used in the outbound
process. They can be existing types or new types.
4.1.1 Adjusting Status Profiles for Item Types

To control whether export outbound deliveries are checked by GTS, you have to activate the GTS Check (DGT)
status in the status profiles used for the outbound delivery item types. This status is not activated in the standard
profiles (for example in /SCDL/OUT_PRD_DLV_STANDARD). To run the check for export outbound deliveries
only, there are two options:
1. You create new status profiles as a copy in which the DGT status is activated.
2. You change the settings for the existing profiles.
In this procedure (and in all other procedures) the second option is described.
Procedure
1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings → Delivery –
Warehouse Request→ Status Management → Define Status Profiles.
2. Choose the appropriate status profile as follows:
a. For standard outbound delivery items, choose /SCDL/OUT_PRD_DLV_STANDARD, for
example
b. For direct outbound delivery items, choose /SCDL/OUT_PRD_DLV_DIRECT, for example
3. On the Status Types screen for each profile, activate the DGT status (deselect the Inactive checkbox).
4. Save the status profiles.
4.1.2 Adjusting Status Profiles for Document Types

To enable the transit procedure and full control of delivery splits based on legal requirements for export outbound
deliveries, you have to activate the Transit Procedure (DWN) and Delivery Split Restricted (DSR) statuses in the
status profiles used for the outbound delivery document types. These statuses are not activated in the standard
profiles.
Procedure
2. Choose the appropriate status profile as follows:
a. For standard outbound delivery documents, choose /SCDL/OUT_PRD_STANDARD, for
example
b. For direct outbound delivery documents, choose /SCDL/OUT_PRD_DIRECT, for example
3. On the Status Types screen for each profile, activate the DWN and / or DSR statuses (deselect the
Inactive checkbox).
EWM Process Setup © 2022 SAP AG or an SAP affiliate company. All rights reserved. 19
4.1.3 Adjusting Action Profiles
To control whether export outbound deliveries are checked by GTS, you must activate the corresponding Post-
Processing Framework (PPF) actions in the action profiles used by the outbound delivery documents.
Procedure
Warehouse Request→ Actions → Change Actions and Conditions → Define Action Profiles and Actions.
2. Select the Action Profile that is used in your outbound delivery order document type (for example
/SCWM/PDO_01) and choose Action Definition in the dialog structure on the left side.
3. Activate the following action definitions by removing the Inactive checkbox:
a. /SCWM/PDO_01_GTS_CHECK
b. /SCWM/PDO_01_GTS_DOC_DELETE
4. Go back, select the Action Profile that is used in your outbound delivery document type (for
example/SCWM/FDO_01), and choose Action Definition in the dialog structure on the left side.
5. Activate the following action definition by deselecting the Inactive checkbox:
a. /SCWM/FDO_01_GTS_DOC_DELETE
6. Save your changes.
Important
This procedure must be repeated after each release upgrade.
4.1.4 Defining Item Types

You can use this procedure to create outbound delivery item types for export orders and assign the status profiles
adjusted in the previous steps to the item types.
Procedure
1. In Customizing for Extended Warehouse Management, choose Goods Issue Process → Outbound
Delivery → Define Item Types for Outbound Delivery Process.
2. Create new entries by copying the following existing entries and changing the item type, for example, to
ZGTS or ZGTD:
Existing Entries New Entries
Item Type Doc. Cat. Item Cat. Item Type Doc. Cat. Item Cat.
ODLV FDO DLV ZGTS FDO DLV
ODLV ODR DLV ZGTS ODR DLV
ODLV PDO DLV ZGTS PDO DLV
ODSH FDO DLV ZGTD FDO DLV
ODSH PDO DLV ZGTD PDO DLV
3. Make sure, that the adjusted status profiles from step 4.1.1 are used in your item type.
4.1.5 Defining Document Types
You can use this procedure to create outbound delivery document types for export orders and make the
necessary settings for them.
Procedure
Delivery → Define Document Types for Outbound Delivery Process.
2. Create new entries by copying the following existing entries and changing the document type, for
example, to ZGTS or ZGTD:
Doc. Type Doc. Cat. Doc. Type Doc. Cat.
OUTB FDO ZGTS FDO
OUTB ODR ZGTS ODR
OUTB PDO ZGTS PDO
ODSH FDO ZGTD FDO
ODSH PDO ZGTD PDO
3. Make sure, that the adjusted status and action profiles from step 4.1.2 and 4.1.3 are used in your
document type.
4. Change the following settings in the entries:

Doc.
Doc. Cat. Legal Control GTS No TCD GTS Check
Type
ZGTS PDO X if necessary
ZGTD PDO X If necessary
4.1.6 Defining Allowed Item Types

You can use this procedure to assign the item types to the document types that were created in the previous
steps. This enables you to use the item and document types in the outbound delivery process.
Procedure
Delivery → Define Allowed Item Types in Outbound Delivery Process.
2. Create new entries and enter the following entries:
Doc. Type Item Type
ZGTS ZGTS
ZGTD ZGTD
4.1.7 Mapping Document Types from an ERP System
You can use this procedure to map the export delivery document types that you are using in you ERP system to
the types you defined in the previous steps.
Procedure
1. In Customizing for Extended Warehouse Management, choose Interfaces → ERP Integration → Delivery
Processing → Map Document Types from ERP System to EWM.
Field Example data
Business
ERP_001
System
DocTypeERP ZGTS
Doc. Type ZGTS
4.1.8 Mapping Item Types from an ERP System

You can use this procedure to map the export delivery item types that you are using in your ERP system to the
types you defined in the previous steps.
Procedure
Processing → Map Item Types from ERP System to EWM.
Field Example data
Business
ERP_001
System
DocTypeERP ZGTS
ItmTpERP ZGTS
Doc. Type ZGTS
Item Type ZGTS
4.1.9 Mapping Date Types from an ERP System

You can use this procedure to map date types to your newly created document type.
Procedure
Processing → Map Date Types from ERP System to EWM.
Field Example data
Business
ERP_001
System
DTypeERP WSHDRLFDAT
Doc. Type ZGTS
End Date TDELIVERY
Space (Do Not Confirm

Conf. D/T
Date/Time)
4.1.10 Determining Warehouse Process Types

You can use this procedure to define the warehouse process types to your newly created document types.
Procedure
1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings → Warehouse
Task → Determine Warehouse Process Type.
2. Search for entries in your warehouse where the document type is OUTB.
3. Copy all entries and set the document type to ZGTS.
4.2 Customizing the Outbound Process in the Advanced

Shipping and Receiving Scenario
You use this procedure to configure the GTS integration in your EWM system together with the Advanced
Shipping and Receiving processes. From a GTS integration point of view, the Transportation Management (TM)
system is the leading application. EWM can’t directly communicate with GTS.
Important
The Advanced Shipping and Receiving functionalities with GTS integration are available with SAP
S/4HANA 2021 or higher only.
Prerequisites
To customize the Advanced Shipping and Receiving processes, please refer to the guide in SAP Note 3225241.
4.2.1 Adjusting Document Types

You can use this procedure to adjust the corresponding outbound delivery order and outbound delivery document
type.
Procedure
Delivery → Define Document Types for Outbound Delivery Process.
2. Choose the corresponding outbound delivery order document type, and change the following settings in
the entry:
Doc.
Doc. Cat. Description Legal Control GTS No TCD GTS Check
Type
Outbound Delivery
OFO PDO Order w/ Freight X if necessary
Order
3. Choose the corresponding outbound delivery document type, and change the following settings in the
entry:
Doc.
Doc. Cat. Description Billing Req. Ty
Type
Outbound Delivery w/ A – Billing Document
OFO FDO
Freight Order Immediately
4.2.2 Adjusting Status Profiles for Document Types

To enable the process, you must activate the Blocked (Transp. Plan) (DBT) and Transport Planning (DTD)
statuses in the status profiles used for your outbound delivery order document type. In addition, you need to
activate the Invoice (DIN) status for your outbound delivery document type.
Procedure
2. Choose the required profile for outbound delivery order, the default is /SCWM/OUT_PRD_FO.
3. On the Status Types screen for the profile, activate the DBT and DTD statuses (deselect the Inactive
checkbox).
4. Choose the required profile for outbound delivery, the default is /SCWM/OUT_FD_FO.
5. On the Status Types screen for the profile, activate the DIN status (deselect the Inactive checkbox).
4.2.3 Adjusting Status Profiles for Item Types

To enable the storage and display of GTS compliance status values in the outbound delivery items, you must
activate the GTS Check statuses in the status profiles used for the outbound delivery order item types.
Procedure
2. Choose the required profile, the default is /SCWM/OUT_PRD_DLV_FO.
3. On the Status Types screen for each profile, activate the following statuses (deselect the Inactive
checkbox):
a. DBT - Blocked (Transp. Plan)
b. DGT - GTS Check
c. DGE - GTS (Embargo)
d. DGL - GTS (LegCtrl)
e. DGS - GTS (SPLScrn)
4. Save the status profile.
4.2.4 Adjusting Header Process Profiles

In the Advanced Shipping and Receiving process together with the GTS integration, the Invoice Before Goods
Issue process is mandatory for EWM outbound deliveries. To enable this functionality, you must activate it for
your outbound delivery order and outbound delivery document types.
Procedure
Warehouse Request → Process Management and Control → Define Process Profile for Document
Header.
2. Choose the required profiles and set the following value:
Process Profile Invoice Before Goods Issue
/SCWM/OUT_PRD_FO A – Only for Export
/SCWM/OUT_FD_FO A – Only for Export
4.3 Customizing the Inbound Process

You use this procedure to configure your EWM system to process inbound deliveries that are relevant for the
transit procedure and temporary storage.
Prerequisites
In the inbound process in EWM, you must reuse the same previous document types that are defined in the ERP
system. See chapter 4.3.2 Defining Previous Document Types.
4.3.1 Defining Stock Types

You can use this procedure to define new stock types to enable the handling of customs blocked stock in the EWM
system.
Procedure
1. In Customizing for Extended Warehouse Management, choose Master Data → Product → Define Stock
Types.
2. Create new entries and enter the following data for your warehouse:
Description of Availability Location- Role
Stock Type Stock Type Group Independent
Stock Type
Customs - Free 001 FF C – Customs
C1 in Putaway Blocked
Stock
Customs - 002 FF C – Customs
C2 Unrstrctd-Use Blocked
Ptaway Stock
Customs - 001 QQ C – Customs
C3 Quality in Blocked
Putaway Stock
Customs - 002 QQ C – Customs
C4 Quality in Blocked
Warehouse Stock
Customs - 001 BB C – Customs
C5 Blocked in Blocked
Putaway Stock
Customs - 002 BB C – Customs
C6 Blocked in Blocked
Warehouse Stock
Customs - 001 RR C – Customs
C7 Returns in Blocked
Putaway Stock
Customs - 002 RR C – Customs
C8 Returns in Blocked
Warehouse Stock
4.3.2 Defining Previous Document Types

You can use this procedure to define previous document types for the relevant warehouse. This enables customs
procedures to be processed in the warehouse.
Procedure
Previous Document Types.
2. Create new entries and enter the following data for your warehouse:
Previous Document Transit Procedure
Description Customs Block
Type Relevance
ATB ATB X -
T- T- X X
T1 T1 X X
T2 T2 - X
T2F T2F - X
4.3.3 Mapping Previous Document Types

You can use this procedure to map previous document types in EWM to the corresponding previous document
types in GTS.
Procedure
1. In Customizing for Extended Warehouse Management, choose Interfaces → GTS Integration → Map
Previous Document Types Between EWM and External Systems.
2. Create new entries and enter the following data:
EWM Prev. Document Ext. Prev.
Type Document Type
ATB ATB
T- T-
T1 T1
T2 T2
T2F T2F
4.3.4 Defining Reference Document Categories

You can use this procedure to check if the required reference document categories have been created.
Procedure
Warehouse Request → Reference Documents → Define Reference Document Categories.
2. Create new entries and enter the following data:
Document Category Description
ATB Customs Previous Doc. Type: Duty Unpaid
T- Customs Previous Doc. Type: Duty Unpaid
T1 Customs Previous Doc. Type: Duty Unpaid
T2 Customs Previous Doc. Type: Duty Paid
T2F Customs Previous Doc. Type: Duty Paid
4.3.5 Adjusting Reference Document Type Profiles

You can use this procedure to add the previously created reference document categories to the reference
document profile that you are using in your inbound delivery document type.
Procedure
Warehouse Request → Reference Documents → Define Reference Document Type Profiles.
2. Select the customer profile that you are using for your inbound delivery document type, for example
/SCWM/INB_PRD, and in the dialog structure double-click on Reference Document Categories on the
left hand side.
3. Activate the following entries by deselecting the Inactive checkbox:
Document Category
ATB
T-
T1
T2
T2F
4.3.6 Adjusting Status Profiles

To enable the transit procedure for inbound deliveries, you must activate the Transit Procedure (DWN) status in
the status profile used for the inbound delivery document type. This status is not activated in the standard profiles
(for example /SCDL/INB_PRD_ STANDARD).
Procedure
2. Select the status profile that you are using for your inbound delivery document type, for example
/SCDL/INB_PRD_STANDARD.
3. On the Status Types screen for the profile, activate the DWN status (deselect the Inactive checkbox).
4.3.7 Adjusting Action Profiles

To run the transit procedure for your inbound deliveries, you must activate the corresponding Post-Processing
Framework (PPF) action in the action profile used by the inbound delivery documents.
Procedure
Warehouse Request→ Actions → Change Actions and Conditions → Define Action Profiles and Actions.
2. Select the action profile that is used in your outbound delivery order document type (for example
/SCWM/PDI_01) and choose Action Definition on the dialog structure on the left side.
3. Activate the following action definition by deselecting the Inactive checkbox:
a. /SCWM/PDO_01_NCTS_NEW.
Important
This procedure must be repeated after each release upgrade.
4.4 Customizing the Inbound Process in the Advanced
Shipping and Receiving Scenario
You use this procedure to configure the GTS integration in your EWM system together with the Advanced
Shipping and Receiving processes. From a GTS integration point of view, the Transportation Management (TM)
system is the leading application. EWM can’t directly communicate with the GTS system.
Important
Advanced Shipping and Receiving functionalities with GTS Integration are available with SAP
Prerequisites
To customize the Advanced Shipping and Receiving processes, please refer to the guide in SAP Note 3225241.
To enable the correction process in the Advanced Shipping and Receiving scenario, you must activate the BC set
/SCWM/DLV_CORRECTION.

To enable the correction process in Advanced Shipping and Receiving, you must activate the following statuses in
the status profile used for the correction inbound delivery document and item type.
Procedure
2. Choose the corresponding status profile for the correction inbound delivery document, the default is
/SCWM/INB_PRD_IDIS.
3. On the Status Types screen for the profile, activate the following statuses (deselect the Inactive
checkbox):
a. DBT - Blocked (Transp. Plan)
b. DTD - Transport Planning
c. DTR - Transit Status.
4. Choose the corresponding status profile for the correction inbound delivery item, the default is
/SCWM/INB_PRD_DLV_IDIS.
5. On the Status Types screen for the profile, activate the following status (deselect the Inactive checkbox):
a. DBT - Blocked (Transp. Plan).
4.4.2 Adjusting Date/Time Profiles

To enable the correction process in Advanced Shipping and Receiving, you must activate the date type Arrival in
Yard (TINYARD) in the date/time profile used for the correction inbound delivery document type.
Procedure
Warehouse Request → Dates/Times → Define Date Profiles.
2. Choose the corresponding date/time profile for the correction inbound delivery document, the default is
/SCWM/INB_PRD_FO.
3. On the Date/Time Types screen for the profile, activate the TINYARD type (deselect the Inactive
checkbox).
4. Save the date/time profile.
4.4.3 Defining Item Types for the Correction Process

You can use this procedure to create inbound delivery item type for the correction process.
Procedure
1. In Customizing for Extended Warehouse Management, choose Goods Receipt Process → Inbound
Delivery → Define Item Types for Inbound Delivery Process.
2. Create a new entry by copying the following existing entry and changing the item type, for example, to
ZIDS:
Item Type Doc. Cat. Item Cat. Item Type Doc. Cat. Item Cat.
IDIS PDI DLV ZIDS PDI DLV
4.4.4 Defining Document Types for the Correction Process

You can use this procedure to create an inbound delivery document type for the correction process and make the
necessary settings for the newly created type.
Procedure
Delivery → Define Document Types for Inbound Delivery Process.
2. Create a new entry by copying the following existing entry and changing the document type to ZIDS:
Doc. Type Doc. Cat. Doc. Type Doc. Cat.
IDIS PDI ZIDS PDI

4. Check and change the profile settings in the entry:
Doc. Type Doc. Cat. Date Profile RefDocCat Profile
ZIDS PDI /SCWM/INB_PRD_FO /SCWM/INB_PRD_FO
4.4.5 Defining Allowed Item Types

You can use this procedure to assign the item types to document types that were created in the previous steps.
This enables you to use the item and document types in the inbound delivery process.
Procedure
Delivery → Define Allowed Item Types in Inbound Delivery Process.
2. Create new entries and enter the following entries:
Doc. Type Item Type
ZIDS ZIDS
4.4.6 Mapping Document Types from an ERP System

You can use this procedure to map the correction inbound delivery document type that you are using in your ERP
system to the type you defined in the previous steps.
Procedure
Processing → Map Document Types from ERP System to EWM.
Field Example data
Business System ERP_001
DocTypeERP EL
Cde. Init. Com. DIS
Doc. Type ZIDS
4.4.7 Mapping Item Types from an ERP System

You can use this procedure to map the export delivery item types that you are using in you ERP system to the
types you defined in the previous steps.
Procedure
Processing → Map Item Types from ERP System to EWM.
Field Example data
Business
ERP_001
System
DocTypeERP EL
ItmTpERP ELN
Doc. Type ZIDS
Item Type ZIDS
4.4.8 Mapping Date Types from an ERP System

You can use this procedure to map date types to your newly created document types.
Procedure
Processing → Map Date Types from ERP System to EWM.
Field Example data
Business
ERP_001
System
DTypeERP WSHDRLFDAT
Doc. Type ZIDS
End Date TDELIVERY
Space (Do Not Confirm

Conf. D/T
Date/Time)
4.5 Customizing the Scrapping Process

You use this procedure to configure your EWM system to process scrapping with posting change documents in a
customs warehouse scenario.
4.5.1 Configuring Message Processing

You use this procedure to define the parameters for sending handling unit information back to ERP from EWM
during the processing of posting changes.
Procedure
Processing → Control Message Processing Dependent on Recipient.
2. Ensure that the following entries exist, or create them if necessary:
DocTypeERP HU Parameter
TSCA Report HU Data
TSCK Report HU Data
TSCR Report HU Data
For a scrapping scenario with a customs warehouse, the Scrapping Customs (DWS) status must be active in the
relevant status profile. You use this procedure to adjust the corresponding status profile for posting changes in a
scrapping scenario.
Procedure
2. Choose the status profile that is used in your posting change item type, for example
/SCWM/INT_SPC_DLV_STANDARD.
3. On the Status Types screen for the profile, activate the DWS status (deselect the Inactive checkbox).
5 Process Descriptions
5.1 Outbound Process Compliance Checks
In the outbound process, EWM uses the compliance checks from GTS to check whether an outbound delivery can
be delivered to a certain goods recipient.
Procedure
1. In ERP, create a sales order with the corresponding (GTS-relevant) order type.
Note that an order reference is a must in the process. Without an order reference, the items will not be
relevant for compliance checks later on.
2. Create an outbound delivery based on your sales order and distribute it to EWM.
3. In EWM, a compliance check to GTS is called when the delivery is created. This is done on item level, and
only the relevant items are checked. Subitems are not relevant for the checks. The item level GTS Check
(DGT) status is changed:
a. For the relevant item, it is set to “In Progress” (2)
b. For the items that are not relevant, it is set to “Not Relevant” (0)
4. Based on the result of the check, the delivery items (and therefore the complete delivery) can be blocked
or unblocked. The DGT status on item level shows the result of the check:
a. For blocked items, it is set to “GTS Check, Not OK” (8)
b. For the items that are not blocked, t is set to “GTS Check, OK” (9)
c. In case of technical issues during the check, it is set to “Technical Errors” (5)
5. If DGT is set to “GTS Check, Not OK” or “Technical Errors”, the item level status Blocked (Inconsist. Item)
(DBD) is set to “Yes” (X), which implies that the header level DBD status is also set to the same value.
This implies also that the header level status Blocked (Overall Status) (DBO) is set to “Yes” (X).
6. If the outbound delivery order is blocked, it is not allowed to:
a. Create any warehouse task in the putaway process
b. Load (simple or complex loading)
c. Create an outbound delivery or post goods issue
7. Already created warehouse tasks can be confirmed.
8. During the outbound process, a new GTS check is called, if:
a. It is manually triggered. You can trigger a GTS check by highlighting the relevant items and then
choosing the button GTS => Recheck GTS Lock
b. The following attributes are changed in the delivery header:
i. Ship-to party or its address
ii. Carrier or its address
iii. Planned out-of-yard date
c. An item is created or deleted
d. The following attributes are changed in a delivery item:
i. Item quantity
ii. Catch weight quantity
iii. Product
e. The compliance check status in GTS has been changed and a notification is sent to EWM, which
also triggers a new check
f. There is always a new check at the time of outbound delivery creation and at the time of goods
issue posting.
9. In case of necessary authorization, the GTS Check status can be released manually. You can trigger the
manual release by highlighting the relevant items, and then choosing the button GTS => Release GTS
Lock. After this action, the item level DGT status is set to the value “Manually Released” (6). With this
status, no further checks are possible.
Important
The date compliance check triggered by date changes mentioned in step 8/b/iii and the push
notification functionality mentioned in step 8/e above are available only with SAP S/4HANA 2020
release 2020 or higher. For further information see SAP Note 299396.
Process Descriptions © 2022 SAP AG or an SAP affiliate company. All rights reserved. 34
5.2 Outbound Process Transit Procedure
You can subject complete outbound deliveries that are transit-procedure-relevant to a transit procedure. In doing
so, you can ensure that the customs authority issues a loading permission for the vehicles with the goods to be
delivered to the goods recipient.
Procedure
1. For an outbound delivery order, you can manually define if this delivery is relevant for Transit Procedure,
or not. By default, the outbound deliveries are not relevant for this process. To enable it for certain
deliveries, you have to implement the corresponding BAdI /SCWM/SHP_PROC_REL_SET.
2. If the delivery is relevant for the transit procedure, you can manually change the delivery to indicate that
the customs authority is informed. You can set header level Transit Procedure (DWN) status value to
“For Checking” (1). To do so, choose the header level button Transit Procedure => Set status to “Check”.
3. This step blocks the delivery, and in this status, it is not allowed to:
a. Create any warehouse task in the picking process
b. Load (simple or complex loading)
c. Create outbound delivery or post Goods Issue
4. Already created warehouse tasks can be confirmed.
5. If the customs authority allows the loading, you can manually release the lock. To do so, choose the
header level button Transit Procedure => Set status to “Release”. This sets the DWN status to the value
“Released” (9).
6. If the customs authority doesn’t allow the loading, you can manually set it on the delivery to postpone the
processing. To do so, choose the header level button Transit Procedure => Set status to “Blocked for
Customs”. This sets the DWN status to the value “Customs Insp.” (8).
5.3 Outbound Process in Advanced Shipping and Receiving

The outbound compliance check process works also in the Advanced Shipping and Receiving
scenario, with the following limitations and extensions:
1. In EWM, the outbound delivery order can be relevant for GTS checks based on Customizing, but EWM is
not allowed to call any GTS checks directly. Therefore, it is not allowed to manually recheck or release
checks.
2. The compliance check results can be received from the ERP system at the time of the delivery
distribution and creation in EWM. Further status updates can be received from the Transportation
Management (TM) system.
3. The status GTS Check (DGT) is still valid and available for delivery items, and it still controls the delivery
item blocks as in the normal process described in 5.1. The following status values are possible:
a. “Not Relevant” (0)
b. “In Progress” (2)
c. “GTS Check, Not OK” (8)
d. “GTS Check, OK” (9)
4. Beside the DGT status, there are 3 new statuses defined that show more precise information about the
compliance situation. These statuses have the same possible values as the DGT status:
a. GTS Check (Embargo) (DGE) – Embargo check
b. GTS Check (Legal Control) (DGL) – Legal Control check
c. GTS Check (SPL Screen) (DGS) – Sanction Party List check
5. The transit procedure is currently not supported together in the Advanced Shipping and Receiving
process.
Important
The Advanced Shipping and Receiving functionalities with GTS integration are available from SAP
5.4 Inbound Process Transit Procedure
You can subject complete inbound deliveries that are transit-procedure-relevant to a transit procedure. In doing
so, you can ensure that the customs authority issues an unloading permission for the vehicles with the goods to
be delivered.
Procedure
1. In ERP, create a purchase order.
2. Create an inbound delivery and distribute it to EWM.
3. In EWM, the created inbound delivery will be relevant for the transit procedure, if:
a. The previous document number is maintained as a reference document in the inbound delivery
(it is either possible to maintain it in EWM manually, or to maintain it manually in ERP and
distribute it with the delivery)
b. The previous document type is relevant for the transit procedure, see chapter 4.3.2
c. The inbound delivery is in yard (you can set it manually or receive the information from ERP
during distribution)
4. If the delivery is relevant for the transit procedure, a message is sent to the GTS system. Meanwhile, the
header level Transit Procedure (DWN) status value is automatically set to “For Checking” (1). It blocks
the delivery, and in this status you can post Goods Receipt, but it is not allowed to:
a. Create any warehouse task in the putaway process
b. Unload (simple or complex unloading).
5. If the response from the GTS system allows the unloading, the lock is automatically released. This sets
the DWN status to the value “Released” (9).
6. If the response does not allow the unloading, the DWN status is set to the value “Customs Insp.” (8).
7. The transit procedure status can be released manually. You can trigger the manual release by
highlighting the relevant delivery and choosing the button Transit Procedure => Set status to “Release”.
After this action, the DWN status is set to the value “Released” (9).
8. The transit procedure status can be rechecked manually. You can trigger the recheck by highlighting the
relevant delivery and choosing the button Transit Procedure => Set status to “Check”. After this action,
the DWN status is set to the value “For Checking” (1). From this the process continues like described
from step 4.
5.5 Inbound Process Temporary Storage

You can use safekeeping (temporary storage) for inbound deliveries in delivery processing.
Procedure
1. In ERP, create a purchase order.
2. Create an inbound delivery and distribute it to EWM.
3. In EWM, the created inbound delivery will be relevant for safekeeping, if:
a. The previous document number is maintained as a reference document in the inbound delivery
(it is either possible to maintain it in EWM manually, or to maintain it manually in ERP and
distribute it with the delivery)
b. The previous document type is relevant for temporary storage, see chapter 4.3.2
c. Customs blocked stock types are configured, see chapter 4.3.1
4. If the delivery is relevant for the temporary storage, a communication is executed to the GTS system.
Meanwhile, the item level stock type information is set to one of the customs blocked stock types (C1 to
C8).
5. At the time of goods receipt posting, the stock is posted to one of these customs blocked stock types.
6. With these customs blocked stock types, it is possible to unload and put away the stock in the inbound
process and pick and load the stock in the outbound process.
7. Stock with one of these customs blocked stock types, can’t leave the warehouse (via scrapping or
posting goods issue).
8. At the end of the process, when GTS informs EWM that a stock is not in customs block anymore, a
posting change is executed for the stock, and it is posted to a normal stock type. The system searches
the corresponding stock in the warehouse in the following order:
a. Stock assigned to the inbound delivery
b. Stock not assigned to any deliveries
c. Stock assigned to an outbound delivery
9. You can track stock in handling units after putaway, in order to always release exact stock. For further
details see SAP Note 2460221.
10. You can monitor pending release requests from GTS system in transaction /SCWM/CBREL_MON.
5.6 Inbound Process in Advanced Shipping and Receiving
The inbound transit procedure process in EWM is not supported in the Advanced Shipping and Receiving
scenario, the functionality is covered by TM.
The inbound temporary storage process works in the Advanced Shipping and Receiving scenario, with the
following limitations:
1. There is no communication from EWM to GTS, the communication is covered by TM.
2. The previous document type and number is always received from ERP, it is not allowed to manually
maintain it in EWM.
3. If the previous document type is relevant for temporary storage, the stock type changes are working in
the same way as in the normal process, including the release of customs blocked stock from GTS.
Important
The Advanced Shipping and Receiving functionalities with GTS integration are available from SAP
5.7 Inbound Correction Process in Advanced Shipping and

Receiving
In the inbound process in the Advanced Shipping and Receiving scenario, it is possible to process overdelivery
situations. The correction process is relevant only if the overdelivery is recognized after the goods receipt posting
(it is even possible to handle it after the putaway process is finished).
Procedure
1. In TM, a new freight unit is created for the quantity deviation, and a new inbound delivery in ERP is
created with a correction flag. This inbound delivery is then distributed to EWM.
2. In EWM, a correction inbound delivery is created.
3. Goods receipt can be posted manually or automatically via a PPF action.
4. The received stock is posted as a difference, and it can be handled further in the Difference Analyzer.
5. The correction delivery is not relevant for unloading or putaway.
Important
The Advanced Shipping and Receiving functionalities with GTS integration are available with SAP
S/4HANA 2021 or higher.
5.8 Scrapping Process

If you use the customs warehousing procedure in EWM, only the scrapping process is affected. If you work with
warehouse requests of the posting change type for scrapping in the scrapping process in the customs warehouse,
GTS can apply to the customs authority for permission to scrap.
Procedure
A posting change delivery from ERP is distributed to EWM and a posting change request for scrapping is created.
If the product is relevant to customs warehousing, delivery processing requests a scrapping reference number
from SAP GTS.
1. In ERP, create a scrapping posting change delivery and distribute it to EWM
2. In EWM, the created posting change delivery will be relevant for the scrapping process. If the products on
the posting change items are relevant for customs warehousing, a communication to the GTS system is
executed. Meanwhile, the item level Scrapping Customs (DWS) status value is automatically set to “For
Inspection” (1). It blocks the delivery, and with this status, it is not allowed to post goods issue and
finalize the scrapping process.
3. If the response from the GTS system allows the scrapping, the lock is automatically released. This sets
the DWS status to the value “Released” (9). In addition, a new scrapping reference document is added to
the delivery header with type Reference Number – Scrap (SCR).
4. If the response does not allow the scrapping, the DWS status stays “For Inspection” (1).
Appendix
Appendix A – Additional Information about BAdIs
The following BAdIs in enhancement spot /SCWM/ES_GTS_INTEGRATION can be used in the GTS integration
during the implementation:
BAdI Definition Usage

With this extension, you can distinguish between the Route
/SCWM/EX_GTS_CHECK_AUTHORITY Release and GTS Release actions in authority checks. You can find
further information in SAP Note 1998492.
With this extension, you can define which outbound delivery order
/SCWM/IF_EX_GTS_CHECK_REL_SET
items are relevant for GTS compliance checks.
With this extension, you can define which inbound or outbound
/SCWM/SHP_PROC_REL_SET
deliveries are relevant for transit procedures.
Appendix B – List of SAP Notes Related to EWM-GTS

Integration
The following SAP Notes may help you with your implementation:
SAP Note Description / Comment System

Adv. SR in S/4HANA: GTS Integration - blocked EWM outbound delivery order
3141236 EWM
after late storage location assignment
3070704 IMG node 'Assign Sales Organization to Warehouse Number' is missing EWM
3038989 Transit procedure relevance in outbound delivery orders EWM
3033772 Short dump during displaying queue entries in /SCWM/MON EWM
3032428 Incorrect status update calls are not displayed in the inbound queue GTS
3016334 GTS - Recheck indicator update EWM
Enhancement of status synchronization between customs document and
3014396 GTS
EWM delivery
3002372 GTS check not triggered after changing main item with delivery split item EWM
Enhancement of compliance checks: Date changes and push messages from
2999396 EWM
GTS
2976134 GTS - /SCWM/GTS_CHECK_RELEVANCE_SET has no affect during PGI EWM
2955440 GTS lock after undoing delivery split EWM
2946789 GTS check triggered unnecessarily at deleting batch subitem EWM
2937784 Missing action /SCWM/OCTS_NEW EWM
2930131 BADI interface /SCWM/IF_EX_GTS_CHECK_REL_SET does not work EWM
2821830 Difference Analyzer can't post customs blocked stock EWM
2789007 Wave item clearing issuing item blocked due to GTS compliance check EWM
Appendix © 2022 SAP AG or an SAP affiliate company. All rights reserved. 39

Bonded scrap requests fail to update GTS, if no sufficient inventory in GTS -
2763189 EWM
missing error message
2756168 EWM business partner not recognized in GTS EWM
2750129 Sales organization information for GTS checks EWM
2725467 Error "ERP partner role &1 cannot be used" during GTS compliance check EWM
2722333 GTS locks after FD deletion EWM
2693640 Change of the address of ship-to party or carrier does not trigger GTS check EWM
2642299 Outbound deliveries are not replicated from EWM to GTS EWM
Fields GTS_VORPA and GTS_VORNU are not persisted in header of inbound
2475570 EWM
delivery
Extension of Customs Block Release search to handle /SCWM/HU_DLV
2460221 EWM
references
2415672 OCTS scenario with Customs Block Stock EWM
2411542 Release of Customs Blocked Stock fails for Nested HUs EWM
2377871 Item level partner information has not transferred to GTS EWM
2373448 Unable to release customs stock block with HUs EWM
Appendix © 2022 SAP AG or an SAP affiliate company. All rights reserved. 40

www.sap.com/contactsap
www.sdn.sap.com/irj/sdn/howtoguides
© 2022 SAP AG 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
AG. The information contained herein may be changed without
prior notice.
Some software products marketed by SAP AG and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The
only warranties for SAP Group 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 AG in Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.

HTG Gts Ewm Integration

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HTG Gts Ewm Integration

Uploaded by

Copyright:

Available Formats

PUBLIC

Integration of SAP GTS with EWM in SAP S/4HANA

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

2 Configuration of the System Connection ........................................................................................... 6

3 General Setup ....................................................................................................................................12

4 EWM Process Setup ..........................................................................................................................19

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

5 Process Descriptions ........................................................................................................................ 34

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

2.1 Background Information About System Landscape

Overview of System Landscape Entities

2.2 Prerequisites for the System Connection

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

2.3 Cross-Client Settings in GTS

2.3.1 Configuring Logical Systems in GTS

2.3.2 Configuring a Group of Logical Systems in GTS

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

2.4 Cross-Client Settings in EWM

2.4.1 Configuring Logical Systems in EWM

2.5 Client-Specific Settings in GTS

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

2.6 Client-Specific Settings in EWM

2.6.1 Assigning a GTS Logical System to an RFC Destination

2.7 Configuration of qRFC Communication

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

2.7.1 Configuring the qRFC Communication in GTS

Destination <RFC Destination>, for example, EWMCLNT001

W/o tRFC Leave this field empty.

Queue Name WMGTS* (or you can use *)

USERDEST Leave this field empty.

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

Destination <RFC Destination>, for example, GTSCLNT001

W/o tRFC Leave this field empty.

Queue Name DLVG* (or you can use DLV*)

USERDEST Leave this field empty.

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

In EWM, the following steps are described:

In SAP GTS, the following steps are described:

3.1 General Settings in EWM

3.1.1 Defining Business Systems

3.1.2 Defining the Customs ID

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

3.1.3 Warehouse-Specific Settings

3.1.3.1 Assigning the Business System

3.1.3.2 Assigning the Customs ID

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

3.2 General Settings in GTS

3.2.1 Defining the Organizational Structure

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

3.2.1.1 Defining and Assigning Legal Units

3.2.1.2 Assigning Plants from the Feeder System to Legal

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

3.2.1.3 Defining Foreign Trade Organizational Units

3.2.1.4 Assigning Partner Numbers to the Foreign Trade

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

3.2.1.5 Defining the Customs ID

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

3.2.1.6 Assigning the Customs ID

3. Save the changes.

3.2.2 Transfering Material and Business Partner Master Data

Integration of SAP GTS with EWM in SAP S/4HANA PUBLIC

4.1.1 Adjusting Status Profiles for Item Types