Show TOC

Process documentationConfiguring Master Data Governance for Customer

 

SAP Master Data Governance for Customer (MDG-C) enables you to govern customer master data on a hub system and to replicate the customer master data to a variety of different client systems.

Additional features for decentralized customer master data governance are delivered with the business function Master Data Governance for Customer on Client (ERP). It enables you to search and compare corresponding data on the hub system, before creating or changing customer master data on a client system.

Note Note

For detailed information how to configure MDG-C on client system, see Configuring Master Data Governance for Customer on Client System.

End of the note.

To use SAP Master Data Governance for Customer, you need to carry out the steps described below.

Prerequisites

Business Functions

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 and the values for the authorization activity ACTVT Activity (for example 01:Create or generate, or 02: Change).

In the Customizing activity Activate Business Functions (transaction SFW5), you have activated the following business functions:

Note Note

If you intend to distribute data using SOA services, you have to activate the following business functions on the hub system and on the client systems:

End of the note.

Note Note

If you want to use graphical elements in the MDG-C work center or the Business Context Viewer (BCV), we recommend to activate the following business functions:

For information about the Business Context Viewer, see Business Context Viewer (BCV).

End of the note.

Note Note

If you want to use the ALE replication of customer master records with bank accounts that were created with IBAN and without BIC, you have to activate the following business function on the MDG hub and on the MDG client system:

End of the note.

Note Note

If you want to use the Highlight Deletions feature, you have to activate the following business function:

End of the note.
Authorization Objects

You have assigned the relevant authorization objects and roles. For more information about the authorization objects and roles, see Customer Master Data Governance (CA-MDG-APP-CUS).

Set Up Workflow

You have defined general settings for SAP Business Workflow in Customizing for SAP NetWeaver under Start of the navigation path Application Server Next navigation step Business Management Next navigation step SAP Business Workflow End of the navigation path.

Web Dynpro Applications

You have activated the services for Web Dynpro Applications. For a detailed list of the relevant services, see Services to be Activated for Web Dynpro Applications.

Constraints
  • Master Data Governance for Customer does not support time dependency for central data, addresses, and business partner relationships. Therefore it cannot run on clients using the SAP business partner with time dependency for central data; see table TB056. Time validity for bank details and roles is supported.

  • With MDG being deployed on an ERP system that is not directly connected to a CRM system by CRM Middleware, services are required to distribute business partner and customer data into a CRM client system as of CRM 7.01 and higher.

    Up to CRM 7.01 the distribution is limited to business partner data; as of CRM 7.02 most customer and CRM specific data such as sales area data or tax classifications can be distributed.

Result

The system is configured for Master Data Governance for Customer.

More Information

Master Data Governance Security Guide

For information about the data model of Master Data Governance for Customer and options to extend the data model, see SAP Note 1973686Information published on SAP site.