How To... Master Data Governance For Material: Set Up Parallel Change Requests For Material
How To... Master Data Governance For Material: Set Up Parallel Change Requests For Material
How To... Master Data Governance For Material: Set Up Parallel Change Requests For Material
Applicable Releases:
MDG 7
Version 1
November 2013
Document History
3
1. BUSINESS SCENARIO
SAP Master Data Governance for Material (MDG-M) provides business processes to find, create, change, and mark
material master data for deletion. It supports the governance of material master data on a central hub and the
distribution of material master data to connected operational and business intelligence systems.
The processes are workflow-driven and can include several approval and revision phases, including collaboration
between all users participating in master data maintenance.
With MDG 7.0 SAP 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.
4
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 backend.
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 following logic applies:
5
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.
For materials in parallel change requests, locking happens on entity level, that is, on the object level of the entity type.
In the background an object list is maintained for this. For example, if Plant ATP Data is maintained for plant 0001 in
the first parallel change request, then in a second change request the Plant ATP Data is locked for plant 0001, but not
for plant 0002. Examples of objects on entity level are plants, storage locations, sales organizations, distribution
channels, warehouses, and storage types.
Note:
You cannot have two change requests accessing the same material in Edit mode at the same time. When going to edit
mode the complete material is locked for changes for all other change requests. Only after ending the edit mode, for
example by saving, can other processors process their parallel change request for the scope as described above.
If the delivered data model MM does not reflect the field groups which you would like to maintain and lock together you
can adapt the model.
Use case:
Fields PRODH and SPART are on entity MATERIAL. But you would like to maintain and lock them together with the
other sales data on MARASALES.
Solution:
Set fields PRODH and SPART on MATERIAL out of Governance Scope. You can do this in Customizing for MDG
under Master Data Governance->General Settings->Process Modeling-> Define Governance Scope.
Create new attributes on MARASALES. You can do this in Customizing for MDG under Master Data Governance-
>General Settings->Data Modeling-> Edit Data Model.
6
Extend the SMT Mapping for MDG_BS_MAT_MAP_2STA and MDG_BS_MAT_MAP_2PP. You can do this in
Customizing for MDG under Master Data Governance->General Settings->Data Modeling-> Extend Mappings->Extend
Mappings.
2.3. UI Configuration
Change Request Types that run in parallel should lead to the same OVP configuration. With CBA (context based
adaptation) for the different Change Request Types you can hide the UIBBs that are not to be shown. Then it is
possible to toggle between the Active and Inactive versions (see chapter 3.4.2 Button Switch to Active Version/Switch
to Inactive Version)
If you have different OVP configuration and assign this in Customizing (Master Data Governance->General Settings-
>Process Modeling->Change Requests->Configure Properties of Change Request Step: User Interface per Change
Request Step) to the Change Request Types you will have these limitations:
Step dependent UIs are not used from My Change Request (only one configuration is possible)
7
Step dependent UIs are not used from search with display and then switch to edit (only one configuration is
possible)
Step dependent UIs work from Worklist and if you enter a change request type in the initial screen.
Note:
If data is changed directly in the active area, these changes are not reflected in the open Change Requests when a
Change Request is opened again. But you will see a staging icon on organization level. This happens because of the
determination is based on comparison of active area and staging. Activation is then only possible if you ignore the
snapshot differences during activation with process pattern 06 in the Non-User Agent Decision Table of the Rule Based
Workflow.
The same behavior occurs if during activation of a Change Request the backend code (Function Module
MATERIAL_MAINTAIN_DARK) derives additional default values. Then also a difference between active area and
staging is indicated. To avoid this indication you have to anticipate the backend derivations by BRF+ Derivation Rules
or the Derive BAdI in the MDG process before activation.
8
3. STEP BY STEP EXPLANATION FOR PARALLEL CHANGES
With this Step by Step Explanation you will be able to support the following example scenario:
Master data users can request changes to the Basic Data of a Material in parallel to create/change unit of measure, to
create/change data of a plant, and to create/change a new Distribution Chain.
The related change requests can be processed, activated, and rejected independently of each other.
3.1. Create new Change Request Type for parallel Changes of Basic Data
You can configure these change request types in the Customizing activity Create Change Request Type under Master
Data Governance->General Settings->Process Modeling->Change Requests.
Copy Change Request Type MAT02 and mark it as Parallel Change Request.
Maintain the scope. Select all Entity Types you would like to change with this Change Request Type.
If entity MATERIAL, UNITOFMSR, or MEAN_GTIN is in scope, all 3 of them must be in scope because of standard
derivations (like dimension data for the base unit of measure) between the entities.
3.1.1.Interlocking
With the scope of the change request type you define the entities that can be changed. But they are not locked in the
CR until you change data in the entity.
Therefore it can happen that you create a change request with EM_01_01 and later in the process you want to change
the Width and Height for the base unit in dimension UIBB (entity UNITOFMSR). But the standard derives to the entity
MATERIAL could not be carried out because the MATERIAL entity is interlocked in a different Change Request. You
9
will get the following message:
You can activate your change request but the other Change Request will overwrite the values. To avoid this behavior
you can create a BRF+ Check Rule which allows changes only if the derivation was successful to the other entities (for
example: Check if values for the dimension in UNITOFMSR are the same as for MATERIAL. If not raise an Error
Message, and you are not able to save the Change Request)
3.2. Create new Change Request Types for parallel Changes of Plants
You can configure these change request types in the Customizing activity Create Change Request Type under Master
Data Governance->General Settings->Process Modeling->Change Requests.
Copy Change Request Type MAT02 and mark it as Parallel Change Request.
Maintain the scope. Select all Entity Types you would like to change with this Change Request Type.
10
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.
3.3. Create new Change Request Types for parallel Changes of Distribution Chain
You can configure these change request types in the Customizing activity Create Change Request Type under Master
Data Governance->General Settings->Process Modeling->Change Requests.
Copy Change Request Type MAT02 and mark it as a Parallel Change Request.
Maintain the scope. Select all Entity Types you would like to change with this Change Request Type.
11
3.4. Process
Create first Change Request with Change Request Type EM_01_01.
You are only able to change Basic Data. All other data is read only and you see the values from the active area.
The change requests can be processed, activated, and rejected independently of each other.
The pop up also appears if you choose the Pending Change Request button in a Change Request for a material which
has other Change Requests.
12
3.4.1.1. Force Pop up Pending Change Request
The Appearance of the Pop ups can be controlled with an Overwrite-Exit in class CL_MDG_BS_MAT_APPCC
If you want to display the Pending Change Request popup always if at least one CR exists, you have to create an
Overwrite Exit of method CL_MDG_BS_MAT_APPCC->SKIP_CR_WI_POPUP.
13
Back:
14
www.sap.com
Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are
registered trademarks of Crossgate AG in Germany and other
countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of
their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.