SAP Master Data Governance

Central Governance of Business Partner, Customer, and Supplier Data

SAP
January 2023
Public
Preface

SAP Master Data Governance (MDG) is a state-of-the-art master data management solution. It
provides out-of-the-box, domain-specific master data governance to centrally create, change, and
distribute, or to consolidate master data across your complete enterprise system landscape.

In this context, MDG can either run as a separate master data hub or be co-deployed on an
operational system. In both cases MDG can run on:
▪ ERP on HANA or any other DB
▪ S/4HANA

From a functional perspective, SAP MDG on SAP S/4HANA 1809 correlates to the SAP MDG 9.2
release based on SAP ERP 6.0.

Note that although no correlating SAP MDG on ERP release exists for the subsequent SAP
S/4HANA releases, many innovations have also been downported to earlier SAP MDG releases.
You can find SAP Notes relating to this in the appendix.

Public 2
Agenda

Introduction

SAP Master Data Governance Capabilities

Function in Detail

Integration Scenarios

Solution Benefits

Public 3
SAP Master Data Governance
Consistent high-quality master data for your entire organization

SAP Master Data Governance is a state-of-the-art master data management application, providing preconfigured,
domain-specific master data governance to monitor and correct potential data quality issues, to centrally create, change,
and distribute, or to consolidate master data across your complete enterprise system landscape.

Central governance or consolidation for consistent master data

▪ Enables centralized governance, compliance, and transparency of master data during
creation and change through integrated staging, approval, and central audit trail
▪ Delivers consistent definition, authorization, and replication of key master data entities
▪ Eliminates error-prone manual maintenance processes for master data in multiple systems
▪ Supports consolidation of decentralized master data in any enterprise system landscape to
create best records and key mapping between duplicates
▪ Optionally combines consolidation with central governance for sustained master data quality

Quality Management
▪ Define master data quality rules, striving for consistent usage across all points of data entry,
and enabling data quality monitoring, analysis and remediation
▪ Observe and investigate master data management process quality to enable optimization

Integration and reuse

▪ Native integration and openness to integrate 3rd-party services
▪ Reuse of SAP’s data models, existing business logic, and configuration for data validation
▪ Open application to manage your own master data flexibly also for non-SAP environments
Public 4
Typical Approaches to Master Data Management
Central Governance and Distribution, decentralized Ownership with Consolidation

LoB customer LoB procurement LoB finance LoB production Other LoB

Systems under central governance

SAP Master Data Governance
– central governance
Maintain master data in line with business
processes (such as integrated product
Enterprise development or supplier management)
SAP Master Data Governance master data
– consolidation
Consolidate master data into a single view SAP Master Data Governance
for accurate analytics and operational – data quality management*
insight (continuously or on request, such as Manage master data quality by defining,
for initial load or mergers and acquisitions) enforcing, monitoring, and improving 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
Public *) only available with SAP MDG on S/4HANA 5
SAP Master Data Governance
Product description
All domains and processes
Service and
Order to cash Procure to pay Design to order Acquire to retire
maintain
Key capabilities
Enterprise
The application for master data
Customers Finance Vendors Materials Products Assets Location
the entire enterprise
master data management All use cases and implementation styles
Manage data quality
Continuous quality management and remediation
Ensure high data quality by continuously measuring, analyzing and correcting quality issues

Periodic consolidation for analytical purposes

Get data clean
Enable data consistency via consolidation for analytical use cases like global spend reporting

1 Get data clean

Consolidation for initial load before central governance
Enable data correctness and accuracy via consolidation run before starting central governance
2 Keep data clean

Get data clean Consolidation for M&A (or for MDG rollout to more regions/units)
Enable data consistency via consolidation every time it comes to an acquisition or, for example,
Keep data clean when onboarding master data for more regions, while continuously running central governance

Central governance only

Keep data clean
Have 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
Keep data clean parts under central governance
Public 6
Agenda

Introduction

SAP Master Data Governance Capabilities

Function in Detail

Integration Scenarios

Solution Benefits

Public 7
What Is SAP MDG, Central Governance for Business Partner Data?
Capabilities

Master Data Governance for Business Partner data offers a central hub-based maintenance of BP
master data.

To address the key business issues related to such a governance solution for master data, MDG for
business partner follows some basic principles that are shared across the domains of MDG
▪ Maintain once, use many
▪ One standardized process to be used by everybody
▪ One standardized user interface for everybody
▪ One standardized set of business logic

In order to fulfil these principles, SAP has built a Master Data Governance solution that offers
▪ Central maintenance of master data
▪ Workflow-driven processes that are flexible while ensuring governance and standardization
▪ Harmonized user interface, based upon Enterprise Portal, Business Client, or SAP Fiori launchpad
▪ Data model and business logic follow the best practices of SAP and reuse existing data structures,
business validations and various services
Public 8
Master Data Governance Capabilities
Establish Best-Quality Master Data to Optimize Business Processes

Reusability 5 1 Deliver
& Extensibility Out-of-the-Box

SAP
Master Data
Governance
Robust Data Integrated
2
Replication 4 Object Model

Governance,
3 Collaboration
& Data Quality
Public 9
Master Data Governance Capabilities
1 Deliver out-of-the-Box

Full Integration to SAP systems as a client

Low TCO
Offer integration services for non-SAP client systems

Workflow flexibility closely integrated to a framework

Flexibility
for defining business rules

Deliver a process-centric solution,

Ease of Consumption with roles and a web-based user interface
Deliver predefined data quality services

Deliver a data model

Best-Practice proven by several applications & industries

Process Transparency Reuse of existing processing logic

Out-of-the-box data replication mechanisms,

Integration using stable mechanisms

Public 10
Master Data Governance Capabilities
2 Integrated Object Model: Business Partners

Provide a directory of Business Partners (organizations, persons, groups of persons). This directory 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 offer seamless integration with customer-specific data and supplier-specific data).

Wildwater Ltd
Customer Supplier

Prospect Bidder

Contact Partner
…

Claire Johnson
Public 11
Master Data Governance Capabilities
2 Integrated Object Model: Solutions for Customers, Suppliers, and Business Partners

All solutions use the SAP-BP as central anchor for identifying data
▪ Business Partners that are both a customer and supplier are represented by one BP only

MDG-BP as basis for

▪ Customers limiting their governance scope to BP data only
▪ Solutions only being based on SAP-BP

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

MDG-C MDG-S MDG-BP

BP data

Customer-specific
Vendor specific data
data

Public 12
Master Data Governance Capabilities
2 Integrated Object Model: The BP Data Model for MDG-BP

Business
Central Data
Partner
Roles
Organization Address Details *Communication:
• Telephone Numbers
Address Usages • Mobile Numbers
Person
Communication* • Fax Numbers
• Email Addresses
Group International Versions • Web Sites
Address-Ind. Communication*

Bank Accounts

Payment Cards

Identification Numbers

Tax Numbers

Industries *² Financial Services:

• Ratings
Relationships • Creditworthiness
Contact Person
• Financial Services Details
• Partner is Bank
Workplace Address* • Financial Services Reporting
• Employment Overview
Financial Services*² • Fiscal Year Information
• Additional Names
• Tax Compliance
Business Partner Data

Public 13
Master Data Governance Capabilities
2 Integrated Object Model: The BP Data Model for MDG-C

Business
Central Data ERP Customer General Data
Partner
Roles Company Code Data
Organization Address Details CC General Data

Address Usages Dunning Areas *Communication:

Person • Telephone Numbers
Communication* Withholding Tax Types • Mobile Numbers
• Fax Numbers
Group International Versions Texts • Email Addresses
• Web Sites
Address-Ind. Communication* Sales Area Data

Bank Accounts General Data

Payment Cards Partner Functions

Identification Numbers Texts

Tax Numbers Tax Indicators

Industries Texts

ERP Customer Unloading Points *² Financial Services:

• Ratings
Relationships Documents • Creditworthiness
• Financial Services Details
Contact Person Classification • Partner is Bank
• Financial Services
Workplace Address* Reporting
• Employment Overview
• Fiscal Year Information
Financial Services*² ERP Customer-Specific Data • Additional Names
• Tax Compliance
Credit Scoring

Public 14
Master Data Governance Capabilities
2 Integrated Object Model: The BP Data Model for MDG-S

Business
Central Data ERP Vendor General Data
Partner
Roles Sub-Ranges
Organization Address Details Company Code Data

Address Usages General Data *Communication:

Person • Telephone Numbers
Communication* Withholding Tax Types • Mobile Numbers
• Fax Numbers
Group International Versions Dunning Areas • Email Addresses
• Web Sites
Address-Ind. Communication* Texts

Bank Accounts Purchasing Organization Data

Payment Cards General Data

Identification Numbers Different Purchasing Data

Tax Numbers Partner Functions

Industries Texts

ERP Vendors Texts *² Financial Services:

• Ratings
Relationships Documents • Creditworthiness
• Financial Services Details
Contact Person Classification • Partner is Bank
• Financial Services
Workplace Address* Reporting
• Employment Overview
ERP Vendor Specific Data • Fiscal Year Information
Financial Services*² • Additional Names
• Tax Compliance

Public 15
Master Data Governance Capabilities
2 Integrated Object Model: Customer/Vendor Integration

Company Code data

Central
Central Data*
Data
Purchase Org. data
Account data Example: Vendor Creation
CVI Complex Interface
A Business Partner is always created when a customer or supplier is created.
Business
Customer Vendor
Partner
The complex interface of the CVI (Customer/Vendor Integration) contains
Business Partner specific data as well as Customer and Vendor specific data.
Customer / Vendor
BP APIs Data Buffer
Get Partially, the data of the Business Partner and Customer/Vendor are redundant
(BUT000 against KNA1 & LFA1 data). For instance ‘Name and Address specific
SAVE CVI attributes’ are available in both persistencies.
Outbound

Customer or Vendor specific data is routed through the Customer/Vendor

Customer Vendor specific interface and mixed up with the Business Partner central data.
APIs APIs

On commit, the Business Partner and corresponding Customer and/or

Vendor is maintained / created.

Business Partner Customer Vendor

Public 16
Master Data Governance Capabilities
2 Integrated Object Model: Customer/Vendor Integration

Company Code data

Central
Central Data*
Data
Sales Area. data Example: Customer Creation
CVI Complex Interface
A Business Partner is always created when a customer or supplier is created.
Business
Customer Vendor
Partner
The complex interface of the CVI (Customer/Vendor Integration) contains
Business Partner specific data as well as Customer and Vendor specific data.
Customer / Vendor
BP APIs Data Buffer
Get Partially, the data of the Business Partner and Customer/Vendor are redundant
(BUT000 against KNA1 & LFA1 data). For instance ‘Name and Address specific
SAVE CVI attributes’ are available in both persistencies.
Outbound

Customer or Vendor specific data is routed through the Customer/Vendor

Customer Vendor
specific interface and mixed up with the Business Partner central data.
APIs APIs

On commit, the Business Partner and corresponding Customer and/or

Vendor is maintained / created.

Business Partner Customer Vendor

Public 17
 SAP Master Data Governance
Integrated Object Model
Out-of-the-box delivery of proven data models for operational and financial master data
Financials Material Supplier & Customer Enterprise Asset Mgmt. ** Retail & Fashion Mgmt. ***

Basic & Classification Data

Business Partner Attributes

Asset Structures
GL Account* /
Basic & Classification Data
General Data & Work Centers Descriptions Units of Measure
Chart of Accounts Descriptions Central Data Roles
Tax Bill of Material
Equipment Master

Linear Asset Capabilities

Cost Element* / Units of Measure Bank Details Identification Textile Components
Accounting, Controlling and Consolidation

Hierarchies Functional Location & Fiber Codes

Quality Data Tax Numbers Industry Sectors
Object Links and Networks Characteristics
Financial Reporting
Assignment & Variants
Structures: EAN, UPC Addresses with Usage and Versions
Balance Sheet, Maintenance Plans Distribution Curve

Work Management
P&L Statement Classification Business Partner Relationships

& Procurement

Purch.
Maintenance Items Purchase Info Record
Cost Center / Document Link
Supplier Attributes Customer Attributes Purchasing Org / Vendor / Site
Hierarchies Measuring Points
Sales Data General Data General Data
Profit Center / Stores Distribution Cntrs.

Logistics, Listing, Sales

Task Lists
Logistics Data

Hierarchies Listing Layout Module

Plant Data Comp. Code Data
Service Master
Comp. Code Data Point of Sales Sales Org. Data
Internal Order
Storage & Sales Area Data
Assortment Season Assignmt.
Warehouse Data

Bill of Material
Company Header: Identifying and Quantity,
Purchasing Data Tax Indicators Additionals Article Hierarchy
Validity Data, Material Data, Texts
Production Version

MRO
Consolidation: Substitution Additional Texts
Item, Group & Contract Account Attributes Item: Detail, Quantity, Status, Document Management System
Value

Hierarchies, Unit, Valuation, Costing, MRP and Purchasing Data,

FMS
Break Down Category Material Ledger General Data Partner specific Data Text and Document Assignment Segmentation Seasons

* User interface integration between GL Account and Cost Element only supported in SAP MDG on SAP S/4HANA ** SAP MDG, enterprise asset mgmt extension by Utopia *** SAP MDG, retail & fashion mgmt. extension by Utopia
Public 18
Master Data Governance Capabilities
3 Governance, Collaboration…

Possibility to extend the process by

Linear or distributed and workflow
adding business logic and thereby
based
bringing in data quality
Business Logic

Data in process stored in a separate

Has roles and responsibilities and
repository, will be transferred to
also task authority
operational database after final
(e.g. create, change, approve)
approval

Flexible enough to respect the

Can be adapted and tailored based distributed responsibilities existing
on customer needs in a company across various
business units

Public 19
Master Data Governance Capabilities
3 …and Data Quality

Prevent creation of duplicates for increased effectiveness

and efficiency
▪ Checked early and embedded in the process
▪ High detection quality of matching using SAP HANA-based or Enterprise
Search

Validations
▪ Reuse of existing validation logic
▪ Custom validations can be modelled and programmed
(For example, code lists, simple checks, or rules using BRFplus)
▪ Integration of rules from MDG, Data Quality Management

Address Enrichment
▪ Simple check and selection lists
▪ Integration with content provided by SAP Data Quality Management
▪ Automatically adding Tax Jurisdiction Code reusing interfaces/providers

Public 20
Master Data Governance Capabilities
4 Robust Data Replication
Replication
▪ Direct, pooled or manual replication to SAP and non-SAP
systems
▪ Peer-to-peer or mediated

User
Replication Techniques
▪ DRF controlling replication mechanisms like
– ALE for SAP S/HANA OP, SAP ERP 6.0, R/3 and non-SAP systems
Process – 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/SRM

Data
Replication Replication Features
Non-SAP SAP
System
▪ Flexibility to replicate selected data only to a specific client
System
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 PI)
▪ Monitoring and error handling
Public 21
Master Data Governance Capabilities
Deployment Options: Consciously Decide for a Central hub or Co-deployment
Deploy SAP MDG… SAP MDG SAP S/4HANA
SAP
…
CRM
 … as standalone system /
master data hub
SAP
3rd-party, SRM
NWAs
SAP MDG
 … on top of an SAP ERP, SCM,
& SAP S/4HANA
operational S/4HANA / ERP 6.0 CRM, SRM …
3rd-party,
NWAs

 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 S/4HANA / ERP 6.0 (or pick one of their SAP S/4HANAs / ERP 6.0s as the master for a
particular domain) and create and distribute master data from there

*) if speed of innovation in their S/4HANA systems does not allow for quick introduction of SAP MDG, some customers create a separate system first, and re-combine later
Public 22
Master Data Governance Capabilities
5 Reusability & Extensibility
Reuse standard content
▪ Reuse existing data structures and functionality of SAP
Individual S/4HANA
Processes
Tasks
Enhance functionality
▪ Be able to enhance MDG functionality based on
Extended
predefined content or customer-specific extensions
Reused

Extend data structures

▪ Provide easy-to-use extensibility capabilities for enhancing
Core
Processes
nodes and fields
– Data models
– User interfaces
– Processes
– Data replication
Central Team

Public 23
Agenda

Introduction

SAP Master Data Governance Capabilities

Function in Detail

Integration Scenarios

Solution Benefits

Public 24
Function in Detail
• Processes: Create, Change, Block/Unblock, Mark for Deletion
• User Interface
• Business Partner Data
• Data Quality
• Data Replication
• Client Maintenance
• Cleansing
• Processing of Multiple Objects
• Hierarchies
• MDG Framework Capabilities and Process Analytics
• Data Protection
• MDG for FI Contract Account
SAP Master Data Governance, Central Governance
Process Flow

External Providers External Services

SAP Master Data Governance

Reuse existing business logic, Collaboration
integrate external services Adaptable workflow
for address cleansing,
Auditable change process
duplicate detection, …
2 3
Maintain Validate Approve Replicate
Central maintenance of 1 4
master data in staging area
Automatic replication to
non-SAP and SAP systems

Business Processes

5
Adapt
Adapt

Adaptation / enrichment
in local systems

Public 26
Function in Detail: Processes
When to Use Which Process?

Usage

Create Change Block / Unblock Set Flag for Deletion

Business Partner, Search successful and Business Partner, Customer or Business Partner, Customer or
Customer or Supplier does data is incorrect Supplier is no longer relevant Supplier needs to be deleted in
not exist for processing for processes the next archiving run

Public 27
Function in Detail: Processes
Navigation to Create / Change Process

Found Yes
?
Requestor
Change Change Workflow

No

STOP

Search

Requestor

Not Found Yes

?
Requestor Create Workflow
Create
No

STOP

Public 28
Function in Detail: Processes
Workflow Template: Create Supplier (Distributed)

Purchasing Organisation Data

Purchasing
Org data
required? Approve
Central Data Purchasing Purchasing
Specialist Specialist
Reject / Rework Maintain Review
purchasing purchasing
org. data org. data
Activate data
Reject / Rework & Replicate
Requestor Submit for Master Data Approve
Maintain Approval Specialist
• Central Data Review
• Comp.Codes central data Reject / Rework
• Purch. Orgs

Financial Financial
Cancel Specialist Specialist Approve
STOP Company
Change Request Code data Maintain Review
company company
required? code data code data

Company Code Data

Public 29
Function in Detail: Processes
Workflow Template: Change Supplier (Distributed)

Central
Central data Data Master Data
changed Specialist Approve
Reject / Rework Review
central. data
Request data change
Purchasing
Activate data
Org. Data & Replicate
Requestor Submit for Purchasing Purchasing
Org. data Specialist
Maintain Approval
• Central Data
changed Review
• CC data Approve
Reject / Rework purchasing org.
• PO data data

Company
Company
Code data Code Data
changed Financial
Cancel STOP Approve
Specialist
Change Request
Review
Reject / Rework company
code data

Public 30
Function in Detail: Processes
Workflow Template: Block / Unblock Supplier (Distributed)

Central
Block Data Master Data
Central data Specialist Approve
Reject / Rework Review
central. data
Request data change
Purchasing
Activate data
Org. Data & Replicate
Requestor Submit for Block Purchasing
Purchasing Specialist
Block Approval Org. data
• Central Data Review
• CC data Approve
Reject / Rework purchasing org.
• PO data data

Block
Company
Company Code Data
Code data Financial
Cancel STOP Approve
Change Request Specialist
Review
Reject / Rework company
code data

Public 31
Function in Detail: Processes
Workflow Template: Set Flag for Deletion Supplier (Distributed)

Central
Deletion flag Data Master Data
Central data Specialist Approve
Reject / Rework Review
central. data
Request data change
Purchasing
Activate data
Org. Data & Replicate
Requestor Submit for Deletion flag Purchasing
Purchasing Specialist
Block Approval Org. data
• Central Data Review
• CC data Approve
Reject / Rework purchasing org.
• PO data data

Deletion flag
Company
Company Code Data
Code data Financial
Cancel STOP Approve
Change Request Specialist
Review
Reject / Rework company
code data

Public 32
Function in Detail: Processes
Workflow Template: Create / Change / Block / Set Flag for Deletion Supplier (Simple)

Reject / Rework

Activate data
& Replicate
Requestor Submit for Master Data Approve
Maintain Approval Specialist
all Data Review
all data

Cancel STOP
Change Request

Public 33
Function in Detail: Processes
Workflow Template: Create Customer (Distributed)

Sales Area Data

Sales area
data required? Approve
Central Data Sales
Specialist
Sales
Specialist
Reject / Rework Maintain sales Review sales
area data area data
Activate data
Reject / Rework & Replicate
Requestor Submit for Master Data Approve
Maintain Approval Specialist
• Central Data Rework and
• Comp.Codes review Reject / Rework
• Sales Areas central data

Financial Financial
Specialist Specialist Approve
Cancel STOP Company code
Change Request Maintain Review
data required? company company
code data code data

Company Code Data

Public 34
Function in Detail: Processes
Workflow Template: Create / Change / Block / Set Flag for Deletion Customer (Simple)

Central Data
Reject / Rework

Activate data
& Replicate
Requestor Submit for Master Data Approve
Maintain Approval Specialist
all Data Review
all data

Cancel STOP
Change Request

Public 35
Function in Detail: Processes
Workflow Template: Create / Change / Block / Set Flag for Deletion Business Partner (Simple)

Central Data
Reject / Rework

Activate data
& Replicate
Requestor Submit for Master Data Approve
Create, change Approval Specialist
Block, Set flag Review
for deletion central data
Central Data

Cancel STOP
Change Request

Public 36
Function in Detail: Processes
Workflow Templates Out-of-the-Box

Title Process WF Technique

Simple Two-step workflow SAP Business Workflow (Supplier +
• Starting with a requester Customer)
workflow • Completed by an approver who is also allowed to change / enrich the Rule-based Workflow WS60800086
data. (Business Partner)
Distributed Separate process steps for Central data, Financials data, and Sales / SAP Business Workflow
Purchasing data providing 4-eyes principle for each segment. Process for
workflow Financials data and Sales / Purchasing data run in parallel.

Fiori workflow Three-step workflow with Rule-based Workflow WS60800086

• A requester maintaining a limited number of fields
• A data steward changing / completing the data
• Another data steward to finally approve the data.

Public 37
Function in Detail: Processes
Workflow Templates Out-of-the-Box

Rule-Based Workflow Template

▪ The generic workflow template (WS60800086) is the
foundation of the RBWF. The different processes are
reflected by BRFplus decision tables, which are
maintained in the Customizing for each change request
type.
▪ The combination of this workflow template with the
BRFplus decision tables allows you to easily set up
many different processes that can be flexibly changed
through Customizing.

Public 38
Function in Detail: Processes
Rule-Based Workflow Components

Customizing BRFplus Decision Tables

Workflow
Template

Public 39
Function in Detail: Processes
Workflow-Step-Dependent Configuration Enables Flexible UI / Process Design

UI Configuration
Provide different User Interface per WF-step based on • Simple UI
task / knowhow of the user. Example: Lean Request UI Step 1 - • Selected checks and enrichments
Request

Validations
Enable or disable checks / enrichments • Expert UI
Example: Switch off required field check and address Step 2 - • Extended checks and enrichments
validation in Lean Request UI Check

Field properties • Approver UI

Set some data to read-only Step 3 - • Full Checks
Example: Processor for company code 0001 can only Approve
maintain these fields

Public 40
Function in Detail
• Processes
• User Interface
• Business Partner Data
• Data Quality
• Data Replication
• Client Maintenance
• Cleansing
• Processing of Multiple Objects
• Hierarchies
• MDG Framework Capabilities and Process Analytics
• Data Protection
• MDG for FI Contract Account
Function in Detail: User Interface
Homepage for NW Business Client

All relevant tasks reachable with Example: Supplier

one click

Additional analysis / graphics like

‘Change Requests with my
participation’ can be integrated

Easy to configure and personalize

Public 42
Function in Detail: User Interface
Fiori Launchpad for MDG on S/4HANA

All relevant tasks Example: Customer

reachable with one
click

Easy to configure and

personalize

SAP template Business Role: SAP_BR_BUPA_MASTER_SPECIALIST

Public 43
Function in Detail: User Interface
Workflow Inbox

Public 44
Function in Detail: User Interface
UI Configurations: Overview of out-of-the-box configurations

Title Process Configuration

BP-UI UI consisting of all data (central data as well as organizational data) of a BP, WD-App: BS_OVP_BP
customer and / or supplier. Separate pages for BP data, central customer / supplier BS_OVP_BP
data as well as organizational data. BS_OVP_CU
BS_OVP_SP
BS_OVP_BP_ALL

ERP Customer / UI consisting of all data (central data as well as organizational data) of a customer WD-App: BS_OVP_BP
or a supplier. Look & feel very similar to ERP Customer / ERP Vendor UI in ERP BS_OVP_CU_CL
ERP Vendor standard. BS_OVP_SP_VL
like UI
Specialized UIs for UI for Sales, Purchasing, Financial specialists consisting of organizational data for WD-App: BS_OVP_BP
one organizational unit. BS_OVP_CU_ORG
org. data BS_OVP_SP_ORG

Fiori UIs Lean UIs to request new customer, supplier or Business Partner; intended for
business users with no / limited MDG knowledge
UIs to approve new or changed customer / supplier; intended for experts approving
MD changes
Implemented as FIORI applications running on all devices.

Public 45
Function in Detail: User Interface
UI Configurations: BP Maintenance UI

Public 46
Function in Detail: User Interface
UI Configurations: ERP Customer-like UI

Goal: Support data maintenance in a way that is

very much like ERP Customer Master

Every new BP automatically becomes an ERP

Customer

Display ERP Customer number and select account

group instead of BP number and BP grouping

Identifying data (name, address, bank accounts,

etc.) and general customer data (Control data,
Company codes, Sales areas, etc.) on one screen

BP role derived in the background

Maintain contact persons similar to ERP Customer

Master
Public 47
Function in Detail: User Interface
UI Configurations: ERP Vendor-like UI

Goal: Support data maintenance in a way that is

very much like ERP Vendor Master

Every new BP automatically becomes an ERP Vendor

Display ERP Vendor number and select account group

instead of BP number and BP grouping

Identifying data (name, address, bank accounts, etc.)

and general vendor data (Control data, Company
codes, Purchasing organizations, etc.) on one screen

BP role derived in the background

Public 48
Function in Detail: User Interface
UI Configurations: Specialized UI, Maintain / approve Company Code data

UI contains data of the relevant company code only

Direct navigation from inbox to the UI

Finalize processing of the task on the same page

Public 49
Function in Detail: User Interface
UI Configurations: Specialized UI, Maintain / approve Sales Area data

UI contains data of the relevant sales area only

Direct navigation from inbox to the UI

Finalize processing of the task on the same page

Public 50
Function in Detail: User Interface
UI Configurations: Specialized UI, Maintain / approve Purchasing Organization data

UI contains data of the relevant purchasing

organization only

Direct navigation from inbox to the UI

Finalize processing of the task on the same page

Public 51
Function in Detail: User Interface
UI Configurations: Fiori UI, Lean Request for new Customer
Business/Process Context
▪ MDG Fiori lean request for Customer is meant for a business user who does not
have much expertise in MDG master data handling but would still like to request a
new MDG Customer
▪ Such a business user may require a new Customer for his product, even while on the
move. Rather than sending an email to or calling a Master Data Expert, he/she can
raise a request to create new customer by using Lean MDG Fiori application for
customer

Typical Business Challenges

▪ Manual efforts (emails, phone calls) to create MDG customer when request comes
from users either having no access to MDG or have no MDG / SAP knowledge
▪ Dependency on few employees having MDG knowledge to trigger MDG master data
creation
▪ High TCO and TCD for improving the user experience for commonly used business
functions of SAP MDG software

Facts & Figures Features and Capabilities

▪ Help Portal: Click here for help documentation ▪ An easy, simple and user-friendly UI for users with no master data expertise
▪ Role: A general business user ▪ Provides a simple, easy-to-use and coherent experience across devices – desktop,
▪ Target Segment: All employees including those with no MDG tablet, or smartphone
or SAP knowledge ▪ Leverages responsive design, the concept of making apps sensitive to the form
▪ Functional and Technical MDG 7.0 SP02
factor of devices with a single user interface
Prerequisites: ▪ Automatic duplicate check when creating a new customer
▪ Attachment functionality to attach a document with request
▪ Device and Browser Desktop, iPad, Smartphone, IE9, Chrome
▪ Supports creation of Organization or Person for a customer
Support:
▪ Supports US and Europe address form layouts for customer
Public 52
Function in Detail: User Interface
UI Configurations: Fiori UI, Lean Request for new Supplier
Business/Process Context
▪ MDG Fiori lean request for Supplier is meant for a business user who does not have much
expertise in MDG master data handling but would still like to request a new MDG Supplier
▪ Such a business user may require a new supplier for his running project, even while on the
move. Rather than sending an email to or calling a Master Data Expert, he/she can raise a
request to create a new supplier by using Lean MDG Fiori application for supplier

Typical Business Challenges

▪ Manual efforts (emails, phone calls) to create MDG supplier when request comes from
users either having no access to MDG or have no MDG / SAP knowledge
▪ Dependency on few employees having MDG knowledge to trigger MDG master data
creation
▪ High TCO and TCD for improving the user experience for commonly used business
functions of SAP MDG software

Facts & Figures Features and Capabilities

▪ Help Portal: Click here for help documentation
▪ An easy, simple and user-friendly UI for users with no master data expertise
▪ Role: A general business user ▪ Provides a simple, easy-to-use and coherent experience across devices – desktop, tablet,
▪ Target Segment: All employees including those with no MDG or smartphone
or SAP knowledge ▪ Leverages responsive design, the concept of making apps sensitive to the form factor of
▪ Functional and Technical MDG 7.0 SP02 devices with a single user interface
Prerequisites: ▪ Automatic duplicate check when creating a new supplier
▪ Attachment functionality to attach a document with request
▪ Device and Browser Desktop, iPad, Smartphone, IE9, Chrome
Support: ▪ Supports creation of Organization or Person for a supplier
▪ Supports US and Europe address form layouts for supplier
Public 53
Function in Detail: User Interface
UI Configurations: Fiori UI, Lean Request for new Business Partner
Business/Process Context
▪ MDG Fiori lean request for Business Partner is meant for a business user who does
not have much expertise in MDG master data handling but would still like to request a
new MDG business partner
▪ Such a business user may require a new business partner for his project, even while
on the move. Rather than sending an email to or calling a Master Data Expert, he/she
can raise a request to create a new business partner by using Lean MDG Fiori
application for business partner

Typical Business Challenges

▪ Manual efforts (emails, phone calls) to create MDG business partner when request
comes from users either having no access to MDG or have no MDG / SAP
knowledge
▪ Dependency on few employees having MDG knowledge to trigger MDG master data
creation
▪ High TCO and TCD for improving the user experience for commonly used business
functions of SAP MDG software
Facts & Figures
Features and Capabilities
▪ Help Portal: Click here for help documentation
▪ An easy, simple and user-friendly UI for users with no master data expertise
▪ Role: SAP_MDG_BCR_REQUESTOR_T ▪ Provides a simple, easy-to-use and coherent experience across devices – desktop,
▪ Target Segment: All employees including those with no tablet, or smartphone
MDG or SAP knowledge ▪ Leverages responsive design, the concept of making apps sensitive to the form factor
▪ Functional and Technical MDG 7.0 SP02 of devices with a single user interface
Prerequisites: ▪ Automatic duplicate check when creating a new business partner
▪ Attachment functionality to attach a document with request
▪ Device and Browser Desktop, iPad, Smartphone, IE9, Chrome
Support: ▪ Supports Organization or Person for a business partner creation
▪ Supports US and Europe address layouts for business partner
Public 54
Function in Detail: User Interface
UI Configurations: Fiori UI, Lean Request for change of Customer (Flexible Search)

Search UI
▪ Uses standard search defined in
MDG Configuration
▪ Configure search fields visible on
main screen
▪ More search options via Filters link
▪ Save predefined filters to reload next
time
▪ Navigate to FIORI app to request a
new customer
▪ SAP template Business Roles:
SAP_MDG_BCR_MYREQUESTS and
SAP_MDG_BCR_REQUESTOR_T

Public 55
Function in Detail: User Interface
UI Configurations: Fiori UI, Lean Request for change of Customer (Change Data)

Same data available as in FIORI Lean Request for

new Customer

Guided step-by-step UI to support unexperienced

users:
▪ Select Data to be changed (e.g. Name &
Organization Data, Address, Bank Account, etc.)
▪ Select Action to be executed on selected data (e.g.
Change selected address)
▪ Change data: Possibility to finalize change or add
more changes

Public 56
Function in Detail: User Interface
UI Configurations: Fiori UI, Track My Request
Business/Process Context
▪ MDG Fiori application ‘Track My Requests’ is meant for a business user
who does not have much expertise in MDG master data handling
▪ After raising the request for a new MDG master data, such a business
user would like to see the status of his/her request to check if the request
is approved or not
Typical Business Challenges
▪ Manual efforts (emails, phone calls) to contact and check the status of
raised request with MDG expert
▪ Dependency on few employees having MDG knowledge to convey the
status of MDG master data requests
▪ High TCO and TCD for improving the user experience for commonly
used business functions of SAP MDG software
Facts & Figures Features and Capabilities
▪ Help Portal: Click here for help documentation ▪ An easy, simple and user-friendly UI for users with no master data
▪ Role: SAP_MDG_BCR_MYREQUESTS expertise
▪ Target Segment: All employees including those with no MDG ▪ Provides a simple, easy-to-use and coherent experience across devices
or SAP knowledge – desktop, tablet, or smartphone
▪ Functional and Technical MDG 7.0 SP02 ▪ Leverages responsive design, the concept of making apps sensitive to
Prerequisites: the form factor of devices with a single user interface
▪ Device and Browser Desktop, iPad, Smartphone, IE9, Chrome ▪ Filter and sort functionality for selected requests
Support: (check configuration guide for more details
of support matrix) ▪ Configurable duration for which user wants to see the raised requests
Public 57
Function in Detail: User Interface
UI Configurations: Fiori UI, Approve Customer

Approve New Customer Approve Changed Customer

Public 58
Function in Detail: User Interface
UI Configurations: Fiori UI, Approve Supplier

Approve New Supplier Approve Changed Supplier

Public 59
Function in Detail: User Interface
Highlight Changes: Field changes

Highlight Saved Changes: Supports processor Highlighting of Table Rows

when deciding about next action Highlighted table rows refer to changes that
Highlight Unsaved Changes: Provides you can only see when navigating from a
information what can be “undone”. table row to the details of a dependent entity.
Saved changes and unsaved changes shown Tooltip Information
in two different colours.
Field tooltip shows previous value.

Public 60
Function in Detail: User Interface
Highlight Changes: Table changes, Create / Update

Unsaved changes
1st account changed
2nd account created

Saved changes
1st account changed
2nd account created

Changes after save

1st account changed and
saved
2nd account created,
saved, and changed again

Public 61
Function in Detail: User Interface
Highlight Changes: Table Changes, Delete

It enables you to highlight deleted values, including deleted rows that are shown in lists, and to
restore the latest active version of the deleted record.

The system highlights the relevant rows and displays deleted values as strikethrough, supporting you
in quickly identifying items marked for deletion when checking change requests, and offering a new
easy way to restore data.

Public 62
Function in Detail: User Interface
Highlight Changes: Changes on Detail Pages

Change in vendor’s
company code data…

Highlighted on first page

(Propagated up to BP-level)

Public 63
Function in Detail: User Interface
Undo Changes

All actions between two roundtrips are

collected in one step that can be undone.

You can undo steps (since last save) using

Undo.

After having used Undo, use Redo to recover

actions.

Public 64
Function in Detail: User Interface
Create with Reference

User Interaction
1. Mark business partner to be copied in search result
list. 2.
2. Select Copy button. 1.
3. UI to create customer / supplier appears, fields to be
copied are taken over from source business partner.
Copy Pattern
Two patterns delivered by SAP: 3.
– Standard: Copy non-individual data only
3.
– Complete: Copy all except fields causing business
error, e.g. do not copy ‘Date of last dunning notice’
For more information, see SAP Note 2020896.

3.
Public 65
Function in Detail: User Interface
Copy Segments

Copy organizational data

2.
1. Mark already available organization. 1.
2. Select Copy button.
3. Select target organization(s) not yet being
maintained.
4. Data is copied and can be reworked.
3.
Copy org. data: Entities
– Customer: Company Code data
– Customer: Sales Area data
– Vendor: Company Code data
– Vendor: Purchasing Org. data

Copy assigned Customer / Vendor: User interaction

1. Mark assigned Customer / Vendor in UIBB.
2.
2. Choose Copy button.
3. Customer / Vendor is copied and can be reworked. 1.
Public 66
Function in Detail: User Interface
Flexible UI via Configuration / Personalization: Call personalization

1. UI easy to configure and

personalize
– Choose Change Page
Layout button
– Change Page Layout
popup appears
– Multi-column (up to 3)
design
– Change sequence
– Stacked UIBBs (Tabs)
– Expand / compress /
suppress blocks

Public 67
Function in Detail: User Interface
Flexible UI via Context-Based Adaptations (CBA)

Integration of Context-Based Adaptations:

– Pre-delivered CBA dimensions:

– Examples of pre-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
Public 68
Function in Detail: User Interface
Integrate Additional Information via BCV Side Panel: Open Side Panel

Public 69
Function in Detail: User Interface
Integrate Additional Information via BCV Side Panel: Content for MDG Customer

 Reuse of generic component Business

Context Viewer (BCV)
 Customers can easily add content to the Side
Panel

 Sales Overview: Sales orders created for the

current customer number
 Changes Overview: Changes raised by the
current MDG change request

Public 70
Function in Detail: User Interface
Integrate Additional Information via BCV Side Panel: Content for MDG Supplier

 Reuse of generic component Business

Context Viewer (BCV)
 Customers can easily add content to the Side
Panel

 Purchasing Overview: Purchase orders

created for the current vendor number
 Changes Overview: Changes raised by the
current MDG change request

Public 71
Function in Detail
• Processes
• User Interface
• Business Partner Data
• Data Quality
• Data Replication
• Client Maintenance
• Cleansing
• Processing of Multiple Objects
• Hierarchies
• MDG Framework Capabilities and Process Analytics
• Data Protection
• MDG for FI Contract Account
Function in Detail: Business Partner Data
Data Model Business Partner BP

Business
Central Data
Partner
Roles
Organization Address Details *Communication:
• Telephone Numbers
Address Usages • Mobile Numbers
Person
Communication* • Fax Numbers
• Email Addresses
Group International Versions • Web Sites
Address-Ind. Communication*

Bank Accounts

Payment Cards

Identification Numbers

Tax Numbers

Industries *² Financial Services:

• Ratings
Relationships • Creditworthiness
Contact Person
• Financial Services Details
• Partner is Bank
Workplace Address* • Financial Services Reporting
• Employment Overview
Financial Services*² • Fiscal Year Information
• Additional Names
• Tax Compliance
Business Partner Data

Public 73
Function in Detail: Business Partner Data
Central Data

Organization Persons Groups (of persons)

▪ 4 Name fields plus search terms ▪ Several name fields like first name ▪ 4 Name fields plus search terms
▪ Organizational data and last name plus search terms ▪ Group data including Group Type
▪ Selected fields visible only, more ▪ Personal data ▪ Selected fields visible only, more
fields can be added via UI ▪ Selected fields visible only, more fields can be added via UI
Configuration fields can be added via UI Configuration
Configuration
Public 74
Function in Detail: Business Partner Data
Addresses

Multiple Addresses can be maintained per BP

Address Data
▪ Postal address
▪ PO Box address

Communication Data: Multiple …

▪ Telephone (landline and mobile) and Fax numbers
▪ Email addresses and Homepages

UI Layouts for Address data

▪ Layouts for Europe, USA, Canada, and Japan
▪ Layout for all users in IMG
SAP NetWeaver → Application Server → Basis Services → Address
Management → International Settings → Choose Address Screen Layout

▪ Layout per user via user parameter ADDRESS_SCREEN

Public 75
Function in Detail: Business Partner Data
Address Usages

Configure Address Types / Transactions

▪ Address Types: Visible in UI
▪ Address Transactions: Code against ID
▪ Configuration in IMG
Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Address Determination

Synchronization via CVI to ERP Customer / ERP Vendor

▪ Synchronize assigned address per ERP Customer / ERP Vendor
➔ See slides about ‘Usage of Multiple Addresses’)

Public 76
Function in Detail: Business Partner Data
Address Versions

Address versions
▪ Maintain address data per character set
▪ Latin, Cyrillic, Greek, Kanji, Hebrew, etc.
▪ Detailed documentation see SAP Note
316331, attached document

Maintain multiple versions per address

Configuration of Address Versions

IMG: SAP NetWeaver → Application Server
→ Basis Services → Address Management
→ International Settings → Activate International Address Versions

Synchronization with ERP Customer / ERP Vendor

▪ Synchronize all address versions per address

Public 77
Function in Detail: Business Partner Data
Multiple Address Handling for Customer Master Data

Up to now different addresses of a customer are often stored in distinct customer master records, because of one standard
address per customer number.

Solution with S/4HANA 2021:

It is now possible to maintain all addresses of a customer under a single
BP master record. Additionally, any data specific to a particular address
can be maintained as part of address dependent data. Prerequisite is
the Lightweight Business Function BPCUSTOMER_MULTIPLE_ADDRESSES.

The following address dependent UIBBs become available:

UIBB Description Back-end Table MDG Entity Type

ERP Customer: Address Dependent General Data KNA1_ADDR BP_CGENAD
ERP Customer: Address Dependent Tax Indicators KNVI_ADDR BP_CTAXAD
ERP Customer: Address Dependent Unloading Points KNVA_ADDR BP_CULPAD
ERP Customer Sales Area: Address Dependent Data KNVV_ADDR BP_CSALAD
ERP Customer Sales Area: Partner Functions KNVP BP_CUSFCN
Addresses -> Details BUT022 BP_ADDDEP
Addresses -> Details -> Tax Numbers DFKKBPTAXNUM_ADR BP_TAX_AD

Public 78
Function in Detail: Business Partner Data
BP Roles

Assign multiple roles per Business Partner

Time-validity of BP Roles supported

▪ Fields can be added to the UI via UI Configuration

Synchronization with ERP Customer / ERP Vendor during activation

▪ Define roles to enable Customer Vendor Integration (CVI)
IMG: Cross-Application Components → Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings
→ Settings for Customer Integration → Set BP Role Category for Direction BP to Customer
→ Settings for Vendor Integration → Set BP Role Category for Direction BP to Vendor

Public 79
Function in Detail: Business Partner Data
Bank Accounts

Multiple bank accounts per BP

Country-specific checks
▪ Bank ID and Bank Account Number
SAP NetWeaver → General settings
→ Set Countries → Set Country-Specific Checks

Time-validity of Bank Accounts

▪ Fields can be added via UI
Configuration

Legal requirements from Single European Payment Area (SEPA)

▪ IBAN: Maintain bank accounts with IBAN only (w/o Bank Identification Code)
▪ Mandates: Maintenance per local system (transactions BP, XD*, XK*), not supported in MDG

Synchronization with ERP Customer / ERP Vendor

▪ Synchronize all Bank Accounts to standard assigned ERP Customer / ERP Vendor
Public 80
Function in Detail: Business Partner Data
MDG-BP/C/S: Address-Independent Communication Data

As a master data specialist, I want to maintain address-independent communication data for a business
partner like email, fax and websites.

Solution from S/HANA 2021:

UIBB ‘Address-Independent Communication’ is available
for the standard communication with fields for Telephone,
Mobile, Fax, Email, Website and Standard Method.
A ‘More Address-Independent Communication’ link is
also available, where additional entries can be
maintained.

UIBB Description Back-end Table MDG Entity Type

Telephone Numbers ADR2 BP_TEL
Mobile Numbers ADR2 BP_TEL
Fax Numbers ADR3 BP_FAX
Email Addresses ADR6 BP_EMAIL
Websites ADR12 BP_URL

Public 81
Function in Detail: Business Partner Data
Payment Cards

1 User Interface
1▪ Multiple payment cards per BP can be maintained in
MDG-C. One can be marked as standard.
2▪ Card numbers can be masked on UI or even
2 encrypted at database level (SAP-BP).
3▪ Only users with special authorization are allowed to
see the full card number on request.

2 3
More Information
▪ Data will be stored during activation
– No security measure or Masked display
SAP-BP: Table BUT0CC, CCARD
ERP Customer: tables VCKUN / VCNUM
– Masked display & Encrypted when saved
SAP-BP: Tables BUT0CC, PCA_*
ERP Customer: Tables VCKUN / VCNUM
▪ Replication
– via ALE (IDoc DEBMAS) or
– SOA Service BusinessPartnerSUITEBulkReplicateRequest
Public 82
Function in Detail: Business Partner Data
Identification Numbers

Maintain multiple Identification Numbers BP SEPA (Slides in What’s new for MDG 7.0
▪ IBAN
Configuration of ID Type and ID Category
▪ Mandates (local use only, not supported in MDG)
▪ Predefined values by SAP
▪ Customer can add values Synchronization with ERP Customer / ERP Vendor
during activation
▪ One or multiple numbers per ID Type
▪ No

Public 83
Function in Detail: Business Partner Data
Tax Numbers

Maintain multiple Tax Numbers BP Synchronization with ERP Customer / ERP Vendor
during activation
Tax Number Categories ▪ Tax Number Category *0: VAT Registration Numbers
▪ All values delivered by SAP, new values via legal – BP home country: Field STCEG in KNA1 / LFA1
patch – Other countries: Tables KNAS / LFAS
▪ Tax Number Category *1.. *4
Tax Number Duplicate Check
– Tax Number fields STCD1.. 4 in KNA1 / LFA1
▪ Activate per Tax Number Category
▪ Tax Number checked against all other BPs

Public 84
Function in Detail: Business Partner Data
Tax Numbers, Support of numbers with more than 20 characters

Tax numbers were limited to a length of 20 characters, now extended to up to 60 characters in the UI

Relevant for some countries like Brazil which have tax numbers with more than 20 characters

Database for long tax numbers

– SAP Business Partner: Tax Number Category ending with ‘5’, data stored in DFKKBPTAXNUM-TAXNUMXL
– ERP Customer / ERP Vendor: data stored in new fields KNA1-STCD5 / LFA1-STCD5

Public 85
Function in Detail: Business Partner Data
Industries

Maintain multiple Industries per BP Synchronization with ERP Customer / ERP Vendor
▪ Standard industry of standard industry system
Optional: Maintain multiple industries for synchronized to Industry field (KNA1 / LFA1-
multiple Industry Systems (Catalogs) BRSCH)
▪ Add field Industry System to UI Configuration if ▪ Precondition: Define industry mapping for CVI
multiple Industry Systems are relevant IMG: Cross-Application Components → Master Data
Synchronization → Customer/Vendor Integration → Business
Partner Settings
Configure Industry Systems and Industries → Settings for Customer Integration → Field Assignment for
Cross-Application Components → SAP Business Partner → Customer Integration → Assign Attributes → Assign Industries
Business Partner → Organizations → Maintain Industry Systems → Settings for Vendor Integration → Field Assignment for
and Industries Vendor Integration → Assign Attributes → Assign Industries

Public 86
Function in Detail: Business Partner Data
BP Relationships

Maintain multiple relationships per relationship category

Relationship Categories
▪ SAP-delivered categories: Contact Person, Shareholder, Marriage, Parent / Child, etc.
▪ Customers can add further Categories (transaction BUBA)
▪ Cardinality and Time Constraint can be defined

Synchronization with ERP Customer / ERP Vendor

▪ Contact Persons with Workplace Address are synchronized

Public 87
Function in Detail: Business Partner Data
BP Relationships, Add Relationship in UI

Add Relationship with existing BP Add Relationship with new BP

1. Choose New to add a new relationship 1. Choose New to add a new relationship
2. Select the relationship category 2. Select the relationship category
3. Select related Business Partner via Search 3. Choose Create and select category of related
4. Select relationship and maintain relationship data Business Partner
4. Enter data of related Business Partner and
choose Done
5. Select relationship and maintain relationship data

1. 1. 3.

2. 3. 2.

Public 88
Function in Detail: Business Partner Data
BP Relationships, Time Dependency

Validity dates can be maintained for BP Relationships

Time constraint and cardinality can be defined for each relationship category (see transaction BUBA)

Time dependency to be activated by customer

Manual action required, for more information see SAP Note 2249877

Public 89
 Function in Detail: Business Partner Data
BP Relationships, Specialized UI for Contact Person Relationships

Business Background
Relevant contact person information distributed across several pages (person data, relationship data,
workplace address). The requirement was to merge most relevant data on one page, decrease the navigation,
and thus optimize the usability.

User Interface
1 ▪ New List UIBB for contact persons containing specific relationship information.
Note: Generic Relationship List UIBB is still available.

Navigation to details UI, see next slide

Public 90
Function in Detail: Business Partner Data
BP Relationships, Specialized UI for Contact Person Relationships

2
User Interface
2 One UI merging the most relevant:
– Contact Person data
(e.g. First Name, Last Name)
– Contact Person (Relationship) details
(e.g. Department, Function)
– Standard Workplace Address
(e.g. Building, Room Number, Communication
data)
– Navigation to further Workplace
Addresses

Public 91
Function in Detail: Business Partner Data
Financial Services Business Partner

As a master data specialist, I want to maintain financial

services specific attributes of a business partner.

Solution:
You can maintain the attributes on the following UIBBs:
UIBB Description Back-end Table MDG Entity Type

Ratings BP1012 FS_BP1012

Creditworthiness BP1010 FS_BP1010
Financial Services Details BP001 FS_BP001
Partner is Bank BUT0BANK FS_BPBANK (only if BP is an organization)

Financial Services Reporting BP1030 FS_BP1030

Employment Overview BP011 FS_BP011 (only if BP is a person)

Fiscal Year Information BP021 FS_BP021 (only if BP is an organization)

Additional Names BKK21 FS_BKK21

Tax Compliance BPTAXC FS_BPTAXC (prerequisite BF: CA_FSBP_TAX_C)

Public 92
Function in Detail: Business Partner Data
Data Model ERP Customer / ERP Vendor

ERP Customer General Data ERP Vendor General Data

Company Code Data Sub-Ranges

CC General Data Company Code Data

Business
Dunning Areas Partner General Data

Withholding Tax Types Withholding Tax Types

Texts Dunning Areas

Sales Area Data ERP Customers ERP Vendors Texts

General Data Purchasing Organization Data

Partner Functions General Data

Texts Different Purchasing Data

Tax Indicators Partner Functions

Texts Texts

Unloading Points Texts

Documents Documents

Classification Classification

ERP Customer-Specific Data ERP Vendor Specific Data

Public 93
Function in Detail: Business Partner Data
Assign ERP Customers / ERP Vendors, Use Cases & Concept

Multiple ERP Customers and ERP Vendors can be assigned to one Business Partner.
Use Case for assigning multiple ERP Customers with same address:
▪ Customer is treated differently within several business units of the same company code

Use Case for assigning multiple ERP Customers with different addresses:
▪ Company includes main location as well as deviating bill-to, ship-to etc. addresses (alternative option: Multiple
Address Handling for Customer Master Data)

Note: Multiple Assignments in MDG-BP will be supported in future only with the current scope and state.
Customers must decide, if this scope is sufficient for their complete system landscape. Also, performance topics
should be considered when using a lot of assignments.
BusinessSee also SAP note 2876690 - Multiple Business
Partner
Partners for the same legal entity.

ERP ERP ERP ERP ERP ERP

Customer Customer Customer Vendor Vendor Vendor

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

Public 94
Function in Detail: Business Partner Data
Assign ERP Customers / ERP Vendors, Implementation

Multiple ERP Customers and ERP Vendors can

be assigned to one Business Partner and share
the same Business Partner data.

ERP Customer-specific and ERP Vendor-

specific data including sales / purchasing
organization and company code data; can be
maintained per assigned ERP Customer or ERP
Vendor

Public 95
Function in Detail: Business Partner Data
Assign ERP Customers / ERP Vendors, Usage of Multiple BP addresses (Use Case)

One Business Partner with 3 Addresses

Main address in Berlin is Sold-to, Bill-to, and Payer Address
Additional addresses in Hamburg and Frankfurt are ship-to addresses

CKC Germany
Unter den Linden 11 Kirchenallee 34 Europa-Allee 46
10117 Berlin 20099 Hamburg 60327 Frankfurt

Standard Bill-to Payer Ship-to

address address address address

Public 96
Function in Detail: Business Partner Data
Assign ERP Customers / ERP Vendors, One BP per Address

CKC Germany
Unter den Linden 11 Kirchenallee 34 Europa-Allee 46
10117 Berlin 20099 Hamburg 60327 Frankfurt

Standard address Bill-to address Payer address Ship-to address

CKC Germany CKC Germany CKC Germany Business Partner

Unter den Linden 11 Kirchenallee 34 Europa-Allee 46 Three Business Partners required, one
10117 Berlin 20099 Hamburg 60327 Frankfurt per address

CKC Germany CKC Germany CKC Germany ERP Customers

Unter den Linden 11 Kirchenallee 34 Europa-Allee 46 Relevant location for each process
10117 Berlin 20099 Hamburg 60327 Frankfurt
Partner Functions (per Sales Area)

SP BP PY
SP, BP, and PY by the same ERP
SH
Sold-to Bill-to Payer Ship-to Customer
party party party For SH: link to other ERP Customer
under deviating Business Partner
Public 97
Function in Detail: Business Partner Data
Assign ERP Customers / ERP Vendors, One BP per Legal Entity

CKC Germany
Unter den Linden 11 Kirchenallee 34 Europa-Allee 46
10117 Berlin 20099 Hamburg 60327 Frankfurt

Standard address Bill-to address Payer address Ship-to address

Unter den Business Partner

Kirchenallee 34 Europa-Allee 46
CKC Germany Linden 11
20099 Hamburg 60327 Frankfurt
One Business Partner for sold-to party
10117 Berlin with three addresses

CKC Germany CKC Germany CKC Germany ERP Customers

Unter den Linden 11 Kirchenallee 34 Europa-Allee 46 Relevant location for each process
10117 Berlin 20099 Hamburg 60327 Frankfurt
Partner Functions (per Sales Area)

SP BP PY
SP, BP, and PY by the same ERP
SH
Sold-to Bill-to Payer Ship-to Customer
party party party For SH: links to other ERP Customers
under the same Business Partner
Public 98
Function in Detail: Business Partner Data
Assign ERP Customers / ERP Vendors, One BP per Legal Entity, User Interface
1 1 Business Partner with Addresses
Add new Business Partner for sold-to party with three
addresses, one address marked as standard

2 ERP Customers with Sales Area Data

2 Assign three ERP Customers including Sales Area data to
the Business Partner. One ERP Customer is marked as
standard which has to use the standard address.
For additional assigned ERP Customers, users can decide
whether to use the standard address or one of the BP
3 addresses that are assigned explicitly
3

Partner Functions (per Sales Area)

3 4
Maintain partner functions at sales area level for the standard
4 ERP Customer. Partner Functions SP, BP, and PY are taken
over by the same ERP Customer, SH (ship-to) is taken over
by the other ERP Customers.
Note: In MDG on S/4HANA 1709 / MDG 9.1, activated ERP Customers can only be
referred within Partner Functions. The process may have to be split into two
consecutive Change Requests.
Public 99
Function in Detail: Business Partner Data
Assign ERP Customers / ERP Vendors, Create BP with Assignments & Partner Functions in One CR

ERP Customers / ERP Vendors added to the Business Partner can now be used as deviating
partner within partner functions in the same change request.

This means that within one change request, you are now able to create a Business Partner with
multiple ERP Customers / ERP Vendors and maintain partner functions between these ERP
Customers / ERP Vendors.

Public 100
Function in Detail: Business Partner Data
General Data (Customer and Vendor)

General data can be maintained per ERP

Customer / ERP Vendor

Account Group for:

▪ Standard Assignment derived from BP
Grouping according to CVI Configuration
▪ Additional Assignments selected by the user

Authorization checks supported:

▪ General Data (F_KNA1_GEN, F_LFA1_GEN)
▪ Account Group (F_KNA1_GRP, F_LFA1_GRP)

Data will be stored in tables KNA1 / LFA1 during

activation

Replication via ALE and SOA Service

Public 101
Function in Detail: Business Partner Data
General Data (Customer and Vendor), Select account group during creation

Business Background
When first assigning an ERP Customer / ERP Vendor to a
Business Partner, the account group was automatically
1 derived according to CVI Configuration. Requirement to
enable users to select another account group manually.

CVI Configuration
1▪ Assignment of BP Grouping to Account Group can now
be marked as flexible. This means the user can overwrite
the account group for standard assignment.
2
User Interface
2▪ When creating a new Business Partner, select flexible
BP Grouping from the value list.
3▪ When adding a new ERP Customer, the account group
is defaulted according to the CVI Configuration, but can
be overwritten by the user.

3
Public 102
Function in Detail: Business Partner Data
Documents (Customer and Vendor)

4 1 User Interface
1▪ Multiple documents can be assigned per
ERP Customer / ERP Vendor.
2▪ Documents as well as links are stored in
the Document Management System (DMS);
2 this UI can be called from MDG UI.
3▪ From DMS UI, document properties can be
managed, and document can be displayed.
3 4▪ Documents can be uploaded to DMS from
MDG UI.

Replication
▪ Document as well as link to ERP Customer / ERP
Vendor via ALE (IDoc DOCMAS) or
▪ Link to ERP Customer / ERP Vendor via SOA Service
BusinessPartnerSUITEBulkReplicateRequest
Public 103
Function in Detail: Business Partner Data
Lean Classification (Customer and Vendor), Motivation

Feedback for MDG-M Classification (up to MDG 9.0 and S/4HANA 1610):
▪ UI-related feedback:
– Classes and characteristics are not on same page
– User should not see a difference between normal attributes and classification
– More usable UI, possibility to adapt the UI

▪ Function-related feedback:
– Integration of derivations missing
– Simultaneous display and change of classification is not supported (authorizations for display not possible)
– Simultaneous processing of different class types or classes using a parallel change request is not possible

Missing support in other MDG applications (up to MDG 9.0 and S/4HANA 1610)
▪ No support for classification in MDG Consolidation
▪ No support for classification for Supplier and Customer in MDG Central Governance

Public 104
Function in Detail: Business Partner Data
Lean Classification (Customer and Vendor), Concept

For Customer, Supplier and Material:

▪ MDG Single Object Maintenance UI
▪ MDG Consolidation

Simplified UIs

Mass-enabled API

Simplified back-end features to reduce complexity

Class assignment and characteristics valuation work like normal entities in data model

Public 105
Function in Detail: Business Partner Data
Lean Classification (Customer and Vendor), Features and Restrictions

Supported Features
▪ Derivations using BAdI CROSS_ENTITY_BADI (incl. defaulting for class types and classes)
▪ Checks using BRFplus
▪ Authorizations (incl. display authorization)
▪ Change Documents
▪ Multiple class types and class assignments
▪ Characteristic values: Single or multiple values, additional values, intervals, mandatory checks (required entry)

Restrictions (not supported)

▪ Object dependencies (pre-conditions, actions, selection condition, procedures)
▪ Overwriting of characteristic values and overwriting of inherited values
▪ Engineering Change Number

You can find detailed information about included/excluded features in SAP Note 2479869.

Public 106
Function in Detail: Business Partner Data
Lean Classification (Customer and Vendor), User Interface

1 1 Assign Classes
List UIBB to assign classes. Classes of class
types assigned to object table LFA1 / KNA1 can
be assigned.

2 Enter Characteristic Values (Single Value)

Single value characteristics assigned to selected
2 classes are visible in one row and can be filled
with a value.
3
3 Enter Characteristic Values (Multiple Values)
Multiple value characteristics are also visible in
one row and can be recognized by ‘+’ and ‘-’
buttons on the left. You can use these buttons to
insert or delete rows.

Public 107
Function in Detail: Business Partner Data
Lean Classification (Customer and Vendor), Further Details

Configuration / Master Data

▪ Based on Customizing configuration of classification system to e.g. maintain object types and class types
(see Customizing under Cross-Application Components ➔ Classification System)
▪ Based on master data of classification system to e.g. maintain characteristics and classes
(see SAP Menu under Cross-Application Components ➔ Master Data)

Consolidation
▪ Can be consolidated like other entities
▪ See separate presentation about Consolidation

Data Activation / Replication

▪ Classification data will be stored in classification system during activation
– Object Type KNA1 for ERP Customer
– Object Type LFA1 for ERP Vendor
▪ ALE replication via standard IDoc CLFMAS
▪ SOA Service replication via BP service BusinessPartnerSUITEBulkReplicateRequest

Public 108
Function in Detail: Business Partner Data
Texts (Customer and Vendor)

You can now enter explanatory texts for ERP Customers and ERP Vendors for different text
types and for different languages.

Texts are available for

– ERP Customers at general level, as well as at company code and sales area level
– ERP Vendors at general level, as well as at company code and purchasing organization level

Configuration of Text IDs within IMG activities known from ERP Customer / ERP Vendor

Public 109
Function in Detail: Business Partner Data
Unloading Points (Customer)
1

User Interface
1 ▪ Multiple unloading points can be maintained per ERP Customer. One can
2 be marked as standard.

2 ▪ Preconfigured goods receiving hours can be assigned or can be

maintained manually (field Goods Receiving Hours is initial).
▪ Receiving points and departments are not supported.

More Information
▪ Data will be stored in ERP Customer (table KNVA) during activation
▪ Unloading points can be replicated via
– ALE (IDoc DEBMAS) and
– SOA Service BusinessPartnerSUITEBulkReplicateRequest

Public 110
Function in Detail: Business Partner Data
Company Code Data (Customer and Vendor)

Multiple Company Codes can be assigned

per ERP Customer / ERP Vendor

Screen Layout per Company Code supported

IMG: Financial Accounting (New) → Accounts Receivable and
Accounts Payable → Customer Accounts → Master Data →
Preparations for Creating Customer Master Data → Define
Screen Layout per Company Code (Customers)
Similar path for ERP Vendor

Authorization check per company code

(F_KNA1_BUK, F_LFA1_BUK) supported

Data will be stored in tables KNB1 / LFB1

during activation

Replication via ALE and SOA Service

Public 111
Function in Detail: Business Partner Data
Dunning Areas (Customer and Vendor)

Multiple Dunning Areas per company code Dunning Area ‘ ‘ (Default) always first entry
assigned to ERP Customer / ERP Vendor
Data will be stored in tables KNB5 / LFB5
Configure Dunning Areas and values for other during activation
fields in IMG for ERP Customer / ERP Vendor
Replication via ALE and SOA Service

Public 112
Function in Detail: Business Partner Data
Withholding Tax Types (Customer and Vendor)

Multiple Withholding Tax Types per company Data will be stored in tables KNBW / LFBW
code assigned to ERP Customer / ERP Vendor during activation

Activate Extended Withholding Tax per Replication via ALE and SOA Service
Company Code
IMG: Financial Accounting (New) → Financial Accounting Global
Settings (New) → Withholding Tax → Extended Withholding Tax →
Company Code → Activate Extended Withholding Tax

Public 113
Function in Detail: Business Partner Data
Sales Area Data (Customer)

Multiple Sales Areas per ERP Customer

Screen layout per sales area supported

(transaction SM30, view V_T079V)

Authorization check for ERP Customer per Sales

Area (V_KNA1_VKO) supported

Data will be stored in tables KNVV during

activation
Replication via ALE and SOA Service

Public 114
Function in Detail: Business Partner Data
Partner Functions (Customer)

Multiple Partner Functions per Sales Area can be assigned to ERP Customer

Partner Determination for ERP Customer can be configured in IMG

IMG: Sales and Distribution → Basic Functions → Partner Determination → Set Up Partner Determination

Data will be stored in tables KNVP during activation

Replication via ALE and SOA Service

Public 115
Function in Detail: Business Partner Data
Tax Indicators (Customer)

Tax Indicators to be maintained per relevant countries

Collect company code’s countries of Sales Organizations assigned to ERP Customer

Data will be stored in table KNVI during activation

Tax Indicators can be replicated via ALE and SOA Service

Public 116
Function in Detail: Business Partner Data
Purchasing Organization Data (Vendor)

Multiple Purchasing Organizations can be Authorization check per Purchasing

assigned per ERP Vendor Organization (M_LFM1_EKO) supported

Field modification per Purchasing Organization Data will be stored in tables LFM1 during
supported (transaction SM30, view V_T079M) activation

Replication via ALE and SOA Service

Public 117
Function in Detail: Business Partner Data
Different Purchasing Organization Data (Vendor)

Multiple records per assigned ERP Vendor /

Purchasing Organizations

Record can be dependent on a:

▪ Plant
▪ Vendor Subrange
▪ Combination of Plant / Vendor Subrange

Data will be stored in table LFM2 during

activation

Replication via ALE and SOA Service

Plants can be configured in IMG

Vendor Sub-Ranges are maintained per ERP
Vendor at general data level (table WYT1)
Public 118
Function in Detail: Business Partner Data
Partner Functions (Vendor)

Multiple Partner Functions can be assigned per Partner Determination can be configured in IMG
ERP Vendor / Purchasing Organization. IMG: Materials Management → Purchasing → Partner
Determination

Partner Functions can be additionally Data will be stored in table WYT3 during
dependent on ‘Different Data’: activation
▪ Plant
▪ Vendor Subrange Replication via ALE and SOA Service
▪ Combination of Plant / Vendor Subrange

Public 119
Function in Detail
• Processes
• User Interface
• Business Partner Data
• Data Quality: Search, Duplicate Check, Validations, Address Enrichment, Checks and Derivations
• Data Replication
• Client Maintenance
• Cleansing
• Processing of Multiple Objects
• Hierarchies
• MDG Framework Capabilities and Process Analytics
• Data Protection
• MDG for FI Contract Account
Function in Detail: Data Quality
Search Overview

Change
Mass
Mark for Change
Deletion

Create Block/Unblock

Search

Search – First Step to Data Quality

Search is the initial action, if a user wants to “do something” with the data
Several flavours supported via Search Provider Concept
Standard providers:
▪ DB-based search
▪ Enterprise Search
▪ SAP HANA-based Search
Public 121
Function in Detail: Data Quality
Search Capabilities

Consistent search UI containing all search

capabilities:
▪ Search methods are easy to configure, more
search methods can be added
▪ Drop-down lists of available fields and operators
▪ Add and remove search criteria (AND combination
of multiple parameters)
▪ Search criteria can be saved using a descriptive
name for quick and easy reuse (as a global or
private variant)
▪ Search for hits within active and inactive data
▪ One or more business partners can be selected to
find related change requests

Public 122
Function in Detail: Data Quality
Search Options

Fuzzy (error-tolerant) search, if supported by search provider

Add and remove search parameter (AND

combination of multiple parameters)

Search criteria can be saved

using a descriptive name for
Drop-down lists of available fields and operators for search quick and easy reuse

Public 123
Function in Detail: Data Quality
Enterprise Search

Using Enterprise Search with MDG provides

– Free text search across many attributes
– Attribute-based search in specific fields only
Free text
– Search active data only to limit search to
active area
Attribute-based – Fuzzy search checkbox to enable error-
tolerant search mode

Advantages of using Enterprise Search (compared with database search)

◼ Free text search
◼ Fuzzy (error-tolerant) search

Public 124
Function in Detail: Data Quality
SAP HANA-based search capabilities

Search terms and attribute-based search

▪ Using a single search term “free-style search” across
all attributes
▪ The fuzziness threshold for search criteria can be
customized. A threshold of 1.0 will run an exact
match search for that criterion and hence behave as
‘equal to’.

Calculated similarity rank

▪ For each positive hit, SAP HANA-based search
calculates a similarity score weighted across all
attributes
▪ Hit List contains ranking and is sorted by ranking

Public 125
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 SAP HANA-based or Enterprise
Search

Validations
▪ Reuse of existing validation logic
▪ Custom validations can be modelled and programmed
(For example, code lists, simple checks, or rules using BRFplus)
▪ Integration of rules from MDG, Data Quality Management

Address Enrichment
▪ Simple check and selection lists
▪ Integration with content provided by SAP Data Quality Management
▪ Automatically adding Tax Jurisdiction Code reusing interfaces/providers

Public 126
Function in Detail: Data Quality
Duplicate detection via SAP HANA-based search

Prevent users from creating redundant

master data
▪ Find duplicates early in the process
▪ High detection quality using SAP HANA-
based search and matching

Help users to decide if duplicates exist

▪ Similarity score used to identify and sort
potential duplicates

Public 127
Function in Detail: Data Quality
Checks and Derivations using BRFplus

For general information

on how to work with
BRFplus, see:
▪ SAP Help Portal

▪ SAP Documentation

Transaction USMD_RULE

Public 128
SAP Master Data Governance, Data Quality Management*
Process Flow

Define Quality Enter Quality Monitor Quality Improve Quality

Requirements are defined based on Ensure quality at point of entry Operational motivation: detect Correct data and drive the
your company’s business processes issues before processes fail correction process
Consider all entry-points: single
Priorities are set according to value, changes, mass changes, load Tactical: ensure progress and Fix data entry processes
impact, and quality evolution scenarios, in daily business, performance of current activities
Evolve the definition of quality
projects, …
► Experts collaborate to define needed Strategic: enable achievements,
► Tools to fix data and to improve
quality level and required checks ► Rule-based checks in all define new initiatives
checks at point of entry
processes of SAP MDG
► The system helps to identify ► Easy-to-consume monitoring
additional meaningful rules and trend reporting

Karl Singer
Steven Olsen

Steven Olsen

Public *) only available with SAP MDG on S/4HANA 129

Master Data Quality Management*
Improve the Quality of Your Business Partner and Product Data
In a nutshell …
Business user application to define master data quality rules, striving for consistent usage across all points of entry
and enabling data quality monitoring and remediation.

Business value
Define Quality Enter Quality Monitor Quality Improve Quality
Central place for master data quality rules. Providing
transparency on business aspects, usages and technical
implementations, consistent quality definition, and continuous
evaluation and monitoring
▪ Business partner and product master data covered as packaged
applications, and platform for custom-defined objects
▪ Collaboratively describe, catalog, and implement rules for data
quality evaluation
▪ Schedule quality evaluations, analyse evaluation results and
initiate correction of erroneous data
▪ Get an overview of current data quality status and KPIs
▪ Allow for drill-down analysis of data quality scores along multiple
dimensions

Public *) only available with SAP MDG on S/4HANA 130

Function in Detail: Data Quality
Using Data Quality Management Validation Rules in Central Governance

As a master data steward, I want to use

existing data quality validation rules for quality
evaluation in change request processing as
well.

Solution: Integration of Data Quality

Management Validation Rules in Central
Governance Change Request Processing
▪ Enable additional usage of rule for check in
change request
▪ Reuse of the same rule implementation
▪ Flexibility to independently enable rules for
evaluation and check
▪ Open for custom implementation in the access
class of MDG, central governance for custom
objects

Public 131
Function in Detail: Data Quality
Using Derivation Scenarios

As a master data steward, I want to derive values of

single or multiple fields, create or update dependent
entities and keep an overview on my derivations so to
achieve a high degree of automation in my governance
processes.

Solution:
Integration of Data Quality Management Derivation
Scenarios into Central Governance based on a
background step in the rule-based workflow, a custom
BAdI implementation, a new API
(CL_MDG_MDQ_RBWF_DERIVE) and corresponding
customizing. See How To Guide for more information.

Derivation scenarios provide derivation rules to derive

values of single or multiple fields as well as to create or
update dependent entities. Derivation scenarios
combine derivation rules into executable and
manageable units including lifecycle management,
configuration and data maintenance by business users.

Public 132
Function in Detail
• Processes
• User Interface
• Business Partner Data
• Data Quality
• Data Replication
• Client Maintenance
• Cleansing
• Processing of Multiple Objects
• Hierarchies
• MDG Framework Capabilities and Process Analytics
• Data Protection
• MDG for FI Contract Account
Function in Detail: Data Replication
Overview
Replication
▪ Automatic or manual replication to SAP and non-SAP systems
▪ Peer-to-peer or mediated

User Replication Techniques

▪ DRF controlling replication mechanisms like
– ALE for S/4HANA OP, SAP ERP 6.0, R/3 and non-SAP systems
– SOA service for SAP and non-SAP systems
Process – RFC and File for SAP and non-SAP systems
▪ CIF for SAP SCM and MW for SAP-CRM/SRM

Replication Features
Data
Replication
▪ Flexibility to replicate selected data only to a specific client
Non-SAP SAP system by defining filters (controlled by DRF)
System System
▪ Support of different object IDs or Customizing keys between
hub and client systems (via mapping in MDG or PI)
▪ Monitoring and error handling

Public 134
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 system available

Public 135
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
▪ Activate option per Change Request type in
IMG under Master Data Governance, Central
Governance → General Settings → Process
Modeling → Change Requests → Create
Change Request Type

Public 136
Function in Detail: MDG Framework Capabilities
Data Replication: Pooled or Direct Replication

You can decide if you want to enable direct replication or pooled replication for each combination of business
object and target system. With direct replication, the messages are sent with the activation of the change
request. With pooled replication, the messages are sent periodically using the DRF change pointer.
▪ Direct Output: Changes are directly transferred to a target system.
▪ Pooled Output: Changes are collected and transferred in a mass process at a later point in time.
You can trigger the mass process for pooled output by starting or scheduling the report Execute Data
Replication
(RDRF_MESSAGE_OUT) for the relevant replication models. SAP MDG
ERP1
Direct Output

Change Pointer
GOVERN Pooled
Output ERP2

Direct Output
ERP3

Public 137
Function in Detail
• Processes
• User Interface
• Business Partner Data
• Data Quality
• Data Replication
• Client Maintenance
• Cleansing
• Processing of Multiple Objects
• Hierarchies
• MDG Framework Capabilities and Process Analytics
• Data Protection
• MDG for FI Contract Account
Function in Detail: Client Maintenance
Maintenance on Hub & on Client can be Used in Unison

Maintenance on MDG Hub Maintenance on Client

1
Client 1 Client 2 Client 1 Client 2
2 2 4 4

2
MDG Hub MDG Hub
1 3

2 2 4 4
Client 3 Client 4 Client 3 Client 4

1 Maintain data on MDG Hub 1 Maintain data on Client 1

2 Replicate data to client systems 2 Replicate data to MDG Hub
3 Rework / approve data on MDG Hub
4 Replicate data to client systems
Public 139
Function in Detail: Client Maintenance
Configure MDG Hub for Client Maintenance via SOA Service

MDG to generate Change Request / Consolidation Run for inbound SOA Services
– Call IMG for Data Replication Framework (transaction DRFIMG)
– Choose Data Replication → Define Custom Settings for Data Replication → Define Technical Settings →
Define Technical Settings for Business Systems
– Select client system and choose Define Bus. Systems, BOs
– Select BO Type 147 (Business Partner) and choose Define Bus. Systems, BOs, Communication Channel
– Change field Storage (Staging Area for Change Request) and Create / Change Template (for Consolidation)

Assign relevant Change Request Type to Business Activities BPPI / BPPU

Public 140
Function in Detail
• Processes
• User Interface
• Business Partner Data
• Data Quality
• Data Replication
• Client Maintenance
• Cleansing
• Processing of Multiple Objects
• Hierarchies
• MDG Framework Capabilities and Process Analytics
• Data Protection
• MDG for FI Contract Account
Function in Detail: Cleansing
Overview

Identifying Duplicates Cleansing Case

Merge

Public 142
Function in Detail: Cleansing
Identifying Duplicates

Before creating a cleansing case and 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 database scan (using external tools)
– Identified potential duplicates will be stored
within a cleansing case for further processing

Public 143
Function in Detail: Cleansing
Cleansing Case

Process steps:
▪ Create a new cleansing case, search
and assign potential duplicates
▪ Search cleansing case (can also 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

Public 144
Function in Detail: 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.

Here it is possible to copy the data including

all dependent data (e.g. address including its
communication data).

In parallel, it is also possible to edit data of

the “Target Record“ directly.

As a result of the merge process, a workflow

process will be triggered.
Public 145
Function in Detail
• Processes
• User Interface
• Business Partner Data
• Data Quality
• Data Replication
• Client Maintenance
• Cleansing
• Processing of Multiple Objects
• Hierarchies
• MDG Framework Capabilities and Process Analytics
• Data Protection
• MDG for FI Contract Account
Function in Detail: Processing of Multiple Objects
When to Use What

Multi-Record Processing
▪ Well-defined governance process with multiple workflow steps for a limited number of Business Partners
▪ Typically a collaboration of multiple processors
▪ Governance processes exist for single and multiple objects
▪ Examples
– Account manager wants to compare and harmonize sales data for all Customers belonging to the account
– Strategic buyer wants to update purchasing conditions of all relevant Suppliers based on newly signed
contract

Mass Processing
▪ Interactive master data change process for huge number of Business Partners
▪ Typically ad hoc / on request / project-based processing by one data specialist
▪ Examples
– Change dunning parameters for all C-Customers of a country based on the newly defined process
– After reorganization in purchasing, Suppliers are assigned to newly responsible purchasing groups
Public 147
Function in Detail: Processing of Multiple Objects
Multi-Record Processing: Accessing

Process to change multiple Business Partners within a spreadsheet-like UI

Start from Search Result list

▪ Select multiple Business Partners
▪ Choose Multi-Processing button

Predefined Change Request types

▪ Multi-Processing for Customer Sales
▪ Multi-Processing for Customer Financials
▪ Multi-Processing for Vendor Purchasing
▪ Multi-Processing for Vendor Financials

Public 148
Function in Detail: Processing of Multiple Objects
Multi-Record Processing: Functionality

Functions for rows

▪ Add new rows
▪ Copy rows
▪ Delete rows

Functions for field values

▪ Edit single fields
▪ Find and Replace
▪ Select rows with same value
▪ Copy value to selected rows

Visualize / handle changes

▪ Highlight changes
▪ Discard changes

Public 149
Function in Detail: Processing of Multiple Objects
Multi-Record Processing: Switch on / off Highlight Changes

The Highlight Changes button

(delivered in some template UI
configurations) allows the user to
toggle the highlight changes
function in Multi-Record
Processing.

At startup, the highlighting of

changes is always switched off.

This may enhance UI

performance in certain cases.

For more information, see SAP Note 2547067 - MR Processing: Switch "Highlight Changes“ and How-To Guide Create User Interface for Multiple-Record Processing.

Public 150
 SAP Master Data Governance, Mass Processing
Process Flow

Scope Selection Edit Validation Activation

Describe the scope of your Enter search criteria to select Edit the data using a tabular UI The system checks the validity The activation releases your
change by choosing the fields the master data objects that you by changing single or multiple of the data in the background. changes from the staging area,
that you want to change. want to change. fields at a time. so that the updated data is used
Verify the validation results and
The system copies the data to a in business processes.
Verify your changes based on correct the data if necessary.
staging area for processing. statistical information provided
by the system.

Public 151
Mass Processing
Effective Process to Execute Mass Changes for Attributes

In a nutshell…
Highly effective mass change process enabling master data stewards to perform bulk changes in business
partner, customer, supplier, and product data.

Business value
▪ Highly effective data processing option for master data specialists
▪ Efficiently edit individual fields or make bulk changes by using a
tabular UI with the ability to filter and sort data
▪ Confidence and transparency when changing large volumes of data
through statistics, change indicators and ability to validate prior to
activating changes
▪ Packaging, queuing, and parallelization contribute to enhanced
performance even when processing large volumes of data
▪ Upload changed records from CSV or Microsoft Excel© file to
incorporate offline processing and other information sources
▪ Background execution enables users to close the application while
processing continues. Users can check the status or proceed with
their work later.

Public 152
SAP Master Data Governance, Consolidation
Process Flow

Calculate Best
Data Load Initial Check Standardize Match Validate Activate
Record

Open to SAP HANA View loaded data Validate and enrich Find duplicates based Create “Best Validate best records Provide consolidated
smart data integration, and check data address data on customer-specific Records” based on against back-end master data for
non-HANA based quality based on matching rules approved match Customizing to verify analytical or
Possibility to connect
SAP ETL back-end groups whether records can operational use
to 3rd-party tools for
mechanisms, Customizing Review match result be activated
standardization and BRF+ can be used for
non-SAP ETL options, Option to activate
enrichment customer-specific
or data import from file Validate against directly, or indirectly
Best Record
Usage of BRF+ for ctrl. governance trigger post-
Calculation
standardization and checks (BAdI, BRF+) processing using
enrichment Review Best Record central governance
Calculation result

Public 153
Master Data Consolidation
Create a Single Source of Truth of Your Customer, Supplier, and Product Data
In a nutshell …
Highly effective data consolidation option for master data specialists seeking a single source of truth for customer,
supplier, and product data.

Business value
Enable consolidation for customer, supplier, and product data based Data Initial
Match
Calculate
Validate Activate
Load Check Best Record
on intuitive and flexible process with consumer-grade user
experience through SAP Fiori user interface
▪ Highly effective data processing option for master data specialists
▪ Easy-to-use UI to visualize all data during a consolidation process (drill-
down, show changes, match review, best record review)
▪ Confidence and transparency when loading large volumes of data through
statistics, change indicators and ability to validate prior to activating the data
▪ Configurable matching capability to identify duplicates inside loaded records
and against existing records
▪ Wizard-like UI to upload source data into the system
▪ Background execution enables users to close the application while
processing continues. Users can check the status or proceed with their
work later. Integration with MDG, central governance possible
Public 154
Function in Detail
• Processes
• User Interface
• Business Partner Data
• Data Quality
• Data Replication
• Client Maintenance
• Cleansing
• Processing of Multiple Objects
• Hierarchies
• MDG Framework Capabilities and Process Analytics
• Data Protection
• MDG for FI Contract Account
Function in Detail: Hierarchies

MDG provides analytical hierarchies only. Data can be extracted toward BI. There is no connection
to operational hierarchies, neither the ERP Customer Hierarchy nor the BP Hierarchy.

Maintain Validate Approve Replicate

Adapt

Central Master Data Governance

Public 156
Function in Detail: Hierarchies
Assign BP to hierarchy from Single object maintenance UI

You can now assign Business Partners to hierarchies during Single Object Processing (Creation or
Change process).

The UI also offers a value help for easy identification of the relevant parent node.

Public 157
Function in Detail
• Processes
• User Interface
• Business Partner Data
• Data Quality
• Data Replication
• Client Maintenance
• Cleansing
• Processing of Multiple Objects
• Hierarchies
• MDG Framework Capabilities and Process Analytics
• Data Protection
• MDG for FI Contract Account
Function in Detail: MDG Framework Capabilities
Common Services of MDG

Common services of change request processing:

▪ Mass change
▪ Support of parallel Change Request
▪ Additional Steps After Activation, Follow-Up Change Request and Recall Change Request
▪ Enrichment Spot
▪ Governance Scope
▪ Import Master Data
▪ Key Mapping and Value Mapping
▪ Process Reporting
▪ Process Overview and Change Request Analysis for Business Partner
▪ Archiving

Public 159
Function in Detail: MDG Framework Capabilities
Mass Change

▪ Optionally, create a change request and submit it

(typically w/o materials assigned yet)

▪ Now start the mass change and select your relevant

materials by choosing Define Selection (Step 1) and
Refine Selection (Step 2)

▪ Step 3: Replace one or more fields with one

dedicated value

▪ Step 4: You can review the results and execute the

change. If not yet done, you now need to assign an
open mass change request that is assigned to you,
or you can create a new change request

Public 160
Function in Detail: MDG Framework Capabilities
Multiple Change Requests Per Customer / Supplier at the Same Time

Creation of customer / supplier with initial Change Request General data

▪ One Change Request for create customer / supplier

Request Approve Activate Replicate

Parallel Change Requests for subsequent individual processing

▪ Parallel Change Requests for extending customer per Sales Area and /
or per Company Code
▪ Parallel Change Request for extending supplier per Purchasing
Organization and / or per Company Code
Sales Sales Comp. Comp.
Activation for general data and per organizational unit directly Area 1 Area 2 Code 1 Code 2
after approval
▪ Workflow creation for each selected organizational unit, activation after Request Request Request Request

approval
Approve Approve Approve Approve
Lock on entity level (interlocking)
▪ Instead of lock on object level only
Activate Activate Activate Activate
▪ Change request type determines the maintainable fields

Replicate Replicate Replicate Replicate

Public 161
Function in Detail: MDG Framework Capabilities
Additional Steps After Activation

As a master data steward, I want to trigger

additional workflow steps after the
activation. This may include additional steps
related to the object of the change request
itself, and could also result in a follow-up
change request as well (see IR 213267).
Solution: A user can now define additional
steps after the activation step, if necessary.
In other words, the workflow no longer has
to end after a change request has been
activated successfully.
Instead, after a change request has been
activated, further actions can be performed
to trigger additional dialog workflow steps. A
workflow item for these additional steps can
then be found in the workflow inbox of the Note that this new feature is included in the single maintenance UI, however it is not available if you are using a CR for
multiple objects involving the MASS, LOAD or HIERARCHY business activities, as these use a generic UI instead

user who has been assigned accordingly. (USMD_CREQUEST_PROCESS).

Public 162
Function in Detail: MDG Framework Capabilities
Follow-up Change Request

As a master data steward, I want to define additional follow-up processes for object changes which are not part of the
original change request (for technical or organizational reasons). Those follow-up change requests should be triggered
automatically with reference to the existing change request.

As a master data steward, I want to be able to find the related change requests and to have transparency about the related
master data changes.

Solution: Master data stewards can define additional follow-up processes that are not part of the original change request due
to technical or organizational reasons using the existing How-To Guide. New links on the Change Request UI and in the My
Change Requests screen allow them to call up previous change requests and follow-up change requests directly.

Public 163
Function in Detail: MDG Framework Capabilities
Recall Change Request

▪ As a requestor, I want to have the ability to recall the request after it has been routed for approval and before
the request has been approved.

▪ The change request should be

routed back to me, as I may
realize that additional changes
are required and might need to
recall it to add the data.

▪ An additional action
‘Recall by Requester’ is delivered
and can be used to setup
corresponding change request
step and workflow.

Public 164
Function in Detail: MDG Framework Capabilities
Perform Duplicate Check on Demand

▪ As a master data steward, I want to perform the

duplicate check on demand independently whether
it has been already performed or if data has
changed so that I can check for potential duplicates
at any time without pre-conditions.

▪ A new button is available in case a duplicate check

has been configured for the respective
CR type and CR step. If configured,
a duplicate check can be triggered
at any time.

Public 165
Function in Detail: MDG Framework Capabilities
Display the Number of Search Result Records

▪ As a master data steward, I want

determine the number of master data
records matching certain search criteria
(which may be empty) so that I can omit a
real search/retrieval of all master data
records since only the aggregate is of
interest but not the result list. This will
save system performance and reduce the
time required of get the number of
records.

▪ For SAP HANA-based search an

additional search criterion ‘Number of
Entries’ is available. If selected the
number of matching master data records
is displayed instead of the search result
list.
Public 166
Function in Detail: MDG Framework Capabilities
Framework for Data Enrichment Spots

Data Enrichment Spots

– Flexible framework to define enrichment spots
– Used by SAP, for example for Address Validation
– Can be used by customers to define further
enhancement spots

Public 167
Function in Detail: MDG Framework Capabilities
Address Enrichment and Name and Organization Cleansing

Address Enrichment / Name and

Organization Cleansing
For Postal Address Validation, SAP delivers the
Enrichment Spot ‘Address Enrichment’. It uses the
Postal Address Validation of SAP Data Quality
Management. The required setup for DQM must exist.
The Enrichment Spot ‘DQM MDG Enrichment Spot‘
for Name and Organization Cleansing is not delivered,
but can easily be set up.

Activate per CR Step

For each Change Request Type, Address Enrichment
or Name and Organization Cleansing can be activated
per Change Request Step.

Public 168
Integration Scenarios: Business Partner Screening (SAP-BPS)
Activate screening per Change Request Step

Enrichment
Implemented as Enrichment Spot
‘Address Screening’ with
corresponding adapter in MDG
Activate per CR Step
For each Change Request
Type, Screening can be activated
per Change Request Step
Deployment Options
BP Screening can run on MDG
instance (same HANA DB, different
NW AS) or on different instance

Public 169
Function in Detail: MDG Framework Capabilities
Governance Scope - Deactivate Entity Types / Fields

Governance Scope
▪ Only parts of the data model shall be put under
governance
▪ Entity types / attributes can be excluded from
governance
▪ Excluded entity types / attributes:
– Cannot 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

Public 170
Function in Detail: MDG Framework Capabilities
Import Master Data
Material master data, Key Mapping and Value Mapping can be uploaded to the MDG system from an XML file using the MDG Import Master
Data transaction. The imported material master data can be adjusted or modified in a change request. Only when the change request is
approved is data written to the SAP S/4HANA material master data (which is the active area).
If data quality is good, the data can also be written directly into the active area.

Master Data Administrator Master Data Specialist Business User Master Data Specialist

File Import into Review Complete Material Approve

Change Request
* Change Request
* Data
* Change Request
*
Customer business challenges Business value
▪ No direct upload functionality was available within SAP ERP ▪ Upload to MDG system (Material, Key Mapping and Value Mapping)
▪ No governance process existed for the upload of mass data ▪ Built-in upload functionality for MDG increases the speed of updates and
streamlines integration between systems
▪ Governance functionality avoids creation of duplicates and ensures
completeness and accuracy of data

Public 171
Function in Detail: MDG Framework Capabilities
Key Mapping and Value Mapping
This feature supports the replication of data into systems with non-harmonized Customizing or with heterogeneous keys. For example, in
cases where the same business partner has a different number on the master data governance (MDG) hub than on a client (key mapping), or
similar account groups have a different code in hub and clients (value mapping).

Master Data Specialist Master Data Steward / Automated step Automated Step

Maintain Key Mappings for Process Key- and Value

Trigger Data Distribution
Material Data Mappings

Customer business challenges Business value

Customers built their own solutions to map the values to distribute the data Heterogeneous system landscapes can be supplied using the key
correctly to different systems mapping and value mapping functionality offered with MDG

Public 172
Function in Detail: Master Data Process Overview

Summary dashboard displaying relevant process information

Public 173
Function in Detail: Master Data Process Overview

The cards on an Overview Page provide you with one-stop information on

work due and the work done for the individual user as well as a set of
processes:
▪ Get overview and real time insight into open work items for change requests.
▪ Analyze performance of completed work items for continuous improvement.
▪ Change Request related information as trigger to work on change requests requiring
my attention (open CRs, long running CRs, rejected CRs)
▪ Average processing times of change requests to improve processing times
▪ Completed CRs and upcoming workload (i.e. open CRs)
▪ Consolidation processes and the status of these processes / which require my attention
▪ Quality of Mass Processing (number of objects per process, no. of changed objects,
runtime per process and no. of objects, validation status and threshold)
▪ Users will be able to hide and unhide cards in the OVP depending on working need

Public 174
Function in Detail: Change Request Analysis

Analytical List Page

All apps implement the
SAP Fiori Analytical List Page
floorplan (ALP) and share the
same behavior.

▪ Header with the filter bar, here:

displaying visual filters for
Number of Change Requests
by Status, Number of Change
Requests by Priority
▪ Change Requests chart –
smart chart for visualization,
drill-down, filtering
▪ Change Request table –
analytical table for detailed
information, actions, export

Public 175
Function in Detail: Change Analysis for Business Partners

Enables master data

specialists to get real time
insight into BP master data
changes in change requests
by master data attributes and
organizations.
▪ View and analyze the changes
by your preferred dimensions
as of master data attribute.
▪ Multiple analysis targets
support different use cases:
Open CRs, Finalized CRs (with
and w/o details), All CRs
▪ Custom labels for fieldnames
in reporting.

Public 176
Function in Detail: MDG Framework Capabilities
Archiving

▪ The general recommendation is to

archive change requests. Archiving
removes the change requests from
the database and moves them to an
external storage. This will reduce the
size of the database and improve
performance.
▪ Only change requests in a final state
can be archived, namely in the
statuses Final Check Approved or
Final Check Rejected. You can still
access archived change request from
the application Display Change
Requests including their (archived)
change documents.
▪ Further information:
– SAP Note 2574330 (Archiving and
deletion of change requests)
– Online Documentation on Data
Archiving in MDG
Public 177
Function in Detail
• Processes
• User Interface
• Business Partner Data
• Data Quality
• Data Replication
• Client Maintenance
• Cleansing
• Processing of Multiple Objects
• Hierarchies
• MDG Framework Capabilities and Process Analytics
• Data Protection
• MDG for FI Contract Account
Function in Detail: Data Protection
Hiding / Deleting Business Partner Data

The concept of simplified blocking and deletion based on SAP Information Lifecycle Management
(ILM) is now supported in SAP MDG. It therefore reacts to the End-of-Purpose (EOP) flag
▪ EOP state 1: Hide blocked BP, data still in system
▪ EOP state 2: Delete BP data from system (at end of retention time)

EOP state 1: Hide blocked BP, data still in system EOP state 2: Delete BP data from the system
▪ Exclude BP from search ▪ BP deleted
▪ Delete BP from existing Change Requests ▪ Delete BP from Change Requests
▪ Delete BP from Consolidation and Mass Processing ▪ Delete BP from Consolidation and Mass
runs Processing runs
▪ Mask BP within Hierarchy Processing, no navigation ▪ Mask BP within Hierarchy Processing, no
▪ Hide all changes from change document list navigation
▪ Delete all changes from change document list

Public 179
Function in Detail: Data Protection
Read Access Logging

Read Access Logging is used to monitor and log read access to sensitive data. This data may be
categorized as sensitive by law, by external company policy, or by internal company policy.
Configuration examples are available for SAP MDG in transaction SRALMANAGER.
▪ Web Dynpro UI: Log access of
– Bank Accounts
– Payment Cards
– Change Documents
– Creditstanding
– Rating
▪ SOA replication: Log access of
– Bank Accounts
– Payment Cards
▪ Gateway Services: Log access of
– Bank Accounts

Public 180
Function in Detail
• Processes
• User Interface
• Business Partner Data
• Data Quality
• Data Replication
• Client Maintenance
• Cleansing
• Processing of Multiple Objects
• Hierarchies
• MDG Framework Capabilities and Process Analytics
• Data Protection
• MDG for FI Contract Account
Function in Detail: MDG for FI Contract Accounts
Introduction

CONTRACT ACCOUNTS RECEIVABLE AND PAYABLE (FI-CA)

▪ Sub ledger accounting for processing large document volumes
▪ Realizes the typical accounts receivable functions
▪ Originally used in Service Industries like Insurance, Utilities, Telecom, Public Sector, Media etc.; now
increasingly used for all kind of mass business
▪ Based on SAP Business Partner (ERP Customer / ERP Vendor Master are not used)
▪ Each Business Partner posting is assigned to one Business Partner and to one Contract Account

Contract Accounts
▪ For each Business Partner, define the procedures that apply when posting and processing line items
▪ Control parameters for billing, payment, dunning, correspondence, etc.
▪ Independent entity
– One Contract Account can include assignments to multiple Business Partners
– One Business Partner can be assigned to multiple Contract Accounts

Public 182
Function in Detail: MDG for FI Contract Account
Data Model

MDG for FI Contract Accounts available in MDG on S/4HANA 1709 SPS1 and MDG 9.1
▪ Contract Account data model consists of generic core data as well as industry-specific data
▪ MDG supports generic core data out-of-the-box as well as extensibility options
▪ In MDG, Contract Account data is part of Data Model BP for Business Partners
Contract Account

Header Data Partner Specific Data

Tax Exemptions Correspondence Recipients

Business Partners Locks

Texts

Charges & Discounts

Public
(Activation via Extensibility) 183
Function in Detail: MDG for FI Contract Account
User Interface, Launchpad & Search

Launchpad Search Screen

Search via Contract Account or BusPartner data

Public 184
Function in Detail: MDG for FI Contract Account
User Interface, Data Maintenance

Header Data Partner Specific Data

Public 185
Function in Detail: MDG for FI Contract Account
User Interface, Maintain Future Changes

Changes to a Contract Account can be planned for a future date

Future changes are stored separately (planned change documents) and will be activated via a
report that is scheduled to run daily.

Planned changes for multiple dates can be maintained, data of two validities can be compared by
displaying list of deviating values.

Public 186
Function in Detail: MDG for FI Contract Account
Services

Activation
▪ Business Function for FI-CA to be activated before starting with MDG for FI Contract Account

Configuration
▪ Using configuration steps in IMG under Financial Accounting (New) → Contract Accounts Receivable and
Payable → Basic Functions → Contract Accounts (Transaction FICAIMG)

Validations
▪ Standard checks implemented in SAP-GUI UI
– Number Ranges and Contract Account Categories
– Contract Account / Business Partner Relationships etc.
▪ Custom Validations via BRF+
▪ Field Modification per Contract Account Category and per Activity
▪ Authority Checks for Contract Account Type, Company Code, Authorization Group etc.

Derivations via BRF+

Public 187
Function in Detail: MDG for FI Contract Account
Process Modelling

Business Activities
▪ FKK1 Create Contract Account
▪ FKK2 Process Contract Account
▪ FKK3 Display Contract Account

Change Request Types (pre-delivered, can be adjusted within project)

▪ FKK1P1 Create Contract Account
▪ FKK2P1 Change Contract Account Reject / Rework

Workflow Activate data

& Replicate
▪ Two-step workflow for four-eyes-principle Requestor Submit for Master Data Approve
Specialist
▪ Implemented via Rules-based Workflow Submit
Change
Approval
Review
Request all data

Cancel STOP
Change Request
Public 188
Function in Detail: MDG for FI Contract Account
Extensibility

Field Extensibility
▪ Pre-delivered MDG data model contains generic fields
▪ Industry-specific fields can be added to pre-delivered entity types via field extensibility
▪ Custom-specific fields can be added to pre-delivered entity types via field extensibility
▪ Field Extensibility Guide with step-by-step explanation available

Node Extensibility
▪ Only industry-specific entity type is Charges & Discounts
▪ UI / logic for Charges & Discounts is pre-delivered, but inactive
▪ Charges & Discounts can easily be activated following the Node Extensibility Guide for Charges & Discounts
▪ Extensibility Guides can be found on the SAP Community for Master Data Governance

Public 189
Function in Detail: MDG for FI Contract Account
Data Replication / Data Load

New SOA Services for replicating Contract Accounts from MDG to operational ERP systems.

Loading Contract Accounts to MDG via Data Import.

Contract Accounts can be sent from other systems to MDG via SOA Service for further processing
within Change Request (Client Maintenance).

Public 190
Agenda

Introduction

SAP Master Data Governance Capabilities

Function in Detail

Integration Scenarios

Solution Benefits

Public 191
Integration Scenarios
• Integration with Supplier Lifecycle Management (SAP-SLC)
• Integration with Customer Relationship Management (SAP-CRM)
• Integration with SAP Sales Cloud
• Integration with Business Partner Screening (SAP-BPS)
• Global & local MD Hubs
• Technique
Integration Scenarios: Supplier Lifecycle Management (SAP-SLC)
Overview SAP-SLC

Supplier
Registration
– First Version Strategic Buyer
Workplace
Supplier Supplier
Phase-out Qualification – Integration with MDG-S
– Procurement Analytics (Portfolio)
and Content Tagging
– Multi-dimensional Supplier
Supplier Supplier Classifications
Development 360° Category Evaluation
Management/Tagging – Interface with BW
– Tighter Integration with SAP
Streamwork for Supplier
Supplier Order
Supplier
Collaboration (UI
Integration)
Classification Development

Public 193
Integration Scenarios: Supplier Lifecycle Management (SAP-SLC)
Core Processes SLC / MDG-S

Strategic Supplier Mgmt

8
7
6
Enhanced Supplier Data
5 Integration into Backend
Mgmt
4
3
2
1
SLC
0
MDG-S
Approval Processes in
Data Validation
BE

Duplicate Checks Supplier Data Distribution

Public 194
Integration Scenarios: Supplier Lifecycle Management (SAP-SLC)
Supplier Data Flow – High level

Supplier registration New potential supplier

Approval

Qualify
supplier

SAP Master Data

Supplier self-service Governance

Approval To SAP Master Data

Governance
 Company data
 Contacts
 Addresses
 Bank and tax data

Potential suppliers are only managed by SAP Supplier Lifecycle Management.

Global supplier master data can be enriched and changed within SAP Supplier Lifecycle Management and transferred to the master data
system or vice versa.
Data for other segments is managed and distributed by the master data system.
Public 195
Integration Scenarios: Supplier Lifecycle Management (SAP-SLC)
Maintain Potential Suppliers in SLC, Governance of Bidders / Suppliers in MDG

1 5
1 Maintain potential suppliers in SAP-SLC only
SAP-SLC Client
4
2 2 Potential supplier becomes bidder / supplier in SAP-
4 SLC ➔ send supplier to MDG Hub & create a CR
2

MDG Hub
3 5 3 Rework / approve data on MDG Hub

4 4 4 Replicate data to client systems

Client Client
3 4 5 Changes to bidders / suppliers in SLC or MDG

MDG Hub is ready for the scenario as of MDG 6.1, SLC is ready for the scenario as of SLC 1.0
SP03
Public 196
Integration Scenarios
• Integration with Supplier Lifecycle Management (SAP-SLC)
• Integration with Customer Relationship Management (SAP-CRM)
• Integration with SAP Sales Cloud
• Integration with SAP Ariba Supplier Lifecycle and Performance
• Integration with Business Partner Screening (SAP-BPS)
• Global & local MD Hubs
• Technique
Integration Scenarios: Customer Relationship Management (SAP-CRM)
Prospects / leads in CRM, governance of customers in connected S/4HANA or ERP 6.0

1 5
1 Maintain prospects & leads in CRM only
SAP-CRM Client 2
4 4 2 Prospect becomes customer in CRM ➔
2 replicate to Operational S/4HANA via CRM-
3 5 MW & create Change Request in MDG
Operational
S/4HANA + MDG 3 Rework / approve data in MDG

4 4 4 Replicate data to client systems

Client 3 Client 4 5 Changes to customers possible in CRM and

S/4HANA via MDG

Public 198
Integration Scenarios: Customer Relationship Management (SAP-CRM)
Prospects / leads in CRM, governance of customers in connected S/4HANA or ERP 6.0

1 5
Good to know
SAP-CRM Client 2 – MDG has to run in operational S/4HANA connected
4 4 with CRM
2
– CRM-MW has to be configured in a way that BP
3 5
with role ‘Customer’ only are replicated to S/4HANA
Operational – BP with customer role is created / changed in
S/4HANA + MDG
Operational S/4HANA before MDG change request
is created (with activity Change)
4 4
– Searching from CRM on MDG requires project-
Client 3 Client 4 specific implementation

Public 199
Integration Scenarios: Customer Relationship Management (SAP-CRM)
Prospects / leads in CRM, governance of customers in separate MDG Hub

MDG Hub between CRM and S/4HANA 1 Maintain prospect / lead in CRM only
2 2 Prospect becomes customer in CRM ➔
Order Order
1
Order CRM-MW Order
replicate to MDG Hub via SOA Service, create
(not for BPs)
Operational a CR in MDG Hub. CRM-MW is deactivated
SAP-CRM 5 for replication of BPs.
S/4HANA
4 Distribution lock is marked automatically for
2 4 related Sales Orders to be replicated to
3 S/4HANA.
MDG Hub 3 Rework / approve data on MDG Hub
(BP data, Sales data,
FIN data)
4 Replicate data from MDG to all connected
4
4 client systems including CRM and
Operational S/4HANA
Client 3 Client 4 5 Unmark distribution lock of related sales
orders and restart replication.
Public 200
Integration Scenarios: Customer Relationship Management (SAP-CRM)
Prospects / leads in CRM, governance of customers in separate MDG Hub

MDG Hub between CRM and S/4HANA Good to know

2 – All BP data (Central, Sales and Financials) can be
Order Order governed within MDG Hub.
1
Order CRM-MW Order – Scenario requires several project-specific coding
(not for BPs)
Operational
SAP-CRM 5
efforts / configuration, recommendations are
S/4HANA described in a How-to Guide
4
(https://www.sap.com/documents/2015/07/d8457b52-
2 4
3 5b7c-0010-82c7-eda71af511fa.html).
MDG Hub – Scenario was tested by MDG Development. However
(BP data, Sales data, - like always – project-specific coding / configuration
FIN data) is the responsibility of the project.
4
4 – Searching from CRM on MDG Hub requires project-
specific implementation
Client 3 Client 4

Public 201
Integration Scenarios
• Integration with Supplier Lifecycle Management (SAP-SLC)
• Integration with Customer Relationship Management (SAP-CRM)
• Integration with SAP Sales Cloud
• Integration with SAP Ariba Supplier Lifecycle and Performance
• Integration with Business Partner Screening (SAP-BPS)
• Global & local MD Hubs
• Technique
Integration Scenarios: SAP Sales Cloud
Summary

Customer data can be maintained in SAP Sales Cloud as well as in MDG-C; bi-directional
replication between SAP Sales Cloud and MDG-C is supported by using SOA Services.

SAP recommends using 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 across Sales Cloud, MDG, and operational ERP system
▪ Enable flow of transactional data (such as sales orders) between SAP Sales Cloud and ERP system

Best-practice integration scenarios are delivered as of:

▪ MDG 9.1 & MDG 9.2 (prerequisite is EHP8SP10)
▪ MDG on S/4HANA 1709 FPS2 & MDG on S/4HANA 1809

For more information about scenarios and system configuration, see SAP Help Portal for MDG

Public 203
Integration Scenarios: SAP Sales Cloud
Scenarios, Overview

New customer from SAP Sales Cloud

▪ No duplicate found in MDG
▪ Duplicate found in MDG: BP not yet in SAP Sales Cloud
▪ Duplicate found in MDG: BP already in SAP Sales Cloud

Change customer in SAP Sales Cloud

Create customer in MDG

Change customer in MDG

Merge two active customers in MDG

Public 204
Integration Scenarios: SAP Sales Cloud
Scenario: New Customer from SAP Sales Cloud and No Duplicate Found in MDG

BP 1000, DEF Corp., MDG 5001

BP 2000, ABC Corp.
1 Create new customer DEF Corp. in SAP Sales
BP 2001, DEF Corp.
Cloud; business with new customer can start
1
Sales Cloud Sales Orders 2 Send customer to MDG via SOA Service
(C4C) 7 ERP
Start Consolidation. No match found, so prepare
3 for adding customer

5 6 6 5
Activate data on MDG Hub, add new customer as
4
well as Key Mapping for MDG → Sales Cloud
2
Replicate customer data from MDG Hub to all
BP 5000: ERP 2000 5
BP 5000, ABC Corp. BP 5001: ERP 2001 connected client systems
BP 5001, DEF Corp. C4C 1000
6 Replicate key mapping to all client systems
MDG Hub 4
Store ERP number of customer in Sales Cloud
7
3 for proper replication of transactional data
Consolidation
Public 205
 Integration Scenarios: SAP Sales Cloud
Scenario: New Customer from Sales Cloud and Duplicate Found in MDG (BP Already in Sales Cloud)

BP 1000, DEF Corp., MDG 5001 BP 2000, ABC Corp. 1 Create new customer DEF Corp. in SAP Sales
BP 1001, ABC Corp., MDG 5000 BP 2001, DEF Corp. Cloud; business with new customer can start
BP 1002, DEF Corp., MDG 5001
2 Send customer to MDG via SOA Service
Sales Cloud 1
(C4C) 7
ERP 3 Start Consolidation. Match found against BP
in MDG / Sales Cloud, merge data
Activate data on MDG Hub, enhance Key
4
5 6 6 5 Mapping for existing customer resulting in two
2 BP 5000: ERP 2000
mappings towards Sales Cloud
C4C 1001
Replicate customer data from MDG Hub to all
BP 5001: ERP 2001 5
BP 5000, ABC Corp. C4C 1000 connected client systems
BP 5001, DEF Corp. C4C 1002
6 Replicate key mapping to all client systems
MDG Hub 4
Sales Cloud detects duplicate customers,
3 7 starts local merge, and marks superfluous
Consolidation customer as inactive (only if not yet replicated
Public
to ERP) 206
Integration Scenarios
• Integration with Supplier Lifecycle Management (SAP-SLC)
• Integration with Customer Relationship Management (SAP-CRM)
• Integration with SAP Sales Cloud
• Integration with SAP Ariba Supplier Lifecycle and Performance
• Integration with Business Partner Screening (SAP-BPS)
• Global & local MD Hubs
• Technique
Integration Scenarios: SAP Ariba Supplier Lifecycle and Performance (SLP)
Summary

Supplier data can be maintained in SAP Ariba as well as in MDG-S; bi-directional replication
between SAP Ariba Supplier Lifecycle and Performance (SLP) and MDG-S is supported by using
SOA Services.

SAP recommends using best-practice integration scenarios with the goal to:
▪ Optimize master data quality by using MDG processes like Consolidation and Central Governance
▪ Make sure supplier master data is in sync across SLP, MDG, and operational ERP system

Best-practice integration scenarios are delivered as of:

▪ MDG 9.2
▪ MDG on S/4HANA 1809 and above

For more information about scenarios and system configuration, see SAP Help Portal for MDG

Public 208
Integration Scenarios: SAP Ariba Supplier Lifecycle and Performance (SLP)
Scenarios, Overview

A) New supplier from SLP replicated during Request

▪ Scenario 1a: New supplier from SLP, No duplicate found in MDG
▪ Scenario 2a: New supplier from SLP, Duplicate found in MDG: BP not yet in SLP
▪ Scenario 3a: New supplier from SLP, Duplicate found in MDG: BP already in SLP
B) New supplier from SLP replicated after Registration or Qualification
▪ Scenario 1b: New supplier from SLP, No duplicate found in MDG
▪ Scenario 2b: New supplier from SLP, Duplicate found in MDG: BP not yet in SLP
▪ Scenario 3b: New supplier from SLP, Duplicate found in MDG: BP already in SLP
Scenario 4: Change supplier in MDG
Scenario 5: Change supplier in SLP
Scenario 6: Create supplier in MDG
Scenario 7: Merge two active suppliers in MDG

Public 209
Scenario 3b: New Supplier from SLP, Duplicate Found in MDG
BP Already in SLP

Initial situation: Supplier ABC Corp. already

BP 1001, ABC Corp., MDG 5001 known in MDG, ERP, and SLP (BP 1001)
BP 1002, ABC Corp., MDG 5001 BP 2001, ABC Corp.
Registration / Qualification of new supplier
1 ABC Corp. (1002) in SLP ignoring already
1 6
existing supplier ABC Corp. (1001);
Ariba SLP ERP
2 Send the supplier to MDG via SOA Service
Start Consolidation. Match found against
5 5 3 BP ABC Corp. (5001) existing in MDG /
ERP / SLP, merge data.
2 BP 5001, ABC Corp. BP 5001: ERP 2001 Activate data on MDG Hub, enhance Key
SLP 1001 4 Mapping for existing BP resulting in two
SLP 1002
mappings towards SLP
MDG Hub 4 Replicate supplier data from MDG Hub to all
5 connected client systems (including SLP)
Consolidation SLP notices that another supplier (1001)
3 6 refers to same MDG ID and therefore
inactivates duplicate supplier (1002).
Public 210
Scenario 5: Change Supplier in SLP

Change supplier name from ABC to BCD

BP 1001, BCD Corp., MDG 5001 BP 2001, BCD Corp. 1
in SLP

1 2 Send the supplier to MDG via SOA Service

Ariba SLP ERP Start Change Request, MD Specialist will
3 verify / correct the data and approve.
4 4 After activation of data in MDG replication
4 to all client systems including SLP will be
2 triggered.
BP 5001, BCD Corp. BP 5001: ERP 2001
SLP 1001

MDG Hub
Maintain Validate Approve Replicate 3
Central Governance

Public 211
Integration Scenarios
• Integration with Supplier Lifecycle Management (SAP-SLC)
• Integration with Customer Relationship Management (SAP-CRM)
• Integration with SAP Sales Cloud
• Integration with SAP Ariba Supplier Lifecycle and Performance
• Integration with Business Partner Screening (SAP-BPS)
• Global & local MD Hubs
• Technique
Integration Scenarios: Business Partner Screening (SAP-BPS)
Manage different type of content; is my business partner on a published list?

? OR OR OR

=
Politically exposed
Denied party Adverse Media No Hit
person

High risk:
Moderate risk: Business
No Business Enhanced
Due diligence o.k.
Due diligence

Some examples:
Some examples:
• US Denied
• 2003 Financial
party lists
Action Task
• DFAT Force on Money
(Australia) Laundering
(FATF)
• METI (Japan)
standard
• Consolidated
list(EU)

Public 213
Integration Scenarios: Business Partner Screening (SAP-BPS)
Why care about these parties?

$1.45 Billion in Penalties for Bank that Concealed Transactions

with Sanctioned Parties (March 2015)
The Justice Department announced March 12 that a global financial institution headquartered in Germany and its New York branch have agreed a
total of $1.45 billion in penalties for concealing hundreds of millions of dollars in transactions prohibited by U.S. sanctions laws on behalf of Iranian
and Sudanese businesses.
Source: http://www.strtrade.com/news-publications-economic-sanctions-penalties-German-bank-031715.html

Diebold agrees to Pay $25.2 Million MoneyGram, one of the world’s

Penalty (October 2013) largest remitters, fined $122,400
The SEC alleges that Diebold spent approximately $1.6 million on leisure trips,
entertainment, and other improper gifts for government bank officials in China. by AUSTRAC (Jan 2015)
During this same time period, the SEC alleges, Diebold spent over $147,000 on MoneyGram Payment Systems, has been fined A$122,400 for
leisure trips and entertainment for officials of government banks in Indonesia. As contraventions of Australia's anti-money laundering and counter-terrorism
alleged in the complaint, Diebold executives in charge of the company's financing laws.
operations in Asia knew of these improper payments, which were falsely recorded
Source: http://www.austrac.gov.au/media/media-releases/moneygram-one-
in Diebold's books and records as training or other legitimate business expenses world%E2%80%99s-largest-remitters-fined-122400-austrac
Source: http://www.justice.gov/opa/pr/diebold-incorporated-resolves-foreign-corrupt-practices-act-
investigation-and-agrees-pay-252

Coutts Bank has been fined £8.75m (March 2012)

Coutts Bank has been fined £8.75m and severely censured by the UK’s Financial Services Authority (FSA) for failing to undertake sufficient anti-money
Public
laundering checks on their customers. 214
Source: http://www.bbc.com/news/business-17512140
Integration Scenarios: Business Partner Screening (SAP-BPS)
Multiple country-specific sanctioned party lists
▪Department of Commerce Entity List - End User Requiring License (ERL)
▪15 CFR Part 744 Supplement No. 4
▪Department of Commerce Unverified List (RFC); 15 CFR Part 744.15
▪Department of Commerce Denials List (TDO);
▪Specially Designated Nationals and Vessels of: (31 CFR ex Parts 500-590)
▪Belarus, Congo, Cote d'Ivoire, Cuba, Iraq, Iran, Lebanon, Liberia, Libya,
▪Myanmar - Burma, North Korea, Somalia, Sudan, Syria, Western Balkans, Zimbabwe
▪Foreign Sanctions Evaders List
▪Weapons of Mass Destruction Proliferators
▪Non-SDN Palestinian Legislative Council
▪Specially Designated Terrorists
▪Specially Designated Global Terrorists
▪Specially Designated Narcotic Traffickers
▪Specially Designated Nationals Sergei Magnitsky
▪Transnational Criminal Organizations
▪Debarred List (DOS); 22 CFR Part 127.7 ITAR; Arms Export Control Act, Sec. 38
▪Missile Proliferators (MT); 22 CFR Part 126
▪Chemical and Biological Weapons Proliferators (CBW); 22 CFR Part 126
▪Designated Terrorist Organization (DTO); 22 CFR Part 126
▪Iran Nonproliferation Act of 2000 (inpa); 22 CFR Part 126
▪Iran, North Korea and Syria Nonproliferation Act
▪Sanctions for the Transfer of Lethal Military Equipment (lme); 22 CFR Part 126
▪Department of Commerce Unverified List - Red Flag Concerns (RFC)
▪15 CFR Part 732 Supplement No. 3.
▪European Union Sanctions List
▪Unverified List - "Red Flag"
▪Japanese End User List (Ministry of Economy, Trade and Industry - METI)
▪UK List - WMD End-Use Control: Licence Applications for Iran
▪Financial Crimes Enforcement Network list (FINCEN).
▪United Nations Security Council Sanctions (UNS)
▪Additional Non-Standard Offerings
▪GSA Debarred Bidders List - Reciprocal
▪GSA Debarred Bidders List -Non-Procurement
▪GSA Debarred Bidders List - Procurement)
▪Australian Consolidated List
▪Bank of England - Financial Sanctions
▪Canadian Restricted Entities
▪World Bank - List of Debarred/Ineligible Firms
▪FBI Most Wanted List
▪Swiss Restricted List (SECO)
▪Politically Exposed Persons

Public 215
Integration Scenarios: Business Partner Screening (SAP-BPS)
Achieve effective and efficient partner screening!

Monitor performance through Manage restricted party

dashboards, reports and KPIs lists and master data
Pre-
delivered
Rules

Enable
Rules

Simplified
Predictive
Rules
Rules Creation

SAP HANA

Manage alerts efficiently Define screening

strategies and
optimize using
calibration

Execute mass and real-time

screening and stop suspicious
business transactions

Public 216
Integration Scenarios: Business Partner Screening (SAP-BPS)
Three Scenarios

1) Decision in MDG 2) Consulting by Compliance 3) Decision in BPS

Expert, Decision in MDG
▪ Screening results shown ▪ Results from screening made ▪ Results from screening
as popup in MDG available in MDG in the notes interpreted in MDG via
▪ No involvement from BPS ▪ Final decision in MDG Customizing
organization ▪ No further actions by an MDG
specialist

Details about integration can be found in SAP Note 2326544

Public 217
Integration Scenarios: Business Partner Screening
1) Decision in MDG (Screening by Master Data Specialist)

Public 218
Integration Scenarios: Business Partner Screening
1) Decision in MDG (Screening by Master Data Specialist)

Compliance Check
– Screening automatically
executed in process steps
being activated.
– Popup appears in case of
suspicion; user can decide
about hit / no hit
– Hits are protocolled within BP
Screening.
– User is free how to continue
CR process independent of
decision about hit / no hit.

Public 219
Integration Scenarios: Business Partner Screening
2) Automatic screening: Consulting by Compliance Expert, Decision in MDG

Public 220
Integration Scenarios: Business Partner Screening
3) Automatic screening: Business Decision by Compliance Expert

Public 221
Integration Scenarios: Business Partner Screening (SAP-BPS)
Activate screening per Change Request Step

Enrichment
Implemented as Enrichment Spot
‘Address Screening’ with
corresponding adapter in MDG
Activate per CR Step
For each Change Request
Type, Screening can be activated
per Change Request Step
Deployment Options
BP Screening can run on MDG
instance (same HANA DB, different
NW AS) or on different instance

Public 222
Integration Scenarios
• Integration with Supplier Lifecycle Management (SAP-SLC)
• Integration with Customer Relationship Management (SAP-CRM)
• Integration with SAP Sales Cloud
• Integration with SAP Ariba Supplier Lifecycle and Performance
• Integration with Business Partner Screening (SAP-BPS)
• Global & Local MD Hubs
• Technique
Integration Scenarios: Global & Local MD Hubs
Govern global data on global MD Hub and application data on local systems

Client
S/4HANA 1 4
1 Client
MDG 3
Global MD Hub 2

MDG S/4HANA 2 Client

4
MDG 3
Client

Client

1 Maintain global data via MDG on Global MD Hub

2 Replicate global data to local systems and other client systems
3 Maintain application data via MDG on local systems
4 Replicate global and application data to connected client systems
Public 224
Integration Scenarios
• Integration with Supplier Lifecycle Management (SAP-SLC)
• Integration with Customer Relationship Management (SAP-CRM)
• Integration with SAP Sales Cloud
• Integration with SAP Ariba Supplier Lifecycle and Performance
• Integration with Business Partner Screening (SAP-BPS)
• Global & local MD Hubs
• Technique
Integration Scenarios: Technique
Interfaces for Data Replication and Data Load

Data Replication of BP / Customer / Supplier data via SOA Service

– Replicate BP data BusinessPartnerSUITEBulkReplicateRequest
– Return (lack of) success BusinessPartnerSUITEBulkReplicateConfirmation
– Replicate BP Relationships BusinessPartnerRelationshipSUITEBulkReplicateRequest
– Return (lack of) success BusinessPartnerRelationshipSUITEBulkReplicateConfirmation

Data Replication / Data Load via ALE

– Replicate ERP Vendors CREMAS / ADRMAS
– Replicate ERP Customers DEBMAS / ADRMAS / ADR2MAS / ADR3MAS
– Replicate Business Partner BUPA_INBOUND_MAIN_SAVE
– Replicate BP Relationships BUPA_INBOUND_REL_SAVE
– Load ERP Vendors CREMDM
– Load ERP Customers DEBMDM

Public 226
Integration Scenarios: Technique
Interfaces for Client Maintenance

Client Maintenance
– Search BP on MDG Hub BusinessPartnerBasicDataByElementsQueryResponse_In (synchronous)
MDG_BS_BP_SEARCH (RFC)
– Copy BP from MDG Hub BusinessPartnerSUITEReconciliationRequestConfirmation_In (synchronous)
MDG_BS_BP_DRF_EXTRACT_READ (RFC)
– Replicate changes to MDG Use SOA Services for Data Replication (see previous slide)
Configure MDG Hub to create Change Request with incoming data
(see Configuration Guide for MDG-S / MDG-C)

Key Mapping
– Read MDG key mapping KeyMappingBulkReplicateRequest_Out
KeyMappingBulkReplicateConfirmation_In
MDG_ID_QUERY_MATCHING (RFC)

Public 227
Integration Scenarios: Technique
Configure MDG Hub for Client Maintenance via SOA Service

MDG to generate Change Request / Consolidation Run for inbound SOA Services
– Call IMG for Data Replication Framework (transaction DRFIMG)
– Choose Data Replication → Define Custom Settings for Data Replication → Define Technical Settings →
Define Technical Settings for Business Systems
– Select client system and choose Define Bus. Systems, BOs
– Select BO Type 147 (Business Partner) and choose Define Bus. Systems, BOs, Communication Channel
– Change field Storage (Staging Area for Change Request) and Create / Change Template (for Consolidation)

Assign relevant Change Request Type to Business Activities BPPI / BPPU

Public 228
Agenda

Introduction

SAP Master Data Governance Capabilities

Function in Detail

Integration Scenarios

Solution Benefits

Public 229
SAP Master Data Governance
Consistent High-Quality Master Data for Your Entire Organization
SAP Master Data Governance is a state-of-the-art master data management application, providing preconfigured,
domain-specific master data governance to monitor and remediate eventual data quality issues, to centrally create, change,
and distribute, or to consolidate master data across your complete enterprise system landscape.
There are two versions: SAP Master Data Governance on SAP S/4HANA and SAP Master Data Governance (technically on SAP ERP 6.0).

Central governance or consolidation for consistent master data

▪ Enables centralized governance, compliance, and transparency of master data during
creation and change through integrated staging, approval, and central audit trail
▪ Delivers consistent definition, authorization, and replication of key master data entities
▪ Eliminates error-prone manual maintenance processes for master data in multiple
systems
▪ Supports consolidation of decentralized master data in any enterprise system landscape
to create best records and key mapping between duplicates
▪ Optionally combines consolidation with central governance for sustained master data
quality
Data quality
▪ Analyze process quality, manage and monitor data quality, and optionally integrate with
SAP HANA smart data quality, or SAP Data Services for quality, enrichment, and
remediation
Integration and reuse
▪ Native integration and openness to integrate 3rd-party services
▪ Reuse of SAP data model, existing business logic, and configuration for data validation
▪ Open application to manage your own master data flexibly also for non-SAP
environments

Public 230
SAP’s Understanding of a State-of-the-Art Master Data Governance Solution

• Deliver process-centric solution

• Workflow closely integrated into a framework for defining business rules
Solution • Full integration to SAP systems and integration services for non-SAP systems
Strategy • Deliver roles on a Web-based UI
Ensure • Deliver a Data Model proven by several applications & industries
Master Data • Reuse of existing processing logic and out-of-the-box data replication mechanisms
Governance
• User-centricity: Central work center for the maintenance of materials
Basic • Governance: Change requests with built-in approval process
Principles • Workflow: standardized but flexible processes incl. rules management and tracking
• Architecture: Staging area to maintain inactive versions of material data

– Search & Display

– Create, Change, Multi-Record Processing, Mass Change, Parallel Change Requests,
Mark for Deletion
Common – Worklists (My Change Request, Display Change Requests, Change Documents)
Services – Duplicate Check
– Data Replication with Key Mapping and Value Mapping
– File Upload / Initial Load
– Extensibility of Data Model & User Interface
– Deployment on top of operational SAP system or as standalone hub
Public 231
Appendix: Customer Connection
and Downport
Contribute – Visit the SAP Customer Influence Site

The SAP Customer Influence site gathers all existing influencing Visit the
opportunities in one single entry channel: landing pages
▪ To participate, first create your user account to logon and
activate Single-Sign-On for easy access (Get started with SAP MDG
instructions here). (for S/4HANA 1909)
SAP MDG 2019
▪ Define your “area(s) of interest“ here by clicking the follow (for S/4HANA 2020)
button. You will receive regular email updates and
notifications on topics within the chosen area(s). You can edit SAP MDG 2020
your choices anytime. (for S/4HANA 2021)
SAP MDG 2021/2022
▪ Get active by searching & voting for or commenting on the (for S/4HANA 2022)
already existing improvement request(s) from which your SAP MDG 2023
company would benefit, or start submitting your own (for S/4HANA 2023)
improvement requests.
▪ Navigate using the filter bar on the left to select SAP Customer
Connection project(s) (here) or other influencing type, by
product, LOB…or use free text search bar on top of screen.
Public 233
MDG Projects in the Customer Connection Program

CC Projects Scope Start Start Start Delivery Deliveries

Collection Selection Development Call
SAP MDG SAP MDG, Central Governance, Mass Processing
May 8, 2018 June 30, 2018 Sep 18, 2018 June 12, 2019
25
(for S/4HANA 1909) and Consolidation, all domains Improvements

SAP MDG, Central Governance, Mass Processing,

SAP MDG 2019 Consolidation and Data Quality Management, all Apr 12, 2019 June 30, 2019 Sep 18, 2019 July 15, 2020
28
(for S/4HANA 2020) Improvements
domains
SAP MDG, Central Governance, Mass Processing,
SAP MDG 2020 Consolidation and Data Quality Management, all July 29, 2020 Oct. 7, 2020 Dec 2, 2020 July 13, 2021
25
(for S/4HANA 2021) Improvements
domains (same as 2019)
SAP MDG, Central Governance, Mass Processing,
SAP MDG 2021/2022 Consolidation and Data Quality Management, July 20, 2021 Oct. 08, 2021 Dec 08, 2021 July 19, 2022
23
(for S/4HANA 2022) Improvements
domains: Material, BP, FIN, Custom Objects
SAP MDG, Central Governance, Mass Processing,
SAP MDG 2023 Consolidation and Data Quality Management, July 27, 2022 Oct 24, 2022 Dec 14, 2022
July 2023
(for S/4HANA 2023) (planned)
domains: Material, BP, FIN, Custom Objects

Thank you for the nice and successful collaboration throughout

the time as well as your trust in us!

Public 234
Details and Demos about Improvements in S/4HANA 1909

ID Title Note/SP/Release Lowest Releases

​212430 MDG-BP: Improve error handling in the UI SAP Note 2765664 From S/4HANA 1511 and from MDG 8.0​

213216 Auto-resizing of columns in the MDG Duplicate popup screen SAP Note 2667744 From S/4HANA 1511 and from MDG 6.1

212427 Workflow Tracker SAP Note 2765664 From S/4HANA 1511 and from MDG 8.0

213090 End of Workflow SAP Note 2765664 From S/4HANA 1511 and from MDG 8.0

212952 MDG: Out-of-the-box application to search CRs by business data SAP Note 2765664 From S/4HANA 1511 and from MDG 8.0

Demo for
Demo for
Google-Like Search in MDG
Out-of-the-Box CR Search
Autoresize Duplicate Popup
Improved Error Message Handling for MDG-BP/C/S
Additional Steps After Activation
Change Request Tracker
Change Request Tracker
Follow-Up Change Request

Public 235
Details about Improvements in S/4HANA 2020

ID Title Note/SP/Release Lowest Releases

* MDG-BP/C/S: Enhanced Data Model and UIs - General Release S/4HANA 2020
MDG-BP/C/S: Enhanced Data Model and UIs - Ratings & Release
* S/4HANA 2020
Creditworthiness
* MDG-C/S: Enhanced Data Model and UIs - Long Incoterms Release S/4HANA 2020

* MDG-C: Enhanced Data Model and UI - Credit Scoring Release S/4HANA 2020

231082 MDG-BP: Central Delete / Block Message - Business Partner SAP Note 2888104 and SAP Note 2843946 From S/4HANA 1610 and from MDG 9.0

231767 MDG-All: Change Request search improvement SAP Note 2888104 and SAP Note 2829640 From S/4HANA 1511 and from MDG 8.0

(*) improvement independent from Customer Connection

Public 236
Details about Improvements in S/4HANA 2021

ID Title Note/SP/Release Lowest Releases

255133 Validation of VAT registration number of EU business partners in MDG SAP Note 3085468 As of S/4HANA 1909

* MDG-C: Multiple Address Handling for Customer Master Data Release As of S/4HANA 2021

* MDG-BP/C/S: Address-Independent Communication Data Release As of S/4HANA 2021

* MDG-BP/C/S: Enhancements for Financial Services Business Partner Release As of S/4HANA 2021

252141 MDG-ALL: Reset / Recall Change request (again) SAP Notes 3043582, 3018966 As of S/4HANA 1809 and MDG 9.2
Possibility to customize default Display option in "Display Change
252206 SAP Notes 3043582, 3000012 As of S/4HANA 1809 and MDG 9.2
Documents"
252631 Have the operator 'is' operating as "is", not as "contains" SAP Notes 3043582, 3036524 As of S/4HANA 1809 and MDG 9.2

253984 Display of archived change documents (again) SAP Note 2995802 As of S/4HANA 1809 and MDG 9.2

(*) improvement independent from Customer Connection

Public 237
Details about Improvements in S/4HANA 2022

ID Title Note/SP/Release Lowest Releases

270658 Missing standard fields in the MDG data model Release As of S/4HANA 2022
Enabling end-users to add valid-from / valid to dates to both addresses
269943 Release As of S/4HANA 2022
and address usages
* Using Derivation Scenarios for BP/Customer/Supplier Release As of S/4HANA 2022
270216 Enable download functionality of all error messages in excel file SAP Notes 3194967, 3129191, 3146760 As of S/4HANA 1809 and MDG 9.2
As of S/4HANA 1809 SP04 and MDG
270207 File down- and upload with EXCEL files SAP Notes 3194967, 3155366, 3137753
9.2
Enable convenience API with option to create change request by
270409 SAP Notes 3199378, 3208250 As of S/4HANA 1809 and MDG 9.2
reference
270656 Perform duplicate check on demand SAP Notes 3194967, 3156812 As of S/4HANA 1809 and MDG 9.2
269930 Number of records/entries functionality in MDG-NWBC SAP Notes 3194967, 3196973, 3216162 As of S/4HANA 1809 and MDG 9.2
MDG - Enhancement of custom columns in Standard Layout of the result
270653 Online Help All
list of found duplicates
271160 Workflow tracker – improvements for parallel workflows SAP Notes 3094459, 3168316, 3203982 As of S/4HANA 1511 and MDG 8.0
272878 Search operator 'Contains' should not be case sensitive SAP Notes 3216762 As of S/4HANA 1809

Demo for
• Display the Number of Search Result Records
(*) improvement independent • Time Dependency for Specific Business Partner Data
• Data Model Aligned With SOAP Service
from Customer Connection • Perform Duplicate Check on Demand
• Change Request Tracker Improved for Parallel Workflow Steps
Public 238
MDG Customer Connection SAP Notes

Some of the new functions developed as a result of requests submitted during the Customer
Connection for MDG require activating via custom business functions which are listed in the
corresponding SAP notes.

▫ 2765664 - MDG Customer Connection 2018

▫ 2888104 - MDG Customer Connection 2019
▫ 3043582 - MDG Customer Connection 2020
▫ 3194967 - MDG Customer Connection 2021/2022

Public 239
Learn More About SAP Master Data Governance

Public 240
Thank you.
Contact information:

SAP Product Management

Join online:
MDG Community Network: https://www.sap.com/community/topics/master-data-governance.html

© 2023 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to SAP Materials for general audiences.