PUBLIC

How-To Guide
SAP NetWeaver
Document Version: 2.0 - 2019-05-29

Integration of SAP ERP or SAP S/4HANA with

decentralized EWM in S/4HANA
SAP S/4HANA 1809
Document History
Document Version Description
1.0 First official release of this guide
2.0 Updates as this guide can also be used for the integration to SAP S/4HANA (used as
global enterprise management system) instead of SAP ERP

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Document History © 2019 SAP AG or an SAP affiliate company. All rights reserved. 2
Table of Contents
1 Business Scenario ......................................................................................................................... 5

2 Background Information ................................................................................................................ 5

3 Prerequisites ................................................................................................................................. 6

4 Configuration of System Connection and Global Settings ............................................................... 7

4.1 Background Information About System Landscape Settings .................................................... 7
4.2 Prerequisites for System Connection ........................................................................................... 7
4.3 Cross-Client Settings in SAP ERP ................................................................................................. 8
4.3.1 Activating Business Functions in Switch Framework in SAP ERP ............................... 8
4.3.2 Configuring Logical Systems in SAP ERP ...................................................................... 9
4.4 Cross-Client Settings in Decentralized EWM ............................................................................... 9
4.4.1 Configuring Logical Systems in EWM............................................................................. 9
4.5 Client-Specific Settings in SAP ERP............................................................................................ 10
4.5.1 Assigning EWM Logical Systems to RFC Destinations in SAP ERP ........................... 10
4.5.2 Configuring Additional Material Master Screens in SAP ERP .................................... 10
4.6 Client-Specific Settings in Decentralized EWM........................................................................... 11
4.6.1 Enabling Decentralized EWM Based on SAP S/4HANA .............................................. 11
4.6.2 Assigning ERP Logical Systems to RFC Destinations in EWM ................................... 12
4.6.3 Configuring Business Systems in EWM ....................................................................... 12
4.6.4 Configuring Business System Groups in EWM ............................................................ 12
4.6.5 Activating the Planning Version and Model for Master Data...................................... 13
4.6.6 Specifying Output Format of Product Number ........................................................... 13
4.6.7 Setting Control Parameters for ERP Version Control ................................................. 14

5 Configuration of qRFC Communication ......................................................................................... 15

5.1 Configuring qRFC Communication in SAP ERP ......................................................................... 15
5.2 Configuring qRFC Communication in Decentralized EWM ....................................................... 17

6 Configuration of IDoc Communication .......................................................................................... 19

6.1 Creating Port for IDoc Processing in Sender System................................................................ 19
6.2 Creating Reduced Message Types .............................................................................................. 19
6.2.1 Creating a Reduced Message Type for MATMAS .......................................................20
6.2.2 Creating a Reduced Message Type for DEBMAS ........................................................ 25
6.2.3 Creating a Reduced Message Type for CREMAS ........................................................26
6.2.4 Transporting Reduced Message Types to Decentralized EWM ................................. 27
6.3 Defining Data Distribution Model and Distributing Views ......................................................... 27
6.3.1 Creating New Filter Object Types ................................................................................. 27
6.3.2 Checking Filter Dependencies.......................................................................................28
6.3.3 Creating Data Distribution Model .................................................................................28
6.4 Defining Partner Profile ............................................................................................................... 30
6.4.1 Creating Partner Profile in Sender System Manually ................................................. 31
6.4.2 Creating Partner Profile in Receiver System Manually ............................................... 31
6.5 Converting Data Between Sender and Receiver ........................................................................ 32
6.5.1 Converting Data Using Conversion Rules .................................................................... 32
6.5.2 Converting Data via BAdI............................................................................................... 33
6.6 Activating Change Pointers in Sender System ..........................................................................34
6.6.1 Activating Change Pointers at Client Level ..................................................................34
6.6.2 Activating Change Pointers per Message Type...........................................................34

7 Customizing Settings in Decentralized EWM ................................................................................ 35

7.1 Checking Basic Table Entries in EWM......................................................................................... 35
7.2 Configuring Customer/Vendor Integration in EWM .................................................................. 35
7.3 Activating BC Sets for Client-Dependent Number Ranges.......................................................38

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Table of Contents © 2019 SAP AG or an SAP affiliate company. All rights reserved. 3
7.4 Activating BC Sets for Client-Dependent Basic Settings ..........................................................38
7.5 Verifying Synchronization of SAP ERP and EWM Customizing ................................................39

8 Master Data Distribution via ALE/IDoc ......................................................................................... 42

8.1 Executing Initial Transfer of Master Data ...................................................................................42
8.1.1 Executing Initial Transfer of Characteristics................................................................42
8.1.2 Executing Initial Transfer of Classes ............................................................................42
8.1.3 Executing Initial Transfer of Materials..........................................................................42
8.1.4 Executing Initial Transfer of Batches............................................................................43
8.1.5 Executing Initial Transfer of Customers.......................................................................44
8.1.6 Executing Initial Transfer of Vendors ...........................................................................44
8.2 Executing Delta Transfer of Master Data....................................................................................44
8.2.1 Creating IDoc Using Change Pointers Manually..........................................................44
8.2.2 Creating IDoc Using Change Pointers Automatically .................................................45
8.3 Implementing BAdIs for Master Data Distribution via IDoc ......................................................45

9 Warehouse Integration into the SAP ERP Enterprise Structure ..................................................... 47

9.1 Prerequisites for Warehouse Integration in SAP ERP ............................................................... 47
9.2 Creating Organizational Units for Warehouse in SAP ERP .......................................................48

10 Warehouse Creation and Integration in EWM................................................................................. 51

10.1 Creating and Integrating an EWM Warehouse ........................................................................... 51
10.2 Activating BC Sets for Warehouse-Dependent Number Ranges ............................................. 52
10.3 Activating BC Sets for Warehouse-Dependent Basic Settings ................................................ 53
10.4 Assigning Storage Locations to EWM Stock Types Using Basic Availability Groups ............. 53
10.5 Assigning Storage Locations to EWM Stock Types Using Location-Specific Availability
Groups ...........................................................................................................................................54
10.6 Aligning HU Numbering ................................................................................................................ 55

11 Additional Data Transfer and Settings in SAP ERP and EWM......................................................... 57

11.1 Activating Transaction Data Transfer in SAP ERP..................................................................... 57
11.2 Activating Additional Data Transfer in EWM ..............................................................................58
11.3 Configuring Additional Settings for Batches ..............................................................................59

Appendix ................................................................................................................................................ 60

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Table of Contents © 2019 SAP AG or an SAP affiliate company. All rights reserved. 4
1 Business Scenario
This how-to guide describes the detailed configuration for integrating SAP ERP or SAP S/4HANA with
decentralized Extended Warehouse Management (EWM) based on SAP S/4HANA 1809.
It covers the following aspects of the configuration:
· Configuration of system connection and global settings between decentralized EWM based on SAP
S/4HANA and SAP ERP
· Configuration of qRFC communication
· Configuration of IDoc communication
· Customizing settings in decentralized EWM
· Master Data Distribution via ALE/IDoc
· Warehouse Integration into the SAP ERP enterprise structure
· Warehouse creation and integration in EWM
· Additional data transfer and settings in SAP ERP and EWM

Decentralized EWM on an SAP S/4HANA stack is a deployment option of the EWM application on the SAP
S/4HANA on premise stack. It is an SAP S/4HANA on premise system for EWM usage. Compared to an
embedded EWM in SAP S/4HANA, it provides integration capabilities to a remote enterprise management
system, for example an SAP ERP system.
The wording ‘decentralized’ indicates a system landscape with a global enterprise management system which is
hosted in the corporate central data center, and which is integrated with a decentralized deployment of an EWM
system. In this guide, the global enterprise management system is an SAP ERP system or an SAP S/4HANA
system.
'Decentralized' also means that stock for these warehouses does not have active MM-IM stock management in
the same SAP S/4HANA system and client. Non-active MM-IM stock implies that the core enterprise
management logistics applications (PP, SD, MM, etc.) are also not actively used in this system and client for the
decentral warehouse-managed stock.

2 Background Information
Before you continue with this how-to guide, make sure this how-to guide fits to your EWM deployment option:
· Decentralized EWM on an SAP S/4HANA OP 1809 stack, linked to
· SAP ERP 6.0 EhP 5 or higher
You can also use this guide for the following deployment option:
· Decentralized EWM on an SAP S/4HANA OP 1809 stack, linked to
· SAP S/4HANA OP 1611 or higher, used as global enterprise management system

Other guides are available for SAP EWM or other EWM deployment options. For more information, refer to SAP
note 2782080.

Important
This guide is primarily intended for the integration of decentralized EWM with SAP ERP. You can
also use it for the integration of decentralized EWM with an SAP S/4HANA system, even if only SAP
ERP is mentioned in the text. In cases where the integration differs between SAP ERP and SAP
S/4HANA, the differences are mentioned explicitly in the text.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Business Scenario © 2019 SAP AG or an SAP affiliate company. All rights reserved. 5
3 Prerequisites
You have installed and correctly configured the following applications:
· You have a running SAP ERP system with active MM-IM (Inventory Management) and LE-SHP (Logistics
Execution – Shipping).
Minimal release/patch level: EhP 5 for SAP ERP 6.0
As an alternative, you have a running SAP S/4HANA system with active MM-IM and LE-SHP
Minimal release/patch level: SAP S/4HANA 1610
· You have installed an SAP S/4HANA system to run as decentralized EWM.
Minimal release/patch level: SAP S/4HANA OP 1809 FPS 2
· You have set up the decentralized EWM client with configuration content from client 000 (including all
tables of delivery class C and G). The configuration is needed for warehouse-independent master data such
as business partners, vendors, customers, and materials.

Tip
In Appendix D, you will find a list of SAP Notes containing information about BC sets in EWM. The
BC sets may help you with your EWM implementation following the basic integration described in
this guide.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Prerequisites © 2019 SAP AG or an SAP affiliate company. All rights reserved. 6

4 Configuration of System Connection and
Global Settings
You use this process to configure the system landscape settings required for the queued remote function call
(qRFC) communication between decentralized EWM and SAP ERP.
EWM communicates with SAP ERP via queued remote function call (qRFC) for parallel processing, using system
resources in parallel to increase business throughput and reduce processing time.

4.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 SAP ERP with
decentralized EWM.
Overview of System Landscape Entities
The following table provides an overview of system landscape entities required for the integration:

Customizing
Entity Setting Level Transport Comments
RFC Destination Cross-Client No Technical setting for RFC and qRFC communication;
Example: Naming convention: <SID>CLNT<CLIENT>;
ERPCLNT001 See chapter Prerequisites for System Connection
EWMCLNT001
Logical System Cross-Client Yes Technical setting for RFC and qRFC communication;
Example: Naming convention: <SID>CLNT<CLIENT>;
ERPCLNT001 Can be created in the System Landscape Directory;
EWMCLNT001
The logical system is assigned to the RFC destination;
Own logical system assigned to client.
See chapter Configuring Logical Systems in SAP ERP
Business System Client No Used in EWM for master data;
Group 1:N relationship to logical system;
Example: See chapter Configuring Business System Groups in EWM
ERP_BG1

Business System Client No Used in EWM for transactional data;

Example: Naming convention: <SID>_<CLIENT>;
ERP_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;
See chapter Configuring Business Systems in EWM

4.2 Prerequisites for System Connection

System administrators must make specific settings for the Remote Function Call (RFC) connection between SAP
ERP and decentralized EWM before any customizing activity is carried out.
Contact your system administrator to ensure the following prerequisites are met:
· An RFC user exists in each target system/client defined as RFC destination. For example, for the
decentralized EWM client to use the RFC destination to the ERP test client, an RFC user exists in the ERP
client.
· RFC destinations exist between the corresponding ERP and EWM clients.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of System Connection and Global Settings © 2019 SAP AG or an SAP affiliate company. All rights reserved. 7
Procedure
...

1. In the decentralized EWM system, create an RFC destination (ABAP Connection) for the ERP 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 ERPCLNT001.
2. In the SAP ERP system, create an RFC destination (ABAP Connection) for the decentralized 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.

4.3 Cross-Client Settings in SAP ERP

You use this process to prepare SAP ERP for the communication with decentralized EWM. The settings affect all
clients of the SAP ERP system and require authorizations for cross-client settings on user and client level.

4.3.1 Activating Business Functions in Switch Framework in

SAP ERP
You use this procedure to activate business functions in the Switch Framework. To benefit from the tight
integration of SAP ERP and decentralized EWM, you must activate the following business function in SAP ERP:
Business Function Description
LOG_LE_INTEGRATION LE, Extended Warehouse Management Integration
For more information, see the business function documentation in transaction SFW5.

Note
This business function is always active in SAP S/4HANA. There is no need to activate it if you
integrate decentralized EWM with SAP S/4HANA instead of SAP ERP.

Other business functions from SAP ERP may be needed for your warehousing processes. Check the
documentation of the following EWM-related business functions in SAP ERP and decide if they are relevant for
your warehousing processes:
Business Function Description
LOG_PP_EWM_MAN EWM Integration into Manufacturing
LOG_PP_EWM_MAN_2 EWM Integration into Manufacturing 2
LOG_SCM_MEAN_INT SCM, CIF Transfer of Additional GTINs (EANs/UPCs)
for Material
OPS_ADVRETURNS_1 Advanced Returns Management
OPS_ADVRETURNS_2 Advanced Returns Management 2
SPE_CI_1 Service Parts Management: Innovations in ERP
LOG_TM_ORD_INT_II ERP-TMS: Order and Invoice Integration
LOG_SCM_EWM_INT EWM Integration
ISR_RET_CD/FT_EWM Retail, Merchandise Distribution-SAP EWM Integration
/CWM/CM_2 CWM, Variable Valuation Unit of Measure (Reversible)
(available only if IS-CWM is installed)

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Configuration of System Connection and Global Settings © 2019 SAP AG or an SAP affiliate company. All rights reserved. 8
Note
Most of these business functions are always active in SAP S/4HANA. There is no need to activate
them if you integrate decentralized EWM with SAP S/4HANA instead of SAP ERP. In transaction
SFW5, you will find them under S/4H_ALWAYS_ON_FUNCTIONS .

Procedure
Contact your system administrator to carry out the following steps in an ERP client allowing cross-client settings
and the creation of workbench requests. If necessary, use the workbench request to transport the settings to
other SAP ERP systems.
...

1. On the SAP Easy Access screen, call transaction SFW5.

2. Activate the business function that you want to use. Only business function LOG_LE_INTEGRATION (LE,
Extended Warehouse Management Integration) is mandatory.
..
...
...

4.3.2 Configuring Logical Systems in SAP ERP

You use this procedure to define the logical systems in SAP ERP.

Procedure
Carry out the first step of the procedure in your ERP customizing client allowing cross-client settings and
transport if necessary the settings to other SAP ERP systems (for example, SAP ERP test system, SAP ERP
productive system). Carry out the subsequent step in all SAP ERP systems (in a client allowing cross-client
settings) that you want to connect to decentralized EWM.

1. Define a logical system for your ERP client (for example, ERPCLNT001) and a logical system for your EWM
client (for example, EWMCLNT001) in Customizing for Integration with Other SAP Components under
Extended Warehouse Management ® Basic Settings for Setting Up the System Landscape ® Name
Logical System.
2. Assign the ERP logical system defined in the first step to the ERP client (for example, in system ERP, assign
ERPCLNT001 to client 001) in Customizing for Integration with Other SAP Components under Extended
Warehouse Management ® Basic Settings for Setting Up the System Landscape ® Assign Logical System
to a Client.

Example
In a landscape with an SAP ERP customizing system (for example ERC, client 001), an SAP ERP test
system (for example ERT client 001) and an SAP ERP productive system (for example ERP, client
001), you define multiple logical systems (for example, ERTCLNT001 and ERPCLNT001) in your
SAP ERP customizing system. The same applies to the decentralized EWM systems (for example
EWTCLNT001 and EWPCLNT001)

4.4 Cross-Client Settings in Decentralized EWM

You use this process to prepare decentralized EWM for the communication with SAP ERP. The settings affect all
clients of the decentralized EWM system and require authorizations for cross-client settings on user and client
level.

4.4.1 Configuring Logical Systems in EWM

You use this procedure to define the logical systems in decentralized EWM.

Procedure
Carry out the first step of the procedure in your EWM customizing client allowing cross-client settings and if
necessary, transport the settings to other EWM systems (for example, EWM test system, EWM productive

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Configuration of System Connection and Global Settings © 2019 SAP AG or an SAP affiliate company. All rights reserved. 9
system). Carry out the subsequent step in all EWM systems (in a client allowing cross-client settings) that you
want to connect to SAP ERP.

1. Define a logical system for your EWM client (for example, EWMCLNT001) and a logical system for your ERP
client (for example, ERPCLNT001) 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 SAP ERP systems (for example ERTCLNT001
and ERPCLNT001).

4.5 Client-Specific Settings in SAP ERP

You use this process to prepare the SAP ERP client for the communication with decentralized EWM.
P r ocess

4.5.1 Assigning EWM Logical Systems to RFC Destinations in

SAP ERP
You use this procedure to assign the EWM logical systems defined in SAP ERP to RFC destinations in SAP ERP.

Note
These settings cannot be transported from your ERP customizing client to other SAP ERP systems
and clients. Therefore, you must repeat the steps in every ERP client connected to decentralized
EWM.

Procedure
Carry out the following steps in each ERP client you want to connect to decentralized 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.

4.5.2 Configuring Additional Material Master Screens in SAP

ERP
You use this procedure to activate the following additional material master screens in SAP ERP:
· WM Execution
· WM Packaging

Note
Skip this chapter if you integrate decentralized EWM with SAP S/4HANA instead of SAP ERP as the
procedure is not required in SAP S/4HANA.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Configuration of System Connection and Global Settings © 2019 SAP AG or an SAP affiliate company. All rights reserved. 10
The additional screens allow you to maintain material master data needed in SAP ERP in the warehousing
processes with Extended Warehouse Management (EWM).
Additional material master screens are used in the standard warehouse with preconfigured processes. For
example, you maintain the handling unit (HU) type for packaging materials on the additional screen WM
Packaging. The data is transferred via IDoc to EWM.

Note
For some material master attributes (for example, HU types) it is necessary to maintain the allowed
values in Customizing for Integration with Other SAP Components under Extended Warehouse
Management ® Additional Material Attributes ® Attribute Values for Additional Material Master
Fields. For more information, see the Customizing documentation and chapter Verifying
Synchronization of SAP ERP and EWM Customizing.

Procedure
Carry out the following steps in your ERP customizing client and if necessary, transport the settings to other ERP
clients or systems.
1. Activate the BC Set /SPE/MATERIAL_SCREENS containing additional entries for screen sequence 21 of the
material master maintenance on the SAP Easy Access screen under Tools ® Customizing Business
Configuration Sets ® Activation of BC Sets.
2. Maintain the screen sequence for the additional material master screens.

1. In Customizing for Logistics – General, choose Material Master ® Configuring the Material Master ®
Maintain Order of Main and Additional Screens .
2. Select sequence 21 and display the details by choosing Goto ® Details in the menu. You can ignore the
warning message that the entry belongs to SAP.
3. For screen number 56, enter 300.
4. For screen number 57, enter 310.
5. Save your entries.

4.6 Client-Specific Settings in Decentralized EWM

You use this process to configure settings at client level in decentralized EWM. The settings are valid for all
warehouses of the client.

4.6.1 Enabling Decentralized EWM Based on SAP S/4HANA

You use this procedure to enable EWM to run as a decentralized client on an SAP S/4HANA stack.

Procedure
Carry out the following steps in your EWM customizing client:
1. In Customizing for Extended Warehouse Management, choose Enable Decentralized EWM.
2. Set the indicator to enable decentralized EWM.
3. Save your entry.

Important
If you receive a STOP message that entries exist in /SPE/V_T340, check why they are there. Make
sure you are in the right system and client. If entries are there by accident (for example, due to
client copy), remove them. Never ignore the STOP message.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Configuration of System Connection and Global Settings © 2019 SAP AG or an SAP affiliate company. All rights reserved. 11
4.6.2 Assigning ERP Logical Systems to RFC Destinations in
EWM
You use this procedure to assign the ERP logical systems to RFC destinations in decentralized EWM.

Note
These settings cannot 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 SAP ERP.
...

Procedure
Carry out the following steps in each EWM client you want to connect to SAP ERP:
...

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 ERP logical system, for example, ERPCLNT001.
3. Choose Standard BAPI destination.
4. Enter the RFC destination created by your system administrator for the corresponding SAP ERP system
and choose Enter.
5. Save your entries.

4.6.3 Configuring Business Systems in EWM

You use this procedure to define the business systems for SAP ERP and EWM in EWM and to assign a business
system to the client.

Note
These settings cannot 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 SAP ERP.

Procedure
Carry out the following steps in each EWM client you want to connect to SAP ERP:
...

1. Define a business system for the ERP client (for example, ERP_001) and a business system for the EWM
client (for example, EWM_001) in Customizing for Extended Warehouse Management under Interfaces ®
ERP Integration ® General Settings ® Define Business Systems. Assign the SAP ERP business system to
the ERP logical system and the EWM business system to the EWM logical system, and set the Manual
Maintenance indicator.
If you use the System Landscape Directory (SLD), entries already exist for the EWM and SAP ERP system.
In this case, no action is required in this step.
2. Enter the EWM business system defined in the first step as own business system (for example, in system
EWM, client 001, enter EWM_001) in Customizing for Extended Warehouse Management under Interfaces
® ERP Integration ® General Settings ® Define Own Business Systems.

4.6.4 Configuring Business System Groups in EWM

You use this procedure to define the business system group for SAP ERP and EWM in decentralized EWM and
assign the logical systems to the business system group. The business system group is used to identify master
data belonging to one SAP ERP system in EWM.

Note
These settings cannot 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 SAP ERP.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Configuration of System Connection and Global Settings © 2019 SAP AG or an SAP affiliate company. All rights reserved. 12
Procedure
Carry out the following steps in each EWM client you want to connect to SAP ERP:
...

1. Define a business system group for the ERP client (for example, ERP_BG1) in Customizing for Extended
Warehouse Management under SCM Basis ® Integration ® Basic Settings for Creating the System
Landscape ® Maintain Business System Group.
2. Assign the logical systems for SAP ERP and EWM and a queue type to the business system group in
Customizing for Extended Warehouse Management under SCM Basis ® Integration Basic Settings for
Creating the System Landscape ® Assign Logical System and Queue Type.
Create and save the following entries, for example, for the following two clients:
BusSystGrp Logical System SAP Ind. Release Queue Type
ERP_BG1 ERPCLNT001 X <highest ERP Release, Inbound
for example 700> Queues
ERP_BG1 EWMCLNT001 <highest EWM Release, Inbound
for example 70> Queues

You can keep the default setting for field Error Handling in Target System .
If applicable, enter a system role for the SAP ERP system. For example, enter system role CW (Catch
Weight Management ERP System) for SAP ERP systems with installed component IS-CWM.

4.6.5 Activating the Planning Version and Model for Master

Data
You use this procedure to create a planning version 000 and a model 000 for master data maintenance in EWM.
This technical setting is required for master data replication.

Procedure
Carry out the following steps in each EWM client you want to connect to SAP ERP:
In the EWM system, on the SAP Easy Access screen, call transaction /SAPAPO/ACTVERCREATE. The system
informs you whether the planning version and model already exist, or if the system just created them.

CAUTION
Note that transaction /SAPAPO/ACTVERCREATE requires an authorization for objects C_APO_MOD
and C_APO_VERS with activity 01. You can check failed authorization checks after report execution
with transaction SU53.

4.6.6 Specifying Output Format of Product Number

You use this procedure to specify the input and output length of product numbers in decentralized EWM as well as
templates for displaying the product number.

Note
If you have specified an output format for material numbers in the SAP ERP system, it is
recommended to specify the same output format for product numbers in EWM.

Procedure
Carry out the following steps in the EWM customizing client:
...

1. In Customizing for Logistics - General, choose Material Master ® Basic Settings ® Define Output Format of
Material Numbers.
2. If not existing yet, create an entry to specify the output format for product numbers. Specify at least the
product number length (recommended in decentralized EWM: 40).

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Configuration of System Connection and Global Settings © 2019 SAP AG or an SAP affiliate company. All rights reserved. 13
3. Save your entry.

Recommendation
Even if the material number length in SAP ERP is set to 18 characters, it is recommended to set the
product number length in decentralized EWM to 40 characters as this is the standard setting for
EWM in SAP S/4HANA.

Note
If you connect decentralized EWM to an SAP ERP supporting 40 characters, you must also activate
the field length extension for the communication to this system in Customizing for Cross-
Application Components under General Application Functions ® Field Length Extension ® Activate
Extended Fields (transaction FLETS).

4.6.7 Setting Control Parameters for ERP Version Control

You use this procedure to activate or de-activate functions in EWM depending on the release of the connected
SAP ERP system.

Procedure
Carry out the following steps in the EWM customizing client:
...

1. In Customizing for Extended Warehouse Management, choose Interfaces ® ERP Integration ® ERP
Integration for Decentralized EWM ® Set Control Parameters for ERP Version Control.
2. Create an entry for the SAP ERP business system (for example, ERP_001) and the current SAP ERP
release. The system automatically proposes default settings corresponding to the EWM functions
supported with the given SAP ERP release.

Note
If you integrate decentralized EWM with SAP S/4HANA instead of SAP ERP, choose the appropriate
value in field SAP Release, for example S4_OP_100.

3. Save your entry.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Configuration of System Connection and Global Settings © 2019 SAP AG or an SAP affiliate company. All rights reserved. 14
5 Configuration of qRFC Communication
You use this process to configure the queued remote function call (qRFC) communication between decentralized
EWM based on SAP S/4HANA and SAP ERP.
Decentralized EWM communicates transaction data like inbound and outbound deliveries with SAP ERP via
queued remote function call (qRFC). Since the communication is bi-directional, you not only configure the sending
of data to both systems but also the reception of data from both systems.

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. Business systems exist in
decentralized EWM.

5.1 Configuring qRFC Communication in SAP ERP

You use this procedure to setup the qRFC communication in SAP ERP, i.e. to send transactional data to EWM and
to receive transactional data from EWM.

Procedure
Carry out the following steps (except step 5) in each SAP ERP client you want to connect to decentralized EWM.
Step 5 is a customizing activity, which you carry out in the ERP customizing client.
...

1. Register the RFC destination for EWM in the QOUT scheduler in SAP ERP. This setting is relevant for the
qRFC communication from SAP ERP to EWM.
a. In the SAP ERP 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

<RFC Destination> , for example,

Destination
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 SAP ERP.
This setting is relevant for the qRFC communication from EWM to SAP ERP.
a. In the SAP ERP system, on the SAP Easy Access screen, call transaction SMQR.
b. On the qRFC Monitor (QIN Scheduler) screen, choose Registration.
c. Enter the data as shown in the following table:

Field Value

Queue Name <used queue name>, we recommend that you

use either * or any of the following: DLW*, EWM*,
QI*, QM*, WM*

Mode D

Max. Runtime 60

USERDEST Leave this field empty.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of qRFC Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 15
Attempts 30

Pause 300
d. Choose Continue.
3. Register display programs for the inbound queue in SAP ERP. This function enables you to display the data
of a queue entry by double-clicking the queue name or to display the application log of a queue entry by
double-clicking the status text in the qRFC monitor for inbound queues. This setting is relevant for the
qRFC communication from EWM to SAP ERP.
a. In the SAP ERP system, on the SAP Easy Access screen, call transaction SMQE.
b. Choose Edit ® Register Display Program.
c. Enter the queue and program names as shown in the following table:

Queue Name Program Name

DLW* /SPE/QUEUE_DISPLAY_TOOLS

EWM* /SPE/QUEUE_DISPLAY_TOOLS

QI* /SPE/QUEUE_DISPLAY_TOOLS

QM* /SPE/QUEUE_DISPLAY_TOOLS

WM* /SPE/QUEUE_DISPLAY_TOOLS
4. Configure the queue for the communication of transaction data from SAP ERP to EWM.
a. In Customizing for Integration with Other SAP Components , choose Extended Warehouse
Management ® Basic Settings for EWM Linkage ® Define Queue for Transfer to Extended WM.
b. Create an entry for the EWM logical system with the following data:

Field Value

<logical system>, for example,

Receiver
EWMCLNT001
Queue Inbound queue

Agg SQueue No aggregation

Mass queue disabled (=> Single
MQueue Act
queues)
MQueue Par 1
For more information, see the value help of the single fields.
5. Activate the automatic restart of erroneous inbound queues from EWM to SAP ERP.
With this setting, inbound queues in SAP ERP that are erroneous due to locking issues will be restarted
automatically again up to 25 times.
a. In Customizing for Logistics Execution , choose Shipping ® System Modifications ® Specify
Characteristics for System Messages.
b. Choose activity Define the message types of system messages.
Create a new entry with the following attributes:

Field Value

Call Type Leave this field empty.

Activity Leave this field empty.

Application Area /SPE/IF_SERVICES

Message Number 023

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of qRFC Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 16
Message Type E
c. Save your entries.
6. Check that the log for received messages is not disabled in Customizing for Integration with Other SAP
Components under Extended Warehouse Management ® Basic Settings for EWM Linkage ® Log Sent and
Received Messages.

5.2 Configuring qRFC Communication in Decentralized EWM

You use this procedure to setup the qRFC communication in decentralized EWM, i.e. to send transactional data to
SAP ERP and to receive transactional data from SAP ERP.
The procedure describes the basic setup for the qRFC communication using inbound queues in both directions.
As an alternative you can use outbound queues for the communication from EWM to SAP ERP to monitor both
communication channels (from SAP ERP to EWM and from EWM to SAP ERP) on the EWM side.

Procedure
Carry out the following steps in each EWM client you want to connect to SAP ERP.
...

1. Register the RFC destination for SAP ERP in the QOUT scheduler in EWM. This setting is relevant for the
qRFC communication from EWM to SAP ERP.
a. In the EWM 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

<RFC Destination>, for example,

Destination
ERPCLNT001
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 SAP ERP to EWM.
a. In the SAP ERP system, on the SAP Easy Access screen, call transaction SMQR.
b. On the qRFC Monitor (QIN Scheduler) screen, choose Registration.
c. Enter the data as shown in the following table:

Field Value

Queue Name <used queue name>, we recommend that you

use either * or any of the following: DLV*, PR*,
QI*, QM*, TU*, UL*, WM*, X*

Mode D

Max. Runtime 60

USERDEST Leave this field empty.

Attempts 30

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of qRFC Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 17
Pause 300
d. Choose Continue.
3. Register display programs for the inbound queue in EWM. This function enables you to display the data of a
queue entry by double-clicking the queue name or to display the application log of a queue entry by double-
clicking the status text in the qRFC monitor for inbound queues.
a. In the EWM system, on the SAP Easy Access screen, call transaction SMQE.
b. Choose Edit ® Register Display Program.
c. Enter the queue and program names as shown in the following table:

Queue Name Program Name

DLV* /SCWM/QRFC_APPL_LOG_DISPLAY

PR* /SCWM/QRFC_DISP_QIN_LOG_PROD

QI* QIE_RFC_DISPLAY_QUEUE_LOG

QM* QIE_RFC_DISPLAY_QUEUE_LOG

TU* /SCWM/QRFC_APPL_LOG_DISPLAY

UL* /SCWM/QRFC_APPL_LOG_DISPLAY

WM* /SCWM/QRFC_APPL_LOG_DISPLAY

X* RSXMB_SHOW_ENTRY
4. Configure the queue for the communication of transaction data from SAP ERP to EWM.
a. In Customizing for Extended Warehouse Management, choose Interfaces ® ERP Integration ®
General Settings ® Control for RFC Queue.
b. Create an entry for the SAP ERP business system with the following data:

Field Value

Business System <business system>, for example, ERP_001

Queue Type Inbound queue

Aggr. Single Queues No aggregation

Mass Queue Deactivated (=>
Mass Queue Act.
Individual Queue)
Parallel Mass Queues

For more information, see the value help of the single fields.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of qRFC Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 18
6 Configuration of IDoc Communication
You use this process to setup the distribution of following master data from SAP ERP to decentralized EWM on
SAP S/4HANA using SAP Standard technology Application Link Enabling (ALE)-IDoc:
· Materials
· Customers
· Vendors and Carriers
· Addresses
· Batches
· Class system: Characteristics master
· Class system: Classes master
· Class system: Classification master

The master data distribution is always from SAP ERP to decentralized EWM. In the IDoc settings, the sender
system is always SAP ERP and the receiver system is always decentralized EWM.

Note
Even if you use the Customer Vendor Integration (CVI) in SAP ERP, the transfer of customer and
vendor data via ALE to decentralized EWM is based on the customer and vendor master data and
not on the business partner master data.

Important
Some settings described in this chapter, such as the creation of reduced message types with
transaction BD53, require a workbench request. You must therefore clarify with your system
administrator which SAP ERP system and client is appropriate to carry out these steps.

Note
This process contains only an example for the ALE IDoc setup. For more information, refer to the
ALE implementation guide.

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.

6.1 Creating Port for IDoc Processing in Sender System

You use this procedure to create a port for the receiver system in the sender system.

Procedure
...

1. In SAP ERP, call transaction WE21(Ports in IDoc Processing)

2. Select the port type Transactional RFC and press Create.
3. Choose own port name and enter a port name for the EWM client, for example EWMCLNT001.
4. On the next screen, enter the RFC destination, for example EWMCLNT001 and select the processing option
Use SAP Release of Receiving System in Control Record .
5. Save the entry. You will be prompted to enter a transport request for the new message type.

6.2 Creating Reduced Message Types

You use this procedure to select segments and fields of the basic types for master data that you want to
distribute. By reducing the number of segments and fields, you also reduce the number of customizing tables
(containing allowed field values for master data) that need to be synchronized between both systems.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 19
Basic types for master data are supplied in the standard SAP System. If you want to reduce the basic types, you
use transaction BD53 to select the segments and fields that you want to distribute. To do this you activate the
segments and fields that you require and generate a new message type.
Mandatory segments and mandatory fields cannot be deactivated.

Note
If you change a reduced message type after you have set up filters, some entries may be reset. In
this case, you will receive a warning in transaction BD53. You should then test the transfer again.
For example, you must check new entries in transaction BD59 as they may be removed in case of
changes of an existing reduced message type.

6.2.1 Creating a Reduced Message Type for MATMAS

You use this procedure to create a reduced message type based on the basis message type MATMAS for the
distribution of material master data to decentralized EWM.

Note
The list of segments and fields mentioned below is just a proposal. It shows a minimum set of fields
EWM requires for main processes. Dependent on your requirements you may add/remove
segments or fields. If you add a new field, check whether allowed values for this field are defined in a
customizing table. If yes, entries for the table are also needed in decentralized EWM.

Procedure
...

1. In SAP ERP, call transaction BD53 (IDoc Reduction Maintenance ).

2. Enter a name for the reduced message type, for example ZEWMMATMAS and press Create.
3. Enter MATMAS as message type reference and press Continue
4. Enter a description for the reduced message type, for example Reduced MATMAS (Material) for decentral
EWM and press Continue.
5. On the next screen, select the following segments:
¡ E1MARAM (already selected as it is mandatory)
¡ E1MARA1
¡ E1MAKTM (already selected as it is mandatory)
¡ E1MARCM
¡ E1MARMM with sub-segment E1MEANM
6. Select the fields for each segment as proposed in the tables below. Mandatory fields are already selected.
7. Save your entries. You will be prompted to enter a transport request for the new message type.
8. The reduced message type was created as a cross-client object, but it cannot yet be used. Before the
reduced message type can be used, it must be activated for each client in the initial screen of the reduction.
This must also be done if new changes are made to a reduced message type.

The following tables contain a proposal for segments and fields to be distributed to decentralized EWM:

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 20
Fields from Segment E1MARAM Description
MSGFN (mandatory) Function
MATNR (mandatory) Material Number
ERSDA Created On
LAEDA Date of Last Change
PSTAT (mandatory) Maintenance status
LVORM (mandatory) Flag Material for Deletion at Client Level
MTART (mandatory) Material Type
MBRSH (mandatory) Industry Sector
MATKL (mandatory) Material Group
MEINS (mandatory) Base Unit of Measure
BSTME Purchase Order Unit of Measure
GROES (mandatory) Size/dimensions
WRKST (mandatory) Basic material (basic constituent of a material) - obsolete
BRGEW Gross Weight
NTGEW Net Weight
GEWEI Weight Unit
VOLUM Volume
VOLEH Volume Unit
BEHVO Container requirements
RAUBE Storage conditions
TEMPB Temperature conditions indicator
TRAGR Transportation Group
STOFF Hazardous material number
SPART (mandatory) Division
ETIAR Label type
ETIFO Label form
EAN11 International Article Number (EAN/UPC)
NUMTP Category of International Article Number (EAN)
LAENG Length
BREIT Width
HOEHE Height
MEABM Unit of Dimension for Length/Width/Height
PRDHA Product Hierarchy
ERGEW Allowed packaging weight
ERGEI Weight Unit
ERVOL Allowed packaging volume
ERVOE Volume Unit
GEWTO Excess Weight Tolerance for Handling unit

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 21
VOLTO Excess Volume Tolerance of the Handling Unit
KZKFG Configurable Material
XCHPF Batch management requirement indicator
VHART Packaging Material Type
FUELG Maximum level (by volume)
STFAK Stacking factor
MAGRV Material Group: Packaging Materials
BEGRU Authorization Group
QMPUR QM in Procurement is Active
MHDRZ Minimum Remaining Shelf Life
MHDHB Total shelf life
MHDLP Storage percentage
VPSTA (mandatory) Maintenance status of complete material
KZUMW Environmentally Relevant
KOSCH Product allocation determination procedure
PROFL Dangerous Goods Indicator Profile
KZGVH Packaging Material is Closed Packaging
COMPL Material completion level
RDMHD Rounding rule for calculation of SLED
IPRKZ Period Indicator for Shelf Life Expiration Date
MTPOS_MARA General item category group
MATFI Material Is Locked
SATNR Cross-Plant Configurable Material
SLED_BBD Expiration Date
MATNR_LONG Material Number (40 Characters, needed f. technical reasons)

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 22
Fields from Segment E1MARA1 Description
HUTYP_DFLT Standard HU Type
PILFERABLE Pilferable
WHSTC Warehouse Storage Condition
WHMATGR Warehouse Material Group
HNDLCODE Handling Indicator
HAZMAT Relevant for Hazardous Substances
HUTYP Handling Unit Type
TARE_VAR Variable Tare Weight
MAXC Maximum Allowed Capacity of Packaging Material
MAXC_TOL Overcapacity Tolerance of the Handling Unit
MAXL Maximum Packing Length of Packaging Material
MAXB Maximum Packing Width of Packaging Material
MAXH Maximum Packing Height of Packaging Material
MAXDIM_UOM Unit of Measure for Maximum Packing Length/Width/Height
HERKL Country of Origin of Material (Non-Preferential Origin)
MFRGR Material freight group
QQTIME Quarantine Period
QQTIMEUOM Time Unit for Quarantine Period
QGRP Quality Inspection Group
SERIAL Serial Number Profile
PS_SMARTFORM Form Name
CWQPROC EWM CW: Catch Weight Profile for Entering CW Quantity
CWQTOLGR EWM-CW: Catch Weight Tolerance Group for EWM
ADPROF Adjustment Profile

Fields from Segment E1MAKTM Description

MSGFN (mandatory) Function
SPRAS (mandatory) Language Key
MAKTX (mandatory) Material Description

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 23
Fields from Segment E1MARCM Description
MSGFN (mandatory) Function
WERKS (mandatory) Plant
PSTAT (mandatory) Maintenance status
LVORM Deletion Indicator
SSQSS QA Control Key
XCHPF Batch management requirement indicator
PRFRQ Character Field With Field Length 7

Fields from Segment E1MARAMM Description

MSGFN (mandatory) Function
MEINH (mandatory) Alternative Unit of Measure for Stockkeeping Unit
UMREZ Numerator for Conversion to Base Units of Measure
UMREN Denominator for conversion to base units of measure
EAN11 International Article Number (EAN/UPC)
NUMTP Category of International Article Number (EAN)
LAENG Length
BREIT Width
HOEHE Height
MEABM Unit of Dimension for Length/Width/Height
VOLUM Volume
VOLEH Volume Unit
BRGEW Gross Weight
GEWEI Weight Unit
GTIN_VARIANT Global Trade Item Number Variant
/CWM/TY2TQ Type of Parallel Unit of Measure
NEST_FTR Remaining Volume after Nesting (in Percentage)
MAX_STACK Maximum Stacking Factor
CAPAUSE Capacity Usage

Fields from Segment E1MEANM Description

MSGFN (mandatory) Function
MEINH (mandatory) Unit of Measure for Display
LFNUM (mandatory) Consecutive Number
EAN11 International Article Number (EAN/UPC)
EANTP Category of International Article Number (EAN)
HPEAN Indicator: Main EAN

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 24
6.2.2 Creating a Reduced Message Type for DEBMAS
You use this procedure to create a reduced message type based on the basis message type DEBMAS for the
distribution of customer master data to decentralized EWM.

Note
The list of segments and fields mentioned below is just a proposal. It shows a minimum set of fields
EWM requires for main processes. Dependent on your requirements you may add/remove
segments or fields. If you add a new field, check whether allowed values for this field are defined in a
customizing table. If yes, entries for the table are also needed in decentralized EWM.

Procedure
...

1. In SAP ERP, call transaction BD53 (IDoc Reduction Maintenance ).

2. Enter a name for the reduced message type, for example ZEWMDEBMAS and press Create.
3. Enter DEBMAS as message type reference and press Continue
4. Enter a description for the reduced message type, for example Reduced DEBMAS (Customer) for decentral
EWM and press Continue.
5. On the next screen, select the following segments:
¡ E1KNA1M (already selected as it is mandatory)
¡ E1KNA11
6. Select the fields for each segment as proposed in the tables below. Mandatory fields are already selected.
7. Save your entries. You will be prompted to enter a transport request for the new message type.
8. The reduced message type was created as a cross-client object, but it cannot yet be used. Before the
reduced message type can be used, it must be activated for each client in the initial screen of the reduction.
This must also be done if new changes are made to a reduced message type.

The following tables contain a proposal for segments and fields to be distributed to decentralized EWM:
Fields from Segment E1KNA1M Description
MSGFN (mandatory) Function
KUNNR (mandatory) Customer Number
ANRED (mandatory) Title
KTOKD (mandatory) Customer Account Group
LAND1 (mandatory) Country Key
LIFNR Account Number of Vendor or Creditor
LOEVM (mandatory) Central Deletion Flag for Master Record
NAME1 (mandatory) Name 1
NAME2 (mandatory) Name 2
ORT01 (mandatory) City
ORT02 (mandatory) District
PFACH (mandatory) PO Box
PSTL2 (mandatory) P.O. Box Postal Code
PSTLZ (mandatory) Postal Code
REGIO Region (State, Province, County)
SORTL (mandatory) Sort field
SPRAS (mandatory) Language Key

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 25
STRAS (mandatory) Street and House Number
TELF1 First telephone number
TELFX Fax Number

Fields from Segment E1MKNA11 Description

CVP_XBLCK Business Purpose Completed Flag

6.2.3 Creating a Reduced Message Type for CREMAS

You use this procedure to create a reduced message type based on the basis message type CREMAS for the
distribution of vendor and carrier master data to decentralized EWM.

Note
The list of segments and fields mentioned below is just a proposal. It shows a minimum set of fields
EWM requires for main processes. Dependent on your requirements you may add/remove
segments or fields. If you add a new field, check whether allowed values for this field are defined in a
customizing table. If yes, entries for the table are also needed in decentralized EWM.

Procedure
...

1. In SAP ERP, call transaction BD53 (IDoc Reduction Maintenance ).

2. Enter a name for the reduced message type, for example ZEWMCREMAS and press Create.
3. Enter CREMAS as message type reference and press Continue
4. Enter a description for the reduced message type, for example Reduced CREMAS (Vendor) for decentral
EWM and press Continue.
5. On the next screen, select the following segments:
¡ E1LFA1M (already selected as it is mandatory)
¡ E1LFA1A
6. Select the fields for each segment as proposed in the tables below. Mandatory fields are already selected.
7. Save your entries. You will be prompted to enter a transport request for the new message type.
8. The reduced message type was created as a cross-client object, but it cannot yet be used. Before the
reduced message type can be used, it must be activated for each client in the initial screen of the reduction.
This must also be done if new changes are made to a reduced message type.

The following tables contain a proposal for segments and fields to be distributed to decentralized EWM:
Fields from Segment E1LFA1M Description
MSGFN (mandatory) Function
LIFNR (mandatory) Account Number of Vendor or Creditor
KTOKK (mandatory) Vendor account group
KUNNR Customer Number
LAND1 (mandatory) Country of Company
LOEVM Central Deletion Flag for Master Record
NAME1 (mandatory) Employee's last name
ORT01 (mandatory) City
PSTL2 (mandatory) Postal Code
PSTLZ (mandatory) Postal Code

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 26
SORTL (mandatory) Character Field Length = 10
SPRAS (mandatory) Language Key
STRAS Street and House Number
SPERQ Function That Will Be Blocked
ADRNR Address
SCACD Standard carrier access code

Fields from Segment E1LFA1A Description

CVP_XBLCK Business Purpose Completed Flag

6.2.4 Transporting Reduced Message Types to Decentralized

EWM
After activation, ask your system administrator to transport the reduced message types to the decentralized
EWM system by means of a transport request.

6.3 Defining Data Distribution Model and Distributing Views

You use this procedure to define the messages in the distribution model in the sender system.

6.3.1 Creating New Filter Object Types

You use this procedure to define new filter object types for the reduced message types. In the following example,
you define the account group as new filter object type for vendor and customer distribution. You will use the new
filter object type later to define filters in the distribution model.

Note
Skip this chapter if you do not need additional filters for the reduced message types.

Procedure
Carry out the following steps in an SAP ERP client allowing cross-client customizing changes.
...

1. To create a new filter object type for vendor distribution, call transaction BD59 (Allocation object type ->
IDoc type) in SAP ERP.
2. Enter the reduced message type for vendor distribution, for example ZEWMCREMAS and press Continue.
Create a new entry with the data as shown in the following table:

Field Value

ALE Object Type KTOKK (Account Group)

Segment Type E1LFA1M

3. Enter the reduced message type for customer distribution, for example ZEWMDEBMAS and press Continue.
Create a new entry with the data as shown in the following table:

Field Value

ALE Object Type KTOKD (Account Group)

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 27
Segment Type E1KNA1M

4. Save your entries.

6.3.2 Checking Filter Dependencies

You use this procedure to check filter dependencies between message types such as materials and batches. The
entries are needed later to define filters in the distribution model.

Procedure
...

1. In SAP ERP, call transaction BD71 (Define FM for dependent bus. object).
2. Check that the following entry exist:

Field Value

Object Type BUS1001006

FM for filter objects MATERIAL_FILTEROBJ_GET_VALUE

If the entry is missing, refer to SAP note 709550.

3. In SAP ERP, call transaction SM30 to display view V_TBD16.
Check that the following entry exist:

Field Value

Object Type BUS1001002

Method SAVEREPLICA

Filter object type MATNR

If the entry is missing, refer to SAP note 2745236.

4. In SAP ERP, call transaction BD48 (Dependency method - message).
5. Check that the following entry exist:

Field Value

Object Type BUS1001002

Method SAVEREPLICA

Ref. message type MATMAS

Filter object type MATNR

6.3.3 Creating Data Distribution Model

You use this procedure to create a data distribution model.

Procedure
...

1. In SAP ERP, call transaction BD64 (Maintenance of Distribution Model).

2. Choose Distribution Model ® Switch Processing Mode.
3. To create a new model view, press Create Model View.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 28
Enter the data as shown in the following table:

Field Value

For example, EWMCLNT001: decentralized EWM

Short Text
(replace EWMCLNT001 with the logical system name for decentralized EWM)
For example, EWMCLNT001
Technical Name
(replace EWMCLNT001 with the logical system name for decentralized EWM)
Press Continue.
4. To add message types to the model, select the new model on the list and press Add Message Type.
For each message type, enter the data as shown in the following table:

Field Value

Sender <ERP logical system>, for example, ERPCLNT001

Receiver <EWM logical system>, for example, EWMCLNT001

Message Type See list of message types below

The following message types are needed:

¡ Reduced message type for vendors, for example ZEWMCREMAS
¡ Reduced message type for customers, for example ZEWMDEBMAS
¡ Reduced message type for materials, for example ZEWMMATMAS
If you use batches, you also need the following message types:
¡ CHRMAS: Class system: Characteristics master
¡ CLSMAS: Class system: Classes master
¡ CLFMAS: Class system: Classification master

5. Batches must be distributed using BAPI instead of messages type BATMAT. To add a BAPI for batch
distribution to the model, select the new model on the list and press Add BAPI.
Enter the data as shown in the following table:

Field Value

Sender/client <ERP logical system>, for example, ERPCLNT001

Receiver/server <EWM logical system>, for example, EWMCLNT001

Obj. Name/Interface Batch

Method SaveReplica

6. Addresses must be distributed using BAPI instead of messages type ADRMAS. To add a BAPI for address
distribution to the model, select the new model on the list and press Add BAPI.
Enter the data as shown in the following table:

Field Value

Sender/client <ERP logical system>, for example, ERPCLNT001

Receiver/server <EWM logical system>, for example, EWMCLNT001

Obj. Name/Interface AddressOrg

Method SaveReplica

7. To create a filter group for the reduced message type for materials, for example ZEWMMATMAS, double-
click No filter set or Data Filter Active under message type ZEWMMATMAS in the tree, then press Create
Filter Group on the dialog box.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 29
You can, for example, filter the materials to be distributed to decentralized EWM by plant. For this purpose,
double-click filter object type Plant and enter the plants that will be linked to a decentralized EWM
warehouse.
You can also filter the materials by material type or material group.

Important
The plant filter defined in this step will only prevent the distribution of plant-specific material master
data (table MARC). If you want to filter the distribution of the complete material master by plant,
you must implement BAdI IDOC_CREATION_CHECK. Refer to the appendix for an example
implementation of this BAdi.

Press Continue.
8. To create a filter group for reduced message type for vendors, for example ZEWMCREMAS, double-click No
filter set or Data Filter Active under message type ZEWMCREMAS in the tree, then press Create Filter
Group on the dialog box.
You can, for example, filter the vendors and carriers to be distributed to decentralized EWM by account
group. For this purpose, double-click filter object type Account group, and enter the account groups you
use for vendors and carriers working with the decentralized warehouse, for example 0005 and LIEF.
Press Continue.
9. To create a filter group for reduced message type for customers, for example ZEWMDEBMAS, double-click
No filter set or Data Filter Active under message type ZEWMDEBMAS in the tree, then press Create Filter
Group on the dialog box.
You can, for example, filter the customers to be distributed to decentralized EWM by account group. For
this purpose, double-click filter object type Account group, and enter the account groups you use for
customers working with the decentralized warehouse, for example KUNA.
Press Continue.
10. To create filter groups for BAPI method AddressOrg.SaveReplica (addresses), double-click Receiver
determination under BAPI AddressOrg.SaveReplica in the tree, then press Create Filter Group on the dialog
box.
In the dialog box, create two filter groups. In the one group, select the message type ZEWMCREMAS. In the
second group, select the message type ZEWMDEBMAS. Two groups are needed to achieve an OR
expression between both message types.
11. To create a filter group for BAPI method Batch.SaveReplica (batches), double-click Receiver determination
under BAPI Batch.SaveReplica in the tree, then press Create Filter Group on the dialog box.
You can re-use the same filter logic defined for message type ZEWMMATMAS for filtering batches via
dependency. For this purpose, select attribute Dependent Distribution for message type ZEWMMATMAS in
the same dialog box.
Press Continue.
12. To create a filter group for message type CLSMAS (classes), double-click No filter set or Data Filter Active
under message type CLSMAS in the tree, then press Create Filter Group on the dialog box.
Double-click filter object type Class Type and enter the class types 022 and 023 for batch classes.
Press Continue.
13. To create a filter group for message type CLFMAS (classifications), double-click No filter set or Data Filter
Active under message type CLFMAS in the tree, then press Create Filter Group on the dialog box.
Double-click filter object type Class Type and enter the class types 022 and 023 for batch classes.
To ensure that only classifications for existing materials are transferred, select attribute Dependent
Distribution for message type ZEWMMATMAS in the same dialog box.
Press Continue.
14. Save the distribution model.
15. Choose Edit ® Model view ® Distribute to transport the distribution model to other systems.

6.4 Defining Partner Profile

You can generate the partner profile within transaction BD64 automatically or create it using transaction WE20
manually. You use this procedure to create the partner profile manually.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 30
6.4.1 Creating Partner Profile in Sender System Manually
You use this procedure to create a partner profile in the sender system (SAP ERP).

Procedure
...

1. In SAP ERP, call transaction WE20 (Partner Profiles).

2. Press Create.
Enter the data as shown in the following table:

Field Value

Partner No. <EWM logical system>, for example, EWMCLNT001

Partner Type LS

Ty. (Post processing) US (User)

Agent <RFC User>

Language EN

3. Save the profile

4. Add a new line to create outbound parameters for message type CHRMAS.
Enter the data as shown in the following table:

Field Value

Message Type CHRMAS

Receiver Port <EWM port>, for example, EWMCLNT001

Output Mode Pass IDoc Immediately

Basic Type Use value help and select the last entry from the list, for example CHRMAS05

Package Size 100

Cancel Processing
X
After Syntax Error

5. Save your data.

6. Repeat steps 4 and 5 for the following message types:
¡ CLSMAS
¡ CLFMAS
¡ ADRMAS
¡ Reduced message type for materials, for example ZEWMMATMAS
¡ Reduced message type for vendors, for example ZEWMCREMAS
¡ Reduced message type for customers, for example ZEWMDEBMAS
¡ BATMAS

6.4.2 Creating Partner Profile in Receiver System Manually

You use this procedure to create a partner profile in the receiver system (decentralized EWM).

Procedure
...

1. In decentralized EWM, call transaction WE20 (Partner Profiles).

2. Press Create.
Enter the data as shown in the following table:

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 31
Field Value

Partner No. <ERP logical system>, for example, ERPCLNT001

Partner Type LS

Ty. (Post processing) US (User)

Agent <RFC User>

Language EN

3. Save the profile

4. Add a new line to create inbound parameters for message type CHRMAS.
Enter the data as shown in the following table:

Field Value

Message Type CHRMAS

Process Code CHRM

Cancel Processing
X
After Syntax Error

Trigger Immediately X

5. Save your data.

6. Repeat steps 4 and 5 for the following message types:
¡ CLSMAS with process code CLSM
¡ CLFMAS with process code CLFM
¡ ADRMAS with process code BAPI
¡ Reduced message type for materials, for example ZEWMMATMAS, with process code MATM
¡ Reduced message type for vendors, for example ZEWMCREMAS, with process code CRE1
¡ Reduced message type for customers, for example ZEWMDEBMAS, with process code DEBM
¡ BATMAS with process code BAPI

6.5 Converting Data Between Sender and Receiver

Field PSTAT (Maintenance Status) of segments E1MARAM and E1MARCM defines which views of a material are
maintained in the sender system. Due to the reduction of the message type, only a subset of all fields and
maintained views are transferred to decentralized EWM. This can lead to errors during MATMAS inbound
processing in the receiver system as the system detects that a view should be maintained but the relevant fields
are not transferred.
To avoid this, you need to adjust the values of fields PSTAT and VPSTA (Maintenance Status of complete
material) to be transferred.
You have two options to adjust the transferred field values:
· Set a fixed value using conversion rules. This can be used if the materials have the same views maintained.
· Set flexible values using a BAdI implementation. As the material views often depends on the material types,
you cannot use a common fixed value. In this case, you use a BAdI implementation to set flexible values.
In this example, a combination is done also to illustrate both options:
· For MARC-PSTAT, a fixed value is set (as here less complex combinations occur)
· For MARA-PSTAT, a BAdI implementation is used.
In customer projects, choose the option fitting to your requirements.

6.5.1 Converting Data Using Conversion Rules

You use this procedure to convert data between sender and receiver system using conversion rules.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 32
Procedure
Carry out the following steps in SAP ERP:
...

1. Create a conversion rule in Customizing for SAP NetWeaver under Application Server ® IDoc Interface /
Application Link Enabling (ALE) ® Modelling and Implementing Business Processes ® Converting Data
Between Sender and Receiver ® Create Rule.
Enter the data as shown in the following table:

Field Value

Conversion rule Enter a name for conversion rule, for example ZEWM_PSTAT_MARC

Description Set constant for PSTAT (MARC)

IDoc segment name E1MARCM

Save your entries.
2. Maintain the conversion rule in Customizing for SAP NetWeaver under Application Server ® IDoc Interface
/ Application Link Enabling (ALE) ® Modelling and Implementing Business Processes ® Converting Data
Between Sender and Receiver ® Maintain Rules.
Choose Maintain and enter constant Q (Quality Management View) for field PSTAT.
Save your entries.
3. Assign the conversion rule to the reduced message type, for example ZEWMMATMAS, in Customizing for
SAP NetWeaver under Application Server ® IDoc Interface / Application Link Enabling (ALE) ® Modelling
and Implementing Business Processes ® Converting Data Between Sender and Receiver ® Assign Rule to
Message Type.
Enter reduced message type, for example ZEWMMATMAS, and press Continue.
Create a new entry and enter the data as shown in the following table:

Ent er th e da ta as s how n in the follo wing ta ble:

Field Value

Ty, (Sender) LS

Sender ERPCLNT001

Ty, (Receiver) LS

Receiver EWMCLNT001

Segment Type E1MARCM

Enter name of conversion rule from step 1, for example
Conversion Rule
ZEWM_PSTAT_MARC
Save your e ntr ies.

Save your entry.

6.5.2 Converting Data via BAdI

Instead of using the approach to set a fixed value to PSTAT and VPSTA, another option is to use a BAdI
implementation.
This can be done by multiple ways.
· on the sending side using BAdI BADI_MATMAS_ALE_CR, method CHANGE_MATMAS
· on the receiving side using BAdI BADI_MATMAS_ALE_IN, method CHANGE_UEB_TAB.

Refer to the appendix for an example implementation of BAdI BADI_MATMAS_ALE_CR.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 33
Tip
As an alternative to the BAdI implementation, you can create a conversion rule for fields PSTAT and
VPSTA of the E1MARAM segment as described in the previous chapter, setting the values for both
fields to the needed material master views, for example KLEVQ (K = Basic data, L = Storage, E =
Purchasing, V = Sales, Q = Quality Management).

6.6 Activating Change Pointers in Sender System

Change pointers are used for logging changes of master data. Change pointers must be activated in the system to
be used. The loggings can be used to created IDoc for a delta transfer.

6.6.1 Activating Change Pointers at Client Level

You use this procedure to activate change pointers at client level.

Procedure
Activate change pointers at client level in Customizing for SAP NetWeaver under Application Server ® IDoc
Interface / Application Link Enabling (ALE) ® Modelling and Implementing Business Processes ® Master Data
Distribution ® Replication of Modified Data ® Activate Change Pointers - Generally in SAP ERP.

6.6.2 Activating Change Pointers per Message Type

You use this procedure to activate change pointers for all message types assigned to your distribution model. The
change pointers are needed to log changes to the master data and distribute them to the receiver system.

Procedure
Carry the following steps in SAP ERP:
1. Activate change pointers for the following reduced message types:
¡ Reduced message type for vendors, for example ZEWMCREMAS
¡ Reduced message type for customers, for example ZEWMDEBMAS
¡ Reduced message type for materials, for example ZEWMMATMAS
For this purpose, call transaction BD53, enter a reduced message type, and press Activate change
pointers.

2. Activate change pointers for the following message types in Customizing for SAP NetWeaver under
Application Server ® IDoc Interface / Application Link Enabling (ALE) ® Modelling and Implementing
Business Processes ® Master Data Distribution ® Replication of Modified Data ® Activate Change
Pointers for Message Types:
¡ CHRMAS: Class system: Characteristics master
¡ CLSMAS: Class system: Classes master
¡ CLFMAS: Class system: Classification master
¡ BATMAS: Batch
¡ ADRMAS: Address

Important
The activation of change pointers per message type creates entries for the fields of the message
type in another table. For batches (message type BATMAS) it might happen that an entry for the
batch status is missing as this depends on the setup of the system whether batch status
management is activated or not. To verify this, start transaction BD52 for message type BATMAS
and check that an entry exists for object CHARGE, table name MCHA, field name ZUSTD.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Configuration of IDoc Communication © 2019 SAP AG or an SAP affiliate company. All rights reserved. 34
7 Customizing Settings in Decentralized
EWM
7.1 Checking Basic Table Entries in EWM
Basic tables like units of measures, currencies, countries, and languages are used both in SAP ERP and in
decentralized EWM. You use this procedure to check that the entries (especially the ISO codes) needed in the
warehousing processes are identical in all systems that are part of your system landscape.

Procedure
Carry out the following steps in your EWM customizing client.
1. On the SAP Easy Access screen, choose Tools ® Administration ® Administration ® Client Administration
® Customizing Objects ® Object Comparison.
2. Compare the information in the following tables between the EWM client and the ERP customizing client.
Compare the entries you plan to use in your warehousing processes. Adjust the tables in SAP ERP or EWM
Customizing, if necessary.

View/Table Description Usage in Decentralized EWM

T002 Language keys Material master and others
T005 Countries Material master and others
T006 Unit of measure Material master and others
TCURC Currency codes Material valuation data

7.2 Configuring Customer/Vendor Integration in EWM

You use this procedure to configure settings for vendors and customers in decentralized EWM.
In decentralized EWM, a business partner exists for every vendor or customer by means of the Customer/Vendor
Integration (CVI), which is always active in an SAP S/4HANA system.
When a vendor or customer is distributed via IDoc to a decentralized EWM system, the system automatically
creates a business partner in addition to the vendor or customer master data and links the business partner to the
vendor or the customer.
The settings described in this procedure are necessary for the replication of the vendor or customer master data
and for the Customer/Vendor Integration.

Note
You can find the settings related to Customer/Vendor Integration in Customizing for Cross-
Application Components under Master Data Synchronization ® Customer/Vendor Integration.

Procedure
Carry out the following steps in your EWM customizing client.

1. Set BP Role Category for Direction BP to Customer (view V_TBD002)

In Customizing for Customer/Vendor Integration, choose Business Partner Settings ® Settings for
Customer Integration ® Set BP Role Category for Direction BP to Customer.
If they do not exist yet, create the following entries:

BP Role Category Description Customer-Based

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Customizing Settings in Decentralized EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 35
FLCU00 Business Partner FI Customer (FS: BP) X

FLCU01 Business Partner Customer (FS: BP) X

Save your entries.

2. Define BP Role for Direction Customer to BP (view CVIV_CUST_TO_BP2)

In Customizing for Customer/Vendor Integration, choose Business Partner Settings ® Settings for
Customer Integration ® Define BP Role for Direction Customer to BP.
If they do not exist yet, create the following entries, for example:

Group BP Role

DEBI FLCU00

DEBI FLCU01

KUNA FLCU00

KUNA FLCU01
Save your entries.

3. Define Number Assignment for Direction BP to Customer (view V_TBD001)

In Customizing for Customer/Vendor Integration, choose Business Partner Settings ® Settings for
Customer Integration ® Field Assignment for Customer Integration ® Assign Keys ® Define Number
Assignment for Direction BP to Customer.
If they do not exist yet, create the following entries, for example:

Grouping Account Group Same Numbers Flexible Grouping

0001 DEBI X

0002 KUNA X

GPEX DEBI X

GPIN DEBI X

Save your entries.

4. Define Number Assignment for Direction Customer to BP (view CVIV_CUST_TO_BP1)

In Customizing for Customer/Vendor Integration, choose Business Partner Settings ® Settings for
Customer Integration ® Field Assignment for Customer Integration ® Assign Keys ® Define Number
Assignment for Direction Customer to BP.
If they do not exist yet, create the following entries, for example:

Account Group Grouping Same Numbers

DEBI 0001

KUNA 0002 X

Save your entries.

5. Set BP Role Category for Direction BP to Vendor (view V_TBC002)

In Customizing for Customer/Vendor Integration, choose Business Partner Settings ® Settings for Vendor
Integration ® Set BP Role Category for Direction BP to Vendor.
If they do not exist yet, create the following entries:

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Customizing Settings in Decentralized EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 36
BP Role Category Description Vendor-Based

BBP000 Vendor X

CRM010 Carrier X

FLVN00 Business Partner FI Vendor (FS: BP) X

FLVN01 Business Partner Vendor (FS: BP) X

Save your entries.

6. Define BP Role for Direction Vendor to BP (view CVIV_VEND_TO_BP2)

In Customizing for Customer/Vendor Integration, choose Business Partner Settings ® Settings for Vendor
Integration ® Define BP Role for Direction Vendor to BP.
If they do not exist yet, create the following entries, for example:

Group BP Role

0005 CRM010

KRED BBP000

KRED FLVN01

LIEF BBP000

KRED FLVN01
Save your entries.

7. Define grouping for carriers (view V_TB001)

Call transaction SM30 to maintain view V_TB001.
Copy grouping 0002 to a new grouping, for example ZCRR.
8. Define Number Assignment for Direction BP to Vendor (view V_TBC001)
In Customizing for Customer/Vendor Integration, choose Business Partner Settings ® Settings for Vendor
Integration ® Field Assignment for Vendor Integration ® Assign Keys ® Define BP Role for Direction
Vendor to BP.
If they do not exist yet, create the following entries, for example:

Grouping Account Group Same Numbers Flexible Grouping

0001 KRED

0002 LIEF X

GPEX LIEF

GPIN KRED

ZCRR 0005 X

Save your entries.

9. Define Number Assignment for Direction Vendor to BP (view CVIV_VEND_TO_BP1)

In Customizing for Customer/Vendor Integration, choose Business Partner Settings ® Settings for Vendor
Integration ® Field Assignment for Vendor Integration ® Assign Keys ® Define Number Assignment for
Direction Vendor to BP.
If they do not exist yet, create the following entries, for example:

Account Group Grouping Same Numbers

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Customizing Settings in Decentralized EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 37
0005 ZCRR X

KRED 0001

LIEF 0002 X

Save your entries.

7.3 Activating BC Sets for Client-Dependent Number Ranges

You use this procedure to create number ranges for the following objects in EWM:
· Packaging specifications
· Transportation units, vehicles and Shipping & Receiving activities
· ERP delivery documents created from EWM
· QIE (Quality Inspection Engine) objects:
¡ Samples and Items
¡ Findings
¡ Inspection documents
The number ranges are valid for all warehouses of the client.

CAUTION
Use this procedure only if you have not created any of those objects in the EWM client yet, as it
invalidates the previous number range status.

Procedure
Carry out the following steps in each EWM client you want to connect to SAP ERP:
...

1. In the EWM system, on the SAP Easy Access screen, choose Tools ® Customizing ® Business
Configuration Sets ® Activation of BC Sets. Alternatively, call transaction SCPR20.
2. Enter the following BC set and choose Activate BC Set:

BC Set Name Description

/SCWM/PRC_10N Number Range Intervals for Basic Settings (Client)
The Activation Options screen appears.
3. On the Activation Options screen, press Enter to continue the activation.

7.4 Activating BC Sets for Client-Dependent Basic Settings

You use this procedure to create basic settings in decentralized EWM. The settings are valid for all warehouses of
the client.

Procedure
Carry out the following steps in each EWM client you want to connect to SAP ERP:
...

1. In the EWM system, on the SAP Easy Access screen, choose Tools ® Customizing ® Business
Configuration Sets ® Activation of BC Sets. Alternatively, call transaction SCPR20.
2. Activate the following BC sets:

BC Set Name Description

/SCWM/PRC_10_10_S4 Basic Settings (Client) - 10 - S/4
/SCWM/PRC_10_20 Basic Settings (Client) – 20

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Customizing Settings in Decentralized EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 38
/SCWM/PRC_10_30 Basic Settings (Client) – 30
/SCWM/BASIC_LIME LIME Basic Settings for EWM

3. If you have created number ranges in chapter Activating BC Sets for Client-Dependent Number Ranges,
activate additionally the following BC set in each EWM client you want to connect to SAP ERP:

BC Set Name Description

/SCWM/PRC_11_9A Assignment Number Range Intervals for Basic Settings

Note
If the activation of a BC set fails due to missing entries in dependent tables, repeat the activation.

7.5 Verifying Synchronization of SAP ERP and EWM

Customizing
You use this procedure to check the synchronization of SAP ERP customizing and customizing in decentralized
EWM.
When transferring master data or transaction data from SAP ERP to EWM or the other way around, the system
checks some attributes in customizing.
For example:
· You create a packaging material with handling unit (HU) type E1 (Europallet) in SAP ERP. When the system
transfers the material to EWM, it checks that HU type E1 also exists in EWM customizing.
· You create an outbound delivery with shipping conditions and Incoterms in SAP ERP. When the system
transfers the outbound delivery from SAP ERP to EWM, it checks that the shipping conditions and
Incoterms also exist in EWM customizing.

Note
Some customizing tables (for example, table T137 below) are not used in any warehouse processes
but they may be used as check table for mandatory IDoc fields. Therefore, you must also
synchronize them to avoid IDoc errors.

Procedure
Check if you use some of the settings listed in the following table in your warehousing processes. Compare the
entries between your EWM and your ERP customizing client and adapt if needed the entries in the EWM or in the
ERP client. Depending on your settings and processes, you may need to synchronize additional tables.

1. On the SAP Easy Access screen, choose Tools ® Administration ® Administration ® Client Administration
® Customizing Objects ® Object Comparison (or call transation SCMP).
2. Compare the information in the following table between the EWM client and the ERP customizing client.
Compare the entries you plan to use in your warehousing processes. Adjust the tables in SAP ERP or EWM
Customizing, if necessary.

View/Table Description Usage in Decentralized EWM

T001W (V_T001W) Plants Material master, batch master
Note: only the plant definition is
needed in EWM for master data
replication, no other plant settings.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Customizing Settings in Decentralized EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 39
TSPA (V_TSPA) Organizational Unit: Sales Divisions Material master
V_T077K Vendor account group Vendor master
V_T077D Customer Account Group Customer master
T134 Material Types Material master
T137 (V137) Industries for materials Material master
T142 (V_142) Storage Conditions for Materials Material master
T143 (V_143) Temperature Conditions for Material master
Storing Materials
T144 (V_144) Container Requirements for Material master
Storing Materials
T023 (V023) Material groups Material master
TCSCP_COMP_LVL Material completion levels Material master
(V_TCSCP_COMP_LVL)
TTGR (V_TTGR) Material transportation groups Material master
T179 Materials: Product Hierarchies Material master
T190S (V_T190S) Product Allocation: Definition Material master
Procedure
TVEGR Material Group: Packaging Material master
Materials
THUTYP Handling Unit Types Material master
TWHMATGR Warehouse Material Group Material master
TWHSTC Warehouse Storage Condition Material master
THNDLCD Handling Indicator Material master
TPTM Materials: Item Category Groups in Material master
Material Master
TMFG Material freight groups Material master
TQGRP Quality Inspection Group Material master
TCWQTOLGR EWM-CW: Tolerance Groups Material master
TCWQPROC EWM-CW: EWM-CW: Catch Weight Material master
Quantity Input Control
V_TAPROF Merchandise Distribution - Material master
Adjustment Profile
TNTP International Article Number (EAN) Material master
Categories
TDG41 (DGV_TDG41) DG Indicator Profiles for Material Material master
Master
T6WP3 (V_6WP3) Labelling Type Material master
T6WP4 (V_6WP4) Label Shape Material master
TQ08 (V_TQ08) Control of QM in procurement - Material master
Control Key
TQ04A (V_TQ04A) Control of QM in procurement - Vendor master
Delivery Block
V_TPRIO Delivery Priority Delivery
V_TINC Incoterms Delivery

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Customizing Settings in Decentralized EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 40
V_TVSB Shipping Conditions Delivery
TSERIAL Serial Number Profile Material master
TCUCH Batch Level and Batch Status Batch master
Management
V_CMG Characteristics Groups Classification
V_CMS Characteristic Status Classification
V_CPS Define Characters in Templates Classification
V_CPA Templates Classification
V_CLO Key Fields of Objects Classification
V_CLT Object Table Classification
V_CLA Class Types Classification
V_CLAO Objects Classification
V_CLU Class Status Classification
V_CLS Organizational Areas Classification
V_CLX Text Types Classification
V_CLC Classification Status Classification
V_CLR Functions/Filters for Finding Classification
Objects
V_CLG Class Groups Classification

3. In Customizing for SAP ERP and in Customizing for decentralized EWM, compare the information in the
following table between the EWM client and the ERP customizing client. Compare the entries you plan to use
in your warehousing processes. Adjust the entries in SAP ERP or EWM Customizing, if necessary.

IMG Path in SAP ERP IMG Path in Decentralized EWM

Logistics – General ® Handling Unit Management ® Extended Warehouse Management ® Cross-Process
Basics ® Define Packaging Material Types Settings ® Handling Units ® Basics ® Define
(View V_TVTY) Packaging Material Types
Note: for number ranges, see chapter Aligning HU (View /SCWM/V_TPMTYPWM)
Numbering

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Customizing Settings in Decentralized EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 41
8 Master Data Distribution via ALE/IDoc
You use this process to start the distribution of master data via ALE/IDoc from SAP ERP as sender system to
decentralized EWM as receiver system.

8.1 Executing Initial Transfer of Master Data

You use the following procedures to create IDocs for the initial master data transfer to decentralized EWM.

Note
Refer to appendix B of this document for a list of transactions you can use to monitor and process
IDocs. For example, you use transaction BD87 in SAP ERP and in decentralized to check the IDoc
status after transfer.

8.1.1 Executing Initial Transfer of Characteristics

You use this procedure to transfer characteristics for classification of batches.

Procedure
Carry the following steps in SAP ERP:
1. Call transaction BD91 (Distribute All Characteristics Using ALE ).
2. Enter the data as shown in the following table:

Field Value

Characteristic Leave empty or enter an interval

Logical system <EWM logical system>, for example, EWMCLNT001

3. Press Execute

8.1.2 Executing Initial Transfer of Classes

You use this procedure to transfer classes for classification of batches.

Procedure
Carry the following steps in SAP ERP:
...

1. Call transaction BD92 (Distribute Classes Using ALE: Send Direct).

2. Enter the data as shown in the following table:

Field Value

Class Type 023 for batch classes

Class Enter the classes you use for batch classification

Logical system <EWM logical system>, for example, EWMCLNT001

3. Press Execute

8.1.3 Executing Initial Transfer of Materials

You use this procedure to transfer material master data.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Master Data Distribution via ALE/IDoc © 2019 SAP AG or an SAP affiliate company. All rights reserved. 42
Procedure
Carry the following steps in SAP ERP:
...

1. Call transaction BD10 (Send Material).

2. Enter the data as shown in the following table:

Field Value

Material Leave empty or enter an interval

Class Leave empty. Enter an interval only if you use material classification

Message Type (Standard) Reduced message type for materials, for example ZEWMMATMAS

Logical system <EWM logical system>, for example, EWMCLNT001

Leave empty.
Set this indicator only if you use material classification. If the indicator
Send Material in Full is set, the material classification data will be transferred together with
the material master data. As an alternative, you can transfer
classification data with transaction BD93 after you have transferred
the corresponding material or batch master data.

3. Press Execute or, if you expect a big amount of data to be transferred, choose Program ® Execute in
Background.

Tip
If a material master field is set as mandatory field in decentralized EWM but is not sent via IDoc, the
IDoc is erroneous in EWM. In this case, you must either transfer the field by changing the reduced
message type, or you must set the field as optional in decentralized EWM. For this purpose, check
the selection group of the field in Customizing for Logistics – General under Material Master ® Field
Selection ® Assign Fields to Field Selection Group and change the field to optional under Material
Master ® Field Selection ® Maintain Field Selection for Data Screens.

8.1.4 Executing Initial Transfer of Batches

You use this procedure to transfer batch master data.

Prerequisites
SAP note 2745236 is implemented in your SAP ERP system.

Procedure
Carry the following steps in SAP ERP:
...

1. Call transaction BD90 (Batch Master Record Initial Transfer).

2. Enter the data as shown in the following table:

Field Value

Material Leave empty

Batch Leave empty

Logical system <EWM logical system>, for example, EWMCLNT001

3. Press Execute or, if you expect a big amount of data to be transferred, choose Program ® Execute in
Background.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Master Data Distribution via ALE/IDoc © 2019 SAP AG or an SAP affiliate company. All rights reserved. 43
8.1.5 Executing Initial Transfer of Customers
You use this procedure to transfer customer master data.

Procedure
Carry the following steps in SAP ERP:
...

1. Call transaction BD12 (Send Customers).

2. Enter the data as shown in the following table:

Field Value

Customer Leave empty

Output Type Reduced message type for customers, for example ZEWMDEBMAS

Logical system <EWM logical system>, for example, EWMCLNT001

3. Press Execute or, if you expect a big amount of data to be transferred, choose Program ® Execute in
Background.

8.1.6 Executing Initial Transfer of Vendors

You use this procedure to transfer vendor master data.

Procedure
Carry the following steps in SAP ERP:
...

1. Call transaction BD14 (Send Vendor).

2. Enter the data as shown in the following table:

Field Value

Account Number of Vendor Leave empty

Message Type Reduced message type for vendors, for example ZEWMCREMAS

Target system <EWM logical system>, for example, EWMCLNT001

3. Press Execute or, if you expect a big amount of data to be transferred, choose Program ® Execute in
Background.

8.2 Executing Delta Transfer of Master Data

After activating change pointers for the message types, IDocs can be created for the corresponding master data
based on logging of master data changes. In a productive environment, you create IDocs to transfer changed
master data automatically but in the implementation phase, you can also create these IDocs manually.

8.2.1 Creating IDoc Using Change Pointers Manually

You use this procedure to create IDocs manually based on change logging of master data:

Procedure
Carry the following steps in SAP ERP:
...

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Master Data Distribution via ALE/IDoc © 2019 SAP AG or an SAP affiliate company. All rights reserved. 44
1. Call transaction BD21 (Creating IDoc Type from Change Pointers)
2. Enter one of the following message types:
o CHRMAS: Class system: Characteristics master
o CLSMAS: Class system: Classes master
o CLFMAS: Class system: Classification master
o Reduced message type for vendors, for example ZEWMCREMAS
o Reduced message type for customers, for example ZEWMDEBMAS
o Reduced message type for materials, for example ZEWMMATMAS
o BATMAS: Batch
3. Press Execute

8.2.2 Creating IDoc Using Change Pointers Automatically

You use this procedure to create IDocs manually based on change logging of master data:

Procedure
Carry the following steps in SAP ERP:
...

1. Call transaction SA38 (ABAP: Program Execution)

2. Enter program RBDMIDOC
3. Create a variant for each of the following message types:
o CHRMAS: Class system: Characteristics master
o CLSMAS: Class system: Classes master
o CLFMAS: Class system: Classification master
o Reduced message type for vendors, for example ZEWMCREMAS
o Reduced message type for customers, for example ZEWMDEBMAS
o Reduced message type for materials, for example ZEWMMATMAS
o BATMAS: Batch
4. Choose Background to define a job to execute all variants of program RBDMIDOC in the background.
5. Schedule the job to run periodically. With each job run, the system will create IDocs for changed master
data automatically.

8.3 Implementing BAdIs for Master Data Distribution via

IDoc
In addition to the settings described in this chapter, you must also implement some BAdIs or customer exits to
optimize the distribution of master data via IDoc/ALE:
BAdI or Customer Exit Usage
BAdI IDOC_CREATION_CHECK Used for filtering the master data records to be
transferred, for example by organizational units.
BAdI VBW_BATCH_REPLICATE Used to ensure that batch classification data is
transferred together with the corresponding batch
master records
BAdI BADI_MATMAS_ALE_CR Used to define the material master views to be
transferred to EWM.transfer The following example
implementation of BADI_MATMAS_ALE_CR, method
CHANGE_MATMAS contains an example where fields
MARA-PSTAT and MARA-VPSTA are changed based
on the receiving systems(s) and message type. The
implementation filters all values from the status which
are not required for EWM (here values KLEVQ). You
must at least adjust the yellow highlighted code.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Master Data Distribution via ALE/IDoc © 2019 SAP AG or an SAP affiliate company. All rights reserved. 45
Enhancement VSV00002 Used to transfer only addresses linked to vendor or
(customer exit EXIT_SAPLKD03_001) and customer master data
enhancement VSV00003
(customer exit EXIT_SAPLVV01_002)

You will find example implementations in Appendix A - Example BADI Implementations for IDoc/ALE.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Master Data Distribution via ALE/IDoc © 2019 SAP AG or an SAP affiliate company. All rights reserved. 46
9 Warehouse Integration into the SAP ERP
Enterprise Structure
You use this process to integrate a warehouse into the enterprise structure in SAP ERP or SAP S/4HANA

Important
As the procedure for integrating decentralized EWM with SAP ERP differs from the procedure for
integrating decentralized EWM with SAP S/4HANA, they are described in different chapters.

9.1 Prerequisites for Warehouse Integration in SAP ERP

In the SAP ERP system, you have created the following objects and settings:
· A plant (for example, PL01). The plant must be assigned to the enterprise structure in SAP ERP such as
company code, purchasing organization, and sales organization.
You can check the plant in Customizing for Enterprise Structure under Definition ® Logistics – General ®
Define, copy, delete, check plant.
· One or more storage locations, for example storage locations ROD and AFS in plant PL01.
You can check this setting in Customizing for Enterprise Structure under Definition ® Materials
Management ® Maintain storage location.
· A customer linked to the plant. For example, customer BPPL01C according to the naming convention
BP<plant>C.
You can check this setting in Customizing for Materials Management under Purchasing ® Purchase Order
® Set up Stock Transport Order ® Define Shipping Data for Plants. Choose an account group for which
IDoc master data distribution is set up, for example, KUNA (Customer (ext.number assgnmnt) ).
· A vendor linked to the plant. For example, vendor BPPL01V according to the naming convention
BP<plant>V. Choose an account group for which IDoc master data distribution is set up, for example,
LIEF (Vendor (ext.number assgnmnt) ).
You can check this setting in the following way:
a. On the SAP Easy Access screen, choose Logistics ® Materials Management ® Purchasing ®
Master Data ® Vendor ® Purchasing ® Display (Current).
b. Enter the vendor number and select the Purchasing Data checkbox.
If you do not know the vendor number, check table T001W.
c. On the Purchasing Data screen, choose Extras ® Add. Purchasing Data.
· A shipping point and a goods receiving point assigned to the plant, for example shipping point 0001 also
used as receiving point and assigned to plant PL01. The shipping point should be allocated to the desired
combinations of shipping condition and loading group for each plant.
You can check this setting as follows:
¡ In Customizing for Enterprise Structure under Definition ® Logistics Execution ® Define, copy,
delete, check shipping point
¡ In Customizing for Enterprise Structure under Assignment ® Logistics Execution ® Assign
shipping point to plant
¡ In Customizing for Logistic Execution under Shipping ® Basic Shipping Functions ® Shipping Point
and Goods Receiving Point Determination ® Assign Shipping Points
¡ In Customizing for Logistic Execution under Shipping ® Basic Shipping Functions ® Shipping Point
and Goods Receiving Point Determination ® Assign Goods Receiving Points for Inbound Deliveries
· The current posting period for materials management is set for the company code. You can check this
setting in Customizing for Logistics – General under Material Master ® Basic Settings ® Maintain
Company Codes for Materials Management.
· The current posting period for materials management is included in the interval defined for the posting
period variant assigned to the company code. You can check this setting in Customizing for Financial
Accounting (New) under Financial Accounting Global Settings (New) ® Ledgers ® Fiscal Year and Posting

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Warehouse Integration into the SAP ERP Enterprise Structure © 2019 SAP AG or an SAP affiliate company. All rights reserved. 47
Periods ® Posting Periods ® Open and Close Posting Periods. Check that the last posting period allowed is
in the future.
· The current fiscal year is defined in the plan version assigned to the controlling area. This setting is only
necessary if the Profit Center Accounting is active in the controlling area assigned to the company code.
You can check this setting as follows:
¡ In Customizing for Controlling under Cost Center Accounting ® Activate Cost Center Accounting in
Controlling Area, you can check whether the Profit Center Accounting is active in the controlling
area.
¡ In Customizing for Controlling under Profit Center Accounting ® Basic Settings ® Controlling Area
Settings ® Activate Direct Postings ® Plan Versions ® Maintain Plan Versions, you can check the
settings for each fiscal year.
· A cost center is assigned to the cost elements used for scrapping. You can check this setting in
Customizing for Controlling under Cost Center Accounting ® Actual Postings ® Manual Actual Postings ®
Edit Automatic Account Assignment. If you use the standard chart of account INT in the company code,
check that a cost center is assigned to the cost elements used for scrapping, for example cost elements
400001 and 890001 for the scrapping of trading goods.

Note
You can use the Customer Vendor Integration (CVI) in SAP ERP but it is not a prerequisite for the
integration with decentralized EWM as the data transfer via ALE is based on customer and vendor
master data and not on the business partner master data. In decentralized EWM, CVI is always
active, meaning that the business partners are created automatically in EWM with the transfer of
customer or vendor master data from SAP ERP.

9.2 Prerequisites for Warehouse Integration in SAP

S/4HANA
In the SAP S/4HANA system used as global enterprise management system, you have created the following
objects and settings:
· A plant (for example, PL01). The plant must be assigned to the enterprise structure in SAP ERP such as
company code, purchasing organization, and sales organization.
You can check the plant in Customizing for Enterprise Structure under Definition ® Logistics – General ®
Define, copy, delete, check plant.
· An active material ledger for the valuation area assigned to the plant.
You can check this setting in Customizing for Controlling under General Controlling ® Multiple Valuation
Approaches/Transfer Prices ® Basic Settings ® Check Material Ledger Settings ® Activate Valuation
Areas for Material Ledger ® Check Material Ledger Settings.
· One or more storage locations, for example storage locations ROD and AFS in plant PL01.
You can check this setting in Customizing for Enterprise Structure under Definition ® Materials
Management ® Maintain storage location.
· A business partner with predefined roles FLCU00 (FI Customer) and FLCU01 (Customer) linked as
customer to the plant, for example business partner BPPL01, following the naming convention
BP<plant>.
You can check this setting in Customizing for Materials Management under Purchasing ® Purchase Order
® Set up Stock Transport Order ® Define Shipping Data for Plants.
· The same business partner (or a second business partner) with pre-defined roles FLVN00 (FI Vendor) and
FLVN01 (Vendor) linked as supplier to the plant.
d. Using the SAP Easy Access menu, choose Logistics ® Materials Management ® Purchasing ®
Master Data ® Vendor ® Purchasing ® Display (Current).
e. Enter the vendor number and select the Purchasing Data checkbox
The system automatically redirects you to the Display Business Partner transaction.
If you do not know the vendor number, check table T001W.
f. In the Display in BP role field, check that the role FLVN01 - Vendor is selected.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Warehouse Integration into the SAP ERP Enterprise Structure © 2019 SAP AG or an SAP affiliate company. All rights reserved. 48
g. Choose Goto ® General Data
h. Check the assigned plant in the Vendor: General Data tab page
· A shipping point and a goods receiving point assigned to the plant, for example shipping point 0001 also
used as receiving point and assigned to plant PL01. The shipping point should be allocated to the desired
combinations of shipping condition and loading group for each plant.
You can check this setting as follows:
¡ In Customizing for Enterprise Structure under Definition ® Logistics Execution ® Define, copy,
delete, check shipping point
¡ In Customizing for Enterprise Structure under Assignment ® Logistics Execution ® Assign
shipping point to plant
¡ In Customizing for Logistic Execution under Shipping ® Basic Shipping Functions ® Shipping Point
and Goods Receiving Point Determination ® Assign Shipping Points
¡ In Customizing for Logistic Execution under Shipping ® Basic Shipping Functions ® Shipping Point
and Goods Receiving Point Determination ® Assign Goods Receiving Points for Inbound Deliveries
· The current posting period for materials management is set for the company code. You can check this
setting in Customizing for Logistics – General under Material Master ® Basic Settings ® Maintain
Company Codes for Materials Management.
· The current posting period for materials management is included in the interval defined for the posting
period variant assigned to the company code. You can check this setting in Customizing for Financial
Accounting (New) under Financial Accounting Global Settings (New) ® Ledgers ® Fiscal Year and Posting
Periods ® Posting Periods ® Open and Close Posting Periods. Check that the last posting period allowed is
in the future.
· The current fiscal year is defined in the plan version assigned to the controlling area. This setting is only
necessary if the Profit Center Accounting is active in the controlling area assigned to the company code.
You can check this setting as follows:
¡ In Customizing for Controlling under Cost Center Accounting ® Activate Cost Center Accounting in
Controlling Area, you can check whether the Profit Center Accounting is active in the controlling
area.
¡ In Customizing for Controlling under Profit Center Accounting ® Basic Settings ® Controlling Area
Settings ® Activate Direct Postings ® Plan Versions ® Maintain Plan Versions, you can check the
settings for each fiscal year.
· A cost center is assigned to the cost elements used for scrapping. You can check this setting in
Customizing for Controlling under Cost Center Accounting ® Actual Postings ® Manual Actual Postings ®
Edit Automatic Account Assignment. If you use the standard chart of account INT in the company code,
check that a cost center is assigned to the cost elements used for scrapping, for example cost elements
400001 and 890001 for the scrapping of trading goods.

9.3 Creating Organizational Units for Warehouse in SAP ERP

You use this procedure to define the 3-digit warehouse in Logistics Execution in SAP ERP. It will be linked later to
the 4-digit EWM warehouse.

Procedure
...

1. Define the 3-digit warehouse number as follows:

a. In Customizing for Enterprise Structure, choose Definition ® Logistics Execution ® Define, copy,
delete, check warehouse number.
b. In Define, copy, delete, check warehouse number, choose the activity Define warehouse number.
c. Create for example the following entry:

Warehouse Number Description

W01 Warehouse W01 (EWM)

2. Assign the warehouse to the plant and storage locations in Customizing for Enterprise Structure under
Assignment ® Logistics Execution Assign warehouse number to plant/storage location. Create and save
an entry for each assignment.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Warehouse Integration into the SAP ERP Enterprise Structure © 2019 SAP AG or an SAP affiliate company. All rights reserved. 49
Example:

Plant Storage Location Warehouse

PL01 ROD W01

PL01 AFS W01

3. Maintain EWM-specific parameters for the warehouse in Customizing for Logistics Execution under
Extended Warehouse Management Integration ® Basic Setup of EWM Connectivity ® Maintain Extended
WM-Specific Parameters.
Enter or select the data for your warehouse as shown in the following table:

Field Value

Ext. WM E ( ERP with Extended Warehouse Management )

Comm. WM Q ( Queued and Serialized Asynchronous RFC )

Dist. Mode Distribution Immediately at

Document Creation

4. Assign the 3-digit warehouse number to the 4-digit EWM warehouse number in Customizing for Integration
with other SAP Components under Extended Warehouse Management ® Assign Warehouse Number to
Warehouse Number of Decentralized SCM System.
Example:

Warehouse Number WHNDecSCM

W01 W001

Note
This setting is optional but recommended. It is currently not used in the ERP-EWM integration, but
it has the advantage of a higher data transparency in SAP ERP and may be needed for future
processes.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Warehouse Integration into the SAP ERP Enterprise Structure © 2019 SAP AG or an SAP affiliate company. All rights reserved. 50
10 Warehouse Creation and Integration in
EWM
You use this process to create a warehouse in decentralized EWM and assign it to the organizational units from
SAP ERP. This includes:
· Warehouse definition and assignment to the 3-digit warehouse number
· Assignment of following organizational units to the EWM warehouse:
¡ Supply chain unit (SCU) of the warehouse
¡ Custodian
¡ Parties entitled to dispose (plants) linked to the warehouse
¡ Default party entitled to dispose (optional)
· Activation of BC sets for warehouse-dependent basic settings and warehouse-dependent number ranges
· Assignment of EWM stock types to the corresponding plants and storage locations by means of availability
groups
· Alignment of handling unit numbering

10.1 Creating and Integrating an EWM Warehouse

You use this procedure to create a 4-digit warehouse number in decentralized EWM and assign organizational
units to the warehouse.

Procedure
Carry out the first step of the following procedure in your EWM customizing client and transport, if necessary, the
settings to other EWM clients or EWM systems. Carry out the subsequent steps in each EWM client you want to
connect to SAP ERP.
...

1. Define the 4-digit warehouse number as follows:

a. In Customizing for Extended Warehouse Management, choose Master Data ® Define Warehouse
Numbers
b. Create and save for example the following entry:

Warehouse Number Description

W001 Warehouse W001

2. Assign the 4-digit EWM warehouse number to the 3-digit ERP warehouse as follows:
a. In Customizing for Extended Warehouse Management, choose Interfaces ® ERP Integration ®
General Settings ® Map Warehouse Numbers from ERP System to EWM.
b. Create and save for example the following entry:

Whse No. ERP Warehouse Number

W01 W001
3. Create a supply chain unit for the warehouse as follows:
a. In the EWM system, on the SAP Easy Access screen, choose Master Data ® Maintain Supply Chain
Unit. Alternatively, call transaction /SCMB/SCUMAIN.
b. Enter a supply chain unit, for example SCU_W001 and a supply chain unit type, for example 1008
(Warehouse), and press Create.
c. Enter a description for the supply chain unit
d. Enter an address for the warehouse on the Address tab page
e. Create the following business attributes on the Alternative tab page:
Business Attribute Description
PLOC Planning Location

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Warehouse Creation and Integration in EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 51
INV Warehouse
SO Shipping Office
RO Goods Receipt Office
f. Save your entries
4. Assign a party entitled to dispose to each plant you want to link to an EWM warehouse. The party entitled to
dispose is a business partner. It is used in EWM as an attribute of each stock you manage in the warehouse.
a. In Customizing for Extended Warehouse Management, choose Interfaces ® ERP Integration ®
General Settings ® Assign Party Entitled to Dispose to Plant
b. Create and save for example the following entry:

Plant Logical System Local Ent. To Dispose

ERPCLNT001 BPPL01V (example for SAP ERP) or

PL01
BPPL01 (example for SAP S/4HANA)

Note
In this example, the party entitled to dispose is the business partner linked to the vendor assigned
to the plant. The business partner was created automatically in EWM with the initial transfer of
vendors from SAP ERP. As an alternative, you can create a business partner manually in EWM only
and assign it to the plant in this step.
5. Assign the organizational entities to the warehouse in Customizing for Extended Warehouse Management
under Master Data ® Assign Warehouse Numbers, for example:
Field Value
Supply Chain Unit <SCU of the warehouse>, for example SCU_W001
Custodian <Business partner of the plant>, for example, BPPL01V or
BPPL01, or a business partner you created manually for the warehouse in
EWM
Default Party Entitled <Business partner of the plant>, for example, BPPL01V or
BPPL01, if the warehouse is only linked to one plant

10.2 Activating BC Sets for Warehouse-Dependent Number

Ranges
You use this procedure to create number ranges at warehouse level in EWM.

CAUTION
Use this procedure only for a newly created warehouse, as it invalidates the previous number range
status.

Procedure
Carry out the following steps in each EWM client you want to connect to SAP ERP:
...

1. In the EWM system, on the SAP Easy Access screen, choose Tools ® Customizing ® Business
Configuration Sets ® Activation of BC Sets. Alternatively, call transaction SCPR20.
2. Enter the following BC set and choose Activate BC Set:

BC Set Name Description

/SCWM/PRC_20N Number Range Intervals for Basic Settings (Warehouse)
The Enter Variable Field Values screen appears.
3. Change, if necessary, the warehouse number, and choose Copy values.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Warehouse Creation and Integration in EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 52
The Activation Options screen appears.
4. On the Activation Options screen, press Enter to continue the activation.

10.3 Activating BC Sets for Warehouse-Dependent Basic

Settings
You use this procedure to create basic settings for your warehouse in decentralized EWM.

Procedure
Carry out the following steps in each EWM client you want to connect to SAP ERP:
...

1. In the EWM customizing system, on the SAP Easy Access screen, choose Tools ® Customizing ®
Business Configuration Sets ® Activation of BC Sets. Alternatively, call transaction SCPR20.
2. Activate the following BC sets in your warehouse:

BC Set Name Description

/SCWM/PRC_20_10 Basic Settings (Warehouse) – 10
/SCWM/PRC_20_20_S4 Basic Settings (Warehouse) - 20 - S/4
/SCWM/EXCEPTION Exception Handling
/SCWM/PRC_20_30 Basic Settings (Warehouse) - 30

Note
If the activation of a BC set fails due to missing entries in dependent tables, repeat the activation.

10.4 Assigning Storage Locations to EWM Stock Types Using

Basic Availability Groups
You use this procedure to map plants and storage locations to already existing EWM availability groups. An EWM
availability group is linked to EWM stock types. In this example, you assign the storage locations ROD and AFS of
plant PL01 to the basic availability groups 001 and 002.

Recommendation
For a better visibility of the plants and storage locations in the warehouse, use the alternative
procedure described in the next chapter.

Procedure
Carry out the following steps in the EWM customizing system:
...

1. On the SAP Easy Access screen, choose Tools ® Customizing ® Business Configuration Sets ® Activation
of BC Sets. Alternatively, call transaction SCPR20.
2. Activate the following BC set in your warehouse:

BC Set Name Description

/SCWM/PRC_21_10 Basic Settings - Avail. Groups and Stock Types (not in Tool)
3. In Customizing for Extended Warehouse Management, choose Interfaces ® ERP Integration ® Goods
Movements ® Map Storage Locations from ERP System to EWM.
4. Create an entry for each storage location linked to the warehouse. For example, create and save the
following entries:

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Warehouse Creation and Integration in EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 53
Field First Entry Second Entry
Plnt PL01 PL01
SLoc ROD AFS
Logical System ERPCLNT001 ERPCLNT001
Warehouse Number W001 W001
Avail.Grp 001 002

10.5 Assigning Storage Locations to EWM Stock Types Using

Location-Specific Availability Groups
You use this procedure to map plants and storage locations to location-specific availability groups. The procedure
is more complex than the procedure described in the previous chapter, but it offers a better visibility of the plants
and storage locations in EWM. In this example, you assign the storage locations ROD and AFS of plant PL01 to the
availability groups PL01/ROD and PL01/AFS.

Procedure
Carry out the following steps in the EWM customizing system:
...

1. In Customizing for Extended Warehouse Management, choose Goods Receipt Process ® Configure
Availability Group for Putaway ® Define Availability Group.
2. Create an entry for each storage location linked to the warehouse. For example, create and save the
following entries in your warehouse:
Avail.Grp Description
<plant/storage location>, Stock in <plant / storage location>, for example
for example PL01/ROD Stock in PL01 / ROD
<plant/storage location>, Stock in <plant / storage location>, for example
for example PL01/AFS Stock in PL01 / AFS
3. In Customizing for Extended Warehouse Management, choose Interfaces ® ERP Integration ® Goods
Movements ® Map Storage Locations from ERP System to EWM.
4. Create an entry for each storage location linked to the warehouse. For example, create and save the
following entries:
Field First Entry Second Entry
Plnt PL01 PL01
SLoc ROD AFS
Logical System ERPCLNT001 ERPCLNT001
Warehouse Number W001 W001
Avail.Grp PL01/ROD PL01/AFS
5. In Customizing for Extended Warehouse Management, choose Goods Receipt Process ® Configure
Availability Group for Putaway ® Configure Stock Type
6. Create EWM stock types for each storage location linked to the warehouse. For example, create and save
the following entries in your warehouse:
Stock Non-Dep. Stock
Type Description Avail.Grp Type Rl
F1 Unrestricted in PL01/ROD PL01/ROD FF Normal Stock
F2 Unrestricted in PL01/AFS PL01/AFS FF Normal Stock
Q3 Quality Insp. in PL01/ROD PL01/ROD QQ Normal Stock
Q4 Quality Insp. in PL01/AFS PL01/AFS QQ Normal Stock
B5 Blocked in PL01/ROD PL01/ROD BB Normal Stock
B6 Blocked in PL01/AFS PL01/AFS BB Normal Stock

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Warehouse Creation and Integration in EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 54
S5 Scrapping in PL01/ROD PL01/ROD BB Scrapping Stock
S6 Scrapping in PL01/AFS PL01/AFS BB Scrapping Stock
R7 Returns in PL01/ROD PL01/ROD RR Normal Stock
R8 Returns in PL01/AFS PL01/AFS RR Normal Stock

Tip
For more information, see IMG activity documentation in Customizing for Extended Warehouse
Management under Goods Receipt Process ® Configure Availability Group for Putaway, and field
help of availability group.

Important
If you create a second warehouse and link it to other plants or storage locations, for example W002
linked to plant PL02 and storage locations ROD and AFS, you can reuse the same stock types but
enter a different stock type description in each warehouse, for example F1 with description
‘Unrestricted in PL02/ROD’ in warehouse W002.

10.6 Aligning HU Numbering

You use this procedure to align the handling unit (HU) numbering in Logistics Execution in SAP ERP and in
decentralized EWM and to activate if necessary the lean HU status update in Logistics Execution.
HUs used in deliveries are communicated from EWM to Logistics Execution or the other way around. The HU
number used in one application must not overlap with the free internal HU number range defined in the other
application, as this would lead to queue errors.
The following table gives an example of aligned HU number range intervals in Logistics Execution and in EWM:

Application / System Internal Ranges External Ranges

Logistics Execution in SAP ERP 1000000000 - 7999999999 (10 8000000000 - 9999999999 (10
digits) digits)

Decentralized EWM (warehouse- 800000000 - 899999999 (9 None (all numbers outside the
specific) digits) internal number ranges allowed)
1000000 - 1999999 (7 digits)

If you use several warehouses to the same SAP S/4HANA system, you must check manually that the warehouse-
specific number ranges do not overlap, especially if you use stock transport orders for the transfer of goods
between warehouses.
For this purpose, we review the basic rules for HU numbering and give an overview of the applications (Logistics
Execution or EWM) in which HUs are created and of the ways the HUs are created (using internal or external
numbers).
Basic Rules for HU Numbering in EWM in SAP S/4HANA
· Logistics Execution (LE) accepts all HU numbers from EWM except if they are within the free internal LE
number range. For example, in case of an internal LE number range from 1000 to 7999 with a current
number range status 1555, LE accepts all numbers from EWM except in the interval of free numbers 1556-
7999.
· EWM accepts HU numbers from LE if they are within the external EWM number range or within the
assigned internal EWM number range (reusing existing HUs).
· If no external number range is defined explicitly in EWM, all numbers outside the free internal number
range belong to the external number range. This is an implicit external number range.

Recommendation
It is technically not necessary to define an external number range in Logistics Execution for HU
numbers communicated by EWM. When working with multiple warehouses, however, we
recommend defining external number ranges in Logistics Execution for documentation purposes.
The following table lists the number range definitions based on where and how you create HUs:

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Warehouse Creation and Integration in EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 55
New HU Created In Number Range Definition
EWM (internal) EWM: internal number range necessary
LE: external number range not necessary. EWM
number must be outside the free internal LE number
range

EWM (external) EWM: implicit or explicit external number range

necessary
LE: external number range not necessary. EWM
number must be outside the free internal LE number
range

Logistic Execution (internal) LE: internal number range necessary

EWM: implicit or explicit external number range
necessary

Logistic Execution (external) LE: external number range necessary

EWM: implicit or explicit external number range
necessary

Recommendation
If you receive advanced shipping notifications (ASNs) from vendors and want to reuse the HU
number from the vendors in the warehouse, we recommend using Serial Shipping Container Code
(SSCC) instead of HU numbers from HU number ranges. The SSCC number ranges should not
overlap with the HU number ranges.
In addition to the definition of the HU number ranges, you can use this procedure to activate the lean HU status
update and the non-unique HU numbering in Logistics Execution. This setting is necessary for stock transport
order (STO) processes involving cross-delivery HUs.

Procedure
If you implement your own warehouse or if you implement the standard warehouse in a more complex system
landscape, carry out the following steps:
...

1. Check if HU number ranges are already defined in EWM:

a. Note the internal number range numbers assigned to the packaging material types in Customizing
for Extended Warehouse Management under Cross-Process Settings ® Handling Units ® External
Identification ® Assign Number Range Intervals to Packaging Material Types.
b. Note the internal and external number ranges defined in your warehouse in Customizing for
Extended Warehouse Management under Cross-Process Settings ® Handling Units ® External
Identification ® Define Number Range for HU Identification.
2. Check if HU number ranges are already defined in Logistics Execution in SAP ERP:
a. Note the internal and external number range numbers assigned to the packaging material types in
Customizing for Logistics – General, under Handling Unit Management ® External Identification ®
Define Number Assignment for Each Packaging Material Type.
b. Note the internal and external number ranges defined in Customizing for Logistics – General, under
Handling Unit Management ® External Identification ® Number Range Maintenance for HU
Identification.
3. Decide in which application (Logistics Execution in SAP ERP or EWM) you create HUs and if you use an
internal or an external number range for the HUs. Define the number ranges in EWM and LE following the
rules described above and transport if necessary the settings to other systems or clients.
4. If you use STO processes with cross-delivery HUs, activate the lean HU status update in SAP ERP in
Customizing for Logistics Execution under Extended Warehouse Management Integration ® Cross-
Process Settings ® Handling Unit Management ® Set Lean HU Status Update in Non-unique HU
Numbering Scenario.
For more information about this setting, see the Customizing documentation.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Warehouse Creation and Integration in EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 56
11 Additional Data Transfer and Settings in
SAP ERP and EWM
You use this process to activate the data transfer from SAP ERP to decentralized EWM.
You activate the following types of data transfer:
· Transaction data transfer from SAP ERP using queued remote function call (qRFC)
This data transfer is triggered in SAP ERP.
· Transfer of additional data (material valuation data) from SAP ERP to EWM
This data transfer is triggered in EWM (according to a “pull” principle).
· If you use batch-managed products in EWM, you also use this process to configure additional settings
related to batch-specific data.

11.1 Activating Transaction Data Transfer in SAP ERP

You use this procedure to activate in SAP ERP the transfer of transaction data (inbound deliveries, outbound
deliveries, and production material requests) to decentralized EWM using queued remote function call (qRFC).
Since only deliveries created in the Logistics Execution warehouse linked to EWM should be transferred to EWM,
you activate the delivery split by warehouse to ensure that no deliveries are created containing centrally-managed
and EWM-managed items in the same document.
You then generate a distribution model containing the 3-digit Logistics Execution warehouse.

Procedure
...

1. Define delivery split by warehouse in SAP ERP in Customizing for Logistics Execution under Shipping ®
Deliveries ® Define Split Criteria for Deliveries ® Delivery Split by Warehouse Number:
a. In Delivery Split by Warehouse Number , choose the activity Define delivery split per delivery type.
b. Select the Delivery Split checkbox for all delivery types you use in your warehouse.
In the standard warehouse with preconfigured processes, select the checkboxes for the following
delivery types:
§ EL (Inbound Delivery)
§ LF (Outbound Delivery)
§ LO (Delivery w/o Ref )
§ LR (Returns Delivery)
c. In Delivery Split by Warehouse Number , choose the activity Determine delivery split per warehouse
number.
d. Select the Delivery Split checkbox for your warehouse.
2. Generate the distribution model for the 3-digit warehouse:
a. In Customizing for Logistics Execution, under SAP EWM Integration ® Basic Setup of Connectivity
® Generate Distribution Model from SAP ERP to SAP EWM.

Note
In SAP S/4HANA, choose the following Customizing path instead: Logistics Execution ® Extended
Warehouse Management Integration ® Basic Setup of Connectivity ® Generate Distribution Model
from SAP S/4HANA to SAP EWM
b. Enter data in the following fields:
§ Warehouse Number, for example, W01
§ Logical System of SAP EWM, for example, EWMCLNT001
§ Distribution Model View, for example, EWM
c. In the Objects screen area, select All to create entries for inbound deliveries, outbound deliveries
and production material requests.
d. In the Action screen area, select Create Entries.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Additional Data Transfer and Settings in SAP ERP and EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 57
e. Choose Execute.
A protocol for all selected warehouses is created.

Result
You have activated the data transfer to EWM. If you create an inbound delivery or an outbound delivery in a plant
and storage location linked to the EWM warehouse, the system transfers the delivery data to EWM.

Note
If you have not yet completed the configuration of the warehouse requests used for deliveries on
the EWM side, the automatic distribution might lead to queue errors. You can prevent this by
stopping temporarily the distribution of deliveries for the warehouse in Customizing for Logistics
Execution under SAP EWM Integration (or Extended Warehouse Management Integration) ® Basic
Setup of Connectivity ® Configure SAP EWM-Specific Parameters.

11.2 Activating Additional Data Transfer in EWM

You use this procedure to activate in decentralized EWM the transfer of additional data (material valuation data)
from SAP ERP to EWM. This data transfer is triggered in EWM (following a “pull” principle). The data is transferred
by means of synchronous remote function call (RFC).
The material valuation data is required for the following functions in EWM:
· Physical inventory
· Quality management
· Split valuation without batches
You schedule a job in EWM to receive regularly material valuation data from SAP ERP for the products used in the
EWM warehouse. Based on the EWM warehouse entered as selection criteria, the system automatically
determines the party entitled to dispose and the ERP client from which the data should be transferred.

Procedure
...

1. On the SAP Easy Access screen, choose Extended Warehouse Management ® Interfaces ® ERP
Integration ® Determine and Set Prices from ERP.
2. Enter the EWM warehouse number, for example, W001.
3. Save as a variant, for example, VW001.
4. Define a background job for program /SCWM/R_VALUATION_SET. In this example, the job runs daily:
a. On the SAP Easy Access screen, choose System ® Services ® Jobs ® Define Job.
b. Enter the name of the job, for example, EWMVAL_W001 (naming convention:
EWMVAL_<warehouse>).
c. Create step number 1 by choosing Step.
d. In the ABAP program screen area, enter program /SCWM/R_VALUATION_SET and variant
VW001.
e. Save your entries.
The Step List Overview screen appears.
5. Go back.
6. Choose Start Condition.
The Start Time screen appears.
7. Choose Date/Time.
8. Enter the scheduled start date and time.
9. Select the Periodic job checkbox.
10. Choose Period values.
The Period Values screen appears.
11. Select for example Daily and save your entries.
12. On the Start Time screen, save your entries.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Additional Data Transfer and Settings in SAP ERP and EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 58
13. On the Define Background Job screen, save your entries.

11.3 Configuring Additional Settings for Batches

You can use this optional procedure to gain an overview of the integration of batches in SAP ERP and EWM. This
procedure is only necessary if you use batch-managed products in EWM.
In decentralized EWM based on SAP S/4HANA 1809 FPS2 batch numbers must be unique at client or material
level in SAP ERP.
You can create batches either in SAP ERP or in EWM:
· If you create a batch in SAP ERP see chapter Executing Initial Transfer of Batches for the initial transfer
and chapter Executing Delta Transfer of Master Data for the delta transfer.
· If you create a batch in EWM maintaining the EWM inbound delivery, the batch and related classification
data are synchronously created in decentralized EWM and updated asynchronously in the connected
SAP ERP system.
If you use internal number ranges for batches, you must check that the internal number ranges defined in SAP
ERP and EWM do not overlap.
You can use batch master attributes such as shelf life expiration date, country of origin, or batch status without
the need to set up classification. In this case a dummy class will be used in the background that contains all
standard attributes corresponding to the standard characteristics LOBM_*- Note that you cannot have a mixed
usage of batch master attributes and batch characteristics in a batch class.

Procedure
Carry out the following steps:
1) Check batch level in SAP ERP and EWM as follows:

a) In Customizing for Logistics – General, choose Batch Management Specify Batch Level and Activate
Status Management .
b) Choose Batch Level and check that batch numbers are unique on material level or client level for a
material.
c) If you change the batch level, a conversion is always necessary, even if you have not created a batch in
your system yet.

2) Check internal number ranges for batches in SAP ERP and EWM.

a) In Customizing for Logistics – General under Batch Management Batch Number Assignment , check
if you use internal batch number assignment and how the internal number range is defined.
b) In Customizing for Extended Warehouse Management under Cross-Process Settings Batch
Management Batch Management for Decentralized EWM -> Define Number Range for Batch , check
that the internal number range for batches (if existing) does not overlap with the internal number range in
SAP ERP. Change if necessary the internal number range in EWM.

3) Copy standard characteristics LOBM_* from client 000 to the SAP ERP and EWM client. Carry out this step in
all ERP clients linked to EWM and the decentralized EWM client as well.
a) Customizing for Logistics – General under Batch Management Batch Valuation Update Standard
Characteristics , execute the update.
b) On the SAP Easy Access screen under Cross-Application Componentsà Classification
SystemàMaster Data, use the value help of field Characteristic to check that characteristics beginning
with LOBM_* now exist in the ERP client.

More Information
Check also the application help http://help.sap.com/S4HANA: select in section Product Assistance English
Navigate to Enterprise Business ApplicationsàSupply ChainàExtended Warehouse Management (EWM)àBatch
Management.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLI C

Additional Data Transfer and Settings in SAP ERP and EWM © 2019 SAP AG or an SAP affiliate company. All rights reserved. 59
Appendix
In this section, you will find additional information for the integration of decentralized EWM with SAP ERP:
· Appendix A - Example BAdI Implementations
· Appendix B - Additional Information about IDoc/ALE
· Appendix C - List of EWM-Related BC Sets in SAP ERP
· Appendix D - Additional Information about BC Sets in EWM

Appendix A – Example BAdI Implementations for IDoc/ALE

Appendix A-1: Filtering via BAdI IDOC_CREATION_CHECK

You implement BAdI IDOC_CREATION_CHECK in the sender system to create IDocs based on specific values of
an attribute which is not defined in the root segment of a message type, for example:
· Plant for Material Master and Batch Master (see example implementation below; you must adjust the
yellow highlighted code with your own receiving systems and message types)
· Purchase Organization for Vendor
· Sales Organization for Customer

Sample code:
METHOD if_ex_idoc_creation_check~idoc_data_check.
* type definition for EWM
TYPES: BEGIN OF lty_ewm_receiver,
rcvpor TYPE edi_rcvpor,
mestyp_matmas TYPE edi_mestyp,
mestyp_batmas TYPE edi_mestyp,
mestyp_clfmas TYPE edi_mestyp,
fobjtype_plant TYPE fobjtype,
END OF lty_ewm_receiver.

DATA: ls_ewm_receiver TYPE lty_ewm_receiver,

lt_ewm_receiver TYPE TABLE OF lty_ewm_receiver,
ls_tbd06_batmas TYPE tbd06,
ls_tbd05_matmas TYPE tbd05,
ls_tbd05_clfmas TYPE tbd05,
ls_idoc_data LIKE LINE OF idoc_data,
ls_e1batmas TYPE e1batmas,
ls_e1oclfm TYPE e1oclfm,
ls_e1maram TYPE e1maram,
lv_matnr TYPE matnr,
lt_matnr TYPE TABLE OF matnr,
lt_plants TYPE TABLE OF werks,
lt_ale_model TYPE TABLE OF bdi_model.

************************************************************************************
*
* Example coding for enhanced selection based on plants to decentralized EWM
* This coding is only an example. You may need to adjust it to your own needs.
*
* The coding enables that ALE filtering by plant for material and/or batch as well as
* classification transfer is enhanced
* Usually a ALE filtering by plant will only cause that E1MARCM segments will be filtered out
* from the data transfer
* But as default the material header (E1MARAM) will not be affected by the plant filter
* If the requirement is that material headers are only sent if the material is at least defined
* for one plant contained in the plant filters, this can be done by the following coding
* If a plant filter is used for the material the coding in the BAdI will cause the following
* - materials for the below defined systems and message types are only sent if the material is
* defined for at least one plant in the plant filter (additional ALE filters like material
* group,... are of course also used upfront by ALE )
* - for batches (BATMAS) if an ALE filter is defined with reference to the material ALE filter
* (and there a plant filter is used),
* then also only batches are sent for materials that are defined for at least one plant
* contained in the filter
* - The same/similar logic as for batches applies for sending of classifications (CLFMAS).

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Appendix © 2019 SAP AG or an SAP affiliate company. All rights reserved. 60

************************************************************************************

* define which systems are a decentral EWM in S/4 and which message types are used for transfer
* TODO by consultant/who sets this up.
* You must adjust this to your systems and message types or alternative logic to define which
* systems/message types are relevant
CLEAR ls_ewm_receiver.
ls_ewm_receiver-rcvpor = 'EWMLNT001'.
ls_ewm_receiver-mestyp_matmas = 'ZEWMMATMAS'.
ls_ewm_receiver-mestyp_batmas = 'BATMAS'.
ls_ewm_receiver-mestyp_clfmas = 'CLFMAS'.
ls_ewm_receiver-fobjtype_plant = 'WERKS'.
APPEND ls_ewm_receiver TO lt_ewm_receiver.
CLEAR ls_ewm_receiver.
ls_ewm_receiver-rcvpor = 'EWMCLNT002'.
ls_ewm_receiver-mestyp_matmas = 'ZEWMMATMAS'.
ls_ewm_receiver-mestyp_batmas = 'BATMAS'.
ls_ewm_receiver-mestyp_clfmas = 'CLFMAS'.
ls_ewm_receiver-fobjtype_plant = 'WERKS'.
APPEND ls_ewm_receiver TO lt_ewm_receiver.

* check if this is a transfer to EWM for material or batch

CLEAR ls_ewm_receiver.
READ TABLE lt_ewm_receiver INTO ls_ewm_receiver WITH KEY
rcvpor = idoc_control-rcvpor.
* if no EWM target system, exit
IF sy-subrc <> 0.
RETURN.
ENDIF.

* check if this is a material or batch transfer. If not exit

IF idoc_control-mestyp <> ls_ewm_receiver-mestyp_matmas AND
idoc_control-mestyp <> ls_ewm_receiver-mestyp_batmas AND
idoc_control-mestyp <> ls_ewm_receiver-mestyp_clfmas.
RETURN.
ENDIF.

********************************************************************
* handling for material.
* avoid that a material header segment is sent and no MARC (plant) segment is contained.
* The plant filter is defined for MARC segment. Without this coding MARC segments would be
* filtered out, but MARA segment would still be sent. This coding avoids that a MARA is sent
* without that a relevant MARC exists
IF idoc_control-mestyp = ls_ewm_receiver-mestyp_matmas.

* check if plant filter is used defined

* read ALE model
SELECT SINGLE * FROM tbd05 INTO ls_tbd05_matmas WHERE
sndsystem = idoc_control-sndprn AND
rcvsystem = idoc_control-rcvpor AND
mestyp = ls_ewm_receiver-mestyp_matmas AND
ftype = '1' AND
fobjtype = ls_ewm_receiver-fobjtype_plant.
IF sy-subrc <> 0.
* no plant filter defined => transfer always
RETURN.
ENDIF.

*Otherwise if plant filter is defined check if at least one MARC is contained.

READ TABLE idoc_data TRANSPORTING NO FIELDS WITH KEY segnam = 'E1MARCM'.
IF sy-subrc <> 0.
* if no MARC is contained there can be multiple reasons.
* - either all MARC got filtered out as material does not exist in the plants of the filter
* - or a transfer of changes pointers is done and MARC was not changed

* get plant selections for the material message type

SELECT fobjvalue FROM tbd05 INTO TABLE lt_plants WHERE
sndsystem = idoc_control-sndprn AND
rcvsystem = idoc_control-rcvpor AND
mestyp = ls_tbd05_matmas-mestyp AND
fobjtype = ls_ewm_receiver-fobjtype_plant.
* if no plant selections defined, do not do additional filtering
IF sy-subrc <> 0 OR lt_plants IS INITIAL.
RETURN.
ENDIF.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Appendix © 2019 SAP AG or an SAP affiliate company. All rights reserved. 61

* get current material of IDoc
READ TABLE idoc_data WITH KEY segnam = 'E1MARAM' INTO ls_idoc_data.
IF sy-subrc = 0.
ls_e1maram = ls_idoc_data-sdata.
lv_matnr = ls_e1maram-matnr.
ELSE.
create_idoc = abap_false.
RETURN.
ENDIF.

* check if any MARC segement exists for the product that is forseen to be transferred
* if yes, this means that also the batches for it can be sent
SELECT matnr FROM marc INTO TABLE lt_matnr FOR ALL ENTRIES IN lt_plants
WHERE matnr = lv_matnr AND
werks = lt_plants-werks.
IF sy-subrc <> 0 OR lt_matnr IS INITIAL.
create_idoc = abap_false.
RETURN.
ENDIF.
ENDIF.
ENDIF.
********************************************************************

********************************************************************
* handling for batch.
* check if batch shall be transferred based as reference to material.
* The plant filter is defined for MARC segment. Without this coding MARC segments would be
* filtered out, but MARA segment would still be sent. This coding avoids that a MARA is sent
* without that a relevant MARC exists
IF idoc_control-mestyp = ls_ewm_receiver-mestyp_batmas.
SELECT SINGLE * FROM tbd06 INTO ls_tbd06_batmas WHERE
sndsystem = idoc_control-sndprn AND
rcvsystem = idoc_control-rcvpor AND
bobjtype = 'BUS1001002' AND
method = 'SAVEREPLICA' AND
ftype = '3' AND
fobjtype = 'MATNR'.
IF sy-subrc <> 0.
* if no distribution based on reference to matmas => do not do additional filtering
RETURN.
ENDIF.

* get plant selections for the material message type

SELECT fobjvalue FROM tbd05 INTO TABLE lt_plants WHERE
sndsystem = idoc_control-sndprn AND
rcvsystem = idoc_control-rcvpor AND
mestyp = ls_tbd06_batmas-fmestyp AND
fobjtype = ls_ewm_receiver-fobjtype_plant.

* if no plant selections defined, do not do additional filtering

IF sy-subrc <> 0 OR lt_plants IS INITIAL.
RETURN.
ENDIF.

* get current material of IDoc

READ TABLE idoc_data WITH KEY segnam = 'E1BATMAS' INTO ls_idoc_data.
IF sy-subrc = 0.
ls_e1batmas = ls_idoc_data-sdata.
lv_matnr = ls_e1batmas-material.
ELSE.
create_idoc = abap_false.
RETURN.
ENDIF.

* check if any MARC segement exists for the product that is forseen to be transferred
* if yes, this means that also the batches for it can be sent
SELECT matnr FROM marc INTO TABLE lt_matnr FOR ALL ENTRIES IN lt_plants
WHERE matnr = lv_matnr AND
werks = lt_plants-werks.
IF sy-subrc <> 0 OR lt_matnr IS INITIAL.
create_idoc = abap_false.
RETURN.
ENDIF.

ENDIF.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Appendix © 2019 SAP AG or an SAP affiliate company. All rights reserved. 62

********************************************************************
* handling for classifications.
* check if batch shall be transferred based as reference to material.
* The plant filter is defined for MARC segment. Without this coding MARC segments would be
* filtered out, but MARA segment would still be sent. This coding avoids that a MARA is sent
* without that a relevant MARC exists
IF idoc_control-mestyp = ls_ewm_receiver-mestyp_clfmas.
SELECT SINGLE * FROM tbd05 INTO ls_tbd05_clfmas WHERE
sndsystem = idoc_control-sndprn AND
rcvsystem = idoc_control-rcvpor AND
mestyp = ls_ewm_receiver-mestyp_clfmas AND
ftype = '3' AND
fobjtype = 'MATNR'.
IF sy-subrc <> 0.
* if no distribution based on reference to matmas => do not do additional filtering
RETURN.
ENDIF.

* get plant selections for the material message type

SELECT fobjvalue FROM tbd05 INTO TABLE lt_plants WHERE
sndsystem = idoc_control-sndprn AND
rcvsystem = idoc_control-rcvpor AND
mestyp = ls_tbd05_clfmas-fmestyp AND
fobjtype = ls_ewm_receiver-fobjtype_plant.

* if no plant selections defined, do not do additional filtering

IF sy-subrc <> 0 OR lt_plants IS INITIAL.
RETURN.
ENDIF.

* get current material of IDoc

READ TABLE idoc_data WITH KEY segnam = 'E1OCLFM' INTO ls_idoc_data.
IF sy-subrc = 0.
ls_e1oclfm = ls_idoc_data-sdata.
CASE ls_e1oclfm-object_table.
WHEN 'MARA' OR 'MCH1' OR 'MCHA'.
* we truncate the other fields. Assumption is that the material is the first element
* in the concatenated OBJEK
lv_matnr = ls_e1oclfm-objek.
WHEN OTHERS.
* the mentioned object tabel was not expected => check and adopt your coding
* you may also use different ALE filters...
ASSERT CONDITION 1 = 0.
ENDCASE.
ELSE.
create_idoc = abap_false.
RETURN.
ENDIF.

* check if any MARC segement exists for the product that is forseen to be transferred
* if yes, this means that also the batches for it can be sent
SELECT matnr FROM marc INTO TABLE lt_matnr FOR ALL ENTRIES IN lt_plants
WHERE matnr = lv_matnr AND
werks = lt_plants-werks.
IF sy-subrc <> 0 OR lt_matnr IS INITIAL.
create_idoc = abap_false.
RETURN.
ENDIF.

ENDIF.

ENDMETHOD.

Appendix A-2: Sequencing Batch Classification via BAdI VBW_BATCH_REPLICATE

You implement BAdI VBW_BATCH_REPLICATE in the sender system to ensure that batch classification data is
transferred together with the corresponding batch master records. With the activation of the BAdI
implementation, the sequencing of classification data and batch master data is ensured as the classification is
transferred together with BATMAS via BAPI_BATCH_SAVEREPLICA. Scheduling CLFMAS is still recommended
for changes to classification data of a batch that do not directly result in a change of the batch master itself, for
example custom characteristics.
Procedure

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Appendix © 2019 SAP AG or an SAP affiliate company. All rights reserved. 63

Create BAdI Implementation for batch managed materials which are using classification.
Return ABAP_TRUE for exporting parameter EV_ALLOW_TRANS_CL to transfer classification data together with
BATMAS.

Appendix A-3: Converting Material Master Data via BAdI BADI_MATMAS_ALE_CR

The following example implementation of BADI_MATMAS_ALE_CR, method CHANGE_MATMAS contains an
example where fields MARA-PSTAT and MARA-VPSTA are changed based on the receiving systems(s) and
message type. The implementation filters all values from the status which are not required for EWM (here values
KLEVQ). You must at least adjust the yellow highlighted code.

METHOD if_ex_badi_matmas_ale_cr~change_matmas.

DATA: ls_e1maram TYPE e1maram,

lv_number_char TYPE i,
lv_index TYPE sy-index,

*this is the default status combination for EWM relevant fields/views

* you may adjust it with your own values
lv_vpsta_ewm_fields TYPE string VALUE 'KLEVQ',
lv_pstat_ewm_fields TYPE string VALUE 'KLEVQ'.

FIELD-SYMBOLS: <ls_idoc_data> LIKE LINE OF t_idoc_data.

* check if for message type and receiver an adjustment of PSTAT should be done
* you must adjust this to your own needs. So e.g. for your elevant receiver systems
* and/or the message types for which a PSTAT replacement should be done
IF NOT
(
( f_idoc_header-rcvprn = 'EWMCLNT001' AND f_idoc_header-mestyp = 'ZEWMMATMAS' ) OR
( f_idoc_header-rcvprn = 'EWMCLNT002' AND f_idoc_header-mestyp = 'ZEWMMATMAS' )
).
RETURN.
ENDIF.

* get header of material where PSTAT and VPSTA is contained

READ TABLE t_idoc_data ASSIGNING <ls_idoc_data> WITH KEY
segnam = 'E1MARAM'.
ASSERT CONDITION sy-subrc = 0.
ls_e1maram = <ls_idoc_data>-sdata.

* check which of the values in PSTAT are relevant for EWM. Only keep those
lv_number_char = strlen( ls_e1maram-pstat ).
DO lv_number_char TIMES.
lv_index = sy-index - 1 .
IF NOT ls_e1maram-pstat+lv_index(1) CA lv_pstat_ewm_fields .
ls_e1maram-pstat+lv_index(1) = ' '.
ENDIF.
ENDDO.

* check which of the values in VPSTA are relevant for EWM. Only keep those
lv_number_char = strlen( ls_e1maram-vpsta ).
DO lv_number_char TIMES.
lv_index = sy-index - 1 .
IF NOT ls_e1maram-vpsta+lv_index(1) CA lv_vpsta_ewm_fields .
ls_e1maram-vpsta+lv_index(1) = ' '.
ENDIF.
ENDDO.

* remove blanks that got set during the above replacement

CONDENSE ls_e1maram-pstat NO-GAPS.
CONDENSE ls_e1maram-vpsta NO-GAPS.

* write back changes to IDoc SDATA

<ls_idoc_data>-sdata = ls_e1maram.

ENDMETHOD.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Appendix © 2019 SAP AG or an SAP affiliate company. All rights reserved. 64

Appendix A-4: Transfer of Address for Customer/Vendor via Customer Exit
If “dependent distribution” is used for transfer of address data (AddressOrg.SaveReplica , ADRMAS) and at the
same time for the dependent objects (customer/vendor IDoc) filters are used (for example account group,…)
then in addition the following user exits have to be implemented. Without these user exits, the filters of the
dependent objects (in our examples for ZEWMCREMAS and ZEWMDEBMAS) will not be considered (which results
in too many address IDocs ADRMAS are transferred as no filter is used).
Note 354107 (ALE: Customers or vendor-dependent distribution) describes this in detail, in the following example
implementations are shown and the relevant user exists are listed.

The relevant enhancements/components are (can be viewed in transaction SMOD):

· Enhancement VSV00002 (Read filter objects for vendor master)
o EXIT_SAPLKD03_001 (User Exit Customer and Vendor Distrib.)
· Enhancement VSV00003 (Read filter objects for customer master)
o EXIT_SAPLVV01_002 (Customer Exit for Customer-Specific Filter Objects)

To implement them start transaction CMOD.

· Enter a project name (e.g. ZEWM). Mark in “subobjects” the field “enhancement assignment”. Click on
“Create”

· Enter a short text e.g. “ALE cust. vend. dependent distribution”.

· Click on “Enhancement Assignment”.
· Enter the enhancements “VSV00002” and “VSV00003”. Save

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Appendix © 2019 SAP AG or an SAP affiliate company. All rights reserved. 65

· Click on “components”. Now a list with functions EXIT_SAPLKD03_001 and EXIT_SAPLVV01_002 shows
up

Double click on EXIT_SAPLKD03_001. The source code appears. Double click on the INCLUDE name (here
ZXVSVU05)

· You will be asked if you want to create the include. Confirm this an save it.
· In the include for EXIT_SAPLKD03_001 enter the following coding (adjust the yellow parts by your own
sender, receiver systems, view name and message types). You can get this from what you have entered
in BD64.
*&---------------------------------------------------------------------*
*& Include ZXVSVU05
*&---------------------------------------------------------------------*

CONSTANTS fobject_ktokk TYPE bdi_flttyp-objtype VALUE 'KTOKK'.

LOOP AT filter_object_type.
CLEAR filter_object_value.
filter_object_value-objtype = filter_object_type-objtype.
CASE filter_object_type-objtype.
WHEN fobject_ktokk.
IF vendor_general_data-ktokk IS NOT INITIAL.
filter_object_value-objvalue = vendor_general_data-ktokk.
APPEND filter_object_value.
ENDIF.
ENDCASE.
ENDLOOP.

· Do the same for enhancement function EXIT_SAPLVV01_002. In the function module double-click on
Include ZXVSVU06

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Appendix © 2019 SAP AG or an SAP affiliate company. All rights reserved. 66

· You will be asked if you want to create the include. Confirm this an save it.
· In the include for EXIT_SAPLVV01_002 enter the following coding (adjust the yellow parts by your own
sender, receiver systems, view name and message types). You can get this from what you have entered
in BD64.
*&---------------------------------------------------------------------*
*& Include ZXVSVU06
*&---------------------------------------------------------------------*
CONSTANTS fobject_ktokd TYPE bdi_flttyp-objtype VALUE 'KTOKD'.

LOOP AT filter_object_type.
CLEAR filter_object_value.
filter_object_value-objtype = filter_object_type-objtype.
CASE filter_object_type-objtype.
WHEN fobject_ktokd.
IF general_data-ktokd IS NOT INITIAL.
filter_object_value-objvalue = general_data-ktokd.
APPEND filter_object_value.
ENDIF.
ENDCASE.
ENDLOOP.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Appendix © 2019 SAP AG or an SAP affiliate company. All rights reserved. 67

Appendix B – Additional Information about IDoc/ALE
Frequently-used transactions:
· /SCWM/MON: Warehouse Monitor. you can view EWM relevant IDocs under Tools ® IDOCs.
Prerequisite: EWM-relevant message types must exist in Customizing for Extended Warehouse
Management under Monitoring ® Message Queue Monitoring ® Define IDoc Mapping.
· WE05: IDoc List
· WE02: Display IDoc
· BD87: Status Monitor for ALE Messages. You can use it to reprocess failed IDocs in receiver system
· SM58: Transactional RFC
· SALE: Customizing for ALE

Useful menu paths from the SAP Easy Access menu:

· ALE ® ALE Administration or ALE ® ALE Development
· ALE ® ALE Administration ® Services ® Periodic Processing.
· ALE ® ALE Administration ® Services ® Change Pointers: you use activities in this path to reorganize
change pointers.

ALE documentation:
Documentation for ALE is available under IDoc Interface/ALE. For example, periodic tasks are explained under
IDoc Interface/ALE ® Administration ® Administration of ALE Functions ® Periodic Tasks

Appendix C - List of EWM-Related BC Sets in SAP ERP

The following table lists BC Sets in SAP ERP that are related to decentralized EWM and may be relevant for your
warehouse processes.
BC Set Description
/SPE/COMPLETE Complete Set of SPE BC Sets
/SPE/MATERIAL_SCREENS Enhance material screen sequences
/SPE/TVSHP Shipping parameters on client level
/SPE/SPM_RETURNS_SHIPPED_IMG Basic Setting SPM Complaints & Returns IMG Shipped
(NO ORG)
/SPE/STO_DISCREPANCIES Basic customizing for STO Discrepancies
/SPE/TRANSPORTATION_CROSS_DOCK Service Parts Management: Transportation Cross-
Docking
/SPE/TNAPR Message processing routines
/SPE/DIRECT_OUTBOUND_DELIVERIES Customizing for Direct Outbound Deliveries
/SPE/DIRODO_ACC_ASSIGNMENT Account Assignments for Direct Outbound Deliveries

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Appendix © 2019 SAP AG or an SAP affiliate company. All rights reserved. 68

Appendix D – List of SAP Notes Related to EWM
Implementation

The following SAP Notes may help you with your EWM implementation:
SAP Note Description / Comment
2450387 Which document type or item type for which warehouse request?
The SAP Note contains as attachment an overview of available BC Sets for EWM warehouse
requests.
2464460 Restricted usage of BC sets in embedded EWM in S/4HANA and in de-central EWM
2775345 Restrictions of Decentralized EWM on S/4HANA 1809 FPS02
2782080 Overview of Guides or Best Practices Documents for Extended Warehouse Management
The SAP Note contains a list of available guides for each EWM deployment options.

Integration of SAP ERP or SAP S/4HANA with decentralized EWM in S/4HANA PUBLIC

Appendix © 2019 SAP AG or an SAP affiliate company. All rights reserved. 69

www.sap.com/contactsap

www.sdn.sap.com/irj/sdn/howtoguides

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