Deployment Recommendations for

SAP Master Data Governance

(related to SAP MDG on ERP and SAP MDG on S/4HANA)
SAP SE
 Disclaimer

This presentation outlines our general product direction and should not be relied on in making a purchase
decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP
has no obligation to pursue any course of business outlined in this presentation or to develop or release
any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future
developments are subject to change and may be changed by SAP at any time for any reason without
notice. This document is provided without a warranty of any kind, either express or implied, including but
not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-
infringement. SAP assumes no responsibility for errors or omissions in this document, except if such
damages were caused by SAP intentionally or grossly negligent.

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

Agenda

Introduction
▪ Methodology & Scope of Landscape Recommendations

Basic Landscape Setups

▪ Recommendations for SAP Master Data Governance
(based on current releases SAP MDG 9.2 / SAP MDG on S/4HANA 1909)

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Introduction
Methodology & Scope of Landscape Recommendations
System Landscapes at Customers
Designing the Optimal Landscape Layout

Product Roadmaps
SAP ERP SAP SRM SAP SCM SAP CRM

ERP SRM SCM CRM

Components Components Components Components

ECC SRM SCM CRM

Business Aspects Server

AS ABAP ABAP
Server

AS ABAP ABAP
Server

AS ABAP ABAP
Server

AS ABAP ABAP

SAP SAP Business Suite

Solution Manager Backend Systems
SolMan Content

Solution Mng
Component

SLD JEE

ABAP
Dual Stack SAP NetWeaver Hubs

Application Portal Business Warehouse BEx Web Process Integration

SEM BICS ESR Content

Additional SAP BS Instance

Architectural Portal
Content
Central BI
Content
BI JAVA ESR&SR

PI
Deployment Recommendations
Strategy EP Core
AS JAVA
ADOBE

JEE
BW

AS ABAP ABAP
EP

AS JAVA JEE
SLD

PI Dual Stack
JEE

ABAP
for SAP Products
Operations
Security
Costs

Speed of
Innovation

Performance &
Scalability
Legal Aspects Solution Landscape
…
of Customer
OS/DB platform SLA &
strategy Availability
Technical Documentation
(Planning, Installation &
IT Aspects Configuration Guides, etc.)

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

Deployment Recommendations for SAP Products
Guiding Principles

SAP ERP SAP SRM SAP SCM SAP CRM

ERP SRM SCM CRM

Components Components Components Components

ECC SRM SCM CRM

Server Server Server Server

ABAP ABAP ABAP ABAP

AS ABAP AS ABAP AS ABAP AS ABAP

SAP SAP Business Suite

Solution Manager Backend Systems
SolMan Content

Solution Mng
Component

SLD JEE

ABAP
Dual Stack SAP NetWeaver Hubs

Application Portal Business Warehouse BEx Web Process Integration

Additional SAP BS Instance

Portal
Content
SEM

Central BI
Content

BW
BICS

BI JAVA
ESR Content

ESR&SR

PI
High-Level Guidance
ADOBE

for optimized
EP Core EP SLD JEE

JEE ABAP JEE ABAP

AS JAVA AS ABAP AS JAVA PI Dual Stack

Landscape Layouts
Deployment Recommendations
Solution Landscape
for SAP Products
of Customer

 Allow flexibility by offering different deployment options (not one-size-fits-all)

 Provide guidance by rating different options
 Ease decisions by listing pros & cons
 Simplify consumption of information by using a common methodology
 Increase reliability by considering SAP product strategy, achieved landscape qualities and
cross-product alignment
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6
Ease Landscape Planning By Stronger Guidance
Used Methodology
Clear recommendations by categorization of deployment options
Possible Exception
◼ Only useful for specific use cases General Recommendation
Option
◼ Supported by SAP, but limitations III ◼ Best choice for majority of typical
might occur
landscape use cases
Option II Option I ◼ Recommended by SAP’s strategy
Reasonable Alternative ◼ Accepted by a wide base of

◼ Useful choice for certain use customers

cases or customer scenarios
◼ Supported and confirmed by
SAP’s strategy

▪ Outlining main important aspects

Goal ▪ Optimal trade-off between flexibility and simplicity
▪ Applied to main building blocks of SAP products

▪ Alternative deployment options typically have different pros & cons

Consider ▪ Customer individual assessment is not compensated
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7
SAP Master Data Governance
Tackling the master data challenge with consolidation and central governance

Get data clean

Consolidate master data Centrally govern and
from de-central sources distribute master data
LoB processes

On-premise systems
De-central
IT landscape
SAP MDG
Cloud applications

Cloud
3rd party apps

Other LoB

Mergers and Acquisitions

Keep data clean

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

 Scope of Landscape Recommendations
Building Blocks in System Landscapes for SAP Master Data Governance
Example:
Considered main usage scenarios
SAP MDG MDG in
SAP S/4HANA
▪ SAP MDG is deployed as master data hub
MDG
▪ SAP MDG is co-deployed with SAP ERP or S/4HANA
or MDG
▪ SAP MDG uses SAP HANA for search & matching
ECC S/4HANA
Server Server

ABAP ABAP
AnyDB AS ABAP
Considered main building blocks
▪ SAP MDG (based on SAP ERP or SAP S/4HANA)
SAP HANA
System ▪ SAP SLT
SAP Business
Suite
SAP System
Business
Suite System
MDG Scenarios ▪ SAP HANA
SAP BS
Application
SAP BS
SAP HANA ▪ SAP Business Suite as example for master data client
▪
Application
ABAP
ABAP
Non SAP application as example for master data client
NON-SAP System
main role of this
Role
system
NON-SAP JEE

Application

SAP system with available platform

own database technology

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

Major Changes or Updates
Summary

Major changes or updates to former landscape recommendations

Type of change Former Status New Status Reason Reference

Deployment of DQM
Additional product New slide with DQM
Enhancement ./. components with SAP MDG
offering deployment options
included

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

Overview Landscape Scenarios

Landscape Scenario I:
Distributed System Landscape with only local SAP ERP / S/4HANA systems
▪ Customer landscape contains different local SAP ERP / S/4HANA or NON-SAP application systems
▪ No central SAP ERP / S/4HANA system in place
▪ Governance processes for master data are going to be implemented

Landscape Scenario II:

Distributed System Landscape with existing central SAP ERP / S/4HANA system
▪ Customer landscape contains a single SAP ERP / S/4HANA system only (simple system landscape)
▪ Or customer landscape contains a dedicated central SAP ERP / S/4HANA system serving central processes against
local SAP ERP / S/4HANA systems, other SAP Business Suite systems or NON-SAP application systems
▪ Governance processes for master data are going to be implemented

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

Basic Landscape Setups
▪ Recommendations for SAP Master Data Governance
Landscape Scenario I

Landscape Scenario I:
Distributed System Landscape with only local SAP ERP / S/4HANA systems
▪ Customer landscape contains different local SAP ERP / S/4HANA or NON-SAP application systems
▪ No central SAP ERP / S/4HANA system in place
▪ Governance processes for master data are going to be implemented

Landscape Scenario II:

Distributed System Landscape with existing central SAP ERP / S/4HANA system
▪ Customer landscape contains a single SAP ERP / S/4HANA system only (simple system landscape)
▪ Or customer landscape contains a dedicated central SAP ERP / S/4HANA system serving central processes against
local SAP ERP / S/4HANA systems, other SAP Business Suite systems or NON-SAP application systems
▪ Governance processes for master data are going to be implemented

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

Deployment of SAP Master Data Governance
Master data hub based on SAP HANA
General Recommendation
◼ Deploy SAP MDG as separate master data hub on SAP HANA
◼ No operational usage of embedded SAP ERP / S/4HANA
◼ Use SAP HANA as primary DB and for search, standardization & matching

Application Benefits
Example System
◼ Independent speed of innovation for new SAP MDG capabilities
NON SAP
Master Data Hub ◼ Clear system of record
SAP ERP A ◼ Easy setup of / migration to SAP MDG running on SAP HANA since
MDG
distribution of existing SAP ERP / S/4HANA landscape is not touched
master data ERP
◼ No additional SAP HANA for search
ABAP
ERP or S/4H AnyDB
◼ No additional index server for address validation & duplicate check
ABAP
AS ABAP
SAP ERP B or
◼ No SLT replication of data compared to deployment with SAP HANA
primary DB connection SAP S/4HANA as sidecar
ERP or S/4H
SAP HANA
System for MDG AS ABAP
ABAP
Considerations
MDG Search & ◼ Additional MDG system required
Matching

SAP HANA
SAP HANA System ◼ Consider reusing SAP HANA according to white list (see SAP Note
for ERP B or S/4H
1826100 )
SAP HANA

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

 Deployment of SAP Master Data Governance
Master data hub based on any DB with optional use of SAP HANA
Reasonable Alternative
◼ Deploy SAP MDG as separate master data hub on any DB
◼ No operational usage of embedded SAP ERP
◼ Connected to SAP HANA with SAP SLT for search & duplicate check

Application
Benefits
Example System ◼ Independent speed of innovation for new SAP MDG capabilities
NON SAP
Master Data Hub
◼ Clear system of record
SAP ERP A ◼ Easily extended with SAP HANA as sidecar
distribution of
MDG
master data
ERP
Considerations
ABAP
AnyDB
ERP
◼ Additional MDG system required
◼ Consider reusing SAP HANA according to white list (see SAP Note
ABAP
AnyDB secondary
DB SAP ERP B or
connection SAP S/4HANA 1826100 )
SAP HANA
ERP or S/4H ◼ Optional usage of other search providers such as SAP Enterprise
System
AS ABAP
ABAP
Search (Embedded Search) or SAP Business Objects Data Services
MDG Search & is also supported
Duplicate Check
SLT replication of
master data for search SAP HANA SAP HANA System
◼ No usage of HANA in SAP MDG, consolidation (Optional usage of
& duplicate check for ERP B or S/4H SAP Business Objects Data Services is also supported for
SAP HANA standardization & matching.)
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15
 Deployment of SAP Master Data Governance
Co-deployed with local SAP ERP / S/4HANA systems and locally used
Possible Exception
◼ Co-Deploy SAP MDG with SAP ERP on any DB or SAP HANA or co-deploy with S/4HANA
◼ SAP ERP / S/4HANA is also operationally used
◼ SAP MDG is locally used in every SAP ERP / S/4HANA system to govern only local master data or
each of these systems governs different kind of master data within the complete system landscape

Example Benefits
SAP ERP with SAP S/4HANA
◼ No separate systems for SAP MDG
local MDG with local MDG ◼ No replication of master data to SAP ERP / S/4HANA
MDG MDG ◼ Easily extended with SAP HANA as sidecar for SAP ERP
secondary DB
ERP connection S/4H

ABAP ABAP
Considerations
AnyDB AS ABAP
SAP HANA ◼ No central but distributed governance of master data; might be
primary DB connection
System useful as a preliminary step for later change to a central MDG hub
MDG Search &
Duplicate Check
SAP HANA System ◼ Risk: no integration between domains
SLT replication of for S/4H
master data for search SAP HANA MDG Search & ◼ No global duplicate detection / duplicate prevention possible
& duplicate check Matching
◼ SAP HANA usage for MDG depends on existing SAP HANA
SAP HANA deployment of individual SAP ERP / S/4HANA systems
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16
Deployment of SAP Master Data Governance
Co-deployed with one local SAP ERP / S/4HANA system and centrally used
Possible Exception
◼ Co-Deploy SAP MDG with SAP ERP on any DB or SAP HANA or co-deploy with S/4HANA
◼ SAP ERP / S/4HANA is also operationally used
◼ SAP MDG is centrally used, but co-deployed with a local SAP ERP / S/4HANA system

Example
SAP ERP B or Application
Benefits
SAP ERP A
distribution of
SAP S/4HANA
distribution of
System ◼ No separate system for SAP MDG
with central MDG
master data master data
ERP NON SAP

AnyDB
ABAP
MDG
Considerations
ERP or S/4H ◼ It may be difficult to choose the local SAP ERP / S/4HANA
ABAP
system that shall serve the SAP MDG Add-On
AS ABAP
◼ So far locally used SAP ERP / S/4HANA becomes central
primary DB connection
usage for other SAP ERP / S/4HANA systems (→ relevant
SAP HANA System
master data and customizing need to be loaded)
for ERP B or S/4H
◼ SAP HANA usage for SAP MDG depends on existing SAP
MDG Search &
Matching HANA deployment of individual SAP ERP / S/4HANA
systems
SAP HANA

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 17

 Deployment of SAP Master Data Governance
Master data hub and SAP ERP / S/4HANA deployed on same SAP HANA DB
Not Supported Today
◼ Deploy SAP MDG as separate master data hub on SAP HANA
◼ No operational usage of embedded SAP ERP / S/4HANA
◼ Use SAP HANA as primary DB and for search & duplicate check
◼ Governed SAP ERP / S/4HANA systems using same SAP HANA DB as primary DB

distribution of master data

Example Master Data Hub Implications
SAP S/4HANA

SAP ERP
◼ Today co-deployment of two or more SAP ERP /
MDG
S/4H S/4HANA systems on the same SAP HANA DB not
ERP AS ABAP
ABAP supported
ERP or S/4H AS ABAP
ABAP ◼ Applications supporting co-deployments with SAP
Business Suite on same SAP HANA DB are listed in
AS ABAP
ABAP
SAP Note 1826100
primary DB connections
Considerations
SAP HANA System for MDG, ERP and S/4H ◼ With SAP HANA SPS9 the new feature MDC (multi
tenant DB container) has been introduced. This feature
MDG Search &
Matching
ERP S/4H allows running SAP MDG and SAP ERP / S/4HANA in
SAP HANA
separate DB tenants of the same HANA server. Refer
also to note 1774566
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 18
 Deployment of SAP Master Data Governance
SAP MDG on any DB with optional use of SAP HANA for consolidation
Not Supported Today
◼ Deploy SAP MDG on any DB
◼ Connected to SAP HANA with SAP SLT for standardization & matching

Example

Considerations
MDG
◼ Optional usage of SAP Business Objects Data Services is
secondary supported for standardization & matching
ERP DB connection

ABAP
AnyDB
SAP HANA
System
MDG
Standardization
SLT replication of master & Matching
data for standardization SAP HANA
& matching

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

Landscape Scenario II

Landscape Scenario I:
Distributed System Landscape with only local SAP ERP / S/4HANA systems
▪ Customer landscape contains different local SAP ERP / S/4HANA or NON-SAP application systems
▪ No central SAP ERP / S/4HANA system in place
▪ Governance processes for master data are going to be implemented

Landscape Scenario II:

Distributed System Landscape with existing central SAP ERP / S/4HANA system
▪ Customer landscape contains a single SAP ERP / S/4HANA system only (simple system landscape)
▪ Or customer landscape contains a dedicated central SAP ERP / S/4HANA system serving central processes against
local SAP ERP / S/4HANA systems, other SAP Business Suite systems or NON-SAP application systems
▪ Governance processes for master data are going to be implemented

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

 Deployment of SAP Master Data Governance
Co-deployed with SAP ERP / S/4HANA in single system based on SAP HANA
General Recommendation
◼ Co-Deploy SAP MDG with SAP ERP / S/4HANA within single SAP ERP / S/4HANA landscape
◼ SAP ERP / S/4HANA is operationally used
◼ Based on SAP HANA as primary DB for SAP MDG and SAP ERP / S/4HANA

Single SAP ERP

Example or SAP S/4HANA Benefits
with MDG
◼ No additional system for SAP MDG
MDG
◼ UI continuity for maintenance of global and local attributes
◼ Process continuity (no latency for replication)
ERP or S/4H

ABAP
AS ABAP
Considerations
primary DB connection ◼ SAP MDG controls master data of single SAP ERP / S/4HANA
application only
SAP HANA System
for ERP or S/4H &
for MDG
MDG Search &
Matching

SAP HANA

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

 Deployment of SAP Master Data Governance
Co-deployment with SAP ERP for single SAP ERP landscape based on any DB
Reasonable Alternative
◼ Co-Deploy SAP MDG with SAP ERP within single SAP ERP landscape
◼ SAP ERP is operationally used
◼ Based on any DB (optional usage of SAP HANA as sidecar)

Example Benefits
Single SAP ERP
with MDG ◼ No additional system for SAP MDG
MDG ◼ UI continuity for maintenance of global and local attributes
◼ Process continuity (no latency for replication)
secondary
ERP DB connection ◼ Easily extended with SAP HANA as sidecar
ABAP
AnyDB
SAP HANA Considerations
System
MDG Search &
◼ SAP MDG controls master data of single SAP ERP application
Duplicate Check
SLT replication of ◼ No usage of HANA in SAP MDG, consolidation (Optional usage
master data for search SAP HANA of SAP Business Objects Data Services is also supported for
& duplicate check standardization & matching.)

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

 Deployment of SAP Master Data Governance
Master data hub based on SAP HANA, separately deployed from central system
General Recommendation
◼ Deploy SAP MDG as separate master data hub, additionally deployed to central SAP ERP /
S/4HANA within multiple SAP ERP / S/4HANA landscape, based on SAP HANA
◼ No operational usage of embedded SAP ERP / S/4HANA
◼ Use SAP HANA as primary DB and for search, standardization & matching

Example
Central ERP
Application
System
Benefits
ERP
NON SAP ◼ Independent speed of innovation
ABAP
AnyDB
◼ Clear system of record
Master Data Hub
distribution of
master data ◼ Easy setup of / migration to SAP MDG running on SAP HANA
MDG
SAP ERP A
since existing SAP ERP / S/4HANA landscape is not touched
ERP
◼ No SLT replication of data compared to deployment with SAP
ERP or S/4H AnyDB
ABAP
HANA as sidecar
ABAP
AS ABAP
SAP ERP B or
primary DB connection SAP S/4HANA Considerations
ERP or S/4H ◼ Additional MDG system required
SAP HANA
◼ Higher administration effort
ABAP
System for MDG AS ABAP
MDG Search &
Matching
SAP HANA System
SAP HANA
for ERP B or S/4H
SAP HANA

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 23

 Deployment of SAP Master Data Governance
Master Data hub co-deployed with central SAP ERP / S/4HANA on SAP HANA
Reasonable Alternative
◼ Co-Deploy SAP MDG with central SAP ERP / S/4HANA on SAP HANA
◼ SAP ERP / S/4HANA is also operationally used as central system
◼ Use SAP HANA as primary DB and for search, standardization & matching

Application
System
Example Central
Benefits
SAP ERP or NON SAP
SAP S/4H &
Master Data Gov. distribution of ◼ No additional system for SAP MDG
master data
◼ No additional SAP HANA for search & matching
MDG
SAP ERP A ◼ No replication of master data to central SAP ERP / S/4HANA
ERP or S/4H ERP ◼ No SLT replication of data compared to deployment with
AS ABAP
ABAP
AnyDB
ABAP SAP HANA as sidecar
primary DB connection
SAP ERP B Considerations
SAP HANA System ◼ Existing central SAP ERP system needs to be migrated to SAP
for ERP or S/4H ERP
& MDG HANA
ABAP
MDG Search & AS ABAP
Matching

SAP HANA
SAP HANA System
for ERP B
SAP HANA
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 24
 Deployment of SAP Master Data Governance
Master Data hub co-deployed with central SAP ERP on any DB
Possible Exception
◼ Co-Deploy SAP MDG with SAP ERP on any DB
◼ SAP ERP is also operationally used as central system
◼ Connected to SAP HANA with SAP SLT for search & duplicate check

Application
Example System Benefits
NON SAP ◼ No additional systems for SAP MDG
Central ERP &
Master Data Gov. distribution of ◼ No replication of master data to central SAP ERP
master data SAP ERP A
MDG ◼ Easily extended with SAP HANA as sidecar
ERP

ERP AnyDB
ABAP
Considerations
AnyDB
ABAP
secondary
◼ Additional SAP HANA system might be required
DB
connection
SAP ERP B ◼ Consider reusing SAP HANA according to white list
ERP ◼ Optional usage of other search providers such as SAP Enterprise
SAP HANA
System ABAP
Search (Embedded Search) or SAP Business Objects Data Services
MDG Search &
AS ABAP
is also supported
Duplicate Check
SLT replication of ◼ No usage of HANA in MDG, consolidation (Optional usage of SAP
master data for search &
duplicate check
SAP HANA SAP HANA System
for ERP B
Business Objects Data Services is also supported for standardization
SAP HANA & matching.)
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 25
Additional Considerations
▪ Recommendations for SAP Master Data Governance
Additional Considerations for MDG hub co-deployed with ERP

A co-deployment of MDG with an operational ERP system is not possible

• In a client where time dependency is required for the Business Partner in ERP

• If “SRM One Server” is also deployed

• If customizing cannot be harmonized in relevant areas (e.g. material valuation)

A co-deployment of MDG with an operational ERP system is restricted

• If co-deployed with certain industry solutions (refer to notes 1690202 and 2392135) or add-ons

• By the effort and feasibility to harmonize and enhance customizing / master data / authorizations /
customer extensions (especially if other systems will be connected to the MDG system) between the MDG
applications and the operational ERP system

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

Additional Considerations for MDG hub co-deployed with ERP

Additional benefits of the co-deployment of MDG with an operational ERP system

• UI continuity: all local attributes can be maintained in the MDG user interfaces because all checks required
for the local attributes (may depend on transactional data) are available in the ERP system
• Process continuity: no latency for data replication, no cross-system monitoring
• No system integration between MDG hub and ERP required → no costs for implementation and monitoring
of replication interfaces
• No additional integration effort with respect to specific external services such as translation management

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

Additional Considerations for separate MDG hub

Additional benefits of separate MDG hub

• Allows fresh start with cleansed data
• Less alignment on system maintenance cycles and faster innovation cycles possible
• No impact of MDG on system load in operational ERP (and vice versa)
• Higher flexibility / additional options when it comes to harmonization or mapping of customizing
• The ERP system is kept free of non-ERP data (data that is required to serve non-ERP or non-SAP
systems)
• More flexibility for master data lifecycle management
• Active area of MDG hub is additional staging (might for example be useful for introduction of new products)
• Master data may be archived in operational systems and is kept in MDG hub

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

Additional Considerations for separate MDG hub

Drawbacks of separate MDG hub

• Additional hardware and maintenance costs
• Initial load of master data, ongoing additional replication of master data to operational ERP
• Initial load and synchronization of customizing
• Meta data is sometimes maintained multiple times or at least at different places

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

Additional Considerations for DB

SAP MDG 9.2 provides applications for central governance and for consolidation & mass
processing.

MDG, central governance works best …

▪ with SAP HANA as primary DB. Using a different primary DB leads to minor restrictions. Most of them can be
compensated with the additional usage of SAP HANA as a sidecar for search & duplicate check.

MDG, consolidation & mass processing works best …

▪ with SAP HANA as primary DB. Not using SAP HANA leads to major restrictions, in especially when looking
at performance. Using SAP HANA as sidecar is not supported. Customers who are interested in MDG,
consolidation but do not want a separate SAP HANA system for MDG should consider the MDC feature of
SAP HANA SPS9 (see note 1774566).

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

Additional Considerations for Standardization & Matching

Concerning standardization & matching (for BP / Address data) the following options exist:

1. In case SAP MDG runs on SAP HANA as primary DB use SAP HANA Smart Data Quality (SDQ)
with primary connection to SAP HANA. Benefit: Simplified setup and maximum performance.

2. In case SAP MDG runs on any DB use SAP Business Objects Data Services.

Refer to note 2535239 for additional information on supported scenarios of SAP DQM.

Note: SAP HANA SDQ is not supported when HANA is used as a sidecar with secondary DB
connection.

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

Additional Considerations for S/4HANA on premise

Starting with S/4HANA OP 1511, SAP MDG is part of S/4HANA OP called SAP S/4HANA Master Data
Governance.

This means customers have the choice to use SAP MDG as add-on for SAP ERP or as part of S/4HANA OP.
This decision is independent of the decision to use a separate master data hub or to do a co-deployment with
the operational S/4HANA processes.
• SAP S/4HANA Master Data Governance 1511 includes capabilities of SAP MDG 8.0 (see also RIN
2214181).
• SAP S/4HANA Master Data Governance 1610 includes capabilities of SAP MDG 9.0 (see also RIN
2349002).
• SAP S/4HANA Master Data Governance 1709 provides new capabilities which are partly down-ported to
SAP MDG 9.1 (see also RIN 2495849).
• SAP S/4HANA Master Data Governance 1809 provides new capabilities which are partly down-ported to
SAP MDG 9.2 (see also RIN 2668153).
• SAP S/4HANA Master Data Governance 1909 provides new capabilities which are partly down-ported to
SAP MDG 9.2 (see also RIN 2817330).
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 33
Additional Considerations for S/4HANA OP

The general recommendation is to use SAP S/4HANA Master Data Governance.

Benefits
• Innovations are available earlier as part of S/4HANA.

• Not all innovations will be available on SAP ERP. Over time, the gap increases.

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

Thank you
Follow us

www.sap.com/contactsap

© 2020 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/copyright for additional trademark information and notices.