You are on page 1of 28

Deployment Recommendations for

SAP Master Data Governance 7.0


SAP AG, January 2014

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.

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

Agenda
Introduction
Methodology & Scope of Landscape Recommendations

Basic Landscape Setups


Recommendations for SAP Master Data Governance 7.0

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

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
Components

SRM
Components

SCM
Components

CRM
Components

ECC
Server

Business Aspects

AS ABAP

SRM
Server
ABAP

AS ABAP

SCM
Server
ABAP

AS ABAP

CRM
Server
ABAP

AS ABAP

ABAP

SAP Business Suite


Backend Systems

SAP
Solution Manager
SolMan Content
Solution Mng
Component

SLD
Dual Stack

JEE

ABAP

SAP NetWeaver Hubs


Application Portal

Business Warehouse
SEM

BEx Web

Process Integration

BICS

ESR Content

BI JAVA

ESR&SR

EP

SLD

Additional SAP BS Instance


Central BI
Content

Portal
Content

Architectural
Strategy

EP Core

AS JAVA

Operations
Costs

PI

BW

ADOBE
JEE

AS ABAP

ABAP

AS JAVA

JEE

PI Dual Stack

JEE

ABAP

Deployment Recommendations
for SAP Products

Security
Speed of
Innovation

Performance &
Scalability

Legal Aspects

OS/DB platform
strategy

Solution Landscape
of Customer

SLA &
Availability

Technical Documentation

IT Aspects
2014 SAP AG or an SAP affiliate company. All rights reserved.

(Planning, Installation &


Configuration Guides, etc.)
Public

Deployment Recommendations for SAP Products


Guiding Principles

SAP ERP

SAP SRM

SAP SCM

SAP CRM

ERP
Components

SRM
Components

SCM
Components

CRM
Components

ECC
Server
AS ABAP

SRM
Server
ABAP

AS ABAP

SCM
Server
ABAP

AS ABAP

CRM
Server
ABAP

AS ABAP

ABAP

SAP Business Suite


Backend Systems

SAP
Solution Manager
SolMan Content
Solution Mng
Component

SLD
Dual Stack

JEE

ABAP

SAP NetWeaver Hubs


Application Portal

Business Warehouse
SEM

BEx Web

Process Integration

BICS

ESR Content

BI JAVA

ESR&SR

EP

SLD

Additional SAP BS Instance


Central BI
Content

Portal
Content

EP Core

AS JAVA

PI

BW

ADOBE
JEE

AS ABAP

ABAP

AS JAVA

JEE

PI Dual Stack

JEE

ABAP

Solution Landscape
of Customer

High-Level Guidance
for optimized
Landscape Layouts

Deployment Recommendations
for SAP Products

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

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

Ease Landscape Planning By Stronger Guidance


Used Methodology
Clear recommendations by categorization of deployment options
Possible Exception

Only useful for specific use cases


Supported by SAP, but limitations
might occur

Option II

Reasonable Alternative

Useful choice for certain use


cases or customer scenarios
Supported and confirmed by
SAPs strategy

Goal

Consider

General Recommendation

Option
III

Option I

Best choice for majority of typical


landscape use cases
Recommended by SAPs strategy
Accepted by a wide base of
customers

Outlining main important aspects


Optimal trade-off between flexibility and simplicity
Applied to main building blocks of SAP products
Alternative deployment options typically have different pros & cons
Customer individual assessment is not compensated

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

SAP Master Data Governance


Centrally Govern Master Data on top of SAP Business Suite
SAP MDG is a natural extension of the business processes running in
SAP Business Suite, providing out-of-the-box, domain-specific master data
governance to centrally create, change and distribute master data.
Governance

Enables governance, compliance and transparency through


integrated staging, approval and central audit trail

Consistent Data

Delivers consistent definition, authorization and replication of


key master data entities for SAP. Eliminates error prone manual
maintenance processes for master data in multiple systems

Integration

Native integration with SAP Business Suite and SAP ERP, as


well as supplier qualification (via SAP SLC), and NW MDM

Re-use

Re-use of SAP data model, UI and existing business logic and


configuration for creation and validation of master data

Flexibility

Allows to extend the existing models or define new objects and


related processes in order to govern own master data domains

Data Quality

Leverages SAP Data Services for data quality and enrichment


as well as SAP Information Steward for data remediation

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

Scope of Landscape Recommendations


Building Blocks in System Landscapes for SAP Master Data Governance
Example:

Considered main usage scenarios


SAP MDG is deployed as master data hub
SAP MDG is co-deployed with SAP ERP
SAP MDG uses SAP HANA for search & matching

Considered main building blocks

SAP Master Data Governance (based on SAP ERP)


SAP SLT
SAP HANA
SAP Business Suite as example for master data client
Non SAP application as example for master data client
main role of this
system

Role
JEE

SAP system with


own database

2014 SAP AG or an SAP affiliate company. All rights reserved.

available platform
technology

Public

Overview Landscape Scenarios


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

Landscape Scenario II:


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

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

10

Basic Landscape Setups


Recommendations for SAP Master Data Governance

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

Landscape Scenario II:


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

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

12

Deployment of SAP Master Data Governance


Master data hub based on SAP HANA
General Recommendation

Deploy SAP MDG 7.0 as separate master data hub on SAP HANA (based on SAP ERP EhP7)
No operational usage of embedded SAP ERP
Use SAP HANA as primary DB and for search & matching
Benefits

Example

Application
System

NON SAP

Master Data Hub

SAP ERP A

MDG

distribution of
master data

AnyDB

ECC
AS ABAP

ERP
ABAP

ABAP

primary DB connection

SAP ERP B

Considerations

ERP

SAP HANA
System for MDG

AS ABAP

ABAP

MDG Search &


Matching

SAP HANA

Independent speed of innovation for new MDG capabilities


Clear system of record
Easy setup of / migration to MDG running on SAP HANA since existing
SAP ERP landscape is not touched
No additional SAP HANA for search & matching
No SLT replication of data compared to deployment with SAP HANA
as sidecar

SAP HANA System


for ERP B
SAP HANA

2014 SAP AG or an SAP affiliate company. All rights reserved.

Additional MDG system required


Using SAP HANA as primary DB requires that the SAP ERP
components that MDG are based on are on EhP7
Consider reusing SAP HANA according to white list (see SAP Note
1826100 )
Public

13

Deployment of SAP Master Data Governance


Master data hub based on any DB with optional use of SAP HANA
Reasonable Alternative

Deploy SAP MDG 7.0 as separate master data hub on any DB (based on SAP ERP EhP6 or EhP7)
No operational usage of embedded SAP ERP
Connected to SAP HANA with SAP SLT for search & matching
Benefits

Example

Independent speed of innovation for new MDG capabilities


Customers already using earlier version of SAP MDG based on SAP
ERP EhP6 only need to upgrade the MDG software components
Clear system of record
Easily extended with SAP HANA as sidecar

Application
System
NON SAP

Master Data Hub


SAP ERP A

MDG

distribution of
master data

ERP
AnyDB

ECC
AnyDB

ABAP

secondary
DB
connection
SAP HANA
System

SLT replication of
master data for
search&matching

ERP
ABAP

MDG Search &


Matching

SAP HANA

Considerations

SAP ERP B

AS ABAP

ABAP

SAP HANA System


for ERP B
SAP HANA

2014 SAP AG or an SAP affiliate company. All rights reserved.

Additional MDG system required


New customers should deploy SAP MDG 7.0 on SAP ERP EhP7
Consider reusing SAP HANA according to white list (see SAP Note
1826100 )
Optional usage of other search providers such as SAP Enterprise
Search (Embedded Search) or SAP Business Objects Data Services
is also supported
Public

14

Deployment of SAP Master Data Governance


Co-deployed with local SAP ERP systems and locally used
Possible Exception

Co-Deploy SAP MDG 7.0 with SAP ERP on any DB (based on SAP ERP EhP6 or EhP7) or
SAP HANA (based on SAP ERP EhP7)
ERP is also operationally used
MDG is locally used in every SAP ERP system to govern only local master data or
each SAP ERP system governs different kind of master data within the complete system landscape
Example

Benefits

SAP ERP A with


local MDG

SAP ERP B with


local MDG

MDG

MDG

secondary DB
connection

ERP
AnyDB

ABAP

SLT replication of
master data for
search&matching

MDG Search &


Matching

SAP HANA

Considerations

ERP
AS ABAP

SAP HANA
System

ABAP

primary DB connection
SAP HANA System
for ERP B
MDG Search &
Matching

SAP HANA

2014 SAP AG or an SAP affiliate company. All rights reserved.

No separate systems for SAP MDG


No replication of master data to SAP ERP
Easily extended with SAP HANA as sidecar

No central but distributed governance of master data; might be


useful as a preliminary step for later change to a central MDG hub
Risk: no integration between domains
No global duplicate detection / duplicate prevention possible
SAP HANA usage for MDG depends on existing SAP HANA
deployment of individual SAP ERP systems
Public

15

Deployment of SAP Master Data Governance


Co-deployed with one local SAP ERP system and centrally used
Possible Exception

Co-Deploy SAP MDG 7.0 with SAP ERP on any DB (based on SAP ERP EhP6 or EhP7) or
SAP HANA (based on SAP ERP EhP7)
ERP is also operationally used
MDG is centrally used, but co-deployed with a local SAP ERP system
Example
SAP ERP A

distribution of
master data

ERP
AnyDB

Benefits
SAP ERP B
with central MDG
MDG

distribution of
master data

NON SAP

No separate system for SAP MDG

Considerations

ABAP

ERP
AS ABAP

Application
System

ABAP

primary DB connection
SAP HANA System
for ERP B
MDG Search &
Matching

It may be difficult to choose the local SAP ERP system that


shall serve the MDG Add-On
So far locally used SAP ERP becomes central usage for other
SAP ERP systems ( relevant master data and customizing
need to be loaded)
SAP HANA usage for MDG depends on existing SAP HANA
deployment of individual SAP ERP systems

SAP HANA

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

16

Deployment of SAP Master Data Governance


Master data hub and SAP ERP deployed on same SAP HANA system
Not Supported Today

Deploy SAP MDG 7.0 as separate master data hub on SAP HANA (based on SAP ERP EhP7)
No operational usage of embedded SAP ERP
Use SAP HANA as primary DB and for search & matching
Governed SAP ERP systems using same SAP HANA system as primary DB
Example

distribution of master data


Master Data Hub
SAP ERP A

MDG

ERP

ERP
ECC

AS ABAP

AS ABAP

Implications

SAP ERP B

AS ABAP
ABAP

ABAP

primary DB connections

ABAP

Today co-deployment of two or more SAP ERP


systems on the same SAP HANA system not
supported
Applications supporting co-deployments with SAP
Business Suite on same SAP HANA systems are listed
in SAP Note 1826100

SAP HANA System for MDG, ERP A and ERP B


MDG Search &
Matching

ERP A

ERP B

SAP HANA

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

17

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

Landscape Scenario II:


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

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

18

Deployment of SAP Master Data Governance


Co-deployment with SAP ERP for single SAP ERP landscape
General Recommendation

Co-Deploy SAP MDG 7.0 with SAP ERP within single SAP ERP landscape
ERP is operationally used
Based on any DB (optional usage of SAP HANA as sidecar) or based on SAP HANA
as primary DB for MDG and SAP ERP
Example

Benefits

Single SAP ERP


with MDG
MDG

secondary
DB connection

ERP
AnyDB

ABAP

SAP HANA
System
SLT replication of
master data for
search&matching

MDG Search &


Matching

SAP HANA

2014 SAP AG or an SAP affiliate company. All rights reserved.

No additional system for SAP MDG


UI continuity for maintenance of global and local attributes
Process continuity (no latency for replication)
Easily extended with SAP HANA as sidecar

Considerations

Using SAP HANA as primary DB requires that the SAP ERP


components that MDG is based on are on EhP7
MDG controls master data of single SAP ERP application only

Public

19

Deployment of SAP Master Data Governance


Master data hub based on SAP HANA, separately deployed from central SAP ERP
General Recommendation

Deploy SAP MDG 7.0 as separate master data hub, additionally deployed to central SAP ERP
within multiple SAP ERP landscape, on SAP HANA (based on SAP ERP EhP7)
No operational usage of embedded SAP ERP
Use SAP HANA as primary DB and for search & matching
Central ERP

Example

Benefits

Application
System

ERP

NON SAP
AnyDB

Master Data Hub

ABAP

distribution of
master data
SAP ERP A

MDG

ERP
ECC
AS ABAP

AnyDB

ABAP

Independent speed of innovation


Clear system of record
Easy setup of / migration to MDG running on SAP HANA since
existing SAP ERP landscape is not touched
No SLT replication of data compared to deployment with SAP
HANA as sidecar

ABAP

primary DB connection

Considerations

SAP ERP B

ERP

SAP HANA
System for MDG

AS ABAP

ABAP

MDG Search &


Matching

SAP HANA

SAP HANA System


for ERP B

Additional MDG system required


Higher administration effort
Using SAP HANA as primary DB requires that the SAP ERP
components that MDG is based on are on EhP7.

SAP HANA

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

20

Deployment of SAP Master Data Governance


Master Data hub co-deployed with central SAP ERP on SAP HANA
Reasonable Alternative

Co-Deploy SAP MDG 7.0 with central SAP ERP on SAP HANA (based on SAP ERP EhP7)
ERP is also operationally used as central system
Use SAP HANA as primary DB for MDG and SAP ERP and for search & matching
Application
System

Example

Benefits

NON SAP
Central ERP &
Master Data Gov.

distribution of
master data

MDG

SAP ERP A
ERP
AS ABAP

ERP
ABAP

AnyDB

primary DB connection

Considerations

SAP ERP B
SAP HANA System
for Central ERP
& MDG
MDG Search &
Matching

ERP
AS ABAP

ABAP

No additional system for SAP MDG


No additional SAP HANA for search & matching
No replication of master data to SAP ERP
No SLT replication of data compared to deployment with SAP
HANA as sidecar

ABAP

SAP HANA
SAP HANA System
for ERP B

Using SAP HANA as primary DB requires that the SAP ERP


components that MDG is based on are on EhP7
Existing central SAP ERP system needs to be migrated to SAP
HANA

SAP HANA

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

21

Deployment of SAP Master Data Governance


Master Data hub co-deployed with central SAP ERP on any DB
Reasonable Alternative

Co-Deploy SAP MDG 7.0 with SAP ERP on any DB (based on SAP ERP EhP6 or EhP7)
ERP is also operationally used as central system
Connected to SAP HANA with SAP SLT for search & matching
Example

Benefits

Application
System

NON SAP
Central ERP &
Master Data Gov.

distribution of
master data

SAP ERP A

MDG
ERP
ERP

AnyDB

AnyDB
ABAP

secondary
DB
connection
SAP HANA
System

SLT replication of
master data for
search&matching

Considerations
SAP ERP B

ERP
AS ABAP

ABAP

MDG Search &


Matching

SAP HANA

ABAP

No additional systems for SAP MDG


Customers already using earlier version of SAP MDG based on SAP
ERP EhP6 only need to upgrade the MDG software components
No replication of master data to SAP ERP
Easily extended with SAP HANA as sidecar

SAP HANA System


for ERP B
SAP HANA

2014 SAP AG or an SAP affiliate company. All rights reserved.

Additional SAP HANA system might be required


New customers should deploy SAP MDG 7.0 on SAP ERP EhP7 and
should consider using SAP HANA as primary DB
Consider reusing SAP HANA according to white list
Optional usage of other search providers such as SAP Enterprise
Search (Embedded Search) or SAP Business Objects Data Services
is also supported
Public

22

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 note 1690202) 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

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

24

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 web dynpros 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

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

25

Additional Considerations for separate MDG hub


Additional benefits of separate MDG hub

Allows fresh start with cleansed data

Less alignment on system maintenance cycles

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

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

26

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

2014 SAP AG or an SAP affiliate company. All rights reserved.

Public

27

Thank you
Frank Damaschke
Chief Development Architect
Master Data Governance
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf, Germany
E frank.damaschke@sap.com
Please visit
www.sap.com/mdm

2014 SAP AG or an SAP affiliate company. All rights reserved.