Configuring Master Data Governance for Material
To use SAP Master Data Governance (MDG) for material, you need to carry out the steps described below.
Business Function
You have activated the following business functions:
Master Data Governance, Generic Functions (MDG_FOUNDATION
)
Master Data Governance, Generic Functions 2 (MDG_FOUNDATION_2
)
Master Data Governance, Generic Functions 3 (MDG_FOUNDATION_3
)
Master Data Governance, Generic Functions 7.0 (MDG_FOUNDATION_4
)
Master Data Governance, Generic Functions 7.0 Feature Pack (MDG_FOUNDATION_5
)
Note
This business function is available with support package 02 and higher of MDG 7.0.
Master Data Governance for Material (MDG_MATERIAL
)
Master Data Governance for Material 2 (MDG_MATERIAL_2
)
Master Data Governance for Material 3 (MDG_MATERIAL_3
)
Master Data Governance for Material 7.0 (MDG_MATERIAL_4
)
Master Data Governance for Material 7.0 Feature Pack (MDG_MATERIAL_5
)
Note
This business function is available with support package 02 and higher of MDG 7.0.
Note
Before you activate the business functions, ensure that you have the administration authorization for MDG. The required authorization objects are delivered with the authorization role SAP_MDG_ADMIN
. In transaction PFCG
, we recommend creating a copy of this role and assigning the relevant authorization values. For the authorization object USMD_DM
Data Model
you need to assign the values for the authorization field USMD_MODEL
Data Model
(for example MM
, BP
, or 0G
) and the values for the authorization activity ACTVT
Activity
(for example 01: Create or generate, or 02: Change).
If you want to use Enterprise Services to load data into the active or staging area of the hub, activate the business function ERP_MATERIAL_SOA
. For additional BCV Content activate business function /BCV/NWBC_SIDEPANEL
. If you want to use the MDG for Material homepage or the Business Context Viewer, activate the business functions /BCV/MAIN
and /BCV/MAIN_1
. For more information on the Business Context Viewer see, Business Context Viewer in Single Processing.
When you activate the MDG_Material
business function the system activates the Material (MM
) data model. Before continuing with system configuration, open transaction SFW5
and check if the activation has been completed by choosing Switch Framework Logs
from the Goto
menu and selecting the corresponding entry.
Set Up Workflow
To use the rule-based workflow processes of MDG for material, you have defined general settings for SAP Business Workflow in Customizing for SAP NetWeaver under . Remember to regenerate the authorization profile of SAP_ALL
or include USMD*
authorization objects into the authorization for the user WF-Batch.
To activate the workflow features, use the semi-automated configuration in transaction SWU3
. You can also access these settings in Customizing under
For further information see the documentation for the Configuration activity. Note the following when maintaining the settings:
When configuring the RFC destination you need superuser authorization to create the default WF-BATCH user.
Regenerate the authorization profile for SAP_ALL
or include the USMD*
authorization objects into the authorizations of the user WF-Batch.
For the Check Entries from HR Control Tables
section you may need to execute report RHSOBJCH
in transaction SE38
and keep the default settings.
Maintain the prefix numbers for the standard objects.
You do not need to maintain the Web Server node and Guided Procedures section.
Set Up Search
You must have installed and connected Enterprise Search either in embedded form or as central search engine service in order to use master data governance for material. If you don’t need to search for classifications you can replace the Enterprise Search with the standard database search or another search provider.
Adjust Profile Parameters
Ensure that the profile parameter size for the Shared Objects Memory
is the correct. To check this setting run transaction RZ11
and verify that the value for parameter abap/shared_objects_size_MB
is between 200 and 300 megabytes.
If you want to use the SAP NetWeaver Business Client
with single sign on, ensure that the parameters login/create_sso2_ticket
and login/accept_sso2_ticket
are set correctly.
Use transaction RZ11 to check that the host name is fully qualified for parameter icm/host_name_full
.
User Roles
In order to successfully conduct the next steps in the configuration process, you must have the following user roles assigned in the PFCG
transaction:
SAP_BC_TREX_ADMIN
SAP_ESH_LOCAL_ADMIN
SAP_MDGA_MENU
– Master Data Governance: Analytics
SAP_MDG_ADMIN
– Master Data Governance: Administrator
This role contains authorizations for basic tasks relevant to the configuration and administration of SAP Master Data Governance (MDG) for all domains. Some authorizations allow critical activities. If you have multiple users involved in the configuration and administration of MDG content, we recommend you split this role into several new roles and give each new role a subset of the authorizations for this role. Such an approach ensures users only complete tasks they are responsible for and reduces the risk of critical errors. Authorizations for the MDG transactions are not included in this role.
SAP_MDGM_MENU_04
– Master Data Governance for Material: Menu
SAP_MDGM_DISP_04
– Master Data Governance for Material: Display
SAP_MDGM_REQ_04
– Master Data Governance for Material: Requester
SAP_MDGM_SPEC_04
– Master Data Governance for Material: Specialist
SAP_MDGM_STEW_04
– Master Data Governance for Material: Data Steward
SAP_MDGM_MENU_05
– Master Data Governance for Material: Menu
SAP_MDGM_DISP_05
– Master Data Governance for Material: Display
SAP_MDGM_REQ_05
– Master Data Governance for Material: Requester
SAP_MDGM_SPEC_05
– Master Data Governance for Material: Specialist
SAP_MDGM_STEW_05
– Master Data Governance for Material: Data Steward
Note
The previous five roles are available with support package 02 and higher of MDG 7.0.
In addition, the authorization object PLM_SPUSR
is needed if the Search Object Connector
for enterprise search is created for the Enterprise Search Software Component PLMWUI
or any Enterprise Search Software Component that includes PLMWUI
. The role SAP_PAGEBUILDER_DISPLAY
is required to use the Page Builder
tool for accessing homepages created using Page Builder
.
Web Dynpro Applications
For security reasons the services delivered for Web Dynpro applications are delivered in an inactive state. You must activate the services you want to use. Use transaction SICF
to activate the services. For a detailed list of the relevant services, see Services to be Activated for Web Dynpro Applications.
This process describes the minimal set of customizing steps and recommended check activities required to do the following:
Create materials
Change materials
Mark materials for deletion
Process multiple materials
Multiple-record processing
You run the settings for this process in Customizing under .
The system is configured for MDG for material. In addition, if data load has been done, mass changes and distribution to other systems can also be executed.
For information on functional restrictions, see SAP Note 1701437
.
Some Material Master customizing activities are relevant for Master Data Governance for Material:
Under the Configuring the Material Master
node, the activity Define How Maintenance Statuses Are Determined in Data Transfer
impacts Master Data Governance for Material.
Under the Field Selection
node, all activities that change the field properties affect the field properties in Master Data Governance for Material. The field properties hidden, displayed, mandatory, and optional impact the Master Data Governance for Material fields.
Under the Basic Settings
node, all activities impact Master Data Governance for Material. Example settings include the output format of the material number and the material types.
Under the Settings for Key Fields
node, all activities impact Master Data Governance for Material. Example settings include the definition of material groups, and the settings for EANs.
Under the Data Transfer: Material Master
node, the activity Define Required-Field Check for ALE/Direct Input
impacts Master Data Governance for Material. There you define how the material master for industry is updated if required fields not belonging to the core maintenance status lack entries.
If you operate a MDG hub, and if you make changes to fields under governance in the material master using a backend transaction ERP, these changes will be overwritten by the next change request created for that material. To prevent this, SAP recommends that you set fields under governance to ready-only in your non-hub systems. The recommended approach for this process in SAP systems is to define new material master backend data screens and screen sequences in the configuration activity Configuring the Material Master
.