Master S/4HANA EWM Integration : Step-by-Step Guide Part 1- The Technical Connectivity Layer

Once the landscape is defined, the next priority is establishing the technical communication layer. This ensures that your Enterprise Resource Planning data flows into the warehouse without synchronization errors or lost deliveries.

Please note that these settings are true for both embedded EWM in S4 HANA & decentralized EWM on S4 HANA.

If any step is different in decentralized EWM on S4 HANA then it is specified specially in the next heading.

Takeaway 1: Naming and Assigning Logical Systems

Logical systems are the backbone of identity in an SAP landscape. These are defined cross-client via Transaction BD54.

• For Embedded EWM: You must define both the ERP client and a “Dummy” EWM logical system.

• For Decentralized EWM: You must maintain an “Actual” logical system for both the S/4HANA ERP and the standalone EWM system.

• Client Assignment: Once named, the logical system must be assigned to the specific client in Transaction SCC4.

Below is the path to configure logical system

SPRO -> Integration with Other SAP Components -> Extended Warehouse Management -> Basic Settings for Setting Up the System Landscape -> Name Logical System

There is another path also to configure the same

SPRO -> SCM Extended Warehouse Management -> SCM Basis -> Integration -> Basic Settings for Creating the System Landscape -> Name Logical System

Assign both the systems

1.1 Assign Logical System to a Client

In this configuration, we will assign a client to each logical system.

Note: These settings must be made after the system installation of a new system has been completed as these settings are not transported

SPRO -> Integration with Other SAP Components -> Extended Warehouse Management -> Basic Settings for Setting Up the System Landscape -> Assign Logical System to a Client

There is another path also to configure the same

SPRO -> SCM Extended Warehouse Management -> SCM Basis -> Integration -> Basic Settings for Creating the System Landscape -> Assign Logical System to a Client

Assign the S4 system as per screenshot shown below

2.1 Configuration of RFC Connection

Before we can configure the determination of RFC Destinations for Method Calls, we need to configure RFC connection

Start SM59

Give your connection name

Input Target Host, Instance Number & IP Address as shown in the below screenshot

HINT

1)-You can use FM “TH_GET_VIRT_HOST_DATA” to know the target host & port (through SE37)

2)-to know the IP address, we can use OS01 as shown in the below screenshots

Now click on Application server and then “Change View” and system will show you IP address

Note

Once we will complete the configuration of the RFC connection, we can see the same in table RFCDES

Start as per below path to configure RFC destinations

SPRO -> Integration with Other SAP Components -> Extended Warehouse Management -> Basic Settings for Setting Up the System Landscape -> Set Up RFC Destination

Alternatively we can use transaction BD97 for this

Select the EWM dummy logical system and click on “Create Standard BAPI destination” and

2.2 Set up QOUT Scheduler

Manages outgoing messages from the source system.

QOUT Scheduler is set in Transaction SMQS.

2.3 Set up QIN Scheduler

Manages incoming messages to the target system.

The QIN Scheduler is called with Transaction SMQR.

Please note that if a queue is not registered, it is not processed i.e. no transfer.

Takeaway 3: Master Data & Application Data Integration

To synchronize material , business partner data and deliveries you must maintain Business System Groups.

3.1 Define the Business System Group (e.g., to group S/4 and EWM clients).

Here we define the business system and all systems that are part of the system landscape.

Here we provide the name of the SAP S/4HANA logical system. The embedded EWM system uses the business system stored in the warehouse to request documents to identify the logical system of SAP S/4HANA

SCM Extended Warehouse Management > SCM Basis > Integration > Basic Settings for Creating System Landscape > Maintain Business System Group.

3.2 Assign Logical System & Queue Type to the group.

Here we assign a logical system to a business system group (BSG). Additionally, you assign a queue type (inbound queue or
outbound queue) to the BSG.

--> To enable error-free communication, every source system (ERP system) must be assigned to a BSG. 

--> A BSG can consist of one or more source systems.

Here we assign the business system group to the logical system of S4 HANA

3.3 Define the “Own Business System” to identify the local instance within the integration landscape.

Here we enter the system key for SAP EWM system as a business system

In this activity we define our own business system. System stores this system key in the document flow tables of the cross-system and cross-partner document flow.

System key defined here must be the same as the system key defined in the System Landscape Directory (SLD)

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

Note : Only EWM system needs to be maintained here

3.4 Define Business System

In SAP Extended Warehouse Management (EWM), the Define Business System step is used to map logical systems to business systems. This mapping is a critical part of ERP–EWM integration.

When deliveries are transferred from the SAP ERP system (S/4HANA or ECC) to EWM, they only carry the logical system information. EWM then uses this configuration to link the logical system with the correct business system and stores it in the delivery.

In the reverse process, when confirmations such as Goods Receipt or Goods Issue are sent back from EWM to ERP, the system refers to this mapping. EWM matches the business system with the logical system and ensures the message is delivered to the right ERP client.

👉 Important: Each business system must be assigned to only one logical system. This ensures unique, consistent, and error-free communication between ERP and EWM.

Example

Suppose your ERP system has a logical system named ERPCLNT100. You can map it to a business system called BS_ERP100.

• When ERP sends a delivery, EWM identifies ERPCLNT100 and automatically maps it to BS_ERP100.
• When EWM sends back a confirmation, it uses the same mapping to make sure the message goes to the correct ERP client.

This configuration is a key integration step that ensures smooth data transfer, reliable confirmations, and strong ERP–EWM connectivity.

We will assign a logical system to only one business system.

If an ERP system is connected to the EWM system, the system needs the mapping of the logical systems to the business systems due to the following reasons:

 --> The deliveries from the ERP system to EWM contain only the  information for the logical system (Defined in SM59 for ERP system). EWM stores the business system in the  warehouse request, so EWM performs a mapping of the logical systems to the business systems.

--> During confirmations from EWM to the ERP system, EWM uses the logical system that originally contained the delivery. EWM then maps the business system to the logical system. So only one logical system is assigned to a business system, to make the assignment unique. Only then can EWM send messages to the ERP system.

CM Extended Warehouse Management > Extended Warehouse Management > Interfaces > ERP Integration > General Settings > Define Business System.

Here we maintain S4 logical system with the same name as Business system

3.5 Assign Business Partners to Plant

Here we maintain link between a party entitled to dispose (disposal party) and a plant.

• This links the plant to a business partner that is only used to manage stock in the warehouse.
• This business partner can differ from the business partner in the vendor role or the customer role that is assigned to a plant and used as ship-to party or ship-from party in the stock transfer order processes.
• It can also differ from the business partner used as the default ship-to party of the warehouse in direct outbound delivery orders.

--> Embedded EWM in SAP S/4HANA
Assignment of a disposal party to a plant is optional. If not assigned, the system uses the business partner in the vendor role that is assigned to the plant as the disposal party.

--> Decentralized EWM
Assignment of a disposal party to a plant is mandatory.

The fields Ship-From and Ship-To are used for the following special processes:

• Transportation Cross Docking (TCD) : In a TCD scenario, the system uses the ship-to party of the relevant outbound delivery and the logical system to determine the cross docking plant
• Kit To Stock : In a kit-to-stock scenario, the system creates inbound and outbound deliveries for goods movement postings. The ship-from and ship-to business partners of these deliveries are determined based on the disposal party that is linked to here.

3.4 Control for RFC Queue

SAP EWM uses RFC-enabled function modules to report data to SAP ERP.

qRFC is used as the communication technology because the delivery-related messages must be serialized. Strict serialization is needed to ensure that the messages are sent to SAP ERP in the correct order so that data inconsistencies can be avoided.

Here maintain the S4 HANA business system name (which we maintained same as logical system in the previous steps)

This completes the S4 HANA EWM System basic connection settings.

4. Possible Errors & Solution

If we have not maintained Business system group/Own system name/RFC destination correctly then system throws the below errors

To remove these errors, please revise the system settings as per above post.

Possible Error 1

Possible Error 2

Possible Error 3

5. FAQ : Basic Connectivity

6. Master S/4HANA EWM Integration : Step-by-Step Video Guide Part-1

To fully understand the foundational steps of SAP S/4HANA–EWM integration, read this post and watch the video titled “Video 1: Connecting SAP S/4HANA & EWM – Basic System Connection Settings Explained [Real-Time Demo]” for a live, step-by-step system setup. The video shows exactly where to click, which parameters to enter, and how the connection behaves in real systems, making the blog’s configuration guidance immediately actionable. Watch it alongside the article to move from theory to confident, hands-on implementation.

To truly master the integration of SAP S/4HANA with EWM, theory alone won’t cut it—real-world application is where the learning sticks. This blog post gave you a practical starting point, but there’s much more to explore. Continue the journey by watching the Full Three-Part Video Series where each episode builds on the last with hands-on demonstrations and expert insights. And don’t miss the additional blog posts linked throughout this page—they dive deeper into configuration steps, troubleshooting tips, and advanced scenarios that will elevate your understanding. Whether you’re implementing, optimizing, or just curious, this series is your roadmap to doing it right.

7. Revision – How to Guide

Missing photo created by Racool_studio – www.freepik.com