ADM328. SAP S/4HANA Conversion and SAP System Upgrade PARTICIPANT HANDBOOK INSTRUCTOR-LED TRAINING

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "ADM328. SAP S/4HANA Conversion and SAP System Upgrade PARTICIPANT HANDBOOK INSTRUCTOR-LED TRAINING"

Transcription

1 4/21/2018 SAP e-book ADM328 SAP S/4HANA Conversion and SAP System Upgrade... PARTICIPANT HANDBOOK INSTRUCTOR-LED TRAINING Course Version: 18 Course Duration: 5 Day(s) e-book Duration: 7 Hours Material Number:

2 4/21/2018 SAP e-book SAP Copyrights and Trademarks 2017 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 corporate-en/legal/copyright/index.epx 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 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.

3 4/21/2018 SAP e-book Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used. This information is displayed in the instructor s presentation Demonstration Procedure Warning or Caution Hint Related or Additional Information Facilitated Discussion User interface control Window title Copyright. All rights reserved. iii

4 4/21/2018 SAP e-book Copyright. All rights reserved. iv

5 4/21/2018 SAP e-book Contents vii Course Overview 1 Unit 1: Concept and Architecture 2 Lesson: Architecture of an SAP System 6 Lesson: Concept of the Upgrade and SAP S/4HANA Conversion 8 Lesson: Considerations 11 Unit 2: SAP S/4HANA Conversion - Overview 12 Lesson: SAP S/4HANA Conversion - Overview 28 Unit 3: Maintenance Planner 29 Lesson: SAP Solution Manager and Maintenance Planner 33 Lesson: Plan a Software Change 39 Unit 4: SAP S/4 HANA Conversion - Prepare Phase 40 Lesson: Pre-Checks 44 Lesson: Custom Code Migration 52 Lesson: Cross-Application Preparations 53 Unit 5: SUM - Manual Preparation Activities 54 Lesson: Performing Steps from SAP Notes 58 Lesson: Performing Steps from the SUM Guides 60 Lesson: Performing Steps from the Application Guide 61 Lesson: Performing Steps from the ASU Toolbox 63 Unit 6: SUM - Prepare Part 64 Lesson: Concept of the SUM 68 Lesson: Using the SUM 71 Lesson: Configuration of the SUM 84 Unit 7: Modification Adjustment 85 Lesson: Concept of Modification Adjustment 92 Lesson: Performing SPDD 93 Lesson: Performing SPAU 96 Unit 8: SUM - Execution Part 97 Lesson: SUM Procedure 112 Lesson: Troubleshooting 120 Lesson: Database Migration Option (DMO) Copyright. All rights reserved. v

6 4/21/2018 SAP e-book 131 Unit 9: Downtime 132 Lesson: Concept of Downtime 136 Lesson: Downtime of the SUM procedure 141 Lesson: Incremental Table Conversion (ICNV) 150 Lesson: Near-Zero Downtime Maintenance (NZDM) Capabilities of SUM 156 Lesson: Downtime-Optimized Data Conversion 165 Unit 10: Upgrade of an SAP System Landscape 166 Lesson: Upgrade of a 3-System-Landscape 177 Lesson: SAP S/4HANA - Landscape Transformation 187 Unit 11: Activating Business Functions 188 Lesson: Concept of Business Functions 193 Lesson: Activation Procedure 199 Lesson: Transport of Business Functions 201 Lesson: SAP S/4HANA and Business Functions 204 Unit 12: Unicode Conversion 205 Lesson: Concept of Unicode 211 Lesson: Performing a Unicode Conversion 222 Unit 13: SUM - Manual Follow-up Activities 223 Lesson: Performing Steps from SAP Notes 226 Lesson: Performing Steps from the SUM Guides 228 Lesson: Performing Steps from the Application Guide 229 Lesson: Performing Steps from the ASU Toolbox 230 Unit 14: SAP S/4HANA Conversion - Follow-on Activities 231 Lesson: SAP S/4HANA Conversion - Follow-on Activities 235 Unit 15: Exercises and Solutions 236 Lesson: Exercises and Solutions Copyright. All rights reserved. vi

7 4/21/2018 SAP e-book Course Overview TARGET AUDIENCE This course is intended for the following audiences: Copyright. All rights reserved. vii

8 4/21/2018 SAP e-book Copyright. All rights reserved. viii

9 4/21/2018 SAP e-book UNIT 1 Concept and Architecture Lesson 1 Architecture of an SAP System 2 Lesson 2 Concept of the Upgrade and SAP S/4HANA Conversion 6 Lesson 3 Considerations 8 UNIT OBJECTIVES explain the architecture of an SAP system explain the concept of an upgrade and an SAP S/4HANA conversion determine considerations of an upgrade and an SAP S/4HANA conversion Copyright. All rights reserved. 1

10 4/21/2018 SAP e-book Unit 1 Lesson 1 Architecture of an SAP System LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the architecture of an SAP system Architecture of an SAP System Figure 1: SAP Business Suite, SAP ERP, SAP NetWeaver The SAP Business Suite consists out of the solutions SAP ERP (Enterprise Resource Planning), SAP CRM (Customer Relationship Management), SAP SCM (Supply Change Management), SAP SRM (Supplier Relationship Management) and SAP PLM (Product Lifecycle Management). SAP ERP consists out of SAP ECC (ERP Central Component), SAP XSS (Employee/Manager Self Services), SAP XECO (Accelerated ECommerce), SAP BW (Business Warehouse), SAP Enterprise Portal, SAP PI (Process Integration) and many more. These are upgradeable units. You can not update or upgrade (to) SAP ERP in general. You can upgrade (to) SAP ECC or SAP BW and so on. Copyright. All rights reserved. 2

11 4/21/2018 SAP e-book Lesson: Architecture of an SAP System Figure 2: Releases of SAP Business Suite and SAP Solutions inside This slide shows some examples of which releases of the solutions are part of a certain release of the SAP Business Suite. For example SAP Enhancement Package 8 for SAP ERP 6.0 (SAP ERP 6.0 EHP8) and others are part of SAP Business Suite 7 Innovations 2016 (SAP Business Suite 7i2016). Figure 3: SAP R/3 4.6C and SAP R/3 Enterprise 4.7 SAP ECC was called SAP R/3 in older releases. This slide shows - as an example - the release of the software components of an SAP R/3 4.6C and an SAP R/3 Enterprise 4.7. SAP_ABA 620 and SAP_BASIS 620 are part of SAP NetWeaver Copyright. All rights reserved. 3

12 4/21/2018 SAP e-book Unit 1: Concept and Architecture Figure 4: SAP ECC 6.00 and SAP ECC 6.07 This slide shows - as an example - the release of the software components of an SAP ECC 6.0 and an SAP ECC SAP ECC 6.07 is part of SAP Enhancement Package 7 for SAP ERP 6.0 (SAP ERP 6.0 EHP7). SAP_ABA 740 and SAP_BASIS 740 are part of SAP NetWeaver 7.4 (SAP NetWeaver 7.4). SAP Enhancement Package 7 for SAP ERP 6.0 is part of SAP Business Suite 7i2013 (BS7i2013). Figure 5: SAP ECC 6.08 and SAP S/4HANA 1511 This slide shows - as an example - the release of the software components of an SAP ECC 6.08 and an SAP S/4HANA SAP ECC 6.08 is part of SAP Enhancement Package 8 for SAP ERP 6.0 (SAP ERP 6.0 EHP8). SAP_ABA 750 and SAP_BASIS 750 are part of SAP NetWeaver 7.5. Copyright. All rights reserved. 4

13 4/21/2018 SAP e-book Lesson: Architecture of an SAP System SAP Enhancement Package 8 for SAP ERP 6.0 is part of SAP Business Suite 7 Innovations 2016 (BS7i2016). SAP S/4HANA is a separate product. SAP S/4HANA Server 1511 is part of SAP S/4HANA Figure 6: AS ABAP 7.51 only and SAP S/4HANA 1610 This slide shows - as an example - the release of the software components of an AS ABAP only system and an SAP S/4HANA SAP S/4HANA Server 1610 is part of SAP S/4HANA SAP_ABA 75B and SAP_BASIS 751 are part of SAP NetWeaver 7.51 for S/4HANA. SAP_ABA 751 and SAP_BASIS 751 are part of SAP NetWeaver 7.51 Innovation Package. This can be used stand alone or as a Frontend Server for an SAP S/4HANA system, for example. LESSON SUMMARY You should now be able to: explain the architecture of an SAP system Copyright. All rights reserved. 5

14 4/21/2018 SAP e-book Unit 1 Lesson 2 Concept of the Upgrade and SAP S/4HANA Conversion LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the concept of an upgrade and an SAP S/4HANA conversion Concept of the Upgrade and SAP S/4HANA Conversion Figure 7: Implementation Scenarios - Examples This course ADM328 shows a S/4HANA Conversion to SAP S/4HANA 1610 of an SAP ECC 6.00, running on an SAP MaxDB database. Copyright. All rights reserved. 6

15 4/21/2018 SAP e-book Lesson: Concept of the Upgrade and SAP S/4HANA Conversion Figure 8: Upgrade of an SAP ECC: Example In this example: For the time being, only a new business function in SAP_HR and EA-HR is required and therefore activated. SAP_ABA and SAP_BASIS are active in any case. Figure 9: SAP S/4HANA Conversion of an SAP ECC: Example From a technical point of view, a conversion to SAP S/4HANA works like an upgrade. But from a development or project point of view, there a several additional steps to be performed. LESSON SUMMARY You should now be able to: explain the concept of an upgrade and an SAP S/4HANA conversion Copyright. All rights reserved. 7

16 4/21/2018 SAP e-book Unit 1 Lesson 3 Considerations LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: determine considerations of an upgrade and an SAP S/4HANA conversion Considerations Figure 10: Complexity Drivers An upgrade project is more or less complex, depending on several drivers. There are IT related and business related complexity drivers. Copyright. All rights reserved. 8

17 4/21/2018 SAP e-book Lesson: Considerations Figure 11: Comparison of Upgrade Experiences in Business Suite and NetWeaver SAP Business Suite and SAP NetWeaver products are compared with an average SAP ECC upgrade project. The average SAP ECC upgrade project is defined based on figures from SAP Upgrade Experience Database from Nov 2008 (~290 entries) for upgrades to SAP ECC 6.0. Comments: * SCM downtime: 2-6h SCM Server + 3-6h Live Cache export/import Figure 12: Long-Term Predictability: Maintenance for SAP Business Suite Copyright. All rights reserved. 9

18 4/21/2018 SAP e-book Unit 1: Concept and Architecture To manifest the long-term predictability of the Business Suite and in support of the Innovation Strategy and Roadmap the standard maintenance was extended. SAP extended mainstream maintenance for the Business Suite core applications through December For details check the Product Availability Matrix at support.sap.com/pam. Figure 13: SAP Upgrade Newsletter - Register NOW! The upgrade homepage is at support.sap.com/upgrade. LESSON SUMMARY You should now be able to: determine considerations of an upgrade and an SAP S/4HANA conversion Copyright. All rights reserved. 10

19 4/21/2018 SAP e-book UNIT 2 SAP S/4HANA Conversion - Overview Lesson 1 SAP S/4HANA Conversion - Overview 12 UNIT OBJECTIVES give an overview of the SAP S/4HANA conversion process Copyright. All rights reserved. 11

20 4/21/2018 SAP e-book Unit 2 Lesson 1 SAP S/4HANA Conversion - Overview LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: give an overview of the SAP S/4HANA conversion process SAP S/4HANA Conversion - Overview Figure 14: SAP S/4HANA On-Premise Copyright. All rights reserved. 12

21 4/21/2018 SAP e-book Lesson: SAP S/4HANA Conversion - Overview Figure 15: Overview and Sequence SAP provides a process for the conversion to SAP S/4HANA, on-premise edition The graphic gives an overview of the tools, the phases, and the activities involved in the process. We recommend that you do the activities in the sequence shown in the graphic and explained in the lesson. Simplification List To enable you to do an optimal planning of your path to SAP S/4HANA, on-premise edition 1610 FPS 02, we provide the Simplification List for SAP S/4HANA, on-premise edition 1610 FPS 02. In this list we describe in detail what happens in SAP S/4HANA, on-premise edition 1610 FPS 02 to individual transactions and functions. For more information, see the SAP Help Portal at help.sap.com/s4hana_op_1610_002 Simplification List or the corresponding collective SAP Note that references the individual SAP Notes or each simplification item. Copyright. All rights reserved. 13

22 4/21/2018 SAP e-book Unit 2: SAP S/4HANA Conversion - Overview Figure 16: Prepare Phase Figure 17: Realize Phase Copyright. All rights reserved. 14

23 4/21/2018 SAP e-book Lesson: SAP S/4HANA Conversion - Overview Figure 18: SAP S/4HANA - Overview Figure 19: SAP S/4HANA - The Three Transition Scenarios Figure 20: System Conversion towards the SAP S/4HANA Family Copyright. All rights reserved. 15

24 4/21/2018 SAP e-book Unit 2: SAP S/4HANA Conversion - Overview Figure 21: SAP S/4HANA - Simplified Data Model Figure 22: SAP S/4HANA System Conversion: System Requirements Figure 23: Transition Paths to move to SAP S/4HANA - Overview Copyright. All rights reserved. 16

25 4/21/2018 SAP e-book Lesson: SAP S/4HANA Conversion - Overview Figure 24: Transition paths to move to SAP S/4HANA - Details (1/2) Figure 25: Transition paths to move to SAP S/4HANA - Details (2/2) Figure 26: Size is important: Minimize & Optimize Data Volume of SAP Systems & Control Data Growth Copyright. All rights reserved. 17

26 4/21/2018 SAP e-book Unit 2: SAP S/4HANA Conversion - Overview Figure 27: SAP S/4HANA System Conversion - Simplification List 1 Figure 28: SAP S/4HANA System Conversion - Simplification List 2 Figure 29: SAP S/4HANA System Conversion - Simplification List 3 Copyright. All rights reserved. 18

27 4/21/2018 SAP e-book Lesson: SAP S/4HANA Conversion - Overview Figure 30: SAP S/4HANA Conversion - Maintenance Planner Figure 31: SAP S/4HANA Conversion - Maintenance Planner - Overview Figure 32: SAP S/4HANA Conversion - Maintenance Planner - Checks Copyright. All rights reserved. 19

28 4/21/2018 SAP e-book Unit 2: SAP S/4HANA Conversion - Overview Figure 33: SAP S/4HANA Conversion - Pre-Transition Checks 1 Figure 34: SAP S/4HANA Conversion - Pre-Transition Checks 2 Figure 35: SAP S/4HANA Conversion Custom - Code Migration Worklist Copyright. All rights reserved. 20

29 4/21/2018 SAP e-book Lesson: SAP S/4HANA Conversion - Overview Figure 36: SAP S/4HANA Conversion - Custom Code Related Process Figure 37: SAP S/4HANA Custom Code: Overview Figure 38: SAP S/4HANA Custom Code Migration Worklist & Code Inspector Copyright. All rights reserved. 21

30 4/21/2018 SAP e-book Unit 2: SAP S/4HANA Conversion - Overview Figure 39: Project Planning Aspects - High-Level Example Project Plan Figure 40: SAP S/4HANA Conversion - Technical Conversion Figure 41: Simplification in SAP S/4HANA Copyright. All rights reserved. 22

31 4/21/2018 SAP e-book Lesson: SAP S/4HANA Conversion - Overview Figure 42: SUM is the Tool for the Technical Conversion to SAP S/4HANA Figure 43: Standard Approach (High Level) Copyright. All rights reserved. 23

32 4/21/2018 SAP e-book Unit 2: SAP S/4HANA Conversion - Overview Figure 44: System Conversion to SAP S/4HANA Figure 45: SAP S/4HANA Transition Paths to Move to SAP S/4HANA - Overview Copyright. All rights reserved. 24

33 4/21/2018 SAP e-book Lesson: SAP S/4HANA Conversion - Overview Figure 46: Downtime Optimized Data Conversion Approach (High Level) Table conversion: move to uptime processing for FIN & Material Ledger (MM-ML) (currently manual action after SUM run) for Inventory Management (MM-IM) (currently part of downtime processing in SUM) Field conversion: move to uptime processing KONV and VBFA tables Speed up setup of long material number for source systems with DIMP-LAMA usage Mapping of existing long material number (DIMP-LAMA) handled in uptime Usage applies only to specific SAP S/4HANA target product versions, and SUM patch level (Delta replay mechanism ensures that any uptime changes are considered) Downtime-Optimized Data Conversion is available as pilot,applicable technique depends on path (source & target) and schedule Customer projects will have to request participation as pilot project,involvement of colleagues from SAP Consulting / Active Global Support is a must Accepted projects benefit from direct development support, and reduced downtime;project will require at least one test run without optimization and one test run with optimization Pilot requests can be posted via incident on component BC-UPG-DTM-TLA,acceptance depends on system landscape, SAP involvement, and capacity of development team Copyright. All rights reserved. 25

34 4/21/2018 SAP e-book Unit 2: SAP S/4HANA Conversion - Overview Figure 47: SAP S/4HANA Conversion: Application Specific Follow-on Activities Figure 48: SAP Fiori Front-End Server Deployment Options SAP S/4HANA In case you are using an embedded FES FES will be updated to SAP NetWeaver automatically along the SAP S/4HANA conversion In case you are using a hub-deployment It is recommended to update the hub to SAP NetWeaver 7.51; SAP S/4HANA apps may be deployed during the update (use maintenance planner to calculate maintenance transaction) old SAP Fiori apps (connected to existing backend systems) will continue to work Note: SAP Fiori front end server will have to run either on SAP MaxDB, SAP ASE or SAP HANA as a database see SAP Note Copyright. All rights reserved. 26

35 4/21/2018 SAP e-book Lesson: SAP S/4HANA Conversion - Overview Figure 49: Considerations LESSON SUMMARY You should now be able to: give an overview of the SAP S/4HANA conversion process Copyright. All rights reserved. 27

36 4/21/2018 SAP e-book UNIT 3 Maintenance Planner Lesson 1 SAP Solution Manager and Maintenance Planner 29 Lesson 2 Plan a Software Change 33 UNIT OBJECTIVES start the Maintenance Planner for an upgrade and an SAP S/4HANA conversion use the Maintenance Planner for an upgrade and an SAP S/4HANA conversion Copyright. All rights reserved. 28

37 4/21/2018 SAP e-book Unit 3 Lesson 1 SAP Solution Manager and Maintenance Planner LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: start the Maintenance Planner for an upgrade and an SAP S/4HANA conversion SAP Solution Manager and Maintenance Planner Figure 50: Unit 3 - The Major Technical Steps Copyright. All rights reserved. 29

38 4/21/2018 SAP e-book Unit 3: Maintenance Planner Figure 51: Starting SUM: Request for Stack Configuration File A properly installed SAP Solution Manager system and the Maintenance Planner are required to generate the xml file. Figure 52: Overview SAP Solution Manager: Preparation for Maintenance Planner When using SAP Solution Manager 7.1 and if the target release is based on AS ABAP 7.40 and below: the Maintenance Optimizer (MOpz) instead of Maintenance Planner (MP) can be used. In case MOpz is used, a Product System has to be defined in LMDB. When using SAP Solution Manager 7.2 or if the target release is based on AS ABAP7.50 and above: the Maintenance Planner (MP) hast to used. In any case the Maintenance Planner (MP) should be used. Copyright. All rights reserved. 30

39 4/21/2018 SAP e-book Lesson: SAP Solution Manager and Maintenance Planner Figure 53: Starting the Maintenance Planner and Selecting the SAP System(s) Select SAP system(s) to be maintained: It is possible to select one single SAP system. Also an complete SAP system landscape can be seleted: e.a. DEV, QAS, PRD. If there are dependencies between different SAP systems - e.g. SAP ECC and SAP EP - these can be selected in one step. Figure 54: Maintenance Planner: Tasks 1. In case of multiple SAP Solution Manager systems: Synchronize SAP system information Copyright. All rights reserved. 31

40 4/21/2018 SAP e-book Unit 3: Maintenance Planner 2. Verify the SAP system(s) 3. Optionally define SAP system track 4. Plan software change 5. Schedule deployment LESSON SUMMARY You should now be able to: start the Maintenance Planner for an upgrade and an SAP S/4HANA conversion Copyright. All rights reserved. 32

41 4/21/2018 SAP e-book Unit 3 Lesson 2 Plan a Software Change LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: use the Maintenance Planner for an upgrade and an SAP S/4HANA conversion Plan a Software Change Figure 55: Maintenance Planner: Select Maintenance, Release and SAP Support Package Stack 1. Select target release. 2. Select target Support Package Stack. Copyright. All rights reserved. 33

42 4/21/2018 SAP e-book Unit 3: Maintenance Planner Figure 56: Maintenance Planner, Example Upgrade to SAP ECC 6.08: Select Technical Usage When upgrading to SAP ECC 6.08: there is no need to select from several Technical Usages any longer - because there is only one that covers all former Technical Usages: 'Central Applications'. Figure 57: Maintenance Planner: Select Add-on(s) Optionally: choose Add-ons to be installed during the procedure. Copyright. All rights reserved. 34

43 4/21/2018 SAP e-book Lesson: Plan a Software Change Figure 58: Maintenance Planner: Select OS/DB Dependent Files Choose OS/DB dependent files, e.g. the kernel files. In case a database change is part of the procedure (DMO), the target kernel for the source and target database has to be chosen. Figure 59: Maintenance Planner: Summary and Download 1. Download stack XML for SUM. Copyright. All rights reserved. 35

44 4/21/2018 SAP e-book Unit 3: Maintenance Planner 2. Push selected files to the Download Basket. 3. Download the files from the Download Basket. Figure 60: Provide Stack XML File to SUM 1. Place the stack XML file in the download directory for SUM. 2. Provide the stack XML file - and therewith the download directory - to SUM. Figure 61: Prior to SAP ERP 6.08: Technical Usages, Business Functions and SWCs Copyright. All rights reserved. 36

45 4/21/2018 SAP e-book Lesson: Plan a Software Change With SAP ERP 6.08 there is only one Technical Usage to be selected: 'Central Applications'. With e.g. SAP ERP 6.07 there are several Technical Usages to select from. The Technical Usage 'Central Applications' in SAP ERP 6.08 is not the successor of 'Central Applications' in SAP ERP but rather all Technical Usages from SAP ERP 6.07 put together in one single Technical Usage. To find out which Technical Usage in e.g. SAP ERP 6.07 contains which business functions and which software components, see the attachments of the SAP Note on the slide. 'Selective approach': Evaluate content of SAP enhancement packages in advance (service.sap.com/erp-ehp) and select required functionality Select required SAP Support Package Stack and select all required parts (technical usages) of the SAP enhancement package 'Broad approach'': Exclude all technical usages that reflect topics that you do not use in your system. For the remaining technical usages, briefly verify if these include interesting capabilities for your end-users. To find out which Business Functions are part of a Technical Usage read SAP note there you will find the respective mapping. All Installed SAP enhancement package components have to be updated with every future SAP upgrade. Potentially additional adjustment effort must be considered. Upgrade all relevant software components together with SAP Support Packages Figure 62: Mapping Process (Example) Activate Business Function when required Copyright. All rights reserved. 37

46 4/21/2018 SAP e-book Unit 3: Maintenance Planner LESSON SUMMARY You should now be able to: use the Maintenance Planner for an upgrade and an SAP S/4HANA conversion Copyright. All rights reserved. 38

47 4/21/2018 SAP e-book UNIT 4 SAP S/4 HANA Conversion - Prepare Phase Lesson 1 Pre-Checks 40 Lesson 2 Custom Code Migration 44 Lesson 3 Cross-Application Preparations 52 UNIT OBJECTIVES perform the pre-checks for an SAP S/4HANA conversion perform the checks for a custom code migration perform the technical cross-application preparations Copyright. All rights reserved. 39

48 4/21/2018 SAP e-book Pre-Checks Unit 4 Lesson 1 LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: perform the pre-checks for an SAP S/4HANA conversion Pre-Checks Figure 63: Unit 4 - The Major Technical Steps Copyright. All rights reserved. 40

49 4/21/2018 SAP e-book Lesson: Pre-Checks Figure 64: Prepare Phase Figure 65: Class Consistency Check Call transaction SNOTE and download SAP Note Implement the SAP Note. When implementing you have to confirm, that there are manual activities to be performed. These manual activities are 1) a guidance for program R_S4_PRE_TRANSITION_CHECKS2) a long list of additional SAP Notes to be implemented Call transaction SA38 and execute program R_S4_PRE_TRANSITION_CHECKS.Select 'P_CONS' and 'P_TEST' (the real texts appear after the first run, only) Copyright. All rights reserved. 41

50 4/21/2018 SAP e-book Unit 4: SAP S/4 HANA Conversion - Prepare Phase Figure 66: SAP S/4HANA Pre-Conversion Checks Again, execute program R_S4_PRE_TRANSITION_CHECKS.This time, select 'Pre-Conversion Check Results' and 'Simulation Mode'.You also have to provide the Stack XML file, provided by Maintenance Planner. Figure 67: Accounting Pre-Checks Controlling and General Ledger pre-checks are included in the report R_S4_PRE_TRANSITION_CHECKS but the pre-check program for Asset Accounting (FI-AA) is not included in this program. To run pre-checks for Asset Accounting you need to use the Copyright. All rights reserved. 42

51 4/21/2018 SAP e-book Lesson: Pre-Checks report RASFIN_MIGR_PRECHECK and implement the SAP Notes listed in the collective SAP Note The program RASFIN_MIGR_PRECHECK needs to be run in each of your productive clients LESSON SUMMARY You should now be able to: perform the pre-checks for an SAP S/4HANA conversion Copyright. All rights reserved. 43

52 4/21/2018 SAP e-book Unit 4 Lesson 2 Custom Code Migration LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: perform the checks for a custom code migration Custom Code Migration Figure 68: Code Inspector Checks Call transaction SNOTE and download SAP Note The download takes several minutes. Perform the manual pre-activities for SAP Note :Call transaction SE80 and create the function group SABP_COMP_PROCS_E in the package SABP_COMPILER (the master language is German - DE).Via the context menu, activate the whole function group immediately after the creation. Back in SNOTE, implement SAP Note It requests SAP Note to be downloaded and implemented, also. Important: During note implementation set the checkboxes for the yellow traffic lights related to LSABP_COMP_PROCS_ETOP and SAPLSABP_COMP_PROCS_E (as described in the SAP Note)! Copyright. All rights reserved. 44

53 4/21/2018 SAP e-book Lesson: Custom Code Migration Perform manual post activity for SAP Note :Call transaction SA38 and execute program RS_ABAP_INIT_ANALYSIS -> keep defaults -> execute. This works only once, then the tables are created. Create an RFC connection for the Code Inspector Check Figure 69: Upload Simplification Data Downloading the Simplification Database from the SAP Support Portal by following SAP Note Log on to your SAP system, where you want to perform the Custom Code Checks Upload the Simplification Database Call transaction SYCM. Choose -> Simplification Database -> Import from ZIP File. Select the Simplification Database you have downloaded. This takes about 4 minutes. Still in transaction SYCM, choosesimplification Database -> Show Information.An information pop up is displayed. Still in transaction SYCM, choosesimplification Database -> Show Content.The content of the Simplification Database is displayed. Copyright. All rights reserved. 45

54 4/21/2018 SAP e-book Unit 4: SAP S/4 HANA Conversion - Prepare Phase Figure 70: Performing the Code Inspector Check Performing the Code Inspector Check via transaction SCI In the Custom Code Check system, call SCI To create an object set for the development objects to be analyzed, enter the name of the object set to be created in the 'Name' input field of the 'Object Set' section. Choose the 'Create' buttonon the 'Obj.Collectors' tab, position the cursor in the 'Object collector' input field and choose F4.Select the 'Remote Objects (RFC)' entry and confirm your selection.in the 'Destination' input field, enter the name of the RFC destination, you created before.in the 'Package' input field, enter the relevant packages, for example, choose 'Z*'To trigger creation of the object set, save your input. Navigate back to the Code Inspector: 'Initial Screen'. To analyze the objects contained in the created object set with the checks configured in the generated check variant, you have to create a Code Inspector inspection. To do this, enter the name of the inspection to be created in the 'Name' input field of the 'Inspection' section. In the Object Selection section, enter the name of the 'Object Set' you have just created or choose F4 to search for the relevant one.in the 'Check Variant' section, enter 'S4HANA_READINESS_REMOTE'(if no check variants exist, in the initial screen of SCI choose 'Utilities -> Import Check Variants')To trigger creation of the inspection, save your input. Execute the inspection for immediate execution. Copyright. All rights reserved. 46

55 4/21/2018 SAP e-book Lesson: Custom Code Migration Figure 71: Code Inspector Results: Example Check the results. Figure 72: ABAP Text Cockpit (ATC) Prepare the SAP system to be converted to install the ATC remote infrastructure: apply SAP Notes and , download and upload the Simplification Database Log on to the SAP system to be analyzed. SAP Note is implemented already for the Code Inspector. Copyright. All rights reserved. 47

56 4/21/2018 SAP e-book Unit 4: SAP S/4 HANA Conversion - Prepare Phase Call transaction SNOTE and implement SAP Note :This SAP Note requests SAP Notes , , , Downloading the Simplification Database from the SAP Support Portal by SAP Note Importing the Simplification Database as a ZIP File into the evaluation system. Figure 73: Central Check System with Remote Access The central ATC check system must be at least SAP_BASIS Figure 74: Example for Grouping a Customer's SAP System Landscape Copyright. All rights reserved. 48

57 4/21/2018 SAP e-book Lesson: Custom Code Migration You can use one central ATC check system for several SAP system landscapes (groups) with different releases. Figure 75: Configuring the Central Check System In the SAP system to perform the analysis: perform the configuration for the Remote Code Analysis in ATC Call transaction ATC. Double click 'System Role', choose 'Settings', choose 'Display <-> Change', select 'ATC Checks by Object Providers Only', choose 'Save' Back in the initial screen of ATC: Double click 'Object Providers'. Add a new system group as follows:1. Double-click the item 'System Groups'2. Switch to change mode (table is cross client)3. Choose 'New Entries' 4. Enter an ID and a Description for the system group to be added.5. Save the new entry Add new object providers as follows:1. Double-click the item 'RFC Object Providers'2. Switch to change mode and then choose 'New Entries' 3. Enter an ID, a Description, a System Group, a RFC Connection, and an SAP System.4. Save the new entry Add a correction system as follows:1. Double-click the item 'Correction System'2. Switch to change mode and choose 'New Entries'3. Enter an ID, a RFC Destination, a System Group, and an SAP System.4. Save the new entry Copyright. All rights reserved. 49

58 4/21/2018 SAP e-book Unit 4: SAP S/4 HANA Conversion - Prepare Phase Figure 76: Performing Central Check Runs In the SAP system to perform the analysis: schedule a Run Series for the Remote Code Analysis in ATC Back in the initial screen of ATC: Double click 'Schedule Runs'. Choose 'Create'. Enter a name for the Run Series. As Check Variant enter 'S4HANA_READINESS_REMOTE'. As Object Provider enter the one you created. As Package, for example, enter 'Z*'. Choose 'Save' - do not leave this screen. Mark the Run Series you created and choose 'Schedule' and the RunSeries, you created. Choose 'Execute'. Copyright. All rights reserved. 50

59 4/21/2018 SAP e-book Lesson: Custom Code Migration Figure 77: Evaluating the Results: Example Evaluate the results of the Remote Code Analysis in ATC via transaction ATC Back in the initial screen of ATC: Double click 'Monitor and Control Runs'.Double click the run and check the results. Change to 'Statistic View', also. Evaluate the results of the Remote Code Analysis in ATC via transaction SE80 In SAP system CCC, client 100, call transaction SE80.Choose 'Utilities -> Settings'Select 'ATC Result Browser' and confirm.choose the button 'ATC Result Browser' and check the results. LESSON SUMMARY You should now be able to: perform the checks for a custom code migration Copyright. All rights reserved. 51

60 4/21/2018 SAP e-book Unit 4 Lesson 3 Cross-Application Preparations LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: perform the technical cross-application preparations Cross-Application Preparations Figure 78: Cross-Application Preparations Use the Maintenance Planner to calculate the needed files Remove client and all other unused clients Uninstall SAP Fiori Apps Perform application specific preparations LESSON SUMMARY You should now be able to: perform the technical cross-application preparations Copyright. All rights reserved. 52

61 4/21/2018 SAP e-book UNIT 5 SUM - Manual Preparation Activities Lesson 1 Performing Steps from SAP Notes 54 Lesson 2 Performing Steps from the SUM Guides 58 Lesson 3 Performing Steps from the Application Guide 60 Lesson 4 Performing Steps from the ASU Toolbox 61 UNIT OBJECTIVES detect the steps from SAP notes detect the steps from the SUM guides detect the steps from the application guide detect the steps from the ASU Toolbox Copyright. All rights reserved. 53

62 4/21/2018 SAP e-book Unit 5 Lesson 1 Performing Steps from SAP Notes LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: detect the steps from SAP notes Performing Steps from SAP Notes Figure 79: Unit 5 - The Major Technical Steps Copyright. All rights reserved. 54

63 4/21/2018 SAP e-book Lesson: Performing Steps from SAP Notes Figure 80: SUM 1.0 and SUM 2.0 Figure 81: SoftwareLogisticsToolsetSAPNotes2.ppt support.sap.com/sltoolset Copyright. All rights reserved. 55

64 4/21/2018 SAP e-book Unit 5: SUM - Manual Preparation Activities Figure 82: Software Logistics Toolset: SAP Notes Figure 83: Steps from SAP Notes - Example: SAP Note for SAP S/4HANA Conversion The central SUM SAP Note is dependent of the version of the SUM. It can be found at support.sap.com/sltoolset. The central SUM SAP Note contains the application specific central SAP Note and the database dependent central SAP Note. Copyright. All rights reserved. 56

65 4/21/2018 SAP e-book Lesson: Performing Steps from SAP Notes All three major update/upgrade SAP Notes contains topics that have to be performed before and after the update/upgrade. LESSON SUMMARY You should now be able to: detect the steps from SAP notes Copyright. All rights reserved. 57

66 4/21/2018 SAP e-book Unit 5 Lesson 2 Performing Steps from the SUM Guides LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: detect the steps from the SUM guides Performing Steps from the SUM Guides Figure 84: Software Logistics Toolset: SUM Guides Copyright. All rights reserved. 58

67 4/21/2018 SAP e-book Lesson: Performing Steps from the SUM Guides Figure 85: SUM Guides Figure 86: Steps from the SUM Guides - Example: Major SUM Guide The SUM guides can be found at support.sap.com/sltoolset LESSON SUMMARY You should now be able to: detect the steps from the SUM guides Copyright. All rights reserved. 59

68 4/21/2018 SAP e-book Unit 5 Lesson 3 Performing Steps from the Application Guide LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: detect the steps from the application guide Performing Steps from the Application Guide Figure 87: Steps from the Application Guide The application guide can be found at service.sap.com/instguides LESSON SUMMARY You should now be able to: detect the steps from the application guide Copyright. All rights reserved. 60

69 4/21/2018 SAP e-book Unit 5 Lesson 4 Performing Steps from the ASU Toolbox LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: detect the steps from the ASU Toolbox Performing Steps from the ASU Toolbox Figure 88: Updating the ASU Toolbox: SAP Note Delivered with ST-PI Must be started manually See SAP Note for details Import new ASU content via transaction /n/asu/start or start directly via transaction /n/asu/upgrade Copyright. All rights reserved. 61

70 4/21/2018 SAP e-book Unit 5: SUM - Manual Preparation Activities Figure 89: Steps from the ASU Toolbox Before/after a technical update/upgrade often additional application-specific steps need to be performed ASU collects and summarizes these activities Enables you to recognize the necessary steps and perform them in a controlled manner One tool for all kinds of predefined tasks (reducing the update/upgrade time) Making the update/upgrade more transparent (avoid mistakes) Avoiding problems after the update/upgrade (message reduction) LESSON SUMMARY You should now be able to: detect the steps from the ASU Toolbox Copyright. All rights reserved. 62

71 4/21/2018 SAP e-book UNIT 6 SUM - Prepare Part Lesson 1 Concept of the SUM 64 Lesson 2 Using the SUM 68 Lesson 3 Configuration of the SUM 71 UNIT OBJECTIVES explain the concept of the SUM use the UI of the SUM configure the SUM Copyright. All rights reserved. 63

72 4/21/2018 SAP e-book Unit 6 Lesson 1 Concept of the SUM LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the concept of the SUM Concept of the SUM Figure 90: Unit 6 - The Major Technical Steps Copyright. All rights reserved. 64

73 4/21/2018 SAP e-book Lesson: Concept of the SUM Figure 91: Software Logistics Toolset support.sap.com/sltoolset Figure 92: SUM - Availability The Software Update Manager 1.0 is available since 2011 Copyright. All rights reserved. 65

74 4/21/2018 SAP e-book Unit 6: SUM - Prepare Part As part of the Software Logistics Toolset 1.0 In the MOpz / Maintenance Planner download list Frequently updated (approx. 3 times a year) SUM is delivered with the Software Logistics Toolset. The following list provides a basic overview of the SL Toolset: Software Logistics Toolset (SL Toolset) Product independent delivery channel Up-to-date set of SL tools along fixed intervals Central access via support.sap.com/sltoolset The Software Logistics Toolset approach started with SAP NetWeaver 7.3. Each shipment usually provides improvements on already delivered tools as well as new tools. For further information about the delivered software logistics tools, the supported implementation processes, and SAP application products, see Central Release Note for Software Logistics Toolset How about a project during which a new SP for SUM is delivered: do you have to switch or not? You do not have to use the latest SP of SUM, but it is recommended. And you always have to use the latest patch levels of a SUM SP. Figure 93: SUM - Implementation Scenarios - Examples Copyright. All rights reserved. 66

75 4/21/2018 SAP e-book Lesson: Concept of the SUM Figure 94: SUM Guides and Application Guide The SUM guides can be found at support.sap.com/sltoolset The application specific guide can be found at service.sap.com/instguides LESSON SUMMARY You should now be able to: explain the concept of the SUM Copyright. All rights reserved. 67

76 4/21/2018 SAP e-book Using the SUM Unit 6 Lesson 2 LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: use the UI of the SUM Using the SUM Figure 95: SUM: the UI The new UI is available starting from SUM 1.0 SP12 on demand - and it is standard starting from SUM 1.0 SP13 Copyright. All rights reserved. 68

77 4/21/2018 SAP e-book Lesson: Using the SUM Figure 96: Roadmap Steps and Phases The SUM consists out of 6 Roadmap Steps. Roadmap Steps Extraction, Configuration, and Checks form the preparational part. Roadmap Steps Preprocessing, Execution, and Postprocessing form the actual upgrade part. Roadmap Steps Execution and the first half of Postprocessing have to run during downtime. Figure 97: SUM UI: Input Window (Example) Copyright. All rights reserved. 69

78 4/21/2018 SAP e-book Unit 6: SUM - Prepare Part You can use UPGANA.XML of previous SUM run for more accurate progress bar: just copy the UPGANA.XML into the download directory for SUM. Figure 98: SUM UI: Utilities The sluigui_ext can be reached via the slugui -> More -> Utilities LESSON SUMMARY You should now be able to: use the UI of the SUM Copyright. All rights reserved. 70

79 4/21/2018 SAP e-book Unit 6 Lesson 3 Configuration of the SUM LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: configure the SUM Configuration of the SUM Figure 99: Build up File System When using DMO: the download directory can contain the UT/DT duration XML files of a previous SUM run, in order to optimize the table migration sequence of this SUM run. Copyright. All rights reserved. 71

80 4/21/2018 SAP e-book Unit 6: SUM - Prepare Part Figure 100: Patching and Configuring SAP Host Agent Use command line option saphostexe.exe -upgrade -archive <...> to upgrade SAP Host Agent. Afterwards configure SAP Host Agent to be able to reach SUM by executing STARTUP.BAT confighostagent from the SUM root directory. This creates the files and content shown on the slide. Now SAP Host Agent knows the location of SUM - and can connect to SUM. Figure 101: Main Configuration Copyright. All rights reserved. 72

81 4/21/2018 SAP e-book Lesson: Configuration of the SUM In case only a migration - and no change of software components is desired, set SAPup parameter 'migration_only = 1' in '...SUM\ABAP\bin\SAPup_add.par'. See SUM DMO guide for details. Figure 102: DMO: Table Comparison, Key for R3load In case the SUM procedure includes a database migration (DMO), you have to provide additional information to SUM: You can select, that SUM only does a row count (default) or compare the content via checksum (about 30% longer runtime). R3load needs a key, in any case. This is because the database of the SAP system changes. The 'Migration Repetition Option' is the 'Test cycle'. This means, you can repeat the pure data migration several times - in order to optimize it. This optimization can be done be adopting the number of R3load processes or providing uptime and downtime duration statistics of the previous run to SUM. the 'DMO with System Move' enables you, to change the host during data migration. Copyright. All rights reserved. 73

82 4/21/2018 SAP e-book Unit 6: SUM - Prepare Part Figure 103: Main Configuration SAPup offers several configuration options. Single system: shortest runtime, longest downtime (not available with DMO) Standard: shortest downtime Advanced: the same as Standard, but with additional downtime minimization option Keep archiving on during the whole procedure: no extra database backup at end of procedure necessary (not available with DMO) Switch expert mode on: SUM offers additional configuration options Copyright. All rights reserved. 74

83 4/21/2018 SAP e-book Lesson: Configuration of the SUM Figure 104: Single System, Standard, Advanced Single System: shortest runtime, longest downtime Standard and Advanced: with or without archiving on - not possible when using DMO Shadow system depends on selected options, e.g. Single System, SGEN during SUM run, selected downtime optimization features (NZDM). Figure 105: Resource Consumption of SUM Copyright. All rights reserved. 75

84 4/21/2018 SAP e-book Unit 6: SUM - Prepare Part The number of parallel processes during uptime compete with the daily business of the SAP system: compete with the users and batch jobs. So only a small number of parallel processes should be chosen. The number of parallel processes during downtime should depend on the power of the hardware and the database. Keep in mind that during downtime the SAP system runs with the PAS, only - no AAS. NZDM reduces downtime - but increases the runtime significantly. This feature can only be used when choosing Advanced in main configuration. NZDM is not possible if the SUM procedure contains a DMO. You can select one of the following SGEN execution modes: Release upgrade only: Do not start ABAP load generation during the upgrade Enhancement package installation and SPS update: Do not start ABAP load generation during the update If you plan to apply a high number of relevant changes to your system after the update in the form of a transport or a Support Package, we recommend that you generate the ABAP loads manually after the update. For more information about starting the load generation manually, see Generating Loads [page 195]. Generate ABAP loads on shadow system during uptime With this option, the Software Update Manager uses the maximum number of processes entered below to generate the loads in the shadow system during the uptime. Start asynchronously in post downtime If you select this option, transaction SGEN automatically starts after the downtime during the Postprocessing roadmap step to regenerate the ABAP loads that were invalidated during the downtime. Generate ABAP loads on shadow system during uptime and start asynchronously in post downtime. With this option, the Software Update Manager uses the maximum number of processes entered below to generate the ABAP loads in the shadow system during the uptime. The transaction SGEN automatically starts again after the downtime during the Postprocessing roadmap step to regenerate the ABAP loads that were invalidated during the downtime. Copyright. All rights reserved. 76

85 4/21/2018 SAP e-book Lesson: Configuration of the SUM Figure 106: DMO: Connection to Target Database In case of DMO, the DB client software and connection data is needed. You can optionally provide a new SAP system license, which is needed, because the type of database changes. If you do not provide it here to SUM, you have to apply it manually after the procedure via transaction SLICENSE. Figure 107: Phase CHECK4NOTES_TOOL: Checking for SAP Notes SUM requests SAP notes for itself. They stabilize the SUM run. These SAP notes do not contain the manual preparation activities! Copyright. All rights reserved. 77

86 4/21/2018 SAP e-book Unit 6: SUM - Prepare Part Figure 108: Phase IS_SELECT: Add-on Handling You have to decide about all installed add-ons, that are not part of the Maintenance Planner calculation. Figure 109: Handling of Add-ons/Software Components Depending on the situation in the old and the new release, during an upgrade the following is possible: Copyright. All rights reserved. 78

87 4/21/2018 SAP e-book Lesson: Configuration of the SUM A additional software component is newly installed as standard component: for example the software components from the Extension Set Existing Add-on becomes part of standard delivery: for example in SAP R/3 4.6C IS-U is an Add-on, in SAP ECC 6.0 it is in standard delivery (Enterprise Extension IS-UT) Existing Add-on becomes part of other standard components: for example the Plug-in (PI) is an Add-on in SAP R/3 4.6C, but part of standard components in SAP ECC 6.0 Existing Add-on is upgraded: for example from a release fitting the old SAP R/3 4.6C to a release fitting the new SAP ECC 6.0 Existing Add-on is kept as it is: for example because it fits just as well the old SAP R/3 4.6C as the new SAP ECC 6.0 (option 'keep') Existing Add-on is deleted: because it is not needed any longer (active or passive deletion) Add-on is newly installed: it is possible to install a new Add-on during the upgrade Figure 110: Information about Software Components Check the release strategy of those software components from the list, you are using. Copyright. All rights reserved. 79

88 4/21/2018 SAP e-book Unit 6: SUM - Prepare Part Figure 111: Phase BIND_PATCH: Selecting SAP Support Packages Component Software component Release Target release of this software component Export Level The SAP Support Package level contained in the upgrade media (upgrade DVDs) Minimum Level Required for the given software component combination A SAP Support Package selection that does not meet the minimum package levels leads to an error absolute minimum here is the level calculated by the Maintenance Planner Equivalent Level SAP Support Package level that is equivalent to the level for the source release To avoid loss of data it is strongly recommend to include enough SAP Support Packages to reach the equivalent level An SAP Support Package selection that does not meet the equivalent package levels leads to a warning absolute minimum here is the level calculated by the Maintenance Planner Maximum Level Required for the given software component combination Calculated Level Copyright. All rights reserved. 80

89 4/21/2018 SAP e-book Lesson: Configuration of the SUM The number of SAP Support Packages found in the download directory Is checked for consistence, already Current Level Is initially the level calculated by the Maintenance Planner Will be bound to the update/upgrade Can be increased by additional SAP Support Packages (take over Calculated Level) Figure 112: Binding Transport Requests to Procedure Bind customer transport requests to the procedure to avoid importing them after the procedure: saves downtime. Bind SPDD/SPAU transport requests - from the SUM run of the development system - to the procedure: avoids performing SPDD and SPAU manually. Copyright. All rights reserved. 81

90 4/21/2018 SAP e-book Unit 6: SUM - Prepare Part Figure 113: Binding Transport Requests from Modification Adjustment The start of the procedure involves the transfer of new data to the SAP system. SAP repository objects are imported into the SAP repository and the customer objects are compared. All ABAP dictionary objects that have been modified by the customer must be compared to the new SAP standard during the procedure. To avoid loss of data and table fields that customers may have created, conflicting structures must be merged before the mass activation of ABAP dictionary objects in the procedure If objects need to be adjusted, use the transactions SPDD and SPAU. All modifications made by the customer are then merged with the new SAP object versions to retain data; otherwise, the new SAP version will be activated and data may be lost. The activation takes place on the shadow system - if a shadow system exists. When the procedure is completed, the SAP system is successfully running at the new release level. Customer-developed objects and modifications have been preserved. Copyright. All rights reserved. 82

91 4/21/2018 SAP e-book Lesson: Configuration of the SUM Figure 114: Checks The checks are performed to avoid problems during the procedure. You can choose to save variants from your SAP system - in order to restore them at the end of the procedure. LESSON SUMMARY You should now be able to: configure the SUM Copyright. All rights reserved. 83

92 4/21/2018 SAP e-book UNIT 7 Modification Adjustment Lesson 1 Concept of Modification Adjustment 85 Lesson 2 Performing SPDD 92 Lesson 3 Performing SPAU 93 UNIT OBJECTIVES explain the concept of modification adjustment perform SPDD perform SPAU Copyright. All rights reserved. 84

93 4/21/2018 SAP e-book Unit 7 Lesson 1 Concept of Modification Adjustment LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the concept of modification adjustment Concept of Modification Adjustment Figure 115: Unit 7 - The Major Technical Steps Copyright. All rights reserved. 85

94 4/21/2018 SAP e-book Unit 7: Modification Adjustment Figure 116: Changing the SAP Standard There are different types of methods for adapting an SAP system to the customers needs: Customizing: Involves setting system business parameters using special customizing transactions. Changes are scheduled and organized in advance. Customizing is mandatory before using the SAP system in a live environment. Do not confuse with technical parameters from transaction RZ10/RZ11/RSPFPAR! Customer developments: Creation of customer-specific objects according to naming conventions. Enhancements: Customer changes to SAP repository objects without the need for modifications. Modification: Customer-specific changes to SAP repository objects. When SAP objects are changed, the customer version has to be modified to match the new SAP version. Figure 117: Modification: Yes or No? Copyright. All rights reserved. 86

95 4/21/2018 SAP e-book Lesson: Concept of Modification Adjustment Figure 118: Calculation of Modified Objects to be Adjusted Without modification adjustment, you would lose all modifications you made to objects that conflict with SAP modifications when you update/upgrade the SAP system. The modification adjustment lets you make your modifications to the appropriate new objects in the update/ upgrade. You can identify modifications as repairs to the SAP standard or as imports of SAP objects. Requests in the customer namespace (number range to 9ZZZZZ) modify the SAP objects included in them. All other requests are dealt with as preliminary corrections. The ABAP dictionary objects (tables, data elements, domains, and so on) can be adjusted during productive operation before the activation of the ABAP dictionary. The adjusted objects are collected in a repair that is released to a transport request. You should not release this transport request; instead it must be flagged in transaction SPDD. Towards the end of the update/upgrade, SUM exports this transport request into the transport directory (for example /usr/sap/trans) and then registers it for transport in the file umodauto.lst. Repository objects (programs, screens, and so on) are adjusted toward the end of the update/upgrade, during downtime. At this stage, the import of SAP objects has already been completed. However, the old, modified version is still available in the versions database. As with ABAP dictionary objects, all adjustments are released to a transport request that is noted and then exported and registered by SUM. Copyright. All rights reserved. 87

96 4/21/2018 SAP e-book Unit 7: Modification Adjustment Figure 119: Binding Transport Requests from Modification Adjustment The start of the update/upgrade process involves the transfer of new data to the SAP system. SAP repository objects are imported into the SAP system and the customer objects are compared. All ABAP dictionary objects that have been modified by customers must be compared to the new SAP standard during this update/upgrade process. To avoid loss of data and table fields that customers may have created, conflicting structures must be merged before the mass activation of ABAP dictionary objects in the update/ upgrade process. If objects need to be adjusted, use the transactions SPDD and SPAU. All modifications made by customers are then merged with the new SAP object versions to retain data; otherwise, the new SAP version will be activated and data may be lost. The SAP system is available during the activation phase. The activation takes place on the shadow system - if it exists. When the update/upgrade is completed, the SAP system is successfully running at the new release level. Customer-developed objects and modifications have been preserved. Figure 120: Handling Transport Requests During Adjustment The configuration of the transport routes in the SAP system determines whether changes to objects during modification adjustment are recorded in a local or transportable transport Copyright. All rights reserved. 88

97 4/21/2018 SAP e-book Lesson: Concept of Modification Adjustment request. You cannot and must not change these settings during the update/upgrade. In all cases, the transport request can still be used for automatically transferring modifications to a subsequent system. For this procedure, the transport requests are not released in the normal way, but handled specially. Do not change the configuration of the transport routes in your SAP system group during the update/upgrade. When modification adjustment has been completed, release your tasks. The tasks are the repairs and/or corrections that were automatically assigned to you when the transport request was created.do not release the transport request at this point if you want to use it to automatically transfer the modification adjustments to subsequent SAP systems. During the adjustment of the ABAP dictionary objects, releasing transport requests is locked until the edited objects have been activated. Do not release these transport requests until after the update/upgrade. Releasing the transport requests should be done by SAPup automatically at the end of the update/upgrade. To automatically transfer modifications to a subsequent SAP system when you have completed modification adjustment, use the select for transport function in SPDD or SPAU. If your modifications are recorded in several transport requests, you first have to place all entries in a single request. More than one transport requests cannot be marked for transport. Figure 121: Preparation Aspects Do not attempt to import adjustment transport requests into the system manually during SPDD. This can leads to a loss of data in customer fields. Do not activate any objects during SPDD. Activation is carried out automatically after the adjustment - as part of phase ACT_UPG. If errors are reported when you activate your own developments after executing this phase, you can correct these here, since SAPup stops when errors occur. However, you also have the option of ignoring these errors. If you chose to ignore here, you must activate these objects after the update/upgrade. After you have completed the update/upgrade, you have a maximum of 14 days to execute transaction SPAU without an SSCR key check (SAP Software Change Registration) for the objects that you changed. Copyright. All rights reserved. 89

98 4/21/2018 SAP e-book Unit 7: Modification Adjustment For further information, see the SUM guide and online application help for SPDD and SPAU. Figure 122: Transport Requests: Notes Before the update/upgrade: Check whether the objects you modified are recorded in repairs. To do this, you can use transaction SE95 and search for objects in requests/tasks in transaction SE03. No repairs or customer transports are displayed by the Transport Organizer (SE01/SE09 although you know that objects have been modified in the SAP system. Indicate the objects that have been modified and differ from the SAP standard by including them in a repair and subsequently releasing it. During the adjustment: No differences are found when you compare the second-to-last and third-to-last versions:during the last update/upgrade you did not perform adjustments to retain changes you had made to objects. Indicate that modifications to these objects are no longer needed with the Reset to original function. The last and second-to-last versions were created by user SAP:During the last update/ upgrade you did not perform adjustments to retain changes you had made to objects. Indicate that modifications to these objects are no longer needed with the Reset to original function. Copyright. All rights reserved. 90

99 4/21/2018 SAP e-book Lesson: Concept of Modification Adjustment Figure 123: Modification Adjustment Transactions Transaction SPDD is used to perform modification adjustments to certain ABAP dictionary objects such as domains, data elements, table structures, transparent tables, pooled tables, cluster tables, and table technical settings. Not performing modification adjustment for these objects would cause data loss. After activating the new repository, transaction SPAU is used to perform modification adjustment for objects for which not performing modification adjustment would NOT directly lead to data loss. These objects include: Some ABAP dictionary objects (lock objects, views, and so on) All other repository objects (such as module pools, ABAP programs, function modules, menus, and screens) After running transactions SPDD and SPAU, all modifications are incorporated into the new SAP release The preparation phases check which modified objects need adjustment to enable you to better plan the time required for modification adjustment. LESSON SUMMARY You should now be able to: explain the concept of modification adjustment Copyright. All rights reserved. 91

100 4/21/2018 SAP e-book Unit 7 Lesson 2 Performing SPDD LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: perform SPDD Performing SPDD Figure 124: SPDD SPDD and SPAU have a new design with AS ABAP Objects can be selected according to their category: SAP Notes, with or without Modification Adjustment, deletions, and so on. The available actions depend on the objects and their status. LESSON SUMMARY You should now be able to: perform SPDD Copyright. All rights reserved. 92

101 4/21/2018 SAP e-book Unit 7 Lesson 3 Performing SPAU LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: perform SPAU Performing SPAU Figure 125: SPAU - Handling SAP Notes SPDD and SPAU have a new design with AS ABAP Objects can be selected according to their category: SAP Notes, with or without Modification Adjustment, deletions, and so on. The available actions depend on the objects and their status. To reset all obsolete SAP Notes, choose Reset Obsolete Notes. This starts a batch job, that resets the SAP notes. Copyright. All rights reserved. 93

102 4/21/2018 SAP e-book Unit 7: Modification Adjustment Figure 126: SPAU SPDD and SPAU have a new design with AS ABAP Objects can be selected according to their category: SAP Notes, with or without Modification Adjustment, deletions, and so on. The available actions depend on the objects and their status. Figure 127: SPAU_ENH Copyright. All rights reserved. 94

103 4/21/2018 SAP e-book Lesson: Performing SPAU All enhancements that you have to adjust are shown in transaction SPAU_ENH. In contrast to modifications of source code units, you only have to adjust enhancements if the underlying SAP development objects were deleted or changed in an incompatible way. For the quality assurance and production system, we recommend that instead of adjusting modifications and enhancements manually, you automatically transfer the transport requests exported from the first system: one for the ABAP dictionary objects adjusted using transaction SPDD and one for the repository objects adjusted using transactions SPAU and SPAU_ENH. If you have implemented enhancement framework options of the new Enhancement Framework or implemented a new kernel-based BAdI (also part of the new Enhancement Framework), and the underlying development objects have changed in an incompatible way, you must adjust these objects in transaction SPAU_ENH. The enhancement framework does not support modifying enhancement definitions or enhancement implementations. In some cases you can, however, replace enhancement implementations of a higher layer with your own enhancement implementations. LESSON SUMMARY You should now be able to: perform SPAU Copyright. All rights reserved. 95

104 UNIT 8 SUM - Execution Part Lesson 1 SUM Procedure 97 Lesson 2 Troubleshooting 112 Lesson 3 Database Migration Option (DMO) 120 UNIT OBJECTIVES explain the SUM procedure perform troubleshooting of the SUM procedure explain the Database Migration Option (DMO) Copyright. All rights reserved. 96

105 Unit 8 Lesson 1 SUM Procedure LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the SUM procedure SUM Procedure Copyright. All rights reserved. 97

106 Unit 8: SUM - Execution Part Figure 129: Resource Consumption of SUM The number of parallel processes during uptime compete with the daily business of the SAP system: compete with the users and batch jobs. So only a small number of parallel processes should be chosen. The number of parallel processes during downtime should depend on the power of the hardware and the database. Keep in mind that during downtime the SAP system runs with the PAS, only - no AAS. NZDM reduces downtime - but increases the runtime significantly. This feature can only be used when choosing Advanced in main configuration. NZDM is not possible if the SUM procedure contains a DMO. You can select one of the following SGEN execution modes: Release upgrade only: Enhancement package installation and SPS update: If you plan to apply a high number of relevant changes to your system after the update in the form of a transport or a Support Package, we recommend that you generate the ABAP loads manually after the update. For more information about starting the load generation manually, see Generating Loads [page 195]. With this option, the Software Update Manager uses the maximum number of processes entered below to generate the loads in the shadow system during the uptime. Copyright. All rights reserved. 98

107 Lesson: SUM Procedure Start asynchronously in post downtime If you select this option, transaction SGEN automatically starts after the downtime during the Postprocessing roadmap step to regenerate the ABAP loads that were invalidated during the downtime. Generate ABAP loads on shadow system during uptime and start asynchronously in post downtime. With this option, the Software Update Manager uses the maximum number of processes entered below to generate the ABAP loads in the shadow system during the uptime. The transaction SGEN automatically starts again after the downtime during the Postprocessing roadmap step to regenerate the ABAP loads that were invalidated during the downtime. Figure 130: Shadow Repository and Shadow System: Does it exist? In case there are upgrade media (upgrade DVDs) for the SUM procedure, the shadow repository is build up from these media + the Maintenance Planner download + additional files (files in download directory, transport requests, add-ons, etc.) In case there are no upgrade media (upgrade DVDs) for the SUM procedure, the shadow repository is build as a copy of the old repository + the Maintenance Planner download + additional files (files in download directory, transport requests, add-ons, etc.) Copyright. All rights reserved. 99

108 Unit 8: SUM - Execution Part Figure 131: SUM Execution Part Begins Transport requests, containing objects delivered in this SUM run, have to be released. Nevertheless, all transport requests should be released - in order to have a clean development cut. The option Lock later is possible, only if upgrade media (upgrade DVDs) exist. Starting from Lock now, no development is possible anymore: no SE11, no SE80, no SNOTE, no importing or releasing of transport requests, and so on. Copyright. All rights reserved. 100

109 Lesson: SUM Procedure Figure 132: SUM Execution Part: Request for SPDD The SPDD modification adjustment has to be performed in the shadow system - if exists. SPDD takes place at the beginning of the SUM procedure. Figure 133: SUM Execution Part: Load Generation During Uptime, Before Downtime Copyright. All rights reserved. 101

110 Unit 8: SUM - Execution Part Figure 134: SUM Execution Part: Start of Uptime Database Migration (DMO) A scale out is a landscape reorganization. It distributes the SAP HANA database among several nodes. This is used for SAP BW, only. A scale up is an optimization of the index server. Figure 135: SUM Execution Part: Uptime Database Migration (DMO) Copyright. All rights reserved. 102

111 Lesson: SUM Procedure The uptime migration is the migration of the repository. It can be migrated during uptime, because no changes are done any long - since the repository was locked at the beginning of the SUM procedure (lock now). Several statistics and graphs are available from the SUM UI at More -> Utilities. Figure 136: SUM Execution Part: Request for Downtime The SUM reaches the point of the procedure, where downtime is needed. Now the administrator begins the downtime by locking all users, logging out the logged on users, stopping all batch jobs, stopping all interfaces, and so on. Several additional steps are described in the SUM guides, also. SUM needs a backup of the SUM directory at this point: if there would be a problem during downtime that can not be solved, it should be possible, to not only restore the database to the point of begin downtime - but also the SUM directory. Then you could restart the SUM procedure at begin downtime. Remember: content of the database and content of the SUM directory have to be aligned! Copyright. All rights reserved. 103

112 Unit 8: SUM - Execution Part Figure 137: SUM Execution Part: Downtime Database Migration (DMO) The downtime migration is the migration of the application data, customizing data, and user master records. It can be migrated during downtime, only, because it would be changed continuously during uptime. Several statistics and graphs are available from the SUM UI at More -> Utilities. Figure 138: SUM Execution Part: Importing New Standard Customizing and Data New standard customizing and new data, delivered by SAP, is imported. The runtime depends - besides others - on the number of clients defined in transaction SCC4 (table T000), and the number of languages in the SAP system defined by profile parameter zcsa/ installed_languages. Copyright. All rights reserved. 104

113 Lesson: SUM Procedure Figure 139: SUM Execution Part: Redesigning Data XPRAS stands for execution of PRogrAmS AIM stands for After Import Methods Here the data is redesigned to the table structures and needs of the business processes of the new release, or - in case of an SAP S/4HANA conversion - to the business processes of SAP S/4HANA. The runtime of this phase depends - besides others - on the number of clients, the applications used, the release gap between old and new release, and the size of the tables been redesigned. Especially in case of an SAP S/4HANA conversion, there are many data changes. Copyright. All rights reserved. 105

114 Unit 8: SUM - Execution Part Figure 140: SUM Execution Part: Begin of Postprocessing The downtime is not finished here. Be sure that all users remain locked! If users would log on to the SAP system at this point, they would destroy data - you would have to reset the SUM procedure to begin downtime. Figure 141: SUM Execution Part: Request for SPAU The SPAU modification adjustment takes place at the end of the SUM procedure - but still during downtime. Copyright. All rights reserved. 106

115 Lesson: SUM Procedure Depending on the individual objects, different options are available. Figure 142: SUM Execution Part: Start of Cleanup SUM informs about the end of the technical downtime. At this point the administrator can log on to the SAP system and start with some of the post procedure steps. No end users are allowed to log on now, of course! What is still missing at this point: the technical post procedure steps - and especially the business related steps, that have to be performed before using the SAP system again! Copyright. All rights reserved. 107

116 Unit 8: SUM - Execution Part Figure 143: SUM Execution Part: End of Procedure UPGANA.XML can be used for a subsequent SUM run to optimize the progress bar. MIGRATE_UT_DUR.XML can be used for a subsequent SUM run to optimize the table migration sequence for the uptime migration. MIGRATE_DT_DUR.XML can be used for a subsequent SUM run to optimize the table migration sequence for the downtime migration. Figure 144: Important Phases of SUM Procedure Copyright. All rights reserved. 108

117 Lesson: SUM Procedure RUN_RSDBSCPY clones tables from original to the shadow repository (update only) EU_IMPORT creates the shadow repository from upgrade DVDs (upgrade only) DIFF* copy customer specific objects from the original to the shadow repository (upgrade only) DDIC_UPG imports dictionary objects from the download directory to the shadow repository ACT_UPG activates all ABAP dictionary objects, that are not delivered activated PARDIST_SHD starts distributor SHADOW_IMPORT* imports non-dictionary objects from the download directory to the shadow repository, also copies upgrade and language data from the download directory - only if it is inserted into new tables RUN_RSPTBFIL_ISUTABU, RUN_CRR* for NZDM - if selected RUN_GEN_GENER8 runs SGEN - if selected EU_CLONE_MIG_UT_RUN performs the uptime migration - if the SUM run contains a DMO DOWNCONF_DTTRANS begin of downtime, changes profiles EU_CLONE_MIG_DT_RUN performs the downtime migration - if the SUM run contains a DMO EU_SWITCH switches to new repository PARCONV_UPG conversion of application tables PMVNTAB_UPG move nametab of application tables TABIM* import of upgrade and language data from the download directory XPRAS* executes XPRAs and AIMs Figure 145: Status at Phase ACT_UPG / SPDD (Example: Upgrade from 'old' to 'new' Release) The active SAP system (old release) is up and running with its old application server(s) (PAS and one AAS in this example), its applications data, and the old repository. Copyright. All rights reserved. 109

118 Unit 8: SUM - Execution Part The temporary shadow system (new release) is up and running with the shadow instance, a minimum set of customizing data, and the shadow repository - which is linked to the shadow system. And the end of the procedure the PAS and AAS will be switched to the new release. The application data will be adopted to the needs of the business functions of the new release. The SAP system will be running with the former shadow repository - which is now the regular repository. The shadow instance will be deleted. Figure 146: Operations on Shadow System The shadow instance is used for SPDD, batch monitoring, troubleshooting during shadow phases DDIC user Password copied from productive SAP system Create additional users with transaction SU01 No access to application tables Only basis tables accessible No customizing No production operation No tp import to shadow instance No tp mvntabs, no DDL statements No online activation and conversion Only 'inactive' activation in SE11 No operations in SE14 Access to target release repository during production operation on source release Copyright. All rights reserved. 110

119 Lesson: SUM Procedure LESSON SUMMARY You should now be able to: explain the SUM procedure Copyright. All rights reserved. 111

120 Unit 8 Lesson 2 Troubleshooting LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: perform troubleshooting of the SUM procedure Troubleshooting Figure 147: Overview: Upgrade Components The user interface is described in the SUM guide. The version of most SAP executables can be determined with the option -v.for those tools which connect to the database, a value in the DB library line indicates that the corresponding DB library can be loaded. Copyright. All rights reserved. 112

121 Lesson: Troubleshooting Figure 148: Overview: Types of Phases The SUM contains several hundred phases. Most of the phases fit into one of three described classes. SAPup itself cannot connect to the database. To read or change information in a database table, SAPup needs a tool that can access the database. In each of the three classes, SAPup chooses different tools. Details of these classes are described on the following pages. During the SUM run phases with names like JOB_ or RUN_, SAPup starts a function module in the system using RFC to schedule and start a background job. After the job had finished, the result is evaluated from the log file. Phases with names such as TABIM, TABUIMP, VIEWIMP, PORT_IMP, TOOLIMP and so on are classical import phases. tp starts R3trans, R3trans imports data.phases like DIFFEXP or SHADOW_IMPORT are similar phases, except that R3trans imports into the shadow tables. The EU_IMPORT phases are the bulk import phases during which the new repository is imported into the shadow tables invisible to the production SAP system.most of the data in the repository is not unique to the system, therefore an exchange is more efficient than a import of the delta. In contrast, customizing is unique to each SAP system, and therefore only the delta is imported. Copyright. All rights reserved. 113

122 Unit 8: SUM - Execution Part Figure 149: Overview: Monitoring SUM Activity You can use the above tools to see the SUM activity. If input is required, the SUM will stop. A file, upalert.log, is then written to SUM\abap\tmp. Figure 150: Overview: When the SUM Stops These steps should be processed to find what caused the SUM to stop.the current phase is the last in SAPup.log. Additional logs can be created in transactions SM21 and SM37 for activities inside the SAP system. The database alert file can contain special DB-related errors such as an archiver stuck. Copyright. All rights reserved. 114

123 Lesson: Troubleshooting Figure 151: Job Phases: Control Flow SAPup starts a function module in the SAP system as user DDIC in client 000 (SUBST_START_BATCHJOB). This function schedules a background job for the phase. SAPup regularly checks the status of this job with a new RFC call (SUBST_CHECK_BATCHJOB), until the job has finished. The log file written by the job in SUM\abap\tmp is analyzed and evaluated by SAPup. Figure 152: Job Phases: Log Files The first RFC phase is RFCCHK_INI in PREPARE. Only the RFC logon is performed during this phase, and no background jobs are started (RFCCHK_INI.LOG). Copyright. All rights reserved. 115

124 Unit 8: SUM - Execution Part The check of the background job functionality is made during BATCHCHK phases (for example, BATCHCHK_IMP.LOG). Figure 153: Transport Phases: Control Flow (TABIM) This is also valid for TOOLIMP, DIFFEXP*, and other import phases. During the DIFFEXP* phases, R3trans reads from the source release tables and writes into the target release tables (copy to shadow). SAPup evaluates a direct return code from the tools (finished) and evaluates an indirect return code from the written log files. Figure 154: Transport Phases: Control Flow (ACT, XPRA) Instead of R3trans, a transport background job might also be started for actions such as activation. Copyright. All rights reserved. 116

125 Lesson: Troubleshooting The start of RDDIMPDP works differently from the start of a job during a JOB phase. PARCONV_UPG (parallel conversion) is similar to this, but SAPup starts the transport background jobs (distribution, conversion) itself, and in parallel. After distribution, an additional check is made for lost fields (FDSAVPROT). SAPup then starts tp only for movenametab (PMVNTAB_UPG, execution of DDLs). Activation errors should be resolved or classified as non-critical. Otherwise, there is a chance that data in PARCONV_UPG will be lost. In ACT_UPG, TABIM_UPG and XPRA_AIMMRG, a return code of 8 means that individual objects were not processed successfully. You could repeat the phase at your own risk with repair severe errors. If you do this, then only return codes larger than 8 will stop the phase. Check for lost fields fails in PARCONV_UPG:Verify that this is correct (SAP note). Data might be lost if the phase is repeated with Do not repeat checks. Figure 155: Transport Phases: Log Files The special SAPup log files are.ecos for standard output and.elgs, where errors from other log files are collected. A line in a transport log is transferred if it contains an E in the second column. The log files for tp differ only in the naming from the usual transport log files. Additional PARCONV_UPG log files are: FDSAVPRT.<SID> Check for lost fields PA<date>.<SID> Only nametab activated PD<date>.<SID> Activate and alter table (add field or similar) PL<date>.<SID> Delete table and remove nametab Copyright. All rights reserved. 117

126 Unit 8: SUM - Execution Part Figure 156: Log File Analysis Transaction SE91 can also be used to identify the development class of the message. The development class has a component assigned. Especially for XPRAs, the customer message can be opened directly on this component. Figure 157: R3load Phases: Control Flow (Reading Upgrade Media, DMO) Depending on your upgrade strategy (downtime minimized, resource minimized and substrategies): If the system is productive during EU_IMPORT<n> phases, you can slow down the R3load process so that the performance of the SAP system is not affected. Copyright. All rights reserved. 118

127 Lesson: Troubleshooting If the system is not productive during EU_IMPORT<n>, the SAP system is shut down during EU_IMPORT<n> and several parallel R3load processes are started. The statistics log file contains only the number of imported bytes and the total number of bytes in this data package. The restart of an EU_IMPORT<n> phase with init first removes all previously imported tables and then starts R3load to import all tables again. The restart of an EU_IMPORT<n> phase with repeat just starts R3load to restart from the point where the error occurred. Duplicate keys during the creation of a index are caused by CD read problems. The recommended solution is init of the phase with the DVD copied to disk. Figure 158: Troubleshooting in SUM Guide Figure 159: Recommendations LESSON SUMMARY You should now be able to: perform troubleshooting of the SUM procedure Copyright. All rights reserved. 119

128 Unit 8 Lesson 3 Database Migration Option (DMO) LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the Database Migration Option (DMO) Database Migration Option (DMO) Figure 160: Steps for Classical Migration Scenario :You want to migrate your existing ABAP-based SAP system to SAP HANA DB or SAP ASE DB or MS SQL Server DB. You choose the inplace-migration avoiding landscape changes (SID, host name,...), so you need an update of your SAP system. Classical migration is complex and requires several steps to be considered. Solution: Use the database migration option (DMO) of the Software Update Manager (SUM). Benefits: Migration steps are simplified System update, Unicode conversion, and database migration are combined in one tool Business downtime is reduced. The well known tool SUM is used Copyright. All rights reserved. 120

129 Lesson: Database Migration Option (DMO) Migrating your existing SAP system to the target database, means switching the SAP system to a new database that is running on a new host. Classical migration is the sequence of an SAP software update (using Software Update Manager, SUM) and heterogeneous system copy (using Software Provisioning Manager, SWPM). Figure 161: DMO Simplifies Migration DMO simplifies the migration and is often referred to as the one-step procedure to the target database. Running an SAP system e.g. on a SAP HANA database requires a specific SAP software level. This means that the SAP system has to be updated before the migration takes place. If the SAP system is updated, this may result in requirements for the database host software, especially the database software release. So for some scenarios, the source database software has to be updated before the SAP system is updated. As with the SAP HANA database, non-unicode systems are no longer supported. So the migration procedure may have to cover the Unicode conversion as well. Now with the database migration option (DMO) of the Software Update Manager (SUM), the procedure is simplified. SAP system update and database migration are combined in one tool, in one procedure. If required, the Unicode conversion may be included as well. For some source database types, it is not required to update the source database software for the migration. The figures above illustrate a process where the SAP application server is separate from the database host, which is referred to as a distributed installation. The DMO procedure works independently of the installation type. It can be used for a central installation, in which the database runs on the same host as the SAP application server. DMO Benefits: A combined procedure only needs one maintenance phase (not two) Copyright. All rights reserved. 121

130 Unit 8: SUM - Execution Part Reduces business downtime (TCO) Less regression tests necessary Inplace migration keeps the application server and SAP system-id stable. Low impact on system landscape, as only the database server is new Original database is kept and can be reactivated as a fallback, reduces risk, no restore required More time for testing before cutover Figure 162: Starting the DMO Procedure The following figures show the Primary Application Server only (PAS - formerly known as Central Instance), because the SUM has to be located on the PAS. The system is running, the existing kernel executables that are comprised in an instance (such as work processes) are running on the application server, based on the source release. The database consists of the application data and the repository (such as programs). The repository is abbreviated as PRD REP to emphasize that it is the productive repository, used by the system. The DMO procedure is started from within a browser, sending an HTTP request to the SAP Host Agent, as shown below. The SAP Host Agent requests authorization from the browser, this user is used to start the SUM. As the DMO procedure is only working on AS ABAP based systems (for which the SAPup is the relevant SUM part), the SAPup is started. Copyright. All rights reserved. 122

131 Lesson: Database Migration Option (DMO) Figure 163: Uptime Processing After some basic configuration settings, such as checking the stack.xml, the SAPup will start to create the shadow system. The shadow system consists of a shadow repository and a shadow instance. The shadow repository is created on the source database, in a separate section. It contains the basic tables and some customizing tables, which will already be updated to the target release during uptime. The shadow repository does not influence the PRD repository. The system is still running, and end users may work in the system and use functionality (like a transaction) that may change application data on the database. The shadow instance is running on the PAS host, and is based on the shadow kernel. The shadow kernel is the kernel for the source database, but for the target release. The shadow system requires additional database space, and resources on the application server host. The SAPup will check the status, and ask for additional resources if required. As the shadow repository is being built up on the target release, changes on the PRD repository are no longer allowed, as they would not be considered on the shadow repository. This is why in this phase, the system is running and available for end users (uptime processing), but the development environment is locked. Copyright. All rights reserved. 123

132 Unit 8: SUM - Execution Part Figure 164: Uptime Migration After the shadow repository has been built up completely, it is copied onto the target database, the target database host. The kernel executable R3load is triggered by SAPup to execute the copy of the shadow repository. Hint:: You can see in the figure above that two additional kernels are required for the DMO procedure, both on the new SAP release, but one for the source database, and one for the target database. Figure 165: Downtime Migration Copyright. All rights reserved. 124

133 Lesson: Database Migration Option (DMO) Now the application tables have to be updated to the new release, so the system has to be shutdown to prevent changes on the application tables. The downtime migration is executed, in which the target kernel is used in addition: it is the kernel for the new database (e.g. SAP HANA DB) and for the target release. For the migration of the application data, two R3load processes are running in parallel. The first R3load of the shadow kernel exports the data from the source database, and the second R3load process imports the data into the target database (e.g. SAP HANA). Both R3load processes are running on the PAS host. The DMO configuration includes configuring the number of R3load pair processes to run in parallel. Figure 166: Kernel Switch After the migration of the application data, the shadow instance is removed. The target kernel is now used for the system, and the system is started. The system is still in downtime because it cannot be used by end users. Copyright. All rights reserved. 125

134 Unit 8: SUM - Execution Part Figure 167: Update of Application Tables Now the application tables are updated to the target release. Finally, the DMO procedure is finished. The system is now migrated to the target database, and updated to the target release. Figure 168: DMO Migration Steps in Uptime and Downtime DMO Migration Procedure The migration to SAP HANA DB takes place partially in uptime (UT) processing and partially in downtime (DT) processing of SAPup. Uptime processing: The shadow repository is created on the source database (on target release) and then copied to the target database. Copyright. All rights reserved. 126

135 Lesson: Database Migration Option (DMO) Downtime processing: The application tables are migrated (on source release) to target database, and converted to the target release later (in phase PARCONV_UPG). Figure 169: R3load for Classical Migration with File Mode R3load modes The DMO procedures uses R3load for the migration, like the classical migration based on the Software Provisioning Manager (formerly known as SAPinst) does. For the typical classical migration, the R3load file mode is used. The file mode means that the export files are created, and imported later. Meanwhile, it is also possible to use a parallel export and import for the classical migration. Copyright. All rights reserved. 127

136 Unit 8: SUM - Execution Part Figure 170: R3load for Classical Migration with Socket Mode Another possibility for the classical migration is to use the R3load socket mode, which transfers the files using a socket connection. Figure 171: R3load for DMO Using Pipe Mode With the DMO procedure, both R3load processes are executed on the same host, the PAS host. This allows the use of the R3load pipe mode which transfers the data using the main memory of the host. No files are created, and so no directory has to be prepared to host all export files. Copyright. All rights reserved. 128

137 Lesson: Database Migration Option (DMO) In case the R3load stops, the SAPup will restart the process without the need of manual intervention of a user. The SUM can be configured to use the R3load file mode instead of the pipe mode. In this case, only temporary files are created. As soon as a file has been processed by the R3load import process, the file is deleted. With SUM 1.0 SP13 and higher, the pipe mode is used for all cases. Figure 172: Test Cycle and Benchmarking Options Benchmarking is an option of SAPup. It allows a quick migration test, skipping the update part of DMO. You execute it prior to the DMO run to test the migration rate, and adjust the number of R3loads. Options allow to only export data, or to only migrate part of the database. Benchmarking can't run parallel to DMO, so no SAPup must run when starting benchmarking. You use a different URL (migtool instead of sumabap) Reset specifics for Benchmarking: last step of benchmarking is to already drop the tables from target database. Reset button allows to quickly start with next benchmarking run, reusing the previous parameters (they are set as default). Cleanup button will instead delete the files (like logs) from the SUM folder, allowing a fresh start without previous settings. Adjust the number of R3load processes. During the migration, you should monitor the performance of the PAS host on which the SAPup is executed, and adjust the number of R3load processes to make best usage of the hosts performance. Using table migration durations for next run. SAPup stores the table migration durations in dedicated files. These files can be used for the next DMO run (on the same system) to speed up the migration, because SAPup will then start the migration for the tables with longest runtime first. It is more effective to sort the tables based on their migration duration than on their size. Copyright. All rights reserved. 129

138 Unit 8: SUM - Execution Part LESSON SUMMARY You should now be able to: explain the Database Migration Option (DMO) Copyright. All rights reserved. 130

139 UNIT 9 Downtime Lesson 1 Concept of Downtime 132 Lesson 2 Downtime of the SUM procedure 136 Lesson 3 Incremental Table Conversion (ICNV) 141 Lesson 4 Near-Zero Downtime Maintenance (NZDM) Capabilities of SUM 150 Lesson 5 Downtime-Optimized Data Conversion 156 UNIT OBJECTIVES explain the concept of downtime explain the influencing factors of the downtime of the SUM procedure explain the usage of the Incremental Table Conversion (ICNV) explain the the Near-Zero Downtime Maintenance (NZDM) capabilities of SUM explain the Downtime-Optimized Data Conversion Copyright. All rights reserved. 131

140 Unit 9 Lesson 1 Concept of Downtime LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the concept of downtime Concept of Downtime Figure 173: Unit 9 - The Major Technical Steps Copyright. All rights reserved. 132

141 Lesson: Concept of Downtime Figure 174: What is Business Downtime? Business downtime is the duration, in which an end user cannot use the SAP systems applications in production. Why downtime? The big advantage of SAP's installation technology is, that it allows customers to adapt, extend and modify SAP software, and these extensions will be kept and adjusted to the new release during the upgrade process. Most of the required processing steps can be performed during SAP system uptime. Downtime is necessary, whenever live running transactions have to be replaced by new functionality, and a potential risk of data inconsistency is given, i.e. changing the processing logic, or changing the data model/structure. Copyright. All rights reserved. 133

142 Unit 9: Downtime Figure 175: Planned Downtime - Availability Impact Overall guideline: Avoid frequent downtime with long downtime period. Frequent events need to be minimized regarding the downtime Offline backups need to be avoided Database reorganizations should be a rare occurrence Figure 176: Downtime Costs versus Availability Costs Copyright. All rights reserved. 134

143 Lesson: Concept of Downtime LESSON SUMMARY You should now be able to: explain the concept of downtime Copyright. All rights reserved. 135

144 Unit 9 Lesson 2 Downtime of the SUM procedure LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the influencing factors of the downtime of the SUM procedure Downtime of the SUM procedure Figure 177: Technical Downtime Applications & table formats/contents are not fully compatible all the time during the SAP maintenance procedure. Downtime is needed to resolve the inconsistencies. Begin and end of downtime is not only a 'click' but could be a complex process: for example stopping the production line with all its implications. Both could take hours of time. So this should be called 'ramp down' and 'ramp up' instead of just 'stop' and 'start'. Copyright. All rights reserved. 136

145 Lesson: Downtime of the SUM procedure Figure 178: Production Downtime During SAP S/4HANA Conversion and Upgrade This slide shows are more schematic view of the procedure. Figure 179: Potential to Reduce Downtime The highest potential lays in: Speeding up the delta transports and manual tasks Speeding up business validation test (for example using tools like ecatt) Copyright. All rights reserved. 137

146 Unit 9: Downtime Figure 180: Influencing Factors for Runtime & Downtime Runtime: total duration of the time controlled by SUM including preparation and uptime activities. Runtime and downtime depend on: Hardware and operating system: The whole installation runtime depends on the hardware you use. Hard disk configuration: Input/output throughput, backup speed Database: size of tables, database configuration, parameter tuning Number of modifications: SPDD and activation time Number of data structure conversions: Phase PARCONV_UPG; depends on start/target releases; bigger leaps mean more data conversions Productive applications: More productive applications mean more data conversions Number of clients: Client cascade in phase TABIM_UPG Number of installed languages: more data import A test SUM run on a production system mirror (sandbox system) and thorough analysis of the installation log files can highlight many possibilities for effective manual tuning activities early in the project. Copyright. All rights reserved. 138

147 Lesson: Downtime of the SUM procedure Figure 181: Overview of Factors affecting Runtime & Downtime Figure 182: Decoupling of OS and DB upgrade and SUM Procedure SAP usually also releases 'older' SAP releases on DB and OS versions higher than those used initially This enables customers to run an SAP release on the latest DB and OS versions if required. Thus the maintenance periods of SAP releases can be enlarged. During the upgrade of an SAP / DB / OS combination this feature may be used to split up the system downtime (e.g. into two different weekends): Copyright. All rights reserved. 139

148 Unit 9: Downtime First, do the upgrade of DB and OS to the version required by the target release of SAP system. Second, upgrade SAP system to target release. Figure 183: Single System, Standard, Advanced Single System: shortest runtime, longest downtime Standard and Advanced: with or without archiving on - not possible when using DMO Shadow system depends on selected options, e.g. Single System, SGEN during SUM run, selected downtime optimization features (NZDM). LESSON SUMMARY You should now be able to: explain the influencing factors of the downtime of the SUM procedure Copyright. All rights reserved. 140

149 Unit 9 Lesson 3 Incremental Table Conversion (ICNV) LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the usage of the Incremental Table Conversion (ICNV) Incremental Table Conversion (ICNV) Figure 184: Transaction ICNV: Reduction of Downtime Because most data is converted before the beginning of downtime, downtime can be reduced by several hours. The actual reduction depends on the table size. The dependence of downtime on the database size is also strongly reduced. The downtime can be predicted more accurately. Conversion of large tables during system uptime Conversion process can be stopped and restarted Possible error situations during uptime Copyright. All rights reserved. 141

150 Unit 9: Downtime ICNV especially suited for WORM tables ICNV is fully integrated into the installation Tables to be processed by ICNV can be selected Conversion process is configurable Additional resource usage of DBMS Sufficient number of background work processes Execute ICNV as early as possible Figure 185: Goals of Early ICNV The main goal of the ICNV is to reduce the downtime during an update/upgrade. The procedure should not be too complicated and it should be fully integrated into the update/upgrade process. The conversion process is executed during uptime. The database load is expected to be higher during this process; therefore, it is possible to define exclusion times during which no ICNV processes are running. The administrator should be informed about the estimated end of the process to be able to plan the update/upgrade accurately. Copyright. All rights reserved. 142

151 Lesson: Incremental Table Conversion (ICNV) Figure 186: Overview Here is the sequence of steps during an incremental table conversion: The conversion table candidates are selected. (1) A QCM table with a new structure is created. (2) The table T1 is renamed to QCM1T1. (3) An additional status field is added to QCM1T1. (4) A view on the old table structure is created. The applications access the view from now on. To log these changes the update (5) and the delete (6) trigger is needed The table content is copied (low priority copy) to the shadow table QCMT1. QCMT1 is filled by periodic runs At beginning of downtime, only a few conversions should remain. The downtime due to table conversion is significantly reduced. Copyright. All rights reserved. 143

152 Unit 9: Downtime Figure 187: Need for Logging Mechanism A shadow table named QCMT1 with is created the new structure. The data from the original table QCM1T1 is copied using a background process during uptime to the shadow table QCMT1. QCM1T1 is still accessible by the applications. Therefore the changes during the data transfer must be logged and also be executed on the shadow table. QCM1T1 is modified by creating a flag field. This field indicates if this entry was already copied to the corresponding fields in QCMT1. Programs can perform updates, deletes and inserts on QCM1T1. Update of already converted entry: The x in the flag field is erased by the update trigger. Deletion of already converted entry: The corresponding entry in the new table is directly deleted by the delete trigger. Insert: The flag field for this entry is left empty. Every entry in table QCM1T1 with an empty flag field is copied to QCMT1 Periodically, the copy is repeated for all new rows since the last copy Copyright. All rights reserved. 144

153 Lesson: Incremental Table Conversion (ICNV) Figure 188: Logging Mechanism This could be the situation right after beginning of downtime: Some rows are updated or inserted but not copied yet (empty flag field). There can be a part of the old table which has not been transferred to QCMT1 (empty flag field). The latest insert/update operations and the remaining conversion will be processed during downtime. Inserting rows is possible without an additional load at that point in time, because no insert trigger is used. The update trigger is very efficient, because the additional load just consists of filling the flag field. Delete operations must be executed in both tables and are therefore inefficient. After the incremental conversion starts, dictionary definitions for the relevant tables cannot be changed until the upgrade ends. This affects changing, deleting or adding field definitions. Transaction SE11 is locked for these tables. If you use incremental table conversion, do not start an SAP archiving program for these tables in parallel, since this can lead to performance bottlenecks. Therefore, archive as much as possible before starting the conversion. Incremental conversion requires sufficient background work processes. Ideally, there should be one process for each table to be converted. If you cannot have one process for each table due to a large number of tables, you can still convert the tables since transaction ICNV distributes the tables by itself to the available background processes. However, completing the incremental conversion takes longer, and therefore more time is needed before beginning the upgrade downtime. Copyright. All rights reserved. 145

154 Unit 9: Downtime Figure 189: Aspects of ICNV Because most data is converted before the beginning of downtime, downtime can be reduced by several hours. The actual reduction depends on the table size. The dependence of downtime on the database size is also strongly reduced. The downtime can be predicted more accurately. The conversion process can be stopped and restarted at any time without loss of converted data. Error situations like table space overflow or reaching of maxextends due to the incremental conversion occur during uptime. ICNV is especially suited for large Write Once Read Many (WORM) tables Pay special attention to the resource usage of your database management system to detect bottlenecks early. Incremental conversion requires double the space in the relevant database container (tablespace, dbspace, and so on) for each affected table during the conversion. Due to the continuous data transfer, there are more transactions. Therefore, you should also monitor the space for the rollback information. Incremental conversion eventually requires more background work processes. Make sure, that at beginning of downtime most data is converted. Copyright. All rights reserved. 146

155 Lesson: Incremental Table Conversion (ICNV) Figure 190: Transaction ICNV: Selection of Candidates By calling transaction ICNV, all potential candidates are displayed with their current selection status. You can decide which of the pre-selected tables should be processed by ICNV. Tables can be excluded from being processed by ICNV with 'Do not perform ICNV'. This should be used for tables with a high number of updates and / or deletes, because in this case the ICNV can be inefficient. The delete operations are especially critical. The load on the database is doubled by performing a delete on a table processed by ICNV. This efficiency check must be done manually. There is no tool that excludes hot spot tables automatically! Copyright. All rights reserved. 147

156 Unit 9: Downtime Figure 191: Transaction ICNV: ICNV Assistant ICNV offers several features to configure the incremental conversion process Batch hosts can be specified The number of running batch processes is adjustable Exclusion times for processing can be specified for each table (This enables you to run conversion job at times with relatively low table I/0). The log files of the conversion processes for each table can be accessed See online documentation in ICNV After deciding about all tables, the user can choose to be guided through the necessary steps by an ICNV Assistant. For the upgrade scenario, there are two steps needed to be started manually: Initialization - Extension by flag field - Build of an index on the flag field - Creation of update and delete triggers - Replacement of table by a view and renaming table Start of the data transfer The remaining steps (switch and delete entry in ICNV) are then performed by SUM! Copyright. All rights reserved. 148

157 Lesson: Incremental Table Conversion (ICNV) Figure 192: Transaction ICNV: Initialization and Steps There are useful tools for analysis and trouble shooting FuBa DD_ICNV_REPAIR lets you execute individual transition steps Report RADIMOVE lets you start the data transfer Report RADINCNV lets you move along the transition graph Report RUTNTCHECK (rutntchk in older releases) lets you display (true) runtime objects - Option S for DDIC source, Option N for nametab, Option I for internal ICNV description - A for Active, N for inactive variants There is a step count in table ICNV If you want to change execution plans, debug to the statement table LESSON SUMMARY You should now be able to: explain the usage of the Incremental Table Conversion (ICNV) Copyright. All rights reserved. 149

158 Unit 9 Lesson 4 Near-Zero Downtime Maintenance (NZDM) Capabilities of SUM LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the the Near-Zero Downtime Maintenance (NZDM) capabilities of SUM Near-Zero Downtime Maintenance (NZDM) Capabilities of SUM Figure 193: Example: NZDM for Update to SAP ECC 6.06 Copyright. All rights reserved. 150

159 Lesson: Near-Zero Downtime Maintenance (NZDM) Capabilities of SUM Figure 194: SUM with Near-Zero Downtime Maintenance (NZDM) Capabilities Significant Reduction of Business Downtime compared to current standard update and upgrade tools Significant TCO-Reduction for standard software maintenance activities compared to customer-specific Downtime Minimization Service based on NZDT and other technologies Addresses AS ABAP based SAP systems SUM has been extended with NZDM-Capabilities: Introduction of capabilities for extended downtime optimization Introduction of 'Record & Replay' technique for business transactions Benefit: more relevant phases will be executed while SAP system is still available for users: Selected, long-running after import methods Mass-generation of enhancement objects, generation of enqueue objects Main import (based on record & replay technique) Table structure adjustment incl. conversions (based on record & replay technique) Allows binding of customer transports into uptime part of the procedure Copyright. All rights reserved. 151

160 Unit 9: Downtime Figure 195: NZDM Capabilities for SAP Business Suite Release and Platform Coverage NZDM is not possible for SUM with Database Migration Option (DMO) SUM with S/4HANA Conversion Figure 196: SUM NZDM Approach Step by Step (1) Copyright. All rights reserved. 152

161 Lesson: Near-Zero Downtime Maintenance (NZDM) Capabilities of SUM Figure 197: SUM NZDM Approach Step by Step (2) Figure 198: SUM NZDM Approach Step by Step (3) Copyright. All rights reserved. 153

162 Unit 9: Downtime Figure 199: SUM NZDM Approach Step by Step (4) Replay Recording in productive system usually done with database triggers and logging tables Replay needs to consider complex SAP data formats SAP Migration Workbench (MWB) Application No/only limited changes to data format/content Keep applications and data compatible all the time Keep transactional and repository data separate XPRA/AIM enablement for shadow Copyright. All rights reserved. 154

163 Lesson: Near-Zero Downtime Maintenance (NZDM) Capabilities of SUM Figure 200: NZDM Selection and Monitoring Select NZDM in Roadmap Step 'Configuration' of SUM. No additional configuration is needed. Use transaction CRR_CONTROL in the shadow system to monitor the progress identify error situations restart broken conversions stop and start the conversion change the number of parallel processes LESSON SUMMARY You should now be able to: explain the the Near-Zero Downtime Maintenance (NZDM) capabilities of SUM Copyright. All rights reserved. 155

164 Unit 9 Lesson 5 Downtime-Optimized Data Conversion LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the Downtime-Optimized Data Conversion Downtime-Optimized Data Conversion Figure 201: Downtime-Optimized Data Conversion in a Nutshell Figure 202: Technical Conversion - SUM Standard approach (high level) Copyright. All rights reserved. 156

165 Lesson: Downtime-Optimized Data Conversion Figure 203: 3 Approaches for System Conversion to SAP S/4HANA Figure 204: Downtime Optimized Data Conversion Approach (High Level) Approaches for Downtime Optimized Data Conversion Ø Table conversion: moved to uptime processing - for FIN & Material Ledger (MM-ML) (currently manual action after SUM run) - for Inventory Management (MM-IM) (currently part of downtime processing in SUM) Ø Field conversion: moved to uptime processing - KONV and VBFA tables Ø Speed up mapping of long material number - for source systems with DIMP-LAMA usage Ø Include uptime migration for big application tables In addition, it is possible to select big application tables for migration in uptime (tables which are not affected by the data conversion) - approach of downtime optimized DMO Copyright. All rights reserved. 157

166 Unit 9: Downtime Uptime Figure 205: Downtime-Optimized Data Conversion (Details) - Migrate and Convert Relevant Tables Already in Conditions for Piloting downtime optimized data conversion Ø Downtime-Optimized Data Conversion is available as pilot for the following scenario: - Source product: SAP ECC 6.0 EHP on any-db (not on SAP HANA DB), Unicode - Target product: SAP S/4HANA Finance 1605 or SAP S/4HANA 1610 (FPS1) Ø Customer projects will have to request participation as pilot project, involvement of colleagues from SAP Consulting / Active Global Support is a must Ø Accepted projects benefit from direct development support, and reduced downtime; project will require at least one test run without optimization and one test run with optimization Ø Pilot requests can be posted via incident on component BC-UPG-DTM-TLA, acceptance depends on system landscape, SAP involvement, and capacity of development team Ø See SAP Note for Prerequisites and Restrictions (will be released to customers as soon as registration is possible) Figure 206: Start the Software Update Manager (SUM) - Step 1 for Downtime Optimized Conversion Copyright. All rights reserved. 158

167 Lesson: Downtime-Optimized Data Conversion Figure 207: Shadow Repository is Created - Step 2 for Downtime Optimized Conversion Figure 208: Short Downtime - Step 3 for Downtime Optimized Conversion Copyright. All rights reserved. 159

168 Unit 9: Downtime Figure 209: Shadow Repository is Migrated to SAP HANA - Step 4 for Downtime Optimized Conversion Figure 210: Initial Transfer of Relevant Tables - Step 5 for Downtime Optimized Conversion Copyright. All rights reserved. 160

169 Lesson: Downtime-Optimized Data Conversion Figure 211: Revert: Set Data to Consistent State - Step 6 for Downtime Optimized Conversion Figure 212: Conversion of Transferred Relevant Tables - Step 7 for Downtime Optimized Conversion Copyright. All rights reserved. 161

170 Unit 9: Downtime Figure 213: Delta Migration of Relevant Tables - Step 8 for Downtime Optimized Conversion Figure 214: Remaining Delta Transfer of Relevant Tables - Step 9 for Downtime Optimized Conversion Copyright. All rights reserved. 162

171 Lesson: Downtime-Optimized Data Conversion Figure 215: Conversion of Delta - Step 10 for Downtime Optimized Conversion Figure 216: Migration of Remaining Application Tables - Step 11 for Downtime Optimized Conversion Copyright. All rights reserved. 163

172 Unit 9: Downtime Figure 217: Kernel Switch for PRD Instance - Step 12 for Downtime Optimized Conversion Figure 218: Update of Application Tables to New Release - Step 13 for Downtime Optimized Conversion LESSON SUMMARY You should now be able to: explain the Downtime-Optimized Data Conversion Copyright. All rights reserved. 164

173 UNIT 10 Upgrade of an SAP System Landscape Lesson 1 Upgrade of a 3-System-Landscape 166 Lesson 2 SAP S/4HANA - Landscape Transformation 177 UNIT OBJECTIVES plan the upgrade of a 3-system-landscape explain an SAP S/4HANA landscape transformation and transition to SAP S/4HANA Copyright. All rights reserved. 165

174 Unit 10 Lesson 1 Upgrade of a 3-System-Landscape LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: plan the upgrade of a 3-system-landscape Upgrade of a 3-System-Landscape Figure 219: Unit 10 - The Major Technical Steps Copyright. All rights reserved. 166

175 Lesson: Upgrade of a 3-System-Landscape Figure 220: Key Project Activities - Project Preparation Deliverables at milestone 'project prepared' (SAP Solution Manager project milestone 'Start of Project'): Project plan exists describing the project organization with roles, tasks and responsibilities as well as exact timelines, milestones and deadlines Project resources (internal/external) are nominated and trained Test focus and framework have been defined Upgrade project (sandbox) system is prepared for first test upgrade Copyright. All rights reserved. 167

176 Unit 10: Upgrade of an SAP System Landscape Figure 221: Key Project Activities - Upgrade Blueprint Deliverables at milestones 'blueprint completed' (SAP Solution Manager project milestone 'Scope to Build'): New business processes, process enhancements and replacements of custom developments with the SAP standard are fully specified Adjustment requirements are specified and all performed adjustment activities (SPDD, SPAU, custom developments, customizing, etc) are documented Existing core business processes run in sandbox system without errors, at least for standard regression test scenarios Full documentation of upgrade procedure, issues and problem resolutions exists in central upgrade script Documentation and first analysis of technical downtime performed during sandbox upgrade Copyright. All rights reserved. 168

177 Lesson: Upgrade of a 3-System-Landscape Figure 222: Key Project Activities - Upgrade Realization I Deliverables at milestones 'solution built' (SAP Solution Manager project milestone 'Build to Test'): Development system is upgraded to new release Double Maintenance and code freeze phase for current production environment is in place. All changes or enhancements to business processes, customizing or custom developments are completed and unit tested in the development system Copyright. All rights reserved. 169

178 Unit 10: Upgrade of an SAP System Landscape Figure 223: Key Project Activities - Upgrade Realization II Deliverables at milestones 'Integration, performance and system tests complete' (SAP Solution Manager project milestone 'Test to Deploy'): Development system is upgraded to new release Double Maintenance and code freeze phase for current production environment is in place All changes or enhancements to business processes, customizing or custom developments are completed and unit tested in the development system Copyright. All rights reserved. 170

179 Lesson: Upgrade of a 3-System-Landscape Figure 224: Key Project Activities - Final Preparation for Cutover Deliverables at milestones 'Cutover prepared': Cutover schedule and upgrade script are compiled Final integration and system tests are completed without issues Infrastructure is ready for production system upgrade Figure 225: Key Project Activities - Final Preparation for Cutover Copyright. All rights reserved. 171

180 Unit 10: Upgrade of an SAP System Landscape Deliverables at milestones 'Start of production': Production system is upgraded to new release and released for production operation Deliverables at milestones 'Handover to production' (SAP Solution Manager project milestone 'End of Project'): Standard operating organization resumes responsibility for solution Temporary project enhancements of system landscape are removed Project is finally signed off and closed Figure 226: Recommended Upgrade Project Landscape The upgrade project landscape consists of the following system groups: Productive LandscapeThis is the landscape that shall be upgraded to the new release. The standard landscape is assumed to consist of a development system (DEV), a quality assurance system (QAS) used for testing, and the production system (PRD).If more SAP systems exists in the actual landscape, more upgrades might be necessary. However, depending on the system role and creation process, some of these additional SAP systems could also be created as copies of the three main SAP systems above after the upgrade has been completed. For example, a training system could be created as copy of the upgraded QAS or PRD systems. Temporary Maintenance LandscapeThis landscape is set up during the project to ensure the maintenance of the production system on the old release until it is upgraded. The SAP systems will be removed after the completion of upgrade project. Upgrade Project SystemThis SAP system - sometimes also called upgrade sandbox system - is created in the preparation or upgrade blueprint phase to conduct the first upgrade tests. This SAP system should be available throughout the project. Even after the DEV and QAS system upgrades, it can serve as additional test system, for example, for optimizing the technical downtime. The upgrade project system can also be removed after the completion of the upgrade project. Copyright. All rights reserved. 172

181 Lesson: Upgrade of a 3-System-Landscape Figure 227: Upgrade Project Landscape Reasons for an upgrade project system: Test technical upgrade procedure learn about specifics of your SAP system Test of customer developments in new release understand and plan custom development changes in detail Start modification and custom development adjustment limit efforts by focusing on objects in production reduce double maintenance/code freeze period Perform first tests of core business processes in new release understand and plan integration tests requirements Perform first checks of new functions obtain insight in new release and plan future functional roll-outs Obtain first test results of technical upgrade downtime understand and plan downtime optimization requirements Copyright. All rights reserved. 173

182 Unit 10: Upgrade of an SAP System Landscape Figure 228: Average Cost Structure of SAP ERP Upgrade Projects Figure 229: How to Keep Upgrade Costs Down Copyright. All rights reserved. 174

183 Lesson: Upgrade of a 3-System-Landscape Figure 230: Lessons Learned: Project Management Plan and communicate code freeze time! Figure 231: Lessons Learned: Functional Aspects Copyright. All rights reserved. 175

184 Unit 10: Upgrade of an SAP System Landscape Figure 232: Lessons Learned: Technical Aspects LESSON SUMMARY You should now be able to: plan the upgrade of a 3-system-landscape Copyright. All rights reserved. 176

185 Unit 10 Lesson 2 SAP S/4HANA - Landscape Transformation LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain an SAP S/4HANA landscape transformation and transition to SAP S/4HANA SAP S/4HANA - Landscape Transformation Figure 233: Project Planning Aspects High-Level Example Project Plan Copyright. All rights reserved. 177

186 Unit 10: Upgrade of an SAP System Landscape Figure 234: Transition to SAP S/4HANA - Landscape Transformation Figure 235: High Level Stack Architecture Copyright. All rights reserved. 178

187 Lesson: SAP S/4HANA - Landscape Transformation Figure 236: Table Consolidation Figure 237: Characteristics Copyright. All rights reserved. 179

188 Unit 10: Upgrade of an SAP System Landscape Figure 238: SAP S/4HANA Data Migration / Landscape Transformation Platform Figure 239: LT Based Technology Powers SAP S/4HANA Transition - Addressing Different Use Cases Copyright. All rights reserved. 180

189 Lesson: SAP S/4HANA - Landscape Transformation Figure 240: SAP S/4HANA Landscape Transformation Scenarios - SAP LT Enabled Solutions Figure 241: Possible Consolidation Scenarios Transition to SAP S/4HANA Service offering for a Transition to SAP S/4HANA Planning the Digital Transformation The Planning the Digital Transformation service provides a comprehensive range of planning support, from a multi-year roadmap to the planning of a specific transformation. The needed level of scoping and planning granularity will determine the effort and intensity of this planning phase. The components can be grouped into three clusters: "Strategic Planning", "Application Scoping" and "Transition Planning". Each of these clusters has one or multiple so called "lead component" which would typically be the starting point of deliveries. Prototyping is seen as a specific engagement which starts with a dedicated "Scoping Workshop for Prototyping" as part of planning whereas running the prototype is leveraging components from other services. A detailed description can be found in the Information Sheet of the Service d.dam.sap.com/a/xjono. Platform Design The Platform Design service supports the customer in definition of a more detailed concept for the technical architecture and infrastructure (hardware platform, HA/DR solution, if required: data scaling solution) of a SAP solution e.g. SAP S/4 HANA, SAP BW/4HANA. A Copyright. All rights reserved. 181

190 Unit 10: Upgrade of an SAP System Landscape comprehensive sizing projection and verification is part of the service as well. A detailed description can be found in the Information Sheet of the Service xynxyp. Platform Execution With standardized, repeatable, and efficient processes, the service is designed to assist in converting existing software or carrying out a new implementation of SAP S/4HANA. Based on SAP Activate methodology, it provides high-quality service delivery and predictable results with minimum impact to your business. This service is designed as an engineered service with a fixed scope and fixed price. Build Design The build design service covers all relevant functional design activities during the implementation of SAP S/4HANA on premise. Main purpose is to design and document customer s SAP S/4HANA target solution based on the functional scope identified during planning phase. This service provides the to-be design for SAP S/4HANA implementations based on predefined business scenarios, like SAP Model Company or SAP Best Practices. It enables the customer to experience the simplification and innovation offered by SAP S/ 4HANA across Core Finance, Order to Cash, Procure to Pay, Plan to Product and other lines of business or industries. Service performance can be based on an agile implementation approach as well as on a traditional waterfall implementation method. Key element is an SAP S/4HANA sandbox to be used to define future business processes, independent of running a system conversion or new install scenario. A detailed description can be found in the Information Sheet of the Service Build Execution The Build Execution service helps you implement previously designed processes for the onpremise edition of the SAP S/4 HANA suite. This service is basically relevant for either an enhancement of best-practice processes a new implementation scenario or a system conversion scenario or a configuration of redesigned customer business processes considered relevant with respect to solution capabilities in SAP S/4HANA. Data Migration Design The service helps you during the preparation of your technical transformation or data migration. As a result of data migration design, you will understand the solution alternatives for your landscape transformation requirements and get a valid base to plan your landscape transformation to SAP S/4HANA in the next level of detail. A detailed description can be found in the Information Sheet of the Service Data Migration Execution Data Migration Execution services cover a set of customer use cases for SAP S/4HANA Landscape Transformation and New Implementation scenario. Delivery of this service covers: SAP-led execution of landscape transformations and data migrations Procedure guidance for customer s tasks in the transformation project Expert support, tailored to the customer s situation, to secure the success of the transformation project, such as providing special expertise for performance optimization for LT migration technology Tailored support for going live and for a defined post-go-live period Custom Code Management Copyright. All rights reserved. 182

191 Lesson: SAP S/4HANA - Landscape Transformation The custom code management portfolio offers different service components for a comprehensive analysis and optimization of all phases of the customer's custom code lifecycle. The services are designed to help ensure efficient and effective custom code management. You can formalize the strategy for management of custom code across a product s whole lifecycle, from requirement to retirement, including the remediation and adjustment needed for important transition phases. This strategy should be defined based on your company s own situation, needs, goals, and requirements. The strategy is enhanced with a specific focus on the transition to SAP S/4HANA software. To transition to SAP S/4HANA, you need to analyze custom code in detail because of the simplification and data structure redesign in the digital core of SAP S/4HANA. Efficient custom code management helps ensure the quality and scalability of the business scenarios enabled by the custom code. It also targets the reduction of overall total cost of ownership (TCO) and implementation. It does this by reducing the number of objects or improving the software quality. A detailed description can be found in the Information Sheet of the Service d.dam.sap.com/a/nynoyr. Analytics Design This service provides guidance on how to leverage new analytics capabilities in S/4HANA such as S/4HANA Analytics, implement new strategic SAP products for Analytics and Enterprise Data Warehousing (e.g. SAP Analytics Cloud, SAP Digital Boardroom, SAP BW/ 4HANA, SAP HANA SQL Data Warehouse) and how to integrate them into your existing infrastructure. The following solution components are in focus: SAP S/4HANA Embedded Analytics SAP BW/4HANA and SAP BW SAP Analytics Cloud and Digital Boardroom SAP BusinessObjects BI Suite A detailed description can be found in the Information Sheet of the Service d.dam.sap.com/a/yynoy7. Analytics Execution We recommend four PS services related to this activity group: Implementation of Analytics with SAP S/4HANA Content Orchestration for SAP Digital Boardroom Quick-start service for SAP Digital Boardroom Enablement Service for SAP Analytics Cloud and SAP Digital Boardroom Transition to Operations (T2O) The changes that are related to the implementation of a new software solution affect IT operations no matter what the scope of the project. This service provides you with guidance on the IT support processes, tools, and skills required to safely and efficiently operate your SAP solution in your environment - and contains well-known operations services from SAP - specifically tailored to the operations requirements of the solution. Copyright. All rights reserved. 183

192 Unit 10: Upgrade of an SAP System Landscape A detailed description can be found in the Information Sheet of the Service d.dam.sap.com/a/xyajyn. Safeguarding the Digital Transformation The service Safeguarding the Digital Transformation provides functional and technical validation of core business processes with respect to business and IT requirements, identification and addressing of risks and issues during implementation, upgrade, or migration to new products and solutions like SAP S/4HANA, SAP BW/4HANA or SAP Hybris Commerce. All SAP activities (incl. service positioning, delivery, follow-up, engagement reporting, engagement controlling) during the engagement are orchestrated by an SAP engagement lead (aka Technical Quality Manager) which is a mandatory delivery role within the Safeguarding the Digital Transformation service. With the safeguarding service, SAP technical experts support your project team to save time, reduce risks, and help minimize costs during the implementation. To validate the technical readiness of the organization for productive use of this software, SAP experts perform a comprehensive analysis and optimization of selected core business processes and the technical setup of the solution. During the transition to productive use, the safeguarding service team can involve SAP development experts directly, as needed. A detailed description can be found in the Information Sheet of the Service d.dam.sap.com/a/oynxyy Figure 242: Transition to SAP S/4HANA: Roadmap and Services Copyright. All rights reserved. 184

193 Lesson: SAP S/4HANA - Landscape Transformation Figure 243: Transition to SAP S/4HANA: Roadmap Viewer Figure 244: Transition to SAP S/4HANA: Roadmap Structure Copyright. All rights reserved. 185

194 Unit 10: Upgrade of an SAP System Landscape Figure 245: Transition to SAP S/4HANA: Implementation Road Map LESSON SUMMARY You should now be able to: explain an SAP S/4HANA landscape transformation and transition to SAP S/4HANA Copyright. All rights reserved. 186

195 UNIT 11 Activating Business Functions Lesson 1 Concept of Business Functions 188 Lesson 2 Activation Procedure 193 Lesson 3 Transport of Business Functions 199 Lesson 4 SAP S/4HANA and Business Functions 201 UNIT OBJECTIVES explain the concept of business functions perform the activation procedure transport business functions explain the activation of business functions in the context of SAP S/4HANA Copyright. All rights reserved. 187

196 Unit 11 Lesson 1 Concept of Business Functions LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the concept of business functions Concept of Business Functions Figure 246: Unit 11 - The Major Technical Steps Copyright. All rights reserved. 188

197 Lesson: Concept of Business Functions Figure 247: How to Evaluate a Business Function in your SAP System Landscape (1/2) Figure 248: How to Evaluate a Business Function in your SAP System Landscape (2/2) Copyright. All rights reserved. 189

198 Unit 11: Activating Business Functions Figure 249: SAP System Landscape Aspects Figure 250: Activation and Configuration The switch transaction shows all the Business Functions that can now be activated after the installation of the new software components. In the switch framework transaction you can: View the list of Business Functions available with the latest system setup Access documentation, release notes, test catalogue, and possible dependencies Copyright. All rights reserved. 190

199 Lesson: Concept of Business Functions Install the relevant documentation, refer to SAP note Before the activation you get transparency of all system and UI changes that will take place. Afterwards you can activate the chosen business functions and perform the configuration tasks. By that the new coding becomes effective. All other parts of the system remain stable. Figure 251: New With SAP Enhancement Package 5: Reversible Business Functions Figure 252: Switch Framework: Transaction SFW5 Transport of Switch Settings Switch Framework: Transactions Copyright. All rights reserved. 191

200 Unit 11: Activating Business Functions SFW5 - activate/deactivate Business Functions SFW_BROWSER - investigate, which enhancements are related to the Business Function in question SFW1 - create switches (only customer enhancements) SFW2 - create Business Functions (only customer enhancements) SFW3 - create Business Function Sets for industry solutions (only customer enhancements) LESSON SUMMARY You should now be able to: explain the concept of business functions Copyright. All rights reserved. 192

201 Unit 11 Lesson 2 Activation Procedure LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: perform the activation procedure Activation Procedure Figure 253: Activation Procedure: Preparation Steps Copyright. All rights reserved. 193

202 Unit 11: Activating Business Functions Figure 254: Activation Procedure Runtime of the activation procedure Runtime varies depending on system performance and business function Generally the runtime will be around minutes Recommendation Evaluate activation runtimes on DEV/QAS (ideally in a system with comparable size) Transaction SFW_BROWSER helps you to get an overview about what specific business functions contain Copyright. All rights reserved. 194

203 Lesson: Activation Procedure Figure 255: Business Function Activation Background Information Figure 256: Activation Procedure: Error Handling Copyright. All rights reserved. 195

204 Unit 11: Activating Business Functions Figure 257: Activation Procedure: Post Steps Figure 258: Switch Framework - How Does It Work? The Switch Framework enables optional activation of Business Functions: With the Switch Framework, it is possible to control the activation of SAP ECC objects. Activating a business function triggers switches, which then influence the execution of the code enhancements. These switches ensure that you only see the new functions if you have activated them. All functional changes and the impact of an activated business function are made transparent in advance by the documentation. Bear in mind that once a business function is activated you cannot reverse it. Please note: The activation process starts a job in your SAP system which automatically performs all changes in the system. Copyright. All rights reserved. 196

205 Lesson: Activation Procedure The Switch Framework is a proven concept as it was already used to retrofit industry solutions in SAP ECC 6.0. Figure 259: Test & Go Live: SAP Delivers Test Case Templates Test case templates will be available for each business function that is new to an SAP enhancement package. These templates can be called directly from the switch transaction. The link to the corresponding test case is located right next to each Business Functions. The SAP test case templates help you to plan and perform your acceptance test and train your end users for the selected business functions. By that you are also able to narrow down the test scope because functional changes are documented for each business function. So - where to find test case templates? Firstly before upgrade: in SAP Support Portal. All test cases are available as documents in the SAP enhancement package information center and can be downloaded. Secondly after Upgrade via the switch framework. Test cases are shipped with the SAP enhancement package and are part of the installation (SAP ECC). From there, you will (by drilldown) enter the test workbench. Test cases can be transported to SAP Solution Manager via workbench request. You can either access the Test Case Templates via the SAP Support Portal or transaction SFW5 after the installation. All test cases are available as documents in the Enhancement Package Information Center( Documents (texts) can be downloaded Test cases are shipped with the Update and are part of the installation (SAP ECC) Access the test case from the switch transaction (SFW5) Copyright. All rights reserved. 197

206 Unit 11: Activating Business Functions From there, enter (by drilldown) the test workbench Test cases can be transported to SAP Solution Manager via workbench request Figure 260: SAP Innovation Discovery Tool Figure 261: Important SAP Notes LESSON SUMMARY You should now be able to: perform the activation procedure Copyright. All rights reserved. 198

207 Unit 11 Lesson 3 Transport of Business Functions LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: transport business functions Transport of Business Functions Figure 262: Activation of Business Functions Activation in SAP System Landscape Copyright. All rights reserved. 199

208 Unit 11: Activating Business Functions Figure 263: Transport of Activation & Customizing General Recommendation Figure 264: Transport of Activation & Customizing Possible Alternative LESSON SUMMARY You should now be able to: transport business functions Copyright. All rights reserved. 200

209 Unit 11 Lesson 4 SAP S/4HANA and Business Functions LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the activation of business functions in the context of SAP S/4HANA SAP S/4HANA and Business Functions Figure 265: SAP S/4HANA: Supported Industry Solutions SAP S/4HANA 1610 supports the following industries/solutions: Consumer Products Wholesale Life Sciences Aerospace & Defense (A&D) HighTech Industrial Machinery & Components (IM&C) Copyright. All rights reserved. 201

210 Unit 11: Activating Business Functions Automotive Chemicals Mining Mill Products Utilities Banking Insurance Public Sector Engineering, Construction & Operations (EC&O) Professional Services Telecommunication Sports & Entertainment Transportation & Logistics Contract Accounts Receivable and Payable (FI-CA) Higher Education and Research Defense and Security Oil and Gas Retail Business functions can have the following status: always_on, customer_switchable, and always_off. This results in the following behavior during the conversion: If a business function was switched on in the start release system, but defined as always_off in the SAP S/4HANA target release, then a system conversion is not possible with this release. If a business function was switched off in the start release system, but defined as always_on in the SAP S/4HANA target release, then the business function will be activated during the conversion. If a business function is defined as customer_switchable in Copyright. All rights reserved. 202

211 Lesson: SAP S/4HANA and Business Functions Figure 266: SAP S/4HANA: Always-Off and Always-On Business Functions Business functions can have the following status: always_on, customer_switchable, and always_off. This results in the following behavior during the conversion: If a business function was switched on in the start release system, but defined as always_off in the SAP S/4HANA target release, then a system conversion is not possible with this release. If a business function was switched off in the start release system, but defined as always_on in the SAP S/4HANA target release, then the business function will be activated during the conversion. If a business function is defined as customer_switchable in LESSON SUMMARY You should now be able to: explain the activation of business functions in the context of SAP S/4HANA Copyright. All rights reserved. 203

212 UNIT 12 Unicode Conversion Lesson 1 Concept of Unicode 205 Lesson 2 Performing a Unicode Conversion 211 UNIT OBJECTIVES explain the concept of Unicode explain how to perform a Unicode conversion Copyright. All rights reserved. 204

213 Unit 12 Lesson 1 Concept of Unicode LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the concept of Unicode Concept of Unicode Figure 267: Unit 12 - The Major Technical Steps Copyright. All rights reserved. 205

214 Unit 12: Unicode Conversion Figure 268: Single Code Pages (Non-Unicode) in SAP Systems Without Unicode a SAP system makes use of one or more 'small' codepages. Figure 269: Unicode: Example Languages Supported with Unicode With Unicode a SAP system makes use of only one 'big' codepage. The English language can be used with every code page because of the common character set. Another very common code page is Latin-1: It covers English, Dutch, French, Italian, Spanish, Swedish, and so on. The Japanese code page covers only Japanese and English. Copyright. All rights reserved. 206

215 Lesson: Concept of Unicode Why is English in every code page? Because SAP only uses the ISO-8859 standard, which contains the 7-bit US-ASCII characters. Acting in global business requires support of a global character set! Companies running global business processes like global HR systems Companies offering web services to their customers: global master data containing multiple local language characters! Companies using open standards: J2EE and.net integration Figure 270: Communication: The Ideal Picture The Unicode logo is used here as an placeholder for any of the Unicode encoding formats UTF16LE, UTF-16BE or UTF-8. In case of an Unicode Unicode combination RFC passes all character data without code page conversion or merely with adaption of the endianness. UTF-16 big endian = SAP code page 4102 UTF-16 little endian = SAP code page 4103 Information about the destination is maintained in SM59 special options character width in target system 1 Byte = non-unicode 2 Byte = Unicode Copyright. All rights reserved. 207

216 Unit 12: Unicode Conversion Figure 271: Internationalized Software with Unicode Figure 272: Unicode Code Page Comparison UTF-8 / UTF-16 UTF-8 is a code page being capable of encoding all possible characters defined by Unicode. The encoding is variable-length and uses 8-bit code units. It was designed for backward compatibility with ASCII and to avoid the complications of endianness and byte order marks in the alternative UTF-16 and UTF-32 encodings. UTF-16 was developed from an earlier fixed-width 16-bit encoding, which was known as UCS-2 (for 2-byte Universal Character Set). UTF-16 was created once it became clear that a fixed-width 2-byte encoding (UCS-2) could not encode enough characters to be truly universal. Copyright. All rights reserved. 208

217 Lesson: Concept of Unicode Figure 273: End of Non-Unicode Support As of SAP NetWeaver 7.50 and ECC 6.08, only Unicode will be supported! The end of non-unicode support is described in SAP Note Last Release for NUC - First Release for UC only SAP NetWeaver SAP NetWeaver 7.50 SAP_BASIS SAP_BASIS 750 Kernel 740, 741, and Kernel 745 SAP new system installations are only possible with Unicode (as of SAP ERP 6.0 and SAP NetWeaver 7.0). SAP upgrades are still possible with non-unicode up to SAP ECC An upgrade of a non-unicode system to SAP ECC 6.08 or higher is NOT possible, because SAP ECC 6.08 is based on SAP NetWeaver 7.5, which does not offer any non-unicode kernel anymore. Therefore, you need to perform two projects: First, a Unicode Conversion Second, upgrade to ECC 6.08 Copyright. All rights reserved. 209

218 Unit 12: Unicode Conversion Figure 274: Who is Affected by Unicode? Figure 275: Areas Affected by a Unicode Conversion LESSON SUMMARY You should now be able to: explain the concept of Unicode Copyright. All rights reserved. 210

219 Unit 12 Lesson 2 Performing a Unicode Conversion LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain how to perform a Unicode conversion Performing a Unicode Conversion Figure 276: SAP Unicode Conversion Guides Figure 277: How to Find the Suitable Guides The documents attached to these SAP Notes are updated frequently! Make sure that you always download the latest version before planning and performing the Unicode Conversion. Copyright. All rights reserved. 211

220 Unit 12: Unicode Conversion Figure 278: Main Unicode Conversion Tasks Figure 279: Hardware Options Copyright. All rights reserved. 212

221 Lesson: Performing a Unicode Conversion Figure 280: Project Scope Figure 281: Technical Overview Copyright. All rights reserved. 213

222 Unit 12: Unicode Conversion Figure 282: From Non-Unicode to Unicode with R3load R3load export and import can run in parallel. R3load exports data in so-called packages. Once a package is completely exported on the source system, the R3load on the target system can start to import this package Packages can be located in a shared file system (Windows Share or NFS mount) or can automatically or manually be transferred via ftp or sockets (named pipes). Figure 283: SPUMG Copyright. All rights reserved. 214

223 Lesson: Performing a Unicode Conversion Figure 284: ABAP Unicode Enabling Automatic conversion of character data for communication between Unicode and non- Unicode Figure 285: UCCHECK Configuration Run transaction UCCHECK. Deselect both checkboxes as mentioned above, otherwise you will not see any local ($TMP) objects. Execute UCCHECK. You can enforce a syntax check for all objects in non-unicode systems System profile paramaeter abap/unicode_check = on Copyright. All rights reserved. 215

224 Unit 12: Unicode Conversion Only Unicode-enabled objects (with Unicode flag) are executed Automatically generated programs may need to be regenerated Only set this parameter if all customer coder was enabled via UCCHECK Figure 286: UCCHECK Results UCCHECK shows The program status as a traffic light (Green=OK, Yellow=Warning, Red=Error) The row of the ABAP coding where the error occurred A hint (message) how this error can be solved Figure 287: Software Provisioning Manager (SWPM) The SWPM (inside: SAPinst) is the tool to perform the database export and import, controlling R3load, to do the Unicode conversion. Copyright. All rights reserved. 216

225 Lesson: Performing a Unicode Conversion Figure 288: Unicode Conversion (Without Upgrade) The default conversion method is to export the entire database using R3Load, create a new Unicode database, and then import the database using R3Load again. Conversion from Unicode to non-unicode is not possible MCOD (more than one SAP system in one database): a Unicode SAP system is not compatible with a non-unicode SAP system Unicode SAP systems are not released for Informix. If the source system is a MDMP system perform additional steps that are described SAP Note If you are using HR functionality within SAP R/3/SAP ECC, additional steps are mandatory, which are described in SAP Note Currently SAP does not support an upgrade with simultaneous Unicode conversion. Therefore you must first upgrade a non-unicode system with a basis release less than AS ABAP 6.20 to AS ABAP 6.20 (or higher). Once the non-unicode system uses AS ABAP 6.20 or later you can convert to Unicode. Perform the following steps on the source system: Preparation step in the transaction SPUMG Initialize the worklist (see SAP Note ) Copyright. All rights reserved. 217

226 Unit 12: Unicode Conversion Figure 289: SUM: Database Migration Option (DMO) Restrictions: SAP Notes, SPAM Update, deleted BW Tables In-place migration keeps Application Server and SID stable: Only database server is new Check SAP Note at support.sap.com/sltoolset for possible upgrade paths As of SUM 1.0 SP10, the DMO procedure allows you to include the Unicode conversion (for SCP systems) It is necessary to perform a database migration, e.g., to SAP HANA and SAP ASE - MS SQL Server is available on demand In case the target release contains SAP_BASIS 7.50 and above, you have to perform the Unicode conversion stand alone, before starting SUM! Figure 290: Typical Landscape Conversion Copyright. All rights reserved. 218

227 Lesson: Performing a Unicode Conversion First do the Unicode conversion on a sandbox system, then on development, quality assurance, and production system. Figure 291: Hardware Requirements When using Unicode, characters use up more space in database and main memory. This causes the need of much more hardware to keep the system performance the same as without Unicode. All of the values are average values. Also refer to SAP Note Based on the real scenario that is used in the system to be upgraded those values may be very different from the ones displayed here. For example, measurements in customer system using UTF-8 based databases showed that more than 90% of the databases actually have shrunk about 10%. The main reason for this decrease is that with the Unicode conversion also an implicit database re-organization is performed freeing unused space. Particularly, with large databases such re-organizations are carried out seldom because it impacts the availability and performance of the system. Copyright. All rights reserved. 219

228 Unit 12: Unicode Conversion Figure 292: Additional Database Size Average Sizes: UTF-8 and CESU-8: -13% (for more than 90% of the installations, the database size actually decreased) UTF-16: % SAP HANA systems are in average factor 6.3 smaller than the source systems due to a very high compression on column store tables. Most row store tables will be converted to column store when migrating to SAP HANA. Legend: * Small growth as biggest part of the ASCII-based database is already UC. ** SAP Unicode installations on z/os always use hardware compression, which reduces the growth of data files due to Unicode Conversion. On the other hand, a significant growth of indices was observed (50% and more). *** SAP Unicode installations always use row compression, which is in fact a variable length storage format. As of SQL Server 2008 R2, row compressed UCS-2 has the same storage requirement as UTF-8. Copyright. All rights reserved. 220

229 Lesson: Performing a Unicode Conversion Figure 293: Further Information LESSON SUMMARY You should now be able to: explain how to perform a Unicode conversion Copyright. All rights reserved. 221

230 UNIT 13 SUM - Manual Follow-up Activities Lesson 1 Performing Steps from SAP Notes 223 Lesson 2 Performing Steps from the SUM Guides 226 Lesson 3 Performing Steps from the Application Guide 228 Lesson 4 Performing Steps from the ASU Toolbox 229 UNIT OBJECTIVES identify the steps from SAP notes identify the steps from the SUM guides identify the steps from the application guide identify the steps from the ASU Toolbox Copyright. All rights reserved. 222

231 Unit 13 Lesson 1 Performing Steps from SAP Notes LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: identify the steps from SAP notes Performing Steps from SAP Notes Figure 294: Unit 13 - The Major Technical Steps Copyright. All rights reserved. 223

232 Unit 13: SUM - Manual Follow-up Activities Figure 295: Software Logistics Toolset: SAP Notes Figure 296: Steps from SAP Notes - Example: SAP Note for SAP S/4HANA Conversion The central SUM SAP Note is dependent of the version of the SUM. It can be found at support.sap.com/sltoolset. The central SUM SAP Note contains the application specific central SAP Note and the database dependent central SAP Note. Copyright. All rights reserved. 224

233 Lesson: Performing Steps from SAP Notes All three major update/upgrade SAP Notes contains topics that have to be performed before and after the update/upgrade. LESSON SUMMARY You should now be able to: identify the steps from SAP notes Copyright. All rights reserved. 225

234 Unit 13 Lesson 2 Performing Steps from the SUM Guides LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: identify the steps from the SUM guides Performing Steps from the SUM Guides Figure 297: Software Logistics Toolset: SUM Guides Copyright. All rights reserved. 226

235 Lesson: Performing Steps from the SUM Guides Figure 298: Steps from the SUM Guides - Example: Major SUM Guide Figure 299: Example: SAP Load Generator (SGEN) LESSON SUMMARY You should now be able to: identify the steps from the SUM guides Copyright. All rights reserved. 227

236 Unit 13 Lesson 3 Performing Steps from the Application Guide LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: identify the steps from the application guide Performing Steps from the Application Guide Figure 300: Steps from the Application Guide LESSON SUMMARY You should now be able to: identify the steps from the application guide Copyright. All rights reserved. 228

237 Unit 13 Lesson 4 Performing Steps from the ASU Toolbox LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: identify the steps from the ASU Toolbox Performing Steps from the ASU Toolbox Figure 301: Steps from the ASU Toolbox Delivered with ST-PI Must be started manually See SAP Note LESSON SUMMARY You should now be able to: identify the steps from the ASU Toolbox Copyright. All rights reserved. 229

238 UNIT 14 SAP S/4HANA Conversion - Follow-on Activities Lesson 1 SAP S/4HANA Conversion - Follow-on Activities 231 UNIT OBJECTIVES explain the SAP S/4HANA Conversion follow-on activities Copyright. All rights reserved. 230

239 Unit 14 Lesson 1 SAP S/4HANA Conversion - Follow-on Activities LESSON OVERVIEW LESSON OBJECTIVES After completing this lesson, you will be able to: explain the SAP S/4HANA Conversion follow-on activities SAP S/4HANA Conversion - Follow-on Activities Figure 302: Unit 14 - The Major Technical Steps Copyright. All rights reserved. 231

240 Unit 14: SAP S/4HANA Conversion - Follow-on Activities Figure 303: The Major Technical Steps Figure 304: Realize Phase Copyright. All rights reserved. 232

241 Lesson: SAP S/4HANA Conversion - Follow-on Activities Figure 305: Software Update Manager (SUM) Within the SUM-process the following steps are done in a one-step procedure (for dedicated start releases): Database migration (optional). If your source system is not yet running on the SAP HANA database, use the database migration option (DMO) of the Software Update Manager to migrate your database to SAP HANA during the conversion. Installation of the SAP S/4HANA software. Conversion of your data into the new data structure used by SAP S/4HANA (automated part of the data migration). Figure 306: Follow-On Activties Copyright. All rights reserved. 233