Skip to Content
Technical Articles

SAP ERP or SAP S/4HANA Integration Settings with Decentral EWM on S/4HANA 1909

Objective –

To provide integration steps for SAP ERP or SAP S/4HANA with Decentralized EWM in S/4HANA 1909

Overview –

Decentralized EWM on an SAP S/4HANA means EWM application is deployed on the SAP S/4HANA on premise stack. The core enterprise management logistics applications (PP, SD, MM, etc.) are not used in decentralized EWM on SAP S/4HANA system and client.

With decentralized EWM on SAP S/4HANA system, master data is transferred from SAP ERP /SAP S/4HANA using ALE/IDOC and transaction data flows using qRFC.

  • Master data is always distributed from SAP ERP to EWM i.e. In the IDoc settings, Sender system is always SAP ERP and receiving system is always Decentralized SAP EWM. To setup the distribution of following master data from SAP ERP to decentralized EWM on SAP S/4HANA, SAP Standard technologies Application Link Enabling (ALE)-IDoc is used –

Materials, Vendor, Customer, Address, Batches & Classes – Class Master, Characteristics Master and Classification Master

Note – Before proceeding with these settings for master data, system connection and global settings such as RFC destinations and logical systems should exist in both the systems (explained in this blog in transactional data flow settings)

 

Settings Path Details

Creating Reduced Message Types in ERP System and Decentralized EWM System

Transporting Reduced Message Types to Decentralized EWM

Creating New Filter Object Types

 

 

 

SE38

/SPE/R_DEC_EWM_REDUCE_MESSTYPE –

This report is used to create the reduced message types in the sender and receiver system (SAP ERP or SAP S/4HANA)

In this report, Select

Reduce Material Message Type MATMAS

Reduce Vendor Message Type CREMAS

Reduce Customer Message Type DEBMAS

Note – Execute this same report in Decentralized EWM system as well

 

Creating ALE Configuration in ERP System

Creating Port for IDoc Processing in Sender System

Define Partner Profile in SAP ERP or S/4HANA

Defining Data Distribution Model and Distributing Views in SAP ERP or S/4HANA

Converting Data Between Sender and Receiver

Activating Change Pointers in Sender System

Activating enhanced settings for data transfer

SE38

/SPE/R_DEC_EWM_ALE_CUST –

This report is used to maintain ALE customizing in the sender system (SAP ERP or SAP S/4HANA)

 

In this report, Select

Reduce Material Message Type MATMAS

Reduce Vendor Message Type CREMAS

Reduce Customer Message Type DEBMAS

Activate Change Pointer

Maintain Distribution Model

 

Creating ALE Configuration in decentralized EWM

 

Define Partner Profile in decentralized EWM

 

 

 

 

 

 

 

SE38

/SCWM/R_DEC_EWM_ALE_CUST –

This report is used to maintain ALE customizing in the receiving system (Decentralized EWM)

 

In this report, Select

 Reduce Material Message Type MATMAS

 Reduce Vendor Message Type CREMAS

 Reduce Customer Message Type DEBMAS

 Maintain Partner Profiles and Outbound Parameters

 Select Immediate IDoc Mode or Collective IDoc Mode

 

  • Master Data distribution settings via ALE/IDoc in SAP ERP or S/4HANA system –
Setting Path Details
Executing Initial Transfer of Characteristics BD91

Enter below data in the transaction –

1.      Characteristics – Empty

2.      Logical System – EWM Logical System

Executing Initial Transfer of Classes BD92

Enter below data in the transaction –

1.      Class Type – 023

2.      Classes – Classes used for batch classification

3.      Logical System – EWM Logical System

Executing Initial Transfer of Materials BD10

Enter below data in the transaction –

1.      Material – Empty

2.      Message Type –

Reduced message type for materials (created in earlier report in step 1)

3.      Logical System – EWM Logical System

4.      Send Material in Full – Empty

Executing Initial Transfer of Characteristics BD90

Enter below data in the transaction –

1.      Material – Empty

2.      Batch – Empty

3.      Logical System – EWM Logical System

Executing Initial Transfer of Customers BD12

Enter below data in the transaction –

1.      Customer – Empty

2.      Output Type –

Reduced message type for Customers (created in earlier report in step 1)

3.      Logical System – EWM Logical System

Executing Initial Transfer of Vendors BD14

Enter below data in the transaction –

1.      Vendor – Empty

2.      Output Type –

Reduced message type for Vendors (created in earlier report in step 1)

3.      Logical System – EWM Logical System

Creating IDoc Using Change Pointers Automatically SA38

1.      Go to Program RBDMIDOC

2.      Create a variant for each of the below message type –

a.      CHRMAS: Class system: Characteristics master

b.      CLSMAS: Class system: Classes master

c.       CLFMAS: Class system: Classification master

d.      Reduced message type for vendors

e.      Reduced message type for customers

f.       Reduced message type for materials

g.      BATMAS: Batch

3.      Select background and define a job to execute all the above variants of program in background

4.      This job should be scheduled periodically so that master data in decentralised EWM is updated automatically

 

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

Settings in SAP ERP (or SAP S/4HANA) for decentralized EWM on SAP S/4HANA system Transactional Data

Setting Path Details
RFC User Creation Tools → Administration → User Maintenance → Users Create RFC user with the help of BASIS team following the EWM 9.5 roles and authorization guide (Source provided in the reference section)
Define RFC Destination to SAP EWM Tools → Administration   → Administration   → Network → RFC Destinations (SM59)

1.  Create a new RFC destination with naming convention as <EWM System Name>CLNT<client> for example EWMCLNT100

2.  Select the connection type as ABAP System i.e. 3

3.  In technical Setting tab, enter Target Host and system number as message server and instance number resp. of SAP Logon system

4.  In ‘Logon and Security tab’, enter the userid and password of RFC User created in step 1

5.  Check if the connection is established by clicking on ‘Connection Test’.

6.      Verify if logon with the userid and password is working by clicking on ‘Remote Logon’.

Define Logical System SAP NetWeaver → Application Server → IDoc Interface / Application Link Enabling (ALE) → Basic Settings → Logical Systems → Define Logical System (BD54)

Create a new logical system with naming convention as <EWM System Name>CLNT<Client> for example EWMCLNT100 (EWM Logical System) and

 

<S/4HANA System Name>CLNT<Client> for example SADCLNT100 (S/4HANA Logical System)

Assignment of Logical System to Client Tools → Administration → Administration → Client Administration
→ Client Maintenance (SCC4)
Select your system client and enter the S/4HANA logical system which we defined in step 2 i.e. SADCLNT100
Determination of RFC Destination for Method calls SAP NetWeaver → Application Server → IDoc Interface/Application Link Enabling (ALE) → Communication → Determine RFC Destinations for Method Calls

1.      Select EWM logical system created in step 3 i.e. EWMCLNT100 and click on ‘Standard BAPI Destination’.

2.      In the RFC destination for BAPI calls field, enter the RFC destination of the SAP S/4HANA EWM system i.e. EWMCLNT100

3.      Check Table TBLSYSDEST has been updated with the logical system and assigned RFC destination.

Define Queue for Transfer to SAP S/4HANA EWM Logistics Execution → Extended Warehouse Management Integration → Basic Setup of Connectivity → Define Queue for Transfer to SAP EWM

Create a new entry with below fields and its values –

Receiver – EWM Logical system i.e. EWMCLNT100

Queue Type                     Inbound

Agg SQueue                     No Aggregation

MQueue Act                    Mass Queue Disabled

MQueue Par                    1

Setting up QOUT Scheduler SMQS

To enable the automatic processing of messages in the outbound queue, QOUT scheduler is setup.

Go to SMQS transaction and register with below parameters –

Destination                     EWMCLNT100

Max. Conn.                     1 (Default)

Max. Runtime                60 (Default)

W/o tRFC                        Empty (Default)

Scheduler Monitoring  0 (Default)

Setting up QIN Scheduler SMQE

To enable the automatic processing of messages in the outbound queue, QOUT scheduler is setup.

Go to SMQS transaction and register with below parameters –

Queue name                     DLW*

Mode                                 D (Default)

Max. Runtime                    60

Destination                        Empty (Default)

Attempts                            Empty (Default)

Pause                                 300

Scheduler Monitoring   0 (Default)

 

Repeat the same steps for Queue name DLV*, EWM*, CF*, WM*.

Assign Logical System and Queue Type SCM Extended Warehouse Management → SCM Basis
→ Integration → Basic Settings for Creating the System Landscape → Assign Logical System and Queue Type

In this step, Business system group is assigned to Logical system and Queue types.

 

Create entry with below parameters –

Business System Group      SAD100

Logical System                     SADCLNT100

SAP Ind.                                 X

Release                                  700

Queue Type                           Inbound

Error Handling                       Strict

Role                                         Not Specified

Control for RFC queues SCM Extended Warehouse Management → Extended Warehouse Management → Interfaces → ERP Integration → General Settings → Control for RFC Queue

It is used to define outbound communication.

 

Create entry with below parameters –

Business System  SAD100

Queue Type                        I Inbound Queues

Aggr. Single Queues           No Aggregation

Mass Queue Act. Mass Queue Deactivated

Parallel Mass Queues         Leave empty (Default)

Specify Characteristics for System Messages Logistics Execution Shipping ® System Modifications ® Specify Characteristics for System Messages (OVM1)

It is used to reprocess inbound queues in Logistics Execution that are erroneous due to locking issues.

 

Create entry with below parameters –

Call Type                               Leave this field empty

Work phase                          Leave this field empty

Application Area   /SPE/IF_SERVICES

Message Number   023

Message Type                      E

Log Sent and Received Messages Logistics Execution → Extended Warehouse Management Integration → Basic Setup of Connectivity → Log Sent and Received Messages

To log the inbound and outbound messages, this step is performed and is optional.

Create a new entry and For Log received and Log send, select log error messages from the dropdown list

Registering Display Programs for Application Log SMQE

To get the detail error message of the stuck queue, this step is performed and is optional.

Create below entries for each type of queues –

DLV*      /SPE/QUEUE_DISPLAY_TOOLS

DLW*     /SPE/QUEUE_DISPLAY_TOOLS

EWM*   /SPE/QUEUE_DISPLAY_TOOLS

WM*     /SPE/QUEUE_DISPLAY_TOOLS

 

  • Settings in decentralized EWM on SAP S/4HANA system for SAP ERP (or SAP S/4HANA) Transactional Data flow –
Setting Path Details
RFC User Creation Tools → Administration → User Maintenance  → Users Create RFC user with the help of BASIS team following the EWM 9.5 roles and authorization guide (Source provided in the reference section)
Define RFC Destination to SAP EWM Tools → Administration   → Administration   → Network → RFC Destinations (SM59)

1.  Create a new RFC destination with naming convention as <SAP ERP System Name>CLNT<client> for example SADCLNT100

2.  Select the connection type as ABAP System i.e. 3

3.  In technical Setting tab, enter Target Host and system number as message server and instance number resp. of SAP Logon system

4.  In ‘Logon and Security tab’, enter the userid and password of RFC User created in step 1

5.  Check if the connection is established by clicking on ‘Connection Test’.

6.      Verify if logon with the userid and password is working by clicking on ‘Remote Logon’.

Define Logical System SAP NetWeaver → Application Server → IDoc Interface / Application Link Enabling (ALE) → Basic Settings → Logical Systems → Define Logical System (BD54)

Create a new logical system with naming convention as <EWM System Name>CLNT<Client> for example EWMCLNT100 (EWM Logical System) and

 

<S/4HANA System Name>CLNT<Client> for example SADCLNT100 (S/4HANA Logical System)

Assignment of Logical System to Client Tools → Administration → Administration → Client Administration
→ Client Maintenance (SCC4)
Select your system client and enter the S/4HANA logical system which we defined in step 2 i.e. EWMCLNT100
Determination of RFC Destination for Method calls SAP NetWeaver → Application Server → IDoc Interface/Application Link Enabling (ALE) → Communication → Determine RFC Destinations for Method Calls

4.      Select SAP ERP logical system created in step 3 i.e. SADCLNT100 and click on ‘Standard BAPI Destination’.

1.      In the RFC destination for BAPI calls field, enter the RFC destination of the SAP ERP system i.e. SADCLNT100

2.      Check Table TBLSYSDEST has been updated with the logical system and assigned RFC destination.

Determination of RFC Destination for Method calls from EWM (If EWM is part of add-on to SAP ERP, otherwise not required) Tools → ABAP Workbench → Development → ABAP Editor (SE38)

1.      Go to program /SCWM/R_ERP_RFC_DEST

2.      On the Assign a Standard BAPI Destination screen, In the RFC Destination field, enter the RFC destination of the S/4HANA system i.e. SADCLNT100

3.      Check Table TBLSYSDEST has been updated with the logical system and assigned RFC destination.

Define Business System SCM Extended Warehouse Management → Extended Warehouse Management → Interfaces → ERP Integration → General Settings → Define Business System

1.      Create a new entry for each system that is part of your system landscape with naming convention as <SAP ERP Name><Client number> i.e. SAD100. And

<SAP EWM Name><Client number> i.e. EWM100

2.      Create entries for each system.

3.      Check table /SCMB/TUBSSYS has been updated with business system.

Define Own Business System SCM Extended Warehouse Management → Extended Warehouse Management → Interfaces → ERP Integration → General Settings → Define Own Business System

1.      It is defined to name the business system of the system in which you have installed EWM

2.      Create a new entry for each system that is part of your system landscape with naming convention as <SAP EWM System Name><Client number> i.e. EWM100.

3.      Create entries for each system.

4.      Check table /SCMB/TOWNBS has been updated with business system.

Maintain Business System Group SCM Extended Warehouse Management → SCM Basis
→ Integration → Basic Settings for Creating the System Landscape → Maintain Business System Group
Create a business system group with naming convention as BSG_SAD whereas SAD being system name.
Setting up QOUT Scheduler SMQS

To enable the automatic processing of messages in the outbound queue, QOUT scheduler is setup.

Go to SMQS transaction and register with below parameters –

Destination                     SADCLNT100

Max. Conn.                     1 (Default)

Max. Runtime                60 (Default)

W/o tRFC                        Empty (Default)

Scheduler Monitoring  0 (Default)

Setting up QIN Scheduler SMQE

To enable the automatic processing of messages in the outbound queue, QOUT scheduler is setup.

Go to SMQS transaction and register with below parameters –

Queue name                     DLV*

Mode                                 D (Default)

Max. Runtime                    60

Destination                        Empty (Default)

Attempts                            Empty (Default)

Pause                                 300

Scheduler Monitoring   0 (Default)

 

Repeat the same steps for Queue name DLW*, EWM*, CF*, X*, WMT*, WMDP*.

Assign Logical System and Queue Type SCM Extended Warehouse Management → SCM Basis
→ Integration → Basic Settings for Creating the System Landscape → Assign Logical System and Queue Type

In this step, Business system group is assigned to Logical system and Queue types.

 

Create entry with below parameters –

Business System Group      BSG_SAD

Logical System                     SADCLNT100

SAP Ind.                                 X

Release                                  700

Queue Type                           Inbound

Error Handling                       Strict

Role                                         Not Specified

 

Create similar entries for Logical system of EWM system EWMCLNT100.

Control for RFC queues SCM Extended Warehouse Management → Extended Warehouse Management → Interfaces → ERP Integration → General Settings → Control for RFC Queue

It is used to define outbound communication.

 

Create entry with below parameters –

Business System  SAD100 (SAP ERP)

Queue Type                        I Inbound Queues

Aggr. Single Queues           No Aggregation

Mass Queue Act. Mass Queue Deactivated

Parallel Mass Queues         Leave empty (Default)

Registering Display Programs for Application Log SMQE

To get the detail error message of the stuck queue, this step is performed and is optional.

Create below entries for each type of queues –

DLV*         /SCWM/QRFC_APPL_LOG_DISPLAY

DLW*        /SCWM/QRFC_APPL_LOG_DISPLAY

EWM*      /SCWM/QRFC_APPL_LOG_DISPLAY

WMDP*  /SCWM/QRFC_APPL_LOG_DISPLAY

WMTH*  /SCWM/QRFC_APPL_LOG_DISPLAY

 

In this way, SAP ERP (or SAP S/4HANA) and SAP Decentralized EWM on S/4HANA 1909 integration is configured.

 

Thanks for reading. Hope you would like this blog

Jayant Pawar

 

Reference –

SAP note 2806070 – SAP S/4HANA 1909: Release information and restrictions for EWM in SAP S/4HANA

 

2 Comments
You must be Logged on to comment or reply to a post.