S4 HANA EWM System Connection : Basic Settings in 3 Easy Steps

S4 HANA EWM System Connection : Basic Settings in 3 Easy Steps

Basic EWM settings
Basic EWM settings
Home » S4 HANA EWM System Connection : Basic Settings in 3 Easy Steps

In this Customizing activity, we will do the basic settings for Extended
Warehouse Management (EWM) in SAP S/4HANA in 3 easy & quick steps

How to execute S4 HANA EWM System Connection basic Settings in 3 Easy Steps

  1. Step 1 : General settings for the system landscape and the qRFC communication:

    1.1)-Name Logical Systems.
    1.2)-Assign Logical Systems to a Client.
    1.3)-Determine RFC Destinations for Method Calls.
    1.4)-Set up QOUT Scheduler.
    1.5)-Set up QIN Scheduler.

  2. Step 2 : Settings for master data integration

    2.1)-Maintain Business System Group
    2.2)-Assign Logical System & Queue Type

  3. Step 3 : Settings for application integration

    3.1)-Define Own Business System
    3.2)-Define Business System
    3.3)-Assign Warehouse Numbers from Logistics execution
    3.4)-Assign Business Partner to Plant
    3.5)-Control for RFC queue

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

Step 1. General settings for the system landscape and the qRFC.

ERP & EWM systems communicates using an qRFC methods. In this step we will configure this

1.1)-Name Logical System

We have to Define a logical system for ERP client and a logical system for EWM client in Customizing . Logical systems are defined cross-clients

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

Picture : EWM & S4 Logical System
 --> For EWM embedded in SAP S/4HANA, a dummy logical system needs to be created to establish communication between embedded EWM and SAP S/4HANA. 

-> Standalone SAP EWM or decentralized EWM on S4 HANA requires to create an actual logical system for the SAP EWM system.

1.2)-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

Assign the S4 system as per screenshot shown below

Picture : Assign Logical System to Client

We need to carry out the following steps in each ERP (S4) client we want to connect to EWM

1.3)-Determine RFC Destinations for Method Calls

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

In this step assign the logical EWM system to the EWM RFC destination

Picture : Set Up RFC Destination

Next we will set up the scheduler for automated processing of inbound and outbound queues in SAP S/4HANA.

1.4)-Set up QOUT Scheduler

QOUT Scheduler is set in Transaction SMQS.

While setting the outbound scheduler, we will set the logical system for the SAP S/4HANA system as the destination because that is where data from qRFCs will be sent.

Picture : QOUT Scheduler

1.5)-Set up QIN Scheduler

The QIN Scheduler is called with Transaction SMQS.

For the inbound scheduler, we will provide the names of inbound queues that need to be registered. Queues are required to be registered for them to be processed.

Picture : QIN Scheduler

Step 2 : Settings for master data integration

qRFC communication is used

  • To transfer master data using core interface (CIF).
  • To transfer Transactional data i.e.inbound deliveries & outbound deliveries
Picture : qRFC Communication from ERP to EWM and from EWM to ERP.

2.1)-Maintain Business System Group

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

In this IMG activity, we determine the assignment to a business system
group of this system and the ERP systems that are to be connected. By
doing this, you create areas with the same naming conventions. These
guarantee that the same names are used for master data and also their
synchronization in distributed system landscapes.

Picture : Maintain Business System Group

2.2)-Assign Logical System & Queue Type

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.

Picture : Assign Logical System & Queue Type

Step 3 : Settings for application integration

In this step we will configure our own business system & assign logical system to queue type

3.1)-Define Own Business System

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.

Picture : system key for SAP EWM system as a business system

3.2)-Define Business System

Here we will specify a business system for each logical system that we want to connect to EWM, and assign the relevant logical system.

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.

Picture : Define Business System

3.3)-Assign Warehouse Numbers from Logistics Execution

Here we define the mapping of warehouse numbers from an enterprise management system (SAP S/4HANA or SAP ERP) to the warehouse numbers in EWM.

If we are using decentralized EWM on SAP S/4HAN, we can also enter the business system if we want to create a rule for an exceptional case, where an ERP warehouse number maps to a different EWM warehouse number if the data from ERP arrives from a particular business system.

3.4)-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.5)-Control for RFC Queue

SAP EWM uses RFC-enabled function modules to report data to SAP ERP. The following types of message are sent from SAP EWM to SAP ERP

Messages with reference to a delivery in SAP ERP (delivery interface)

  • Reporting delivery changes (for example, quantity changes)
  • Reporting goods movements for the delivery (goods receipt or
    goods issue)

Messages without reference to a delivery in SAP ERP (Goods Movement Interface)

  • Reporting stock postings without reference to a delivery
  • Posting changes without reference to a delivery
  • Reporting inventory differences
  • Scrapping without a delivery in 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.
Picture : Control for RFC Queue

This completes the S4 HANA EWM System basic connection settings.

Missing photo created by Racool_studio – www.freepik.com

None. This is the starting post of our journey to configure our own SAP S4 HANA Embedded/Decentralized EWM working system in the minimum possible configuration efforts.

In the next post we will configure Basic integration settings related to the S4 HANA Embedded/Decentralized EWM. Click on the above link to read in detail.

Join the discussion