SAP SE, August 2015 Deployment Recommendations for SAP Master Data Governance 8.0
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. 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 2
Agenda Introduction Methodology & Scope of Landscape Recommendations Basic Landscape Setups Recommendations for SAP Master Data Governance 8.0 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 3
Introduction Methodology & Scope of Landscape Recommendations
JEE JEE JEE JEE System Landscapes at Customers Designing the Optimal Landscape Layout Product Roadmaps SAP SAP SRM SAP SCM SAP CRM SRM SCM CRM Components Components Components Components Business Aspects ECC Server SRM Server SCM Server CRM Server AS AS AS AS SAP Solution Manager SAP Business Suite Backend Systems SolMan Content Solution Mng Component SLD Dual Stack SAP NetWeaver Hubs Application Portal Business Warehouse BEx Web Process Integration Operations Costs Architectural Strategy Security Additional SAP BS Instance Portal Content ADOBE EP Core AS JAVA SEM Central BI Content BW AS BICS BI JAVA EP AS JAVA ESR Content ESR&SR PI SLD PI Dual Stack Deployment Recommendations for SAP Products Speed of Innovation Performance & Scalability Legal Aspects Solution Landscape of Customer OS/DB platform strategy IT Aspects SLA & Availability Technical Documentation (Planning, Installation & Configuration Guides, etc.) 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 5
JEE JEE JEE JEE Deployment Recommendations for SAP Products Guiding Principles SAP SAP SRM SAP SCM SAP CRM SRM SCM CRM Components Components Components Components ECC SRM SCM CRM Server Server Server Server AS AS AS AS SAP Solution Manager SAP Business Suite Backend Systems SolMan Content Solution Mng Component SLD Dual Stack SAP NetWeaver Hubs Application Portal Additional SAP BS Instance Portal Content EP Core AS JAVA ADOBE Business Warehouse SEM Central BI Content BW AS BEx Web BICS BI JAVA EP AS JAVA Solution Landscape of Customer Process Integration ESR Content ESR&SR PI SLD PI Dual Stack 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 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 6
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 Reasonable Alternative Useful choice for certain use cases or customer scenarios Supported and confirmed by SAP s strategy Option III Option II Option I General Recommendation Best choice for majority of typical landscape use cases Recommended by SAP s strategy Accepted by a wide base of customers Goal Consider 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 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 7
SAP Master Data Governance Covering consolidation and central governance Consolidate master data from de-central sources Centrally govern and distribute master data LoB processes De-central IT landscapes SAP MDG On-premise systems Cloud applications Cloud 3 rd Party apps Mergers & acquisitions Other 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 8
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 SAP MDG uses for search & matching Considered main building blocks SAP Master Data Governance (based on SAP ) SAP SLT SAP Business Suite as example for master data client Non SAP application as example for master data client Role main role of this system JEE SAP system with own database available platform technology 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 9
Major Changes or Updates Summary Major changes or updates to former landscape recommendations Type of change Former Status New Status Reason Reference Deployment rating Deployment rating Co-deployment with SAP for single SAP landscape based on any DB General recommendation Master Data hub codeployed with central SAP on any DB Reasonable Alternative Co-deployment with SAP for single SAP landscape based on any DB Reasonable Alternative Master Data hub codeployed with central SAP on any DB Possible Exception Major restrictions for MDG, consolidation (new in MDG 8.0) w/o HANA Major restrictions for MDG, consolidation (new in MDG 8.0) w/o HANA Slide 22 Slide 25 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 10
Overview Landscape Scenarios Landscape Scenario I: Distributed System Landscape with only local SAP systems Customer landscape contains different local SAP or NON-SAP application systems No central SAP system in place Governance processes for master data are going to be implemented Landscape Scenario II: Distributed System Landscape with existing central SAP system Customer landscape contains a single SAP system only (simple system landscape) Or customer landscape contains a dedicated central SAP system serving central processes against local SAP systems, other SAP Business Suite systems or NON-SAP application systems Governance processes for master data are going to be implemented 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 11
Basic Landscape Setups Recommendations for SAP Master Data Governance
Landscape Scenario I Landscape Scenario I: Distributed System Landscape with only local SAP systems Customer landscape contains different local SAP or NON-SAP application systems No central SAP system in place Governance processes for master data are going to be implemented Landscape Scenario II: Distributed System Landscape with existing central SAP system Customer landscape contains a single SAP system only (simple system landscape) Or customer landscape contains a dedicated central SAP system serving central processes against local SAP systems, other SAP Business Suite systems or NON-SAP application systems Governance processes for master data are going to be implemented 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 13
Deployment of SAP Master Data Governance Master data hub based on General Recommendation Deploy SAP MDG 8.0 as separate master data hub on No operational usage of embedded SAP Use as primary DB and for search, standardization & matching Example Master Data Hub MDG ECC AS primary DB connection System for MDG MDG Search & Matching distribution of master data Application System NON SAP SAP B AS System for B SAP A AnyDB Benefits Independent speed of innovation for new MDG capabilities Clear system of record Easy setup of / migration to MDG running on since existing SAP landscape is not touched No additional for search No additional index server for address validation & duplicate check No SLT replication of data compared to deployment with as sidecar Considerations Additional MDG system required Consider reusing according to white list (see SAP Note 1826100 ) 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 14
Deployment of SAP Master Data Governance Master data hub based on any DB with optional use of Reasonable Alternative Deploy SAP MDG 8.0 as separate master data hub on any DB No operational usage of embedded SAP Connected to with SAP SLT for search & duplicate check Example Master Data Hub MDG ECC AnyDB SLT replication of master data for search & duplicate check distribution of master data secondary DB connection System MDG Search & Duplicate Check Application System NON SAP SAP B AS System for B SAP A AnyDB Benefits Independent speed of innovation for new MDG capabilities Clear system of record Easily extended with as sidecar Considerations Additional MDG system required Consider reusing 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 No usage of HANA in MDG, consolidation (Optional usage of SAP Business Objects Data Services is also supported for standardization & matching.) 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 15
Deployment of SAP Master Data Governance Co-deployed with local SAP systems and locally used Possible Exception Co-Deploy SAP MDG 8.0 with SAP on any DB or is also operationally used MDG is locally used in every SAP system to govern only local master data or each SAP system governs different kind of master data within the complete system landscape Example SAP A with local MDG MDG AnyDB SLT replication of master data for search & duplicate check secondary DB connection System MDG Search & Duplicate Check SAP B with local MDG MDG AS primary DB connection System for B MDG Search & Matching Benefits No separate systems for SAP MDG No replication of master data to SAP Easily extended with 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 usage for MDG depends on existing deployment of individual SAP systems 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 16
Deployment of SAP Master Data Governance Co-deployed with one local SAP system and centrally used Possible Exception Co-Deploy SAP MDG 8.0 with SAP on any DB or is also operationally used MDG is centrally used, but co-deployed with a local SAP system Example SAP A AnyDB distribution of master data SAP B with central MDG MDG AS primary DB connection System for B MDG Search & Matching distribution of master data Application System NON SAP Benefits No separate system for SAP MDG Considerations It may be difficult to choose the local SAP system that shall serve the MDG Add-On So far locally used SAP becomes central usage for other SAP systems ( relevant master data and customizing need to be loaded) usage for MDG depends on existing deployment of individual SAP systems 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 17
Deployment of SAP Master Data Governance Master data hub and SAP deployed on same DB Not Supported Today Deploy SAP MDG 8.0 as separate master data hub on No operational usage of embedded SAP Use as primary DB and for search & duplicate check Governed SAP systems using same DB as primary DB Example Master Data Hub MDG ECC AS distribution of master data SAP A AS SAP B AS Implications Today co-deployment of two or more SAP systems on the same DB not supported Applications supporting co-deployments with SAP Business Suite on same DB are listed in SAP Note 1826100 primary DB connections System for MDG, A and B MDG Search & Matching A B Considerations With SPS9 the new feature MDC (multi tenant DB container) has been introduced. This feature allows running SAP MDG and SAP in separate DB tenants of the same HANA server. Refer also to note 1774566 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 18
Deployment of SAP Master Data Governance SAP MDG on any DB with optional use of for consolidation Deploy SAP MDG 8.0 on any DB Not Supported Today Connected to with SAP SLT for standardization & matching Example MDG secondary DB connection Considerations Optional usage of SAP Business Objects Data Services is supported for standardization & matching AnyDB SLT replication of master data for standardization & matching System MDG Standardization & Matching 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 19
Landscape Scenario II Landscape Scenario I: Distributed System Landscape with only local SAP systems Customer landscape contains different local SAP or NON-SAP application systems No central SAP system in place Governance processes for master data are going to be implemented Landscape Scenario II: Distributed System Landscape with existing central SAP system Customer landscape contains a single SAP system only (simple system landscape) Or customer landscape contains a dedicated central SAP system serving central processes against local SAP systems, other SAP Business Suite systems or NON-SAP application systems Governance processes for master data are going to be implemented 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 20
Deployment of SAP Master Data Governance Co-deployment with SAP for single SAP landscape based on General Recommendation Co-Deploy SAP MDG 8.0 with SAP within single SAP landscape is operationally used Based on as primary DB for MDG and SAP Example Single SAP with MDG MDG AS primary DB connection System for & MDG MDG Search & Matching Benefits No additional system for SAP MDG UI continuity for maintenance of global and local attributes Process continuity (no latency for replication) Considerations MDG controls master data of single SAP application only 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 21
Deployment of SAP Master Data Governance Co-deployment with SAP for single SAP landscape based on any DB Reasonable Alternative Co-Deploy SAP MDG 8.0 with SAP within single SAP landscape is operationally used Based on any DB (optional usage of as sidecar) Example Single SAP with MDG MDG secondary DB connection 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 as sidecar AnyDB SLT replication of master data for search & duplicate check System MDG Search & Duplicate Check Considerations MDG controls master data of single SAP application only No usage of HANA in MDG, consolidation (Optional usage of SAP Business Objects Data Services is also supported for standardization & matching.) 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 22
Deployment of SAP Master Data Governance Master data hub based on, separately deployed from central SAP General Recommendation Deploy SAP MDG 8.0 as separate master data hub, additionally deployed to central SAP within multiple SAP landscape, on No operational usage of embedded SAP Use as primary DB and for search, standardization & matching Example Master Data Hub MDG ECC AS primary DB connection System for MDG MDG Search & Matching Central AnyDB distribution of master data Application System NON SAP SAP B AS SAP A AnyDB System for B Benefits Independent speed of innovation Clear system of record Easy setup of / migration to MDG running on since existing SAP 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 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 23
Deployment of SAP Master Data Governance Master Data hub co-deployed with central SAP on Reasonable Alternative Co-Deploy SAP MDG 8.0 with central SAP on is also operationally used as central system Use as primary DB for MDG and SAP and for search, standardization & matching Example Central & Master Data Gov. MDG AS distribution of master data Application System NON SAP SAP A AnyDB Benefits No additional system for SAP MDG No additional for search & matching No replication of master data to central SAP No SLT replication of data compared to deployment with as sidecar primary DB connection System for Central & MDG MDG Search & Matching SAP B AS System for B Considerations Existing central SAP system needs to be migrated to 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 24
Deployment of SAP Master Data Governance Master Data hub co-deployed with central SAP on any DB Possible Exception Co-Deploy SAP MDG 8.0 with SAP on any DB is also operationally used as central system Connected to with SAP SLT for search & duplicate check Example Central & Master Data Gov. MDG AnyDB SLT replication of master data for search & duplicate check distribution of master data secondary DB connection System MDG Search & Duplicate Check Application System NON SAP SAP B AS System for B SAP A AnyDB Benefits No additional systems for SAP MDG No replication of master data to central SAP Easily extended with as sidecar Considerations Additional system might be required Consider reusing 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 No usage of HANA in MDG, consolidation (Optional usage of SAP Business Objects Data Services is also supported for standardization & matching.) 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 25
Additional Considerations Recommendations for SAP Master Data Governance
Additional Considerations for MDG hub co-deployed with A co-deployment of MDG with an operational system is not possible In a client where time dependency is required for the Business Partner in 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 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 system 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 27
Additional Considerations for MDG hub co-deployed with Additional benefits of the co-deployment of MDG with an operational 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 system Process continuity: no latency for data replication, no cross-system monitoring No system integration between MDG hub and required no costs for implementation and monitoring of replication interfaces No additional integration effort with respect to specific external services such as translation management 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 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 No impact of MDG on system load in operational (and vice versa) Higher flexibility / additional options when it comes to harmonization or mapping of customizing The system is kept free of non- data (data that is required to serve non- 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 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 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 Initial load and synchronization of customizing Meta data is sometimes maintained multiple times or at least at different places 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 30
Additional Considerations for DB MDG 8.0 provides applications for central governance and for consolidation. MDG, central governance works best with as primary DB. Using a different primary DB leads to minor restrictions. Most of them can be compensated with the additional usage of as a sidecar for search & duplicate check. MDG, consolidation works best with as primary DB. Not using leads to major restrictions, in especially when looking at performance. Using as sidecar is not supported. Customers who are interested in MDG, consolidation but do not want a separate system for MDG should consider the MDC feature of SPS9 (see note 1774566). 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 31
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 2015 SAP SE or an SAP affiliate company. All rights reserved.