Landscape Deployment Recommendations for SAP Customer Activity Repository (CAR) and SAP CAR Application Bundle (CARAB)

Transcription

1 Landscape Deployment Recommendations for SAP Customer Activity Repository (CAR) and SAP CAR Application Bundle (CARAB)

2 New Rollout Channel The rollout channel for publishing landscape deployment recommendations changed. Please have a look at our announcement. You will find the newest version of this document here: SAP Customer Activity Repository 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 2

3 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 SAP AG or an SAP affiliate company. All rights reserved. Public 3

4 Agenda Introduction Methodology & Scope of Landscape Recommendations Use Cases Customer Activity Repository (CAR) in different Landscape scenarios Basic Landscape Setups Recommendations for Customer Activity Repository (CAR) and CAR Application Bundle (CARAB) 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 4

5 Introduction Methodology & Scope of Landscape Recommendations

6 JEE ABAP ABAP JEE ABAP ABAP ABAP JEE ABAP JEE ABAP 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 Business Aspects ECC Server SRM Server SCM Server CRM Server AS ABAP AS ABAP AS ABAP AS ABAP 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 ABAP 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.) 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 6

7 JEE ABAP ABAP JEE ABAP ABAP ABAP JEE ABAP JEE ABAP 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 AS ABAP AS ABAP AS ABAP AS ABAP 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 ABAP 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 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 7

8 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 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 8

9 Use Cases Customer Activity Repository (CAR) in different Landscape Scenarios

10 CAR Building Blocks SAP PMR Audience Discover & Targeting* SAP BW* *) Optional co-deployments SAP IS Retail in-memory computing Customer Activity Repository Virtual Data Model (SAP Live) - Analytics SAP CRM Master Data POS Data Transfer & Audit Unified Demand Forecast Inventory Visibility Sales Documents Inventory Multichannel sales transactions OSA Algorithms Customer Data 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 10

11 Overview Landscape Scenarios I. Landscape Scenario I: Standalone usage of Customer Activity Repository (SAP CAR 1.0) II. Landscape Scenario II: Customer Activity Repository (SAP CAR 2.0) as part of SAP CAR Application Bundle (CARAB) III. Landscape Scenario III: Customer Activity Repository (SAP CAR 2.0) as part of CARAB and as data provider for analytical or transactional applications 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 11

12 Scope of Landscape Recommendations Building Blocks in System Landscapes for Landscape Scenario I Example: Considered main usage scenarios SAP CAR used to collect, to harmonize and to enrich sales information from all channels (Web, Store, ERP, Interaction Center) SAP CAR used as a central repository for sales- and inventory information SAP CAR used as the data foundation for forecasts SAP CAR sales information enhanced with CRM customer information (optional) Considered main building blocks SAP CAR 1.0 SAP NetWeaver SAP HANA Appliance Software SAP LT Replication Server for HANA SAP RFC based Replication SAP HANA Live for SAP Business Suite SAP ERP SAP CRM (optional) 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 12

13 Scope of Landscape Recommendations Building Blocks in System Landscapes for Landscape Scenario II Considered main usage scenarios SAP CAR usage like in landscape scenario I: CAR used to collect, to harmonize and to enrich sales information from all channels (Web, Store, ERP, Interaction Center) CAR used as a central repository for sales- and inventory information CAR used as the data foundation for forecasts In addition SAP CAR 2.0 used as part of SAP CAR Application Bundle CAR used as a platform for consuming retail applications on-top (CARAB) Considered main building blocks SAP CAR Application Bundle SAP NetWeaver SAP HANA Appliance Software SAP LT Replication Server for HANA SAP RFC based Replication SAP HANA Live for SAP Business Suite 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 13

14 Scope of Landscape Recommendations Building Blocks in System Landscapes for Landscape Scenario III Considered main usage scenarios CAR usage like in landscape scenario II: CAR used to collect, to harmonize and to enrich sales information from all channels (Web, Store, ERP, Interaction Center) CAR used as a central repository for sales- and inventory information CAR used as a platform for consuming retail applications on-top CAR used as the data foundation for forecasts CAR used as data provider for analytical or transactional applications (e.g. a central* SAP NetWeaver BW) Considered main building blocks SAP CAR SAP NetWeaver SAP HANA Appliance Software SAP LT Replication Server for HANA SAP RFC based Replication SAP HANA Live for SAP Business Suite SAP BW * co-deployment with a local BW might require additional data replication towards the central BW system, with potential negative impact on TCO 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 14

15 General Assumptions and Considerations for all Landscape Scenarios a co-deployment of CAR with a central SAP NetWeaver BW provides a basis for replication-free, high performance access to CAR s sales repository co-deployment with a local BW might require additional data replication towards the central BW system, with potential negative impact on TCO CAR has whitelist approval and may be co-deployed with other applications approved co-deployment scenarios and potential caveats are described in Note currently CAR does not support multiple SAP ERP systems scenarios, where CAR shall connect to multiple SAP ERP systems are currently not supported currently CAR does not support 3 rd party ERP systems natively there is no automated or preconfigured support for integration with 3 rd party ERP systems. The Documentation includes content to help map data from 3 rd party ERP systems into CAR/CARAB. This mapping needs to be scoped carefully as part of an implementation project SAP AG or an SAP affiliate company. All rights reserved. Public 15

16 Basic Landscape Setups Recommendations for Customer Activity Repository (CAR) and CAR Application Bundle (CARAB)

17 Overview Landscape Scenarios Landscape Scenario I: Standalone usage of Customer Activity Repository CAR used side-by-side with a central SAP Retail ERP CAR co-deployed with a central SAP Retail ERP CAR co-deployed with a SAP Retail ERP, sharing same SAP NetWeaver instance 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 17

18 Deployment of CAR Side-by-Side to the central SAP Retail ERP system General Recommendation CAR used side-by-side with a central SAP Retail ERP system CAR is deployed on a separate SAP NetWeaver AS ABAP and a separate SAP HANA system ERP data (e.g. sales orders, inventory, master data ) is replicated with SLT and RFC from SAP ERP into SAP HANA Additional customer and loyalty information can optionally be replicated from a central SAP CRM Example Benefits No need to migrate SAP ERP to SAP HANA Easier sizing of SAP HANA system Decoupling of mission critical SAP ERP system and SAP CAR Easier operating of SAP CAR on decoupled SAP HANA system Additional customer and loyalty information can optionally be replicated from a central SAP CRM Considerations ERP data needs to be replicated from SAP ERP 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 18

19 Deployment of CAR Co-deployed with the central SAP Retail ERP system, separated SAP NetWeaver instances Reasonable Alternative CAR Sharing SAP HANA system with the central SAP Retail ERP system Deployed in different SAP NetWeaver AS ABAP instances Example Benefits Lower TCO due to shared SAP HANA system Lower TCO due to no SLT based data replication required Best option to avoid data redundancy Best option for real-time scenarios Considerations SAP ERP needs to be migrated to SAP HANA before Check white-list for supported co-deployments with other Business-Suite applications: Note and consider additional efforts for operating multiple applications on one DB Proper sizing and resource planning required Consider that resources for productive ERP are not isolated ERP archiving directly affects data history for CAR 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 19

20 Deployment of CAR Co-deployed with the central SAP Retail ERP system, same SAP NetWeaver instance Not Supported CAR Sharing SAP HANA system with the central SAP Retail ERP system Deployed in the same SAP NetWeaver AS ABAP instance Example Implications SAP NetWeaver version must fit for CAR and ERP Adds an additional dependency to both applications Patches and corrections of SAP NetWeaver must be supported by CAR and ERP Upgrades of CAR (or ERP) might require a new SAP NetWeaver version, which is not yet supported by the other application Later separation of CAR for scale-out not possible 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 20

21 Overview Landscape Scenarios Landscape Scenario II: Customer Activity Repository as part of CARAB CAR used embedded in CARAB and side-by-side with a central SAP Retail ERP CAR used embedded in CARAB and co-deployed with a central SAP Retail ERP on the same SAP HANA system CAR used embedded in CARAB and co-deployed with a SAP Retail ERP on the same SAP NetWeaver and SAP HANA instance 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 21

22 Deployment of CAR/CARAB Side-by-Side to the central SAP Retail ERP system General Recommendation SAP CAR is coupled and shipped as a bundle with consuming retail applications (SAP CARAB) SAP CAR and the consuming retail applications are co-deployed on the same SAP NetWeaver AS ABAP and SAP HANA system, but separated from any other application SAP CARAB is locally integrated via SAP CAR with a central SAP ERP Retail system SAP ERP business data (e.g. sales orders, inventory, master data) is replicated to the SAP HANA system for SAP CARAB with SAP LT Replication Server Benefits Automated installation & configuration of SAP CAR together with other retail applications on top with SAP CARAB SAP CAR and other retail applications of SAP CARAB are automatically in sync No need to migrate SAP ERP to SAP HANA Easier sizing of SAP HANA system Decoupling of a mission critical SAP ERP Retail system and SAP CARAB Easier operating of SAP CARAB on decoupled SAP HANA system Considerations The innovation speed of SAP CAR is closely coupled with the other retail applications of SAP CARAB ERP data needs to be replicated from SAP ERP 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 22

23 Deployment of CAR/CARAB Co-deployed with the central SAP Retail ERP system, separated SAP NetWeaver instances Reasonable Alternative SAP CAR is coupled and shipped as a bundle with consuming retail applications (SAP CARAB) SAP CAR is locally integrated via SAP CAR with a central SAP ERP Retail system SAP CAR and the consuming retail applications are co-deployed on the same SAP NetWeaver AS ABAP system (SAP CARAB), separated from the SAP ERP Retail system SAP CARAB is sharing the same SAP HANA system with the central SAP ERP Retail system SAP ERP business data (e.g. sales orders, inventory) can directly be accessed in the shared SAP HANA system system (no replication required) Benefits Automated installation & configuration of SAP CAR together with other retail applications on top with SAP CARAB SAP CAR and other retail applications of SAP CARAB are automatically in sync Lower TCO due to the shared SAP HANA system No replication of SAP ERP business data required Best option to avoid data redundancy and for real-time scenarios Considerations The innovation speed of SAP CAR is closely coupled with the other retail applications of SAP CARAB SAP ERP needs to be migrated to SAP HANA before Check white-list for supported co-deployments with other Business-Suite applications: Note and consider additional efforts for operating multiple applications on one DB Proper sizing and resource planning required 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 23

24 Deployment of CAR Co-deployed with the central SAP Retail ERP system, same SAP NetWeaver instance Not Supported SAP CAR is coupled and shipped as a bundle with consuming retail applications (SAP CARAB) SAP CAR is locally integrated via SAP CAR with a central SAP ERP Retail system SAP CARAB is co-deployed with SAP ERP on the same SAP NetWeaver AS ABAP system SAP CARAB is sharing the same SAP HANA system with the central SAP ERP Retail system Implications SAP NetWeaver version must fit for SAP CARAB and SAP ERP An additional dependency is added to both applications Patches and corrections of SAP NetWeaver AS ABAP must be supported by SAP CARAB and SAP ERP Upgrades of SAP CARAB (or SAP ERP) might require a new SAP NetWeaver version, which is not yet supported by the other application Later separation of SAP CARAB for scale-out is technically not possible 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 24

25 Overview Landscape Scenarios Landscape Scenario III: Customer Activity Repository (SAP CAR 2.0) as part of CARAB and as data provider for analytical or transactional applications CAR embedded in CARAB and co-deployed with another central analytical or transactional application (like SAP NetWeaver BW or SAP hybris Marketing) on the same SAP HANA system CAR embedded in CARAB and separately deployed from the other applications (like SAP NetWeaver BW or SAP hybris Marketing) CAR embedded in CARAB co-deployed with another central analytical or transactional application, sharing also the same SAP NetWeaver instance 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 25

26 Deployment of CAR Co-deployed with a consuming central application on the same SAP HANA system General Recommendation SAP CAR is coupled and shipped as a bundle with consuming retail applications (SAP CARAB) SAP CAR is integrated with another central application system (like SAP BW or SAP hybris Marketing) and serves as data provider for this application SAP CAR is deployed as part of SAP CARAB on a separate SAP NetWeaver AS ABAP system, but shares the same SAP HANA system with the application that consumes SAP CAR data SAP ERP business data (e.g. sales orders, inventory, master data) is replicated to the SAP HANA system of SAP Customer Activity Repository with SAP LT Replication Server Benefits Lower TCO due to shared SAP HANA system Syndicated CAR data can be consumed directly by the other application (without replication) Best option to avoid data redundancy when co-deployed with the other application Considerations Check white-list for supported co-deployments: Note and consider additional efforts for operating multiple applications on one SAP HANA instance Proper sizing and resource planning required 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 26

27 Deployment of CAR Separately deployed from the consuming central application Possible Exception SAP CAR is coupled and shipped as a bundle with consuming retail applications (SAP CARAB) SAP CAR is integrated with another central application system (like SAP BW or SAP hybris Marketing) and serves as data provider for this application SAP CAR is deployed as part of SAP CARAB on a separate SAP NetWeaver AS ABAP and SAP HANA system Benefits AP ERP, SAP CAR/CARAB and the consuming analytical or transactional applications (like SAP BW or SAP hybris Marketing) can be operated isolated from each other No need to migrate SAP ERP or other application systems to SAP HANA first, allows to easily deploy SAP CAR/CARAB into an existing system landscape Considerations Deploying SAP CAR and the consuming analytical or transactional applications (like SAP BW or SAP hybris Marketing) separately result in additional data replication or data federation 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 27

28 Deployment of CAR Co-deployed with a consuming central application on the same SAP NetWeaver instance Not Supported SAP CAR is coupled and shipped as a bundle with consuming retail applications (SAP CARAB) SAP CARAB is integrated via SAP CAR with a central SAP ERP Retail system SAP CAR is integrated with another central application system and serves as data provider for this application SAP CAR is deployed as part of SAP CARAB and co-deployed with the other consuming analytical or transactional application on the same SAP NetWeaver AS ABAP and SAP HANA system Implications SAP NetWeaver version must fit for SAP Customer Activity Repository Application Bundle (CARAB) and the other consuming application like SAP BW An additional dependency is added to both applications Patches and corrections of SAP NetWeaver AS ABAP must be supported by SAP CARAB and the other application Upgrades of SAP CARAB might require a new SAP NetWeaver version, which is not yet supported by the other application Later separation of SAP CARAB for scale-out is technically not possible 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 28

29 Thank you Contact information: Matthias Steinwagner Retail Architecture Team Dirk Anthony Enterprise Architecture Team 2014 SAP AG or an SAP affiliate company. All rights reserved.

30 2015 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. 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. Please see for additional trademark information and notices. 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 SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE 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 platform 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 forwardlooking 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, which speak only as of their dates, and they should not be relied upon in making purchasing decisions SAP SE or an SAP affiliate company. All rights reserved.