Data Replication Framework (DRF) for SAP EWM
The future-proof interface between EWM and ERP
While the transfer of transaction data between EWM and ERP is always done with the help of inbound and outbound deliveries via queued remote function calls (qRFCs), there are several options for transferring master data. Which ones are suitable for you depends on your system constellation; i.e. which EWM and which ERP you use. Here is an overview:
ERP |
EWM |
Alternativen |
| SAP ECC |
up to SAP EWM 9.5, decentralized | CIF (ALE, BTE) |
| SAP S/4HANA |
up to SAP EWM 9.5, decentralized | CIF (ALE, BTE) |
| SAP ECC | EWM on S/4HANA (from 1809), decentralized | ALE, DRF (services, ALE, Datei, RFC) |
| SAP S/4HANA | EWM on S/4HANA (from 1809), decentralized | ALE, DRF (services, ALE, Datei, RFC) |
| SAP S/4HANA | Embedded EWM on S/4HANA (from 1610) | master data replication not necessary |
If you run your decentralized EWM in the classic way on a SAP Netweaver or SCM server, there is no alternative to the CIF (Core Interface Framework) in the SAP standard even up to the latest version 9.5. In such a case, in our experience, IDocs (ALE) prove to be advantageous over BTE (Business Transaction Events), as the latter reacts less robustly in the event of errors.
On the other hand, if EWM runs decentrally on an S/4HANA platform, the connection can be made via the familiar ALE interface, i.e. using IDocs, and via the DRF (Data Replication Framework), which is part of the MDG (Master Data Governance) business function that needs to be activated. We expressly advocate the use of the DRF, because it covers the conversion of master data - for example between material and warehouse product, between customer and business partner, or for the purpose of mapping overlapping nomenclatures of different parties entitled to dispose. Within the DRF, different communication channels come into question, whereby in most cases IDocs will be the first choice. In this way, the already existing message types can be used. In the future, the DRF offers the advantage that you can switch to replication via services, file or RFC with just a few changes to the settings in the corresponding Implementation Guide (transaction DRFIMG).
If you have any questions about setting up your EWM interface, please do not hesitate to contact us!