SAP Master Data Governance Operations Guide

1 Getting Started

1.1 Important SAP Notes

⚠ Check regularly for updates available for the Application Operations Guide.

1.2 History of Changes

⚠ Make sure you use the current version of the Application Operations Guide. The current version of the Application Operations Guide is at service.sap.com/instguides on SAP Service Marketplace.

The following table provides an overview of the most important changes in prior versions.

2 Technical System Landscape

SAP Master Data Governance (SAP MDG) is designed for a low total cost of ownership. It runs on a single ABAP stack. Its functionality can be enhanced by optional components.

For the latest version of SAP Master Data Governance, the SAP Business Suite and SAP Solution Management are mandatory components (shown in yellow). For SAP MDG Material, the TRex and MDM component is also required. All the other components in figure 2.1 are optional.

Figure 2.1

Description: A diagram illustrating the SAP system landscape for SAP Master Data Governance. It shows several key areas: SAP Solution Management (including SAP Solution Manager, WEB AS ABAP, J2EE Server, Maintenance Optimizer, SLM, System Landscape Directory, Solution Manager Diagnostics, WEB AS Java), SAP Business Suite (including SAP ERP Enhancement Package, ABAP Server, J2EE Server, Database, SAP Business Objects Portfolio), SAP NetWeaver (including Portal & ADS, BI Reporting, PI Process Integration), and specific components like SAP NWDI, TREX & MDM. The diagram visually represents how these components interact and are deployed. Mandatory components are highlighted in yellow.

2.1 Scenario/Component Matrix

Figure 2.3 Description: A diagram depicting the structure packages and main packages of SAP Master Data Governance (SAP MDG) within their respective software components. It shows groupings like MDG_BS_ECC_STRUCTURE, MDG_BS_ECC_APPLICATION, MDG_BS_ECC_COMMON_OBJECTS under SAP_APPL, and MDG_APPL, MDG_ECC_BP, MDG_ECC_MAT also under MDG_APPL. Another section shows BS_REUSE, MDG_BS_FOUNDATION, MDG_BS_APPLICATION under SAP_APPL, and MDG_FND, MDG_BUSINESS_PARTNER, MDG_FINANCIALS, MDG_FOUNDATION, MDG_RIF under MDG_FND. The ECC EhP 6 is also indicated.

The following table includes all components of SAP Master Data Governance in the application component hierarchy (ACH):

Figure 2.2 Description: A diagram illustrating the evolution of SAP Master Data Governance software components. It shows SAP_APPL 6.06 and MDG_APPL 6.06, and SAP_BS_FND 7.31 and MDG_FND 7.31. It also lists underlying components like SAP_ABA, SAP_BASIS, WEBCUIF, PI_BASIS, SAP_BW 7.31. The text explains that new components MDG_APPL and MDG_FND allow independent shipments after EhP6.

3 Monitoring of SAP Master Data Governance

Within the management of SAP Technology, monitoring is an essential task. A section has therefore been devoted solely to this subject. You can find more information about the underlying technology in the SAP Netweaver Administrator's Guide - Technical Operations Manual in the SAP Library under SAP NetWeaver Library.

3.1 Alert Monitoring

Proactive, automated monitoring is the basis for ensuring reliable operations for your SAP system environment. SAP provides you with the infrastructure and recommendations needed to set up your alert monitoring to recognize critical situations for SAP Master Data Governance as quickly as possible.

3.1.1 Monitoring Installation and Setup

In order to enable the auto-alert mechanism of CCMS, see SAP Note 617547.

3.1.2 Component-Specific Monitoring

Under the Technical Expert Monitors of CCMS, there is a monitoring context for DRF. Whenever an outbound replication failure occurs, an alert is written into CCMS.

3.2 Detailed Monitoring and Tools for Problem and Performance Analysis

3.2.1 Trace and Log Files

Trace files and log files are essential for analyzing problems.

SAP Master Data Governance (SAP MDG) provides the following application logs:

• Validation log for change requests
• Validation log for editions
• Workflow log
• Data exchange log

All application logs are displayed in a hierarchical view and can be filtered by message type. All SAP MDG applications call the log display using Web Dynpro applications.

Validation logs: In order to access both validation logs in transaction SLG1, enter the object FMDM and select the subobject CREQUEST from the value help.

Workflow log: SAP MDG also uses a workflow log. It is the standard workflow log provided by SAP Business Workflow. We provide our own application for the display of the log. It can be started from the change request list.

Data exchange log: Data exchange includes the following data replication (process-driven, usually message-based replication of data from the SAP MDG hub to the client's hub) and data transfer (mass transfer, usually file-based export and import) logs:

Data replication logs

You can display the replication logs in the SAP Easy Access menu under Cross-Application Components -> Processes and Tools for Enterprise Applications -> Master Data Governance -> Data Replication -> DRFLOG – Analyze Replication Log (transaction DRFLOG). For more information, see Evaluation of Replication Logs - SAP Easy Access. In order to access the replication logs in transaction SLG1, enter the object DRF_OUTBOUND.

Replication logs can be deleted with the transaction DRFLOGDEL.

In addition, it is possible to display the replication status for each object from the object display. For example, from the search result for supplier, you can see to which systems the supplier has been replicated, successfully or not. For system administration and error analysis, you can use the transaction DRFRSD.

There is also a database where the trace files are stored. These can only be accessed using the application logs. The table name is DRFD_SERVOUT_LOG. The entries in the table are deleted together with the corresponding application logs. Here the result of the filtering is stored, and the list of objects which will be replicated. The replication status is stored for each object in the database table DRFD_OBJ_REP_STA. Entries in this table can be deleted with the transaction DRFRSDEL.

Data transfer logs

You can monitor the import and export of master data using the Monitor Data Transfer function in the Enterprise Portal or in the NetWeaver Business Client (Data Exchange -> Data Transfer -> Monitor Data Transfer). You can also access this using transaction DTMONITOR. This function offers the display of the logs and details on the status of the import processes.

Data transfer logs can also be found using transaction SLG1, object MDG_FILE_PROCESSING.

Additionally, qRFC monitoring (transaction SMQ2) is available to find out more details about exports and imports which have been executed with parallel processing enabled. The corresponding queues have to be created before executing the export or import process.

For SAP MDG for Financials and Custom Objects, the XML-based data transfer is currently not available. Here the CSV-based file upload and download is used. Logs for this can be found in transaction SLG1, object FMDM, sub-objects UPLOAD and DOWNLOAD. File upload allows you to copy master data from a file to the database tables defined in the data model for SAP Master Data Governance. File download allows you to copy master data from MDG-specific database tables to a local file in CSV format, allowing you to upload the data from this file to decentralized systems.

3.2.2 Workload Monitors

For more information, see the section on Workflow Monitors in the general ERP Operations Guide.

3.2.3 Interface Monitors

Interface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and HTTP.

For the full list of interface monitors, see section 8.3 on Interface Monitors.

Monitor tools for these Interfaces:

3.2.4 Data Growth and Data Archiving Monitors

For reuse objects, a standard mechanism is used. However, change requests are not archived, but can only be deleted using a standard report.

SAP MDG for Customer: SAP MDG for customer/supplier and business partner uses the ERP archiving framework and monitoring tools. An SAP MDG customer/supplier always represents an ERP business partner (BP) and the linked ERP customer/vendor (CVI), so the existing ERP archiving objects were enhanced with MDG specific checks (at the moment only the existence of change requests for the object is checked).

The relevant archiving objects (table AUTH_OBJ, transaction SARA) are:

• CA_BUPA (business partner)
• FI_ACCRECV (customer master data)
• FI_ACCPAB (vendor master data)

SAP MDG for Material: SAP MDG for Material uses the archiving object MM_MATNR. For more information on these archiving objects, see the ERP Operations guide.

SAP MDG for Financials: SAP MDG for Financials does not use archiving objects. Customers can copy the data model 0G or create their own data model. The fastest growing entity types are ACC, ACCCDET, FSI, CCTR, and PCTR, which can be viewed in transaction SE38. Enter the program USMD_DATA_MODEL and select the checkbox for Count Data Records.

For periodic tasks required to contain data growth (that is, to reorganize temporary data), refer to the periodic tasks section in this guide.

3.3 Data Consistency

If related or identical data is stored in multiple places there may be the possibility of inconsistencies (e.g. after a restore of a single component). The following table describes how consistency can be verified and how inconsistencies may be repaired.

The report ESH_TEST_SEARCH provides information about the connectors and this information can be cross-checked with SE16 for the reuse and staging area.

3.4 Change Request Analysis

You can analyze change requests in the following ways:

• Check how quickly change requests are being processed: For any time frame or change request priority, you can quickly identify the extent to which change requests comply with or violate target processing times. If you enable dashboards, you can view this information in an interactive graphical format.
• Check the status of change requests: For any time frame or change request priority, you can get a summary of the numbers of change requests completed and rejected, completed and accepted, and created. You can also get a summary of rejection reasons.
• Assess your own involvement with change requests: For change requests involving you, you can view a graphical summary of the nature of your involvement in a side panel.

For instructions on how to ensure the analysis of change requests is possible within MDG, see Enabling Detailed Analysis of Change Requests.

4 Management of SAP Master Data Governance

SAP provides you with an infrastructure to help your technical support consultants and system administrators effectively manage all SAP components and complete all tasks related to technical administration and operation.

You can find more information about the underlying technology in the Technical Operations Manual in the SAP Library under SAP NetWeaver.

4.1 Software Configuration

This section explains which components or scenarios used by this application are configurable and which tools are available for adjusting.

Configure the Workflow

You use this process to make all Customizing settings that are needed to run the workflow for the change process in SAP Master Data Governance.

The settings you make depend on whether you use a rule-based workflow or a different workflow (for example, the standard workflow templates for business partner/supplier, customer, or financials).

For the rule-based workflow, you integrate rules from the Business Rule Framework plus (BRFplus) with the workflow.

Prerequisites: You have made the necessary general settings for workflows and defined the organizational plan in Customizing for SAP NetWeaver under Cross-Application Components -> Processes and Tools for Enterprise Applications -> Master Data Governance - General Settings -> Application Server-> Business Management -> SAP Business Workflow (transaction SWU3).

Process: You can find Customizing for SAP Master Data Governance for the following steps under General Settings -> Process Modeling -> Workflow or Change Requests.

1. To assign processors to a workflow task, classify the workflow task in the Customizing step Configure Workflow Tasks as a General Task.
2. For a rule-based workflow, make the following settings:
   1. In the Customizing activity Define Steps for Rule-Based Workflow, define the individual workflow steps that are to be executed for a particular change request type.
   2. In the Customizing activity Define Service Names for Rule-Based Workflow, define a corresponding service name for each Business Add-In (BAdI) implementation that you want to create. Service names are used as filter values for the BAdI implementations used in the rule-based workflow.
   3. In the Customizing activity Configure Rule-Based Workflow, configure the workflow rules.
   4. Assign the workflow template WS60800086 to your change request type in the Customizing activity Create Change Request Type.

For more information, see Setting of Rule-Based Workflows.

The use of rule-based workflows can be part of your enhancement concept. For more information, see Enhancement of Master Data Governance Content.

3. For all other workflows of Master Data Governance (for example, the standard workflow templates for business partner/supplier or financials), make the following settings:

1. In the Customizing activity Define Workflow Step Numbers, check whether the delivery Customizing is being used.
2. In Customizing activity Assign Processor to Workflow Step Number (Simple Workflow), assign one or more processors to each workflow step.
3. When processing a change request, assign the workflow templates to be used (for example, the standard workflow template for Financials, WS75700027) to your change request type in the Customizing activity Create Change Request Type.
4. You can also define a specific application depending on the workflow step under General Settings -> Process Modeling -> Change Requests -> Configure Properties of Change Request Step. Make your settings under the area menu User Interface per Change Request Step.

In addition, there are Customizing BAdIs available to enhance the standard functions. For more information, see SAP Library for SAP enhancement package 6 for SAP ERP 6.0 on SAP Help Portal at http://help.sap.com/erp606. In SAP Library, choose SAP ERP Central Component -> SAP ERP Enhancement packages -> ERP Central Component Enhancement Package 6 -> SAP ERP Cross-Application Functions -> Cross-Application Components -> Master Data Governance -> Configuration of Master Data Governance.

Set Up the Search Function

To use the search function for SAP Master Data Governance for Material, you have installed and connected either Embedded Search or the dedicated search solution SAP NetWeaver Enterprise Search. If you are not on SAP NetWeaver 7.02 SP06, implement SAP Note 1502296.

The following scenarios can be implemented:

• Embedded Search, which is included in the local SAP NetWeaver system
• SAP NetWeaver Enterprise Search, the central search solution

Embedded Search is limited to indexing and searching within a single SAP system (single SAPSID). If you want to extend the reach of searches across two or more systems, we recommend you 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.

For more information, see Embedded Search and SAP NetWeaver Enterprise Search.

4.2 Backup and Restore

You need to back up your system landscape regularly to ensure that you can restore and recover it in case of failure.

The backup and restore strategy for SAP Master Data Governance consists of two parts:

• Backup and restore coverage for each component (see table below)
• Cross-system data dependencies and handling

The backup and restore strategy for your system landscape should not only consider SAP systems but should also be embedded in overall business requirements and incorporate your company's entire process flow.

In addition, the backup and restore strategy must cover disaster recovery processes, such as the loss of a data center through fire. It is most important in this context that you ensure that backup devices are not lost together with normal data storage (separation of storage locations).

4.3 Periodic Tasks

4.3.1 Scheduled Periodic Tasks

This section describes all automatable tasks required to run periodically in order to keep the application running smoothly over time. Such tasks may be required on component level and are therefore relevant in each scenario that uses the component. You can find the mapping in section 2.1 Scenario/Component Matrix. Other tasks may be relevant for certain business scenarios only.

It is important that you monitor the successful execution of these tasks on a regular basis.

For SAP MDG, customers often plan a periodic report RBDMIDOC to trigger ALE outbound tasks based on change pointers.

Scheduled periodic tasks for SAP Master Data Governance

4.4 Load Balancing

Logging On and Load Balancing Setup/Tools

5 High Availability

SAP Master Data Governance follows the general high availability concept for all SAP NetWeaver based systems. For more information on high availability, see SAP Service Marketplace at help.sap.com/erp606. In SAP Library, choose SAP ERP Central Component -> SAP ERP Enhancement packages -> ERP Central Component Enhancement Package 6 -> SAP ERP Cross-Application Functions -> Cross-Application Components -> Master Data Governance -> High Availability.

6 Software Change Management

Software Change Management standardizes and automates software distribution, maintenance, and testing procedures for complex software landscapes and multiple software development platforms. These functions support your project teams, development teams, and application support teams.

The goal of Software Change Management is to establish consistent, solution-wide change management that allows for specific maintenance procedures, global rollouts (including localizations), and open integration with third-party products.

This section provides additional information about the most important software components.

The following topic is covered:

Transport and Change Management - Enables and secures the distribution of software changes from the development environment to the quality assurance and production environment.

6.1 Transport and Change Management

If you want to add fields or entities to a data model which is connected to a reuse active area (for example, the data models BP or MM or copies of those), all open change requests for this data model will be locked. In order to unlock these change requests and to adapt the change request data to the enhanced data models, you run the report USMD_ADJUST_STAGING. You can schedule this report to run in all clients in Customizing for Master Data Governance under General Settings -> Data Modeling -> Edit Data Model. Choose the button Adjust Staging Area of Linked Change Requests. For more information, see SAP Note 1591280.

Note that this step must be executed in every system where the data model change has been imported.

7 Support Desk Management

Support Desk Management enables you to set up an efficient internal support desk for your support organization that seamlessly integrates your end users, internal support employees, partners, and SAP Active Global Support specialists with an efficient problem resolution procedure.

For support desk management, you need the methodology, management procedures, and tools infrastructure to run your internal support organization efficiently.

The following topics are covered:

• Remote Support

Component hierarchy relevant for this application

7.1 Remote Support Setup

To set up remote support the following connection types should be opened in the Service Connection maintenance screen:

• R/3 Support
• HTTP connect - URLAccess

For more information, see SAP Note 592085.

7.2 Problem Message Handover

For information about the processing of internal support messages and forwarding them to SAP, see SAP Help Portal at help.sap.com -> SAP Solution Manager -> SAP Solution Manager 7.0 -> English -> Service Desk. To send problem messages to SAP, use the relevant ERP application component in the SAP application component hierarchy.

For information on the component hierarchy names used to send tickets, see section 2.1, Scenario/Component Matrix.

8 Appendix

8.1 Related Guides

You can find more information about installation and configuration in the Master Guide.

8.2 Related Information

The following table contains links to information relating to the Application Operations Guide.

8.3 Interface Monitors

Interface Monitors Table: