Details: Written by: Ayhan Akkaya; Category: EWM Articles; Published: 07 November 2023; Hits: 22

Business Scenario 5
Configuration of the System Connection 6
General Setup 12
1. General Settings in EWM 12
2. General Settings in GTS 14
  1. Defining the Organizational Structure 14
  2. Transfering Material and Business Partner Master Data 18
EWM Process Setup 19
Process Descriptions 34

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:
    - Decentralized EWM on SAP S/4HANA OP 1909 or higher, linked to
    - SAP ERP 6.0 EhP 3 or higher
  - Option 2:
    - Decentralized EWM on SAP S/4HANA OP 1909 or higher, linked to
    - SAP S/4HANA OP 1610 or higher, used as global enterprise management system
  - Option 3:
    - 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.

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.

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:

Entity	Setting Level	Customizing Transport	Comments
RFC Destination Example: GTSCLNT001 EWMCLNT001	Cross-Client	No	Technical setting for RFC and qRFC communication; Naming convention: <SID>CLNT<CLIENT>;
Logical System Example: GTSCLNT001 EWMCLNT001	Cross-Client	Yes	Technical setting for RFC and qRFC communication; Naming convention: <SID>CLNT<CLIENT>; Can be created in the System Landscape Directory; The logical system is assigned to the RFC destination; Own logical system assigned to client.
Business System Example: GTS_001 EWM_001	Client	No	Used in EWM for transactional data; Naming convention: <SID>_<CLIENT>; The business system is assigned to a logical system; 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.

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

TOP
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.
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).

TOP
Client-Specific Settings in GTS

You use this process to prepare the GTS client for the communication with EWM.
TOP
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.
TOP
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:

GTS sends compliance check triggers to EWM
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.

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.
  1. In the GTS system, on the SAP Easy Access screen, call transaction SMQS.
  2. On the qRFC Monitor (QOUT Scheduler) screen, choose Registration.
  3. 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.
  4. 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.
  1. In the SAP GTS system, on the SAP Easy Access screen, call transaction SMQR.
  2. On the qRFC Monitor (QIN Scheduler) screen, choose Registration.
  3. Enter the data as shown in the following table:
    
    Field
    
    Value
    
    Queue Name
    
    WMGTS* (or you can use *)
    
    Mode
    
    D
    
    Max. Runtime
    
    60
    
    USERDEST
    
    Leave this field empty.
    
    Attempts
    
    30
    
    Pause
    
    300
  4. Choose Continue.
    
    TOP

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:

Register the RFC destination for GTS in the QOUT scheduler in EWM. This setting is relevant for the qRFC communication from EWM to GTS.
1. In the SAP EWM system, on the SAP Easy Access screen, call transaction SMQS.
2. On the qRFC Monitor (QOUT Scheduler) screen, choose Registration.
3. Enter the data as shown in the following table:
  
  Field
  
  Value
  
  Destination
  
  <RFC Destination>, for example, GTSCLNT001
  
  Max.Conn.
  
  10
  
  Max. Runtime
  
  60
  
  W/o tRFC
  
  Leave this field empty.
4. Choose Continue.

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:

In the SAP EWM system, on the SAP Easy Access screen, call transaction SMQR.
On the qRFC Monitor (QIN Scheduler) screen, choose Registration.

Enter the data as shown in the following table:

Field

Value

Queue Name

DLVG* (or you can use DLV*)

Mode

Max. Runtime

USERDEST

Leave this field empty.

Attempts

Pause

300

Choose Continue.

TOP

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

EWM Process Setup

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.

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
  
  Carry out the following steps in your EWM customizing client:
  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:
    1. For standard outbound delivery items, choose /SCDL/OUT_PRD_DLV_STANDARD, for example
    2. 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.
  TOP
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

Carry out the following steps in your EWM customizing client:
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:
  1. For standard outbound delivery documents, choose /SCDL/OUT_PRD_STANDARD, for example
  2. 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).
4. Save the status profiles.
  
  TOP
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

Carry out the following steps in your EWM customizing client:
1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery –
  
  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:
  1. /SCWM/PDO_01_GTS_CHECK
  2. /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:
  1. /SCWM/FDO_01_GTS_DOC_DELETE
6. Save your changes.
  
  Important
  
  This procedure must be repeated after each release upgrade.
  
  TOP

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

Carry out the following steps in your EWM customizing client:

In Customizing for Extended Warehouse Management, choose Goods Issue Process Outbound Delivery Define Item Types for Outbound Delivery Process.

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

Make sure, that the adjusted status profiles from step 4.1.1 are used in your item type.
Save your changes.

TOP

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

Carry out the following steps in your EWM customizing client:

In Customizing for Extended Warehouse Management, choose Goods Issue Process Outbound Delivery Define Document Types for Outbound Delivery Process.

Create new entries by copying the following existing entries and changing the document type, for example, to ZGTS or ZGTD:

Existing Entries		New Entries
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

Make sure, that the adjusted status and action profiles from step 4.1.2 and 4.1.3 are used in your document type.
Change the following settings in the entries:

Doc. Type

Doc. Cat.

Legal Control GTS

No TCD GTS Check

ZGTS

PDO

X

if necessary

ZGTD

PDO

X

If necessary
Save your changes.

TOP

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

Carry out the following steps in your EWM customizing client:
1. In Customizing for Extended Warehouse Management, choose Goods Issue Process Outbound 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
3. Save your changes.
  
  TOP
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

Carry out the following steps in your EWM customizing client:
1. In Customizing for Extended Warehouse Management, choose Interfaces ERP Integration Delivery Processing Map Document Types from ERP System to EWM.
2. Create a new entry and enter the following data:
  
  Field
  
  Example data
  
  Business System
  
  ERP_001
  
  DocTypeERP
  
  ZGTS
  
  Doc. Type
  
  ZGTS
3. Save your changes.
  
  TOP
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

Carry out the following steps in your EWM customizing client:
1. In Customizing for Extended Warehouse Management, choose Interfaces ERP Integration Delivery Processing Map Item Types from ERP System to EWM.
2. Create a new entry and enter the following data:
  
  Field
  
  Example data
  
  Business System
  
  ERP_001
  
  DocTypeERP
  
  ZGTS
  
  ItmTpERP
  
  ZGTS
  
  Doc. Type
  
  ZGTS
  
  Item Type
  
  ZGTS
3. Save your changes.
  
  TOP
Mapping Date Types from an ERP System

You can use this procedure to map date types to your newly created document type.

Procedure

Carry out the following steps in your EWM customizing client:
1. In Customizing for Extended Warehouse Management, choose Interfaces ERP Integration Delivery Processing Map Date Types from ERP System to EWM.
2. Create a new entry and enter the following data:
  
  Field
  
  Example data
  
  Business System
  
  ERP_001
  
  DTypeERP
  
  WSHDRLFDAT
  
  Doc. Type
  
  ZGTS
  
  End Date
  
  TDELIVERY
  
  Conf. D/T
  
  Space (Do Not Confirm Date/Time)
3. Save your changes.
  
  TOP
Determining Warehouse Process Types

You can use this procedure to define the warehouse process types to your newly created document types.

Procedure

Carry out the following steps in your EWM customizing client:
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. Save your changes.
  
  TOP

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.
1. Adjusting Document Types
  
  You can use this procedure to adjust the corresponding outbound delivery order and outbound delivery document type.
  
  Procedure
  
  Carry out the following steps in your EWM customizing client:
  1. In Customizing for Extended Warehouse Management, choose Goods Issue Process Outbound 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. Type
    
    Doc. Cat.
    
    Description
    
    Legal Control GTS
    
    No TCD GTS Check
    
    OFO
    
    PDO
    
    Outbound Delivery Order w/ Freight Order
    
    X
    
    if necessary
  3. Choose the corresponding outbound delivery document type, and change the following settings in the entry:
    
    Doc. Type
    
    Doc. Cat.
    
    Description
    
    Billing Req. Ty
    
    OFO
    
    FDO
    
    Outbound Delivery w/ Freight Order
    
    A – Billing Document Immediately
  4. Save your changes.
    
    TOP
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
  
  Carry out the following steps in your EWM customizing client:
  1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery –
    
    Warehouse RequestStatus Management Define Status Profiles.
  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).
  6. Save your changes.
    
    TOP
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
  
  Carry out the following steps in your EWM customizing client:
  1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery –
    
    Warehouse RequestStatus Management Define Status Profiles.
  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):
    1. DBT - Blocked (Transp. Plan)
    2. DGT - GTS Check
    3. DGE - GTS (Embargo)
    4. DGL - GTS (LegCtrl)
    5. DGS - GTS (SPLScrn)
  4. Save the status profile.
    
    TOP
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
  
  Carry out the following steps in your EWM customizing client:
  1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery – 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
  3. Save your changes.
    
    TOP

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.

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

Carry out the following steps in your EWM customizing client:

In Customizing for Extended Warehouse Management, choose Master Data Product Define Stock Types.

Create new entries and enter the following data for your warehouse:

Stock Type

Description of Stock Type

Availability Group

Location- Independent Stock Type

Role

Customs - Free in Putaway

001

C – Customs Blocked Stock

Customs - Unrstrctd-Use Ptaway

002

C – Customs Blocked Stock

C3	Customs - Quality in Putaway	001	QQ	C – Customs Blocked Stock
C4	Customs - Quality in Warehouse	002	QQ	C – Customs Blocked Stock
C5	Customs - Blocked in Putaway	001	BB	C – Customs Blocked Stock
C6	Customs - Blocked in Warehouse	002	BB	C – Customs Blocked Stock
C7	Customs - Returns in Putaway	001	RR	C – Customs Blocked Stock
C8	Customs - Returns in Warehouse	002	RR	C – Customs Blocked Stock

Save your changes.

TOP

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

Carry out the following steps in your EWM customizing client:
1. In Customizing for Extended Warehouse Management, choose Interfaces GTS Integration Define Previous Document Types.
2. Create new entries and enter the following data for your warehouse:
  
  Previous Document Type
  
  Description
  
  Customs Block
  
  Transit Procedure Relevance
  
  ATB
  
  ATB
  
  X
  
  -
  
  T-
  
  T-
  
  X
  
  X
  
  T1
  
  T1
  
  X
  
  X
  
  T2
  
  T2
  
  -
  
  X
  
  T2F
  
  T2F
  
  -
  
  X
3. Save your changes.
  
  TOP
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

Carry out the following steps in your EWM customizing client:
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 Type
  
  Ext. Prev. Document Type
  
  ATB
  
  ATB
  
  T-
  
  T-
  
  T1
  
  T1
  
  T2
  
  T2
  
  T2F
  
  T2F
3. Save your changes.
  
  TOP

Defining Reference Document Categories

You can use this procedure to check if the required reference document categories have been created.

Procedure

Carry out the following steps in your EWM customizing client:

In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery –

Warehouse Request Reference Documents Define Reference Document Categories.

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

Save your changes.

TOP

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

Carry out the following steps in your EWM customizing client:
1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery –
  
  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. Save your changes.
  
  TOP
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

Carry out the following steps in your EWM customizing client:
1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery –
  
  Warehouse RequestStatus Management Define Status Profiles.
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. Save the status profile.
  
  TOP
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

Carry out the following steps in your EWM customizing client:
1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery –
  
  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:
  1. /SCWM/PDO_01_NCTS_NEW.
4. Save your changes.
  
  Important
  
  This procedure must be repeated after each release upgrade.
  
  TOP

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 S/4HANA 2021 or higher only.

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.

TOP
1. Adjusting Status Profiles
  
  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
  
  Carry out the following steps in your EWM customizing client:
  1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery –
    
    Warehouse RequestStatus Management Define Status Profiles.
  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):
    1. DBT - Blocked (Transp. Plan)
    2. DTD - Transport Planning
    3. 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):
    1. DBT - Blocked (Transp. Plan).
  6. Save the status profiles.
    
    TOP
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
  
  Carry out the following steps in your EWM customizing client:
  1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery –
    
    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.
    
    TOP
3. Defining Item Types for the Correction Process
  
  You can use this procedure to create inbound delivery item type for the correction process.
  
  Procedure
  
  Carry out the following steps in your EWM customizing client:
  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:
    
    Existing Entries
    
    New Entries
    
    Item Type
    
    Doc. Cat.
    
    Item Cat.
    
    Item Type
    
    Doc. Cat.
    
    Item Cat.
    
    IDIS
    
    PDI
    
    DLV
    
    ZIDS
    
    PDI
    
    DLV
  3. Save your changes.
    
    TOP
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
  
  Carry out the following steps in your EWM customizing client:
  1. In Customizing for Extended Warehouse Management, choose Goods Receipt Process Inbound 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:
    
    Existing Entries
    
    New Entries
    
    Doc. Type
    
    Doc. Cat.
    
    Doc. Type
    
    Doc. Cat.
    
    IDIS
    
    PDI
    
    ZIDS
    
    PDI
  3. Save your changes.
  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
  5. Save your changes.
    
    TOP
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
  
  Carry out the following steps in your EWM customizing client:
  1. In Customizing for Extended Warehouse Management, choose Goods Receipt Process Inbound Delivery Define Allowed Item Types in Inbound Delivery Process.
  2. Create new entries and enter the following entries:
    
    Doc. Type
    
    Item Type
    
    ZIDS
    
    ZIDS
  3. Save your changes.
    
    TOP
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
  
  Carry out the following steps in your EWM customizing client:
  1. In Customizing for Extended Warehouse Management, choose Interfaces ERP Integration Delivery Processing Map Document Types from ERP System to EWM.
  2. Create a new entry and enter the following data:
    
    Field
    
    Example data
    
    Business System
    
    ERP_001
    
    DocTypeERP
    
    EL
    
    Cde. Init. Com.
    
    DIS
    
    Doc. Type
    
    ZIDS
  3. Save your changes.
    
    TOP
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
  
  Carry out the following steps in your EWM customizing client:
  1. In Customizing for Extended Warehouse Management, choose Interfaces ERP Integration Delivery Processing Map Item Types from ERP System to EWM.
  2. Create a new entry and enter the following data:
    
    Field
    
    Example data
    
    Business System
    
    ERP_001
    
    DocTypeERP
    
    EL
    
    ItmTpERP
    
    ELN
    
    Doc. Type
    
    ZIDS
    
    Item Type
    
    ZIDS
  3. Save your changes.
    
    TOP
8. Mapping Date Types from an ERP System
  
  You can use this procedure to map date types to your newly created document types.
  
  Procedure
  
  Carry out the following steps in your EWM customizing client:
  1. In Customizing for Extended Warehouse Management, choose Interfaces ERP Integration Delivery Processing Map Date Types from ERP System to EWM.
  2. Create a new entry and enter the following data:
    
    Field
    
    Example data
    
    Business System
    
    ERP_001
    
    DTypeERP
    
    WSHDRLFDAT
    
    Doc. Type
    
    ZIDS
    
    End Date
    
    TDELIVERY
    
    Conf. D/T
    
    Space (Do Not Confirm Date/Time)
  3. Save your changes.
    
    TOP
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.
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
  
  Carry out the following steps in your EWM customizing client:
  1. In Customizing for Extended Warehouse Management, choose Interfaces ERP Integration Delivery 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
  3. Save your changes.
    
    TOP
2. Adjusting Status Profiles
  
  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
  
  Carry out the following steps in your EWM customizing client:
  1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery –
    
    Warehouse RequestStatus Management Define Status Profiles.
  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).
  4. Save the status profile.

TOP

Process Descriptions

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:
  1. For the relevant item, it is set to “In Progress” (2)
  2. 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:
  1. For blocked items, it is set to “GTS Check, Not OK” (8)
  2. For the items that are not blocked, t is set to “GTS Check, OK” (9)
  3. 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:
  1. Create any warehouse task in the putaway process
  2. Load (simple or complex loading)
  3. 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:
  1. It is manually triggered. You can trigger a GTS check by highlighting the relevant items and then choosing the button GTS => Recheck GTS Lock
  2. The following attributes are changed in the delivery header:
    1. Ship-to party or its address
    2. Carrier or its address
    3. Planned out-of-yard date
  3. An item is created or deleted
  4. The following attributes are changed in a delivery item:
    1. Item quantity
    2. Catch weight quantity
    3. Product
  5. The compliance check status in GTS has been changed and a notification is sent to EWM, which also triggers a new check
  6. 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.
  
  TOP
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:
  1. Create any warehouse task in the picking process
  2. Load (simple or complex loading)
  3. 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).
  
  TOP
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:
  1. “Not Relevant” (0)
  2. “In Progress” (2)
  3. “GTS Check, Not OK” (8)
  4. “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:
  1. GTS Check (Embargo) (DGE) – Embargo check
  2. GTS Check (Legal Control) (DGL) – Legal Control check
  3. 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 S/4HANA 2021 or higher only.
  
  TOP
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:
  1. 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)
  2. The previous document type is relevant for the transit procedure, see chapter 4.3.2
  3. 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:
  1. Create any warehouse task in the putaway process
  2. 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.
  
  TOP
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:
  1. 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)
  2. The previous document type is relevant for temporary storage, see chapter 4.3.2
  3. 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:
  1. Stock assigned to the inbound delivery
  2. Stock not assigned to any deliveries
  3. 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.
  
  TOP
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 S/4HANA 2021 or higher only.
  
  TOP
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.
  
  TOP
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).

TOP

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
/SCWM/EX_GTS_CHECK_AUTHORITY	With this extension, you can distinguish between the Route Release and GTS Release actions in authority checks. You can find further information in SAP Note 1998492.
/SCWM/IF_EX_GTS_CHECK_REL_SET	With this extension, you can define which outbound delivery order items are relevant for GTS compliance checks.
/SCWM/SHP_PROC_REL_SET	With this extension, you can define which inbound or outbound 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
3141236	Adv. SR in S/4HANA: GTS Integration - blocked EWM outbound delivery order after late storage location assignment	EWM
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
3014396	Enhancement of status synchronization between customs document and EWM delivery	GTS
3002372	GTS check not triggered after changing main item with delivery split item	EWM
2999396	Enhancement of compliance checks: Date changes and push messages from GTS	EWM
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

2763189	Bonded scrap requests fail to update GTS, if no sufficient inventory in GTS - missing error message	EWM
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
2475570	Fields GTS_VORPA and GTS_VORNU are not persisted in header of inbound delivery	EWM
2460221	Extension of Customs Block Release search to handle /SCWM/HU_DLV references	EWM
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

Field	Example data
Business System	ERP_001
DTypeERP	WSHDRLFDAT
Doc. Type	ZGTS
End Date	TDELIVERY
Conf. D/T	Space (Do Not Confirm Date/Time)

Process Profile	Invoice Before Goods Issue
/SCWM/OUT_PRD_FO	A – Only for Export
/SCWM/OUT_FD_FO	A – Only for Export

Doc. Type	Doc. Cat.	Date Profile	RefDocCat Profile
ZIDS	PDI	/SCWM/INB_PRD_FO	/SCWM/INB_PRD_FO

Field	Example data
Business System	ERP_001
DocTypeERP	EL
Cde. Init. Com.	DIS
Doc. Type	ZIDS

GTS Configuration-Integration & Process steps

Table of Contents

Business Scenario

Prerequisites

Configuration of the System Connection

Background Information About System Landscape Settings

Overview of System Landscape Entities

Prerequisites for the System Connection

Procedure

Cross-Client Settings in GTS

Configuring Logical Systems in GTS

Procedure

Configuring a Group of Logical Systems in GTS

Prerequisites

Procedure

Cross-Client Settings in EWM

Configuring Logical Systems in EWM

Procedure

Client-Specific Settings in GTS

Assigning an EWM Logical System to an RFC Destination in GTS

Procedure

Client-Specific Settings in EWM

Assigning a GTS Logical System to an RFC Destination in EWM

Procedure

Configuration of qRFC Communication

Prerequisites

Configuring the qRFC Communication in GTS

Procedure

Configuring the qRFC Communication in EWM

Procedure

General Setup

Prerequisites

General Settings in EWM

Defining Business Systems

Procedure

Defining the Customs ID

Procedure

Warehouse-Specific Settings

Assigning the Business System

Procedure

Assigning the Customs ID

Procedure

Assigning the Sales Organization

Procedure

General Settings in GTS

Defining the Organizational Structure

Procedure

Defining and Assigning Legal Units

Procedure

Assigning Plants from the Feeder System to Legal Units

Procedure

Defining Foreign Trade Organizational Units

Procedure

Assigning Partner Numbers to the Foreign Trade Organization

Procedure

Defining the Customs ID

Procedure

Assigning the Customs ID

Procedure

Transfering Material and Business Partner Master Data

EWM Process Setup

Customizing the Outbound Process

Prerequisites

Adjusting Status Profiles for Item Types

Procedure

Adjusting Status Profiles for Document Types

Procedure

Adjusting Action Profiles

Procedure

Defining Item Types

Procedure

Defining Document Types

Procedure

Defining Allowed Item Types

Procedure

Mapping Document Types from an ERP System

Procedure

Mapping Item Types from an ERP System

Procedure

Mapping Date Types from an ERP System