S/4HANA Embedded EWM Integration settings in SAP S/4HANA

[Jayant_Pawar]

Objective –

To provide integration steps for SAP S/4HANA 1909 embedded EWM

Overview –

Embedded EWM is part of S/4HANA installation. It only supports integration with same system instance and client. i.e. it can’t be connected to multiple ERP systems.

We will go through in details of EWM integration settings in S/4HANA 1909.

SAP EWM communicates with other applications of SAP S/4HANA via queued remote function call (qRFC).

 

Setting	Path	Details
Define RFC Destination	Tools → Administration   → Administration   → Network → RFC Destinations (SM59)	Create a new RFC destination with naming convention as <S/4HANA system name>CLNT<client> for example SADCLNT100 Select the connection type as ABAP System i.e. 3 In technical Setting tab, enter Target Host and system number as message server and instance number resp. of SAP Logon system Check if the connection is established by clicking on ‘Connection Test’. 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 <S/4HANA System Name>CLNT<Client> for example SADCLNT100 (S/4HANA Logical System)
Define Dummy 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 <S/4HANA System Name>EWM<Client> for example SADEWM100 (EWM 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	Select EWM logical system created in step 3 i.e. SADEWM100 and click on ‘Standard BAPI Destination’. In the RFC destination for BAPI calls field, enter the RFC destination of the SAP S/4HANA EWM system i.e. SADEWM100 Check Table TBLSYSDEST has been updated with the logical system and assigned RFC destination.
Determination of RFC Destination for Method calls from EWM	Tools → ABAP Workbench → Development → ABAP Editor (SE38)	Go to program /SCWM/R_ERP_RFC_DEST 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 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	Create a new entry for each system that is part of your system landscape with naming convention as <System Name><Client number> i.e. SAD100. Create entries for each system. Check table /SCMB/TBUSSYS 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	It is defined to name the business system of the system in which you have installed EWM Create a new entry for each system that is part of your system landscape with naming convention as <System Name><Client number> i.e. SAD100. Create entries for each system. 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 <System Name><Client number> i.e. SAD100.
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. SADEWM100 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                    SADCLNT100 Max. Conn.                    1 (Default) Max. Runtime                60 (Default) W/o tRFC                      Empty (Default) Scheduler Monitoring    0 (Default)
Setting up QIN Scheduler	SMQR	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*, WM*, X*.
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 Recived 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 X*           RSXMB_SHOW_ENTRY

 

In this way, SAP S/4HANA 1909 embedded EWM 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 (https://launchpad.support.sap.com/#/notes/2806070)

 

 

[former_member670101]

Hello,

Thank you for an informative blog. I have noticed a couple of typos

1. In the step Define Business System the table should be /SCMB/TBUSSYS


2. In the step Setting up QIN Scheduler the transaction should be SMQR. In the description there is a copy-paste from QOUT.


3. In the step "Registering Display Programs for Application Log" maybe it would make sense to mention, that we need to choose from the menu Edit - Register display program, though it could be guessed from the name of the step.

Best regards,

Vasili Tsikhanenka

[atul_joshi2]

Thanks Jayant for detailed setup details

Do you have any SAP note or document with detailed step on SAP EWM basic/ initial and integration setup on EWM embedded on S/4 hana for 1909

[Jayant_Pawar]

Hello Vasili,

 

Thanks for pointing out the typing error. I have corrected it now.

[former_member720105]

Thanks for sharing.

[wlourens2]

Hi,

Thanks for the blog.

On the section on "Determination of RFC Destination for Method calls" --> The RFC we created in the first step is SADCLNT100, not SADEWM100. Since it is an embedded EWM system, we can just point it to SADCLNT100.

Helpfull might be to also list the Post-Activation Steps for Embedded EWM that is required, on URL https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/4cef93946a0b48ec89533b3c34443b85/b476c4df59724f2682c....

KR,

[Prashanth2_D]

Hi Jayant,

The Program - /SCWM/R_ERP_RFC_DEST is obsolete and any alternate program for this?

Thank You!

[former_member846183]

Is there an answer?

[former_member850738]

Yes, look here: SAP NetWeaver → Application Server  → IDoc Interface/Application Link Enabling (ALE)   → Communication  → Determine RFC Destinations for Method Calls (Transaction BD97)

1. On the Assign RFC Destinations for Synchronous Method Calls screen, select the relevant EWM logical system, for example, EWMCLNT001.
2. Choose Standard BAPI destination.
3. In the Assign RFC Destinations for Synchronous Method Calls dialog box, in the RFC destination for BAPI calls field, enter the RFC destination of the SAP EWM system (in capital letters or use the value help).