SAP EWM in S/4 HANA
Data Replication Framework (DRF) in S/4 HANA
Master Data Integration
Below Master Data‘s are need to be integrated from S/4 HANA with
EWM.
• Material Master
• Batch Master
• Classification
• Business Partner (Vendor/Customer)
Master Data Integration Techniques in S/4 HANA
Master Data S/4 HANA Embedded EWM S/4 HANA De-Central EWM
Material Master No data replication, SCM Product master gets ALE IDOCs are used to replicate S/4
created automatically when S/4 HANA material HANA Material Master as Product
master is created. Warehouse Product master Master in S/4 HANA De-central
needs to be created manually. Mass creation is EWM
possible via monitor transaction
Batch Master No data replication, same S/4 HANA batch ALE IDOCs are used to replicate S/4
master is directly used in EWM HANA Batch Master in S/4 HANA
De-central EWM
Classification No data replication, same S/4 HANA ALE IDOCs are used to replicate S/4
classification data is directly used in EWM HANA Batch Master in S/4 HANA
De-central EWM
Business Partner No data replication, same S/4 HANA BP master ALE IDOC/DRF is used to replicate
is directly used in EWM S/4 HANA BP to S/4 HANA De-
central EWM
Note: IDOC/DRF is used only when De-central EWM is hosted on S/4 HANA. If backend is hosted on S/4 HANA
and connected to De-central EWM 9.5, then CIF is used for master data integration.
Master Data Distribution techniques
BP Integration by DRF
There are two ways to integrate Vendor and Customer from SAP S/4 HANA to SAP S/4 HANA De-Centralized
EWM.
ALE IDOC – To integrate as Vendor (IDOC Type – CREMAS) and Customer (IDOC Type – DEBMAS)
DRF – To integrate as Business Partner (CVI mandatory)
However, the IDocs DEBMAS and CREMAS are not recommended for data integration between S/4HANA
systems. In S/4HANA, Business Partner is the leading object. Therefore, you can use Business Partner web
services (SOAP) for SAP S/4HANA integration. This is published in the SAP Note 2417298 (attached below).
BP_DRF_2417298
Benifits of DRF
• If you want to connect multiple SAP ERP or SAP S/4HANA systems with a
decentralized EWM in S/4HANA with not harmonized business partners, you
must use the DRF for the business partner distribution. You cannot achieve the
mapping of overlapping business partner numbers with ALE distribution.
• For the material master you must ensure that your materials have different
material numbers in the relevant ERP systems. There is currently no option to
have a material number mapping between the different systems using ALE.
• For your business partners (vendors, carriers, and customers) you can use the
UKMS key mapping services provided by the Data Replication Framework (DRF) to
activate a mapping of business partner numbers between the different systems.
• If you use ALE/IDocs for your business partner distribution you must ensure that
your business partners have different business partner numbers in the
corresponding ERP systems.
Connection options of DRF
There are two options to establish a connection between two systems to
communicate with each other via Web Services.
• Communication messages can be sent and received via intermediate XI server
• Direct point-to-point communication between the systems.
Here we describe the usage of a point to point communication.
DRF System Activities
1) Activate FM MDG_BS_BP_OUTBOUND_DRF (T.Code – BUPA_CALL_FU)
2) Configuration of Replication Model (T.Code – DRFIMG)
3) Define Filter Criteria (T.Code – DRFF)
4) Integration of BP Master data (T.Code – DRFOUT)
5) Monitoring of outbound and inbound message (T.Code – SRT_MONI)
Note: Activity 1 is required for system to replicate change message when a
business partner is change in SAP S/4 HANA system.
DRF Log Analysis
• Transaction code – DRFLOG can be used to analyzis the detailed log
for replication performed via DRFOUT.
• It help us to display the list of data‘s selected for replication based on
filter criteria
• It also allows to repeat the replication.
CIF vs DRF
S.No Criteria CIF DRF
1 Interface QRFC Interface Web Service Interface
2 Business Support all the master data objects Currently support only Business Partner
Objects relevant for EWM
3 System Integration Model Replication Model
Connection
4 Filter Maintained within Integration model Maintained seperately against Replication
during generation model
5 Transfer Data transfer is 2 step activity (Generate – Data transfer is 1 step activity (Replicate -
CFM1 and Activate – CFM2) DRFOUT)
6 Monitor Queue Monitor (SMQ1 & SMQ2) Message Monitor (SRT_MONI)
7 Log Log Analysis in Application Log SLG1 Log Analysis for Outbound Impl. in DRFLOG
