Sie sind auf Seite 1von 32

SAP MDG

MDG100 MASTER DATA GOVERNANCE

All rights reserved Nitin G.


Course Contents
Unit 1 MDG Processes
Unit 2 Single Objects Processing
Unit 3 Multiple Objects Processing
Unit 4 Change Request Monitoring & Analysis
Unit 5 Process & User Interface Configuration
Unit 6 Data Quality & Search Configuration
Unit 7 Data Transfer & Data Replication
Unit 8 Custom Object Handling
Exercises - theory/MCQ/Configuration (after each unit)

All rights reserved Nitin G.


Course Contents
Unit 1 MDG Processes
Unit 2 Single Objects Processing
Unit 3 Multiple Objects Processing
Unit 4 Change Request Monitoring & Analysis
Unit 5 Process & User Interface Configuration
Unit 6 Data Quality & Search Configuration
Unit 7 Data Transfer & Data Replication
Unit 8 Custom Object Handling
Exercises - theory/MCQ/Configuration (after each unit)

All rights reserved Nitin G.


Unit II Single Object Processing 2 hours

All rights reserved Nitin G.


MDG Business Processes
The MDG maintenance process starts
when a user requests new master data,
changes to existing master data, or
when changes to master data are
requested by data flowing into the
system through an API.
A master data request causes the
system to generate a change request. A
change request is a container that
keeps all intended changes in a staging
area, separate from the active master
data. This process ensures that changes
are only moved to production after final
approval. The change request moves
through a user-defined workflow
template until everyone in the
workflow views the change request and
the master data is completed.

All rights reserved Nitin G.


MDG Business Processes
Change requests can also store incomplete, inactive data during the workflow. Storing
incomplete data allows a company to determine who will contribute specific information to the
new record without affecting the active master data.
The system continuously validates data during maintenance with existing business logic and
customization settings. The system validation also integrates services for data enrichment and
cleansing. Data enrichment and cleansing include checking addresses against reference data
from an SAP Data Services system. Companies can add their own validation rules.
Near the end of the workflow, a user approves the changes. After approval, the system moves
the data from the staging area into the active master data. The system makes the data available
to business processes and replicates the appropriate data to other systems.
Organizations can place a subset of all master data attributes under central governance. These
attributes can be enriched in the receiving systems according to local needs.

All rights reserved Nitin G.


Work center Roles
The roles in MDG are structured consistently with access to change requests and data exchange.
Financials has an additional Workcenter for editions. SAP provides templates of typical roles that
customers can copy and modify to create their own roles. The following list describes
Workcenter roles process:
A user selects an assigned role.
The user then accesses the Workcenter based on their roles.
The user triggers processes from the Workcenter or from the user work list.

All rights reserved Nitin G.


Change Request Workflow Process

All rights reserved Nitin G.


Change Request Workflow Process
You can use the create change request process to create any type of change request. The change
request type determines the following elements:
The data model and entity types can be maintained
The workflow template the system uses
The UI configuration, if applicable
When creating a change request, the requestor enters a description what they want changed or
created. A master data expert, who can also be the requestor, then enters the master data according
to the description of the requestor. The workflow can also include additional steps for users to enter
comments or specific master data. The submission for final approval is then triggered either by a
person in the workflow or by an automated rule. After final approval, the master data is activated and
available for replication to local systems.
If the final approver rejects the change request, a special rework step can be triggered. The person
designated to rework the data can determine what changes to make and then resubmit or withdraw
the change request.

All rights reserved Nitin G.


Staging Area Usage

All rights reserved Nitin G.


Staging Area Usage
The following steps make up a request and change request workflow process:
Request Creation of a change request including the reason for the request and other information such as
attachments.
Maintain
Users add comments.
The system retrieves active master data.
The system maintains the master data and updates it in the staging area.
Validate Validation happens upon request, when users save changes, and after a save in the background.
Approve
The approval process is part of collaboration by an adaptable workflow template.
The approval activates new data, and the system moves the new data from the staging area to the active database.
Replicate Automatic replication by the system to non-SAP and SAP systems.
You can configure the workflow process change requests for differently specific applications and customers.

All rights reserved Nitin G.


MDG User Interface
All activities associated with creating and
maintaining master data are combined in
one workcenter for each domain.
Companies can establish this Workcenter
as the standard hub for creating and
changing master data. If your company
does not use the SAP Enterprise Portal,
you can use a workcenter based on SAP
NetWeaver Business Client.

All rights reserved Nitin G.


MDG User Interface
The following business challenges have been expressed by some SAP customers:
Master data is maintained on different computer systems.
Different transactions are performed to complete common maintenance tasks such as change,
create, and delete.
Planned changes are not transparent or shared to other systems.
The following business values can be achieved using SAP Workcenters:
Activities required to complete master data governance on one system are bundled into one
system.
Central deployment and authorization ensures comprehensive governance.
Localize and personalize the UI to meet customer needs.

All rights reserved Nitin G.


Specific processes in MDG
The following domain-specific processes are available in Master Data Governance:
Mass loading of master data
Searching for object instances
Centrally creating new object instances
Change existing single object instances
Make general changes
Extend existing object instance, such as adding a new company code
Block or phase out an existing object instance

Replicating specific object instances into specific target systems

All rights reserved Nitin G.


Specific processes in MDG
MDG features many built-in processes, including domain-specific processes for material
governance. Many of these processes employ user interface components specific to the domain.

All rights reserved Nitin G.


Specific processes in MDG
These material domain processes are
preconfigured with a set of BRFplus
rules for the rule-based workflow
template. You can import and
enhance these rules based on the
requirements of your system.
MDG includes standard material
workcenters in the user menu, which
correspond to the preconfigured
material domain processes.

All rights reserved Nitin G.


Processing Parallel workflow steps
Process Parallel workflow for supplier records

All rights reserved Nitin G.


Parallel processing of Supplier Data
The change request workflow
template can be configured
with parallel approval steps for
specific parts of the process.
The process ends when all
parallel approval steps have
been completed.

All rights reserved Nitin G.


SAP Business Partner
A person, organization, group of persons, or group of organizations in which a company has a
business interest. This business object can be used for a variety of business transactions.
You create and manage centrally your business partners (BPs) and the roles they assume for
your company. For this purpose, you define the general data of the business partner once and
you assign business partner roles (BP roles) to the business partner. Specific data is stored for
each business partner role. In this way you do not store redundant data, since the general data
is independent of a business partners function or of application-specific extensions.
When you first create a business partner in the system, the BP role General Business Partner is
automatically assigned to the business partner.

All rights reserved Nitin G.


Customer/Vendor Integration (CVI)
Customer/Vendor Integration for the business partner may be required if you want to use Financial
Accounting (FI)and SAP Business Partner in parallel.
In Financial Accounting (FI) for company external accounting, accounts receivable and accounts
payable accounting is used as part of the Accounts Receivable (AR) and Accounts Payable
(AP) subledgers to manage accounting data for all customers and vendors. Financial
Accounting does not rely on the SAP Business Partner to manage the business partners, but uses
its own customer/vendor master records, which are integrated in all accounting transactions, such
as creating business transactions on accounts and processing posting data.
Many SAP customers have been using Financial Accounting for a long time and are now
increasingly using other applications, such as Loans Management (FS-CML) or
SAP Treasury and Risk Management (TRM) , which use the SAP Business Partner to manage
business partners. These customers require business partners that are managed as
customers/vendors in Financial Accounting and as business partners in other applications, to exist
synchronously.

All rights reserved Nitin G.


CVI - Example
Business partner Adams is one of your companys customers. In the
business partner he is managed under the number 4556 ,and in the
customer master record under number 7894. If certain data, such as
his address or bank details, changes, this data should be changed in
both business partner management systems. You can use customer
and vendor integration independent of each other. There are
applications that use only customer integration, and others that also
require vendor integration.

Customer/vendor integration is intended as a one system/one client


solution.

All rights reserved Nitin G.


MDG Supplier Data Model

All rights reserved Nitin G.


MDG Material Data Model

All rights reserved Nitin G.


MDG Financial Data Model

All rights reserved Nitin G.


Handling of Active & Inactive Data

All rights reserved Nitin G.


Processing Customer Master Data on a
Client System

All rights reserved Nitin G.


Processing Customer Master Data on a
Client System
The business function, Master Data Governance for Customer on the designated SAP ERP client
(MDG_CUST_ERPCLIENT_1), provides features for decentralized customer master data
governance. It enables you to search and compare corresponding data on the hub system before
creating or changing customer master data on a client system. If the customer data is not
already available on the client, you can copy the customer master data from the hub system to
the client system. The data can be edited in the client system.
This business function provides features for decentralized customer master data governance. It
enables you to search and compare corresponding data on the hub system before creating or
changing customer master data on a client system. If the customer data is not already available
on the client, you can copy the customer master data from the hub system to the client system.
The data can be edited in the client system.

All rights reserved Nitin G.


MDG & Information Steward
This is one of the latest achievements with SAP Information Steward 4.1. DQ Scorecard can be
exposed and the Failed Records to the MDG Business Client and then users from within the
Business Client can view and drill down the DQ Scorecard, check and highlight the failed records
and immediately create a Change Request to process the wrong data.
SAP offers a RDS Master Data Governance with Information Stewardship to the customers that is
especially including this integration.

All rights reserved Nitin G.


SAP Information Steward
SAP Information Steward provides business analysts, data stewards, and IT users with a single
environment to discover, assess, define, monitor, and improve the quality of their enterprise
data assets through the various modules described below: -
Data Insight: Profile data, create and run validation rules, and monitor data quality through
scorecards.
Metadata Management : Catalog the metadata across their system landscape, analyse and
understand the relationships of their enterprise data.
Metapedia: Define business terms for data and organize the terms into categories.
Cleansing Package Builder: Define cleansing packages to parse and standardize data.
Match Review: Review results of automated matching on a regular basis and make any
necessary corrections. Match Review maintains a list of records in the "My Worklist" tab that
involves reviewers' actions for match decisions.

All rights reserved Nitin G.


SAP Information Steward

Through the Data Insight module of Information Steward, business analysts and data stewards discover data
characteristics and data relationships, create and run validation rules to perform business process centric data quality
assessment, identify and analyze bad data and monitor data quality through scorecards.
Metadata Management module enables business analysts and data stewards to catalog their data and understand the
relationships of their enterprise data
Metapedia is essentially a business term taxonomy that data stewards can define to develop common understanding
across business and IT users that sets the foundation for their information governance initiative.
Cleansing Package Builder module provides data stewards the ability to define cleansing packages and effectively
apply their business expertise into the process of data cleansing and data standardization.
My Worklist is a centralized task management component within Information Steward through which data stewards and
business analysts can engage in Metapedia term approval process or Match Review tasks in which they can inspect
results of automated matching on a regular basis and make any necessary corrections.

All rights reserved Nitin G.


Exercise:
1. MDG_EX_U2.1 = Detailed (For understanding of concept) 90 Mins

All rights reserved Nitin G.


Q&A

All rights reserved Nitin G.