system landscape recommendations for sap master data governance 7.0
DESCRIPTION
801 Guide for SAP Business WorkflowTRANSCRIPT
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 2 Public
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. 3 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. 5 Public
System Landscapes at Customers Designing the Optimal Landscape Layout
Business Aspects
Operations
Costs
Speed of
Innovation
Security
Architectural
Strategy
Performance &
ScalabilityLegal Aspects
…
OS/DB platform
strategy
SLA &
Availability
IT Aspects
Product Roadmaps
Technical Documentation (Planning, Installation &
Configuration Guides, etc.)
Deployment Recommendations
for SAP Products
SLD
Dual Stack
SAP
Solution Manager
ABAP
JEE
Solution Mng
Component
AS ABAP
ECC
Server
SAP ERP
ABAP
ERP
Components
AS ABAP
SRM
Server
SAP SRM
ABAP
SRM
Components
AS ABAP
SCM
Server
SAP SCM
ABAP
SCM
Components
AS ABAP
CRM
Server
SAP CRM
ABAP
CRM
Components
BW
AS ABAP
Business Warehouse
SEM
Central BI
Content
ABAP
EP
AS JAVA
BEx Web
JEE
BI JAVA
BICS
PI
PI Dual Stack
Process Integration
ABAP
JEE
ESR&SR
ESR Content
SLD
SolMan Content
SAP NetWeaver Hubs
SAP Business Suite
Backend Systems
EP Core
AS JAVA
Application Portal
JEE
Additional SAP BS Instance
Portal
Content
ADOBE
Solution Landscape
of Customer
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 6 Public
Deployment Recommendations for SAP Products Guiding Principles
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
High-Level Guidance
for optimized
Landscape Layouts
SLD
Dual Stack
SAP
Solution Manager
ABAP
JEE
Solution Mng
Component
AS ABAP
ECC
Server
SAP ERP
ABAP
ERP
Components
AS ABAP
SRM
Server
SAP SRM
ABAP
SRM
Components
AS ABAP
SCM
Server
SAP SCM
ABAP
SCM
Components
AS ABAP
CRM
Server
SAP CRM
ABAP
CRM
Components
BW
AS ABAP
Business Warehouse
SEM
Central BI
Content
ABAP
EP
AS JAVA
BEx Web
JEE
BI JAVA
BICS
PI
PI Dual Stack
Process Integration
ABAP
JEE
ESR&SR
ESR Content
SLD
SolMan Content
SAP NetWeaver Hubs
SAP Business Suite
Backend Systems
EP Core
AS JAVA
Application Portal
JEE
Additional SAP BS Instance
Portal
Content
ADOBE
Solution Landscape
of Customer
Deployment Recommendations
for SAP Products
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 7 Public
Ease Landscape Planning By Stronger Guidance Used Methodology
Clear recommendations by categorization of deployment options
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
Goal
Consider
Option I Option II
Option
III General Recommendation
Best choice for majority of typical
landscape use cases
Recommended by SAP’s strategy
Accepted by a wide base of
customers Reasonable Alternative
Useful choice for certain use
cases or customer scenarios
Supported and confirmed by
SAP’s strategy
Possible Exception
Only useful for specific use cases
Supported by SAP, but limitations
might occur
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 8 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. 9 Public
Scope of Landscape Recommendations Building Blocks in System Landscapes for SAP Master Data Governance
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
JEE
SAP system with
own database
available platform
technology
Rolemain role of this
system
Example:
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 10 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. 12 Public
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. 13 Public
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
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
Considerations
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 )
Example
SAP ERP B
ERP
AS ABAPABAP
SAP HANA System
for ERP B
SAP HANA
AS ABAP
Master Data Hub
ABAP
primary DB connection
SAP HANA
SAP HANA
System for MDG
ECC
MDGSAP ERP A
ERP
ABAP
distribution of
master data
MDG Search &
Matching
AnyDB
Application
System
NON SAP
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 14 Public
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
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
Considerations
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
Example
SAP HANA
SAP HANA
System
MDG Search &
Matching
AnyDB
Master Data Hub
ABAP
ECC
MDG
SLT replication of
master data for
search&matching
secondary
DB
connectionSAP ERP B
ERP
AS ABAPABAP
SAP HANA System
for ERP B
SAP HANA
SAP ERP A
ERP
ABAPAnyDB
Application
System
NON SAP
distribution of
master data
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 15 Public
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
Benefits
No separate systems for SAP MDG
No replication of master data to SAP ERP
Easily extended with SAP HANA as sidecar
Considerations 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
Example
SAP ERP B with
local MDG
ERP
AS ABAPABAP
primary DB connection
SAP HANA
SAP HANA System
for ERP B
SAP ERP A with
local MDG
ERP
ABAPAnyDB
SAP HANA
SAP HANA
System
MDG Search &
Matching
MDG MDG
MDG Search &
Matching
secondary DB
connection
SLT replication of
master data for
search&matching
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 16 Public
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
Benefits
No separate system for SAP MDG
Considerations
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
Example
SAP ERP B
with central MDG
ERP
AS ABAPABAP
primary DB connection
SAP HANA
SAP HANA System
for ERP B
MDG
MDG Search &
Matching
SAP ERP A
ERP
ABAPAnyDB
distribution of
master data
Application
System
NON SAP
distribution of
master data
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 17 Public
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
Implications
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
Example
SAP ERP A
ERP
AS ABAPABAP
SAP ERP B
ERP
AS ABAPABAP
AS ABAP
Master Data Hub
ABAP
primary DB connections
SAP HANA
SAP HANA System for MDG, ERP A and ERP B
ECC
MDG
MDG Search &
MatchingERP A ERP B
distribution of master data
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 18 Public
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. 19 Public
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
Benefits
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
Example
Single SAP ERP
with MDG
ERP
ABAP
MDG
SAP HANA
SAP HANA
System
MDG Search &
Matching
AnyDB
secondary
DB connection
SLT replication of
master data for
search&matching
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 20 Public
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
Benefits
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
Considerations
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.
Example Central ERP
ERP
ABAPAnyDB
SAP ERP A
ERP
ABAPAnyDB
AS ABAP
Master Data Hub
ABAP
primary DB connection
SAP HANA
SAP HANA
System for MDG
ECC
MDG
MDG Search &
Matching
distribution of
master data
SAP ERP B
ERP
AS ABAPABAP
SAP HANA System
for ERP B
SAP HANA
Application
System
NON SAP
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 21 Public
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
Benefits
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
Considerations
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
Example Application
System
NON SAP
AS ABAP
Central ERP &
Master Data Gov.
ABAP
primary DB connection
SAP HANA
SAP HANA System
for Central ERP
& MDG
ERP
MDG
MDG Search &
Matching
SAP ERP A
ERP
ABAPAnyDB
SAP ERP B
ERP
AS ABAPABAP
SAP HANA System
for ERP B
SAP HANA
distribution of
master data
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 22 Public
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
Benefits
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
Considerations
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
Example
SAP HANA
SAP HANA
System
MDG Search &
Matching
AnyDBABAP
MDG
SLT replication of
master data for
search&matching
secondary
DB
connectionSAP ERP B
ERP
AS ABAPABAP
SAP HANA System
for ERP B
SAP HANA
SAP ERP A
ERP
ABAPAnyDB
Application
System
NON SAP
distribution of
master data
ERP
Central ERP &
Master Data Gov.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 24 Public
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. 25 Public
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. 26 Public
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. 27 Public
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.
Thank you Frank Damaschke Chief Development Architect
Master Data Governance
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf, Germany
Please visit www.sap.com/mdm
© 2014 SAP AG. All rights reserved. 43
No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,
z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,
OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered
trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or
registered trademarks of Adobe Systems Incorporated in the United States and/or other
countries.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
© 2014 SAP AG. All rights reserved.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World
Wide Web Consortium, Massachusetts Institute of Technology.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG in Germany and other
countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports,
Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and
services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects Software Ltd. Business Objects is an
SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National
product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be
reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.