SAP Master Data Governance, Consolidation

Master Data Governance on S/4HANA
2021 Consolidation
November 2021
PUBLIC
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)
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Overview and Use Cases
Typical approaches to master data management
Central governance and distribution / decentral ownership and consolidation
LoB customer LoB procurement LoB finance LoB production Other LoB
Systems under central governance

SAP Master Data Governance
– central governance
Create master data in line with
business processes (such as integrated
Enterprise product development or supplier
SAP Master Data Governance master data management)
– consolidation
Consolidate master data into a single SAP Master Data Governance
view for accurate analytics and operational – data quality management
insight (continuously or on request, such Manage master data quality by defining,
as for initial load or mergers and enforcing, monitoring, and improving
acquisitions) quality
Systems not under central governance
Legacy systems Reporting and analytics Business networks Cloud
All typical approaches are supported: central governance with distribution, decentralized ownership with consolidation, data quality monitoring with remediation
SAP Master Data Governance
One single application for enterprise master data management
All Domains and Processes

Service &
Order to Cash Procure to Pay Design to Order Acquire to Retire
Maintain
ENTERPRISE
MASTER DATA
Customers Finance Vendors Materials Products Assets Location
All Use Cases and Implementation Styles

Continuous consolidation for analytical purposes
Get data clean
Ensure data consistency using consolidation for analytical use cases, e.g., global spend reporting
1 Get data clean

Consolidation for initial load before central governance
Ensure data correctness and accuracy using consolidation run before starting central
2 Keep data clean
governance
Get data clean Consolidation for M&A

Ensure data consistency using consolidation runs every time it comes to M&A process while
Keep data clean
continuously running central governance
Central governance only

Keep data clean
Ensure clean data at the point of creation or change
Get data clean

Coexistence hybrid approach
Deliberately keep some parts under local ownership with continuous consolidation and some
parts under central governance
Keep data clean

Consolidation 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 Records
Process Flow
Calculate Best
Data Load Initial Check Standardize Match Validate Activate
Record
Import data from View loaded data Validate and Find duplicates Create Best Validate best Activate
file and check data enrich data (For based on Records based on records against consolidated
quality based on example, matching rules approved match backend master data for
Use csv or xlsx file backend address groups customizing analytical or
format to upload customizing or validation) Review match operational use
source records own BRFplus result Review best Validate against
rules Usage of record calculation Data Quality Option to activate
External load BRFplus for own result Rules directly, or
using BP SOAP Validate against standardization indirectly triggering
service Central and enrichment post processing
Governance capabilities using central
checks (BAdI, governance
BRFplus)

Data Load
Calculate Best
Record
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

Initial Check/Validation
Calculate Best
Record
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

Standardize data
Calculate Best
Record
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
Process-step specific KPI’s

visualized

Matching data
Calculate Best
Record
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

Matching data
Calculate Best
Record
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

Calculating the best record
Calculate Best
Record
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

Validating data
Calculate Best
Record
Check correctness of new, best, and updated records

• Validation of records against backend customizing and Data Quality Rules to verify
whether records can be activated
• Process-step specific KPI’s visualized: status of new Single Records, new Best
Records,
and status of Updates

Activating data
Calculate Best
Record
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
Consolidation of Active Records
Master 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
Process Flow
Calculate Best
Select Match Validate Activate
Record
Enter search Find duplicates Create Best Validate best Activate the data
criteria to select the based on matching Records based on records against and adapt the
master data rules approved match backend duplicate records
objects that you groups customizing to according to the
want to check for Review match verify whether process strategy
duplicates result Review best record records can be
calculation result activated

Master Data Consolidation of Active Records
Process Goal and Strategies
 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

Consolidate Active Records
Selection
 Possibility to do a full
database scan and
0
Selected
search for duplicates
Records
 Select a subset of active
Strategy: Improve Best Record
records and search for
duplicates
Selection criteria for active records:

• All selectable fields are available
• Selection of multiple fields possible

Consolidate Active Records
Match 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)

Strategy:
RecordsImprove Best Record
Client System
MDG Hub Consolidate Active
Business Records
Partner A Business Partner A Business Partner 100
Company ABC Company ABC Company ABC
Replication (MDG Hub <-> Client)

Consolidate Active Records (A=B)
Data A Data B Data C Data A Data B Data C Data D Data A Data B Data C Data D
Data Data Data C
A B BPRel: Replaces BP B BPRel: Replaces BP 200
Business Partner B Business Partner 200

Business Partner B
Company ABC Company ABC
Company ABC
Data A Data B Data D Data A Data B Data D
DataA
Data Data
Data B Data
Data DD
A B BPRel: BPRel: Is rep laced by B P 100
BPRel:IsIsreplaced by BP
Replaced byABP A
Optional: Set blocking flags Optional: Set blocking flags
Blocking Flag‘s
Key mapping (MDG Hub <-> Client)
BP A <–> BP 100
BP B <–> BP 200
Remove
RecordsDuplicates
Client System
MDG Hub Consolidate Active
Business Records
Partner A Business Partner A Business Partner 100
Company ABC Company ABC
Replication (MDG Hub <-> Client)

Company ABC
Consolidate Active Records (A=B)

Data A Data B Data C Data
Data AA Data
Data BB Data
Data CC Data
Data DD Data A D ata B Data C Data D
Data Data Data C Data Data B Data C
A B A
Business Partner B Business Partner B Business Partner 200

Company ABC Company ABC Company ABC
Data
DataA Data
DataB Data
DataDD Data A Data B Data D Data
DataAA D ata B B
Data Data CData
Data
DD
A B Remove duplicate
(Set flag for deletion/archiving)
Key mapping (MDG Hub <-> Client)

BP A <–> BP 100 & BP 200
General Functions
General Functions
W orklist 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 Functions
Process 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 Functions
Show data of all tables
 Show content of all
affected tables in each
process step
 Navigate between
tables using tabs

General Functions
Show changes
 Show all changes of a

record
 Drill-down into field
level information
 Available for all
related
tables

General Functions
Rollback
 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 Functions
Process Step Scheduling
• Schedule the execution of a

process step at a predefined
date/time
• Prevents the execution of long

running jobs with high system
load during business time
• Allows the activation of

changed/created master data
at a given point of time (e.g. 1st
of January)

General Functions
Configuration of steps during runtime
 Step configuration
during runtime
 Settings from process
template can be
adjusted

General Functions
Remove 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 Functions
Filter 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 Functions
Edit capabilities
 Replace field values for

selected records
 Clear field values for
selected records

General Functions
Show messages
 Show messages for

each step
 Navigate into affected
records

General Functions
Audit 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 Functions
Authorization Concept Based on Process Step
Best
 Possibility to control authorizations Matching
Record Calc.
Validation Activation
Auth. Group A Auth. Group B
and activities per process step
 Activities, which can be managed User 1 User 2
Authorizations Authorizations
 Change data (including remove Auth. Group A Auth. Group B
records, approve/reject match Activity: Change Activity: Confirm
groups)
 Continue process Examples:
 Rollback process In step Matching only users with Authorization Group A can
 Change step configuration execute special activities, e.g. approve match groups.
 Adjust configuration In step Validation only users with Authorization Group B can
continue/confirm this process step.

General Functions
Fiori 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)
Client Systems
Loyalty Service Socia l party

3rd
Program Center Media CRM
SAP C4C SAP CRM Other Systems

Replicate data/key
mapping back to
client systems
Integration using Web
Web Service Service call
(SOA) (Create and Change)
SAP MDG, Consolidation
Calculate
Standardize Match Validate Activate
Best Record MDG Central Master
Data
Match Review for “Approved” Match Groups are
“open” Match Groups processed automatically

General Functions
Configure integration scenario
Configure Business Partner Service:

- Define consolidation template (for Creation and Change case)
- Leave Storage field on Not Defined

General Functions
Additional 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 Functions
Additional 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 / two-man rule / 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 Consolidation
Import Data for Consolidation
 This app can be used to import data into the

source data
 File formats: Office Open XML 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

Configure 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

Track 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)
Integration Scenario: Cloud for Customer (SAP C4C)
Summary
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

Scenarios, Overview
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

Scenario, New customer from C4C and no duplicate found in MDG
BP 2000, ABC Corp.

1 Create new customer DEF Corp. in C4C;
BP 1000, DEF Corp., MDG 5001 BP 2001, DEF Corp. business with new customer can start at
1 2 once
Sales Orders
Send customer to MDG using SOA Service
C4C 7 ERP 3
Start Consolidation. No match found, so
prepare for adding customer.
4
6 5 Activate data on MDG Hub, add new
5 6
2 customer
5 as well as Key Mapping for MDG 
BP 5000, ABC Corp.
BP 5000: ERP 2000 C4C.
BP 5001: ERP 2001 6
BP 5001, DEF Corp. C4C 1000 Replicate customer data from MDG Hub
7 to all connected client systems.
MDG Hub 4
Replicate key mapping to all client
3
systems
Consolidation
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC Store ERP number of customer in C4C 50
Scenario, New customer from C4C and Duplicate found in MDG (BP already in C4C)
1 Create new customer DEF Corp. in C4C
BP 1000, DEF Corp., MDG 5001 BP 2000, ABC Corp.
BP 1001, ABC Corp., MDG 5000
business with new customer can start at once
BP 2001, DEF Corp.
BP 1002, DEF Corp., MDG 5001
2 Send customer to MDG using SOA Service
1
C4C ERP 3 Start Consolidation. Match found against BP
7 in MDG/C4C, merge data.
4 Activate data on MDG Hub, enhance Key
Mapping for existing customer resulting in
5 6 6 5
two mappings towards C4C.
2 BP 5000: ERP 2000
BP 5000:C4C
ERP1001
2000 5 Replicate customer data from MDG Hub
BP 5000, ABC Corp.
BP 5001: ERP
C4C2001
1001 to all connected client systems
C4C 1000
BP 5001:
BP 5001, DEF Corp. C4C
ERP1002
2001 6 Replicate key mapping to all client
C4C 1000
systems
MDG Hub 4 7
3 C4C detects duplicate customers, starts
Consolidation local merge, and marks superfluous
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
customer as inactive (only if not yet 51
Learn more
about SAP Master Data Governance
► SAP Road Maps

(direct link: SAP MDG in Roadmap Explorer)
► SAP Community
► SAP User Groups
► SAP Customer Connection

(Projects: MDG 2018, MDG 2019, MDG
2020, MDG 2021/22)
► SAP Master Data Governance on

SAP.com
► SAP Master Data Governance

Community
(recent strategy updates:
#mdgupdates2021)
► SAP Master Data Governance

Application Help
Thank you.
Contact information:
SAP Product Management
Join online:
MDG Community Network: https://www.sap.com/community/topics/master-data-governance.html
Follow us
www.sap.com/contactsap
© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any formor for any purpose w ithout the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed w ithout 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, w ithout representation or
w arranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions w ith respect to the
materials. The only w arranties for SAPor 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 w arranty.
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
w ithout notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, c ode,
or functionality. All forw ard-looking statements are subject to various risks and uncertainties that could cause actual results to
differ materially fromexpectations. Readers are cautioned not to place undue reliance on these forw ard-looking statements, and
they should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as w ell 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.

SAP Master Data Governance, Consolidation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Master Data Governance, Consolidation

Uploaded by

Copyright:

Available Formats

Master Data Governance on S/4HANA

1. Overview and use cases

2. Consolidation process flows

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

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

Systems under central governance

Legacy systems Reporting and analytics Business networks Cloud

All Domains and Processes

All Use Cases and Implementation Styles

1 Get data clean

Get data clean Consolidation for M&A

Central governance only

Get data clean

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Choice of Governance Options

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Other Import Options

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

Check correctness of loaded records

Process-step specific KPI’s

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

Process-step specific KPI’s

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

Match review to verify the

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13

Create best record according to survivorship rules

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14

Check correctness of new, best, and updated records

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15

Provide consolidated data for

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 18

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 19

 New Process Goal: Consolidation of Active

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 20

Selection criteria for active records:

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 21

Results (Match Review)  The match decision on match

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 22

Replication (MDG Hub <-> Client)

Business Partner B Business Partner 200

Replication (MDG Hub <-> Client)

Consolidate Active Records (A=B)

Business Partner B Business Partner B Business Partner 200

Key mapping (MDG Hub <-> Client)

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 26

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 27

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 28

 Show all changes of a

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 29

 Clear result data after a

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 30

• Schedule the execution of a

• Prevents the execution of long

• Allows the activation of

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 31

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 32

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 33

 Automatically removes records or move

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 34

 Replace field values for

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 35

 Show messages for