SAP Marketing Landscape Recommendation

1y ago
13 Views
2 Downloads
1.18 MB
22 Pages
Last View : 2m ago
Last Download : 2m ago
Upload by : Jenson Heredia
Transcription

Landscape DeploymentRecommendations forSAP MarketingSeptember, 2018PUBLIC

DisclaimerThis presentation outlines our general product direction and should not be relied on in making apurchase decision. This presentation is not subject to your license agreement or any otheragreement with SAP. SAP has no obligation to pursue any course of business outlined in thispresentation or to develop or release any functionality mentioned in this presentation. Thispresentation and SAP's strategy and possible future developments are subject to change and maybe changed by SAP at any time for any reason without notice. This document is provided without awarranty of any kind, either express or implied, including but not limited to, the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibilityfor errors or omissions in this document, except if such damages were caused by SAP intentionallyor grossly negligent. 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC2

Major Changes or UpdatesSummaryMajor changes or updates toformer landscape deployment recommendationsType of rentpresentation)Former StatusNew StatusReason(not available)Support forS/4HANA onpremiseAvailability ofS/4HANA on premise./.13-18Not SupportedComplex maintenance andsizing dependenciesCo-deployment withSAP CRM on sameAS ABAP systemSlide 17Possible ExceptionComplex CPU and sizingdependenciesHub Deployment withshared SAP HANAsystemSlide 14Complex CPU and sizingdependenciesHub Deployment withshared SAP HANAsystem, Side-by-SideDeployment withshared SAP HANAsystemSlide 15/16DeploymentRatingPossible ExceptionDeployment RatingGeneralRecommendationDeployment RatingReferenceReasonableAlternative 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLICPossible Exception3

AgendaIntroduction Methodology & Scope of Landscape Deployment RecommendationsBasic Landscape Setups Recommendations for SAP MarketingRecommendations SAP Marketing – UI deployment 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC4

IntroductionMethodology & Scope ofLandscape Recommendations

System Landscapes at CustomersDesigning the Optimal Landscape LayoutCustomerSAPProduct RoadmapsSAP ERPSAP SRMSAP SCMSAP nentsECCServerBusiness AspectsAS ABAPSRMServerABAPAS ABAPSCMServerABAPAS ABAPCRMServerABAPAS ABAPABAPSAP Business SuiteBackend SystemsSAPSolution ManagerSolMan ContentSolution MngComponentSLDDual StackJEEABAPSAP NetWeaver HubsApplication PortalBusiness WarehouseSEMBEx WebProcess IntegrationBICSESR ContentBI JAVAESR&SREPSLDAdditional SAP BS InstanceCentral BIContentPortalContentArchitecturalStrategyEP CoreAS JAVAOperationsCostsPIBWADOBEJEEAS ABAPABAPAS JAVAJEEPI Dual StackJEEABAPDeployment Recommendationsfor SAP ProductsSecuritySpeed ofInnovationPerformance &ScalabilityLegal Aspects OS/DB platformstrategySolution Landscapeof CustomerSLA &AvailabilityTechnical DocumentationIT Aspects 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC(Planning, Installation &Configuration Guides, etc.)6

Deployment Recommendations for SAP ProductsGuiding PrinciplesSAP ERPSAP SRMSAP SCMSAP nentsECCServerAS ABAPSRMServerABAPAS ABAPSCMServerABAPAS ABAPCRMServerABAPAS ABAPABAPSAP Business SuiteBackend SystemsSAPSolution ManagerSolMan ContentSolution MngComponentSLDDual StackJEEABAPSAP NetWeaver HubsApplication PortalBusiness WarehouseSEMBEx WebProcess IntegrationBICSESR ContentBI JAVAESR&SRAdditional SAP BS InstanceCentral BIContentPortalContentEP CoreADOBEAS JAVAPIBWJEEAS ABAPEPABAPAS JAVASLDJEESolution Landscapeof Customer PI Dual StackJEEABAPHigh-Level Guidancefor optimizedLandscape LayoutsDeployment Recommendationsfor SAP ProductsAllow flexibility by offering different deployment options (not one-size-fits-all)Provide guidance by rating different optionsEase decisions by listing pros & consSimplify consumption of information by using a common methodologyIncrease reliability by considering SAP product strategy, achieved landscape qualities andcross-product alignment 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC7

Ease Landscape Planning By Stronger GuidanceUsed MethodologyClear recommendations by categorization of deployment optionsPossible Exception Only useful for specific use casesSupported by SAP, but limitationsmight occurOption IIReasonable Alternative Useful choice for certain usecases or customer scenarios Supported and confirmed bySAP’s strategyGoalConsider 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLICGeneral RecommendationOptionIII Option IBest choice for majority of typicallandscape use cases Recommended by SAP’s strategy Accepted by a wide base ofcustomers 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 compensated8

Architecture OverviewSAP JAMUser InterfaceSAP Marketing UI: SAP Fiori with LaunchpadSAPCommerce/Web ShopSocial /WebCampaignOData via SAP Web DispatcherFioriSAP MarketingSAP CRMSAP ERPSAP C4CEmailServiceProviderSAP Application Server ABAPSMSServiceProviderSocial &ConsumerDataSAP Marketing: Tables, Views, Procedures, Search ModelsNon-SAP /Web PageSAP HANAPrivate Cloud On-Premise 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC9

Product Deployment ViewSAP Marketing in System LandscapesSAP WebdispatcherSAP CRMCRMSAPMarketingIntegrationMiddlewareUI for MKTMKTSAP ERP orS/4HANAERP or S/4AS ABAPPrimary DB connectionSAP HANA Systemfor MKTApplicationSystemHANA ContentMKTNON SAPSAP HANA 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLICMain required products External Application System based on SAP NetWeaverAS ABAP SAP Marketing (MKT) Add-On SAPUI5-based UI for MKT MKT content for SAP HANA SAP HANA system SAP BS application system replicating business data Integration Middleware SAP Process Integration (PI)/ SAP Cloud PlatformIntegration (CPI) for SAP ERP or S/4HANA, SAP CRM andNON-SAP applications on project basis SAP Landscape Transformation (LT) for SAP ERP andSAP CRM (not S/4HANA) SAP Data Services for NON-SAP applications10

Basic Landscape SetupsRecommendations forSAP Marketing

Deployment of SAP MarketingOverview of Recommended Landscape PatternsSAP CRMCRMSAPMarketingIntegrationMiddlewareUI for MKTMKTSAP ERP orS/4HANAGeneralRecommendationERP or S/4AS ABAPPrimary DB connectionSAP HANA Systemfor MKTApplicationSystemHANA ContentMKTNON SAPSAP HANAHub Deployment with separate SAPHANA system and separate AS ABAPSAP CRMCRMIntegrationMiddlewareSAPMarketingSAP ERPUI for MKTERPSAP CRMCRMMKTApplicationSystemAS ABAPAS ABAPNON SAPSAP ERP orS/4HANAERP or S/4SAP HANA Systemfor MKTHANA ContentMKTData WarehouseBWAS ABAPAS ABAPPrimary DB connectionsSAP HANA SystemApplicationSystemHANA ContentMKTHANA ContentBWNON SAPSAP HANAHub Deployment withshared SAP HANA systemof SAP Business Suite 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLICSAPMarketingUI for MKTMKTPrimary DB AP HANAHub Deployment withshared SAP HANA systemof other application12

Deployment of SAP MarketingHub Deployment with separate SAP HANA system and separate AS ABAPGeneral Recommendation(“Non-disruptive MKT deployment into existing SAP Business Suite landscape”) MKT centrally integrated with multiple business applications (e.g. SAP ERP or S/4HANA on premise, SAP CRM, NON-SAP)MKT deployed in the cloud or on-premise on a separate AS ABAP and SAP HANA systemAll required business data is replicated to the SAP HANA for MKT systemBenefitsExample SAP CRMCRMSAPMarketingIntegrationMiddleware UI for MKTMKTSAP ERP orS/4HANAERP or S/4AS ABAP Primary DB connectionSAP HANA Systemfor MKTApplicationSystem Fast adoption of MKT via hybrid cloud or separate on-premise deploymentIndependent innovation speed for new MKT capabilitiesIntegration of SAP ERP or S/4HANA with CRM business data for MKT possibleSimple sizingNo need to migrate SAP ERP or SAP CRM to HANA firstNo risk for existing SAP ERP/CRM system (performance, patching, downtime, etc.)HANA ContentMKTConsiderations One additional SAP HANA system required (could be deployed in the cloud) Connecting multiple SAP ERP or S/4HANA or multiple SAP CRM systems notsupportedNON SAPSAP HANA 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC13

Deployment of SAP MarketingHub Deployment with shared SAP HANA systemPossible Exception(“Deployment with shared SAP HANA”) MKT centrally integrated with multiple business applications (e.g. SAP ERP, SAP CRM, NON-SAP)MKT deployed on a separate AS ABAP system, but co-deployed on SAP HANA system of oneSAP Business Suite Application (SAP CRMonHANA or SAP ERPonHANA) or S/4HANABenefitsExample SAP CRMCRMIntegrationMiddlewareSAPMarketingSAP ERPUI for MKTERPMKTApplicationSystemIndependent innovation speed for new MKT capabilities Integration of SAP ERP or S/4HANA with SAP CRM business data for MKT possible Flexible decision which SAP HANA system to use (SAP CRM or SAP ERP)ConsiderationsAS ABAPAS ABAP Primary DB connections SAP HANA Systemfor MKT NON SAPHANA ContentMKT SAP HANA 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLICRequires at least SAP CRM 7.03 on SAP HANA (resp. SAP ERP 6.07 on SAP HANA)More complex SAP HANA sizingShared resources (CPU, memory) influence performance of other applications on top ofSAP HANA systemImpact on existing SAP HANA system during lifecycle operations (patching, downtime,etc.)Consider restrictions of SAP HANA co-deployments (SAP note 1826100, 2248291)Connecting multiple SAP ERP or multiple SAP CRM systems not supportedS/4HANA OnPremise cannot be integrated through cross schema access14

Deployment of SAP MarketingHub Deployment with shared SAP HANA system – General RemarksPossible Exception(“Deployment with shared SAP HANA”)Multiple Components one Database (MCOD)*SAP HANA ApplianceSAP HANA System SID DB Schema 1DB Schema 2 1 SAP HANA Appliance 1 SAP HANA System 1 SAP HANA Database n Applications in different schemasSAP HANA DatabaseDisksCPUsMemory* only supported for applications listed onwhite list (SAP Notes 1661202, 1826100 ) SAP HANA system shared with other whitelist applicationslike SAP CRM, SAP ERP or S/4HANA Other HANA applications SAP BWMulti Database Containers (MDC)SAP HANA ApplianceSAP HANA System SID System DatabaseDB SchemaDB SchemaTenantDatabase 1TenantDatabase 2Disks 1 SAP HANA Appliance 1 SAP HANA System n SAP HANA DatabasesCPUsMemory SAP HANA system shared with any other application Co-deployment on SAP HANA via MDC installation Replication of CRM, ERP or S/4HANA data into SAPMarketing has to be done via integration middleware Co-deployment on SAP HANA via MCOD installation Integration of ERP or CRM data across different schemasinto SAP Marketing 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC15

Deployment of SAP MarketingBusiness Warehouse Hub Deployment with shared SAP HANA systemPossible Exception(“Data sharing with other SAP HANA-based application”) MKT centrally integrated with multiple business applications (e.g. SAP ERP or S/4HANA, SAP CRM, NON-SAP)MKT deployed on a separate AS ABAP system, but co-deployed with other application(s), e.g. SAP BW, on same SAP HANA systemMKT and other SAP HANA-based application(s) allow data sharing within SAP HANA systemAll required business data is replicated to the SAP HANA systemBenefitsExample SAP CRMCRMIntegrationMiddlewareSAPMarketingData WarehouseUI for MKTBW MKTSAP ERP orS/4HANAAS ABAPAS ABAP Primary DB connectionsERP or S/4SAP HANA SystemApplicationSystem Independent innovation speed for new MKT capabilitiesIntegration of SAP ERP or S/4HANA with SAP CRM business data for MKT possibleLower TCO due to shared SAP HANA system and shared replication dataMutual data consumption between MKT and other SAP HANA-based application(e.g. ADT accessing SAP BW data)No risk for existing SAP ERP/CRM system (performance, patching, downtime, etc.)No need to migrate SAP ERP or SAP CRM to HANA firstHANA ContentMKTHANA ContentBWNON SAPSAP HANA 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLICConsiderations Connecting multiple SAP ERP or multiple SAP CRM systems not supported More complex SAP HANA sizing Impact on existing SAP HANA system applications(performance, patching, downtime,etc.) Co-deployment on SAP HANA only supported for applications listed on whitelist(SAP note 1661202)16

Deployment of SAP MarketingAdd-On Deployment with shared ABAP and SAP HANA systemNot Supported(“Hardware minimized deployment with SAP CRM on SAP HANA”) MKT locally integrated with SAP CRMMKT co-deployed on AS ABAP and SAP HANA system of SAP CRMSAP CRM business data is directly accessed by MKTImplicationsExample SAP CRM with SAP MarketingCRMMKT AS ABAP Primary DB connectionsSAP HANA SystemHANA ContentMKT Shared ABAP system not supported for SAP CRM (or any other SAP Business Suiteapplication or S/4HANA)Innovation speed for MKT dependent from SAP CRMHigh maintenance dependenciesHigh manual effort for later scale-out, if MKT needs to be separatedMore complex sizing (ABAP and SAP HANA)Impact on existing SAP HANA system of SAP CRM (performance, patching, downtime,etc.)Consider restrictions of SAP HANA co-deployments (SAP note 1826100)SAP HANA 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC17

Deployment of SAP MarketingHub Deployment with shared ABAP and SAP HANA systemNot Supported MKT centrally integrated with multiple business applications (e.g. SAP ERP, SAP CRM, NON-SAP)MKT co-deployed on AS ABAP and SAP HANA system with other ABAP-based SAP HANA applicationRequired business data is replicated to the SAP HANA systemImplicationsExample SAP Marketing andother applicationOtherapplicationUI for MKT MKTAS ABAPPrimary DB connectionsSAP HANA System No support of a co-deployment with any other application on the same AS ABAPsystemInnovation speed for MKT needs to be aligned with other applicationUpgrades may not be possibleLow maintenance flexibilityHigh manual effort for later scale-out, if MKT needs to be separatedMore complex sizing (ABAP and SAP HANA)Co-deployment on SAP HANA only supported for applications listed on whitelist(SAP note 1661202)HANA ContentMKTSAP HANA 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC18

RecommendationsSAP Marketing – UI Deployment

Deployment of UI for SAP MarketingEmbedded UI Deployment with MKT AS ABAP systemGeneral Recommendation UIs for MKT deployed within product SAP MarketingUIs for MKT locally integrated with MKT backend functionalityUIs for MKT co-deployed with MKT backend application on same AS ABAP systemSAP WebdispatcherExampleBenefits SAP CRMCRMSAPMarketingIntegrationMiddlewareUI for MKT MKT SAP ERP orS/4HANAERP or S/4AS ABAPPrimary DB connectionSAP HANA Systemfor MKTApplicationSystem Automated installation & configuration with MKT backend functionalityUI and MKT backend application automatically in syncLower alignment and regression test effort for updates (only MKT concerned)All MKT UIs are integrated within same environment (single URL, no Fiori Launchpadrequired)No additional system requiredLower maintenance effortHANA ContentMKTConsiderations Innovation speed of MKT UIs closely coupled with MKT backend functionality No cross-integration with other SAP Fiori UI applicationsNON SAPSAP HANA 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC20

Deployment of UI for SAP MarketingAdd-On Deployment with central SAP Fiori Front-End ServerNot Supported UIs for MKT co-deployed with SAP Fiori UIs of other applications on central Fiori Front-End ServerFiori Frontend ServerUI for MKTExampleFiori UIs of otherapplicationsUI Add-OnGateway ServerReasons End-user access to MKTSAPMarketingMKT UIs for MKT not shipped separately, but only as part of SAP MarketingManual additional installation & configuration for MKT backend connectivity requiredStrict version dependencies with MKT backend application, frontend and backend partsneed to be manually kept in syncAlignment and regression test effort for all UI applications after required updates of ASABAP of central Frontend-ServerAdditional system requiredPerformance and downtime side effects due to shared usage of Frontend-ServerAS ABAPPrimary DB connectionSAP HANA Systemfor MKTHana ContentMKTSAP HANA 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC21

Thank you.Contact information:By mail tosaphybrismarketingfeedback@sap.comor by a Support Incident on component nameCEC-MKT-ITC

SAP CRM CRM SAP ERP AS ABAP Integration Middleware Application System NON SAP SAP Marketing AS ABAP UI for MKT MKT ERP Possible Exception ("Deployment with shared SAP HANA") MKT centrally integrated with multiple business applications (e.g. SAP ERP, SAP CRM, NON-SAP) MKT deployed on a separate AS ABAP system, but co-deployed on SAP HANA .

Related Documents:

SAP ERP SAP HANA SAP CRM SAP HANA SAP BW SAP HANA SAP Runs SAP Internal HANA adoption roadmap SAP HANA as side-by-side scenario SAP BW powered by SAP HANA SAP Business Suite powered by SAP HANA Simple Finance 1.0 2011 2013 2014 2015 Simple Finance 2.0 S/4 HANA SAP ERP sFin Add-On 2.0

SAP Certification Material www.SAPmaterials4u.com SAP Certification Material for SAP Aspirants at Low cost Home Home SAP Business Objects SAP BPC CPM SAP BPC 7.0 SAP EWM SAP GTS SAP Public Sector SAP Real Estate SAP FSCM SAP FI/CO SAP AC - FI/CO SAP BI 7.0 SAP CRM 5.0

SAP Master Data Governance SAP Information Steward SAP HANA smart data integration SAP Data Hub SAP Cloud Platform Big Data Services SAP HANA, platform edition SAP Vora Customer Experience IoT Workforce Engagement SAP Cloud for Customer SAP Commerce SAP Marketing SAP Asset Intelligence Network SAP Predictive Maintenance and Service SAP .

SAP HANA Appliance SAP HANA DB In-Memory A io BI Client non-ABAP (SAP supported DBs) SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Warehouse SAP HANA DB r In-Memory Source Systems SAP LT Replication Ser

ALE/RFC Setup 88 SAP System Type 88 SAP IDoc Version 88 Program ID (SAP to e*Gate) 88 SAP Load Balancing Usage (e*Gate to SAP) 89 SAP Application Server (e*Gate to SAP) 89 SAP Router String (e*Gate to SAP) 90 SAP System Number (e*Gate to SAP) 90 SAP Gateway Ho

Customer Roadmap to SAP Simple Finance - Example " Adopting SAP Simple Finance is a journey - start early" Side-by-side SAP HANA Acceleration SAP HANA accelerators, BW, BPC, GRC SAP Business Suite on SAP HANA SAP ERP on SAP HANA SAP ERP in SAP HANA Enterprise Cloud SAP Accounting Powered By SAP HANA Simple Finance add-on/

SAP Business Suite SAP BW SAP Apps Partner Apps SAP HANA PLATFORM Planning and Calculation Engine Real-Time Replication Services Information Composer & Modeling Studio SAP UI HTML5 Mobile SAP BI 4 SAP ERP SAP CRM SAP SCM SAP PLM SAP SRM SAP Netweaver Predictive Analytics & Business Function Libraries In-Memory

Introduction: From Figure to Field There are, in fact, no cities anymore. It goes on like a forest. —Ludwig Mies van der Rohe, 1955 Landscape has recently emerged as model and medium for the contemporary city. This claim has been available since the turn of the twenty-first century in the discourse and practices the term “landscape urbanism” describes. This volume offers the first .