The Road to S/4 HANA Deep Dive for IT

Transcription

1 The Road to S/4 HANA Deep Dive for IT Dr. Volkmar Jaeckle, Mario Weigend, Digital Business Services, SAP Switzerland Lothar Büttner, HANA Enterprise Cloud, MEE 13 September 2016 Customer

2 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 noninfringement. 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. Customer 2

3 » Introduction to Infrastructure and System Architecture» Major Elements of Transition Process» Details for each Transition Scenario» Supporting Services

4 SAP HANA Platform The data management and application platform for all applications All Devices SAP, ISV and Custom Applications S A P H A N A P L A T F O R M APPLICATION SERVICES PROCESSING SERVICES INTEGRATION & QUALITY SERVICES Web Server </> JavaScript Spatial Graph* Predictive Search Data Virtualization ELT & Replication ALM Fiori UX Graphic Modeler Application Lifecycle Management Text Analytics Streaming Analytics Series Data Business Functions Data Quality Hadoop & Spark Integration Remote Data Sync DATABASE SERVICES Columnar OLTP+OLAP Multi-Core & Parallelization Advanced Compression Multi-tenancy Multi-Tier Storage Data Modeling Openness Admin & Security High Availability & Disaster Recovery ONE Open Platform * Graph is in controlled availability OLTP + OLAP ONE Copy of the Data Customer 4

5 SAP S/4HANA, our next-generation business suite Internet of Things Business networks SAP Fiori user experience (UX) Role-based user experience for all devices SAP S/4HANA applications and extensions Instant insight-driven applications for all lines of business and industries SAP HANA platform In-memory platform for all data People Devices Social networks On-premise edition Cloud edition Big Data Native integration for hybrid scenarios Ariba Concur Fieldglass hybris SuccessFactors Customer 5

6 SAP S/4HANA Basic Architecture Options Deployment Model? Transition Scenario? System Architecture & Deployment Options Target Release? Sizing? Infrastructure Options Custom Code? Customer 6

7 Accelerate your Path to SAP S/4HANA with HEC TODAY Every landscape is different Customers manage governance Complexity slow down innovation INNOVATION ADOPTION Standardized core on HEC Use HCI for integration Make core S/4HANA ready ENTERPRISE AGILITY Accelerate innovation New Business Models Shared governance Complex Simpler Simple 7

8 SAP the cloud company powered by SAP HANA SAP HANA Enterprise Cloud Private Cloud & Managed Services SAP HANA Cloud Platform (PaaS) SAP Cloud Apps (SaaS) Build New Cloud Apps SAP-solutions and customer specific developed solutions based on SAP HANA Extend On-premise & Cloud Apps Integrate Everything S A P C l o u d I n f r a s t r u c t u r e 8

9 Standardized CLOUD packages Applications (S/4HANA Enterprise Mgmnt, engines, (users)) SAP HANA (Runtime or Enterprise Edition) Applications (BYOL/subscription) SAP HANA (BYOL/Subscription) ONE Price ONE Contract Standardized packages No modifications Infrastructure Application Management Service Application license subscription SAP HANA platform subscription Infrastructure and Services Application Management Service Cloud Enterprise Support On premise On premise deployment of S/4 HANA will continue to deliver new innovations, leveraging the potential of inmemory technology and new user interfaces. Custom HEC The SAP HANA Enterprise Cloud (HEC) offers individually sized infrastructure and application management services as additional, customer specific options to software licenses. S/4HANA Cloud Private Option Standardization, TCO and scalability of the cloud combined with the full functional scope, extensibility and geographical reach of the S/4HANA on premise solution HEC is the accelerated option to deploy S/4HANA S/4HANA Cloud Public Option Highly standardized, multi-tenant cloud services covering selected LoB- and industry scenarios and a comprehensive ERP scope 9

10 SAP HEC Nobody Knows SAP Better Than SAP SAP HANA ENTERPRISE CLOUD SECURITY INFRASTRUCTURE AND CLOUD MANAGED SERVICES ENTERPRISE APPLICATIONS ENHANCED MANAGED SERVICES 10

11 SAP HANA Enterprise Cloud - Proven Value % of HEC customers run SAP Business Suite powered by SAP HANA 32% include SAP BW and/or SAP BI Databases under management SAP HEC customers globally Global Data Center Coverage How does HEC bring value? Simplicity Experience Optimization Peace of Mind Foundation for Innovation 11

12 Transition to SAP S/4HANA On-Premise Editions and Adoption Paths Intermediate steps can be skipped! S/4HANA SAP S/4HANA, onpremise edition 1511 SAP S/4HANA, onpremise edition 1610 Several simplified solutions (finance + manufacturing + ) Innovation track New technical component Comprehensive scope, country & industry availability SAP ERP 6.0 EHPx S/4HANA Finance (add-on) SAP Simple Finance, on-premise edition 1503 (aka: Simple Finance 2.0) SAP ERP 6.0 EHP7 SAP S/4HANA Finance, on-premise edition 1605 SAP ERP 6.0 EHP8 Simplified Finance only for combination with classic logistics Ongoing improvements for Finance only Technical add-on to ERP Full scope / country & industry availability Suite on any DB Any DB Suite on HANA SAP ERP 6.0 EHP7 SAP HANA SAP ERP 6.0 EHP8 Classic functionality running on SAP HANA No further major innovations (besides legal requirements) Full scope / country & industry availability Customer 12

13 The Move to SAP S/4HANA The Transition Scenarios System Conversion ERP System On-Premise Cloud Example: Complete conversion of an existing SAP Business Suite system to SAP S/4HANA Landscape Transformation ERP System - Region A - ERP System - Region B - ERP System - Region C - On-Premise Cloud Example: Consolidation of current regional SAP Business Suite landscape into one global SAP S/4HANA system New Implementation ERP System Non-SAP System On-Premise Cloud Example: New or existing SAP customer implementing a new SAP S/4HANA system Customer 13

14 Sizing Process with SAP HANA Scalable HW offering Practical sizing Experience Different configurations Different technology partners Hardware Vendor Customer Sizing Recommendation CPU (SAPS) Memory (GB) Disk Space (GB) Component performance Requirements Performance Business SLAs Business figures Final Sizing HW partner responsible Sizing Tools & Reports Sizing Guidelines Sizing Verification SAP Customer 14

15 Sizing with SAP HANA installations Sizing Scenarios Sizing New Applications Initial Sizing Migrating to SAP HANA Applications Productive Sizing Sidecar Scenarios Sizing 1. SAP QuickSizer tool 2. SAP Note Available Tools/Resources 1. Stand-alone HANA: SAP Note SAP Business Suite or Industry Solutions Powered by SAP HANA: SAPNote SAP NetWeaver BW Powered by SAP HANA: SAP Note SAP HANA Enterprise Search: SAP Note CO-PA Accelerator: HANA Sizing for CO-PAAccelerator 3. SAP Applications on HANA: SAP QuickSizer Tool 1. Please check SAP HANA Sizing Overview for latest updates. 2. Consider Sizing paper for SAP HANA 3. General statement: Prefer a scale-up before starting to scale-out to multiple boxes (SAP HANA Scalability document Chapter 4.5) 4. Special requirements for BW and Scale-Out: SAP note (discontinued note ) check attachments Customer 15

16 SAP HANA Datacenter Integration Concepts (TDI) Appliance vs. Tailored Data Center Integration SAP HANA Appliance: All in one box TDI: Use your own preferred solutions Database Database SAP HANA Server Server Node Node Server Node Operating System Virtualization Server Certified by SAP Operating System Server Virtualization SAP HANA Server Server Node Node Server Node Appliance Built-in Storage Network Network Enterprise Storage Storage Storage Pre-assembled, pre-installed and pre-configured hardware and software. Complete package certified by SAP Custom assembled hardware from SAP-certified components. Software installed by SAP-certified engineer Customer 16

17 HANA DB Deployment Deployment Options 1 of 2 - Details 1 Dedicated 2 Physical Part. 3 MDC 4 MCOD 5 Virtualized 6 MCOS SAP System 1 SAP System 2 SAP System 1 SAP System 2 SAP System 1 SAP System 2 SAP System 1 SAP System 2 SAP System 1 SAP System 2 SAP System 1 SAP System 2 DB Schema DB Schema DB Schema DB Schema DB Schema DB Schema DB Schema DB Schema DB Schema DB Schema DB Schema DB Schema DB Tenant DB Tenant SAP HANA SAP HANA SAP HANA SAP HANA SAP HANA SAP HANA SAP HANA SAP HANA SAP HANA SAP HANA VM + OS VM + OS OS + Server OS + Server OS + HW Partition Server OS + HW Partition OS + Hardware OS + Hardware Hypervisor Hardware OS + Hardware Storage Storage Storage Storage Storage Storage Storage Production Production (with restrictions) Non-Prod. only Customer 17

18 HANA DB Deployment Deployment Options 2 of 2 - Details 1 Dedicated 2 Physical Part. 3 MDC 4 MCOD 5 Virtualized 6 MCOS Classical scenario Appliance approach for optimal performance 1 x Hardware + OS 1 x HANA DB 1 x DB schema 1 x System (e.g. ERP, CRM or BW) Physical Server Partitioning Server is physically split into fractions. No Performance impact 1 x Hardware 2 x HW partitions + OS 2 x HANA DB 2 x DB schema 2 x Systems (e.g. ERP, CRM or BW) See note MDC Multitenant Database Containers 1 x Hardware + OS 1 x HANA DB 1 x System DB Container n x Tenant DB Containers n x Systems Productive usage See note MCOD Multiple Components on one Database 1 x Hardware + OS 1 x HANA DB n x DB schema n x Systems Productive usage for white listed scenarios only. See notes and Virtualization VMware virtualization technology. Hitachi LPAR Separate OS images each containing one HANA DB 1 x Hardware n x VM + OS n x HANA DB n x DB schema n x Systems HANA on Virtualization see note MCOS Multiple Components on one System 1 x Hardware + OS n x HANA DB n x DB schema n x Systems E.g. DEV and QA system on one hardware. See note Production Production (with restrictions) Non-Prod. only Customer 18

19 » Introduction to Infrastructure and System Architecture» Major Elements of Transition Process» Details for each Transition Scenario» Supporting Services

20 What is the impact of SAP HANA on your custom code? A Can any custom ABAP code cause potential functional issues requiring it to be changed? B Is any custom ABAP code likely to cause performance issues with SAP HANA? C Which of the main businesses processes have the potential for HANA to speed up massively? Customer 20

21 Functional considerations A SAP HANA migration is just a DB migration Everything works as before, except : Native SQL with vendor-specific statements Database hints Relying on undocumented behavior: Implicit DB sorting Checking for existence of secondary indices Direct access to physical pools / clusters Run Code Inspector using check variant «FUNCTIONAL_DB» * 1) Use of native SQL EXEC SQL.... ENDEXEC. * 2) Native SQL via ADBC lo_result = NEW cl_sql_statement( )->execute_query( 'SELECT ROWNUM, * && 'FROM SNWD_BPA' ). * 3) Database Hints SELECT * FROM snwd_so INTO wa FOR ALL ENTRIES IN lt_fae WHERE node_key = flt_fae-node_key %_HINTS MSSQLNT '&prefer_join 0&'. * 4) Relying on implicit sorting SELECT * FROM my_table INTO TABLE lt_data WHERE id < 100. READ TABLE lt_data WITH KEY id = 10 BINARY SEARCH. * 5) Check for secondary index IF ( lv_index_exists = abap_true ).... ENDIF. Customer 21

22 Row vs Columnar Layout Columnar table layouts enables very fast column scans as they can sequentially scan the memory, allowing e.g. on the fly calculations of aggregates. Row Layout Column Layout Customer 22

23 N-Tuple Reconstruction Example: the size of one tuple is 200 byte; the number of attributes in the tuple is 6. Assumptions: speed of the read operation from main memory: 4 MB/ms/core; 64 byte long cache lines; Tuple reconstruction response time (row layout) = 256 byte / 4 MB/ms = microseconds Tuple reconstruction response time(column layout) = 384 byte / 4 MB/ms = microseconds Columnar layout is 50% worse in comparision with row layout (gets progressively worse when we increase the number of a tuple s attributes) => Select only the necessary fields of a tuple Customer 23

24 Performance considerations B Well-written ABAP code runs immediately much faster on SAP HANA Performance optimization potential Critical constructs according to the performance guidelines Constructs with low DB performance profile Run Code Inspector using check variant «FUNCTIONAL_DB_ADDITIONAL» ** SOME PERFORMANCE OPTIMIZATION CANDIDATES * 1) pure existence check no field used after FORM_mara_exist_check USING mara-matnr CHANGING rc. SELECT SINGLE * FROM mara INTO wa_mara WHERE matnr = i_matnr. rc = sy-subrc. ENDFORM. * 2) Nested SELECT loops (across modularization units) LOOP AT it_mara INTO mara. PERFORM mara_exist_check USING mara-matnr CHANGING rc.... ENDLOOP. * 3) SELECT + SELECT FAE SELECT vbeln FROM vbak INTO lt_vbak1 WHERE.... SELECT vbeln FROM vbak INTO lt_vbak1 FOR ALL ENTRIES IN lt_vbak1 WHERE vbeln = lt_vbak1-table_line. Customer 24

25 Optimize custom code for SAP HANA Efficient analysis Use monitoring and trace tools to measure the usage of ABAP and SQL in your productive system 1. Use Usage Procedure Logging (UPL) to separate not used (dead) code 2. Use the standard performance trace tools (ST05, SAT, ) to analyze your core business processes 3. Find the performance hotspots with the SQL Monitor Relevant for performance optimizations Not relevant for performance optimizations Unused Code Covered by monitoring tools Customer 25

26 SAP S/4HANA Custom Code Overview Within the SAP S/4HANA system conversion project you can distinguish between the following steps related to your custom code:» Step 1: Get transparency on your custom code» Step 2: Remove waste» Step 3: Analyze the impact, and create a plan» Step 4: Do the required custom code changes Custom Code Guide Use of traditional custom-code related tooling and new tooling:» Custom Code Lifecycle Management» Usage and Procedure Logging (UPL)» SAP Code Inspector» ABAP Test Cockpit (ATC)» Custom Code Migration Worklist (new) For more information about the Custom Code Check tool, see SAP Help Portal: Link and the following SCN blog :SAP S/4HANA Custom Code Migration Worklist. Customer 26

27 SAP S/4HANA, on-premise edition 1511 Simplification List Overview Simplification List Area Area Area Simplification Item Simplification Item Simplification Item Simplification Item Simplification Item Simplification Item Simplification Item Simplification Item Basic Information Description Edition / Release Category Impact Description Related Services Customer Effort Recommendation Service Offering Custom Code Re-architecting for SAP HANA in-memory platform Data model changes Removal of aggregates Material Master field length extension Consolidation of existing Functionality Merge Transaction No functional equivalent Customer 27

28 SAP S/4HANA, on-premise edition 1511 FPS 02 Simplification List» Currently we have 293 Simplification List Items. They fall basically into three categories» Based on our current project experience in average Simplification Items are finally relevant for a dedicated customer ~17% ~59% ~24% ~ 33% functional equivalent available ~ 26% functional equivalent not available Change of existing functionality: 17% (50/293) Example: Simplifications of Data Structure (for example in Sales & Distribution) Functionality not available within SAP S/4HANA (with or without functional equivalent): 59% (175/293) Example: FI-AR-CR Credit Management is not available, functional equivalent is FIN-FSCM-CR ITS Services in QM are not available without direct successor Not the target architecture: 24% (68/293) functionality still available Example: The Warehouse Management (LE-WM) is not the target architecture. The (already available) alternative functionality is SAP EWM. Current Version: Simplification List for SAP S/4HANA, onpremise edition 1511 FPS02: Link SAP S/4HANA SCN: Further Details for selected Simplification Items (e.g. Business Partner Approach, Material Field Length extension, ): Link Customer 28

29 SAP S/4HANA, on-premise edition 1511 Simplification Item Database Overview Customers SAP Business Suite On-Premise Landscape Source ERP System see SAP note Development Custom Code Extractor ABAP Netweaver 7.5 System Simplification Item: < Simplification Item ID > Simplification Item: < Simplification Item ID > Simplification Item: < Simplification Item ID > Impact Impact Custom Code Impact Impact Custom Code Impact < Related Piece List > + related SAP Note Custom Code Impact < Related Piece List > + related SAP Note < Related Piece List > + related SAP Note Transaction SE01 Simpl. DB File Custom Code Custom Code Analysis Tools Custom Code Analysis Results SAP Notes SAP Note 1 SAP Note 2 SAP Note 3 SAP Note x Custom Code Management (SAP NW 7.50) SAP Service Marketplace File Customer 29

30 » Introduction to Infrastructure and System Architecture» Major Elements of Transition Process» Details for each Transition Scenario» Supporting Services

31 The Move to SAP S/4HANA The Transition Scenarios System Conversion ERP System On-Premise Cloud Example: Complete conversion of an existing SAP Business Suite system to SAP S/4HANA Landscape Transformation ERP System - Region A - ERP System - Region B - ERP System - Region C - On-Premise Cloud Example: Consolidation of current regional SAP Business Suite landscape into one global SAP S/4HANA system New Implementation ERP System Non-SAP System On-Premise Cloud Example: New or existing SAP customer implementing a new SAP S/4HANA system Customer 32

32 Transition to SAP S/4HANA Scenario 1 System conversion Scenario description Customers who want to change their current system into a SAP S/4HANA system. Change Database, SAP NetWeaver and application transition in one step. SAP GUI SAP ERP Core Software Update Manager (SUM) with Database Migration Option (DMO) * SAP S/4HANA On-premise Edition (SAP GUI) / SAP Fiori SAP S/4HANA Core AnyDB / SAP HANA SAP HANA Benefits + Migration without re-implementation + No disruption for existing business processes + Re-evaluation of customization and existing process flows What Installation and migration How Rapid Database Migration of SAP Business Suite to SAP S/4HANA (all one step migration, including data conversion) using SUM with DMO Customer 33

33 Transition to SAP S/4HANA Scenario 2 Landscape Transformation Scenario description Customers who want to consolidate their landscape or to selectively transform data into a SAP S/4HANA system. Consolidation or selective data transformation based on SAP LT SAP S/4HANA On-premise Edition SAP S/4HANA Cloud Edition (SAP GUI) / SAP Fiori Benefits SAP S/4HANA Core + Value-based migration: selective data transformation allows a phased approach focusing the first S/4HANA migration phase on parts of the business with highest ROI and lowest TCI + Agility: stay on current business processes but move gradually to S/4HANA innovations (Move to S/4HANA at your own pace!) + TCO reduction: system and landscape consolidation with harmonized/ simplified processes and unified master data lead to lower cost of operations 1 2 What Consolidation Selective Data Transformation How SAP HANA SAP Landscape Transformation Consolidate clients from different source systems into one new or existing S/4HANA system (build-up multiple client system) SAP Landscape Transformation Carve-out of single entities or processes Migration of selected SAP applications (example: central Finance) Customer 34

34 Transition to SAP S/4HANA Scenario 3 New Implementation Scenario description New installation of SAP S/4HANA e.g. for customers migrating a legacy system. SAP ERP 6.0 or higher SAP S/4HANA On-premise Edition SAP S/4HANA Cloud Edition Non-SAP Legacy Any customers legacy system Option: Initial data load from Legacy or SAP system based on SAP LT SAP Fiori SAP S/4HANA Core SAP HANA Benefits for the customer + Reengineering and process simplification based on ready-to-run business processes and reference solution delivered with the product + Pre-defined migration objects & Best Practices available in a guided process 1 2 What Install S/4HANA Initial data load from source system How Software Provisioning Manager SAP Landscape Transformation SAP source: system connection Legacy system: file upload; SAP Data Services additionally supported Customer 35

35 Degree of Simplification Transition to SAP S/4HANA compare transition scenarios The transition scenarios differ with respect to amount & type of data taken over New installation: Master Data & selected transactional data System conversion: entire repository New Implementa tion Cloud Quadrant Landscape Transformat ion Rule of thumb: Cloud deployment model when simplification is ultimate goal On-premise deployment model is universally suited On-premise System Conversion Amount of transferred data Customer 36

36 SAP S/4HANA Implementation Roadmap Prepare Explore Realize / Deploy All Implementation Scenarios Dependent on Implementation Scenarios Migrate Existing System Conversion Technology driven migration offerings Value Discovery Workshop Strategy & Roadmap Technical Architecture & Migration Planning Landscape Transformation Business driven migration offerings New Install New Implementation On S/4 HANA on premise and cloud Implement new innovations Installation and data transition for SAP S/4HANA + Implement additional industry / LOB packages SAP Support and Premium Engagement (optional) Customer 37

37 The Road to SAPACTIVATE is the unique combination of SAP Best Practices, Methodology, and Guided Configuration to simplify the adoption of SAP S/4HANA delivers ready-to-run business processes optimized for SAP S/4HANA New Implementation System Conversion Landscape Transformation provides best practices for migration, integration and configuration for SAP S/4HANA is geared for a speedy initial implementation of SAP S/4HANA and is designed for continuous innovation supports different starting points for customers to adopt SAP S/4HANA - new implementation, system conversion and landscape transformation SAP S/4HANA On-Premise Edition SAP S/4HANA Cloud Edition Customer 38

38 » Overview Transition Scenarios Implementation Roadmap» Details per Transition Scenario System Conversion Landscape Transformation New Implementation

39 The Move to SAP S/4HANA The Transition Scenarios System Conversion ERP System S/4HANA On-Premise Example: Complete conversion of an existing SAP Business Suite system to SAP S/4HANA Landscape Transformation ERP System - Region A - ERP System - Region B - ERP System - Region C - On-Premise Cloud Example: Consolidation of current regional SAP Business Suite landscape into one global SAP S/4HANA system New Implementation ERP System Non-SAP System On-Premise Cloud Example: New or existing SAP customer implementing a new SAP S/4HANA system Customer 40

40 Possible Upgrade Path Software Packages and related product names SAP FINANCIALS 1503 Official Name: SAP Simple Finance, onpremise edition 1503 SAP S/4HANA ON- PREMISE 1511 Official Name: SAP S/4HANA, on-premise edition 1511 SAP SFINANCIALS 1605 Official Name: SAP S/4HANA Finance, onpremise edition 1602 SAP S/4HANA CLOUD 1608 Official Name: SAP S/4HANA, cloud edition 1608 SAP S/4HANA ON- PREMISE 1610 Official Name: SAP S/4HANA, on-premise edition 1610 ERP 6.07 SPS04 EA-FIN 720 SAP FIN 720 FSCM CCD 720 S4CORE 100 on NW 7.50 FINBASIS 800 FI-CA 800 ERP 6.08 SAP FIN 730 FSCD CCD 730 SAP GATEWAY 2.0 S4CORE101 on NW 7.64 SUITE CORE 105 S4CORE101 on NW 7.51 FINBASIS 801 FI-CA 801 SAP GATEWAY 2.0 Customer 41

41 SAP S/4HANA System Conversion Sequence Prepare Phase Realize Phase t 1 t 2 t 3 t 4 t 5 t Maintenance Planner Pre-Checks Custom Code Migration Worklist Software Update Manager (SUM) Application specific follow-on activities Simplification List SAP S/4HANA, on-premise edition Database Migration Software Update Data Conversion Customer 42

42 SAP S/4HANA, on-premise edition System Conversion Application Innovation Simplified Data Model Increased Throughput Innovation Compatibility SAP S/4HANA On-premise Edition SAP GUI SAP ERP Core (SD, MM, LO, FIN, HR ) SAPGUI for Windows still available Compatibility Views Stable Interfaces (SAP GUI) / SAP Fiori SAP S/4HANA Enterprise Mgmt. (Sales, Service, Procurement Supply Chain, Manufacturing, Financials ) AnyDB / SAP HANA Maintenance Planner SUM DMO SAP HANA Technical Change Semantical Change Simplification List Conversion Pre- Checks Custom Code Analysis Customer 43

43 SAP S/4HANA System Conversion Compatibility & Innovation SAPGUI for Windows SAP FIORI is our User Interface Go-To Architecture, but for compatibility reasons SAPGUI for Windows is still available (for exception see Simplification List). Compatibility Views Application Innovation Simplified Data Model Increased Throughput SAP tries to keep migration effort on custom code as low as possible. Compatibility views allow to keep read access unchanged. Additional tool support to detect custom Code Adaption effort. Innovation Compatibility SAPGUI for Windows still available Compatibility Views Stable Interfaces Stable Interfaces The interfaces to integrate external systems are adapted in a compatible manner. Same Inbound Data are mapped to new data structure where required. SAP S/4HANA, on-premise edition, currently supports the existing published legacy interfaces. Customer 44

44 SAP S/4HANA System Conversion Technical Procedure & Semantic Adaption Maintenance Planner Simplification List Sizing SUM DMO Technical Change Semantical Change Conversion Pre- Checks Custom Code Analysis Maintenance Planner The Maintenance Planner checks the system with regards to business functions, industry solutions, and add-ons. If there is no valid path for the conversion (for example, the add-on is not released yet), the Maintenance Planner prevents the conversion. Software Update Manager (SUM) with Database Migration Option (DMO) The Software Update Manager (SUM) is the SAP tool that is used to update software. It is the main tool used to convert your system to SAP S/4HANA, on-premise edition. If your source system is not yet running on SAP HANA database, use the database migration option (DMO) of the Software Update Manager to migrate your database to SAP HANA during the conversion. Simplification List To allow our customers a better planning and estimation of their way to S/4HANA, we have created the Simplification list. In this list we are describing in detail on a functional level what happens in S/4HANA to individual transactions and solution capabilities. If some transactions or capabilities are falling away, this does not mean that we are decommissioning functionality, but that we have merged this functionality with other elements or reflected it within a new solution / architecture. Pre-Checks Pre-checks are shipped as SAP Notes to customers that want to convert to S/4HANA. Customers can use these pre-checks to find out what mandatory steps they have to carry out before converting to S/4HANA. The results list the instances that need addressing before attempting the conversion process. The checks are run twice again during the conversion process: both times in the Software Update Manager (SUM). The conversion is stopped if errors persist. Custom Code Checks These checks are based on the Simplification list concept. S/4HANA simplifies business processes. Before converting to S/4HANA, you need to check your custom code against the S/4HANA simplifications. These simplifications are loaded into the Custom Code Check Tool. After you run the tool, you obtain a list of instances where your custom code does not comply with the scope and data structure of SAP S/4HANA 1511, on-premise edition. Customer 45

45 SAP S/4HANA System Conversion Example Activities during the different phases in logistics Pattern 1: Activity before migration + downtime Material Ledger Inventory valuation not supported in SAP S/4HANA. Switch to material ledger can be done before migration (activation of ML supported via dedicated report) During downtime ML migration to new logic. Pattern 2: Activity before or after migration BOM-Determination One Logic for BOM-Determination only via production version. Conversion to new logic via report possible before and after migration possible, has to run before starting MRP in SAP S/4HANA Pattern 3: Activity after migration Simplification of MRP areas One logic for all storage location MRP-Logic. In case of using such logic, program needed to create missing MRP-areas and MRP-File before running MRP in SAP S/4HANA Pattern 4: Technical migration MM-IM Conversion of IM-Tables (MSEG) into new MATDOC Customer 46

46 Welcome to the world of Unicode! System Conversion requires a Unicode (UC) source system Non-Unicode source systems will require a two-step approach SUM creates a shadow system to reduce downtime processing Shadow system is based on target release kernel SAP S/4HANA Shadow system has to be non-uc for non-uc source systems not possible for target systems based on SAP NetWeaver 7.5 Based on SAP NetWeaver 7.5: only Unicode (UC) No non-uc kernel Customer 47

47 Source system is Unicode: One-step system conversion possible Legend From Suite From ERP on HANA From S/4HANA AnyDB SAP HANA DB non-hana DB CVI: Customer-Vendor-Integration, prerequisite for System Conversion SUM w/ DMO SUM SAP Simple Finance 1503 SUM SAP S/4HANA Finance 1602 SAP S/4HANA May be on Unicode, but CVI not available, so 2 steps SAP ERP 5.0 & SAP R/3 4.7 SAP ERP 6.0 EHP x 7 SAP ERP 6.0 EHP 7 / 8 AnyDB AnyDB EHP / x 7.40 EHP 7 / 8* EHP 7 EHP 8 S/4CORE 7.40 / Customer 48

48 SAP S/4HANA System Conversion Details of simple Finance Data model of classic Finance BSEG COEP FAGLFLEXA Line items tables BSID COSS COSP Index and totals tables Technical Upgrade Persistency layout is prepared during technical upgrade. COSS COSP BSID - Rename Totals Tables - Create ACDOCA - Create Compatibility Views BSEG COEP FAGLFLEXA BSID_BCK COSS_BAK COSP_BAK ACDOCA Technical Downtime: few hours Data-Migration Line Items are merged into the new Universal Journal (ACDOCA). Runtime: depends on table size BSEG COEP FAGLFLEXA BSID_BCK COSS_BAK COSP_BAK COSS COSP BSID ACDOCA Customer 49

49 The Move to SAP S/4HANA The Transition Scenarios System Conversion ERP System S/4HANA On-Premise Example: Complete conversion of an existing SAP Business Suite system to SAP S/4HANA Landscape Transformation ERP System - Region A - ERP System - Region B - ERP System - Region C - On-Premise Cloud Example: Consolidation of current regional SAP Business Suite landscape into one global SAP S/4HANA system New Implementation ERP System Non-SAP System On-Premise Cloud Example: New or existing SAP customer implementing a new SAP S/4HANA system Customer 50

50 SAP S/4HANA Landscape Transformation Project Phases 1 Prepare Analyze involved systems to collect project relevant information to support project scoping and selection of the right Transformation Solutions 2 Explore Determine and pick required business from Business Object Directory (BOD) or create new Execute context based analysis to identify active objects and customer tables Define selection criteria and assign transformation rules 3 Realize in n-test cycles and Deploy Generate runtime objects in the test and productive landscape Execute (test-) migrations and conversions Technology Foundation SAP LT Platform running on SAP Solution Manager Analysis, Design, Execution and Process Control functions Integrated Transformation Solutions: Migration (OBMIG), Conversion (OBCNV) and Posting (OBPOE) Customer 51

51 SAP S/4HANA Landscape Transformation System Consolidation Consolidation from multiple dimensions Example: System Consolidation Start Release SAP ERP Core AnyDB or SAP HANA Start Release SAP ERP Core AnyDB or SAP HANA SAP S/4HANA On-premise Edition SAP Fiori SAP S/4HANA Best Practices SAP HANA SAP S/4HANA Cloud Edition Consolidation and harmonization of two or more SAP source systems into one (central) SAP S/4HANA system Significant simplification effects can be realized using this approach Initial analysis needed to determine business related descisions Customer 52

52 The Move to SAP S/4HANA The Transition Scenarios System Conversion ERP System S/4HANA On-Premise Example: Complete conversion of an existing SAP Business Suite system to SAP S/4HANA Landscape Transformation ERP System - Region A - ERP System - Region B - ERP System - Region C - On-Premise Cloud Example: Consolidation of current regional SAP Business Suite landscape into one global SAP S/4HANA system New Implementation ERP System Non-SAP System On-Premise Cloud Example: New or existing SAP customer implementing a new SAP S/4HANA system Customer 53

53 SAP S/4HANA New Implementation Guided Configuration Data Migration The data migration activities can be executed based on the cloud implementation cockpit Based on the selected Business Scenarios relevant data migration objects are proposed Existing customer can connect their SAP Business Suite system. For new customer a template based approach can be used Customer 54

54 SLT SLT SAP S/4HANA New Implementation Data Migration Functionality (Cloud) SAP Business Suite (Source System) (a) Virtual private network (VPN) (b) S/4HANA Cloud (Target System) Customer Master (classic) SLT (c) Customer Master (S/4HANA) (a) (b) (c) SAP Landscape Transformation (SLT) Tool required on customers OP system Customer need to establish VPN connection to OP System For new customers (legacy migration) a template-based approach is used (XLS). Data Extraction Transfer into new data structure Data Mapping API/BAPI Call SAP S/4HANA Cloud System SAP Cloud Operations: provision of cloud instance Customer: Implement configuration in target Customer: Implement integration to SAP Business Suite System or use template-based approach Service Center: Re-Implement customer enhancements SAP S/4HANA Cloud Data Migration Consulting Service: Maintain data mapping (Business Objects to be transferred) in SLT Transfer of master data; Transfer of transactional data Customer: Data Validation Customer 55

55 Extract & Profile SAP S/4HANA New Implementation Data Migration based on SAP Data Services Legacy Data Environment Data Staging and Test Environment Loading Target Environment 7 1 Legacy Applications & Cloud Applications Legacy Databases (ODBC) 2 Performance Analysis Staging Area Dashboards and Business Reporting 3 Cleanse Name Parsing, Address Parsing and Correction, Material/Product Parsing, Matching Transform Transform data into SAP structure WebService IDocs 5 Flat Files, XML, HTML, CSV, Mainframe, Microsoft Excel Validate & Load Business Validation Rules, Automatic SAP Configuration validation Reconciliation Transparency, Governance and Communication 4 SAP Configuration Extraction 6 Customer 56

56 Your way to SAP S/4HANA Summary Scenario 1: System Conversion DESCRIPTION BENEFITS TARGET GROUP Customers who want to change their current system into a SAP S/4HANA system. Migration without reimplementation No disruption for existing business processes Re-evaluation of customization and existing process flows Transformation over time SAP Business Suite customers with SAP ERP or SAP Business Suite on SAP HANA as starting point Scenario 2: Landscape Transformation DESCRIPTION BENEFITS TARGET GROUP Customers who want to consolidate their landscape or carve out selected entities or processes into a SAP S/4HANA system. Stay with current business processes and move gradually to S/4HANA innovations Harmonized business processes and shared master data through consolidation Carve out of single entities of the company to SAP S/4HANA and leverage process simplification. SAP Business Suite customers with multiple SAP ERP or SAP Business Suite on SAP HANA systems, or hybrid cases Scenario 3: New Implementation DESCRIPTION BENEFITS TARGET GROUP New installation of SAP S/4HANA e.g. for customers migrating a legacy system. New implementation of industry-leading Business Suite Reengineering and process simplification based on ready-to-run business processes and reference solution delivered with the product SAP Business Suite customers or net new customers Customer 57

57 » Introduction to Infrastructure and System Architecture» Major Elements of Transition Process» Details for each Transition Scenario» Supporting Services

58 Starter Workshop S/4 HANA Advise and Plan with You 1 WHAT WE ARE PROVIDING YOU WHY YOU CAN BENEFIT 2 3 HOW WE WILL PLAN AND DELIVER Free 1 to 1,5 day innovation focused workshop Outside-In approach to provide best and leading practices from SAP experts based on customer insight Introduce a point of view for potential areas of innovation for your company Provides a framework to discover beneficial business scenarios enabled by SAP HANA Learn the value of achieving Real-Time business intelligence Ability to accelerate adoption for your HANA investment Review your current challenges and provide real benefits the SAP HANA platform can provide your company Help you plan to move very quickly from initial vision to realization 0,5-1d Account Team Prep 1-1,5d On-Site 1-2h Virtual (Account Team & Customer) Solid Preparation Point of View Light Document Innovation Workshop Use Case Input As-Is Alignment Follow-Up Meeting Point of View Completed (High Value Use Cases) Finalize Scope with Customer To-Be Discovery Adoption Path & Next Steps Customer 59

59 Technology Business Discovery and Roadmap Service for SAP S/4HANA 1. Your business situation with relevant system information is gathered in an up-front validation by automated assessment tools. 2. Onsite workshops that provide a framework to understand SAP S/4HANA scope tailored to your enterprise and to discover beneficial business scenarios enabled by SAP S/4HANA. 3. Discussions yield a high-level heat map for relevant scope of SAP S/4HANA. SAP S/4 HANA Discovery Service SAP S/4HANA incremental benefits matched to your business scenarios and today s usage of SAP ERP Initial guidance on transformation paths for a successful SAP S/4HANA adoption Can be combined with TCO / ROI / Business Case Services Customer 60

60 Your Value Discovery Service Results Business Scenario Recommendation report outlining areas where S/4HANA provides new innovation and benefits Documented workshop results with S/4 HANA value deck and tailored heat map showing affected solution capabilities High level roadmap with based on identified implementation strategy and transformation path Customer 61

61 The SAP Value Assurance Commitment to your Success with SAP S/4HANA We are fully committed to helping our customers thrive in the Digital Age with SAP S/4HANA. Bill McDermott, CEO, SAP SE We offer end-to-end solution guidance We deliver value by linking your business & technology We use cloud as an accelerator We adapt our solutions to fit your business model changes Customer 62

62 Involvement of SAP Partner/Customer Involvement of SAP Involvement Partnering for Success with SAP S/4HANA Value Assurance Partner- or customer-led projects Complemented by service packages Partner or customer value delivery SAP-led projects Individually scoped Full engagement coverage Full responsibility Plan and safeguard Technical implementation Migrate and implement Innovate and optimize SAP S/4HANA Value Assurance Engagement Scope Engagement Scope Engagement Scope Customer 63

63 INVOLVEMENT OF SAP SAP S/4HANA Value Assurance Service Packages Defined Services, Defined Outcome, at a Defined Price What you get Innovate and optimize 4 Innovate and optimize: Expands the context of innovation beyond the digital core to reimagine business models across the enterprise. This is the most comprehensive level. Migrate and implement 3 Migrate and implement: Implements functions with preconfigured setup and ready-to-use business process templates, as well as analyzing operations impact. Technical implementation 2 Technical implementation: Focuses on the technical implementation, including data and system migration, high availability, and disaster recovery. Plan and safeguard 1 Plan and safeguard: Helps define the implementation strategy with a technical coach, including dependencies and prerequisites for the target architecture. ENGAGEMENT SCOPE Customer 64

64 Technical Architecture Overall Innovation Strategy & Road Map Creation Trial System Provisioning Starter Workshop Value Discovery Workshop Transition Planning Transition Preparation Production Cutover Value and Impact Analysis Implementation Strategy Safeguarding Handover to Support Organization SAP S/4HANA Implementation Project Mgmt. Application: Solution Adopt. Application: Design & Configuration DISCOVER PREPARE QG1 EXPLORE QG2 REALIZE QG3 DEPLOY QG4 RUN Init Planning Execution / Monitoring / Controlling Closing Team Enablement Training Strategy Training Enabled End User Training Delivery Activate Solution / Sandbox Fit Gap / Delta Design *) Build Design Support Data Volume Planning Gap Validation Data Volume Strategy Engagement Foundation Design Review Organizational Change Management (OCM) Configuration (General, Master Data, Core & Delta) *) Build Execution Product Enhancements Cleanup / Archive Data Aging Config. Integration Validation 16Q2 ( ) QG5 LT Central Design Finance Support Design LT Execution Central Finance Implementation * Analytics & D. Boardroom Analytics & Digital Design Boardroom Support Design Analytics Execution Analytics & Digital Boardroom Configuration Custom Code Extensions Application: Testing System & Data Migration Planning the Digital Transformation CC. Cleanup & Improve CC. Impact Analysis CC. Management Execution Project Delivery Platform Setup Custom Code Management Build Design Test Support Planning Sandbox System Setup Data Load Preparation LT Design Support DEV Setup Test Preparation QAS Setup Platform Execution Load & Verification Build Execution Landscape Transformation Design LT Scenario Implementation *) Test Execution Cutover Preparation LT Execution Dress Rehearsal Hyper Care Support Technical Architecture & Infrastructure Transition to Operations Initial Sizing Technical Architecture Definition Platform Design Support IT Infrastructure Definition Operations Impact Evaluation Technical Blueprint Sizing & Scalability Verification IT Infrastructure Setup & Test Transition to Operations Operations Implementation IT Infrastructure Service Finalization Operations Readiness Quality gates Service Packages: Planning & Safeguarding Certain planning constraints Technical such as regulatory Implementation and licensing issues are outside Migrate of our control & Implement and may impact the timelines LT = Landscape Customer Transformation 65

65 Recommandations Put SAP Strategy / Roadmap today keep eye on vision Check SAP Cloud offerings SAP innovations early by migrating to HANA Special offers from SAP (Starter Workshop, Value Discovery Service) Implementation with Value Insurance Package Check pre-requisites today Consider running long running pre-checks on a S/4 HANA project system Customer 66

66 Where to go for more information

67 SAP S/4HANA, on-premise edition 1511 Cookbook Customer 68

68 SAP S/4HANA More Information SAP Help (Guides) Getting Started With SAP S/4HANA, on-premise edition 1511: Link Conversion Guide for SAP S/4HANA 1511: Link Simplification List for SAP S/4HANA, on-premise edition 1511 FPS02: Link Conversion of SAP Systems to SAP S/4HANA, OnPremise Edition Using Software Update Manager: Link SAP S/4HANA SCN S/4HANA SCN: Link S/4HANA Cookbook: Link System Conversion: Link TOP Items: Link Custom Code: Link Customer 69

69 Thank you Dr. Volkmar Jaeckle S/4 HANA Program Manager SAP (Schweiz) AG Althardstrasse 80 CH-8105 Regensdorf T volkmar.jaeckle@sap.com Mario Weigend Senior Technical Consultant SAP (Schweiz) AG Althardstrasse 80 CH-8105 Regensdorf T mario.weigend@sap.com Lothar Büttner Head of Program Execution MEE SAP Deutschland SE & Co.KG Hasso-Plattner-Ring 7 D Walldorf/Baden T lothar.buettner@sap.com

70 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. Customer 71