master data governance on s/4hana 1909...

PUBLIC

September, 2019

Master Data Governance on S/4HANA 1909Consolidation

2PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Agenda

1. Overview and use cases

2. Consolidation process flows

▪ Consolidation of source records

▪ Consolidation of active records

3. General functions

4. Integration scenario: Cloud for Customer (SAP C4C)

Overview and Use Cases


Typical approaches to master data managementCentral governance and distribution / decentral ownership and consolidation

Systems under central governance

LoB customer LoB procurement Other LoB

Systems not under central governance

Legacy systems Reporting and analytics Business networks

LoB finance LoB production

Cloud

SAP Master Data Governance

– central governance

Create master data in line with business

processes (such as integrated product

development or supplier management)


– consolidation

Consolidate master data into a single view

for accurate analytics and operational

insight (continuously or on request, such as

for initial load or mergers and acquisitions)

Enterprise master data

All typical approaches are supported: central governance with distribution, decentralized ownership with consolidation, data quality monitoring with remediation


– data quality management

Manage master data quality by defining,

enforcing, monitoring, and improving quality


SAP Master Data Governance One single application for enterprise master data management

ENTERPRISE

MASTER DATA

Order to Cash Procure to Pay Design to OrderService &

MaintainAcquire to Retire

All Domains and Processes

All Use Cases and Implementation Styles

Customers Finance Vendors Materials Products Assets Location

Continuous consolidation for analytical purposesEnsure data consistency using consolidation for analytical use cases, e.g., global spend reporting

Consolidation for initial load before central governanceEnsure data correctness and accuracy using consolidation run before starting central governance

Consolidation for M&AEnsure data consistency using consolidation runs every time it comes to M&A process while continuously running central governance

Central governance onlyEnsure clean data at the point of creation or change

Coexistence hybrid approachDeliberately keep some parts under local ownership with continuous consolidation and some parts under central governance

Get data clean

Get data clean

Keep data clean2

1

Get data clean

Keep data clean

Keep data clean

Get data clean

Keep data clean


Mass Processing with MDG

Domain Coverage and Choice of Governance

Domains

Business Partner, including customer and vendor (*)

Business Partner Relationships (*)

Material Master (*)

Custom Objects (**)

Choice of Governance Options

Can be used with or without central governance

Choice: activation with change request

Choice: use of MDG, central governance validations

(*) for detailed information about the coverage on table-level, see IMG activity Configure Process Models.

Extensibility is supported.

(**) based on single database table, MDG active area (flex) not supported.

Consolidation of Source Records


Master Data Consolidation of Source RecordsProcess Flow

MatchInitial CheckData Load Validate Calculate Best

RecordActivate

Import data from

file

Use csv or xlsx file

format to upload

source records

External load

using BP SOAP

service

View loaded data

and check data

quality based on

backend

customizing or

own BRFplus

rules

Validate against

Central

Governance

checks (BAdI,

BRFplus)

Find duplicates

based on

matching rules

Review match

result

Create Best

Records based on

approved match

groups

Review best

record calculation

result

Activate

consolidated

master data for

analytical or

operational use

Option to activate

directly, or

indirectly triggering

post processing

using central

governance

Validate best

records against

backend

customizing to

verify whether

records can be

activated

Validate against

Central

Governance

checks (BAdI,

BRFplus)

Standardize

Validate and

enrich data (For

example,

address

validation)

Usage of

BRFplus for own

standardization

and enrichment

capabilities


Import App:

• Upload data in CSV or Open Office XML

format

• Checks for conflicts in source data tables

• Option to start consolidation process directly

• Manage import app

Other Import Options

• Use any ETL tool to fill source tables for consolidation (For example: SAP Smart Data Integration)

• Use Business Partner service to fill source tables and create a consolidation process


RecordActivate Standardize

Master Data Consolidation of Source RecordsData Load


Master Data Consolidation of Source RecordsInitial Check/Validation



Check correctness of loaded records

• Validation of records against backend customizing to verify whether records can be

activated (in combination with central governance validation also against BAdI and BRFplus

checks)

• Process-step specific KPI’s visualized: status of loaded Single Records

Process-step specific KPI’s

visualized


SAP HANA smart data quality (BP model only) transforms data to common

format to enable matching. Includes out-of-the-box address validation and

address standardization.

Non SAP HANA-based standardization option possible:

• SAP Data Services, called using BAS interface (BP model only)

• Standardization using BRFplus

Master Data Consolidation of Source RecordsStandardize data




visualized


SAP HANA Fuzzy Search ensures high detection quality in search and matching based on customer

specific rule sets

SAP HANA smart data quality (BP model only) provides batch matching features to identify duplicate

data

Non HANA-based matching

option possible:

• SAP Data Services, called using

BAS interface (BP model only)

• Simple database matching

(material model only)

Process-step specific

KPI’s visualized

Master Data Consolidation of Source RecordsMatching data




Match review to verify the

correctness of identified

duplicates and provide the

appropriate match groups for

subsequent calculation of

best record.

• Approve or reject match

groups

• Delete or split single or

multiple records

Master Data Consolidation of Source RecordsMatching data




Create best record according to survivorship rules

• Survivorship rule types on table level: source system reliability, recency, BRFplus

• Survivorship rule types on field level: completeness

Master Data Consolidation of Source RecordsCalculating the best record




Check correctness of new, best, and updated records

• Validation of records against backend customizing to verify whether records can be

activated (in combination with central governance validation and also against BAdI and

BRFplus checks)

• Process-step specific KPI’s visualized: status of new Single Records, new Best Records,

and status of Updates


visualized

Master Data Consolidation of Source RecordsValidating data




Provide consolidated data for

analytical or operational use, or

initiate governance. Activation type

can be flexibly configured:

• Direct activation. Typically for

analytical use cases or correct

records during initial load

• Activation initiating central

governance with change request.

Typically for incorrect records to be

corrected using change request

• No Activation. Typically for incorrect

records to be corrected and loaded

again

Master Data Consolidation of Source RecordsActivating data



Consolidation of Active Records


Innovations:

▪ In addition to consolidation and de-duplication when loading

new master data, de-duplication is also available for active

master data records in central governance activities. This

enables customers to ensure superior master data quality

and lead to better business outcomes.

Business value:

▪ Drive better business outcomes with superior master data

▪ De-duplicate your master data during regular clean-up

activities

Master Data Consolidation of Active Records


Master Data Consolidation of Active RecordsProcess Flow

Enter search

criteria to select the

master data

objects that you

want to check for

duplicates

Select

Find duplicates

based on matching

rules

Review match

result

Match

Create Best

Records based on

approved match

groups

Review best record

calculation result

Validate

Validate best

records against

backend

customizing to

verify whether

records can be

activated

Activate

Activate the data

and adapt the

duplicate records

according to the

process strategy

Calculate Best

Record


▪ New Process Goal: Consolidation of Active

Records

▪ Strategies for Consolidation of Active Records (as

part of the process template)

Improve best record

− Define which record will be improved

− Relationship “is replaced by” is created for

the best record and each duplicate record

− Optional: Set flag for duplicate records (For

example: central block)

Remove duplicates

− Set archiving flag/deletion flag on MDG Hub

side for each duplicate record

− Move key mapping(s) from duplicate records

to the best record

Master Data Consolidation of Active RecordsProcess Goal and Strategies


Consolidate Active RecordsSelection

▪ Possibility to do a full

database scan and

search for duplicates

▪ Select a subset of active

records and search for

duplicates

Strategy: Improve Best Record

0Selected

Records

Selection criteria for active records:

• All selectable fields are available

• Selection of multiple fields possible


Consolidate Active RecordsMatch Review and Match Decision

Results (Match Review) ▪ The match decision on match

group and record level is

stored and used in the

subsequent Consolidate Active

Records processes

▪ The match review UI provides

the following information:

▪ Groups already defined in

previous processes with the

best record decision

▪ Rejected records

▪ Previous duplicate strategy

▪ Match (Improve Best)

▪ Improve (Improve All)


Master Data Consolidation of Active RecordsStrategy: Improve Best Record

MDG Hub

Key mapping (MDG Hub <-> Client)BP A <–> BP 100BP B <–> BP 200

Client System

Co

nso

lidat

e A

ctiv

e R

eco

rds

(A=B

)

Re

plic

atio

n (

MD

G H

ub

<->

Clie

nt)

Business Partner A

Company ABC

Business Partner B

Company ABC

Data A Data B Data C

Data A Data B Data D

Business Partner A

Company ABC

Business Partner B

Company ABC


Business Partner 100

Company ABC


Company ABC


Data A Data B Data C Data D



BPRel: Is Replaced by BP A

Blocking Flag‘s

BPRel: Replaces BP B

BPRel: Is replaced by BP A

Optional: Set blocking flags

BPRel: Is replaced by BP 100

Optional: Set blocking flags


BPRel: Replaces BP 200

Consolidate Active Records


Master Data Consolidation of Active RecordsRemove Duplicates


MDG Hub

Key mapping (MDG Hub <-> Client)BP A <–> BP 100 & BP 200

Client System

Co

nso

lidat

e A

ctiv

e R

eco

rds

(A=B

)

Re

plic

atio

n (

MD

G H

ub

<->

Clie

nt)

Business Partner A

Company ABC

Business Partner B

Company ABC



Business Partner A

Company ABC

Business Partner B

Company ABC



Company ABC


Company ABC




Data A Data B Data C Data A Data B Data C Data D Data A Data B Data C Data D


Remove duplicate (Set flag for deletion/archiving)

Consolidate Active Records

General Functions


General FunctionsWorklist with all consolidation processes

Overview of all

processes including

status

Navigation to process

details

Ability to create and

delete processes

Filter capabilities

Process monitoring, for

example, long-running

activation of process

with high volume of data


General FunctionsProcess UI to track the process

Show the progress of a

consolidation process

See results for each process

steps (chart or table)

Drill-down into results


General FunctionsShow data of all tables

Show content of all

affected tables in each

process step

Navigate between

tables using tabs


General FunctionsShow changes

Show all changes of a

record

Drill-down into field

level information

Available for all related

tables


General FunctionsRollback

Clear result data after a

process step

Rollback to any step in

the process

Re-run process steps

(possibility to change

settings for following

steps)


General FunctionsConfiguration of steps during runtime

Step configuration

during runtime

Settings from process

template can be

adjusted


General FunctionsRemove records / split process

If a process is stopped for

review, you can:

Remove records from

process with several

options, for example,

records with errors into

separate process for later

processing

Removal can be triggered

from table view or using

drill-down from chart view

Also available as separate

process step is to

automatically remove

records in the background

(Filter and Remove step

type = FAR)


General FunctionsFilter and Remove (FAR adapter)

Automatically removes records or move

records into a new duplicate process

After matching: move open match groups

After best record calculation: move specific

groups of records

After validation: move records with warnings

or errors

▪ Remaining records can be processed directly


General FunctionsEdit capabilities

Replace field values for

selected records

Clear field values for

selected records


General FunctionsShow messages

Show messages for

each step

Navigate into affected

records


General FunctionsAudit Trail

All activities on process-

level (For example,

change of configuration,

continue the process,

roll-back the process)

are tracked

Audit trail can be

displayed in the process

UI

Drill-down into details

(For example, match

review)


General FunctionsFiori UI personalization

Personalization for showing

and hiding fields

Define number of maximum

hits in table view (performance

relevant)

Table views can be saved as

variants


General Functions

Using service to trigger consolidation process (integration scenario)

LoyaltyProgram

ServiceCenter

SocialMedia

SAP CRM Other SystemsSAP C4C

Match Review for

“open” Match Groups

Replicate data/key

mapping back to

client systems

3rd partyCRM

Calculate

Best RecordMatchStandardize ActivateValidate

SAP MDG, Consolidation

MDG Central Master

Data

Client Systems

“Approved” Match Groups are

processed automatically

Web Service

(SOA)

Integration using Web

Service call

(Create and Change)


General Functions

Configure integration scenario

Configure Business Partner Service:

- Define consolidation template (for Creation and Change case)

- Leave Storage field on Not Defined


General FunctionsAdditional features 1/2

• Review UI for Best Record Calculation

Shows how a best record has been built (based on which rules)

Possibility to edit calculated data

Delete entries (For example, duplicate addresses)

Define upper threshold for Fuzzy matching and matching using BAS adapter

Match groups with matches above upper threshold will be approved automatically

Match groups with matches below upper threshold are open and have to be approved/rejected

manually

Records within open match groups will be processed separately (as single records)

Integration of BRFplus

Standardization

Best Record Calculation

Validation (Central Governance rules can be applied)

Update step to change/enrich data (on table level)


General FunctionsAdditional features 2/2

• Retention time

Possibility to keep the process data (for a specific time frame) after the last process step for verifications

Support of multiple assignments for Business Partner

• Key and value mapping

Standardization adapter to transform incoming source data using Data Replication Framework (DRF) mapping tables

• Enable 4-eyes principle / separation of duties

Defines who is allowed to continue with the next process step (based on customizing)

Enable re-validation functionality after making changes in validation step

After changing the data within validation step data can be validated again using an additional validation step

• Multiple re-validation steps are possible

• Within rollback functionality it is possible to rollback to a specific validation step


Additional Apps for ConsolidationImport Data for Consolidation

▪ This app can be used to import data into the

source data

▪ File formats: Office Open XML, Microsoft Excel

or CSV file.

▪ Use data packages to divide your records up

for organizational purposes.

▪ The data will be validated and a consolidation

process can be started immediately or later.

▪ The imported data can be managed using

these apps:

– Manage Imports for Consolidation

– Manage Source Data


Additional Apps for ConsolidationConfigure Matching

▪ App to configure matching rules for the

new SAP HANA Fuzzy matching adapter

▪ Pre-delivered match configurations for

Business Partner and Product

▪ Possibility to create, change, copy and

delete match configurations

▪ Within a match configuration multiple

rules can be defined, existing attributes

from the model assigned and configured


Additional Apps for ConsolidationTrack Changes

▪ Auditing of active area

change documents

triggered by a

consolidation process

▪ Select changes using

object ID (BP number,

material number),

process ID, or change

date

Integration Scenario:

Cloud for Customer (C4C)


Customer data can be maintained in C4C or MDG-C because bi-directional replication is supported by

means of SOA services.

SAP recommends to use best-practice integration scenarios with the goal to

▪ Optimize master data quality by using MDG processes like Consolidation and Central Governance

▪ Make sure customer master data is in sync among C4C, MDG, and operational ERP system

▪ Enable the flow of transactional data (such as sales orders) between C4C and ERP system

Best-practice integration scenarios are delivered as of

▪ MDG 9.1 and MDG 9.2 (Prerequisite is EHP8SP10)

▪ MDG on S/4HANA 1709 FPS2 and MDG on S/4HANA 1809

More information about scenarios and system configuration in SAP Help Portal for MDG

Integration Scenario: Cloud for Customer (SAP C4C)Summary

https://help.sap.com/viewer/6d52de87aa0d4fb6a90924720a5b0549/1809.002/en-US/458ae2b93df24a0993148041fdc8b2f3.html


New customer from C4C

– No duplicate found in MDG

– Duplicate found in MDG: BP not yet in C4C

– Duplicate found in MDG: BP already in C4C

Change customer in C4C

Create customer in MDG

Change customer in MDG

Merge two active customers in MDG

Integration Scenario: Cloud for Customer (SAP C4C) Scenarios, Overview


MDG Hub

BP 5000: ERP 2000

BP 5001: ERP 2001

C4C 1000

5

1

2

Create new customer DEF Corp. in C4C;

business with new customer can start at once

Send customer to MDG using SOA Service

4

Replicate customer data from MDG Hub to

all connected client systems.

3

Integration Scenario: Cloud for Customer (SAP C4C)Scenario, New customer from C4C and no duplicate found in MDG

Start Consolidation. No match found, so

prepare for adding customer.

Activate data on MDG Hub, add new customer

as well as Key Mapping for MDG → C4C.

C4C ERP

1

2

3

4

5 5

BP 5000, ABC Corp.

BP 5001, DEF Corp.

BP 2000, ABC Corp.

BP 2001, DEF Corp.BP 1000, DEF Corp., MDG 5001

Consolidation

6

6

7

Replicate key mapping to all client systems

Store ERP number of customer in C4C for

proper replication of transactional data

6

7

Sales Orders

javascript:void(0);

javascript:void(0);

javascript:void(0);


5

1

2

Create new customer DEF Corp. in C4C

business with new customer can start at once

Send customer to MDG using SOA Service

4

Replicate customer data from MDG Hub to

all connected client systems

3

Integration Scenario: Cloud for Customer (SAP C4C)Scenario, New customer from C4C and Duplicate found in MDG (BP already in C4C)

Start Consolidation. Match found against BP

in MDG/C4C, merge data.

Activate data on MDG Hub, enhance Key

Mapping for existing customer resulting in two

mappings towards C4C.

C4C ERP

MDG Hub

1

2

3

4

5 5

BP 5000, ABC Corp.

BP 5001, DEF Corp.

BP 2000, ABC Corp.

BP 2001, DEF Corp.

6 Replicate key mapping to all client systems

BP 1000, DEF Corp., MDG 5001

BP 1001, ABC Corp., MDG 5000

BP 1002, DEF Corp., MDG 5001

6

Consolidation

6

7 C4C detects duplicate customers, starts

local merge, and marks superfluous

customer as inactive (only if not yet

replicated to ERP)

7

BP 5000: ERP 2000

C4C 1001

BP 5001: ERP 2001

C4C 1000

BP 5000: ERP 2000

C4C 1001

BP 5001: ERP 2001

C4C 1000

C4C 1002

javascript:void(0);

javascript:void(0);

javascript:void(0);

Thank you.

© 2019 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its

distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or

warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.

The only warranties for SAP or SAP affiliate company 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or

any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,

and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and

functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason

without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or

functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ

materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they

should not be relied upon in making purchasing decisions.

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

trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names

mentioned are the trademarks of their respective companies.

See www.sap.com/copyright for additional trademark information and notices.

www.sap.com/contactsap

Follow us

https://www.sap.com/copyright

https://www.sap.com/registration/contact.html

https://www.linkedin.com/company/sap

https://www.youtube.com/user/SAP

https://twitter.com/sap

https://www.facebook.com/SAP

master data governance on s/4hana 1909...

Documents