Set Up Parallel Change Requests for Material
With MDG 7.0 and with SAP S/4HANA 1511, MDG also supports the creation of more than one Change Request in parallel for a single Business Object. This enables you to activate or reject a change request independently from the processing results of other change requests for the same business object. Download the DocumentPUBLIC
How-To: Set Up Parallel Change Requests for
Material
Applicable Releases:
From MDG 7.0 and from SAP S/4HANA 1511
Version 4.0
October 2023
How-To: Set Up Parallel Change Requests for
Material
Applicable Releases:
From MDG 7.0 and from SAP S/4HANA 1511
Version 4.0
October 2023
Document History
Document
Version Description
1.0 First official release of this guide
2.0 Validity update
3.0 Small update (March 2020)
4.0 Layout update (October 2023)
Document
Version Description
1.0 First official release of this guide
2.0 Validity update
3.0 Small update (March 2020)
4.0 Layout update (October 2023)
3 / 17
© 2023 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to SAP Materials for general audiences.
1 BUSINESS SCENARIO.................................................................................................4
2 BACKGROUND INFORMATION ..................................................................................5
2.1 Scope of Change Request ................................................................................................................... 5
2.2 Locking Logic ....................................................................................................................................... 5
2.3 UI Configuration .................................................................................................................................... 7
2.4 Display Logic ........................................................................................................................................ 8
2.5 Activation Logic .................................................................................................................................... 8
3 STEP BY STEP EXPLANATION FOR PARALLEL CHANGES ...................................9
3.1 Create new Change Request Type for parallel Changes of Basic Data .......................................... 9
3.1.1 Interlocking ...................................................................................................................................... 9
3.2 Create new Change Request Types for parallel Changes of Plants ............................................. 10
3.3 Create new Change Request Types for parallel Changes of Distribution Chain ......................... 11
3.4 Process ................................................................................................................................................ 12
3.4.1 Pending Change Request Pop-Up ................................................................................................ 12
3.4.1.1 Force Pending Change Request Pop-Up ...................................................................................... 13
3.4.1.2 Additional fields in the Pop-Up ...................................................................................................... 13
3.4.1.3 New Window to display Pending Change Request ....................................................................... 14
3.4.2 Button ‘Switch to Active Version’/’Switch to Inactive Version’ ....................................................... 14
4 ADDITIONAL INFORMATION .................................................................................... 15
4.1 Further Reading .................................................................................................................................. 15
4.1.1 Information on SAP MDG on SAP S/4HANA ................................................................................ 15
4.1.2 SAP Roadmap Explorer ................................................................................................................ 15
4.1.3 Related Information ....................................................................................................................... 15
4.2 SAP Notes............................................................................................................................................ 15
© 2023 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to SAP Materials for general audiences.
1 BUSINESS SCENARIO.................................................................................................4
2 BACKGROUND INFORMATION ..................................................................................5
2.1 Scope of Change Request ................................................................................................................... 5
2.2 Locking Logic ....................................................................................................................................... 5
2.3 UI Configuration .................................................................................................................................... 7
2.4 Display Logic ........................................................................................................................................ 8
2.5 Activation Logic .................................................................................................................................... 8
3 STEP BY STEP EXPLANATION FOR PARALLEL CHANGES ...................................9
3.1 Create new Change Request Type for parallel Changes of Basic Data .......................................... 9
3.1.1 Interlocking ...................................................................................................................................... 9
3.2 Create new Change Request Types for parallel Changes of Plants ............................................. 10
3.3 Create new Change Request Types for parallel Changes of Distribution Chain ......................... 11
3.4 Process ................................................................................................................................................ 12
3.4.1 Pending Change Request Pop-Up ................................................................................................ 12
3.4.1.1 Force Pending Change Request Pop-Up ...................................................................................... 13
3.4.1.2 Additional fields in the Pop-Up ...................................................................................................... 13
3.4.1.3 New Window to display Pending Change Request ....................................................................... 14
3.4.2 Button ‘Switch to Active Version’/’Switch to Inactive Version’ ....................................................... 14
4 ADDITIONAL INFORMATION .................................................................................... 15
4.1 Further Reading .................................................................................................................................. 15
4.1.1 Information on SAP MDG on SAP S/4HANA ................................................................................ 15
4.1.2 SAP Roadmap Explorer ................................................................................................................ 15
4.1.3 Related Information ....................................................................................................................... 15
4.2 SAP Notes............................................................................................................................................ 15
4 / 17
© 2023 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to SAP Materials for general audiences.
1 Business Scenario
SAP Master Data Governance (MDG) provides business processes to find, create, change, and mark master
data for deletion. It supports the governance of master data in a central hub and the distribution to connected
operational and business intelligence systems.
The processes are workflow-driven and can include several approval and revision phases, and the
collaboration of all users participating in the master data maintenance.
MDG offers change request (CR)-based processing of master data with integrated workflow, staging,
approval, activation, and distribution.
As of MDG 7.0 and SAP S/4HANA 1511, MDG also supports the creation of more than one Change Request
in parallel for a single Business Object. This enables you to activate or reject a change request
independently from the processing results of other change requests for the same business object.
This guide gives some background information and explanation for setting up Parallel Change Requests for
the Business Object Material.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to SAP Materials for general audiences.
1 Business Scenario
SAP Master Data Governance (MDG) provides business processes to find, create, change, and mark master
data for deletion. It supports the governance of master data in a central hub and the distribution to connected
operational and business intelligence systems.
The processes are workflow-driven and can include several approval and revision phases, and the
collaboration of all users participating in the master data maintenance.
MDG offers change request (CR)-based processing of master data with integrated workflow, staging,
approval, activation, and distribution.
As of MDG 7.0 and SAP S/4HANA 1511, MDG also supports the creation of more than one Change Request
in parallel for a single Business Object. This enables you to activate or reject a change request
independently from the processing results of other change requests for the same business object.
This guide gives some background information and explanation for setting up Parallel Change Requests for
the Business Object Material.
5 / 17
© 2023 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to SAP Materials for general audiences.
2 Background Information
You can only use parallel change requests for the change material process. You cannot use them to create
materials in parallel. Note that creation of a plant/distribution chain/storage location assignment is considered
as change in MDG and not as creation like it is in the back end.
2.1 Scope of Change Request
What you can change with a parallel change request is determined by the change request type. Parallel
change requests are created on entity-level; you must choose the entities to be included in your change
request. You can only maintain fields related to entities in the change request scope. Other fields are read
only.
To create a meaningful scope, you must ensure that you can maintain all mandatory fields required.
Otherwise, you will not be able to activate the change request.
To ensure basic consistency of the change request type in terms of the implemented derivations, restrictions
concerning the maintenance are checked. For the MM data model, the following logic applies:
Selected Entity Additional Required Entity
MATERIAL UNITOFMSR, MEAN_GTIN
UNITOFMSR MATERIAL, MEAN_GTIN
MEAN_GTIN MATERIAL, UNITOFMSR
MVKEGRPNG MLANSALES
MVKESALES MLANSALES
MARCBASIC MLANPURCH
There are additional points you must consider:
• If you want to create a new Distribution Chain, the Entities MVKEGRPNG, MVKESALES and
MLANSALES must be in scope.
• If you want to create a new Plant Assignment, MARCBASIC and all MARC*Entities which have
Required Fields (from T130F, Model, BAdI, BRF+ Checks...) must be in scope.
• If you have Cross Entity Derivations, all relevant Entities must be in scope.
• Some hardcoded derivations that run in the back end (SAP Standard) default values (for example:
Procurement type MARC-BESKZ), which are on different entities. Create a BRF+ Rule to derive the
default values and make sure that the related Entity is in scope.
• See restriction SAP Note 1806108, 2129261 and 2284745 - Functional restrictions in MDG-M. Some
hardcoded rules that run in the back end (SAP Standard) require value in fields that belong to
different entities. All relevant Entities must be in scope.
• If you use T130F customizing for Required Fields, all relevant Entities must be in scope. For example,
field Material Group MARA-MATKL is required if you create a new plant assignment. Entities
MARCBASIC and MATERIAL must be in scope.
• It is also possible to have Change Request Types with Business Activity MATA with PCR. Please
keep in mind that you also need a scope for this Change Request Type where you should reduce
the entities. But you could also create a new material with this Change Request Type and this will
only work if you have all necessary basic data entities in scope.
2.2 Locking Logic
Non-parallel change requests, such as those created by MAT01, completely lock the chosen material.
Likewise, to create a non-parallel change request the entire material record must be unlocked.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to SAP Materials for general audiences.
2 Background Information
You can only use parallel change requests for the change material process. You cannot use them to create
materials in parallel. Note that creation of a plant/distribution chain/storage location assignment is considered
as change in MDG and not as creation like it is in the back end.
2.1 Scope of Change Request
What you can change with a parallel change request is determined by the change request type. Parallel
change requests are created on entity-level; you must choose the entities to be included in your change
request. You can only maintain fields related to entities in the change request scope. Other fields are read
only.
To create a meaningful scope, you must ensure that you can maintain all mandatory fields required.
Otherwise, you will not be able to activate the change request.
To ensure basic consistency of the change request type in terms of the implemented derivations, restrictions
concerning the maintenance are checked. For the MM data model, the following logic applies:
Selected Entity Additional Required Entity
MATERIAL UNITOFMSR, MEAN_GTIN
UNITOFMSR MATERIAL, MEAN_GTIN
MEAN_GTIN MATERIAL, UNITOFMSR
MVKEGRPNG MLANSALES
MVKESALES MLANSALES
MARCBASIC MLANPURCH
There are additional points you must consider:
• If you want to create a new Distribution Chain, the Entities MVKEGRPNG, MVKESALES and
MLANSALES must be in scope.
• If you want to create a new Plant Assignment, MARCBASIC and all MARC*Entities which have
Required Fields (from T130F, Model, BAdI, BRF+ Checks...) must be in scope.
• If you have Cross Entity Derivations, all relevant Entities must be in scope.
• Some hardcoded derivations that run in the back end (SAP Standard) default values (for example:
Procurement type MARC-BESKZ), which are on different entities. Create a BRF+ Rule to derive the
default values and make sure that the related Entity is in scope.
• See restriction SAP Note 1806108, 2129261 and 2284745 - Functional restrictions in MDG-M. Some
hardcoded rules that run in the back end (SAP Standard) require value in fields that belong to
different entities. All relevant Entities must be in scope.
• If you use T130F customizing for Required Fields, all relevant Entities must be in scope. For example,
field Material Group MARA-MATKL is required if you create a new plant assignment. Entities
MARCBASIC and MATERIAL must be in scope.
• It is also possible to have Change Request Types with Business Activity MATA with PCR. Please
keep in mind that you also need a scope for this Change Request Type where you should reduce
the entities. But you could also create a new material with this Change Request Type and this will
only work if you have all necessary basic data entities in scope.
2.2 Locking Logic
Non-parallel change requests, such as those created by MAT01, completely lock the chosen material.
Likewise, to create a non-parallel change request the entire material record must be unlocked.