SAP MDG · DATA MODEL UI
How do I configure SAP MDG Material replication with the Data Replication Framework (DRF)?
SAP MDG Material replication with DRF requires activating application MDGM, using the Material outbound implementation I_MAT or I_MAT_V2 as needed, and maintaining DRF/customizing plus change-pointer and ALE settings. The guide also covers DRFOUT execution, reduced IDoc limitations, deletion handling, key mapping with ALE Audit, and filter setup.
SAP MDG Material replication with DRF requires activating application MDGM, using the Material outbound implementation I_MAT or I_MAT_V2 as needed, and maintaining DRF/customizing plus change-pointer and ALE settings. The guide also covers DRFOUT execution, reduced IDoc limitations, deletion handling, key mapping with ALE Audit, and filter setup.
SAP MDG Material replication with DRF is based on activating application MDGM in the Material customizing, then using the correct outbound implementation and replication model. The standard Material DRF setup supports MATMAS and CLFMAS through I_MAT, while I_MAT_V2 extends support to MATQM, ECMREV, and DOLMAS. DRFOUT can be run manually or in a background job, and change-pointer tables such as MDGD_CP and MDGD_CP_REP_STAT help you verify whether replication was created and processed.
Process flow
- Activate application MDGM in MDGIMG -> Central Governance for Material -> Activate Business Transaction Events.
- Maintain the outbound implementation: use I_MAT for standard MATMAS/CLFMAS or I_MAT_V2 for MATQM, ECMREV, and DOLMAS.
- If ECMREV is required, activate ALE change pointers in BD50.
- Run DRFOUT to trigger replication, or schedule it in a background job using a variant.
- Check TBE11 and TBE31 to confirm DRF change-pointer setup for MDGM.
- Verify generated pointers in MDGD_CP and MDGD_CP_REP_STAT using SE16N; status should be CR.
- If deletions must be sent, use BD21 for standard ALE or implement IDOC_DATA_MAPPER to set MSGFN = 003 in the target system.
- For key mapping, maintain the MDG/ALE Audit setup so the hub can update mapping after target assignment.
MDGIMGCentral Governance for Material -> Activate Business Transaction Events
Activate application MDGM for Material DRF processing.
BD50SALE -> IDoc Interface / Application Link Enabling (ALE) -> Modeling and Implementing Business Processes -> Master Data Distribution -> Activate Change Pointers for Message Types
Activate ALE change pointers required for ECMREV replication.
Use a variant of DRFOUT for scheduled/background execution
Run Material replication manually or in batch.
SE16NInspect MDGD_CP and MDGD_CP_REP_STAT
Verify change-pointer creation and replication status.
Referenced tables
| Object | Purpose |
|---|---|
TBE11 | Application activation; MDGM must be active. |
TBE31 | BTE function registration for DRF change-pointer generation. |
MDGD_CP | Stores DRF change pointers. |
MDGD_CP_REP_STAT | Stores DRF change-pointer replication status. |
ILLUSTRATIVE ABAP SAMPLE
Source ABAP example: Extend_MDG_M_New_Reuse_Entity_Type.abap
Exact relevant implementation excerpt from the knowledge document set.
1*---------------------------------------------------------------------*
2* <SOURCE_DOCUMENT>
3* Extend MDG-M by a New Reuse Entity Type
4* Version 9.1 - July 2026
5* </SOURCE_DOCUMENT>
6*---------------------------------------------------------------------*
7
8*---------------------------------------------------------------------*
9* <BADI_IMPLEMENTATION>
10* <INTERFACE>IF_MDG_BS_MAT_API_SEGMENTS_EXT</INTERFACE>
11* <METHOD>READ</METHOD>
12*---------------------------------------------------------------------*
13METHOD if_mdg_bs_mat_api_segments_ext~read.
14 DATA: lt_mdgm_bupa TYPE ymdgm_bupa01_t.
15
16 CLEAR: et_data, et_message.
17
18 SELECT *
19 FROM ymdgm_bupa00
20 INTO CORRESPONDING FIELDS OF TABLE lt_mdgm_bupa
21 WHERE matnr IN is_selection-matnr_range
22 AND bupa_id IN is_selection-bupa_id_range.
23
24 INSERT LINES OF lt_mdgm_bupa INTO TABLE et_data.
25ENDMETHOD.
26* </BADI_IMPLEMENTATION>
27
28*---------------------------------------------------------------------*
29* <BADI_IMPLEMENTATION>
30* <INTERFACE>IF_MDG_BS_MAT_API_SEGMENTS_EXT</INTERFACE>
31* <METHOD>CHECK_AND_SAVE</METHOD>
32*---------------------------------------------------------------------*
33METHOD if_mdg_bs_mat_api_segments_ext~check_and_save.
34
35 DATA: ls_data TYPE ymdgm_bupa01_s.
36 DATA: ls_data_x TYPE ymdgm_bupa01_s_x.
37 DATA: ls_message TYPE mdg_bs_mat_s_mat_msg.
38 DATA: lt_modify TYPE STANDARD TABLE OF ymdgm_bupa00.
39 DATA: ls_modify TYPE ymdgm_bupa00.
40 DATA: lt_delete TYPE STANDARD TABLE OF ymdgm_bupa00.
41 DATA: ls_delete TYPE ymdgm_bupa00.
42
43 CLEAR et_message.
44
45 " First some checks
46 LOOP AT is_data-ymdgm_bupa00_tab INTO ls_data.
47 " All fields must be filled, otherwise
48 " MESSAGE e000(00) WITH ls_data-matnr
49 " ls_data-bupa_id
50 " ls_data-nickname.
51 IF ls_data-matnr IS INITIAL
52 OR ls_data-bupa_id IS INITIAL
53 OR ls_data-nickname IS INITIAL.
54
55 ls_message-msgid = '00'.
56 ls_message-msgno = '000'.
57 ls_message-msgty = 'E'.
58
59 ls_message-msgv1 = 'Empty value detected in:'.
60 ls_message-msgv2 = ls_data-matnr.
61 ls_message-msgv3 = ls_data-bupa_id.
62 ls_message-msgv4 = ls_data-nickname.
63
64 INSERT ls_message INTO TABLE et_message.
65 ENDIF.
66
67 " BuPa must exist
68 " ...
69 ENDLOOP.
70
71 " In test mode, we're finished now
72 CHECK iv_test_mode = abap_false.
73
74 " Determine which records to delete or to insert/update
75 LOOP AT is_data-ymdgm_bupa00_x_tab INTO ls_data_x.
76 IF ls_data_x-delete_row = abap_true.
77 " Keep key fields for deletion
78 ls_delete-matnr = ls_data_x-matnr.
79 ls_delete-bupa_id = ls_data_x-bupa_id.
80 INSERT ls_delete INTO TABLE lt_delete.
81 ELSE.
82 READ TABLE is_data-ymdgm_bupa00_tab INTO ls_data
83 WITH TABLE KEY matnr =
84* <SOURCE_TRUNCATED_AT_THIS_POINT />The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What is the Data Replication Framework in SAP MDG Material?
- How can Material master changes be replicated from an MDG hub?
- Which replication mechanisms are supported by DRF?
Possible questions
- How do I activate DRF for SAP MDG Material?
- Which application indicator must be active for MDG Material DRF?
- What are outbound implementations 194_2 and 194_3?
- Which message types are supported by I_MAT?
- How do I schedule DRFOUT in a background job?
- How are DRF Material change pointers generated?
- What is the recommended approach for Material key mapping?
- Does DRF Material support segment deletion?