SAP MDG · DATA MODEL UI
How do I set up Parallel Change Requests for Material in SAP MDG?
Parallel Change Requests for Material let multiple change requests for the same material be processed independently in SAP MDG, but only for the change process, not for parallel creation. Setup is done by copying MAT02, marking the new request type as Parallel Change Request, and defining the entity scope carefully so mandatory and cross-dependent entities stay consistent.
Parallel Change Requests for Material let multiple change requests for the same material be processed independently in SAP MDG, but only for the change process, not for parallel creation. Setup is done by copying MAT02, marking the new request type as Parallel Change Request, and defining the entity scope carefully so mandatory and cross-dependent entities stay consistent.
Parallel Change Requests for Material allow more than one change request to exist for the same material, with each request activated or rejected independently. The key setup is to copy MAT02, flag the request type as Parallel Change Request, and define the entity scope so mandatory and dependent entities remain consistent.
Process flow
- Copy MAT02 to a new change request type.
- Mark the new type as Parallel Change Request.
- Maintain the scope for the scenario.
- Include all mandatory and cross-entity-dependent entities.
- Check `MATERIAL` / `UNITOFMSR` / `MEAN_GTIN` together when one is included.
- For plant scenarios, include `MARCBASIC` plus relevant `MARC*` entities.
- For distribution chain scenarios, include `MVKEGRPNG`, `MVKESALES`, and `MLANSALES`.
- Keep the OVP configuration aligned across PCR types where possible.
Master Data Governance -> General Settings -> Process Modeling -> Change Requests -> Create Change Request Type
Copy `MAT02`, flag the new type as Parallel Change Request, and maintain the scope.
Master Data Governance -> General Settings -> Process Modeling -> Define Governance Scope
Adjust governance scope so fields and entities are editable in the intended PCR.
Master Data Governance -> General Settings -> Data Modeling -> Edit Data Model
Adapt data model entities and field placement if locking groups must change.
Master Data Governance -> General Settings -> Data Modeling -> Extend Mappings -> Extend Mappings
Extend SMT mappings when fields are moved between entities or modeled on new entities.
Referenced tables
| Object | Purpose |
|---|---|
MM Entity Dependencies | Lists the entity combinations that must be scoped together for PCR consistency and activation. |
Process Example CR Types | Shows the example PCR types `EM_01_01`, `EM_01_02`, and `EM_01_03` for independent processing. |
SAP Notes | Lists relevant MDG-M functional restriction and support notes referenced by the guide. |
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 are Parallel Change Requests in SAP MDG for Material?
- From which MDG and S/4HANA releases are PCRs supported?
- How is PCR scope defined?
Possible questions
- What are Parallel Change Requests in SAP MDG for Material?
- From which MDG and S/4HANA releases are PCRs supported?
- Can parallel change requests create new materials?
- How is PCR scope defined?
- Which entities must be included with MATERIAL?
- Which entities are needed for a new Plant Assignment?
- How can I force the Pending Change Request pop-up?