What You Must Know to Make Your Conversion to SAP S/4HANA Seamless - PowerPoint PPT Presentation

What You Must Know to Make Your Conversion to SAP S/4HANA Seamless with SAP S/4HANA RIG Support Lars Rueter, Thomas Csapo • 5 September 2017

Legal Disclaimer The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related document, or to develop or release any functionality mentioned therein. This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation 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. This presentation is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross negligence. All forward-looking 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.

Agenda • Lessons Learnd • Guiding Architecture Principles • Transition Scenarios, System Conversion, Technical Procedure and Tools • Readiness Check, Custom Code, Back to Standard • Migration Cockpit / -Modeler, Data Migration Options • Q&A

LESSONS LEARNT – REGIONAL IMPLEMENTATION GROUP APJ

SAP S/4HANA Projects Overview • 2600+ active projects (800 in Asia) • 970+ live customers (340 in Asia) • All industries • New Implementations and System Conversions • 65 % of existing SAP ERP customers choosing System Conversion • Clear trend towards System Conversion

SAP S/4HANA Projects Insights from engaging with SAP S/4HANA implementation projects

Lessons Learned? SAP S/4HANA RIG Kno Knowled wledge ge Asse Assets ts on SAP SAP .C .COM OM reaching 14 140k 0k pa page ge views views + https://go.support.sap.com/ roadmapviewer

Based on the experience gained from current projects, a customer system will be affected by 30 to 50 of the currently around 400 Simplification Items

GUIDING ARCHITECTURE PRINCIPLES

The 3 Key Enablers For Digital Transformation SAP HANA AS THE UNDERLYING SIMPLIFICATION OF APPLICATIONS AND PLATFORM UNDERLYING DATA MODEL • • OLAP & OLTP MERGE NO AGGREGATES & NO INDICES • • IN-MEMORY COMPRESSION HIGHER FLEXIBILITY & THROUGHPUT SAP HANA • • INCREASE IN SPEED DATA FOOTPRINT REDUCTION SIMPLIFIED SAP FIORI • • WEB-BASED, ALL DEVICES SAP FIORI AS THE USER EXPERIENCE • (UX) PARADIGM; ROLE-BASED • • CROSS-APPLICATION USER EXPERIENCE DECISIVE, PREDICITVE, SIMULATION

High Level Stack Architecture SAP S/4HANA Architecture is much simpler than the Business Suite architecture • Data structures (Compatibility provided through Core Data Services) • Application engines • Launchpad / Fiori (SAPGUI for Windows still available for compatibility reasons On Premise)

The New S/4HANA Programming Model Search ONE UI Dashboard UI UI experience Business Business Analytical ONE application application application programming model ONE DATA TX SEARCH common data modelling ACCESS (OPEN SQL) (TREX) technology (ODP) ONE Database Any Database TREX BW SAP HANA

Programming model for SAP S/4HANA Efficient ABAP programming model for all types of SAP Fiori apps

TRANSITION SCENARIOS, SYSTEM CONVERSION, TECHNICAL PROCEDURE AND TOOLS

Release Strategy and Adoption Paths General availability (GA / RTC) Innovation path SAP S/4HANA 1809 Alternative path (as an example) SAP Guided Beta program Mainstream Maintenance – Feature Packages (FPs) SAP S/4HANA 1709 Mainstream Maintenance – Support Packages (SPs) Maintenance SAP S/4HANA 1610 Maintenance Line SAP S/4HANA 1511 Maintenance Line possible transition paths SAP ERP System SAP Release Strategy

3 Different Approaches to Move to S/4HANA Bring your business processes to the new platform • A complete technical in-place conversion of an existing SAP ERP SAP Business Suite ERP system to SAP S/4HANA. System On-Premise • System Adopt new innovations at your speed Conversion SAP S/4HANA New implementation / re-implementation Reengineering and process simplification based on SAP ERP On-Premise latest innovations or New 3 rd -party • Implement innovative business processes with best-practice Implementation System content on a new platform S/4HANA Cloud • Perform initial data load • Retire old landscape Value driven data migration to the new platform SAP ERP System Region A e.g. consolidation of current SAP Business Suite Landscape SAP ERP System landscape into one global SAP S/4HANA system or On-Premise Transformation Region B selective data migration based on legal entities SAP ERP System SAP S/4HANA Region C SCN Blog: How to find my path to SAP S/4HANA

The SAP S/4HANA Family and Transition Paths SAP Business Suite SAP S/4HANA family (e.g. BS7i2013) S/4HANA Cloud New implementation only! SAP ERP System (on AnyDB) or SAP Central Finance SAP S/4HANA Finance 1503, 1605 SAP ERP System (on SAP HANA) SAP S/4HANA (On-Premise) System Conversion New Implementation Landscape Transformation

Questions Influencing the Choice of Transition Scenario Custom Code System Requirements Business Processes New New System Conversion Implementation New System Conversion Implementation System Conversion Implementation A company has business processes that A company has checked and is able A company has restrictions that do to take over existing custom code. not allow to move to SAP S/4HANA already fit to the current requirements. on-premise in a one-step procedure. Time to Value New New System Conversion Implementation System Conversion Implementation A company wants to go live rather fast. A company seeks to fundamentally redesign its business processes.

Choice of Deployment • SAP S/4HANA and SAP S/4HANA Cloud share following characteristics for consistency at every level of your enterprise: – Share same code line – Designed for in-memory – Same simplified data model – Improved user experience • Important considerations: – Scope of business functionality (i.e. industry solutions) Cloud On-Premise – Deployment times – New Implementation New Implementation Update frequency / impact on running processes Landscape Transformation System Conversion – Customizations Landscape Transformation – Regulatory, industry, and regional requirements Perfect choice, if: – System operations skills and efforts ✓ Functional scope is sufficient – efforts for maintaining custom code and modifications during ✓ Focus is on Standardization every maintenance event ✓ Faster delivery on innovation

System Conversion – Transition Paths Overview The transition to SAP S/4HANA does not require the source system to be already on SAP HANA Database SAP ERP 6.0, EHP xx SAP S/4HANA 1709 System Conversion Paths (basically) AnyDB or SAP HANA SAP HANA From SAP Business Suite (ERP6.0, EHP xx, Any DB or SAP HANA DB) to SAP S/4HANA 1709 SPS00 Note 1 : For older SAP Business Suite releases or systems on Non-Unicode an additional step to SAP ERP 6.0 EHPxx is required. Conversion requirements incl. min./max. SP-level on source system: Note 2 : System has to be an AS ABAP-only system. Dual-stack systems (AS ABAP and AS Java 2482453 - SAP S/4HANA 1709: Release Information Note combined in one system) are not supported for the conversion. If your system is as dual-stack 2346431 - SAP S/4HANA 1610: Release Information Note system, you have to split it before doing the conversion. Note 3 : SAP Suite on HANA customers who are planning a system conversion to SAP S/4HANA 1709 should first update the database from SAP HANA 1.0 to SAP HANA 2.0 and then do the system conversion (either in the same or a separate downtime).