Embedded SAP EWM: Client BASIS Implementation Step by Step

Embedded SAP EWM client BASIS implementation is the foundational configuration required before any warehouse management processes can run in an S/4HANA environment with integrated EWM. Unlike Decentralised EWM — where EWM runs on a separate system — Embedded EWM shares the same client as S/4HANA, which simplifies the landscape but still requires specific BASIS-level settings to establish correct communication between the ERP and EWM layers. This guide walks through all 11 implementation steps in sequence, from defining the business system to assigning logical systems and queue types.

If you are new to SAP Extended Warehouse Management, it is recommended to first review the foundational concepts before proceeding with this technical implementation.

What Is Embedded SAP EWM and Why Does Client BASIS Matter?

In an Embedded EWM setup, the EWM system runs within the same S/4HANA client rather than as a separate SCM system. This architecture eliminates the need for cross-system ALE (Application Link Enabling) infrastructure, but it does require precise client-level BASIS configuration to ensure that delivery documents, queue communications, and distribution models function correctly.

Client BASIS implementation defines how the ERP and EWM layers identify each other, how they communicate via qRFC queues, and how delivery objects are distributed between them. Skipping or misconfiguring any of these steps typically results in delivery transfer failures, queue errors, or warehouse order creation issues. MDP Group has implemented Embedded EWM across multiple industries; in our experience, the steps below represent the minimum required configuration for a stable system landscape.

Step 1: Define Own Business System

The system uses a business system key across many document flow tables as the primary system identifier. This key must be defined at the SCM system level and must match the EWM location (central EWM structure).

Navigate to:

SPRO → SCM EWM → EWM → Interfaces → ERP Integration → General Setting → Define Own Business System

The naming convention follows the pattern: SAP system number + CLNT + client number. For example: Q4HCLNT100

Step 2: Define Logical System to the Business System

This step establishes the mapping between the logical system and the business system — a critical requirement for ERP-EWM communication. When deliveries are created and sent from the ERP to EWM, the system uses this mapping to identify the target. Similarly, when EWM sends updates back to ERP (such as goods movement confirmations), it uses the logical system to route the information correctly.

Navigate to:

SPRO → SCM EWM → EWM → Interfaces → ERP Integration → General Setting → Define Business System

Example values: Business System: Q4HCLNT100 / Logical System: Q4HCLNT100 / Manual Maintenance flag: set.

Step 3: Add and Check qRFC Destinations

ERP and EWM communicate via queues. Business system destinations must be added at the client level using transaction code SMQS. Set the runtime to 60 seconds.

The existing destination (e.g. Q4HCLNT100) will already be present. Add the EWM business system destination (Q4HEWM100). After configuration, both destinations should appear in the SMQS screen: Q4HCLNT100 and Q4HEWM100.

Step 4: Check qRFC Queues

Queues enable monitoring of process status during ERP-EWM triggering. The system creates differently named queues for each document type in SMQ1 (outbound) and SMQ2 (inbound). All required queues must be present for the implementation to function. Verify queue registration at transaction code SMQR.

Step 5: Check qRFC Queue Administration

In SMQR, confirm that the following queue name patterns are registered with their correct display programs:

• DLV*
• DLW*
• EWM*
• MMPUR*
• WM*
• X*
• ZQMSKIP

Step 6: Create a Distribution Model View

Use transaction code BD64 to create the distribution model view. For EWM, the model view name must start with EWM* (e.g. EWMQ4H100). In the BD64 screen, select “Create Model View” and enter the same value for both the short text and technical name fields.

Step 7: Create a Distribution Model

The distribution model controls the transfer of objects (inbound deliveries, outbound deliveries, etc.) from the SAP ERP system to the SAP EWM system. This step must be repeated for each warehouse number.

SPRO → Integration with Other SAP Components → EWM → Basic Settings for EWM Linkage → Generate Distribution Model from S/4HANA to SAP EWM

Example values: Warehouse Number: CHM1 / EWM Logical System: Q4HEWM100 / Distribution Model View: EWMQ4H100

Step 8: Create BAPI Destination for the Logical System

Standard BAPI destination and standard dialog BAPI must be added to the EWM logical system using transaction code BD97. Select the EWM logical system, then create the standard BAPI destination using the button at the top of the screen.

The Receiver/Server and RFC Destination fields must both contain the EWM logical system value (e.g. Q4HEWM100 for quality or D4HEWM100 for development).

Step 9: Check RFC Destination of Logical System

Verify the RFC destination assignment using table TBLSYSDEST in transaction code SE16N. The Receiver and RFC Destination fields must both show the EWM logical system value (e.g. Q4HEWM100).

Step 10: Maintain Business System Group at the EWM Side

The business system group at the EWM side must match the ERP client. Navigate to:

SPRO → SCM EWM → SCM Basis → Basic Setting for Creating the System Landscape → Maintain Business System Group

Step 11: Assign Logical System and Queue Type

The final step assigns a logical system and queue type to define how document-specific queues are determined for ERP-EWM communication.

SPRO → SCM EWM → SCM Basis → Integration → Basic Setting for Creating the System Landscape → Assign Logical System and Queue Type

With all 11 steps completed, the Embedded EWM client BASIS implementation is ready. You can now proceed with warehouse-specific configuration, such as sort rules for RF screen warehouse tasks or automating warehouse management tasks with SAP EWM.

Frequently Asked Questions

What is the difference between Embedded EWM and Decentralised EWM?

Embedded EWM runs within the same S/4HANA client and does not require a separate SCM system or cross-system ALE configuration. Decentralised EWM operates on a separate system and communicates with ERP via ALE/IDocs. Embedded EWM is the standard approach for new S/4HANA implementations, while Decentralised EWM is typically found in existing landscapes that predate S/4HANA.

What happens if the qRFC queue patterns are not registered correctly in SMQR?

Missing or incorrectly registered queue patterns in SMQR result in delivery transfer failures between ERP and EWM. Documents may appear to be sent from the ERP side but never arrive in EWM, or EWM confirmations may not reach the ERP. Always verify all required queue prefixes (DLV*, EWM*, WM*, etc.) are present before testing document flow.

Does this implementation need to be repeated for each warehouse number?

Step 7 (Create Distribution Model) must be executed for each warehouse number, as the distribution model links the EWM logical system to a specific warehouse. Steps 1 through 6 and Steps 8 through 11 are performed at the client level and do not need to be repeated per warehouse.

Which S/4HANA release does this configuration apply to?

The SPRO paths and transaction codes described in this guide apply to SAP S/4HANA releases from 1709 onwards, which introduced Embedded EWM as the standard warehouse management component. Minor menu path variations may exist between releases, but the configuration objects and logic remain consistent.

Can I verify the ERP-EWM communication without creating a live delivery?

Yes. After completing the configuration, you can use the SMQS and SMQR transaction codes to check that destinations and queue registrations are active. For a functional test, creating a test inbound or outbound delivery in a non-production client and monitoring the queue in SMQ1/SMQ2 is the standard verification method before go-live.

You can contact us for SAP EWM consultancy services.

References

SAP Extended Warehouse Management — SAP Help Portal
What is SAP Extended Warehouse Management (SAP EWM)? — MDP Group
How to Use SAP EWM to Automate Warehouse Management Tasks — MDP Group

MDP Group