WP4 ACT 1610 Conversion S4HANA WSUM WIN Incl.dmo SP18 V1.10 Migration Do...

10Steps2S4 Conversion Guide for SAP S4HANA 1610 Installed Base Conversion

July 2017 Version 1.10

10Steps2S4 – Conversion Guide for SAP S4HANA 1610

TABLE OF CONTENT Table of Content ........................................................................................................................................... 2 1

Introduction ............................................................................................................................................. 9

1.1 About this Document .............................................................................................................................. 9 1.2 Naming Convention .............................................................................................................................. 10 1.3 Required SAP Notes ............................................................................................................................ 11 1.3.1

Central SUM Note and the SAP Notes for your source database: ............................................. 11

1.4 Required Documentation ..................................................................................................................... 18 1.4.1

SUM Guide ................................................................................................................................. 18

1.4.2

DMO Guide ................................................................................................................................. 18

1.4.3

SAP Note for the DMO ............................................................................................................... 19

1.5 Additionally activities before Upgrade .................................................................................................. 20

2

1.5.1

Deletion of client 066 and 001 .................................................................................................... 20

1.5.2

Kernel update ............................................................................................................................. 20

Planning ............................................................................................................................................... 22

2.1 Basic Concepts .................................................................................................................................... 22 2.1.1

Technical Details of the Upgrade Procedure .............................................................................. 22

2.1.2

DMO Concept ............................................................................................................................. 22

2.1.3

Standard SUM versus SUM with DMO ....................................................................................... 24

2.1.4

Conversion to SAP S/4HANA ..................................................................................................... 24

2.2 Tool Information: Software Update Manager ....................................................................................... 24 2.2.1

SL Common User Interface (SL Common UI) ............................................................................ 24

2.2.2

SL Common UI Elements and Options ....................................................................................... 25

2.2.3

SL Common UI: Getting Support Using the Support File ........................................................... 31

2.2.4

SUM Observer Monitor ............................................................................................................... 31

2.2.5

Communication between Back-End Processes and the SL Common UI ................................... 32

2.2.6

SUM Directory ............................................................................................................................ 33

2.2.7

SUM MailNotifier ......................................................................................................................... 33

2.2.8

Storage of Passwords ................................................................................................................. 34 2


2.3 Preconfiguration Mode Planning .......................................................................................................... 35 2.4 Update Strategy Parameter ................................................................................................................. 37 2.5 Adaption of Parameters ....................................................................................................................... 38 2.5.1

Database Archiving Parameter ................................................................................................... 38

2.5.2

Process and Tool Parameters .................................................................................................... 38

2.5.3

Running the Shadow Instance Remotely ................................................................................... 39

2.5.4

Shadow Instance Parameters..................................................................................................... 39

2.5.5

SGEN Execution Modes ............................................................................................................. 39

2.6 Time Frame for Upgrading the Front-End Software............................................................................. 39 2.7 Database-Specific Aspects .................................................................................................................. 39 2.8 Data Management Planning ................................................................................................................. 40 2.9 Modification and Enhancement Adjustment Planning.......................................................................... 40 2.10

Importing Additional Languages .................................................................................................... 41

2.11

Handling of Customer-Specific Translations and Z Languages in the Upgrade ........................... 41

2.12

Component Levels Contained in the Upgrade Export ................................................................... 41

2.13

Additional Planning Aspects for DMO ........................................................................................... 42

2.13.1 3

Performance Optimization with Migration Duration Files ....................................................... 42

Preparations ......................................................................................................................................... 43

3.1 Determining the Host for the Preparations ........................................................................................... 43 3.2 Checking the Hardware Requirements ................................................................................................ 43 3.3 Checking the Software Requirements ................................................................................................. 43 3.3.1

Checking the Source Release of the SAP System ..................................................................... 43

3.3.2

Checking the Uninstallation of Software Components ............................................................... 43

3.3.3

Meeting the Operating System-Specific Requirements .............................................................. 44

3.3.4

Upgrade of the Operating System and Database System: Overview ........................................ 45

3.3.5

Installing or Updating SAP Host Agent ....................................................................................... 45

3.4 Checking the Structural Requirements for ABAP ................................................................................ 46 3.4.1

Checking the Database-Specific Requirements Before the Update .......................................... 48

3.5 Configuring OS User Authentication .................................................................................................... 49

3


3.6 Setting the Operation Mode for the Update ......................................................................................... 49 3.7 Checking the Consistency of the Host Name ...................................................................................... 51 3.8 Deleting the AUTOSTART Parameter ................................................................................................. 52 3.9 Making Preparations in the Monitoring Area ........................................................................................ 52 3.10

Checking the Requirements for the Modification Adjustment ....................................................... 52

3.11

Filling the Download Directory ....................................................................................................... 52

3.11.1

QCM Table check ................................................................................................................... 54

3.11.2

Additionally Checks ................................................................................................................ 54

3.12

4

Preparing Database Migration Option ........................................................................................... 55

3.12.1

Checking Pool and Cluster Tables ......................................................................................... 55

3.12.2

Oracle: Suppressing Long-Running Phases .......................................................................... 59

3.12.3

Oracle: Checking Database Parameterization ....................................................................... 59

3.12.4

Preparing Target Database SAP HANA ................................................................................. 59

3.12.5

Requesting Migration Key for Target Database ..................................................................... 59

3.12.6

Downloading Latest Database Client Software ...................................................................... 60

3.12.7

Requesting Permanent SAP License ..................................................................................... 62

3.12.8

Changing Schema Name........................................................................................................ 62

3.12.9

Downloading Files from Maintenance Planner ....................................................................... 62

3.12.10

Testing Update and Migration................................................................................................. 62

Running the Software Update Manager ............................................................................................... 63

4.1 Meeting the Requirements for the SUM Directory ............................................................................... 63 4.2 Downloading and Unpacking the Software Update Manager .............................................................. 63 4.3 Starting the Software Update Manager ................................................................................................ 64 4.4 Starting and Restarting the Software Update Manager ....................................................................... 65 4.5 Starting the SUM Observer Monitor ..................................................................................................... 67 4.6 Resetting the Update ........................................................................................................................... 67 4.7 Using Breakpoints During the Update .................................................................................................. 67 4.8 Starting the MailNotifier ........................................................................................................................ 67 4.9 Verifying SAP Archives (Digital Signature Handling) ........................................................................... 67

4


4.10

Importing or Installing Software After Starting the Upgrade .......................................................... 67

4.11

Making Entries for the Specify Authentication Mechanism Roadmap Step .................................. 67

4.12

Making Entries for the Select Target Roadmap Step .................................................................... 68

4.13

Making Entries for the Extraction Roadmap Step ......................................................................... 68

4.13.1

Current Phase: PREP_PRE_CHECK/PROFREAD................................................................ 68

4.13.2

PREP_PRE_CHECK/SPAMCHK_INI .................................................................................... 69

4.13.3

PREP_INPUT/MIG2NDDB_INI............................................................................................... 69

4.14

Configuration ................................................................................................................................. 71

4.14.1

Current Phase: PREP_CONFIGURATION/INITSUBST ........................................................ 71

4.14.2

Current Phase: PREP_CONFIGURATION/INITSUBST ........................................................ 72

4.14.3

PREP_CONFIGURATION/SUBMOD_MIG_INSTCLIENT/HDB_INSTCLIENT ..................... 73

4.14.4

PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/HDB_MIGCONFIG ............................ 74

4.14.5

PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/HDB_PREPARE ................................ 75

4.14.6

PREP_CONFIGURATION/LANG_SELECT ........................................................................... 76

4.14.7

SUM-Phase: PREP_CONFIGURATION/CHECK4NOTES_TOOL ........................................ 77

4.14.8

PREP_SETUP/REQ_ARCHIVING_BLOCKED ...................................................................... 78

4.14.9

PREP_EXTENSION/UPLOAD_REQUEST ............................................................................ 79

4.14.10

PREP_EXTENSION_INST ..................................................................................................... 79

4.14.11

PREP_EXTENSION/UNINSTALL_PREPARE ....................................................................... 80

4.14.12

PREP_EXTENSION/BIND_PATCH ....................................................................................... 80

4.14.13

PREP_EXTENSION/BIND_PATCH ....................................................................................... 82

4.14.14

Current Phase: PREP_INTEGRATION/ADJUSTPRP............................................................ 82

4.14.15

Current Phase: PREP_INSTALL/INITSHD ............................................................................. 83

4.14.16

Backup/Delete no used Profiles.............................................................................................. 83

4.14.17

CURRENT Phase: PREP_INSTALL/SHDINST_CPY ............................................................ 84

4.14.18

Current Phase: PREP_INSTALL/RUN_DBCLONE_INIT ....................................................... 84

4.15 4.15.2 4.16

Checks ........................................................................................................................................... 85 Current Phase: PREP_PREPROC/SAVE_VAR_CHK ........................................................... 85 Preprocessing ................................................................................................................................ 87

5


4.16.1 Current Phase: PREP_GENCHECKS/SUBMOD_MIG_PRPCHECKS/JOB_RDDNTPUR_PREP ............................ 87 4.16.2

Current Phase: MAIN_INIT/REPACHK1 ................................................................................ 88

4.16.3

Current Phase: MAIN_INIT/REPACHK_TRANS .................................................................... 89

4.16.4

CURRENT Phase: MAIN_SHDRUN/ACT_UPG .................................................................... 92

4.16.5

Current Phase: MAIN_SHDIMP/SUBMOD_MIG_UPTIMR_RUN/REQ_SCALEUP_PREREQ 102

4.16.6

Current Phase: MAIN_SHDIMP/REQ_PARTITIONING_MATDOC ..................................... 103

4.16.7

Current Phase: MAIN_DTTRANSSHD/DOWNCONF_DTTRANS ....................................... 103

4.16.8

Current Phase: MAIN_DTTRANSSHD/DOWNCONF_DTTRANS_BCK .............................. 104

4.16.9

HDB Memory ........................................................................................................................ 105

4.16.10

Current Phase: MAIN_DTTRANS/SETSYNC_PREUP_DT_CONFIRM .............................. 105

4.17

Execution ..................................................................................................................................... 106

4.17.2

Current Phase: MAIN_UPTRANS/UPCONF ........................................................................ 107

4.17.3

Current Phase: MAIN_POSTPROC/SETUPGPAR_UPG_POST ........................................ 108

4.18

Postprocessing ............................................................................................................................ 108

4.18.2 Current Phase: MAIN_POSTPROC/SUBMOD_MIG_BI_TASKS_POSTP1/REQPOSTING_BWHANA_NOTE ..... 109 4.18.3

Current Phase: MAIN_POSTPROC/SPAUINFO .................................................................. 110

4.18.4

Current Phase: MAIN_POSTPROC/REQUPFINAL ............................................................. 110

4.18.5

LONGPOST.LOG ................................................................................................................. 111

4.19

Evaluating the Update Process ................................................................................................... 111

4.20

Running the Software Update Manager Repeatedly ................................................................... 113

4.21

Stopping the Software Update Manager ..................................................................................... 113

5

SUM Timeline overview ..................................................................................................................... 114

6

Time SUMMARY ................................................................................................................................ 115

6.1 Time Overall 28 hours / 31 hours ....................................................................................................... 115 6.1.1

Entries / Extraction: 1 hour / 0.5 hour ....................................................................................... 115

6.1.2

Configuration: 6 hours /4 hours ................................................................................................ 115

6.1.3

Checks: 1 hour/ 0.5 hours......................................................................................................... 115

6.1.4

Preprocessing: 13 hours/ 19 hours ........................................................................................... 116 6


6.1.5

Execution: 6 hours / 7 hours ..................................................................................................... 116

6.1.6

Postprocessing: 1 hour / 0.5 hours ........................................................................................... 116

6.2 Disk space/Memory ............................................................................................................................ 116 6.2.1

Disk space K01: ........................................................................................................................ 116

6.2.2

Memory HDB: ........................................................................................................................... 117

6.2.3

Check HDBVIEWS ................................................................................................................... 118

6.3 Follow-Up Activities ............................................................................................................................ 119 6.3.1

Check Installed Software and Product Versions ...................................................................... 119

6.3.2

SAP HANA DB: Backing Up the Database ............................................................................... 120

6.3.3

Performing Follow-Up Activities in the Monitoring Area ........................................................... 120

6.3.4

Performing Follow-Up Activities for the SAP Kernel ................................................................. 120

6.3.5

Reimporting Additional Programs ............................................................................................. 120

6.3.6

Adjusting Repository Objects.................................................................................................... 122

6.3.7

Updating the Where-Used List in the ABAP Workbench .......................................................... 123

6.3.8

Adjusting Customizing Settings ................................................................................................ 123

6.3.9

Adjusting Customer Developments .......................................................................................... 123

6.3.10

Performing Follow-Up Activities for SAP Solution Manager ................................................. 124

6.3.11

Secure Single Sign-On with Microsoft LAN Manager SSP .................................................. 124

6.3.12

Adjusting the User and Role Administration ......................................................................... 124

6.3.13

Rescheduling Background Jobs ........................................................................................... 124

6.3.14

Generating Loads ................................................................................................................. 125

6.3.15

Checking for Unused Indexes............................................................................................... 127

6.3.16

Importing Support Packages After the Upgrade ................................................................... 129

6.3.17

Transport Management System: Distributing the Configuration ........................................... 129

6.3.18

DMO-related Follow-up Activities ......................................................................................... 129

6.3.19

Configuring Domain Controller for Transport Management System .................................... 129

6.3.20 Application specific issues to be considered within the follow-on phase of a system conversion ........................................................................................................................................ 129 6.3.21

ST22 dumps after conversion ............................................................................................... 130

6.3.22

VCH_MASS_MAINTENANCE .............................................................................................. 130 7


7

Tables and Figures............................................................................................................................. 131

8


Conversion to SAP S/4HANA using SUM: ABAP Systems on Windows (Guide)

Figure 1: Software Update Manager 1.0 SP18 incl. Database Migration Option Guide

1 Introduction 1.1 About this Document This tool guide deals with the conversion of SAP systems to SAP S/4HANA using the Software Update Manager (SUM) 1.0 SP18. Furthermore it describes specifics, when you want to migrate a source database, which is not SAP HANA, to SAP HANA database in the course of the conversion using the database migration option of the Software Update Manager. Purpose The Software Update Manager (SUM) is part of the Software Logistics Toolset (SLToolset) and a multipurpose tool that supports various processes, such as performing a release upgrade, installing enhancement packages, applying Support Package Stacks, installing add-ons, or updating single components. For clarity and readability, the term “update” is used in this document for all supported processes. Software Update Manager 1.0 SP18 supports among others the following system maintenance processes:    

Converting SAP systems to S/4HANA Upgrading or Updating to SAP Business Suite 7 Innovation 2016 based on SAP NetWeaver 7.5 Upgrading or Updating to SAP NetWeaver 7.5 Applying Support Packages Stacks to systems based on SAP NetWeaver 7.5

If your source database is another database than SAP HANA, perform in addition a migration to SAP HANA database, since SAP S/4HANA runs on this database only. To smooth the way to the SAP HANA target database, SAP introduced a one-step procedure that combines the system update and the database migration. This is provided with the Database Migration Option (DMO) feature of the SUM tool. The main benefits of DMO are:    

Simplified migration steps System update and database migration combined in one tool Reduced business downtime The source database remains consistent, thus a fast fallback is possible

Note This tool guide contains mainly parts of the SUM guide and the DMO guide, which can be used in particular for the conversion scenario. They have a special focus on ABAP technology, target release SAP NetWeaver 7.5 (or higher), and target database SAP HANA.

9


1.2 Naming Convention Update In this document, the term “update” is used as a collective term for all the software logistics processes that you can perform using the Software Update Manager (such as performing release upgrades, installing enhancement packages, or updating a system with support package stacks).

Colors explanation: Only Information no activity Activities still open All done no activity

10


1.3 Required SAP Notes This section informs you about the SAP Notes in addition to this guide, which are important for the conversion.

1.3.1 Central SUM Note and the SAP Notes for your source database:

SAP Note Number

Description

1.3.1.1 2277058_Rev.11

Central Note - Software Update Manager 1.0 SP18

-------------------------< D023536 NOV/11/16 >------------------------Data loss for Change Documents when using SUM in Single System mode Do not use SUM in preconfiguration mode Single System when you want perform an upgrade or a update from SAP_BASIS lower than 750 to SAP_BASIS 750 or higher, and the table TCDOB is a transparent table in the start release. This combination may lead to data loss for change documents. The issue will not occur, if either the table TCDOB is not transparent in the start release, or you use one of the preconfiguration modes Standard or Advanced.

Figure 2: SE14 Result of table TCD0B

Figure 3: Content of table TCD0B

11


-------------------------< I030847 JUN/18/15 >------------------------Install or Update SAP Host Agent to the minimum supported version Make sure that at least the relevant SAP Host Agent minimum version is present in your system. Regardless of your stack type, use at least the following versions: SAP Host Agent 7.20 version 203 (or higher), or SAP Host Agent 7.21 version 3 (or higher). https://help.sap.com/saphelp_nw74/helpdata/de/39/a1f623bae74a2784f88282c8652070/content.htm See section 3.3.5 ----------------------< I027789 NOV/21/2016 >-------------------------

The OSS Note 2311738 says that it’s possible to ignore the error and after migration it’s need to execute technical steps: You can ignore these findings. Most findings can be rectified after the upgrade by generating the views (transaction HDBVIEWS -> Generate All) and then updating the data in DB02. The tables TTFIN_ARPOS_DSOV, TTFIN_ARPOS_TERMS, and TTFIN_ARPOS_TERMV and the view FIN_ARPOS_NETDT might also appear in DB02 again after a successful generation. This is not a problem and can be ignored. -------------------------------------------------------------------------------------------------------------------------------------1.3.1.2 2277083_Rev.10

Add. info. on converting to SAP S/4HANA using SUM SP18

-----------------------< D028310 NOV/18/15 >-------------------------Procure latest SAP Notes for pre-checks SAP provides a series of pre-checks to help identify the steps, which you need to take to ensure that your system is compatible with S/4HANA. Among others, one of the activities to perform the prechecks is the implementation of SAP Note 2182725 and all the related SAP Notes attached to it. Make sure that you have always the latest version of this SAP Note, and check regularly for updates of all attached SAP Notes! For more information, see chapter 4.2 "Pre-Checks" of the Conversion Guide for SAP S/4HANA 1511, which is available on the Help Portal at: http://help.sap.com/s4hana_op_1511 -> Product Documentation. - 2187732 7 (S4TC EA-GLTRADE Master Check for S/4 System Conversion Checks) - 2186288 3 (S4TC SRMSMC Master Check for S/4 System Conversion Checks) - 2185960 68 (S4TC SAP_APPL Master Check for S/4 System Conversion Checks)

12


Figure 4: Additional notes of note 2185960

- 2194368 10 (S4TC EHSM Master Check for S/4 System Conversion Checks) - 2198401 14 (S4TC EA-APPL Master Check for S/4 System Conversion Checks) - 2194272 39 (S4TC ECC-DIMP Master Check for S/4 System Conversion Checks)

2326776 S4TC Pre-Transition Checks for 1 LAMA and Material Versioning -14-

Software Component ECC-DIMP is present

2

2326822 S4TC Pre-Transition Checks for Supplier Workplace -12-

Business function DIMP_SDUD is activated

3

2326788 S4TC Pre-Transition Checks for Equipment and Tools Management -11-

Business function DIMP_SDUD is activated

4

2326952 S4TC Pre-Transition Checks for Parts Interchangeability -11-

Business function IS_AD_MPN is activated

13


5

2334008 S4TC Pre-Transition Checks for MPN -21-

Business function IS_AD_MPN is activated

Checks for transition of ERP system Business functions IS_AD_MPN or 6 2305404 with ECC-DIMP(DIMP-LAMA MGV_LAMA is activated. activated) to S/4HANA. S4TC: PreCheck for application component LO-VC

Business functions IS_AD_MPN or MGV_LAMA is activated.

S4TC Pre-Transition Checks for 8 2328727 Home Building Solution

Business function DIMP_SDUD is activated and if note 2328727 is not automatically downloaded

7 2356196

2381185 9

-1-

S4TC-Pre-Transition Checks for Bill of Services

Business function ECO_BOS is activated

- 2198974 7 (S4TC FINBASIS Master Check for S/4 System Conversion Checks) - 2237932 (S4TC Ariba BS Add-On Master Check for S/4 System Conv. Checks) - 2248512 (S4TC PICM Master Check for S/4 System Conversion Checks) - 2243963 (S4TC CPD Master Check for S/4 System Conversion Checks) - 2216943 (S4TC SRM_SERVER Master Check for S/4 System Conversion Checks) - 2293565 (S4TC CODERINT Master Check for S/4 System Conversion Checks) - 2358407 2 (S4TC EA-FINSERV Master Check for S/4 System Conversion Checks) - 2326521 9 (S4TC EA-RETAIL Master Check for S/4 System Conversion Checks) - 2314696 (S4TC CEEISUT Master Check for S/4 System Conversion Checks) - 2335793 4 (S4TC IS-CWM Master Check for SAP S/4 System Conversion Checks) - 2202282 9 (S4TC IS-UT Master Check for S/4 System Conversion Checks) - 2331943 5 (S4TC IS-OIL Master Check for S/4 System Conversion Checks) - 2321885 (S4TC CPRXRPM Master Check for S/4 System Conversion Checks) - 2379272 3 (S4TC MDG_APPL Master Check for S/4 System Conversion Checks)

Programm R_S4_PRE_TRANSITION_CHECKS 14


Figure 5: R_S4_PRE_TRANSITION_CHECKS to stack XML

Z:\CONV\MP_Stack_1000106540_2034_.xml

Figure 6: S4_PRE_TRANSITION_CHECKS Result overall

Figure 7: S4_PRE_TRANSITION_CHECKS Check Result ERROR “10”

15


Figure 8: S4_PRE_TRANSITION_CHECKS Check Result WARNING "60"

 Second run

Figure 9: S4_PRE_TRANSITION_CHECKS Check Result WARNING "5"

---------------------------------------------------------------------------------------------------------------------------

16


1.3.1.3 2350408_Rev.2

Add. info. on the update/upgrade to SAP NetWeaver 7.51

--------------------< D023536 SEP/10/2015 >----------------------Update to SAP NW AS for ABAP 7.51 Innovation PKG and higher: Minimum database version All updates to this release and SPS level require a certain minimum database version. To check if your database version is supported, go to SAP Note 2329005, and update it to a supported version if required. Be aware that the minimal DB-version has to be applied before the upgrade to NW AS ABAP 7.51 INNOVATION PKG can take place.        

ASE 16.0 SP02 PL4 HF1 (16.0.02.04 HF1) DB2 for i 7.2 DB2 for LUW Version 10.5 FP6SAP = 10.05.0006 DB2 for z/OS 11 HANA (HDB) 1.0 Rev 121.00.14664660, HANA Client 1.00.120.042.1474657934 MaxDB 7.9.08.40 (Still under evaluation. See SAP note: 1444241) Oracle 12.1.0.2.2 SQL Server 2012/2014/2016 (min. versions see SAP note 62988)

-------------------------------------------------------------------------------------------------------------------------------------1.3.1.4 2313632_Rev.1 MSS: Additional Information – Software Update Manager 1.0 SP18 05/Oct/16 ABAP/ABAP+JAVA Performance problem in ACT_UPG and MAIN_SHDRUN/SUBMOD_PREP_DDIC_740/JOB_RUTREMINDX Please read SAP Note 1933739 on how to prevent long runtimes in phase ACT_UPG and MAIN_SHDRUN/SUBMOD_PREP_DDIC_740/JOB_RUTREMINDX ----------------------------------------------------------------------------------------------------------------------------- ---------

17


1.4 Required Documentation

Table 1: Software Logistics Toolset

1.4.1 SUM Guide

SP18 Version 1.0

Figure 10: Updating SAP ABAP Systems on Windows: Microsoft SQL

1.4.2 DMO Guide

SP18 Version 1.1

Figure 11: Database Migration Option: Target Database SAP HANA

18


1.4.3 SAP Note for the DMO

SAP Note Number

Description

1.4.3.1 2277055_Rev.17

Database migration option (DMO) of SUM 1.0 SP18

--------------------< D029945 29/FEB/2016 >-----------------------------Running DMO on AAS not supported if no ASCS instance exists In general, SUM and SUM with DMO may be executed not only on the Primary Application Server (PAS), but also on an Additional Application Server (AAS). However, running SUM with DMO on an AAS is only supported if your system has a separate ASCS instance. It is not supported if the central services are part of the DVEBMGS instance.

Figure 12: New ASCS instance

------------------------------------------------------------------------------------------------------------------------------------Note For additional SAP Notes that are relevant for DMO, see the section Preparation of the DMO Guide. Note 1000009_Rev.56 - ASU Toolbox 2008 ----------------------Recommendation See also the PDF documents, which are attached to the DMO Note and the central SUM Note, for a graphical representation of the supported update and upgrade paths. Upgrade Guide complete

Figure 13: Upgrade and Update Guide SAP Netweaver 7.4 ABAP

19


1.5 Additionally activities before Upgrade 1.5.1 Deletion of client 066 and 001 1.5.1.1 1749142 - How to remove unused clients including client 001 and 066

Figure 14: SCC4 Client view

1.5.2 Kernel update

Figure 15: Kernel update before

Figure 16: Kernel update after

SICK problems

20


Figure 17: Standalone enqueue server and ENQ work processes

Note 2146940 - Desupport of Enqueue Work Process  "enque/process_location = REMOTESA" o Added automatically to Default profile o Standard kernel “Optimize”  "rdisp/wp_no_enq = 0" o Deleted o Standard Kernel “0”  SGEN 2270689 - RFC Extractor for performing static checks 2216528 Pre-upgrade check for storage location migration report

21


Planning

2

This part of the document contains information about planning your SAP system update. Before you begin the actual update, you must first plan it carefully. This includes requesting all the SAP Notes you need. Careful planning is a prerequisite for a successful update. The following information helps you plan your update so that downtime is reduced to a minimum, and the update runs as efficiently as possible.

2.1 Basic Concepts

2.1.1 Technical Details of the Upgrade Procedure Note This section is only relevant if you perform a release upgrade.

Figure 18: Process Flow of a System Switch Upgrade

2.1.2 DMO Concept This section describes the idea behind the database migration option of the Software Update Manager. The DMO feature helps you avoiding landscape changes (SID, host name) and allows the combination of all relevant steps for the in-place migration to the target database (Unicode Conversion, Update, and Migration) in one tool. Assuming that you run your SAP system on anyDB, and you want to update the SAP system and to migrate the anyDB to the wanted target database, several steps such as a    

Dual-stack split Database update of anyDB Update of your SAP software Database migration to target database

22


The processing sequence is based on the shadow system functionality of SUM:

1. The SUM creates the shadow repository on the traditional database until downtime phase, while in parallel the target database is being set up (such as client, schema). 2. The shadow repository is copied to the target database. Then the downtime starts. 3. After the migration of the application data (including data conversion), the update is finalized and the SAP system runs on the target database. The Source database continues to run and it is not modified. It remains as a fallback for the Reset Option throughout the complete DMO procedure. After the successful DMO procedure however, it cannot be used anymore as a productive database for an SAP system in parallel with the target database. It remains as a fallback for the reset procedure throughout the complete procedure.

Figure 19: Different phases of the DMO

23


2.1.3 Standard SUM versus SUM with DMO Take into account the following main differences to the standard SUM procedure, that is, the system update without combined database migration in a one-step procedure:  Different prerequisites Supported are all database versions listed in the Product Availability Matrix (PAM) of the source release and all operating system versions listed in the PAM of the target release.

2.1.4 Conversion to SAP S/4HANA The sections deals with the basic information about the conversion to SAP S/4HANA SAP S/4HANA is the next-generation business suite. It is a new product fully built on the most advanced in-memory platform today – SAP HANA – and modern design principles with the SAP Fiori user experience (UX) and a new role-based user experience concept. SAP S/4HANA delivers massive simplifications (data model, user experience, decision making, business processes, and models) and innovations (Internet of Things, Big Data, business networks, and mobile-first) to help businesses run simple in the digital economy. SAP S/4HANA offers a business scope that is similar in terms of coverage, functionality, industries, and languages as the SAP Business Suite 7. Within this scope, SAP S/4HANA also includes the transformational simplifications delivered with SAP S/4HANA Finance (SAP Accounting powered by SAP HANA) as well as a planned integration with SuccessFactors Employee Central and Ariba Network. The S/4HANA system conversion is based on the switch upgrade procedure within Software Update Manager (SUM), optionally with database migration option (DMO) if the source system is not yet on SAP HANA database.

2.2 Tool Information: Software Update Manager The following sections provide you with important information about the update program Software Update Manager (SUM):

2.2.1 SL Common User Interface (SL Common UI) The SL Common User Interface (SL Common UI) is used when you perform an update with SUM. The UI provides all functions for monitoring and navigating through the roadmap steps of the update procedure. The complete procedure consists of several roadmap steps that contain modules, which in turn consist of the individual steps. As it is based on the SAP UI Development Toolkit for HTML5 (SAPUI5), which is a clientside rendering library, the SL Common UI does not require any Java components. It provides a rich set of standard and extension controls, a lightweight programming language, and a high level of customization. The benefits of SAPUI5, and thus of the SL Common UI, are the following:   

Zero foot print (no installation requirements) Only a browser is required. You can view logs in the browser window. 24


  

You can open the current phase list from the UI. You can maintain breakpoints in the browser window. You can change processing parameters during the runtime of the Software Update Manager using the web browser.

Prerequisites for Using the SL Common UI  Your browser has the following minimum supported version:  Microsoft Internet Explorer 9 and higher (not using compatibility view)  Google Chrome 28 and higher  Mozila Firefox 21 and higher

Recommendation -> We recommend that you always use the latest available browser version.

2.2.2 SL Common UI Elements and Options This section describes the different elements and options of the SL Common UI that you can use during an update or a migration.

On the user interface, you see the different roadmap steps and a progress bar indicating how much of the current roadmap step has already been processed (in percent). In addition, the UI offers several options, menus and buttons that are helpful for your update.

Figure 20: SL Common UI Elements and Options

25


Second Progress Bar The duration of the different phases within a roadmap step can vary significantly. If longrunning phases start within the roadmap step, the SL Common UI displays in addition a second progress bar that is only valid for this current phase. This supports you in estimating the progress of this long-running phase. In the following you see an example of a second progress:

Figure 21: Second Progress Bar

Failed Buckets Notification Flag If you are executing the database migration option (DMO) of the Software Update Manager, and failed buckets occur during the DMO, warning icon appears on the SL Common UI with a tooltip

"There are failed process buckets", as you can see in the following example:

Figure 22: Failed Buckets Notification Flag

If you click that icon, and a new window with the Utilities opens. The DMO Migration Control Center is displayed directly and allows you to monitor and maintain the buckets. 26


Checks.log Flag As soon as the log file checks.log contains an entry, which can be of type information, warning, or error message, an icon appears at the upper left side of the SL Common UI. You can click the icon to open a dialog box with a list of the current log file entries such as in the following example: (Note that the messages in the figure below are not real messages but only examples for demonstration purposes.)

Figure 23: Checks.log Flag

Options: Task List, Logs, and Breakpoints The right-hand side of the UI offers you the options Task List, Logs, and Breakpoints.  Task List By using the task list, you can view the status of the current, preceding and subsequent steps or phases of the procedure. The icons used in the Task Type and the Status rows are described in the legend.  Logs You can open an overview of the available log files for the current step or phase. By choosing Description, you can sort the list and use the filtering functionality to search for specific log files. The icons for the log file format are described in the legend. Note Alternatively, you can access the log files on file system level:  /abap/log

27


Some phases or steps generate log files in the subdirectories of the log directory, so you might still need file system access to analyze them.  Breakpoints SUM offers the possibility to use breakpoints, which allow you to pause the update procedure at a specified point. A list of the breakpoints is displayed. By choosing Description, you can sort the list and use the filtering functionality to search for breakpoints. The icons for the breakpoint status are described in the legend. Menus In the upper-right corner of the UI, you find the menus Legend and More. Legend The legend explains the meaning of the icons used for the different types and status of the tasks in the task list, the status of the breakpoints, and the format of the log files (for example, text or HTML).

Figure 24: Legend

More

Figure 25: More

28


With this menu, you can get support or more information, or log out from the browser session.  Logout Logs you out from the current browser session. Note that the update procedure itself continues running in the background. To log in again, proceed as described in Starting the SL Common UI 

Toggle Color Schema Switches the high-contrast color schema on or off.

 SUM Guide Opens the main Web page for the current Software Update Manager guides. 

SUM Note Opens the central SAP Note for the current Software Update Manager version.



SAP Help Portal Opens the SAP Help Portal, which contains SAP product documentation and other related information such as SAP Notes, product availability information, and community content.



Log Tail Opens the log tail viewer for several log files.



Utilities Opens a new window with an extended user interface. This user interface offers you the following options: o SUM Parameters This option enables you to adapt the configuration of your SAP system by processing the following parameters:  Standard parameters (such as host name and instance number, or system passwords)  Process parameters (such as the number of parallel processes)  Shadow system parameters  Migration parameters  Password for DDIC user  Password for shadow DDIC user  Migration passwords  Mount points  Migration key o SUM Phaselist This option displays the phase list of the Software Update Manager with the phase descriptions based on the phaselist.xml file.

29


o SUM Analysis This option visualizes the UPGANA.XML file, which contains detailed information about the update procedure and the runtime of the different phases. o DMO Migration Control Center This option is relevant, if you are executing the database migration option (DMO) of the Software Update Manager. It offers a control center for the following real-time monitoring of DMO migration phases: ○ Real-time Chart R3load Utilization ○ Real-time Gauges Hana System Load The option Configuration displays the resource files for the charts area. The system checks the existence of the selected default resource files and also of the custom resource files of other DMO migrations that you can manually.

o DMO Migration Post Analysis This option is relevant, if you are executing the database migration option (DMO) of the Software Update Manager. It offers a charting tool for the visualization of the R3load Utilization. You can select between a line chart and a bar chart. The option Configuration displays the resource files for the charts area. The system checks the existence of the selected default resource files, and also of the custom resource files of other DMO migrations that you can manually.

Note Be aware that some options of the Utilities can only be used during the update procedure if the corresponding data is available in the system.



Get Support File Creates an XML file for SAP Support if you have problems with the user interface. For more information see SL Common UI: Getting Support Using the Support File  Debug This option is used for debugging by SAP Support.  About Displays information about the current versions of the Software Update Manager, the Software Logistics Protocol, and the Software Logistics UI Client.

30


Buttons During the update, the buttons Back, Next, Cancel, and Exit are displayed depending on the current step or phase and dialog. If you encounter an issue during the update procedure such as aborts or errors, the Software Update Manager displays in some cases the buttons Repeat and/or Init. Init means basically that the current phase will be initialized again and restarted. However, this varies depending on the phase. Due to several restrictions or limitations it can also happen that only certain processes of a phase will be repeated again and not the whole phase. If you choose Repeat, the current process within a phase will be repeated from the point where update procedure stopped. In addition, the button Cleanup is offered at the end of a successful update procedure or after you have chosen the Reset button.

2.2.3 SL Common UI: Getting Support Using the Support File Context The SL Common UI offers the possibility to create support files in case of problems with the user interface during the update procedure. You create a support file and supply it to SAP Support in order to receive assistance. Proceed as follows:

2.2.4 SUM Observer Monitor The Software Update Manager offers an additional SL Common UI mode that is called the observer mode, and it is displayed as the SUM Observer Monitor. The SUM Observer Monitor is a kind of non-admin mode or guest mode of the SL Common UI that allows you to monitor a current update procedure and provides you with information about its status. You cannot enter data or change the update procedure. You can use the SUM Observer Monitor in browsers on different devices, such as on a desktop PC or on a mobile device, and with every Software Update Manager technology, that is, SUM ABAP, SUM Java, or the SUM dual-stack version. The SL Common UI automatically determines the type of the Software Update Manager, indicates it in the title bar, and displays the appropriate status information.

31


Overview of the SUM Observer Monitor in a Browser Window on a Desktop PC:

Figure 26: SUM Observer Monitor in a Browser Window on a Desktop PC

In the following, you see an example of the SUM ABAP Observer Monitor on a mobile device.

Figure 27: SUM Observer Monitor in a Browser Window on a Mobile Device

2.2.5 Communication between Back-End Processes and the SL Common UI

If you have configured the Software Update Manager for the use with the SAP Host Agent, you start the SL Common UI by entering its URL in the address bar of the Web browser. By means of the SAP Host Agent, it connects the Web browser on a client with the Software Update Manager that runs on the primary application server instance. By default, the SL Common UI uses the standard protocol HTTPS (for a secure 32


connection) and the port 1129 of the SAP Host Agent. The Software Update Manager on the primary application server instance internally calls the corresponding executables to carry out the update steps as described in the following figure:

Figure 28: Communication between Browser and Primary Application Server Instance

Note

The Software Update Manager internally calls the SAPup executable. Technically, SAPup will be started twice, which is visible in the process list. One entry with gt=httpchannel represents the SAPup handling the requests coming from the SAP Host Agent. The second SAPup with parameter guiconnect triggers tools such as R3trans, tp, or R3load.

2.2.6 SUM Directory The Software Update Manager creates the SUM directory on the host with the primary application server instance and copies data and programs into this directory. The recommended standard path of the SUM directory is:/usr/sap//SUM

2.2.7 SUM MailNotifier The MailNotifier is a Java-based tool that notifies you by means of an e-mail when the Software Update Manager (SUM) waits in a dialog for a user action. If you are using the MailNotifier, you do not have to check the user interface (UI) of the SUM frequently, which is especially helpful during long-running update phases.

33


Figure 29: The following figure shows the basic functionality of the MailNotifier

2.2.8 Storage of Passwords During the update, you have to enter passwords for the users ADM and DDIC. These passwords are stored in the memory file MEMSAPup.dat in subdirectory mem of the abap subdirectory of the update directory. Although the passwords are encrypted, you have to deny the access to the mem subdirectory for other operating system users. Only the user ADM needs access to this subdirectory. In addition, you should not share this subdirectory in the network. If you save the update directory for later analysis after the update has finished, delete the file MEMSAPup.dat from the mem subdirectory.

34


2.3 Preconfiguration Mode Planning The downtime and the consumption of system resources depend on the interaction of several parameters that you can set for the update. To optimize the duration of the downtime and the consumption of your system resources, we have grouped several parameter settings into preconfiguration modes. To provide predefined values for all parameters, you can choose the preconfiguration mode that suits your system resource situation.

Table 2: Available Preconfiguration Modes

35


Option “Keep database archiving on during the whole procedure” If you choose the option Keep database archiving on during the whole procedure, archiving is activated permanently during the update. Database archiving cannot be deactivated automatically. When you choose a preconfiguration mode for which archiving needs to be deactivated during the downtime, the Software Update Manager asks you at the beginning of roadmap step Execution to deactivate archiving. Caution Once you have deactivated archiving, you can no longer use the SAP system in production operation.

Option “Switch expert mode on” If you choose the option Switch expert mode on, you can adapt additional tool configuration options during the update: 

If the option is chosen, the Software Update Manager always displays a Support Package overview in phase BIND_PATCH (for information about this phase, see including Software), even if manual adjustment is not necessary. You can overrule the Support Package level, which is derived from the stack configuration file (stack.xml).



You can change the automatically generated instance number for the shadow instance.



You can remove installed languages or their components, for which the Software Update Manager does not find an appropriate DVD.



The Software Update Manager asks you if you want to use saved profiles from a previous update for the shadow system.

Recommendations for Choosing the Preconfiguration Mode Depending on your situation, you can choose the preconfiguration mode that best meets your requirements. Here are some recommendations: 

If you want to perform an update without a shadow system, you can choose the preconfiguration mode single system. This might be the case when you want to install an enhancement package or when you want to import the latest Support Packages after the installation of a new system.



If you update a sandbox system, the system downtime might not be important. You can then choose the preconfiguration mode single system. Using this preconfiguration mode, the prompt to start the downtime appears early compared to the standard and advanced preconfiguration modes. Since this is the last user interaction for a longer time, this allows you to let the update procedure run unattended (for example, during the weekend).



If you update a production system, you have to consider the impact on production operation. If you choose the standard or advanced preconfiguration mode, the shadow system is operated during uptime. This means that the source release system and the shadow system compete for 36


the system resources. If the resource usage is of concern for the system, it makes sense to choose the preconfiguration mode standard since this mode uses only a limited amount of system resources.



If you update a production system with a high demand for minimal downtime, the impact of the running shadow system on the source release system might not be important. In this case, it could make sense to choose advanced to shorten the overall runtime as much as possible.

Note Applying enhancement package queues or large Support Package queues using preconfiguration mode Single System. This is relevant if you perform an enhancement package installation or SPS update. During the installation of enhancement package queues or large Support Package queues with preconfiguration mode Single System, the system might need more memory than available, especially during the ACT_UPG phase. In this case, the system terminates with the runtime error SYSTEM_NO_TASK_STORAGE, TSV_TNEW_PAGE_ALLOC_FAILED, or SYSTEM_NO_ROLL.

2.4

Update Strategy Parameter

The update strategy parameter is one of the main factors in determining how much downtime is involved. The SAP update technology offers two update strategy parameters: downtime-minimized and resource-minimized. The parameter is determined by the preconfiguration mode: The standard and advanced preconfiguration modes use strategy downtime-minimized.

Figure 30: Course of the Update

37


2.5

Adaption of Parameters

Depending on your chosen preconfiguration mode, you can adapt further parameters to tailor the update to your specific needs. There are several parameters with which you can influence the use of SAP system resources for the update procedure during uptime and downtime, such as the number of background processes used by tp during uptime and downtime.

Background Process and Tool Parameters  

Release upgrade only: The preconfiguration modes make sure that these numbers fit to the upgrade strategy and database archiving strategy used. Enhancement package installation and SPS update: The background processes are used for the system cloning and thus, their number influences the speed of the system cloning process. The preconfiguration modes make sure that these numbers fit to the database archiving strategy used.

2.5.1 Database Archiving Parameter There are two options: Either the archiving mode is on during the update, or archiving is deactivated at the beginning of the Downtime roadmap step. At the beginning of the downtime, you are prompted to deactivate archiving. You are prompted again at the end of the downtime to activate archiving.

2.5.2 Process and Tool Parameters You can maintain process and tool parameters to configure the update process additionally. Several processes have parameter values for uptime and downtime. The values for downtime are active during the Downtime roadmap step of the update procedure. The values for uptime are active during the Checks and Preprocessing roadmap steps. Note that high values for processes during the uptime can have an impact on production operation.

 

   

Host name of the background server There is usually a background service available on the primary application server instance. You can check this with transaction SM51 ABAP PROCESSES (UPTIME) and ABAP PROCESSES (DOWNTIME) Number of parallel background processes and activator processes used by tp. The minimum number is 5. We recommend a value that is high enough to enable parallel processing, but small enough so that the production system is not affected. SQL PROCESSES (UPTIME) and SQL PROCESSES (DOWNTIME) Number of parallel SQL processes used by tp to execute database statements R3TRANS PROCESSES (UPTIME) and R3TRANS PROCESSES (DOWNTIME) Number of parallel import processes used by R3trans to import data into the database. Note that these processes can generate significant loads on the database. R3LOAD PROCESSES Number of R3LOAD processes. When you enter the value 1, you have to calculate an import time of 6 hours for the EU_IMPORT phases. If the load on the database during the import is an issue, you can slow down the import of the substitution set to reduce its influence on the production system. To achieve this, enter a value lower than 1. The runtime is then extended to 6 hours multiplied by this factor. For example, the value 0.5 will slow down the import to last 12 hours. 38


 

PARALLEL PHASES (UPTIME) and PARALLEL PHASES (DOWNTIME) Number of parallel phases used by SAPup Memory-optimized activation The memory-optimized mode allows the activation of ABAP Dictionary objects with reduced memory consumption, but a longer runtime. This is the default for 32-bit systems.

2.5.3 Running the Shadow Instance Remotely Use If you are unable to operate the shadow instance on the same host as the original system, you can determine another host for the shadow instance in this phase.

2.5.4 Shadow Instance Parameters When the Software Update Manager installs the shadow instance locally, an unused instance number is selected automatically. If you want to enter a specific instance number, choose the option Switch expert mode on. You have to enter an instance number that is not used in your system landscape.

2.5.5 SGEN Execution Modes If you selected the Advanced preconfiguration mode, you need to choose an execution strategy for the ABAP load generation (transaction SGEN).

2.6

Time Frame for Upgrading the Front-End Software

Note This section is only relevant if you perform a release upgrade.

Figure 31: Time Frame for Upgrading the Front-End Software

2.7

Database-Specific Aspects


39


SAP HANA DB Database Archiving and Backup If you chose to deactivate the archiving option at the beginning of roadmap step Execution, the Software Update Manager switches the database log mode to OVERWRITE after you confirmed that a complete backup (data and configuration files) has been created successfully. After the mode has been switched, the contents of the log are lost permanently. You are then able to recover the database to the state it has at this point in time. Recommendation After you have isolated the primary application server instance, you are prompted to perform a complete backup. You need to make a complete backup after the update. How you back up the database depends on whether archiving was switched on or off.

2.8

Data Management Planning

This section deals with the management of large database tables using methods such as data archiving. Note This section is only relevant if you perform a release upgrade.

2.9

Modification and Enhancement Adjustment Planning

Modifications are changes to objects of the SAP standard. There are two types of modifications: ones that make changes to the translation of an object text, and ones that make changes to the object itself. In addition (as of SAP NetWeaver 7.0), the Enhancement Framework allows enhancements, such as source code plug-ins, implementations of the new kernel-based BAdI, and class enhancements. We recommend using the new Enhancement Framework to enhance or adapt SAP development objects. Release upgrade only: All modified standard SAP objects are displayed for adjustment in transaction SPDD or SPAU. Objects that SAP no longer delivers are deleted. If you want to keep these objects, you have to accept the modifications in transaction SPDD or SPAU. Make sure that before the update there is at least one package in the customer namespace (Z*). You need this package if you have to create objects during the modification adjustment, for example, for an append structure for customer fields of an SAP table. You cannot create packages during the update. Release upgrade only: If you choose preconfiguration mode standard or advanced, the modification adjustment of ABAP Dictionary objects occurs during production operation. This is possible since the complete version management is available in the shadow system. The remaining Repository objects are still adjusted at the end of the upgrade.

40


2.10 Importing Additional Languages Note This section is only relevant if you perform a release upgrade. Recommendation Importing new languages during an upgrade is a highly efficient process and is preferable to importing a language into a production system after an upgrade.

2.11 Handling of Customer-Specific Translations and Z Languages in the Upgrade Note This section is only relevant if you perform a release upgrade.

2.12 Component Levels Contained in the Upgrade Export Note This section is only relevant if you perform a release upgrade. The transport requests that are imported during the upgrade from the Upgrade Export archives contain data for the main SAP system components and for add-on components that are included in the standard SAP delivery of SAP NetWeaver or your SAP solution. For Support Releases, the component levels in the archives are usually quite high. In the IS_SELECT phase of the Configuration roadmap step, the Software Update Manager only prompts you for add-ons contained in the archive for which we may deliver another update. Add-ons from the standard delivery for which we will not ship updates until the next release are not offered on the screen. You do not have to make a decision about them as they are updated automatically. In the BIND_PATCH phase of the Configuration roadmap step, the Software Update Manager asks you to include Support Packages in the upgrade. If the Upgrade Export archives already contains a Support Package level higher than 0, only include Support Packages above this level.

41


2.13 Additional Planning Aspects for DMO 2.13.1

Performance Optimization with Migration Duration Files

You can provide the Software Update Manager with the information about table migration durations from a previous SUM with DMO run. SUM uses this data to optimize the performance of subsequent DMO runs. Although SUM does consider the table sizes for the migration sequence, other factors can influence the migration duration. In other words, consider more criteria than just the table size for the duration of a table migration. The real durations are the best criteria, but they are only known after the migration of the tables. During a migration, SUM creates text files with the extension XML that contain the information about the migration duration for each migrated table. The files are created in directory SUM\abap\htdoc\ and are called  

MIGRATE_UT_DUR.XML for the uptime migration MIGRATE_DT_DUR.XML for the downtime migration

They can be used for the next DMO run to improve the table splitting. For this purpose, put the files into the download folder so that SUM can consider the files during the next run. Note The files with the duration information ("duration files") can even be reused for a similar system. The systems can also have a different SID. For example, you can use a duration file from a copy of the productive system for the DMO run on the productive system. The file contains both the table migration time as well as the table size, and in case of different table sizes, SAPup will adapt the migration time accordingly.

42


Preparations

3

This part of the document contains information about the preparations that you need to make before you update your system. You can prepare for the update while the system is in production operation. Careful preparation of the update is the best guarantee that it runs without errors.

3.1 Determining the Host for the Preparations Procedure Decide which hosts you need for the update preparation and the actual update of the SAP system:

 Host with the ABAP application server instance You have to execute the update on the host where the ABAP application server instance is running. Typically, it is the host with the primary application server instance. However, you can also use an additional application server instance.  Other hosts  The SL Common UI can run on any hosts that meet the necessary requirements.  Database host  You have to perform the actions that affect the database on the database host.○  User Management Engine host  The remote instance host where the User Management Engine (UME) is located must be running.

3.2 Checking the Hardware Requirements Space Requirements in the File System Make sure that there is enough temporary disk space available in the file system for the update. You need this free space for the SUM directory, the download directory, and directory DIR_TRANS. As the space requirements depend on the product, see the document with additional product-specific information for your update procedure to find information about the requirements. This document is referenced in the Master Guide or Upgrade Master Guide, respectively.

3.3 Checking the Software Requirements You have to meet certain software requirements before you update the SAP system.

3.3.1 Checking the Source Release of the SAP System Note This section is relevant if you perform a release upgrade or enhancement package installation.

3.3.2 Checking the Uninstallation of Software Components This section deals with the possible uninstallation of product instances and software components calculated by the Maintenance Planner.

43


3.3.3 Meeting the Operating System-Specific Requirements All Supported Operating Systems Release upgrade: Only 64-bit systems are supported by the Software Update Manager. For information about which operating systems are supported, see the Product Availability Matrix (PAM) on SAP Service Marketplace at http://support.sap.com/pam Windows You need to install a new SAP MMC package (sapmmc.msi) on all application servers. The package is available for download as SAPMMCMSI_.SAR file on SAP Service Marketplace at https://support.sap.com/swdc Support Packages and Patches

Figure 32: SAP MMC version before

Figure 33: SAP MMC version after

44


3.3.4 Upgrade of the Operating System and Database System: Overview When you update the SAP system, you may have to upgrade your operating system and database to a new version. For more information about which versions are currently supported, see the Product Availability Matrix on SAP Service Marketplace at http://support.sap.com/pam. The Software Update Manager only checks the minimum versions required for the update. If you need to upgrade an operating system or database, or migrate a database, then the timing and the sequence of the individual upgrades is of great importance. The procedure differs according to the database you use. The following text provides an overview of the main process steps for upgrading the operating system and database system for each database.

3.3.5 Installing or Updating SAP Host Agent The SAP Host Agent is a tool that can be used for monitoring and control of SAP instances and non-SAP instances, operating systems, and databases. Furthermore, software provisioning manager 1.0 installs or updates the SAP Host Agent in the course of the installation of an SAP instance based on SAP NetWeaver 7.0 SR3 or higher. If the SAP Host Agent is not available on the host of the SAP instance, it will be installed. If the SAP Host Agent is already preinstalled on the host of the SAP instance, the software provisioning manager checks its version and updates it if necessary. For a correct execution of the update procedure, make sure that you have installed at least the relevant minimum SAP Host Agent version on all application server instances as mentioned in the central SUM Note. However, we strongly recommend that you always use the latest version of the SAP Host Agent. For more information, see SAP Notes 1031096 and 1907566.

Figure 34: Host Agent version before

Figure 35: Host Agent version after update

45


3.4 Checking the Structural Requirements for ABAP You have to meet the following structural requirements before you update your system:



The message server must run on the host with the primary application server instance. During the update, the Software Update Manager uses Remote Function Call (RFC) to call function modules and temporarily schedules ABAP report programs for background processing. For this reason, the message server must still be running after the additional application server instances are stopped. You can only guarantee this if the message server is located on the same host as the primary application server instance.

SAP systems installed in the standard way meet the specified structural requirements. If you are not sure whether you have a standard installation, you can use the following procedure to check the structural requirements. Procedure

1. Call transaction RZ10. Choose Goto Profile values Of a server. 2. Choose the server (host) where the primary application server instance is running. The profile parameters for this server are displayed with their values. 2a. Utilities -> Import all profiles -> Of active Servers

Figure 36: Start Profil Could not be activated

1751381 - Start profiles can no longer be edited in rz10

46


Figure 37: RZ10 Profile check "OK"

3. Check the profile parameter rdisp/mshost. This parameter contains the host name where the message server is running. It must run on the same host as the primary application server instance. This makes sure that the message server is active during downtime, because only the primary application server instance runs during downtime, while the additional application server instances are stopped.

Figure 38: Profile Parameter rdisp/mshost

47


4. If you have made changes to the standard SAP system, check the profile parameter rdisp/wp_no_vb. This parameter displays the number of update processes for the primary application server instance. The number must be greater than 0.

Figure 39: Profile Parameter rdisp/wp_no_vb

3.4.1 Checking the Database-Specific Requirements Before the Update (From SQL Guide) You make sure that you meet the following requirements before you start the Software Update Manager for the first time:  Check the logon of the user adm. In this procedure, the SAP executable logs on to the SQL Server database under the Windows user under which it is called. Therefore it is necessary that the MS SQL Server contains a logon for each Windows user under which SAP processes are started. These are usually the users adm and SapService. Release upgrade only: During the upgrade, the SAP tools use the Windows user ADM to log on to the database. This means that you have to make sure before the upgrade that a logon exists for user ADM in the database and that it has the required settings. Enhancement package installation and SPS update: During the update, the SAP tools use the Windows user ADM to log on to the database. This means that you have to make sure before the update that a logon exists for user adm in the database and that it has the required settings. Check the logon in the Microsoft SQL Server Management Studio as follows:   

Start the Microsoft SQL Server Management Studio. Connect to your MS SQL Server using the Windows authentication. In the Console Root tree, expand the MS SQL Server instance node and choose SecurityLogins. The child nodes of the Logins node display the available logons. The logon for the user ADM has to exist here. Check that the database is the default database for this logon and that sysadmin is set as the server role. If you are upgrading an MCOD system, make sure that the default database name corresponds to the rsdb/mssql/dbname parameter (or dbs/mss/dbname in newer releases). If necessary, correct the settings and confirm your changes with OK.

48


Figure 40: MS SQL Role of SIDadm

3.5 Configuring OS User Authentication To ensure that the user authentication used by SUM is working and the restart operations during the update are successful, you have to configure the OS user authentication correctly before starting SUM.

3.6 Setting the Operation Mode for the Update

Enhancement package installation and SPS update: Various background jobs are started during the update. When you schedule jobs, a check is made to see whether the SAP instance on which you want them to run is defined in an operation mode. The operation mode specifies which services are offered by the work processes (dialog, update, background processing, enqueue, spool, and so on). Stop at first all planned Jobs with BTCTRNS1

Figure 41: BTCTRNS1

49


Procedure 1. Call transaction RZ04 to check the definition of your operation modes. In addition, check the DUMMY operation mode. The DUMMY operation mode may have _ entered as the server name. Change this entry to __.

2. Delete the invalid operation modes If operation modes contain names of servers other than those belonging to the system, problems may arise in the background interface in some phases. The jobs may be released, but not set as active (in theory, this affects all jobs scheduled to start on a specific server and triggered by an event).  Modify DIA 10 -> 15 and BTC 3 -> 8

Figure 42: CCMS Maintain Operation Modes and Instances before

3. Call transaction SM63 to enter the operation mode you have defined as an active operation mode for 24 hours (select Normal operation (24 hours)).

Figure 43: Display Exception Operation Mode Set for Normal 24h

50


3.7 Checking the Consistency of the Host Name For all references to the host names in the SAP system, you need to check whether you need to enter the host name in uppercase or lowercase letters. If the host name is inconsistent, problems occur in the phases PROFCHK and RFCCHK. When you enter the host name, you have to use the TCP/IP host name. Procedure Execute the following steps to check how host names are used:

1. Determine the TCP/IP name, choosing the following path:StartControl Panel Network ConnectionsPublic PropertiesProperties You can also check the TCP/IP name by entering the following command in the command line: ipconfig /all 2. Check the SAP profiles: All references to the host name in SAP profiles (for example, rdisp/btcname, SAPDBHOST, SAPLOCALHOST) should contain the TCP/IP name. The only place where uppercase and lowercase letters are not important is the SAPGLOBALHOST parameter. If you have made corrections to the SAP profiles, stop the SAP system and the SAP service and start them both again. 3. Check the nslookup configuration on both sides (Windows / Linux) if the IP are resolved correctly to your corresponding hosts as see in the Cheat sheet. a. Nslookup izrhvmkxx b. Nslookup linux-hkxx 4. If not you have to maintain the corresponding Hosts file on both sides too. Recommendation We recommend that you maintain all the addresses and host names of all the SAP servers in the grouping in the local file hosts. In addition, insert an entry for the IP address and the TCP/IP name of your computer according to the following convention:

5. Use transaction SM51 to check the host name. For each server, the different names are displayed in table format (columns Server Name, Host Name, and Message Types). The host names in the columns Server Name and Host Name have to be identical and have to match the TCP/IP host name. (Check the entries in the file \etc\hosts).---- (HANA host)

Figure 44: Hosts on K01

51


Figure 45: Hosts on H01

6. Check the case lettering of your host name in the definition of your operating types. To do this, call transaction RZ04, double-click the operation mode, and make sure that the TCP/IP name is always referenced.

3.8 Deleting the AUTOSTART Parameter Setting the parameter Autostart = 1 causes the SAP service and the SAP system to start when the Windows system is booted.

Figure 46: Autostart Parameter

3.9 Making Preparations in the Monitoring Area 3.10 Checking the Requirements for the Modification Adjustment 3.11 Filling the Download Directory You can put all files and software packages with which you want to update your system in a download directory. During the Select Target roadmap step, you are prompted to enter the path to the stackconfiguration XML file that must be available in your download directory. The Software Update Manager reads the download directory, unpacks the .SAR files, and moves the files to the appropriate directories from where they are then further processed by the Software Update Manager. You can put the following files in the download directory:  Support Package stacks of the target release Release upgrade only: The Support Package stacks include among other things ABAP patches, which are optional. If you do not fill your download directory with ABAP patches, the Software Update Manager will not automatically extract them during the Extraction roadmap step.  Enhancement packages  SAP kernel for the target release Release upgrade only: Unless you are performing the upgrade directly after you have received the DVDs, you can always check whether there is a newer version of the SAP kernel available on SAP Service Marketplace and download it to the download directory. The Software Update Manager then 52


unpacks the files and moves them to subdirectory exe of the abap subdirectory of the SUM directory. Downloading the latest version of the SAP kernel has the following advantages:





You do not have to install the latest SAP kernel after the upgrade. During the Configuration roadmap step, the Software Update Manager prompts you to put the latest SAP kernel into the download directory. If the latest SAP kernel is available in this subdirectory, the SAP kernel of your system is already up-to-date after the upgrade. You can avoid this prompt if you download the latest SAP kernel from SAP Service Marketplace to the download directory. It appears if you have included SAP Basis Support Packages in the upgrade and dependencies exist between these Support Packages and the SAP kernel version.

Enhancement package installation and SPS update: There may be dependencies between the versions of the SAP Basis Support Packages and the SAP kernel. If you want to install Support Packages for SAP Basis during the update and such dependencies exist, then during the Configuration roadmap step, the Software Update Manager prompts you to put the latest SAP kernel into the download directory. You can avoid this prompt if you download the latest SAP kernel for the target release from SAP Service Marketplace to the download directory.  

Stack configuration XML DVDs

Release upgrade only: You can provide all necessary language DVDs in the download directory.

Caution Make sure that the files and software packages that you want to include in the upgrade, such as .SAR files, are located at the top level of your download directory. They should not be located in any subdirectories. This could be the case, for example, when you just copy the upgrade DVD into the download directory. Note Usage of Spanning Archives The media content may be delivered as spanning archives on SAP Service Marketplace. This means that the archives are split into several files to avoid a large data volume and provided on multiple data carriers. To use these files with the Software Update Manager, you extract the archive files that belong together into the provided subdirectories. When the Software Update Manager requests the DVD mount points, you enter the subdirectories that contain the MID.XML file.

53


3.11.1

QCM Table check

Figure 47: SE 14 QCM Table check

 Check please

3.11.2

Additionally Checks

Figure 48: SM12 Lock entry List

 Check please

Figure 49: SM13 Update Requests

 Check please

54


3.12 Preparing Database Migration Option

3.12.1

Checking Pool and Cluster Tables

We recommend to check all pool tables or cluster tables in the source system before the migration. Note 1784377_Rev.6 - Checking pool tables and cluster tables

SDBI_CLUSTER_CHECK This report is available in all Releases >=46C via SAP Note 1077403. It checks if there are corrupt or initial cluster records. You can check individual table clusters (for example RFBLG) or all table cluster sequentially in one run. The report may have long runtimes for large datasets (see also section "Runtime" in SAP Note 1309728).

SDBI_POOL_CHECK The report is available in all Releases with SAP BASIS 6.20 or higher. For a certain table pool, you can check the contained pool tables for their readability. An improved version of the report is provided shortly with SAP Note 1807959. This version handles all table pools sequentially in a mass check.

SDBI_CHECK_BCD_NUMBERS The report is available in all Releases as of SAP BASIS 6.20 or higher (see SAP Note 700486). It checks if the BCD number are correct in a table that you must specify individually. SAP Note 1807959 provides an improved version of the report. As a result, all pool tables and cluster tables can then be handled sequentially in a mass check. For the Unicode and SAP HANA migrations, we recommend that you execute the reports SDBI_CLUSTER_CHECK for all cluster tables as well as SDBI_CHECK_BCD_NUMBERS for all pool tables and cluster tables in time before the scheduled migration date. You should execute the reports several months before the migration date because they can have very long runtimes and if errors should occur, you need time to correct them. Note: Both reports must be executed in the background. Errors are output in a result list (spool list). Both reports contain additional information in the header of the source text.

SDBI_CLUSTER_CHECK 1077403 Cluster table check with SDBI_CLUSTER_CHECK

Figure 50: SDBI_CLUSTER_CHECK Display overall Status

55


Figure 51: Result of overall status

Figure 52: Execute Cluster Check

56


Figure 53: Background Option of SDBI_CLUSTER_CHECK

Figure 54: Run time of SDBI_CLUSTER_CHECK

Figure 55: Check Result again -> No action needed

SDBI_POOL_CHECK

Figure 56: SDBI_POOL_CHECK

57


Figure 57: Runtime SDBI_POOL_CHECK

Result overview:

Figure 58: Result SDBI_POOL_CHECK

Log:

TXT

Log:

HTM

SDBI_CHECK_BCD_NUMBERS --------

Figure 59: SDBI_CHECK_BCD_NUMBERS spool request

Repair SDBI_CHECK_BCD_NUMBERS

Figure 60: Repair SDBI_CHECK_BCD_NUMBERS

58


Figure 61: Result of SDBI_CHECK_BCD_NUMBERS

3.12.2

Oracle: Suppressing Long-Running Phases

If your source database is Oracle, you can suppress long-running phases before you start the update.

3.12.3

Oracle: Checking Database Parameterization

If your source database is Oracle, make sure that the database parameterization is properly configured with regard to parameter parallel_max_server.

3.12.4

Preparing Target Database SAP HANA

Prepare the target database SAP HANA for the SUM with DMO run. ------Procedure 1. Make sure that you have successfully installed an SAP HANA database. 2. Make sure that you are prepared to enter system details and the password of user SYSTEM as well. linux-hkxx SID: HDB /00 IP: 10.0.2.xx

3.12.5

Requesting Migration Key for Target Database

Make sure that you have a valid migration key for the new target database. 1G5fdEM504qSq3egt6h]pGhK

59


3.12.6

Downloading Latest Database Client Software

Make sure that you have the latest client software for your target database.



HANA Client 1.00.120.042.1474657934 at minimum

Figure 62: hdbsetup.exe

Figure 63: SAP HANA Lifecycle Management “Define Client Properties“

60


Figure 64: SAP HANA Lifecycle Management “Review and Confirm“

Figure 65: SAP HANA Lifecycle Management “Install Software“

61


Figure 66: SAP HANA Lifecycle Management “Finish“

3.12.7

Requesting Permanent SAP License

Make sure that you have a permanent SAP license for your system that will be migrated to the target database.  This will be sent to you after migration is done

Figure 67: new license

3.12.8

Changing Schema Name

This section is relevant if you want to change the schema name of the target database SAP HANA.

3.12.9

Downloading Files from Maintenance Planner

Download the files calculated by the SAP Maintenance Planner that are necessary for the update.

3.12.10

Testing Update and Migration

Before your start the actual update and migration procedure for your productive system, it is necessary and highly recommended that you carry out DMO test runs.

62


4

Running the Software Update Manager

This section provides information about starting and running the Software Update Manager. It describes all required user input and actions, as well as critical points during the update.

Figure 68: Disk space before Conversion

4.1 Meeting the Requirements for the SUM Directory If you do not specify a path when you unpack the Software Update Manager package, the SUM directory is automatically created as a subdirectory of the directory where you unpack the software package. However, we recommend that you use the standard path :\usr\sap\.

4.2 Downloading and Unpacking the Software Update Manager 1. Download the latest version of the Software Update Manager from SAP Service Marketplace. Note The latest version of the Software Update Manager can automatically be downloaded when calculating the target software components and the stack configuration file in SAP Solution Manager Maintenance Optimizer. For more information about using this function, see SAP Note 1626435. 2. Log on to the host on which the primary application server instance is running as user ADM. 3. Unpack the Software Update Manager package with the following command: SAPCAR –xvf //.SAR -R /usr/sap/ This command creates the directory SUM under the /usr/sap/ directory. You can also specify a directory other than /usr/sap/. In the following, the directory //SUM is referred to as . SAPCAR –xvf Z:\SUM10SP18_3-20006676.SAR -R D:\usr\sap\Kxx

63


Figure 69: : SUM directory

4.3 Starting the Software Update Manager Prerequisites

    

You have downloaded and unpacked the latest version of the Software Update Manager and the software packages that you need for the update. You have met the requirements for the update. The SAP system and the database have been started. The SAPCAR version that is referenced in the environment variable PATH is identical with the one that is located in the kernel directory. In addition, no reference to any other SAPCAR version should exist in the PATH variable. Your system has at least the minimum supported SAP Host Agent version mentioned in SAP Note 2155664 on your remote SCS instance and on all additional application server instances, if your system has any. o C:\Program Files\SAP\hostctrl\exe o saphostexec –status (als administrator) o saphostexec -version

Figure 70: HOST Agent Version



On the host where you want to start the UI, at least Java 6 must be installed

64


Figure 71: JAVA Version

To start the Software Update Manager, enter the command cd \usr\sap\\SUM /STARTUP.BAT confighostagent Kxx

Start within a Command Prompt as Administrator

Figure 72: Registration of HOST AGENT

No SSL within HOST AGENT, we have to use port 1128:

4.4 Starting and Restarting the Software Update Manager Prerequisites

 

SAP Host Agent has been configured on your system with the minimum version required for your scenario. For more information, see Installing or Updating SAP Host Agent When using Internet Explorer, you have to make sure that the URL relevant for your system is listed in the “Trusted” security zone. To do so, proceed as described in the Internet Explorer documentation.

65


Procedure

 

Open a Web browser window. In the address bar, enter the following URL:https://:1129/lmsl/sumabap//doc/sluigui o Replace with your system ID. o 1129 is the https port of the SAP Host Agent. o If the SSL has not been configured, use http instead of https at the beginning of the URL and use port 1128: http://:1128/lmsl/sumabap//doc/sluigui

In the dialog box that appears, enter the user name adm and the password.

To start the installation GUI, call the Webpage directly on the Windows Kxx host http://izrhvmkxx:1128/lmsl/sumabap/Kxx/doc/sluigui of the SUM Tool

Figure 73: enter the user name adm and the password

Results The SAP Host Agent starts the Software Update Manager, and the SL Common GUI of the Software Update Manager is displayed in the Web browser. Note Start Options: By default, the SL Common UI starts the Software Update Manager without any special parameters, and you can skip the field Start Options. If you want to start the Software Update Manager with special parameters provided by SAP, enter these parameters in the field Start Options and choose Next.

 ./STARTUP restarted den HostAgent für verwendung von SUM  Browser verbindet sich an den HA und merkt aha SUM wird verwendet und startet je nach Software hier „ABAP“ aus dem einen Schritt tiefer liegenden Verzeichnis „SUMSTART“ und daraufhin wird der Anmeldescreen für sidadm nötig 66


4.5

Starting the SUM Observer Monitor

The Software Update Manager offers an additional SL Common UI mode called the observer mode.This mode is displayed as SUM observer monitor.

4.6

Resetting the Update

The Software Update Manager offers the option to reset the update.

4.7 Using Breakpoints During the Update You can stop the update procedure at a specified point by using breakpoints.

4.8 Starting the MailNotifier The MailNotifier informs you via e-mail when the Software Update Manager (SUM) displays a dialog that requires user interaction.

4.9 Verifying SAP Archives (Digital Signature Handling) SUM offers the option to check the signature of SAP software archives that are located in the download folder.

4.10 Importing or Installing Software After Starting the Upgrade Note This section is only relevant if you perform a release upgrade.

4.11 Making Entries for the Specify Authentication Mechanism Roadmap Step Procedure Enter the password for the ADM user and choose Next.

67


4.12 Making Entries for the Select Target Roadmap Step The new content is updated with the stack that is available in the download directory. The stack is described in a stack configuration XML file. If you have downloaded the software packages using the Maintenance Optimizer in SAP Solution Manager, the stack configuration file has been generated automatically and saved to the EPS inbox of SAP Solution Manager. In the Select Target roadmap step, you have to enter the path to the stack configuration file. 4.12.1.1 Start time 04-01-17 3:24pm

Figure 74: Stack.xml

Z:\CONV\MP_Stack_1000106540_2034_.xml

4.13 Making Entries for the Extraction Roadmap Step 4.13.1 Current Phase: PREP_PRE_CHECK/PROFREAD

Figure 75: Required System passwords

68


4.13.2

PREP_PRE_CHECK/SPAMCHK_INI

Figure 76: SPAM Version Check

4.13.3

PREP_INPUT/MIG2NDDB_INI

Figure 77: Migration Parameters

1G5fdEM504qSq3egt6h]pGhK Small hint to do a copy to an editor and check if no blank before and at the end available

69


Figure 78: DMO may compare content of table rows

Figure 79: Checks Information

4.13.3.1Extraction End Time 04-01-17 4:06pm

70


4.14 Configuration 4.14.1

Current Phase: PREP_CONFIGURATION/INITSUBST

Figure 80: Tool Configuration

71


4.14.2

Current Phase: PREP_CONFIGURATION/INITSUBST

Figure 81: Parameters for procedure

72


4.14.2.1 Start Time 04-01-17 7:15pm

Figure 82: Target database client

Path: Z:\SAP_HANA_CLIENT_Win64_120_45\

4.14.3 PREP_CONFIGURATION/SUBMOD_MIG_INSTCLIENT/HDB_INS TCLIENT

Figure 83: Required Migration Specific password

 See cheat sheet

73


4.14.4 FIG

PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/HDB_MIGCON

Figure 84: Database Migration Initialization

 See cheat sheet 4.14.4.1 End Time 04-01-2017 7:20pm 4.14.4.2 Go further Time 04-01-2017 7:20pm

Figure 85: Required Migration Specific Passwords

74


4.14.5 E

PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/HDB_PREPAR

Figure 86: Required Migration Specific Passwords user DBACOCKPIT

Figure 87: Required Migration Specific Passwords user SAPK00

75


4.14.6

PREP_CONFIGURATION/LANG_SELECT

Figure 88: Language Update/Installation

Figure 89: Language Update/Installation Summary

76


4.14.7

SUM-Phase: PREP_CONFIGURATION/CHECK4NOTES_TOOL

Figure 90: Missing Notes

*Missing SAP Notes:* has to be applied by Partner’s

0002344014

0002222916 0002260116 0002122333

Figure 91: Implemented SAP Notes

 Release TP’s

77


Figure 92: Release all TP's

4.14.7.1 Time 04-01-2017 8:44pm

4.14.8

PREP_SETUP/REQ_ARCHIVING_BLOCKED

Figure 93: New archiving jobs and aging jobs will be blocked

78


4.14.9

PREP_EXTENSION/UPLOAD_REQUEST

Figure 94: Add-On Request Part I

4.14.10

PREP_EXTENSION_INST

Figure 95: Add-On Request Part II

 No additional Add On

79


4.14.10.1

Time 04-01-2017 8:50pm

4.14.11

PREP_EXTENSION/UNINSTALL_PREPARE

Figure 96: COMPONENT Uninstallation Preparation POASBC 100_731

2322477 - Uninstallation of Add-on POA SBC 100_731Version 4 from 06.06.2016  No activities (“I have read the note”)

4.14.12

PREP_EXTENSION/BIND_PATCH

Figure 97: Select Support Packages You Want to Include

80


4.14.12.1

End Time 04-01-2017 09:10pm

4.14.12.2

Start Time 04-01-2017 10:45pm

 Solve problems if comes up  Repeat phase -> “Next”  No error anymore

81


4.14.13

PREP_EXTENSION/BIND_PATCH

Figure 98: Include Change Request

4.14.13.1

Time 04-01-2017 11:12pm

4.14.14

Current Phase: PREP_INTEGRATION/ADJUSTPRP

Figure 99: Modification Adjustment

 No Requests

82


4.14.15

Current Phase: PREP_INSTALL/INITSHD

Figure 100: Shadow Instance Numbers

4.14.16

Backup/Delete no used Profiles

Figure 101: Backup Profiles

 Backup profiles to Z:\Backup_Profiles

Figure 102: Delete Profiles

 Delete unused profiles *.1”

83


4.14.17

CURRENT Phase: PREP_INSTALL/SHDINST_CPY

Figure 103: Shadow System Profiles

Figure 104: Information Log after Configuration

4.14.17.1

End Time 04-01-2017 11:18pm

4.14.18

Current Phase: PREP_INSTALL/RUN_DBCLONE_INIT

Figure 105: Continue with roadmap step Checks

84


4.15 Checks

Figure 106: Phase Checks

4.15.1.1Start Time 04-01-2017 11:18pm

4.15.2

Current Phase: PREP_PREPROC/SAVE_VAR_CHK

Figure 107: Save Variants

 After reading note 1696821 choose “No”

85


4.15.2.1Time 04-01-2017 11:31 pm

Figure 108: Parameters for BW-Specific reports

 “OK” choose Next

Figure 109: Start ASU ToolBox

 No Actions (The phase still runs, but can be ignored in some time for S/4HANA conversions)  Next

86


4.16 Preprocessing 4.16.1 Current Phase: PREP_GENCHECKS/SUBMOD_MIG_PRPCHECKS/JOB_RDDNTPUR_PR EP

Figure 110: Continue with roadmap step "Preprocessing”

4.16.1.1Start Time 04-01-2017 11:35pm

Figure 111: : Preprocessing

87


4.16.2

Current Phase: MAIN_INIT/REPACHK1

Figure 112: Inactive Object found

 All deleted and only green activated and release the corresponding created transport If you get some problems with LZIBCTOP because there was two versions available and both of them were empty. You have nothing to correct the code because there are much too many thing to do. Here are two solutions:  We had a similar issue with that include. We ended up starring everything in function module ZCONTROL_RECIPE_DOWNLOAD (function group ZIBC) to get rid of a rather nasty syntax error. After that, the top include could be activated and processing could be continued.  But if I delete them, I have a problem with all the function from the group ZIBC. Shall I delete the whole function group?

88


4.16.3

Current Phase: MAIN_INIT/REPACHK_TRANS

Figure 113: Lock Development Environment

4.16.3.1 Start Time 04-01-2017 11:55pm 4.16.3.1.1

Disk space Preprocessing

Figure 114: Disk space Preprocessing 04-01-2017 11:55pm

89


Figure 115: MAIN_SHDCRE/SHADOW_IMPORT_UPG1 "Deadlock" 04-01-2017 01:30 am

 Between 50% and 54% during the phase MAIN_SHDCRE/SHADOW_IMPORT_UPG1 we get an SQL -1205 with a deadlock 90


Figure 116: MAIN_SHDCRE/SHADOW_IMPORT_UPG1 repeat after deadlock

 Repeat “Next”, goes further without any problems  Time 05-01-2017 07:10am 4.16.3.2 Meantime 05-01-2017 09:05 am

Figure 117: Meantime 14-12-16 1:30 pm/05-01-17 09:05 am "Preprocessing" 33%

91


4.16.4

CURRENT Phase: MAIN_SHDRUN/ACT_UPG

Figure 118: Repository Modifications Shadow Instance

4.16.4.1 Stop Time 05-01-2017 09:26 am

Figure 119: SE06 Shadow Instance "Modifiable"

 Press SAVE  TR SPDD

92


Figure 120: SPAU Shadow Protocol

Figure 121: SPDD with Assistant

 Reset both  Create new Request

Figure 122: SPAU Shadow 1610

93


Figure 123: SPDD without Assistant I

 Reset

Figure 124: SPDD without Assistant II

 Adjust

Figure 125: Accept proposal of table SUPG_TEST_STRUCTURE

94


Figure 126: SPDD without Assistant III

 Adjust

Figure 127: Accept proposel of table T130F_C

Figure 128: SPDD without Assistant IV

95


 Adjust

Figure 129: Edit Proposal of table T130F_C

Figure 130: Dictionary: Define Technical Settings of table T130F_C

 SAVE  Back 96


Figure 131: Continue Proposal of table T130F_C

 Continue

Figure 132: Modification completed

 Delete completed entries Adjustments made, continue with procedure within SUM Just an information to the members, if you get an undocumented entry in the SPDD for our system

Figure 133: RSEUPACTRL undocumented entry in the SPDD

 Since the old version and the new version seems to be the same, you can reset the object to original.

97


4.16.4.2Start Time 05-01-2017 10:53am

Figure 134: Start time 14-12-16 2:10 pm/ 05-01-17 10:53am "Preprocessing" 35%

4.16.4.3 Meantime 05-01-2017 1:35pm

Figure 135: Meantime 14-12-16 4:45pm/05-01-17 1:35pm "Preprocessing" 43%

98


4.16.4.4 Meantime 05-01-2017 2:52pm

Figure 136: Meantime 14-12-16 5:50 pm/05-01-17 02:52pm "Preprocessing" 46%

99


4.16.4.5 Stop Time 05-01-2017 3:53pm

Figure 137: Missing SAP Notes for Tools in Shadow System

100


             

2381743 2373473 2352928 2376191 2376298 2371299 2356758 2377063 2378064 2381775 2380453 2371811 2379303 2368460

4.16.4.6Start Time 05-01-2017 4pm TR SM59 and set password of User OSS_RFC “CPIC”

Figure 138: SAPOSS RFC Password

 Test RFC Connection  Test authorization

101


Figure 139: 14 notes implemented

 The created TP has not to be released 4.16.4.7 Stop Time 05-01-2017 4:15pm  Next SUM 4.16.4.8 Start Time 05-01-2017 4:15pm 4.16.4.9 Stop Time 05-01-2017 5:27pm

4.16.5 Current Phase: MAIN_SHDIMP/SUBMOD_MIG_UPTIMR_RUN/REQ_SCALEUP_PREREQ

Figure 140: Perform Scale Up (Single Node) Prerequisite on SAP HANA if necessary

 No action

102


4.16.5.1 Start Time 05-01-2017 5:30pm 4.16.5.2 Stop Time 05-01-2017 7:30pm

4.16.6

Current Phase: MAIN_SHDIMP/REQ_PARTITIONING_MATDOC

Figure 141: Provide partitioning for table MATDOC

2259038 - S/4HANA: Partitioning of table MATDOC  Next

4.16.7

Current Phase: MAIN_DTTRANSSHD/DOWNCONF_DTTRANS

Figure 142: Preparations for Downtime

103


4.16.8 Current Phase: MAIN_DTTRANSSHD/DOWNCONF_DTTRANS_BCK

Figure 143: Backup Request

4.16.8.1 Disk space before Downtime

Figure 144: Disk Space before Downtime

104


4.16.9

HDB Memory

Figure 145: HDB memory before Downtime

Verify if HANA Log Mode to overwrite

Figure 146: Log Mode HANA Studio "overwrite"Execution

4.16.10 Current Phase: MAIN_DTTRANS/SETSYNC_PREUP_DT_CONFIRM

Figure 147: Continue with roadmap step "Execution"

105


4.17 Execution Start Time 05-01-2017 10:35pm

Figure 148: SUM ABAP process started Execution

Figure 149: Error in phase MAIN_SWITCH/SUBMOD_MIG_SWITCH_NEW...

 No Error comes up in the second run

106


4.17.1.1Meantime 05-01-2017 11:10pm

Figure 150: Meantime -> 74%

4.17.2

Current Phase: MAIN_UPTRANS/UPCONF

4.17.2.1 Stop Time 06-01-2017 5:13am

Figure 151: End of Downtime

107


4.17.3

Current Phase: MAIN_POSTPROC/SETUPGPAR_UPG_POST

Figure 152: Continue with roadmap step "Postprocessing"

4.18 Postprocessing 4.18.1.1 Start Time 06-01-2017 7:25am

Figure 4-153: Post Prostprocessing

108


4.18.2 Current Phase: MAIN_POSTPROC/SUBMOD_MIG_BI_TASKS_POSTP1/REQPOSTING_B WHANA_NOTE

Figure 154: Apply note 1908075

1908075 - BW on SAP HANA: Table placement and landscape redistribution

 No activities  Go further

109


4.18.3

Current Phase: MAIN_POSTPROC/SPAUINFO

4.18.3.1 Stop Time 06-01-2017 7:35am

Figure 155: Procedure Complete

 After New SAP License is implemented we can do as made the SPAU and SPDD

4.18.3.2 Start Time 06-01-2017 7:35am

4.18.4

Current Phase: MAIN_POSTPROC/REQUPFINAL

Figure 156: Start of Cleanup Processing

110


4.18.5

LONGPOST.LOG

Figure 157: Longpost.Log report 'VCH_MASS_MAINTENANCE'

 See section Post activities 6.3.22

4.19 Evaluating the Update Process

Figure 158: Update complete

111


 Don’t send

Figure 159: Procedure Finished

4.19.1.1 End Time: 06-01-2017 8:00am

 Exit

Figure 160: Confirmation

 Yes  Close Browser

112


Figure 161: Close Browser

4.20 Running the Software Update Manager Repeatedly Prerequisites You have successfully performed an update process using SUM and have exited the tool. Procedure If you want to start the Software Update Manager from the beginning again, proceed as follows: 1. Rename the update directory used for the already finished process. 2. Unpack SUM again and start it as described in Starting the Software Update Manager

4.21 Stopping the Software Update Manager After a successful update, you have to stop the Software Update Manager manually. Context

113


After the update procedure has been performed successfully, SUM displays an appropriate information in the Web browser window. Afterwards, you must terminate all remaining SAPup processes on operating system level to stop SUM completely. This also applies after a reset and the subsequent cleanup in case you do not want to continue the update. Procedure 1. Close all browser windows connected with SL Common UI. 2. Search for all SAPup processes 3. Kill all found process IDs (PIDs) using the following command: kill

Figure 162: Close SAPup process

5

SUM Timeline overview

Figure 163: SUM Summary Timeline Folder

-> Summary Timeline 114


 -> Can be open with IE or Chrome

6 Time SUMMARY 6.1 Time Overall 28 hours / 31 hours 6.1.1 Entries / Extraction: 1 hour / 0.5 hour 6.1.1.1 2-12-2016 3pm – 2-12-2016 4pm = 1h 6.1.1.2 4-01-2016 3:24pm – 4-01-2016 4:06pm = 0.5h ------------------------------------------------------------------------------------------------------------------- -------------

6.1.2 Configuration: 6 hours /4 hours 6.1.2.1 2-12-2016 5pm – 2-12-2016 5:45pm = 45min 6.1.2.2 8-12-2016 9am – 8-12-2016 1:30pm = 4.5h 6.1.2.3 13-12-2016 10:40am – 13-12-2016 11:20am = 40min 6.1.2.4 4-01-2017 7:15pm – 4-01-2017 11:18pm = 4h --------------------------------------------------------------------------------------------------------------------------------

6.1.3 Checks: 1 hour/ 0.5 hours 6.1.3.1 13-12-2016 11:20am – 13-12-2016 12:25pm = 1h 6.1.3.2 04-01-2017 11:18pm – 04-01-2017 11:35pm = 0.5h --------------------------------------------------------------------------------------------------------------------------------

115


6.1.4 Preprocessing: 13 hours/ 19 hours 6.1.4.1 13-12-2016 12:25pm – 13-12-2016 4:30pm = 4h 6.1.4.2 14-12-2016 12:05pm – 14-12-2016 6:40pm =6.5h 6.1.4.3 14-12-2016 9:55pm – 15-12-2016 0:30am = 2.5h 6.1.4.4 04-01-2017 11:35pm – 05-01-2017 7:30pm = 19h ----------------------------------------------------------------------------------------------------------------------------- ---

6.1.5 Execution: 6 hours / 7 hours 6.1.5.1 15-12-2016 1:30am – 15-12-2016 2:05am = 0.5h 6.1.5.2 15-12-2016 8:10am – 15-12-2016 1:40pm = 5.5h 6.1.5.3 05-01-2017 10:35pm – 06-01-2017 5:13 am =7h ----------------------------------------------------------------------------------------------------------------------------- ---

6.1.6 Postprocessing: 1 hour / 0.5 hours 6.1.6.1 15-12-2016 2:10pm – 15-12-2016 3:15pm = 1h 6.1.6.2 06-01-2017 7:25am – 06-01-2017 8:00 am = 0.5h ----------------------------------------------------------------------------------------------------------------------------- ---

6.2 Disk space/Memory 6.2.1 Disk space K01: 6.2.1.1 Before

Figure 164: Disk space Windows before Conversion

116


6.2.1.2 After

Figure 165: Disk space Windows after Conversion

6.2.2 Memory HDB: 6.2.2.1 After

Figure 166: HDB Memory and Disk space after Conversion

117


6.2.3 Check HDBVIEWS

Figure 167: Analysis and Repair Tool for Views generated by HDB (TR hdbviews)

 Check please and make some activities

Figure 168: Generate Views

Figure 169: Result of generated HDBVIEWS

118


6.3 Follow-Up Activities 6.3.1 Check Installed Software and Product Versions

Figure 170: S/4HANA Installed Software Components

Figure 171: S/4HANA Installed Product Versions

119


6.3.2 SAP HANA DB: Backing Up the Database  No activities

6.3.3 Performing Follow-Up Activities in the Monitoring Area  No activities

6.3.4 Performing Follow-Up Activities for the SAP Kernel Check kernel version

Figure 172: Kernel after Conversion

 No activities

6.3.5 Reimporting Additional Programs

During the update, the contents of directory \usr\sap\\SYS\exe\run are completely deleted before the new SAP kernel is imported. If you installed additional programs in this directory such as the RFC library, you have to install them again.

 No activities

120


6.3.5.1 SAP License

Figure 173: Get Hardware Key

 Sent us the Hardware Key with SID to Mail address 10steps2s4 o Example K01 Hardware key: H1495596928

Figure 174: Install new License

 Install

Figure 175: Permanent license key successfully installed

121


6.3.6 Adjusting Repository Objects If you have made modifications to objects such as programs, screens or interfaces (GUIs), you have to adjust them with transaction SPAU. Adjust notes before adjusting modifications. Modification adjustment of an object is only possible after all notes, which are changing the object, have been adjusted.  Activities are not needed, because some notes can’t be installed due to not released for customer

Figure 176: SPAU after Conversion

 Compute adjustment mode (117)

Figure 177: Again, needed notes

Figure 178: Note actually not released

 Cancel -> Adjustment goes further o Hint: some notes can’t be installed do to not released for customer

122


Figure 179: Confirm obsolete 88 notes

6.3.7 Updating the Where-Used List in the ABAP Workbench Note This action is optional.  No activities

6.3.8 Adjusting Customizing Settings This section is only valid if you perform a release upgrade.

Caution Adjusting the Customizing settings is done in close cooperation with the business consultants and other upgrade project team members.  -> Inform project members

6.3.9 Adjusting Customer Developments Note This section is only valid if you perform a release upgrade. Caution Adjusting the Customizing settings is done in close cooperation with the business consultants and other upgrade project team members.  -> Inform project members

123


6.3.10

Performing Follow-Up Activities for SAP Solution Manager

Note This section is only valid if you perform a release upgrade.

 No activities

6.3.11

Secure Single Sign-On with Microsoft LAN Manager SSP

Note This section is only valid if you perform a release upgrade.

 No activities

6.3.12

Adjusting the User and Role Administration

Use After the update, you have to make adjustments to the user and role administration. What these are depends on whether you were already using the profile generator in the source release.

6.3.13

Rescheduling Background Jobs

Use this procedure to release all background jobs that were locked when you isolated the primary application server instance. Procedure 1. Log on in client 100 as user DDIC. 2. Execute report BTCTRNS2.

Figure 180: BTCTRNS2

124


6.3.14

Generating Loads

Stop SQL Server Instance

Figure 181: Stop SQL Server Instanz after Conversion

Disable all SQL Server Services

Figure 182: Disabled SQL Services

Remark: During the post-installation activities, you schedule an SGEN for all components (450.000+ objects). This does not seem like a sensible thing to do, since this will generate loads for objects that might never be used. Better practice would seem to skip this step entirely, and just let the used objects get compiled on first execution. This will also not waste any memory space on HANA. In a live situation on a productive system, the testing of transactions after the update/upgrade will probably take care of the bulk of the compilations to be done anyway.

125


Load Procedure Generating Loads with Transaction SGEN 1. Call transaction SGEN. 2. Select one of the following options: Regenerate after an SAP System upgrade Generation of BSP Applications Generation of Web Dynpros 3. Repeat the generation for all options that you want to perform. For a detailed description of these features, see the online documentation in transaction SGEN by choosing Information on the SAP Load Generator, or in the Job Monitor by choosing Job Monitor. 6.3.14.1 Start Time 06-01-2017 9:42am

Figure 183: Job SGEN

Figure 184: SGEN Result I

Figure 185: SGEN Result II

6.3.14.2 Run time: 4.5h/4h

126


6.3.15

Checking for Unused Indexes

Figure 186: Missing Tables and Indexes or views

 Select all missing views and create on DB

Figure 187: Create missing views on DB

 Select mass processing

Figure 188: Mass processing for missing DB views

 Go to SE14

127


Figure 189: Mass Processing within SE14

 Select all and then schedule selections

Figure 190: schedule selections

 Wait until job is successfully finished

Figure 191: Job of generated DB views

 Check again Missing tables and Indexes

Figure 192: dbacockpit missing tables and indexes part II

128


6.3.16

Importing Support Packages After the Upgrade


 No activities

6.3.17

Transport Management System: Distributing the Configuration

After an upgrade, you have to distribute the information about the new release to all systems in the transport domain. Note This section is only relevant if you perform a release upgrade.

 No activities

6.3.18

DMO-related Follow-up Activities

 No activities

6.3.19 Configuring Domain Controller for Transport Management System  No activities

6.3.20 Application specific issues to be considered within the followon phase of a system conversion Here you can find a collection of information about application specific issues to be considered within the follow-on phase of a system conversion project to SAP S/4HANA 1610 2389807 - SAP S/4HANA 1610 - application specific notes in system conversion follow-on phase 2367771 Migration: Error message FINS_RECON741 in step R23 because A 2386085 - sFIN Migration: Error FINS_RECON 543 or 544 for transfer prices

Figure 193: Installed New Notes after conversion

129


6.3.21

ST22 dumps after conversion

Check if you get some dumps as follow MESSAGE_TYPE_X" "SAPLRRBA" bzw. LRRBAF01 "MANDT_UNIQUE_GET" HINT: Please check also within WP09 after activation of SAP_GATEWAY_ACTIVATE_ODATA_SERV with STC01  Add BWMANDT 100 in table RSADMINA  check note 2213074 - MESSAGE_TYPE_X in Program MANDT_UNIQUE_GET during Upgrade  2213074 - MESSAGE_TYPE_X in Program MANDT_UNIQUE_GET during Upgrade and run report RS_TCO_ACTIVATION in the background

6.3.22

VCH_MASS_MAINTENANCE

Check after a conversion was done the LONGPOST.LOG for some more activities. In this case the report VCH_MASS_MAINTENANCE must be run, because MRP Live will be activated during the conversion. See note 2324671 - Preparing the data for the low-level configuration with SAP HANA.

130


7 Tables and Figures Figure 1: Software Update Manager 1.0 SP18 incl. Database Migration Option Guide .............................. 9 Figure 2: SE14 Result of table TCD0B ......................................................................................................... 11 Figure 3: Content of table TCD0B ............................................................................................................... 11 Figure 4: Additional notes of note 2185960 ............................................................................................... 13 Figure 5: R_S4_PRE_TRANSITION_CHECKS to stack XML ........................................................................... 15 Figure 6: S4_PRE_TRANSITION_CHECKS Result overall.............................................................................. 15 Figure 7: S4_PRE_TRANSITION_CHECKS Check Result ERROR “10” ........................................................... 15 Figure 8: S4_PRE_TRANSITION_CHECKS Check Result WARNING "60" ..................................................... 16 Figure 9: S4_PRE_TRANSITION_CHECKS Check Result WARNING "5" ....................................................... 16 Figure 10: Updating SAP ABAP Systems on Windows: Microsoft SQL ....................................................... 18 Figure 11: Database Migration Option: Target Database SAP HANA ......................................................... 18 Figure 12: New ASCS instance .................................................................................................................... 19 Figure 13: Upgrade and Update Guide SAP Netweaver 7.4 ABAP ............................................................. 19 Figure 14: SCC4 Client view ........................................................................................................................ 20 Figure 15: Kernel update before ................................................................................................................ 20 Figure 16: Kernel update after ................................................................................................................... 20 Figure 17: Standalone enqueue server and ENQ work processes.............................................................. 21 Figure 18: Process Flow of a System Switch Upgrade ................................................................................ 22 Figure 19: Different phases of the DMO .................................................................................................... 23 Figure 20: SL Common UI Elements and Options ....................................................................................... 25 Figure 21: Second Progress Bar .................................................................................................................. 26 Figure 22: Failed Buckets Notification Flag ................................................................................................ 26 Figure 23: Checks.log Flag .......................................................................................................................... 27 Figure 24: Legend ....................................................................................................................................... 28 Figure 25: More .......................................................................................................................................... 28 Figure 26: SUM Observer Monitor in a Browser Window on a Desktop PC .............................................. 32 Figure 27: SUM Observer Monitor in a Browser Window on a Mobile Device .......................................... 32 Figure 28: Communication between Browser and Primary Application Server Instance .......................... 33 Figure 29: The following figure shows the basic functionality of the MailNotifier .................................... 34 Figure 30: Course of the Update ................................................................................................................ 37 Figure 31: Time Frame for Upgrading the Front-End Software.................................................................. 39 Figure 32: SAP MMC version before........................................................................................................... 44 Figure 33: SAP MMC version after ............................................................................................................. 44 Figure 34: Host Agent version before......................................................................................................... 45 Figure 35: Host Agent version after update ............................................................................................... 45 Figure 36: Start Profil Could not be activated ............................................................................................ 46 Figure 37: RZ10 Profile check "OK" ............................................................................................................ 47 Figure 38: Profile Parameter rdisp/mshost ................................................................................................ 47 Figure 39: Profile Parameter rdisp/wp_no_vb ........................................................................................... 48 Figure 40: MS SQL Role of SIDadm ............................................................................................................. 49 Figure 41: BTCTRNS1 .................................................................................................................................. 49

131


Figure 42: CCMS Maintain Operation Modes and Instances before .......................................................... 50 Figure 43: Display Exception Operation Mode Set for Normal 24h ........................................................... 50 Figure 44: Hosts on K01 .............................................................................................................................. 51 Figure 45: Hosts on H01 ............................................................................................................................. 52 Figure 46: Autostart Parameter.................................................................................................................. 52 Figure 47: SE 14 QCM Table check ............................................................................................................. 54 Figure 48: SM12 Lock entry List .................................................................................................................. 54 Figure 49: SM13 Update Requests ............................................................................................................. 54 Figure 50: SDBI_CLUSTER_CHECK Display overall Status ........................................................................... 55 Figure 51: Result of overall status .............................................................................................................. 56 Figure 52: Execute Cluster Check ............................................................................................................... 56 Figure 53: Background Option of SDBI_CLUSTER_CHECK .......................................................................... 57 Figure 54: Run time of SDBI_CLUSTER_CHECK ........................................................................................... 57 Figure 55: Check Result again -> No action needed ................................................................................... 57 Figure 56: SDBI_POOL_CHECK .................................................................................................................... 57 Figure 57: Runtime SDBI_POOL_CHECK ..................................................................................................... 58 Figure 58: Result SDBI_POOL_CHECK ......................................................................................................... 58 Figure 59: SDBI_CHECK_BCD_NUMBERS spool request ............................................................................ 58 Figure 60: Repair SDBI_CHECK_BCD_NUMBERS ........................................................................................ 58 Figure 61: Result of SDBI_CHECK_BCD_NUMBERS .................................................................................... 59 Figure 62: hdbsetup.exe ............................................................................................................................. 60 Figure 63: SAP HANA Lifecycle Management “Define Client Properties“ .................................................. 60 Figure 64: SAP HANA Lifecycle Management “Review and Confirm“ ........................................................ 61 Figure 65: SAP HANA Lifecycle Management “Install Software“ ............................................................... 61 Figure 66: SAP HANA Lifecycle Management “Finish“ ............................................................................... 62 Figure 67: new license ................................................................................................................................ 62 Figure 68: Disk space before Conversion ................................................................................................... 63 Figure 69: : SUM directory .......................................................................................................................... 64 Figure 70: HOST Agent Version .................................................................................................................. 64 Figure 71: JAVA Version.............................................................................................................................. 65 Figure 72: Registration of HOST AGENT ..................................................................................................... 65 Figure 73: enter the user name adm and the password.................................................................... 66 Figure 74: Stack.xml.................................................................................................................................... 68 Figure 75: Required System passwords ...................................................................................................... 68 Figure 76: SPAM Version Check.................................................................................................................. 69 Figure 77: Migration Parameters ............................................................................................................... 69 Figure 78: DMO may compare content of table rows ................................................................................ 70 Figure 79: Checks Information ................................................................................................................... 70 Figure 80: Tool Configuration ..................................................................................................................... 71 Figure 81: Parameters for procedure ......................................................................................................... 72 Figure 82: Target database client ............................................................................................................... 73 Figure 83: Required Migration Specific password ...................................................................................... 73 Figure 84: Database Migration Initialization .............................................................................................. 74 Figure 85: Required Migration Specific Passwords .................................................................................... 74 132


Figure 86: Required Migration Specific Passwords user DBACOCKPIT....................................................... 75 Figure 87: Required Migration Specific Passwords user SAPK00 ............................................................... 75 Figure 88: Language Update/Installation ................................................................................................... 76 Figure 89: Language Update/Installation Summary ................................................................................... 76 Figure 90: Missing Notes ............................................................................................................................ 77 Figure 91: Implemented SAP Notes............................................................................................................ 77 Figure 92: Release all TP's........................................................................................................................... 78 Figure 93: New archiving jobs and aging jobs will be blocked ................................................................... 78 Figure 94: Add-On Request Part I ............................................................................................................... 79 Figure 95: Add-On Request Part II .............................................................................................................. 79 Figure 96: COMPONENT Uninstallation Preparation POASBC 100_731 .................................................... 80 Figure 97: Select Support Packages You Want to Include .......................................................................... 80 Figure 98: Include Change Request ............................................................................................................ 82 Figure 99: Modification Adjustment .......................................................................................................... 82 Figure 100: Shadow Instance Numbers ...................................................................................................... 83 Figure 101: Backup Profiles ........................................................................................................................ 83 Figure 102: Delete Profiles ......................................................................................................................... 83 Figure 103: Shadow System Profiles .......................................................................................................... 84 Figure 104: Information Log after Configuration ....................................................................................... 84 Figure 105: Continue with roadmap step Checks....................................................................................... 84 Figure 106: Phase Checks ........................................................................................................................... 85 Figure 107: Save Variants ........................................................................................................................... 85 Figure 108: Parameters for BW-Specific reports ........................................................................................ 86 Figure 109: Start ASU ToolBox.................................................................................................................... 86 Figure 110: Continue with roadmap step "Preprocessing” ........................................................................ 87 Figure 111: : Preprocessing ........................................................................................................................ 87 Figure 112: Inactive Object found .............................................................................................................. 88 Figure 113: Lock Development Environment ............................................................................................. 89 Figure 114: Disk space Preprocessing 04-01-2017 11:55pm ...................................................................... 89 Figure 115: MAIN_SHDCRE/SHADOW_IMPORT_UPG1 "Deadlock" 04-01-2017 01:30 am ....................... 90 Figure 116: MAIN_SHDCRE/SHADOW_IMPORT_UPG1 repeat after deadlock .......................................... 91 Figure 117: Meantime 14-12-16 1:30 pm/05-01-17 09:05 am "Preprocessing" 33% ................................ 91 Figure 118: Repository Modifications Shadow Instance ............................................................................ 92 Figure 119: SE06 Shadow Instance "Modifiable" ....................................................................................... 92 Figure 120: SPAU Shadow Protocol ............................................................................................................ 93 Figure 121: SPDD with Assistant................................................................................................................. 93 Figure 122: SPAU Shadow 1610 ................................................................................................................. 93 Figure 123: SPDD without Assistant I ......................................................................................................... 94 Figure 124: SPDD without Assistant II ........................................................................................................ 94 Figure 125: Accept proposal of table SUPG_TEST_STRUCTURE ................................................................. 94 Figure 126: SPDD without Assistant III ....................................................................................................... 95 Figure 127: Accept proposel of table T130F_C........................................................................................... 95 Figure 128: SPDD without Assistant IV ....................................................................................................... 95 Figure 129: Edit Proposal of table T130F_C ............................................................................................... 96 133


Figure 130: Dictionary: Define Technical Settings of table T130F_C .......................................................... 96 Figure 131: Continue Proposal of table T130F_C ....................................................................................... 97 Figure 132: Modification completed .......................................................................................................... 97 Figure 133: RSEUPACTRL undocumented entry in the SPDD ..................................................................... 97 Figure 134: Start time 14-12-16 2:10 pm/ 05-01-17 10:53am "Preprocessing" 35%................................. 98 Figure 135: Meantime 14-12-16 4:45pm/05-01-17 1:35pm "Preprocessing" 43% ................................... 98 Figure 136: Meantime 14-12-16 5:50 pm/05-01-17 02:52pm "Preprocessing" 46% ................................ 99 Figure 137: Missing SAP Notes for Tools in Shadow System .................................................................... 100 Figure 138: SAPOSS RFC Password ........................................................................................................... 101 Figure 139: 14 notes implemented .......................................................................................................... 102 Figure 140: Perform Scale Up (Single Node) Prerequisite on SAP HANA if necessary ............................. 102 Figure 141: Provide partitioning for table MATDOC ................................................................................ 103 Figure 142: Preparations for Downtime ................................................................................................... 103 Figure 143: Backup Request ..................................................................................................................... 104 Figure 144: Disk Space before Downtime ................................................................................................ 104 Figure 145: HDB memory before Downtime ............................................................................................ 105 Figure 146: Log Mode HANA Studio "overwrite"Execution ..................................................................... 105 Figure 147: Continue with roadmap step "Execution" ............................................................................. 105 Figure 148: SUM ABAP process started Execution ................................................................................... 106 Figure 149: Error in phase MAIN_SWITCH/SUBMOD_MIG_SWITCH_NEW... .......................................... 106 Figure 150: Meantime -> 74% .................................................................................................................. 107 Figure 151: End of Downtime ................................................................................................................... 107 Figure 152: Continue with roadmap step "Postprocessing" .................................................................... 108 Figure 4-86: Post Prostprocessing ............................................................................................................ 108 Figure 154: Apply note 1908075 .............................................................................................................. 109 Figure 155: Procedure Complete.............................................................................................................. 110 Figure 156: Start of Cleanup Processing ................................................................................................... 110 Figure 157: Longpost.Log report 'VCH_MASS_MAINTENANCE' ............................................................... 111 Figure 158: Update complete ................................................................................................................... 111 Figure 159: Procedure Finished ................................................................................................................ 112 Figure 160: Confirmation.......................................................................................................................... 112 Figure 161: Close Browser ........................................................................................................................ 113 Figure 162: Close SAPup process .............................................................................................................. 114 Figure 163: SUM Summary Timeline Folder ............................................................................................. 114 Figure 164: Disk space Windows before Conversion ............................................................................... 116 Figure 165: Disk space Windows after Conversion .................................................................................. 117 Figure 166: HDB Memory and Disk space after Conversion..................................................................... 117 Figure 167: Analysis and Repair Tool for Views generated by HDB (TR hdbviews) ................................. 118 Figure 168: Generate Views ..................................................................................................................... 118 Figure 169: Result of generated HDBVIEWS............................................................................................. 118 Figure 170: S/4HANA Installed Software Components ............................................................................ 119 Figure 171: S/4HANA Installed Product Versions ..................................................................................... 119 Figure 172: Kernel after Conversion ......................................................................................................... 120 Figure 173: Get Hardware Key ................................................................................................................. 121 134


Figure 174: Install new License ................................................................................................................. 121 Figure 175: Permanent license key successfully installed ........................................................................ 121 Figure 176: SPAU after Conversion .......................................................................................................... 122 Figure 177: Again, needed notes .............................................................................................................. 122 Figure 178: Note actually not released .................................................................................................... 122 Figure 179: Confirm obsolete 88 notes .................................................................................................... 123 Figure 180: BTCTRNS2 .............................................................................................................................. 124 Figure 181: Stop SQL Server Instanz after Conversion ............................................................................. 125 Figure 182: Disabled SQL Services ............................................................................................................ 125 Figure 183: Job SGEN ................................................................................................................................ 126 Figure 184: SGEN Result I ......................................................................................................................... 126 Figure 185: SGEN Result II ........................................................................................................................ 126 Figure 186: Missing Tables and Indexes or views..................................................................................... 127 Figure 187: Create missing views on DB................................................................................................... 127 Figure 188: Mass processing for missing DB views .................................................................................. 127 Figure 189: Mass Processing within SE14................................................................................................. 128 Figure 190: schedule selections................................................................................................................ 128 Figure 191: Job of generated DB views .................................................................................................... 128 Figure 192: dbacockpit missing tables and indexes part II ....................................................................... 128 Figure 193: Installed New Notes after conversion ................................................................................... 129

© 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 http://www.sap.com/corporateen/legal/copyright/index.epx#trademark for additional trademark information and notices.

135

WP4 ACT 1610 Conversion S4HANA WSUM WIN Incl.dmo SP18 V1.10 Migration Do...

Recommend Documents