SAP Master Data Governance for Supplier and Customer Data %e2%80%93 Overview

SAP Master Data Governance for

Business Partner, Customer and Supplier Data Overview including SAP MDG 7.0 updates

November 2013

2013 SAP AG. All rights reserved. 2 SAP Master Data Governance for Business Partner, Supplier, Customer MDG-BP/C/S

Agenda

Introduction

Current Reality

Need for the Future

Master Data Governance Capabilities

Architecture and Deployment

Function in Detail

Integration Scenarios

Benefit from the Solution


Every organization has master data, yet every organization's definition of what master data is, is different. And many organizations may have no or

incomplete definitions of what master data is. Although there is no universal

example of what constitutes master data, a common definition must be

applied. http://www.gartner.com/technology/it-initiatives/master-data-management.jsp

Master data is the consistent and uniform set of identifiers and extended attributes that describes the core entities of the enterprise, such as

customers, prospects, citizens, suppliers, sites, hierarchies, and chart of

accounts. http://www.gartner.com/technology/it-glossary/mdm-master-data-management.jsp

What are Master Data?


Lack of Data Governance Policies and

Poor Data Quality Hurt the Business

Compliance

Failures

90% of all businesses still do not have

sufficient policies in place to meet data

governance regulations. IT Policy Compliance Group

Low

Productivity

50% to 70% of ERP implementations are reported as

challenged in part to data integrity and/or data

accuracy problems.

Adaptive Growth, Inc.

Lower Profits

Average organization loses $8.2 million annually

through poor data quality.

Gartner


All lines of business are impacted by master data quality

High master data

maintenance costs

Need for multiple systems

to manage master data in

different domains

Lack of flexibility in dynamic

business environments

Lack of consolidated view of customer data across all channels

Customer transactions are compromised due to limited view of the facts

Lack of transparency relating to suppliers and products

High costs due to insufficient supplier selection and rationalization

Loss of potential for benefit realization (i.e. discounts, conditions, central contracts)

Limited availability of up-to-date master data in my business network

Inconsistent financial

master data across the

enterprise

Manual efforts to update

financial master data in

local financial systems

Risk of non-compliance to

IFRS, SOX etc.

Slow group closes

Lack of transparency about

changes (Who, what, when,

why?)

Organizations & Roles

Challenges

IT

CIO CFO VP of Supply Chain,

VP of Planning

Financials Sales

(S)VP of Sales, (S)VP

of Sales & Marketing

Supply Chain


SAP Master Data Governance Centrally govern master data on top of SAP Business Suite

SAP MDG is a natural extension of the business processes running in

SAP Business Suite, providing out-of-the-box, domain-specific master data

governance to centrally create, change and distribute master data.

Governance Enables governance, compliance and transparency through integrated staging, approval and central audit trail

Consistent Data Delivers consistent definition, authorization and replication of key master data entities for SAP. Eliminates error prone manual maintenance processes for master data in multiple systems

Integration Native integration with SAP Business Suite and SAP ERP, as well as supplier qualification (via SAP SLC), and NW MDM

Re-use Re-use of SAP data model, UI and existing business logic and configuration for creation and validation of master data

Flexibility Allows to extend the existing models or define new objects and related processes in order to govern own master data domains

Data Quality Leverages SAP Data Services for data quality and enrichment as well as SAP Information Steward for data remediation


Maintain Validate Approve Replicate

Adapt

3rd party systems

Business

Suite

systems

Business Processes

SAP Master Data Governance Process flow archetype

Master Data Governance

Central

maintenance of

master data in

staging area

Automatic replication to

non-SAP and SAP

systems

Adaptation /

Enrichment in

local systems 5

Maintain Validate Approve Replicate

Adapt 5

External Providers External Services

Re-Use existing business logic

Integrate external services

Data Enrichment, Address

Cleansing, Duplicate Check

Collaboration

Adaptable Workflow

Auditable Change Process


Agenda

Introduction

Current Reality

Need for the Future



Function in Detail




Questions From the Procurement / Supply Chain LOB

How can I maximize financial benefits (i.e. discounts, conditions,

central contracts) through correct and complete supplier data?

How can I improve my procurement decisions, i.e. supplier

performance / evaluation, duplicates, spend analysis that falsify

my view on my suppliers?

How can I ensure high quality of my supplier data, in order to

save costs and efforts in subsequent processes, i.e. shipping to

the correct address, assigning the best source of supply?

How can I reduce manual work through the need to maintain

data in several systems?

How can I get transparency on who has changed what, when

and why?

How can I establish a single source of truth for supplier master

data in my multi-system environment?

And while accomplishing all that how can I best leverage my investment in SAP?


Master Data Multitude of Processes and Facets

Is there one single person in your

organization who knows all this?

Supplier

Master Data

Procurement

Planning and

Analysis Purchase

Requests

RFx

Process

Purchase Order

Processing

Goods Receipt

and Service Entry

Invoice

Processing

Payment

Demand /

Request Creation


Questions From the Sales / Order-to-Cash Chain / LOB

How can I maximize financial benefits (i.e. discounts, conditions,

central contracts) through correct and complete customer data?

How can I have better visibility to make the right sales decisions,

i.e. customer performance / evaluation, duplicates, sales activity

that falsify my view on my customers?

How can I ensure high quality of my customer data, in order to

save costs and efforts in fulfillment and post-delivery processes,

i.e. shipping to the correct address, debit from correct bank

account or credit card, acquiring and creating accurate orders

and contracts?

How can I reduce manual work through the need to maintain

data in several systems?

How can I get transparency on who has changed what, when

and why?

How can I establish a single source of truth for customer master

data in my multi-system environment to avoid the lack of

integration?

And while accomplishing all that how can I best leverage my investment in SAP?


Master Data Multitude of Processes and Facets

Sales

Central Customer

Management

Sales Planning and

Analysis

Quotation and Inquiry

Management

Contract Management and

Pricing

Order Processing

Order Fulfillment

Billing Complaints and

Returns

Is there one single person in your

organization who knows all this?


Agenda

Introduction

Current Reality

Need for the Future



Function in Detail




Strengthen Purchasing and Financials and Sales and

Financials by enabling highest quality customer and supplier

master data over the entire system landscape thereby

optimizing their core business function

SAP MDG

Need for the Future Goal for MDG-C and MDG-S


Need for the Future Goal for MDG-BP, MDG-S and MDG-C

Data Flow

Transparency

within system

landscape

Single Entry

Point to

maintain

supplier data

Standardized

Process to

control data

changes

Transparency on

the data changes

done

(Who, When, What,

Why)

Get a Snapshot of

all the supplier

related activities

Need

Enable All UsersEnable All UsersEnable All Users

Standardized

Tools for

ensuring

data quality

Manage ProcessesManage Processes

Clean Master DataClean Master Data


Agenda

Introduction

Current Reality

Need for the Future



Function in Detail




SAP Master Data Governance capabilities Establish best quality master data to optimize business processes

Re-Usability

& Extensibility

Governance,

Collaboration

& Data Quality Robust Data

Replication

Integrated

Object Model

Deliver

Out-of-the-Box

SAP Master

Data Governance

1

2

5

4 3


SAP Master Data Governance capabilities Deliver out-of-the-box

Out-of-the box data replication mechanisms, using stable mechanisms

Deliver a Data Model proven by several applications & industries

Workflow flexibility closely integrated to a framework for defining business rules

Deliver roles on a web based UI Deliver process-centric solution

Deliver predefined Data Quality Services

Reuse of existing processing logic

Full Integration to SAP Systems as a client

Offer integration services for non-SAP client

systems Low TCO

Flexibility

Ease of consumption

Best Practice

Process Transparency

Integration



Re-Usability

& Extensibility

Governance,

Collaboration


Replication

Integrated

Object Model

Deliver

Out-of-the-Box

SAP Master

Data Governance

1

2

5

4 3


SAP Master Data Governance capabilities Integrated Object Model

Claire Johnson

Wildwater Ltd

Provide a directory of Business Partners (organizations, persons, groups of persons). This contains

data primarily used for identification (e.g. name, address, ID numbers, etc).

The MDG objects like customer and supplier will be based on this directory and shall offer seamless

integration with existing SAP master data objects (e.g. customer master and vendor master in ERP).

Customer Supplier

Prospect

Contact Partner

Bidder


BPs can be connected using relationships

Relationship categories depict types of business connection

between BPs

Categories can have attributes and the categories and the attributes

can be enhanced by the customer

Relationships Usage

General Data Role Concept

SAP BP

The Entity type Business Partner is a generic application for business partner management

(maintaining organizations, persons and groups of persons)

Suite Ext.Applications (CRM, SRM)

Industry solutions

Suite Ext. Industries (Banking, Insurance, Utilities, Telecom,

Media, ) to meet generic and industry-

specific requirements for business

partner management

Roles are views on the attributes and define the relevance by

displaying the specific fields ONLY

Classification according to business criteria

Different attributes relevant for each BP Role

Examples: Customer, Supplier, Prospect, Bidder, Payee, Employee

Consists of core attributes and business attributes from various

applications

Customers/Partners can enhance the BP by adding their own

attributes

Time dependent with Technical validity and business validity

SAP Master Data Governance capabilities Integrated Object Model: SAP Business Partner Fundamentals


Master Data Governance for Business Partner

Integrated Object Model

All solutions use the SAP-BP as central anchor for identifying data

MDG-BP as basis for

Customers limiting their governance scope to BP data only

Solutions only being based on SAP-BP (e.g. Service Industries)

Transition from MDG-BP to MDG-S / MDG-C without disruption

MDG-C

ERP-Customer

data

MDG-S

ERP-Vendor

data

MDG-BP

BP data


Business Partner

data

Roles

Business

Partner Central Data

Bank Details

Identification

Numbers

Tax Numbers

Industry

Sectors

Address

Address

Details

Address

Usages

Phone

Fax

Email

URL

Address

Versions

Organization

Person

Group

Relationships

Contact

Partners

SAP Master Data Governance capabilities Integrated Object Model: Data Model MDG-BP


ERP Customer

specific data

Business Partner

data

Roles

Business


Bank Details

Identification

Numbers

Tax Numbers

Industry

Sectors

Address

Address

Details

Address

Usages

Phone

Fax

Email

URL

Address

Versions

Organization

Person

Group

General Data

Company Code

Data

Dunning Areas

Sales Area

Data

Partner

Functions

Withholding

Tax Types

Tax Indicators

ERP

Customers

Relationships

Contact

Partners

SAP Master Data Governance capabilities Integrated Object Model: Data Model MDG-C


Business Partner

data

ERP Vendor

specific data

Roles

Business


Bank Details

Identification

Numbers

Tax Numbers

Industry

Sectors

Address

Address

Details

Address

Usages

Phone

Fax

Email

URL

Organization

Person

Group

General Data

Company Code

Data

Dunning Areas

Purchasing

organiz. Data

Purchasing

organiz. Data 2

Withholding

Tax Types

ERP

Vendors

Relationships

Contact

Partners

Address

Versions

Partner

Functions

SAP Master Data Governance capabilities Integrated Object Model: Data Model MDG-S


Customer

APIs

Vendor

APIs

CVI Outbound

Get

CVI Complex Interface

Business

Partner

BP APIs Customer / Vendor

Data Buffer

SAVE

Business Partner Customer Vendor

A Business Partner is always created when a

customer or supplier is created.

The complex interface of the CVI (Customer-Vendor-

Integration) contains Business Partner specific data as

well as Customer and Vendor specific data.

Partially, the data of the Business Partner and

Customer/Vendor are redundant (BUT000 against

KNA1 & LFA1 data). For instance Name and Address

specific attributes are available in both persistencies.

Customer or Vendor specific data is routed through

the Customer/Vendor specific interface and mixed up

with the Business Partner central data.

On commit, the Business Partner and corresponding

Customer and/or Vendor is maintained / created.

Central Data

Vendor Customer

Company Code data

Purchase Org. data

Account data Central Data*

Example: Vendor Creation

SAP Master Data Governance capabilities Integrated Object Model: Customer / Vendor Integration


Customer

APIs

Vendor

APIs

CVI Outbound

Get

CVI Complex Interface

Business

Partner

BP APIs Customer / Vendor

Data Buffer

SAVE

Business Partner Customer Vendor

A Business Partner is always created when a

customer or supplier is created.

The complex interface of the CVI (Customer-Vendor-

Integration) contains Business Partner specific data as

well as Customer and Vendor specific data.

Partially, the data of the Business Partner and

Customer/Vendor are redundant (BUT000 against

KNA1 & LFA1 data). For instance Name and Address

specific attributes are available in both persistencies.

Customer or Vendor specific data is routed through

the Customer/Vendor specific interface and mixed up

with the Business Partner central data.

On commit, the Business Partner and corresponding

Customer and/or Vendor is maintained / created.

Central Data

Vendor Customer

Company Code data

Sales Area. data Central Data*

Example: Customer Creation

SAP Master Data Governance capabilities Integrated Object Model: Customer / Vendor Integration



Re-Usability

& Extensibility

Governance,

Collaboration


Replication

Integrated

Object Model

Deliver

Out-of-the-Box

SAP Master

Data Governance

1

2

5

4 3


SAP Master Data Governance capabilities Governance, collaboration

Can be adapted and tailored based on customer needs

Linear or distributed & workflow based

Has roles and responsibilities and also Task authority (e.g., create, change, approve)

Flexible enough to respect the distributed responsibilities existing in a company across various business units

Business Logic

Possibility to extend the process by adding business logic and thereby bringing in data quality

Data in process stored in a separated repository, will be transferred to operational database after final approval

Approval


SAP Master Data Governance capabilities and data quality

Prevent creation of duplicates for in-

creased effectiveness and efficiency

Checked early and embedded in the process

High detection quality of matching using

Enterprise Search or SAP Data Services

Validations

Re-use of existing validation logic in ERP

Custom validations can be modeled and

programmed (e.g. code lists, simple checks,

or modeled rules via SAP BRF+)

Address Enrichment

Simple check and selection lists

Integration with content provided by

SAP Data Services

Automatically adding Tax Jurisdiction Code

re-using existing interfaces / providers



Re-Usability

& Extensibility

Governance,

Collaboration


Replication

Integrated

Object Model

Deliver

Out-of-the-Box

SAP Master

Data Governance

1

2

5

4 3


SAP Master Data Governance capabilities Robust data replication

Replication

Automatic or manual replication to SAP and non-

SAP systems

Peer-to-peer or mediated

Replication Techniques

DRF controlling replication mechanisms like

ALE for SAP ECC, R/3 and non SAP systems

SOA service for SAP and non SAP systems

RFC and File for SAP and non SAP systems

CIF for SAP SCM and MW for SAP CRM and SRM

Replication Features

Flexibility to replicate selected data only to a specific

client system by defining filters (controlled by DRF)

Support of different object IDs or customizing keys

between hub and client systems (via mapping in

MDG or NW PI)

Monitoring and error handling

Process

User

Data Replication

Non-SAP System SAP System



Re-Usability

& Extensibility

Governance,

Collaboration


Replication

Integrated

Object Model

Deliver

Out-of-the-Box

SAP Master

Data Governance

1

2

5

4 3


SAP Master Data Governance capabilities Reusability & extensibility

Reuse standard content

Reuse existing data structures and

functionality of SAP Business Suite

Enhance functionality

Be able to enhance MDG

functionality based on predefined

content (e.g. plant or sales data) or

customer-specific extensions

Extend data structures

Provide easy-to-use extensibility

capabilities for enhancing nodes and

fields

data model

user interface

processes

data replication

Central Team

Core Processes

Extended

Individual Processes

Tasks

Reused


Agenda

Introduction

Current Reality

Need for the Future



Function in Detail




SAP Master Data Governance High-level Architecture Overview

Portal / NetWeaver Business Client

SAP Information

Management Suite

Central System for Master Data Processes Client

Systems

ERP

SRM

CRM

SCM

Cloud

Systems

3rd Party

NetWeaver MDM

AS ABAP

Enterprise Search

Data Services

Information Steward

Optional

Parts

SAP ERP 6.0

SAP Master Data Governance

On Premise

Apps

Financials

User Interfaces, Roles, Work Centers

Change Request, Governance Model, Search & DQ Adapters,

UI Framework, Analytics, Replication, Key / Value Mapping

Material

Business Partner Custom Objects

Workflows

Staging

Validation

Integrate services for data cleansing, matching & consolidation

Client systems are integrated via various channels (such as SOA, ALE, RFC, File)

Tight integration into SAP Business Logic and leveraging standard AS ABAP

SAP HANA


SAP SCM

3rd party

systems,

SAP SRM

SAP ERP, SCM,

CRM, SRM

3rd party

systems,

SAP MDG Deployment Options Consciously Decide for a Central hub or Co-deployment

Deploy SAP MDG

as standalone system / master data hub

on top of an operational ERP

Customers typically choose to

create a dedicated master data hub and distribute to all operative systems from there, or

co-deploy*) with their single instance SAP ERP (or pick one of their SAP ERPs as the master for a particular domain) and create and distribute master data from there

SAP MDG SAP ERP

SAP MDG

& SAP ERP

*) if speed of innovation in their ERP systems does not allow for quick introduction of SAP MDG, some customers create a separate system first, and re-combine later


Using SAP HANA in the Context of SAP MDG as Primary or Secondary Database

SAP MDG 7.0 can be installed on both EhP6 or EhP7 for SAP ERP 6.0

If installed on EhP7, it can run on SAP HANA as primary database

SAP MDG 7.0

SAP HANA

SAP MDG 7.0

SAP HANA Any Database

duplicate-detection and

similarity-ranked search

Option 1: HANA Side-by-Side Option 2: MDG on HANA

replicate

EhP6 or EhP7

for SAP ERP 6.0

EhP7

for SAP ERP 6.0


Agenda

Introduction

Current Reality

Need for the Future


Architecture

Function in Detail




Agenda

Function in Detail

Processes

Workflow

Entry Points / User Interface

Multiple Customer/Vendor Assignments

Client Maintenance

Search

Data Quality / Validation / Cleansing

Data Replication

Process Analytics


Block / Unblock Create Set Flag for Deletion Change

Business Partner, Customer or Supplier needs to be deleted in the next archiving run

Search successful and data is incorrect

Business Partner, Customer or Supplier is no longer relevant for processes

Business Partner, Customer or Supplier does not exist for processing

Usage

Function in Detail Processes: When to Use Which Process?


Function in Detail Processes: Single Object Maintenance

MDG 6.1: Two-step approach

Change Request 1: Create new organization

Change Request 2: Create new person(s) and add contact person relationship(s)

MDG 7.0: One step approach

Change Request 1: Create new organization, add new relationship (a) and new person (b)

a) Add new

relationship

b) Create new

person


Requestor

Search

Found

Not Found

Requestor

?

Change

No

Yes

Change Workflow

STOP

Requestor

?

Create

No

Yes

Create Workflow

STOP

Function in Detail Workflow: Business Partner / Customer / Supplier


Function in Detail Workflow: Create Supplier

Activate data

& Replicate

Company Code Data

Purchasing Organisation Data

Central Data

Submit for

Approval

Approve

Company

Code data

required?

Requestor

Maintain Central Data Comp.Codes Purch. Orgs

Master Data Specialist

Review central data

Purchasing

Org data

required?

STOP

Reject / Rework

Cancel

Change Request

Purchasing Specialist

Review purchasing org. data

Financial Specialist

Review company code data


Maintain purchasing org. data


Maintain company code data

Reject / Rework

Reject / Rework

Approve

Approve


Function in Detail Workflow: Change Supplier

Request data change

Submit for

Approval

Company

Code data

changed

Requestor

Maintain Central Data CC data PO data

Purchasing

Org. data

changed

STOP Cancel

Change Request

Central data

changed

Activate data

& Replicate

Approve

Approve

Approve


Review central. data





Central

Data

Purchasing

Org. Data

Company

Code Data

Reject / Rework

Reject / Rework

Reject / Rework


Function in Detail Workflow: Block / Unblock Supplier

Activate data

& Replicate

Request data change

Submit for

Approval

Block

Company

Code data

Requestor

Block Central Data CC data PO data

Block

Purchasing

Org. data

STOP Cancel

Change Request







Central

Data

Purchasing

Org. Data

Company

Code Data

Block

Central data

Reject / Rework

Reject / Rework

Reject / Rework

Approve

Approve

Approve


Function in Detail Workflow: Set Flag for Deletion Supplier

Activate data

& Replicate

Request data change

Submit for

Approval

Deletion flag

Company

Code data

Requestor

Block Central Data CC data PO data

Deletion flag

Purchasing

Org. data

STOP Cancel

Change Request







Central

Data

Purchasing

Org. Data

Company

Code Data

Deletion flag

Central data

Reject / Rework

Reject / Rework

Reject / Rework

Approve

Approve

Approve


Function in Detail Workflow: Create / Change Business Partner / Customer

Central Data

Submit for

Approval

Approve Requestor

Create,change Block, Set flag

for deletion Central Data


Review central data

Reject / Rework

STOP

Cancel

Change Request

Activate data

& Replicate


Function in Detail Entry Points / User Interface: Landing Page for NW Business Client

(Example: Supplier)

All relevant tasks

reachable with one

click

Additional content like

My Change Requests can be integrated

Easy to configure and

personalize


Function in Detail Entry Points / User Interface: NWBC (Change Request Services)


Function in Detail Entry Points / User Interface: Maintenance UI


Function in Detail Entry Points / User Interface: Flexible UI via Configuration / Personalization

User interface easy to configure and easy to personalize

Note: Certain customer adaptions made in EHP5-UI have to be redone for the

new EHP6-UI


Function in Detail Entry Points / User Interface: Flexible UI via

Configuration / Personalization

1. Multi column (up to 3) design

2. Change sequence

3. Expand / compress / suppress blocks

4. Stacked UIBBs (Tabs)


Function in Detail Entry Points / User Interface: Flexible UI via Integration of Context Based

Adaptations (CBA)

Integration of Context Based Adaptations:

Pre-delivered CBA dimensions:

Examples of per-delivered dimension usages:

Category used for BP category specific attributes like name and e.g. birth date / marital status for persons

Country is used for country specific address layout

CBA schema can be reused and enhanced with custom-defined dimensions

Delivered CBA schema can be substituted by custom-defined schema

Customizing Configure Properties of Change Request Step, if the CBA is not used in the UI Configuration


Function in Detail Entry Points / User Interface: Side Panel - Integrate Additional Information

Customers can easily add content to the Side Panel

Reuse of generic component Business Context Viewer (BCV)


Function in Detail Entry Points / User Interface: Lean Request for ERP Vendor

Lean Request for ERP Vendor

Goal: Enable all users to submit a

request, also users w/o ERP knowhow

Very easy UI to request a new ERP

Vendor

All data on one screen, navigation to

detail screens not required

Only the most important data is visible

Name / address

Bank Details

Company Code / Purchasing organization

UIBBs for Identification Numbers and Tax

Numbers can be added by configuration

BP role derived in the background

Account group derived in the

background based on standard BP Grouping and

assigned account group


Function in Detail Entry Points / User Interface: Governance Scope - Deactivate Entity Types / Fields

Governance Scope

Only parts of the data model shall be

put under governance

Entity types / fields can be excluded

from governance

Excluded entity types / fields

can not be changed within a Change

Request

are displayed only within the UI; can be

suppressed by changing the UI

configuration

can still be loaded to Active Area but not

via CR / Staging

Can easily be re-added to the governance

scope afterwards


Function in Detail Entry Points / User Interface: WF-Step Dependent Configuration Enables Flexible

UI / Process Design

UI Configuration

Provide different User Interface per WF-

step based on task / knowhow of the user

Example: Lean Request UI

Validations

Enable or disable checks / enrichments

Example: Switch off required field check

and address validation in Lean Request

UI

Field properties

Set some data to read-only

Example: Processor for company code

0001 can only maintain these fields

Step 1 - Request

Simple UI Selected checks

and enrichments

Step 2 - Check

Expert UI Extended checks

and enrichments

Step 3 - Approve

Approver UI Full Checks


Function in Detail Multiple Customer / Vendor Assignments

Business Case

Already today customers have to establish multiple ERP Customers and ERP Vendors for

the same Business Partner

Reasons are e.g.:

Customer or Supplier is treated differently within several business units of the same company code

For special business processes information like communication data, bank details or even names etc.

have to be maintained differently

Option to allocate multiple ERP Customers and multiple ERP Vendors to one Business

Partner

Customer

(Business Partner)

ERP

Customer

ERP

Customer

ERP

Customer

PO CC CC SA PO CC CC SA PO CC CC SA PO CC

Supplier

(Business Partner)

ERP

Vendor

ERP

Vendor

ERP

Vendor

CC PO PO CC CC PO PO CC CC PO


Implementation

Multiple ERP Customers and

ERP Vendor can be assigned to

one MDG Business Partner)

ERP Customer and ERP Vendor

specific data including sales /

purchasing organization and

company code data can be

maintained per assigned ERP

Customer or ERP Vendor

Deviations of central fields like

e.g. Name 3, Telephone number and Bank details can be maintained within a

specific UI

Small project specific implementation required

Function in Detail Multiple Customer / Vendor Assignments


Function in Detail Client Maintenance for Customers: Process Steps

MDG Hub

Client Maintenance

Requestor Local Hits

Search from client system

1. Requestor searches customers

/ suppliers from the client

2. Hit list contains entries of the

hub and the client

Change on the client system

After copying, requester can

process changes on the

customer / supplier copied from

the hub

Hub Hit

Copy from hub to client system

1. Hit list contains entry currently

only available on hub system

2. Requestor needs this customer

/ supplier also on the client

3. Requestor requests copying

the same from the hub to the

client

Transfer changes to hub

1. The changes done on client

are then transferred to the hub

2. Governance workflow is

executed

3. After final approval the

changes are replicated to all

client systems


Function in Detail Client Maintenance: Possibility to Search on HUB and Copy From HUB

MDG Hub

Client Maintenance

Search from client system

1. Requestor searches customers

from the client

2. Hit list contains entries of the

hub and the client

Copy from hub to client system

1. Requestor requests copying

the same from the hub to the

client


MDG Hub

Client 1 Client 2

Client 4

1

2 2

2 2

1

2

Maintain data on MDG Hub

Replicate data to client systems

Maintenance on MDG Hub

MDG Hub

Client 1 Client 2

Client 4 Client 3

4 4

4 4

1

2

Maintain data on Client 1

Replicate data to MDG Hub

Maintenance on Client

2

Client 3

1

3

4

Rework / approve data on MDG Hub


3

Function in Detail Client Maintenance: Maintenance on Hub & on Client can be Used in Unison


Function in Detail Search

Search First Step to Data Quality

Search is the initial action, if a user wants to do something with the data.

Several Flavors Supported via Search Provider Concept

Standard providers:

DB-based search

Enterprise Search

Fuzzy Search via BAS-DES (e.g. SAP BusinessObjects Data Quality Management)

Hana-based Search

Search

Change

Create Block/Unblock

Mark for Deletion

Mass Change


Function in Detail Search: Search Capabilities

Consistent search UI

containing all search

capabilities

Search methods easy to

configure, more search

methods can be added

Search for hits within

active and inactive data

Result can be

downloaded to Excel

Result list can be

personalized


Function in Detail Search: General Search Options

Drop-down lists of available

fields and operators for search

Search criteria can be saved

using a descriptive name for

quick and easy re-use

Fuzzy (error-tolerant)

search, if supported by

search provider

Add and remove

search parameter

(AND combination of

multiple parameters)


Function in Detail Search: Search Provider for Enterprise Search

Using Enterprise Search

with MDG provides

Free-text search across

many attributes

Attribute-based search in

specific fields only

Search active data only

to limit search to active

area

Fuzzy search checkbox to

enable error-tolerant

search mode

Free-text

Attribute-based

Advantages of using Enterprise Search (compared with database

search)

Free-text search

Fuzzy (error-tolerant) search


Function in Detail Data Quality: Duplicate Check, Validations, Address Enrichment

Prevent creation of duplicates for

increased effectiveness and efficiency

Checked early and embedded in the process

High detection quality of matching using

Enterprise Search or BusinessObjects DS

Validations

Re-use of existing validation logic in ERP

Custom validations can be modeled and

programmed (e.g. code lists, simple checks,

or modeled rules via BRF+)

Address Enrichment

Simple check and selection lists

Integration with content provided by

SAP BusinessObjects Data Services

Automatically adding Tax Jurisdiction Code

re-using existing interfaces / providers


Function in Detail Data Quality: HANA Search / Duplicate Check

All Business Partner data is stored within HANA

MDG running on HANA

MDG running on different DB connected side-by-side to HANA

Error Tolerant search

Hit List contains ranking and is sorted by ranking

Search types

Additional search provider within MDG with search fields / hit list

Search via drill down search


Function in Detail Data Cleansing Overview

Merge

Cleansing Case Identifying Duplicates

Create Cleansing case out of

Duplicate Check popup is planned

for a future MDG 7.0 SP


Function in Detail Data Cleansing Identifying Duplicates

Before creating a cleansing case and do the merging the data potential duplicates have to be identified.

Within MDG duplicates can be identified during

Search (within search result list)

Single object maintenance

(duplicate check)

Outside MDG Hand over cleansing case from

client system to MDG Hub Full data base scan (using external

tools) Identified potential duplicates will be

stored within a cleansing case for further processing


Function in Detail Data Cleansing Cleansing Case

Create a new cleansing case,

search and and assign

potential duplicates

Search cleansing case (also

can be used as worklist)

Check details of potential

duplicate records

Identify one Target Record Identify one or more Potential

Duplicates as well as No Duplicates

Start Cleansing and create a

Change Request


Function in Detail Data Cleansing Merge

During the merge process all

relevant data from Potential Duplicate records can be taken over to the Target Record.

This can be done using the keep

flag as well as using drag and drop

functionalities.

Hereby its possible to copy the data including all dependant data

(e.g. address including its

communication data).

In parallel it is also possible to edit

data of Target Record directly.

As result of the merge process a

workflow process will be triggered


Function in Detail Data Quality: Validations via BRFplus

For general information on how to work with BRFplus, see SAP Help Portal:

http://help.sap.com SAP NetWeaver Search for Business Rule Framework plus

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/9a/6b67ce7c26446483af079719edf679

/frameset.htm


Function in Detail Data Quality: Framework for Data Enrichment Spots

Data Enrichment Spots

Flexible framework to define

enrichment spots

Is used by SAP for e.g. Address

Validation / Enrichment and will be

used for further spots in future

Can be used by customers to define

further enhancement spots

(e.g. D&B services)


Function in Detail Data Replication Explicit Selection of Target Systems

Explicit Selection of Target

Systems

Enter required target systems explicitly

during CR processing

These target systems are considered

in addition to the target systems

automatically determined by the filter

logic


Function in Detail Data Replication Replication Status Information

Replication Status Information

Overview of replication status per

customer / supplier to all relevant

target systems

Status per target system

Green: OK

Yellow: OK, but answer from target

system still pending

Red: Error occurred

Detailed log per target systems

available


Function in Detail Process Analytics: Change Request Reporting

Change Request Reporting

Definition of SLA: Max. processing

time per change request type and

priority

Reporting on change request duration

and SLA compliance


Agenda

Introduction

Current Reality

Need for the Future


Architecture

Function in Detail




Supplier Management

Supplier Lifecycle Management (SLC)

Supplier Master Data Governance

Integration Scenarios Supplier Management With SLC and MDG

Supply Chain Product

Development

Finance Cost

Accounting

Procure-to-Pay Strategic

Sourcing &

Procurement

Create or change supplier Distribute validated supplier

Operational Procurement

Supplier Registration

Supplier Qualification

Supplier Evaluation

Supplier Classification

Supplier Order Collaboration

Supplier Development

Supplier Phase-out

Potential

Supplier

Approved as

Bidder Supplier Data

Approved as

Supplier


MDG Hub

SAP SLC Client 2

Client 4 Client 3

4 4

4 4

1

2

Maintain potential suppliers in

SAP-SLC only

Potential supplier becomes bidder

/ supplier in SAP-SLC send supplier to MDG Hub & create a

Change Request

2

1

3

4



3

MDG SLC Integration Scenario is available as of

MDG 6.1 and SLC 1.3

5 Changes to bidders / suppliers in

SLC or MDG

5

5

Integration Scenarios Maintain Potential Suppliers in SLC, Governance of Bidders / Suppliers in MDG


Operational ERP

MDG

SAP CRM Client 2

Client 4 Client 3

4 4

4 4

1

2

Maintain prospects & leads in CRM

only

Prospect becomes customer in

CRM replicate to Operational ERP via CRM-MW & create Change

Request in MDG

2

1

3

4

Rework / approve data on MDG

Hub


3

5 Changes to customers possible in

CRM and ERP via MDG

5

5

Integration Scenarios Prospects / Leads in CRM, Governance of Customers in Connected ERP


MDG Hub (BP data, Sales data,

Fin data)

SAP CRM

Client 4 Client 3

4

4 4

1

2

Maintain prospect / lead in CRM

only

Prospect becomes customer in

CRM replicate to connected ERP via CRM-MW and from there to

MDG Hub (2b), create CR in MDG

Hub

2

1

3

4

Rework / approve data on MDG

Hub

Replicate data from MDG Hub to all

connected client systems and from

ERP further to connected CRM (4b)

3

5

SAP ERP CRM-MW

2b

5

4b

5 Changes to customer possible in

CRM, MDG Hub, and ERP

5

Integration Scenarios Prospects / Leads in CRM, Governance of Customers in Separate MDG Hub (1)


MDG Hub (BP data, Sales data*)

SAP CRM

Client 4 Client 3

4

4 4

1

2

Maintain prospect / lead in CRM only

Prospect becomes customer in CRM

replicate to connected ERP via CRM-MW and to MDG Hub via SOA

service, create a change request in

MDG Hub

2

1

3

4


Replicate data from MDG to all

connected client systems and from

CRM further to connected ERP (4b)

3

5

6

SAP ERP MDG-C for Fin data

CRM-MW

4b

2

5

Customer can be enhanced by

financials data in ERP using MDG-C

6 Changes to customer possible in

CRM, MDG Hub, and ERP

6

6

Integration Scenarios Prospects / Leads in CRM, Governance of Customers in Separate MDG Hub (2)


Replication to SAP-CRM New replication scenario btw. MDG-C & SAP-CRM / SAP-ERP

MDG Hub (BP data, Sales data,

FIN data

SAP CRM

Client 4 Client 3

4

4

1

2

Maintain prospect / lead in CRM only

Prospect becomes customer in CRM

replicate to MDG Hub via SOA service, create a change request in

MDG Hub. CRM-MW is deactivated

for replication of BPs.

Related Sales Orders to be

replicated to ERP will run into error.

1

3

4


Replicate data from MDG to all

connected client systems including

CRM and Operational ERP

3

5

Operational

ERP

CRM-MW

(not for BPs)

2

5

Restart replication of related sales

orders.

4 4

MDG Hub between CRM and ERP

Order

Order Order

Order

2


Replication to CRM Extended replication data model btw. MDG-C and SAP-CRM

MDG 6.1: Business Partner data only

Business Partner data like general data, addresses, bank details, ID Numbers etc.

Business Partner Relationships like Contact persons, etc.

MDG 7.0: Sales specific data (additionally)

General customer data

Sales data

Shipping data

Pricing data

Tax Indicators

Partner Functions

MDG Hub

SAP CRM


Global MD Hub

ERP 1

Client

1

2

4

1

2

Maintain global data on the Global MD Hub

Replicate global data to local ERP systems and other client systems

Client

3

4

Maintain local ERP data on ERP systems

Replicate global and local data to connected client systems

MDG

ERP 2

MDG

Client

Client

Client

3

3 4

MDG


Maintain ERP Specific Data on Local ERP Systems


Agenda

Introduction

Current Reality

Need for the Future


Architecture

Function in Detail




Benefit From the Solution Need for MDG-S and MDG-C: Solutions Provided

Enable All UsersEnable All UsersEnable All Users

Manage LifecyclesManage Lifecycles

Compose xApps

Texas Instruments: Reduced the time to partner

Carl Zeiss: Reduce time and cost to integrate new

General Electric: 400-500 new launches, better

Compose xApps

Texas Instruments: Reduced the time to partner

Carl Zeiss: Reduce time and cost to integrate new

General Electric: 400-500 new launches, better

Manage ProcessesManage Processes

Clean Master DataClean Master Data

Single Point of Access

(Role Based) via Portal

or NWBC

Workflow

based

process Flexible &

Adaptable

Duplicate Check, Data

Validation & Enrichment,

Merging & Cleansing (planned)

Process Analytics

Data analytics

(planned)

Change Documents,

Change Request Process

integrated into UWL &

Workflow

Monitor for Data Replication,

ID mapping, key mapping &

client side ID mapping

Single Entry

Point to

maintain data

Standardized

Process to

control data

changes

Standardized

Tools for

ensuring data

quality

Data Flow

Transparency

within system

landscape

Get a Snapshot

of all the

supplier related

activities

Transparency on the

data changes done

(Who, When, What,

Why)

Solution

Need


Common Services

Basic Principles

Solution Strategy

SAPs understanding of a state-of-the-art master data governance solution

Ensure

Master Data

Governance

Deliver process-centric solution

Workflow closely integrated to a framework for defining business rules

Full Integration to SAP Systems and integration services for non-SAP

Deliver roles on a web based UI

Deliver a Data Model proven by several applications & industries

Reuse of existing processing logic

Out-of-the box data replication mechanisms

User-centricity : Central work center for the maintenance of materials

Governance: Change requests with built-in approval process

Workflow: standardized but flexible processes incl. rules management and tracking

Architecture: Staging area to maintain inactive versions of material data

Search & Display

Create, Change, Mass Change, Mark for Deletion

Work lists (My Change Request, Display Change Requests, Change Documents)

Duplicate Check

Key- and Value-Mapping

Data Replication

File Upload / Initial Load

Extensibility of Data Model & User Interface

Deployment on top of operational ERP or as standalone hub


Benefits through SAP Master Data Governance

Up-front, central creation of master data

enables high data quality and leads to

significant business improvements.

Out-of-the-box, process-centric applications

provide centralized governance for master

data domains such as financial data, supplier

data, customer data, material data.

Native integration with SAP Business Suite

using existing business logic and

infrastructure leads to low TCO.

SAP Master Data Governance provides

flexibility, from configurable workflows and

extensible data models, up to custom built

applications.


Further Readings and Links MDG-S and MDG-C EhP6

SAP Master Data Management on sap.com

http://www.sap.com/mdm

SAP Master Data Governance on sap.com

http://www.sap.com/solutions/enterprise-information-management/master-

data-management/master-data-governance

SAP Developer Network and related communities

http://www.sdn.sap.com/irj/sdn/mdm


2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or

warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing

herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.