Transcription
The Path to S/4HANA:Transition Scenarios and Best Practices
Overview Transition Scenarios
Transition to SAP S/4HANAThree different approaches to move to SAP S/4HANABring your business processes to the new platformSystemConversionSAP ERPSystemSAP S/4HANAOn-Premise A complete technical in-place conversion of an existing SAPBusiness Suite ERP system to SAP S/4HANA. Adopt new innovations at your speedSAP S/4HANANewImplementationSAP S/4HANAOn-PremiseSAP ERP orThird-partySystemSAP S/4HANACloudRegion AERP SystemSAP S/4HANAOn-PremiseRegion BERP System Implement innovative business processes with best-practicecontent on a new platform Perform initial data load Retire old landscapeValue driven data migration to the new platformERP SystemLandscapeTransformationNew implementation / re-implementationReengineering and process simplification based onlatest innovationsSAP S/4HANAe.g. consolidation of current SAP Business Suitelandscape into one global SAP S/4HANA system orselective data migration based on legal entitiesRegion CSCN Blog: How to find my path to SAP S/4HANA 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀCustomer3
The SAP S/4HANA family and transition pathsSAP Business SuiteSAP S/4HANA family(e.g. BS7i2013)S/4HANA CloudNew implementation only!SAP ERP System(on AnyDB)orSAP S/4HANA Finance1503, 1605SAP ERP System(on SAP HANA) 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀSAP S/4HANA(On-Premise)System ConversionNew ImplementationLandscape TransformationCustomer4
Transition to SAP S/4HANASystem ConversionScenario descriptionA complete technical in-place conversionof an existing SAP Business Suite ERPsystem toSAP S/4HANA (Database, SAPNetWeaver and Application transition inone step).Software UpdateManager (SUM)with DatabaseMigration Option(DMO)SAP GUI*SAP ERP CoreWhy would you choose thisoption? Bring your existing business processesto the new platform.AnyDB / SAP HANA 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀSAP S/4HANA CoreSAP HANASAP ERP 6.0 (any EHP level) Keep your investment in custom code Mitigate the risk and investment of a bigbang conversion project by reducing thescope of the transition project to a puretechnical conversion project, and adoptnew innovations at your speed at a laterpoint of time and in a phased approach.(SAP GUI) / SAP Fiori*WhatHowIn-place technicalconversiontool-based technical conversion process of a SAP BusinessSuite ERP system to SAP S/4 HANA using SAP SoftwareUpdate manager (SUM);Downtime minimizing options availableSCN Blog: SAP S/4HANA System Conversion – At a glanceCustomer5
SAP S/4HANA system conversionOverview technical process stepsPreparation phaseSystemrequirementsMaintenanceplannerPre checksRealization phaseCustomCustom codecode preparationpreparationApplicationApplication specificspecific follow-upfollow-up activitiesactivitiesSoftware UpdateManager (SUM)Database migrationUnicodeconversionCross-application & application specific preparation activitiesSoftware updateData conversionSimplification List**)incl. migration of FICustomizing and Data*) incl.preparation offinancial data 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀCustomer7
Summary: Recommended Preparation for a System Conversion Project– Run the maintenance planner (https://apps.support.sap.com/sap/support/mp) early to confirm that yourSAP ERP system (including SAP and partner add-ons) can technically be converted to SAP S/4HANA.– Explore in the simplification list (http://help.sap.com/s4hana op 1610 - Simplification List) which of thefunctionalities relevant for you have changed. The simplification list is also available in XLS format, seenote 2313884.– Start early to clean up your customer and vendor data in your current SAP ERP system in preparationfor the Business Partner and Customer/Vendor Integration (CVI) in SAP S/4HANA. Further info in thesimplification list.– Check your custom code and optimize it for SAP S/4HANA. Further info on help.sap.com 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀCustomer8
Transition to SAP S/4HANANew ImplementationScenario descriptionNew implementation of SAP S/4HANA, e.g. forcustomers migrating a legacy system, also knownas “greenfield” approach.Why would you choose this option?Customers planning to migrate A non-SAP / 3rd-part legacy system, A good option for a SAP System, which may be Of an older release and/or Is highly customized/modified and/or Does not meet the system requirements fora technical system conversionBenefits for the customer are Reengineering and process simplificationbased on pre-configured business processesRapid adoption of new innovations in astandardized mannerStepsHowInstall SAP S/4HANASoftware Provisioning ManagerInitial data load fromsource system SAP S/4HANA Migration Cockpit SAP Data Services (SAP DS)both with best practice migration content 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀCustomer9
Transition to SAP S/4HANALandscape TransformationScenario descriptionM I G R A T EY O U RD A T ACustomers who want to consolidate theirlandscape or to selectively transform datainto a SAP S/4HANA system.LegacyWhy would you choose this option? Value-based migration: selective datatransformation allows a phased approachfocusing the first SAP S/4HANA migrationphase on parts of the business with highestROI and lowest TCIAgility: stay on current business processesbut move gradually to SAP S/4HANAinnovations Move to SAP S/4HANA atyour own paceTCO reduction: system and landscapeconsolidation with harmonized/simplifiedprocesses and unified master data lead tolower cost of operationsOn-Premiseselect – transform on the fly - insertTechnical migration on table level using pre-configured LT transformation solutionsConsolidationSelective DataTransformationSystem Merge of multiple source systems into one SAP S/4HANAsystem or transfer of clients into existing SAP S/4HANA system(build-up multiple client system)Migration of business units/single entities such as company codeRe-platforming scenarios, e.g. PP/DSReal-time repostingImplementation ofcentral finance *Real-time reposting of financial transactions into Central Financeinstance, e.g. to enable centralized reporting using SAP S/4HANA(synchronization of systems / side-car scenario)*) SAP S/4HANA for central finance foundation (Central Finance) 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀCustomer10
The Landscape Transformation option migrates data intoSAP S/4HANA systemsThe pre-configured Landscape Transformation Scenarios:- can migrate data into newly implemented SAP S/4HANA target systems as well as into systems created via system conversion procedure, before or after they are handed over to operations, and independent if they are foreseen for productive use or not.- can complement the other SAP S/4HANA transition optionsNote: SAP Landscape Transformation scenarios are supported within SAP S/4HANA Value Assuranceengagements. The transformation solutions mentioned for technical transformation are not generally released.Note 2: SAP is ready to discuss and support data migration requirements beyond the pre-configured use cases.Refer to the data migration services in the Activate phases prepare and explore for details.Transition to S/4HANA Roadmap Viewer 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀCustomer11
Best Practices & Q&A
Actual findings from customer projects & recommendations The average project duration (project start to go-live) is approx. 8-11 months System conversion projects are in average shorter than new implementation projects System conversion is apparently often chosen for doing a ‚technical uplift‘ to the SAP S/4HANA platform, intensive adoption of newSAP S/4HANA applications and Fiori UI Technology is not necessarily in the conversion project focus and will be often addressed infollow-up projects (big bang projects are less often). The share of customers choosing the system conversion path is increasing rapidly: 2015: 25% 2016: 39% 2017 to date: 83% SAP S/4HANA Finance (Add-On) and SAP S/4HANA projects have pretty much the same project duration In general a two step approach by moving to SAP S/4HANA via SAP S/4HANA Finance does not make sense Starting with a Central Finance Setup to start a step-by-step or process-by-process transition to SAP S/4HANAfor one or many SAP systems is not recommended. The objective of Central Finance is to enable a centralized corporate financial reporting, taking data from various source systems intoaccount. Customers wishing to move to SAP S/4HANA and to simplify their SAP landscape, should better consider the standard transitionscenarios. SAP offers tailored services as part of the SAP S/4HANA Value Assurance portfolio to properly plan the digitaltransformation. What is (the benefit of) a phased approach? Phased move to SAP S/4HANA by organization units (company code- / client-wise LT Scenario), vs.System conversion approach with scope limited to adapt currently running business processes to SAP S/4HANA For SAP ERP on any DB customers a two step approach via SAP ERP on HANA has in general no significant benefits(individual exceptions may make sense in case of for non-Unicode systems & for SAP ERP Systems releases SAP ERP 6.0)Customer 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ14
Migration to SAP S/4HANA – the earlier the betterSAP productdevelopmentSAP S/4 HANAbig gapMigration efforts Product development Intensity in useSmall gapSAP ERP on HANAtoday2025time 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀCustomer15
Functional scope: illustrative evolution of S/4HANA overtaking ECC 6 scopeECC 6ECC 6ECC 6ECC 6ECC 6any DB & SAP HANAany DB & SAP HANAany DB & SAP HANAany DB & SAP HANAany DB & SAP HANAInnovation scenarios (eg. Leonardo portfolio) not available for ECC landscape2015S/4HANA1503Initial shipmentS/4HANA Finance re-designedS/4HANA1511Material Management &Operations re-designed2016S/4HANA1610Industry CoverageS/4HANAfunctionallyIncreased Fiori app availabilityInitial Industry-to-Core releasesuperior to ECCExtended functionality unification 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ2017S/4HANA1709 2025 S/4HANA25xxSpecial Industry processesFiori Co-Pilot and Apps libraryFoundation for CRM back to coreCustomer16
SAP S/4HANAKey Innovation Evolution Commodity Management Sales – Electronic and Digital Payments GRC – Legal Control and Export Classification Projects support withMigration Cockpit and Migration Object Modeler Consumer Products – Catch Weight Management SAP S/4HANA Central Master Data Oil and Gas with SAP S/4HANA Finance – Machine Learning for automation capability Industry to core – Retail QM – Manage usage decisions and Analytics forQuantitative Results Consistent SAP Fiori User Experience EAM – Report and Repair Malfunction Optimized Portfolio and Project Management Embedded Software in Product Development Industry to core- Discrete Industries and Mill Products (DIMP) - Entire SAP S/4HANA Finance Scope included Effective Order Management and Billing Plan to Produce in ONE System(Production Planning and Detailed Scheduling – PP/DS) Efficient Procurement Accelerated Material Requirements Planning Real-time Inventory Management andMaterial ValuationSAP S/4HANA, on-premise edition 1511 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PLM – Visual Manufacturing Planner andRecipe Management Maximize Fiori Experience withSAP Fiori Overview Pages Predictive Analytics as a system of intelligence- Contract Consumption in Procurement Embedded Transportation Management Embedded SAP Extended Warehouse Management Demand Driven Manufacturing Integrated Quality Management Manufacturing Extension for Complex AssemblyIndustries advanced Available to Promise (aATP) Advance Variant ConfigurationSAP S/4HANA 1610SAP S/4HANA 1709 ** This is the current state of planning and may be changed by SAP at any time without notice.Customer17
Project timelines view: SoH is not a head start for S/4HANA later201720182019202020212022202320242025S/4HANA stabilisationYou are now adigital enterpriseS/4HANA go-liveS/4HANA Conversion projectS/4HANA Conversion project startS/4HANA License investmentSoH stabilisation & improvementsSoH go-liveSoH Migration projectno access to digital core innovationsadditional project budget needed within 5 years after upgrade to SoHorganisational change managementSoH Migration project startHANA License investmentInvesting in SoH now and S4HANA later will double the effort (and money) needed compared to investing in a S/4HANA Conversionproject now and keeping the system up-to-dateS/4HANA UpdateS/4HANA operational improvementsS/4HANA stabilisationS/4HANA go-liveYou are now adigital enterpriseS/4HANA Conversion projectS/4HANA Conversion project startS/4HANA License investmentS/4HANA Updates (non-mandatory) 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀCustomer18
SAP S/4HANA – Manage All Parts ProperlyFiori User ExperienceCustomers choose their own path Diversity of drivers – in all cases deployment ofSAP S/4HANA causes impactAttention to change management topics,relevant for customers but alsoimplementation partners S/4HANA is not erequisitesProjects Knowledge transfer is a key element Involve relevant stakeholders right from thebeginning: decision makers, key users, projectleads, partners, etc.Simplification means changeTools,MethodologyTechnologies, Configuration,Extensibility 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀCustomer19
SAP S/4HANA – Summary of Project Learnings and Success FactorsProject Preparation and Setup Start early Tailored up-skilling to understand boundaries and tools Set focus, assess impact, include business Understand the impact from the Simplification List Consider Fiori in every SAP S/4HANA roadmap Do the homework (specifically in the case of system conversions)Project Planning & Execution Familiarize with “top simplification items” (i.e. Business Partner,etc.) Exploration resp. sandbox conversions to optimize execution Demo early to key users to discuss value and changeStart today, not tomorrow! 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀCustomer20
Thank you.Diana TodorovaSAP S/4HANA Presales Expert, SAP SEE
APPENDIX
Where to go for more informationDiscover SAP S/4HANASAP S/4HANA TrialsSAP S/4HANARelease InfoSAP S/4HANARoadmapsSAP Help PortalJoin the SAPS/4HANA CommunityS/4HANA CookbookSAP S/4HANA FAQChoose your Pathto SAP S/4HANASAP Learning Hub 2017 SAP SE or an SAP affiliate company. All rights reserved.Internal23
SAP S/4HANACheck out the following links for more informationYou can find the “What’s New” and the “Feature Scope Description”with the entire information concerning the SAP S/4HANA 1610FPS02 delivery on the SAP HELP Page.Follow this link to the Bookhttp://help.sap.com/s4hana 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀCustomer24
Information about SAP S/4HANA 1709Innovation DiscoveryFollow this link to the Innovation DiscoverySAP S/4HANA Road MapsFollow this link to SAP Road Maps 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀCustomer25
System ConversionMaintenance Planner BlogPre-checks BlogCustom Code MigrationWorklist 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀCustomer26
SAP HANA SAP S/4HANA Core SAP GUI AnyDB / SAP HANA SAP ERP Core Software Update Manager (SUM) with Database Migration Option (DMO) What How In-place technical conversion tool-based technical conversion process of a SAP Business Suite ERP system to SAP S/4 HANA using SAP Software Update manager (SUM); Downtime minimizing options available * *
