Professional Documents
Culture Documents
Deployment Recommendations MDG70 Approved
Deployment Recommendations MDG70 Approved
Deployment Recommendations MDG70 Approved
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.
Public
Agenda
Introduction
Methodology & Scope of Landscape Recommendations
Public
Introduction
Methodology & Scope of Landscape Recommendations
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
Solution Manager
SolMan Content
Solution Mng
Component
SLD
Dual Stack
JEE
ABAP
Business Warehouse
SEM
BEx Web
Process Integration
BICS
ESR Content
BI JAVA
ESR&SR
EP
SLD
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.
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
Solution Manager
SolMan Content
Solution Mng
Component
SLD
Dual Stack
JEE
ABAP
Business Warehouse
SEM
BEx Web
Process Integration
BICS
ESR Content
BI JAVA
ESR&SR
EP
SLD
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
Public
Option II
Reasonable Alternative
Goal
Consider
General Recommendation
Option
III
Option I
Public
Consistent Data
Integration
Re-use
Flexibility
Data Quality
Public
Role
JEE
available platform
technology
Public
Public
10
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
Public
12
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
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
SAP HANA
13
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
Application
System
NON SAP
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
SAP HANA
Considerations
SAP ERP B
AS ABAP
ABAP
14
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
MDG
MDG
secondary DB
connection
ERP
AnyDB
ABAP
SLT replication of
master data for
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
15
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
Considerations
ABAP
ERP
AS ABAP
Application
System
ABAP
primary DB connection
SAP HANA System
for ERP B
MDG Search &
Matching
SAP HANA
Public
16
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
MDG
ERP
ERP
ECC
AS ABAP
AS ABAP
Implications
SAP ERP B
AS ABAP
ABAP
ABAP
primary DB connections
ABAP
ERP A
ERP B
SAP HANA
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
Public
18
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
secondary
DB connection
ERP
AnyDB
ABAP
SAP HANA
System
SLT replication of
master data for
search&matching
SAP HANA
Considerations
Public
19
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
ABAP
distribution of
master data
SAP ERP A
MDG
ERP
ECC
AS ABAP
AnyDB
ABAP
ABAP
primary DB connection
Considerations
SAP ERP B
ERP
SAP HANA
System for MDG
AS ABAP
ABAP
SAP HANA
SAP HANA
Public
20
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
ABAP
SAP HANA
SAP HANA System
for ERP B
SAP HANA
Public
21
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
SAP HANA
ABAP
22
Additional Considerations
Recommendations for SAP Master Data Governance
In a client where time dependency is required for the Business Partner in ERP
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
Public
24
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
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
Public
25
The ERP system is kept free of non-ERP data (data that is required to serve non-ERP or non-SAP systems)
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
Public
26
Initial load of master data, ongoing additional replication of master data to operational ERP
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