Explaining Master Data Governance (MDG) Customizing and Setup

Objective

After completing this lesson, you will be able to understand MDG setup and customization

System Preparation and Verification

Business Functions

The figure shows the link and a screenshot of the Product Availability Matrix.

The SAP Product Availability Matrix (PAM) is the essential and central entry point to verify the compatibility of components for SAP Master Data Governance.

You can also find further details on the implementation and operations of Master Data Governance (MDG) applications.

The figure shows screenshots of the System Status and the Installed Software Components.

Check the compatibility of installations with the Product Availability Matrix (PAM) and the Release Info Notes (RIN) for the current application needs.

You can find the installed software versions in the SAP Menu, under System→Status. For product details, choose the button shown in the figure, System Verification: Installed MDG Components. The installation of those components is part of the SAP basis procedures.

System Compatibility Verification Support Launchpad

On the screenshot you can see the ONE Support Launchpad showing some notes.

The figure, System Compatibility Verification Support Launchpad, shows the SAP ONE Support Launchpad.

Release Information Notes for SAP Master Data Governance Releases:

  • SAP Master Data Governance 9.0 SP03: 2450293
  • SAP Master Data Governance 9.2 SP02: 2789942
  • SAP Master Data Governance on S/4HANA 2022: 3251553
  • SAP S/4HANA Master Data Governance 2023: 3346733

Note

In the SAP ONE Support Launchpad, the Release Info Notes (RIN) for each SAP Master Data Governance release are available as an SAP standard note: https://launchpad.support.sap.com

Adjust Profile Parameters

The screenshot shows the Display Profile Parameter Attributes screen for the Parameter abap/shared_objects_size_MB)

You can adjust profile parameters as follows:

  • Ensure that the profile parameter size for the shared objects memory is 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 SAP Business Client with single sign on, ensure that the parameters login/create_sso2_ticket = 1 and login/accept_sso2_ticket = 2 are set correctly.

  • Run transaction RZ11 to check that the host name is fully qualified for parameter icm/host_name_full.

Check additional prerequisites for MDG_FOUNDATION. To make further adjustments to the system parameter settings, you can access these settings in customizing, under Cross-Application Components→Processes and Tools for Enterprise Applications→Master Data Governance→General Settings→Technical Settings for Master Data→Profile Parameter Setting. You can also run system transaction RZ11.

Web Dynpro Applications

Note

Services must be activated in each system. There is no known way to transport them from DEV to Q/P-Systems.

SICF - Service Activation

The figure shows the screenshot of the services to be activated in a Master Data Governance system.

You could receive errors when a service is not active. If you do, you need to activate the service. This activity is reversible. It can also be used to temporarily deactivate an MDG application when needed, for instance, during migration loads.

Initial Basis Setup

The figure shows on the left side the client setting with the Currency, Client Role and Changes and Transports for Client-Specific Objects. On the right side screenshots with the SOA Management settings and the Import Queue.

Perform an initial basis setup as follows:

  • Specify the httpurlloc table entries, if needed, to enable transactions such as NWBC and SOAMANAGER. These are forwarded to the proper link from the MDG system.
  • To enable name resolution for the links https://mdgappserver/nwbc/~launch/?sap-client=100&sap-language=EN, set Dynamic Name Services Entries (DNS) on network level for the WEB-Link access to the MDG system.
  • In transaction SCC4, check the logical system name of the system. If necessary, adjust them to the target name.
  • Also, consider necessary activities planned for performing transaction BDLS to switch the logical name in the whole environment.
  • Also, open the MDG system in SCC4 to a mode that enables performance of necessary customizing activities. These cannot be transported (replication cutover).
  • Check and initiate, if necessary, the transport route from DEV→QAS→PRD.

Definition of File System Folders for Import

The figure shows in various screenshots the customizing setting for the definition of the file system structures.

File system access is necessary for performing initial loads based on files stored on the application server.

These settings are usually transported. However, in some cases, they must be verified because they must be accessed physically on the application server level.

Workflow Setup

On the screenshots you can see the entry point for the workflow configuration for SAP Master Data Governance.

In SAP Master Data Governance, a business workflow has to be set up.

You can define the general settings for workflows in transaction SWU3.

Most settings are done using Automatic Workflow Customizing.To configure an RFC destination, you need SUPER-user authorization to create the default SAP_WFRT user (formerly known as WF-BATCH user).

Note

2637240 - Error in SWU3 - System user 'SAP_WFRT' does not exist

Before an MDG system can be used, the basic workflow settings need to be performed. It is essential to have a green light on the first items of the runtime environment, but the lower items of this section should also be maintained and marked as completed.

To use the rule-based workflow processes of MDG, you must define general settings for workflows in customizing under: SAP Customizing Implementation Guide→Service→→Basic Functions→SAP Business Workflow→Maintain Standard Settings for SAP Business Workflow.

To activate general workflow features, use the semi-automated configuration feature of transaction SWU3. You can also access these settings in customizing, under SAP Customizing Implementation Guide→Service→→Basic Functions→SAP Business Workflow→Maintain Standard Settings for SAP Business Workflow.

In the wizard, you can see descriptions, details, and further instructions for all activities.

Note the following when maintaining the settings:

  • When configuring an RFC destination, you need superuser authorization to create the default SAPWFRT user.
  • Regenerate the authorization profile for SAP_ALL or include the USMD* authorization objects into the authorizations of the user SAP-WFRT.
  • 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 and Guided Procedures section.

For more information on using the business workflow, go to customizing in SAP NetWeaver, under Application Server→Business Management→SAP Business Workflow.

The screenshots explain the Master Data Governance Event Type Linkage Settings.

Maintain the linkage settings as follows:

  • Check the SPRO help:
    • BUS2240 = Consolidation + Mass

    • BUS2250 = Central Governance Change Request

  • Check the notes in the SAP implementation guide and specify the linkage settings accordingly to prevent workflow issues.
The screenshots explain the Master Data Governance workflow agent assignment settings

All tasks not defined as background tasks need to be attributed and set as General Task.

The assignment is essential to be able to provide steps or tasks into end users' inboxes. If this is not set correctly, the user will not receive the tasks.

It is recommended to also perform this for any workflows that are not used to prevent issues when workflows need to be used (for example, for migration purposes).

After the system upgrades, new steps or tasks may appear and the activity may be repeated for certain steps or workflows.

Transport of these settings is not recorded in all cases. Therefore, they must sometimes be performed as cutover in each system or each client.

The figure shows the screenshot to refresh the workflow buffer.

If there are updates in the workflow configuration, it may be necessary to perform a workflow buffer refresh with transaction SWU_OBUF.

The synchronization of runtime buffers for workflow is necessary to clean up buffers and prevent issues in the workflow engine.

This will usually be done once per day automatically and will be initiated once manually when the setup tasks took place.

Diverse Settings and Checks

The figure shows the screenshot of the queue reconciliation of HR tables.

Check the entries from the HR control tables. You will likely need to execute report RHSOBJCH using transaction SE38 and keep the default settings.

One activity of each MDG client installation should be to perform the reconciliation of HR tables to prevent issues with agent determination procedures.

The screenshot shows the transactional RFC verification using transaction code SM58.

Run transaction SM58 and verify whether there are issues in the system in general. If necessary, get in contact with the basis to clarify the issues here.

Another task of the cutover should be to check the status in the transactional RFC queue. This is usually empty or contains currently running tasks. If there are erroneous steps recorded here, verify and resolve the underlying issues (authorization, dumps, and so on).

The screenshot shows the number ranges settings for Master Data Governance objects like the Material number, Change Request, Temporary Address ID and others.

Run transaction SNRO to specify MDG-related number range settings.

Number range settings need to be defined for the domains or components used with the current MDG application. Review any warning messages that appear during the maintenance procedures related to transport approaches for number ranges. Transaction SNRO usually has to be used here, but specific transactions are also available.

The figure shows screenshots to define prefixes for internal number handling.

The temporary IDs that are in the staging area can either be created with an external or internal key.

For internal key assignment, MDG uses a temporary key, including a prefix, until the status with the mandatory key is reached. The internal keys from the standard number ranges are then used instead of this temporary ID.

You can set this up as follows:

  • Define the prefix here. For example, $ or §§.

  • Check (enhance) and activate the MM data model (for example), including temporary IDs for internal number handling.

  • Assign an internal key.

To support internal key assignment, run the activity in customizing for MDG, under Classic Mode in SAP MDG→General Settings→Data Modeling→Define Prefixes for Internal Key Assignment.

For example, if you create new entries with the following values, all temporary IDs are prefixed with $ and an internal sequence number.:

  • Data Model: MM
  • Entity Type: MATERIAL
  • Prefix: $

Note

For MDG for material, Authorizations cannot be defined here. Instead, the existing backend authorizations are reused.

For more information, see customizing under Logistics- General→Material Master→Tools→Maintain Authorizations and Authorization Profiles.

Data Model Authorization Relevance

The screenshots show the data model authorization relevance. In detail you can see an example of the authorization for entity type account.

There are also options to specify data model sections (entities and attributes) as relevant for authorization checks.

For MDG domains using flex modes, this is usually an essential part to be specified in the setup. This can normally be transported, but should be checked before end users start with their activities.

Facts about user roles for configuration and administration are as follows:

  • These roles contain authorizations for basic tasks relevant to the configuration and administration of SAP Master Data Governance for all domains.

    • The role SAP_PAGEBUILDER_DISPLAY is required to use the page builder tool for accessing homepages created using page builder.

    • In addition to user MDG-M, 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.

  • To successfully conduct the next steps in the configuration process, you might need the following user roles assigned in the PFCG transaction:

    • SAP_BC_TREX_ADMIN - for TREX (external Search and Classification Engine)

    • SAP_ESH_LOCAL_ADMIN - for Enterprise Search

    • SAP_MDGA_MENU - for Master Data Governance: Analytics

    • SAP_MDG_ADMIN - for Master Data Governance: Administrator

Some authorizations enable 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. Such an approach ensures users only complete tasks they are responsible for and reduces the risk of critical errors. Authorizations for MDG transactions are not included in this role.

Customizing

The screenshots show the path in the customizing and implementation guide (IMG) to the consolidation and mass processing as well as to the central governance settings.

For direct access to customizing in master data governance components, use the following transactions:

  • MDCIMG (Consolidation and Mass processing)
  • MDGIMG (Central Governance)

These are embedded in separated sub nodes in the SPRO.

The figure show screenshots of the MDGIMG customizing; here for general settings and data model.

The figure, MDGIMG Overview - General Settings and Data Model, illustrates the main customizing activities of the IMG, under the transaction MDGIMG.

The screenshots explains the customizing for UI modeling and data quality management in MDGIMG.

The figure, UI Modeling and Data Quality Settings, illustrates the possible customizing activities for UI modeling and data quality settings.

Change Request Framework

The figure shows on the left hand side the technical concept starting with an Actions, Business Activity, Change Request Type, Change Request Step Types, and Change Request Step (Number). These steps are mapped to the corresponding customizing entries on the right hand side.

The assignment of step types to step numbers is done as follows:

  • In the BRFplus decision tables (for the rule-based workflow)
  • In the workflow step (for other MDG workflows)

Data Modeling

Example: Check and Activate the Material Maintenance Data Model

The screenshots show the inactive data models in the customizing; here the data model for MM.

Check (enhance) and activate the Material Maintenance (MM) data model, including temporary IDs for internal number handling, as follows:

  • Check whether you can use the data model delivered by SAP for managing your material master data with Master Data Governance (MDG) for material.
  • In the case of an upgrade from the previous release, it is essential that you adjust the staging area of the linked change requests.
  • Review and activate the delivered MM data model in customizing for MDG, under Classic Mode in SAP MDG→Central Governance→General Settings→Data Modeling→Edit Data Model.

    Alternatively, run transaction SM34 and select view cluster VC_USMD001.

  • The MM data model has the following characteristics:
    • Root Object Type Material (ID 194) (see also customizing activity: DEFINE ENTITY TYPE TO BE USED BY BUSINESS OBJECT TYPE).
    • Does not support hierarchies.
    • Reuses the standard ERP material database structures as active area using access class CL_MDG_BS_MAT_ACCESS.
This screenshots visualizes the MM data model. Here the entity type material is shown with the attributes on the general tab.

You can visualize the data model in a tabular format.

As of EhP6, you can also check and activate the data models using the Configuration Workbench which offers a more intuitive user interface.

  1. Check the model.

    If the data model does not include all required fields, follow the online documentation and the MDG enhancement guides on: https://pages.community.sap.com/topics/master-data-governance

  2. Review the standard structure.

    You can also use a list or graphic viewer to visualize the data model.

  3. Finally, activate the data model.

    You can only activate the data model if you have the necessary authorization object USMD_DM. You need the required values for the authorization field USMD_MODEL (for example, MM, BP, 0G, …, or *) and the values for the authorization activity ACTVT Activity (01:Create or generate, 02: Change, …).

Other customizing activities in data modeling are only relevant for the material domain if your data model needs to be enhanced.

The screenshot shows the attributes of the entity type marapurch of the mm data model. All attributes in the screenshot are set to centrally governed.

The governance scope determines which fields from the data model can be edited by the MDG application. By deactivating or reactivating an entity, relationship, or attribute, you are not changing any dictionary or database object; you are only changing the ability of MDG to edit the chosen object. When you take a field out of governance scope, it becomes read-only on the MDG UI and you may wish to remove it. You can use the customizing activity Import BC Set to Reset Governance Scope to set the governance scope to the EHP6 model which contains only identifying and descriptive data.

You can select the governance scope at any point after you activate the data model. Use this customizing activity to narrow the governance scope: Master Data Governance→Classic Mode in SAP MDG→Central Governance→General Settings→Process Modeling→Define Governance Scope.

Example: Activate Business Configuration Set

The screenshots explains the activation of the BC-Sets.

The business configuration set for material request type contains the following:

  • Predefined change request types
  • Basic data for workflow

The data model has to be activated in advance.

For create materials, change materials, mark materials for deletion, and process multiple materials, there are example change request types available.

You can run this activity in customizing for Master Data Governance as follows:

  1. Go to Master Data Governance for Material→Import Predefined Change Request Types.
  2. Check that the most recent business configuration set is selected.
  3. To start, choose Activate and keep the default settings.
  4. Execute the business configuration set.

    Note

    If you receive an error message of No processor assigned to workflow WS60800086f for change request type <XXX>, you can ignore it here.

    However, it is necessary for you to assign a processor in the related workflow customizing activity.

The screenshot explains the steps to activate bc-set mdgmat_bcv_70.

If you want to use MDG for material or the Business Context Viewer (BCV), activate the business configuration set MDGAF_BCV and MDGMAT_BCV_70 under SAP Menu→Tools→Customizing→Business Configuration Sets→Activation of BC Sets.

Define Field Properties for UI

The three screenshots explain the field properties definition for entity type material and the field mbrsh. The selected value is no mass changes.
  • Hide Entity Types:

    For material, there are no hidden entity types by default, but you can prevent certain entity types from being visible and included.

    • Change Request
    • Up/Download
  • Hide Field Names:

    For material, certain fields are disabled for displaying search results or for mass changes.

You can hide parts of the pre-delivered Material Maintenance data model either at entity type level or on field level.

To verify the pre-delivered field properties for the Material Maintenance data model in customizing, go to Central Governance→General Settings→UI Modeling→Define Field Properties for UI.

For the Material Maintenance data model, only specific fields are disabled for some of the processes:

Example 1

Classification data is not shown in the search result list since those results can be multi-valued.

Example 2

Material Type (MTART) and Material ID (MATERIAL) are not available as fields in mass change processes.

Example: Verify UI Modeling - Application Configuration

The figure above shows a screenshot of the different application configurations for package MDG_BS_MAT_UI.

Verify the pre-delivered UI model for the Material Maintenance data model.

The following UI configurations are defaulted:

Defaulted UI Configurations

Web Dynpro ApplicationApplication ConfigurationUI
MDG_BS_MATBS_MAT_INIT_09Initial Screen
MDG_BS_MAT_OVPBS_MAT_OVP_09Process-oriented UI
MDG_BS_MAT_OVPBS_MAT_OVP_09HHierarchical UI
MDG_BS_MAT_SEARCHMDG_BS_MAT_SEARCH_09Search UI

You can review these settings using the development workbench. The package name is MDG_BS_MAT_UI. The Floor Plan Manager (FPM) tool needs to be started with those component configurations.

The figure describes the set up procedure for the enterprise search.

The required steps to configure SAP NetWeaver Enterprise Search for MDG for supplier, customer, and material are as follows:

  1. Embedded Search (or Enterprise Search Hub) is configured for the MDG system.

    See the ERP Master Guide and the SAP NetWeaver Enterprise Search documentation on Embedded Search for further information:

    https://help.sap.com/docs/SAP_NETWEAVER_750/6522d0462aeb4909a79c3462b090ec51/773d61cec12a4c1088d78ac909b9abb4.html?locale=en-US

  2. Create the search connector using the SAP NetWeaver Enterprise Search cockpit
  3. Schedule indexing
  4. Test the setup

There are two types of search options available:

  • Embedded Search (included in SAP NetWeaver on a local system)

    Embedded Search is limited to indexing and searching within a single SAP system (single SAPSID).

  • SAP NetWeaver Enterprise Search (run centrally)

    If you want to extend the reach of searches across two or more systems, use SAP NetWeaver Enterprise Search.

In production scenarios with heavy data load, it is mandatory to install a separate TREX instance that is used exclusively by Embedded Search for performance and sizing reasons. For installation information for TREX 7.1 see SAP note 1249465.

Note

The second option requires a separate license for Enterprise Search, while the Embedded Search is included in the MDG license.

SAP HANA-based search for MDG-M

In the figure the path in the customizing for configuring the hana based search for MDG is shown.

SAP HANA-based search for SAP Master Data Governance enables you to perform searches and duplicate checks on master data residing in the SAP HANA database. An SAP HANA search provider is delivered to enable these features.

For more information, see: Configuration of MDG→General Setting→Search Providers→Configuring SAP HANA-based Search for MDG.

Example: Verify Data Quality and Search Settings

Both screenshots show the define search application in the customizing for the data model mm. Here the match profile ID match_mm_material is shown, for the search mode ES.

You can verify and adjust the settings for material. This step is relevant if you have defined your own search application. In the delivered standard, the SAP NetWeaver Enterprise Search is used for master data governance for material.

In the figure, Example: Verify Data Quality and Search Settings, for ES, an Access Class exists, and Freeform, Fuzzy, and Complex Selection are activated. The Match Profile holds the details on fields and weights for duplicate detection.

The standard access class that is delivered is CL_SDQ_USMD_SEARCH_DATA_IMPL.

Data Transfer and Data Replication for Material

The figure illustrates the data transfer option and data replication for material.

The options for data transfer and data replication for material include the following:

  • Enterprise Services (Inbound Processing)
  • Data Replication Framework (DRF) (Out-of-the-Box Replication)
  • More Data Segments / Object Types
  • Mappings
  • Filtering Capabilities (For example, by Classification)
  • Monitor Data Transfer

Data transfer allows you to move master data between systems. These systems can be clients or your main Master Data Governance (MDG) system. The first step of a data transfer is the export of the master data to an IDoc-XML file, which you can save locally or on your application server. In the second step, you import the data into your central MDG system. During the import step, you can decide if you want the new master data to appear directly in the active area, or if you want to work with change requests and import the data to the staging area.

For more details on data transfer, follow the detailed steps described in the configuration guide.

MDG for material reuses existing technologies for the replication of materials and related data to other connected business systems:

  • SOA to connect to third party systems, but also to import data
  • ALE for connected SAP ERP or third party systems
  • CIF to connect to SAP SCM
  • Middleware to connect to SAP CRM or SAP SRM

Perform Customizing for MDG Processing

Business Scenario

You are acting as a business process consultant for MDG and must build the Customizing for your own processes.

Note

All objects of this exercise are named with ##. Replace with your group number.

Use the prepared MDG system T41 client 400 with the SAP Fiori launchpad.

Replace ## with your two-digit team number or in special cases with A .. Y.