Data Replication Framework (DRF)

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:

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. BTE (Business Transaction Events) reacts less robustly in the event of errors. IDocs (ALE) is the more advantageous alternative here.

However, if EWM runs decentrally on an S/4HANA platform, the connection can be made in both ways. Both via the familiar ALE interface, i.e. using IDocs, and via the DRF (Data Replication Framework). This is part of the MDG (Master Data Governance) business function that needs to be activated. We expressly advocate the use of the DRF here. It immediately covers the conversion of master data – for example between material and warehouse product, between customer and business partner or also for the purpose of mapping overlapping nomenclatures of different authorized parties.
Translated with DeepL.com (free version) 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).