SAP SCM and LiveCache Upgrade Cookbook

8/11/2019 SAP SCM and LiveCache Upgrade Cookbook

http://slidepdf.com/reader/full/sap-scm-and-livecache-upgrade-cookbook 1/196

Sumitomo Chemical Asia

Upgrade Cookbook for SCM Production System11th November 2013



SCA – SCM 7.0 EHP2

Upgrade Cookbook SCM System

Date of Issue: 21/11/2013

2013 Sumitomo Chemical Asia - Confidential Page 2 of 196

Document Information

Document Title: SCA SCM 7.0 EHP2 – Upgrade Cookbook for SCM Production System

Document Purpose: The purpose of this document is to create a detailed SCM upgrade procedure.

To ensure the quality and track all issues coming up during the update, the

cookbook will also store the information like SAP Notes implementation toeliminate errors during the update. The detailed plan will also be the basis for

knowledge transfer between the parties SCA and IBM.

Document Owner

Author Position / Responsibility

AshishKumar S. Tak SAP Technical Upgrade Consultant, IBM

Change History

Version No. Date Changed Modified By Nature of Amendment

1.0 08-Nov-2013 AshishKumar S. Tak Initial document

1.1 11-Nov-2013 AshishKumar S. Tak Upgrade Step Amendments

File Management Details :

File Name : Sumitomo-SCM 7.0 - EHP2 Tech-UpgradeCookbook-S2P&S3P-PROD.PDF

File Location : \\10.30.11.12\SAP_Phase2\2013 Projects\SCM Upgrade\40 BASIS\

Approvals RecordApprover Title / Role Signature

SCA IT – Carine Chong SCA Basis

Reviewers Record

Approver Title / Role Signature

Prince Antony IBM Project Manager

Fujikawa Masaya SCA Project Manager

Document Distribution

Recipient Position / Responsibility

IBM Responsible / Accountable

SCA Informational







Table of Contents

1 Introduction ......................................................................................................................................... 8

2 Information Documents ...................................................................................................................... 9

3 Preparation and Requirements ........................................................................................................ 12

3.1 Determine Target Components ................................................................................................................................ 12

3.2 Supported & Minimum Source Releases ................................................................................................................... 14

3.3 Solution Manager – Upgrade XML Stack Preparation ................................................................................................. 14

3.4 SAP Software Update Manager [SUM] ...................................................................................................................... 21

3.5 Passwords .............................................................................................................................................................. 22

3.6 Configure OS User Authentication ............................................................................................................................ 23

3.7 Verify/Renew Maintenance Certificate (SLICENSE) .................................................................................................... 23 3.8 System in Modifiable State ................................................................................................................................... 23

3.9 OS Related Checks .................................................................................................................................................. 24

3.9.1 Hardware and Storage ............................................................................................................................................ 24

3.9.2 Check SUM Directory Disk Storage ........................................................................................................................... 30

3.9.3 Check Oracle Archive Log Directory Disk Storage ....................................................................................................... 30

3.9.4 Check SAP Transport Directory Disk Storage ............................................................................................................. 30

3.9.5 Check C++ version ................................................................................................................................................... 30

3.9.6 Check JDK version................................................................................................................................................... 31

3.9.7 Check OS MAXUPROC (refer to SAP Note 1048686) ................................................................................................... 31

3.9.8 Filling the Download Directory ................................................................................................................................. 32

3.9.9 Installing or Updating SAP Host Agent ...................................................................................................................... 32

3.10 Database Related Checks ......................................................................................................................................... 32

3.10.1 Check database shared_pool_size and shared_pool_reserved_size value .................................................................... 32

3.10.2 Database CHARACTERSET ........................................................................................................................................ 33

3.10.3 Check SAP database SAPSR3 privilege ....................................................................................................................... 33

3.10.4 Check database OPEN_CURSORS parameter ............................................................................................................. 34

3.10.5 Check DB for missing indexes (DB02) ........................................................................................................................ 34

3.10.6 Oracle Password ..................................................................................................................................................... 35

3.10.7 Update database statistics ....................................................................................................................................... 35

3.10.8 Check backup status (DB12) ..................................................................................................................................... 36

3.10.9 Database Size - Before ............................................................................................................................................. 37

3.11 SAP Related Checks ................................................................................................................................................. 37

3.11.1 Check SAP Default and Instance Profile ..................................................................................................................... 37

3.11.2 Extract and Check Software Update Manager ........................................................................................................... 38

3.11.3 Configure Transport System (where applicable) ........................................................................................................ 40

3.11.4 Check Central Syslog Parameter ............................................................................................................................... 40







3.11.5 Check Application Log (SLGN) .................................................................................................................................. 41

3.11.6 Verify No Entry in Table TBATG (SE16) ...................................................................................................................... 41

3.11.7 Verify Central Instance is defined in Background Process Group (SM61)...................................................................... 42

3.11.8 Verify Clean-ups Activities Status ............................................................................................................................. 42

3.11.9 Check SAP Basis User Access to All clients ................................................................................................................. 43

3.11.10 Update Latest SPAM version .................................................................................................................................... 43

3.11.11 Check Active ICF Services (SICF) ............................................................................................................................... 44

3.11.12 Clean up SAP Profiles .............................................................................................................................................. 44

3.11.13 Prepare the EPS/in directory .................................................................................................................................... 44

3.11.14 Verify Workflow Configuration (SWU3) .................................................................................................................... 44

3.11.15 Check for Open Transport Requests ......................................................................................................................... 44

3.11.16 Check TMW_ADM Table .......................................................................................................................................... 45

3.11.17 Check RSBASIDOC Table .......................................................................................................................................... 45

3.12 SCM Related Checks ................................................................................................................................................ 46

3.12.1 Stopping the CIF Queues ......................................................................................................................................... 46

3.12.2 Check LiveCache Connection.................................................................................................................................... 47

3.12.3 Livecache Upgrade Preparation - /SAPAPO/OM_LC_UPGRADE_70 ............................................................................. 48

3.12.4 Consistency Check of the LiveCache ......................................................................................................................... 49

3.12.5 Check the LiveCache Relevant Client ........................................................................................................................ 53

3.12.6 Adopting the Simulation Versions ............................................................................................................................ 53

3.12.7 Preparing the Upgrade and Update for Forecasting & Replenishment ......................................................................... 53

3.12.8 Planning the Upgrade of DP/SNP Macro Books .......................................................................................................... 54

3.12.9 Check Optimizer Status ........................................................................................................................................... 55

4 Start Uptime ...................................................................................................................................... 56

4.1 Uptime PART I ........................................................................................................................................................ 56

4.1.1 Manual Activities .................................................................................................................................................... 56

4.1.1.1 Check/Configure Operation Mode (RZ04) ................................................................................................................. 56

4.1.1.2 Check Additional SAP Notes ..................................................................................................................................... 57

4.1.1.3 Verify No Entry in Table TBATG (SE16) ...................................................................................................................... 57

4.1.1.4 Verify Clean Up Activities Status ............................................................................................................................... 58

4.1.1.5 Starting SUM Tool ................................................................................................................................................... 59

4.1.1.6 Starting the Installation GUI ..................................................................................................................................... 59

4.1.2 Initialization Phase .................................................................................................................................................. 60

4.1.3 Extraction Phase ..................................................................................................................................................... 65

4.1.4 Configuration Phase ................................................................................................................................................ 71

4.1.5 Check Phase ........................................................................................................................................................... 82

4.1.5.1 Live Cache Upgrade Preparation .............................................................................................................................. 83

4.1.6 Pre-processing Phase Part I ....................................................................................................................................104







4.1.6.1 End Uptime PART I ................................................................................................................................................109

4.1.6.2 SPDD Adjustment .................................................................................................................................................109

4.1.6.3 Start Uptime Part II ...............................................................................................................................................111

4.1.7 Pre-processing Phase Part II ...................................................................................................................................111

4.1.7.1 End Uptime Part II .................................................................................................................................................115

5 End Uptime ...................................................................................................................................... 116

6 Verify Backup .................................................................................................................................. 117

7 Start Downtime................................................................................................................................ 118

7.1 Start External Isolation ..........................................................................................................................................118

7.2 End External Isolation ............................................................................................................................................118

7.3 Start Internal Isolation ...........................................................................................................................................118

7.3.1 Suspend Batch Jobs (Program: BTCTRNS1) ..............................................................................................................118

7.3.2 Lock All SAP Users (refer to Project Plan) ................................................................................................................119

7.3.3 Stop Active Users’ Session (refer to Project Plan).....................................................................................................120

7.3.4 Disable RFC Destinations .......................................................................................................................................120

7.3.5 Disable SMTP Node and FAX (SCOT) .......................................................................................................................121

7.3.6 Disable Outbound Queue (Program: RSTRFCQ1)......................................................................................................121

7.3.7 Disable Inbound Queue (Program: RSTRFCI1) ..........................................................................................................122

7.3.8 Stop CCMS ...........................................................................................................................................................123

7.3.9 Stop Solution Manager Agent ................................................................................................................................123

7.3.10 Check and Stop All Active Batch Jobs (SM37/SM66) .................................................................................................123

7.3.11 Check and Clear Update Requests (SM13) ...............................................................................................................124

7.3.12 Check and Clear Lock Entries (SM12) ......................................................................................................................124

7.3.13 Check and Clear Mass Processing (SE14) .................................................................................................................125

7.3.14 Check and Clear Outbound Queue (SMQ1) .............................................................................................................125

7.3.15 Check and Clear Inbound Queue (SMQ2) ................................................................................................................126

7.3.16 Check for unprocessed logistics extraction data (Program: RMCEXCHK) ....................................................................126

7.3.17 Check and Stop Active User Session (AL08/SM04) ...................................................................................................128

7.3.18 Disable Database Backup Job .................................................................................................................................128

7.3.19 Shutdown SAP Application Servers (stopsap) ..........................................................................................................128

7.3.20 High Availability ....................................................................................................................................................128

7.3.21 High Availability (Disable HA Clustering Process) .....................................................................................................129

7.4 End Internal Isolation ............................................................................................................................................129

7.5 Start Technical Downtime ......................................................................................................................................129

7.5.1 Define Central Instance Server in SM61 (Productive System Only) ............................................................................129

7.5.2 Pre-processing Phase Part III – [Live Cache Upgrade Section B] .................................................................................129

7.6 Execution (Downtime) Phase .................................................................................................................................140

7.7 Post-Processing Phase ...........................................................................................................................................162







7.8 Finalization Phase .................................................................................................................................................166

7.9 End Technical Downtime .......................................................................................................................................168

7.10 Follow-up Activities ...............................................................................................................................................168

7.10.1 Generating Loads (SGEN) .......................................................................................................................................168

7.10.2 Update Oracle statistics .........................................................................................................................................170

7.10.3 Check Oracle database archive log mode enabled ...................................................................................................171

7.10.4 Enable ICF Services (SICF) ......................................................................................................................................171

7.10.5 Replace new kernel in dialog instances and verify kernel version ..............................................................................172

7.10.6 Execute SAPDBA_ROLE.SQL ...................................................................................................................................172

7.10.7 Follow-Up Activities for User root ..........................................................................................................................172

7.10.8 Install SAPHOSTAGENT ..........................................................................................................................................173

7.10.9 Verify updated SAP component version ..................................................................................................................175

7.10.10 Verify Kernel/IGS/BRTOOLS/DBSL Version ..............................................................................................................175

7.10.11 Verify Workflow Configuration (SWU3) ..................................................................................................................175

7.10.12 Clear the Shadow system details from Secure Storage .............................................................................................176

7.11 High Availability – Only for Production System ........................................................................................................176

7.12 SPAU Adjustment..................................................................................................................................................176

7.13 Start De-Isolation ..................................................................................................................................................177

7.13.1 Prior to LiveCache Upgrade ...................................................................................................................................177

7.13.2 System Sanity Checks (in parallel with SPAU) ..........................................................................................................177

7.13.3 Verify SAP startsap and stopsap scripts ...................................................................................................................178

7.13.4 SAP HA Cluster Failover Test (Productive System Only) ............................................................................................178

7.13.5 Start SAP Host Agent .............................................................................................................................................178

7.13.6 Start Solution Manager Agent ................................................................................................................................179

7.14 End De-Isolation (Internal – ERP) ............................................................................................................................179

7.15 Backup .................................................................................................................................................................179

7.16 De-Isolation (External) ...........................................................................................................................................179

7.16.1 Enable Inbound Queue (Program: RSTRFCI3) ...........................................................................................................179

7.16.2 Enable Outbound Queue (Program: RSTRFCQ3) ......................................................................................................180

7.16.3 Enable Node for SMTP (SCOT) ................................................................................................................................181

7.16.4 Restart Batch Jobs (Program: BTCTRNS2) ................................................................................................................182

7.16.5 Implementation of SSFS Mode for Oracle ...............................................................................................................182

7.16.6 Enable Backup Job (OS cronjob) .............................................................................................................................182

7.17 Unlock Business Users Account (refer to Project Plan) .............................................................................................182

8 End Downtime ................................................................................................................................. 183

9 Appendix A (Errors Resolution or Manual Tasks or Additional Information) ............................. 184

9.1 Initialization Phase ................................................................................................................................................184

9.2 Extraction Phase ...................................................................................................................................................184







9.3 Configuration Phase ..............................................................................................................................................184

9.4 Checks Phase ........................................................................................................................................................184

9.5 Pre-processing Phase ............................................................................................................................................184

9.6 Downtime Phase ...................................................................................................................................................184

9.7 Post-processing Phase ...........................................................................................................................................184

9.8 Finalization Phase .................................................................................................................................................184

9.9 OSS Messages Raised ............................................................................................................................................184

9.10 Post Upgrade Error & Solutions ..............................................................................................................................184

9.11 List of Transports for Production ............................................................................................................................195

9.12 Unlock of Production Users ...................................................................................................................................196







1 Introduction

The focus of this initiative is to update & upgrade the SCM Landscape in Sumitomo Chemical Asia. The SCM

landscape is connected to ECC environment in SCA landscape wherein ECC landscape is on SAP ECC 6.0. Also SCM

Landscape in Sumitomo is connected to LES [Logistics Execution System – Product of Microsoft Navision]. Amongthese systems, SAP SCM which needs to be upgrade from the version SCM 5.0 to SAP SCM 7.0 EHP2 & Live Cache

7.6 to 7.9.

This document represents the certain situation, strategy and procedure of the SAP SCM upgrade process. It also

includes the upgrade additional SAP SCM components viz., as SAP LiveCache.

The overall process including errors captured which can be used for future SCM Upgrade. Beside error capturing, this

document can be used to optimize long running process or potential errors. The final upgrade will be based on the

completion of the Production SCM 7.0 EHP2 Upgrade.







2 Information Documents

Master Guide for SAP EHP2 for SCM 7.0:

http://service.sap.com/instguides

Installation & Upgrade Guides SAP Business Suite Applications SAP SCM SAP SCM Server

Using SAP enhancement package 2 for SAP SCM 7.0 Server Master Guide

o Master Guide for SAP EHP2 for SCM 7.0

Upgrade Guide for SAP SCM:



Using SAP enhancement package 2 for SAP SCM 7.0 Server Upgrade Guides Upgrade

and Update Guides for SAP EHP2 for SAP SCM 7.0 SAP SCM 7.0 EHP 2 Upgrade and Update

Guide

o Upgrade and Update Guides for SAP EHP2 for SAP SCM 7.0

Update of SAP Systems Using Software Update Manager:




and Update Guides for SAP EHP2 for SAP SCM 7.0 Software Update Manager Guides

Update of SAP Systems Using Software Update Manager (ABAP Systems) UNIX/Oracle

o Update of SAP Systems Using Software Update Manager 1.0 SP08

Upgrade Guide for SAP LiveCache:




and Update Guides for SAP EHP2 for SAP SCM 7.0

o Upgrade : SAP liveCache for SAP SCM 7.0 EHP 2 on UNIX

Media List:



Using SAP enhancement package 2 for SAP SCM 7.0 Server Media List

o Media List for SAP EHP 2 for SCM 7.0

SAP Notes:

http://service.sap.com/notes

























SAP Notes for pre-checks, issues and error solutions and root cause. It is strongly recommend to check for the latest

version and read the below notes before starting the SCM upgrade.

If there is any change in the Oracle version (e.g. Upgrade to Oracle 11g), please check for latest relevant notes and

add them to the below list.

SAP Notes for Preparing the SCM Upgrade and Update

SAP Note

NumberShort description

Version of

SAP Note

1497083 EHP2 for SAP SCM 7.0 SP stacks - Release & Information Note 21

850038 Support Package levels for SCM/APO installations/upgrades 23

1567308 Requirements for the upgrade to SCM 7.02 (SCM 7.0 EHP2) 4

1566982 Additional information about upgrading to SAP liveCache 7.9 10

1334357 SCM Java components handling by the upgrade program 17

1684429 /SAPAPO/OM_LC_UPGRADE_70: Problems during SCM 7.02 upgrade 8

Other SCM-Specific SAP Notes

SAP Note


Version of

SAP Note

1539087 Removal of ABAP program variants from TCT process chains 4

844745 Upgrade to SCM 5.0 requires the deletion of WFM Core 1

1656160 Note 1250862 - Enhancements to upgrade SCM F&R, Release 7.0 and higher 9

1250862 Enhancements to upgrade SCM F&R, Release 7.0 and higher 3

1178483 SNC 7.0 Order Documents: Required Customizing 5

915367 TDL: Automatic activation of the transaction data areas 5

865333 Upgrade SCM 5.0: Upgrade assistant for macro books 4

865334 Upgrade SCM 5.0: Macros in DP and SNP 1

505304 Disk space for Core interface communication 5

210919 Collective note: Logical system names 1

568289 Information about the /SAPAPO/MC01_CACL_FROM_R3 report 13428102 Performance: Loading planning area version 5

707828 Switching from old to new TLB planning 1

1833931 POS deactivation by SCM SNC upgrade (POS 9AINVM1, 9ADFC01) 2

1827492 Data loss during SCM SNC upgrade (POS 9AINVM1, 9ADFC01) 2. 1

1798981 Data loss during SCM SNC upgrade (POS 9AINVM1, 9ADFC01) 2

1783090 Deleting an appset based on MultiProvider from BPC dumps 8

1868809 SCM upgrade job terminates with message RSDODSO 207 4

1847922 Termination DBIF_RSQL_INVALID_RSQL when you activate content 3

1169790 SAP SNC 7.0x: Steps After Upgrade 5







SAP Notes for SAP liveCache

SAP Note


Version of

SAP Note

1529690 Importing SAP liveCache Version 7.9 7

833216 Parameter values as of liveCache Versions 7.5, 7.6 and 7.7 41

1567117 Parameter values for SAP liveCache Version 7.9 2

337445 liveCache and memory management 20

487972 Operating system parameterization of liveCache 57

SAP Notes related to the SUM and Upgrade Process

SAP Note


Version of

SAP Note

1790828 Central Software Update Manager Note 18

1843966 Oracle: Add. Information – Software Update Manager 1.0 SP08 1

554031 Creating space statistics with BRCONNECT 25

485741 Handling customer translations during the upgrade 15

669902 Setting the national character set to UTF8 34

556764 Upgrade hangs in phase ACT_<REL> 12

11777 ORA-1632 max # extents <n> reached in index <ind.> 71678780 Installation or upgrade of BI_CONT/BI_CONT_XT 7x7 44







3 Preparation and Requirements

All checks need to be done before starting the upgrade and ensure the quality of the SCM updates are mentioned in

this section.

This part of the document contains information about the preparation that need to make before starting the SCM

upgrade.

Careful preparation is the best guarantee that it runs without errors!

3.1 Determine Target Components

Below stats the support package level of current and the target components as agreed by the management.

Source Software Components for SCM 5.0 Production System – S2P







Source Kernel version for SCM 5.0 Production System – S2P

Source Database Version & Release for SCM Production System – S2P

Source Operating System Version & Release for SCM Production & Live Cache Production Hosts







3.2 Supported & Minimum Source Releases

This section provides an overview of the supported upgrade and update paths for SAP Supply Chain Management(SAP SCM) to SAP Enhancement Package 2 for SAP SCM.

Before the upgrade, the SAP system must have one of the source releases that have been released for this upgrade

and apply to all databases.

SCM/LC Minimum Requirements Prior SCM 7.0 EHP2 Upgrade

Software

Components

S/W Components

ReleaseSP Level

S/W Components

ReleaseSP Level

BI_CONT 703 2 703 2

EA-IPPE 400 8 400 10

LCAPPS 2005_700 1 2005_700 5PI_BASIS 2006_1_700 1 2006_1_700 2

QIE 200 4 200 4

SAP_ABA 700 12 700 19

SAP_AP 700 10 700 10

SAP_BASIS 700 12 700 19

SAP_BW 700 12 700 15

SCM 500 1 500 11

SCM_BASIS 500 3 500 11

ST-A/PI - - 01P_700 0

ST-PI 2005_1_700 6 2008_1_700 6LIVECACHE 7.6.00 - 7.6.03 BUILD 008-123-159-187

All components are respecting the minimum level required.

3.3 Solution Manager – Upgrade XML Stack Preparation

SAP Solution Manager plays a central role in the SCM upgrade process. The maintenance Optimizer of SAP Solution

Manager must be used in order to calculate a system-dependent stack of software components to be installed in thetarget system. Therefore SAP Solution Manager Support Packages level must meet the minimum requirement of at

least SP23 and ST-ICO 150_700 SP 25. Beside this requirement, the setup of solution manager must be done

correctly and contains the up-to-date information of its satellite systems. Information like the software components

and the correct patch level are utmost important.

After confirming the target version of the SAP software components to be updated, download the software and the

important stack file.

Create a Maintenance Transaction in Solution Manger System to Generate XML file for Upgrade:







Select Solution Sumitomo Development & Product Version SAP SCM 5.0 with Product System as SCM 5.0

Development System – S2P & Continue [Project Landscape system[P2D] is not configured in Solution Manager so the

XML file need to be changed as per the project system with the change and replace of Hostname & SID ]

Note: Also the same XML will be continued for subsequent upgrade by replacing the Hostname / SID & Instance

Number







Select Calculate the Files Automatically

Select Upgrade with EHP Installation & Continue







Select Live Cache & SCM [SCM Optimizer is not in SCA Landscape] & Continue

Click Continue







Select if any additional Add-On required [SCA landscape there is no additional Add-On required]







Select the Kernel Files / LiveCache / Hostagent / SUM & IGS Files

Select the SPAM Update for the upgrade process & Continue







Continue with the Default selected components from MPOZ for Upgrade.







Stack delta file SMSDXML_S2P_20130813045452.881.txt exported to EPS inbox

/usr/sap/transSC3/EPS/in.

Stack delta file SMSDXML_S2P_20130813045452.881.xml exported to EPS inbox

/usr/sap/transSC3/EPS/in.

131 file(s) are pushed into download basket successfully.

Stack XML File generated for the Upgrade process

3.4 SAP Software Update Manager [SUM]

Please ensure the latest SUM 1.0 software and the correct version is downloaded from SAP service market place. The

path to download is as follows

http://service.sap.com/sltoolset

Software Logistics Toolset 1.0 table with the Software Logistics tools Software Update Manager 1.0

SP08 Download Link










3.5 Passwords

Ensure that the password for the following IDs are available. Logon with the IDs’ password and ensure that they are

correct.

DDIC (All clients ) [DDIC for Client 000 is Mandatorily required]

<sid>adm (SAP OS user ID)*

ora<sid> (Oracle OS user ID)

system (Oracle database user ID)**

control (LiveCache DB Admin User ID)

ibm (OS User ID for Basis Admin to SU)

sap<sid> (DB Schema Password)

root (OS user ID)* this is needed to run command to set the kernel. If this is not available due to

security reason, will have to provide the command syntax to the administrator to execute it.

*<SID>adm password has to be MANDATORY acquired and set to interactive in the production system. As a good

practice, acquire the password for the other systems before starting the update.

**ONLY for Oracle 11g system user password. When you test the system password, the below screen may appear.

Please check that it is valid and not ‘expired (grace)’ status. This is an additional security feature incorporated in

Oracle 11g.

The Oracle system user is assigned the DEFAULT profile with PASSWORD_LIFE_TIME set as 180 days. In older Oracle

version, this is set as unlimited.

SQL Command:

select * from dba_sys_privs where grantee = 'SAPSR3';







Solution:

To change the parameter, logon as ora<sid> and execute SQLPLUS.

alter profile default limit password_life_time unlimited;

If at all require you can reset the password of system by the command as below:

alter user system identified by password ;

(You can reset it to your old password provided that the password policy allows you to change to the same

password)

Login to user system again

3.6 Configure OS User Authentication

To ensure that the user authentication used by SUM is working and the restart operations during the update are

successful, you must configure the OS user authentication correctly before starting SUM.

If applicable Apply SAP Note 927637 and the OS-specific SAP Notes attached to it.

3.7 Verify/Renew Maintenance Certificate (SLICENSE)

Before you update the SPAM, please verify that the maintenance certificate is not expired. If it has expired, go to SAP

Service Market and download the maintenance certificate and install it using transaction code SLICENSE. i.e.,

http://service.sap.com/licensekey

3.8 System in Modifiable State

You are required to seek approval to open SAP system during UPTIME Phase in order to download SAP Notes

including obsolete notes. This is necessary as the SUM tool will not advance further until all SAP notes are

downloaded and applied either manually or transports.

To download SAP notes, you will have to use transaction code SE06 to open the SAP system.










Click System Change Option

3.9 OS Related Checks

3.9.1 Hardware and Storage

CPU, Main Memory, Disk and Swap Space

A]. SCM ABAP System :- S2P

Command: lparstat –i







Command: vmstat 2 10







Command: iostat 2 1

Command: df –gt

Modify /etc/security/limits file to adopt -1 for both SCM ABAP & LiveCache Production system respectively.







B]. SCM LiveCache System :- S3P

Command: lparstat –i







Command: vmstat 2 10

Command: iostat 2 1







Command: df –gt

Important Storage requirements for Release Upgrade Activity

Disk space for Free spacerequirement

Location Remarks

SUM Directory 40 - 50 GB /usr/sap/<SID>/SUM Any other directories are OK

except for database data

directories

S/W download

Directory

30 – 40 GB /misc Directory to store the SCM 7.0

EHP2 software

Extraction Directory

(DIR_TRANS)

20 – 30 GB /usr/sap/trans Extracted SCM 7.0 EHP2 software

Shadow Instance

Directory

50 – 100 GB /usr/sap/<SID>/SUM For NW 731, the Tablespace name

will be PSAPSR3731and free spacedependent on current DB size

Free Space in 50 – 80 GB /oracle/<SID>/sapdata1 Make Sure the File System has







Directory /oracle/<SID>/sapdata2

/oracle/<SID>/sapdata3

/oracle/<SID>/sapdata4

enough space for Tablespaces to

grow automatically and use the

free space in the Filesystem

Database Archive

Directory

30 – 75 GB /oracle/<SID>/oraarch Free space needed during Uptime

phase and free space dependenton current DB size

The SAP system has been disconnected from the global transport system. The transport system will be

reconfigured to include a virtual system as the target system for transportable transport requests.

3.9.2 Check SUM Directory Disk Storage

The directory to install the Software Update Manager is in /usr/sap/<SID>/SUM (for production, /usr/sap/<SID> is

not mounted as a file system and we can use /oracle/<SID>/oraarch or /usr/sap instead). Please ensure that the disk

storage has sufficient free space of at least 40-50 GB. If free space is not available in the mentioned directory, you

can still install the Software Update Manager in another directory BUT do not use database directory.

The other directory is /tmp and please ensure that there is free disk storage of at least 2 - 5GB.

3.9.3 Check Oracle Archive Log Directory Disk Storage

In the uptime phase especially during the shadow instance table/indexes creation and copying of data, there will be

lots of archive logs generated. Please ensure that there is enough free storage to accommodate both the normal

activities from business users and uptime activities from SUM tools.

3.9.4 Check SAP Transport Directory Disk Storage

Check if there are entries in /usr/sap/trans/bin/umodauto.lstand If there are, please rename the umodauto.lst file.

This is necessary as the SUM tool will put the transport entries into the update transport.

3.9.5 Check C++ version

Command: lslpp -L xlC.aix61.rte







The output must be at least 10.1.0.0. OK

Production SCM ABAP System – S2P

Production SCM LiveCache System – S3P

3.9.6 Check JDK version

Command: su – s2padm

java -version


It is OK if you have a higher java version than the above screen.

3.9.7 Check OS MAXUPROC (refer to SAP Note 1048686)

Command : lsattr -E -l sys0|grep max


Production SCM LiveCache System – S3P











If this entry does not exist, execute the below SQLPLUS statement:

Command:

grant unlimited tablespace to saspr3;

3.10.4 Check database OPEN_CURSORS parameter

Increase the OPEN_CURSORS Parameter

To avoid the error "ORA-01000: maximum open cursors exceeded" during the update/upgrade, we recommend that

before starting the update/upgrade, you increase the OPEN_CURSORS parameter value to 20000 with the following

Command:

alter system set open_cursors = 20000 scope=both;

show parameter open_cursors;

3.10.5 Check DB for missing indexes (DB02)

We will need to capture the screenshot for in DB02 for any missing indexes before we start the update. Any missing

indexes appear in the screenshot will need to be sent to functional team to verify.

T-code: - DBACOCKPIT

Check Oracle Client







3.10.6 Oracle Password

Do not use the '@' character in your database passwords, as the Software Update Manager cannot handle the

passwords then.

3.10.7 Update database statistics

Make sure that the statistics are up-to-date for all tables. Out-of-date statistics can increase the runtime of the

support packages update significantly.

From the below screenshot, the update statistics is also scheduled as a background job program in SM36 to run

successful on every day at 20:00hrs for around 8 days before the actual upgrade activities.

It is recommended to run the full statistics again a day or 2 before the upgrade with the below command logon as

ora<SID>:

Command:

su – oras2p

brconnect -u / -c -f stats -t oradict_stats







brconnect -u / -c -f stats -t system_stats

brconnect -c -u / -f stats -t all -f collect -p 16

Calculate the space statistics before the upgrade/update in order to have correct space calculations.

(SAP Note 1843966)

brconnect -u / -c -f stats -t all -m +I -s P1 -f allsel,collect,method,precision -p 4 -o SAPSR3

3.10.8 Check backup status (DB12)

From the DB12 screen, the backup completed successfully. If there is no successful backup, start a backup. Make

sure there is one or two good backup copy available always and all the archive logs also verify the backup status of

each backup taken timely throughout the upgrade activity. Successful Backup will be easier and safe to bring back

the system back to the point in time.

T-Code: DB12







3.10.9 Database Size - Before

Overall DB size and the space occupied by each Tablespace in the Database prior to upgrade.

3.11 SAP Related Checks

3.11.1 Check SAP Default and Instance Profile

Check the value for the following parameters.

Profiles:

DEFAULT.PFL

1) rdisp/mshost hostname

INSTANCE Profile -

1) rdisp/wp_no_vb > 02) rdisp/wp_no_vb2 > 0

This parameter contains the host name where the message server is running. It must run on the same host as the

central instance. This makes sure that the message server is active during downtime, because only the central

instance runs during downtime, while the dialog instances are stopped. 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 central instance. The number must be greater than 0.







3.11.2 Extract and Check Software Update Manager

To ensure that the Software Update Manager tool can execute without any errors, you can extract the software andexecute the tool.

It is normally recommended to extract the SUM tool in /usr/sap/SID

For production system due to /usr/sap/<SID>/ which is not mounted as a file system, we will put the SAR file in

/oracle/<SID>/oraarch or either /usr/sap file system and SAPCAR the SUM software. Please use /usr/sap/<SID> if

possible.

Command:

su – s2padm

/sapmnt/S2P/exe/SAPCAR -xvf /misc/UpgradeDump/SUM10SP08_4-20006540.SAR

Extract the SUM tool in the path /usr/sap/S2P/

Start the SUM service, login with <sid>adm

Command:

su – s2padmcd /usr/sap/S2P/SUM

./STARTUP &









3.11.3 Configure Transport System (where applicable)

After the SAP system has been taken out from the transport landscape, it is now a standalone system. It is importantto configure the transport landscape so that transport can be generated. Once it is placed back into the system

landscape, you will need to setup according to the initial configuration.

You will need to reconfigure the transport landscape.

For production, the transport landscape will not be reconfigured. Any SPAU adjustments that need to be performed

will be done in Quality Upgrade and transported to production.

3.11.4 Check Central Syslog Parameter

Parameter for the Central syslog rslg/collect*

There may be conflicts with parameter values for the central syslog “rslg/collect*” of the default profile.

If the parameters are set with 39<no.> or 40<no.>, you must change them to 14<no.> or 15<no.>. Make sure thatthe ports are not used by other applications. If so, choose some other number. For more information, please refer to

SAP note 1069225.

Check the parameter using T-Code RZ11







3.11.5 Check Application Log (SLGN)

Check the application as stated in SAP Note 196113 to ensure no runtime error for table BALHDR. Cross check the

values in SLGN and table BALHDR and ensure that the value in SLGN is greater than value in BALHDR table.

T-Code: SLGN

T-Code: SE16 table BALHDR

The last record in table BALHDR must not be greater than the current value in SLGN.

3.11.6 Verify No Entry in Table TBATG (SE16)

Please check and ensure that there is no entry in table TBATG. The TBATG table should be empty to ensure that

there is no error during DB conversion. If there are entries in the table, please ensure that they are rectified or

processed.

T-Code: SE16 Table TBATG







3.11.7 Verify Central Instance is defined in Background Process Group (SM61)

**** Applicable only for Production system ****

In productive environment, background jobs will only run on dialog instances and not on the central instance. This is

controlled by setting the background process group in SM61.During the update, we will only run the SUM on the central instance. Please verify if the central instance server is

defined in SM61 (background processing group). If it is not, you will need to define the central instance server before

the SUM Downtime Phase.

Click on Job Server Groups

3.11.8 Verify Clean-ups Activities Status

Any outdated entries output from the below transaction code will have to be sent to Team for their verification.

T-Code: SM12







T-Code: SM13

T-Code: SMQ1

T-Code: SMQ2

3.11.9 Check SAP Basis User Access to All clients

This task will have to be done by IBM. Please check, verify and ensure that you have access to all the clients in thesystem. This is for client clean up (example SMQ1 and SMQ2).

3.11.10 Update Latest SPAM version

SPAM version is already at the latest and no update is necessary.







3.11.11 Check Active ICF Services (SICF)

Use transaction code SICF to check for current activated services in the system.

This is to ensure that the services are active after the update. If not, we will have to activate the services after the

update.T-Code: SICF

3.11.12 Clean up SAP Profiles

You will need to clean up the SAP profile directory where only the required files are to be resided. Please remove any

backup or unwanted profiles.

3.11.13 Prepare the EPS/in directory

Copy all the downloaded SAP target software component files from the software repository into the /usr/sap/trans

directory and extract them into EPS/in directory.

3.11.14 Verify Workflow Configuration (SWU3)

***** Not Applicable in Sumitomo Case *****

3.11.15 Check for Open Transport Requests







This task is not an accurate check on the open repair transports existing in the current SAP system because these

open repairs need to be compared with SAP delivery patches (to be installed) which is done by SUM tool. It will

provide a rough estimation which transports are likely to be released.

You will have to check SE03 -> Display repaired object

Check the table TLOCK in T-Code SE16 and list out the transport number and user. Verify the transports that can be

released and release them.

3.11.16 Check TMW_ADM Table

This check is to ensure that the project locking is deactivated. If the field CID_ACTIVE is ‘active’, Application team will

have problem when performing adjustment during SPAU phase.

T-Code: SE16

**PLEASE TAKE NOTE AND PERFORM THE BELOW IF THE ENTRY RETURN IS NOT ZERO**

Example:-

If CID_ACTIVE = ‘X’, execute the program TMW_CONTROL_PROJECT_LOCK in TCODE SE38.

3.11.17 Check RSBASIDOC Table

This check is to ensure that there is no entry ‘M’ for field SRCTYPE in table RSBASIDOC. If the entry is there, the

deletion will be performed after upgrade in the follow-up activity.

T-Code: SE16 Table RSBASIDOC







3.12 SCM Related Checks

3.12.1 Stopping the CIF Queues

Before performing a database backup later, we need to stop the CIF queues in the SAP SCM system to ensure a

consistent recovery state.

To determine whether you are using inbound or outbound queues, call transaction CFC1 in the connected ERP

systems and transaction /n/sapapo/c2 in the SAP SCM system.

ERP System: Transaction Code: CFC1

Stop Inbound and Outbound Queues

SCM System: Transaction Code: /n/sapapo/c2

Stop Inbound and Outbound Queues

To stop the queues, use the following reports in the SAP SCM system and all ERP systems connected, according to

the queue type you are using:

For outbound queues, use report RSTRFCQ1

Enter the following values:

Parameter QNAME: CF*

Parameter Dest: <Name of Logical System of receiving system>

Parameter FORCE: <no entry required>

For inbound queues, use report RSTRFCI1

Enter the following values

Parameter QNAME: CF

Parameter FORCE: <no entry required>

Check the queue Manager

T-Code: /n/SAPAPO/CQ









3.12.3 Livecache Upgrade Preparation - /SAPAPO/OM_LC_UPGRADE_70

To upgrade the SAP liveCache, we have to perform a number of activities before, during, and after the upgrade of

the SAP system. Therefore, one of the main activities is to download the transactional data before the SAP liveCache

upgrade and upload the data before production operation resumes.

Report /SAPAPO/OM_LC_UPGRADE_70 lists all actions necessary to perform the upgrade. Note that program

/SAPAPO/OM_LC_UPGRADE_70 is part of the tool import of the upgrade, so you won’t find it, before having started

Upgrade. The activities are grouped in sections according to when they have to be performed:

This section is based on the SAP Note 1684429 - /SAPAPO/OM_LC_UPGRADE_70: Problems during SCM 7.02

upgrade, which give the steps and SAP notes to apply prior/during the upgrade of the LiveCache.

The notes specified below

Correct various problems that may occur when you upgrade from 4.1, 5.0, or 5.1 to SCM 7.02, or more

precisely, when you download or upload liveCache data.

Allow SAP to analyze errors more efficiently.

And provide additional checks that stabilize the uploading process.

SAP Note


Version of

SAP Note



1809553 Enhancements and system message for SAP Note 1809508

1809508 Model consistency check: Resource location and timezone 2

1801860 /SAPAPO/OM_UPGR_TSTR_CHECK: Correction of SAP Note 1

1800707 New system messages for model consistency check 1

1566046 Note 1566046 - New check in /sapapo/om_check_activities (error 199) 3

1562495 New check in /sapapo/om_check_activities... 3

1548130 Test on cycle with internal constraints

1485051 New check in /sapapo/om_check_activities...

1457064 Usability: SNP time series reorganization

1351213 New check in /sapapo/om_check_activities...

1297605 New check in /SAPAPO/OM_CHECK_ACTIVITIES

1257293 Notes regarding resource time stream, relevant for upgrade

899108 The PAL correction doesn't run in /SAPAPO/OM17 trans. 4

1389914 Update program version in different report in allocations 14

1574075 OM17: Assignments outside parea validity shouldnt be checked 61825133 An error /SAPAPO/OM_SYNC001 in liveCache consistency check 2

1742772 /SAPAPO/OM17 does not check for shipments missing in LC 1







1031487 Incomplete liveCache consistency check for resources 2

1299949 Error in Resource live Cache consistency check 2

1457097 /SAPAPO/OM17: Error cannot be corrected 1

3.12.4 Consistency Check of the LiveCache

T-Code: /n/SAPAPO/OM17

Consistency Check













Click on













3.12.5 Check the LiveCache Relevant Client

Ensure that the client that contains the SAP liveCache data has not been marked as “not relevant for liveCache”.

T-Code: SE38 /SAPAPO/OM_NON_LC_RELEVANT_CLT

3.12.6 Adopting the Simulation Versions

The upgrade does not keep simulation versions. If you do not want to lose the changes stored in certain simulation

versions, you must adopt them into the corresponding planning version before the upgrade.

It is advisable to inform the owners of any existing simulation versions about the imminent upgrade, so that they can

decide which saved simulation versions should be transferred to the plan version and which saved simulationversions are obsolete and can therefore be deleted (this is technically possible, but not necessary because the

upgrade ignores simulation versions anyway).

Follow instruction in SAP Note 977644 - SCM/APO upgrade does not transfer any simulation versions:

T-Code: /n /SAPAPO/CDPSS0

If there is, select and click on

3.12.7 Preparing the Upgrade and Update for Forecasting & Replenishment

****** Not Applicable in Sumitomo ******

Check with SCM Functional is they are using the scenario.







If yes, make a backup the data storage folder of Forecasting & Replenishment (F&R) before the upgrade or update.

You then have to save it to the new folders after the upgrade, and run a report to convert the data.

Back up all FRP data separated by FRP server and FRP server group.

3.12.8 Planning the Upgrade of DP/SNP Macro Books


As of SAP SCM 5.0, Demand Planning (DP) and Supply Network Planning (SNP) contain new functions that make it

necessary to introduce developments in the macro definition logic that are incompatible with existing macro

definitions. This applies, for example, to distinguishing 0 and initial values in Interactive Planning.

To allow a smooth upgrade without the need for interaction during the upgrade process, SAP has introduced a

compatibility mode for existing macro books. The Software Update Manager automatically enables the compatibility

mode during the upgrade process for each macro book, thus allowing you to execute macros after the upgrade that

you defined in previous releases. No manual interaction is necessary during the upgrade process.

The report /sapapo/adv_upgrade_50 should be used for analysis purpose and will list the necessary adjustmentsthat need to be made to the macros after upgrade. More about this report can be found in the path mentioned in

the note 1452276.

Compatibility mode of the macrobook can be checked via //advm -> dataview -> menu -> edit -> book information

compatibility mode of macro book. This check allows identifying the macros to be modified.

We also recommend deactivating the compatibility mode after you have upgraded so that you can also benefit from

the new macro functions.

If you have set the compatibility mode for the macro book data view and executed the report. It would have

shown the necessary modification required.

T-Code: SE38 /SAPAPO/ADV_UPGRADE_50

Click on







Everything is checked.

3.12.9 Check Optimizer Status


T-Code: /n/SAPAPO/OPT09







4 Start Uptime

4.1 Uptime PART I

4.1.1 Manual Activities

4.1.1.1 Check/Configure Operation Mode (RZ04)

Call transaction RZ04 to check the definition of your operation modes. Delete the invalid operation modes in case if

it exists. If operation mode contains 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 serverand triggered by an event).

If the SAP instance on which you want to update EHP2 is not entered in an operation mode, create the operation

mode for the installation as follows:

Call transaction RZ04 -> Choose Operation mode Create -> Enter a name for the operation mode, for example:

“EHP2” -> enter a short description and then save the operation mode.

Make sure that the instance required for the installation has been started up. Position the cursor on the new

operation mode and choose Operation mode Maintain instances -> Instances/OP modes -> Choose Settings based on

act. Status New Instances Create. This displays all instances and their current configuration -> Choose Save.

Call transaction SM63 to enter the operation mode you have defined as an active operation mode for 24hours

(select Normal operation (24 hours)).

T-Code: RZ04

T-Code: SM63









4.1.1.4 Verify Clean Up Activities Status

If any outdated entries output from the below transaction code will have to be sent to Functional Team for their

verification.T-Code: SM12

T-Code: SM13

T-Code: SMQ1

T-Code: SMQ2







4.1.1.5 Starting SUM Tool

The installation tool was already extracted and tested in preparation phase and now you will need to execute thetool before starting the Uptime.

To start the installation program (in background), login as <SID>adm i.e., S2Padm and enter the command

Command:

su – s2padm

cd /<SUM_DIRECTORY>/SUM

i.e., cd /usr/sap/S2P/SUM

./STARTUP &

4.1.1.6 Starting the Installation GUI

To start the installation GUI, login as <SID>adm to a VNC session or xwindows software i.e., Xmanager.

Command:

su – s2padm

cd <SUM_DIRECTORY>/sdt/exe

./DSUGui







4.1.2 Initialization Phase







Name = administrator

Password = ****** [Mentioned in the Secure File]

Phone or Email = [email protected]













Browse to the XML file for Upgrade purpose.













Click NEXT to continue with the Extraction Phase

**** Initialization Phase Completed Successfully ****

4.1.3 Extraction Phase

Passwords stored in secure file and maintained separately and not part of this cookbook.







Provide the Password for - DDIC & SYSTEM [Password Maintained in the Secure File]







As the existing SPAM version is lower it is mandatory to comply with the latest SPAM level requirement to avoid any

unwanted errors during upgrade phases.

As the SPAM Patch level 50 is already extracted and placed in the /usr/sap/trans/EPS/in, select the Import Spam

Version 50 and Continue.

Provide the DVD Mount points as below:

/misc/UpgradeDump/51041986_SLCONT700/Kernel_7.20_EXT_AIX_z_OS_OS400_LNXz_

/misc/UpgradeDump/51041986_SLCONT720/Kernel_7.20_EXT_AIX_z_OS_OS400_LNXz_

/misc/UpgradeDump/51041986_KERNEL/Kernel_7.20_EXT_AIX_z_OS_OS400_LNXz_

/misc/UpgradeDump/Upgrade_Export

/misc/UpgradeDump/COMPONENTS

/misc/UpgradeDump/BICONT_747_DelUpg

/misc/UpgradeDump/BICONT_747_INST

/misc/UpgradeDump/BICONT_747_UPG

/misc/UpgradeDump/KERNEL

/misc/UpgradeDump/LANGUAGE

/misc/UpgradeDump/LiveCache7.9

/misc/UpgradeDump/LiveCache_Update

/misc/UpgradeDump/SLCONT700

/misc/UpgradeDump/SLCONT720

/misc/UpgradeDump/SOLUTIONTOOLS

/misc/UpgradeDump/SCM7_EHP2_Upgrade_13Aug2013

/misc/UpgradeDump/SAPHOSTAGENT







Click Continue

At the end of the extraction phase, the brconnect [DBAtools] is quite old in version, please update with the latest

patch level of dbatools.

Login to a new putty session and execute the below steps to correct the above error:-

Commands:

su – s2padm

cd /usr/sap/S2P/SUM/abap/exe

SAPCAR -xvf /misc/UpgradeDump/DBATL720O10_33-20006700.SAR

cd /usr/sap/S2P/SUM/abap/exe

SAPCAR -xvf /misc/UpgradeDump/R3trans_127-10011182.SAR









At the end of the extraction phase, the required R3trans exe is quite old in version, please update with the latest

patch level file of R3trans in the Upgrade Directory path /usr/sap/S2P/SUM/abap/exe

Click NEXT







Close the Pop-up

Click NEXT to continue with Configuration Phase

***** Extraction Phase Completed Successfully *****

4.1.4 Configuration Phase







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, 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 use a remote shadow instance.

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

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

shadow system.

























Continue

Continue without adding CD’s

Check if newer versions













Continue







Incase of Dev & QA there was no SPDD & SPAU Transports from Trail upgrade, Both SPDD & SPAU were created

locally in the system due to difference in SPDD & SPAU of DEV & QualityNote:-

For Production Upgrade, SPDD will be carried from Quality system created SPDD TR i.e., [ SC7K900024 IBM_ABAP

SCM Upgrade: SPDD Adjustments ] or can be created locally in Production Shadow Instance.

For Production Upgrade, SPAU will be Transported immediately after Upgrade and the SPAU Transport of quality will

be used [ SC7K900026 ANTHONY SCM Upgrade: SPAU Adjustments ].

ABAP Shadow Instance Details :-







Continue

Select NO and click Continue







Close







Click NEXT to continue with Checks Phase

***** Configuration Phase Completed Successfully *****

4.1.5 Check Phase









Login to Client 800

SE38 /SAPAPO/OM_LC_UPGRADE_70











Execute

Execute

Execute

Execute

Execute

C).

If you upload inconsistent transaction data from the database following an upgrade, this can lead to various

problems.







You should therefore perform a consistency check before the upgrade using transaction /SAPAPO/OM17. This check

compares the liveCache data with the data in the database. If necessary, correct the inconsistent data.

You do not have to perform the consistency check immediately before the upgrade, but the closer you run this check

to the time of the upgrade, the more current the results will be.

Make sure that you perform the consistency check in each liveCache-relevant client for all planning versions.

All planning versions selected







In-case there is Inconsistency resulted as below please follow the steps mentioned:-







Note 1825133 - An error /SAPAPO/OM_SYNC001 in liveCache consistency check

D).

Due to a program error in some older COM or liveCache builds, you may have faulty APS data in your dataset. (APS =

Advanced Planning & Scheduling. This means data belonging to the applications SNP, PP/DS, ATP, and TP/VS).

If you do not correct this data, you will encounter errors when uploading the liveCache data.

You can use the program /SAPAPO/OM_CHECK_LIVECACHEDATA to check whether you have faulty data in the

system.

You should delete any faulty orders and then use the connected systems to import them again after the upgrade, ifrequired.

To delete orders in older releases, select the field "Delete Using DELETE Command" on the selection screen. If the

report finds faulty orders, select the orders that you want to delete and enter DELETE in the command field.

One by One







E).

You need to analyze the SAP liveCache and the LCA builds well before the upgrade as well as directly after the

upgrade. To do this, you can use transaction the /SAPAPO/OM13, which is called when you choose the button for

this step. Pay special attention to whether red lights are displayed. An information pushbutton next to the red lights

explains how you can eliminate them.

Since only a limited number of partial checks are performed in the overview, a green light is never displayed.





























Repeat for all planning versions

Execute program /SAPAPO/TS_LCM_REORG_SNP in repair mode for each initialized planning area. Note that

planning areas can be initialized for multiple planning versions.

Repeat for each planning







The program /SAPAPO/TS_LCM_CONS_CHECK_ALL performs various checks on the integrity of the Demand Planning

and Supply Network Planning data stored in the SAP APO database. It also checks the consistency of the

corresponding data in liveCache. If it reports inconsistencies, you must use program /SAPAPO/TS_LCM_CONS_CHECK

to manually rectify them for the relevant planning areas.

/n/SAPAPO/TR32

/n/SAPAPO/MSDP_ADMIN

The program /SAPAPO/OM_TS_LCCONS checks whether the objects in liveCache have the correct networking and it

also checks for logical consistency and for the consistency of the time series data.









Continue once the Section A is completed for all Clients.

Select Yes and continue







S2PK901809 BC-ASHISH Upg:tcode /ASU/Upgrade Note 875986-ChecksPhase Do Not Trspt







Continue after Transport is Import in further QA & Prd upgrade

Software Update Manager has flagged that a new tablespace (for shadow instance) needs to be created

with the storage size. Please note that this storage size will varies according to the current system database

size.

Create Oracle Tablespace PSAPSR3731

Increase the Tablespace PSAPSR3731 as below with oraS2P







Click Next







Click Next to continue with the Pre-processing Phase

***** Checks Phase Completed Successfully *****

4.1.6 Pre-processing Phase Part I

******** TAKE NOTE SPECICIALLY IN DEVELOPMENT SYSTEM *********







T-Code: SE10

Release all the above listed transports









Lock Now and Continue [This Step will Lock the Development]







We have reached the sub-phase MAIN_SHDRUN/ACT_UPG and we will generate the SPDD list and pass them toABAP to make the adjustment.

Before ABAPer can make the adjustment, we will need to setup the environment access in the shadow instance.

Login to Shadow Instance and Create an ABAP User ID – IBM_ABAP







After setting up the access environment, proceed to next activity in Section 4.3 SPDD adjustment.

4.1.6.1 End Uptime PART I

4.1.6.2 SPDD Adjustment

SPDD list is generated and handed to ABAP to perform the adjustment.

Once ABAP Team has confirmed that the SPDD adjustment has completed, we will proceed to the next activity in

Section 4.4 Start Uptime Part II













4.1.6.3 Start Uptime Part II

We will continue from the Pre-processing phase after ABAP Team has confirmed SPDD adjustment.

4.1.7 Pre-processing Phase Part II



























5 End Uptime

This is the phase where we have completed our uptime activities and most of the pre-processing phase. At this

stage, we are ready to go to downtime phase. Before we start the downtime, we will need to perform the next step

of isolating the systems. Please refer to the Project Plan.







6 Verify Backup

Before we proceed with the downtime phase, ensure that the scheduled online and archive log backup are

completed successfully and we are able to perform a point-in-time database recovery when necessary.

If database is not completed successfully, please run the backup again before entering downtime phase. This is to

ensure that the database can be recovered till this point in time.

Please also ensure that the successful backup is stored separately and is not overwritten.







7 Start Downtime

7.1 Start External Isolation

This step will be performed by IBM. The steps involve will include the below:-

1) To ensure that external scheduled job is completed successfully before the downtime and stop external

jobs which will run across the downtime period.

2) The other is to stop business communication channel to and from ERP & other External System viz., LES

3) IBM Basis Team will disable below RFC for APO and ECC with guidance from the isolation team (SCM).

NOTE: Please refer to project plan for the activity.

7.2 End External Isolation

7.3 Start Internal Isolation

Internal Isolation activities will be performed by IBM. During this time, there may be activities that need to be

performed on OS or SAP level. Please refer to the project plan for the activity.

7.3.1 Suspend Batch Jobs (Program: BTCTRNS1)

T-Code: SE38 execute report BTCTRNS1







T-Code: SM37

NOTE: Check for any active jobs, please refer to project plan for the sequence task to review and kill them.

7.3.2 Lock All SAP Users (refer to Project Plan)

This procedure will be performed by BASIS. Please refer to Project Plan. User should be locked in all client in case of

Production only one client.

Client 800







7.3.3 Stop Active Users’ Session (refer to Project Plan)

This procedure is to stop users’ session which are still active and logon before Basis locked all users. This is to

prevent users from updating the system.

7.3.4 Disable RFC Destinations

Sumitomo’s case we didn’t executed this step

To disable all the RFC destinations, a script is executed at the database level (login as oraS2P and run sqlplus). Syntaxof the SQL script is as follows:

Command:

su – oras2p

sqlplus /nolog

connect / as sysdba;

update sapsr3.rfcdes set rfcoptions=replace (rfcdes.rfcoptions, 'H=', 'H=SCM_Trial.') where rfcoptions like

'%H=%' and rfcoptions not like '%H=dumm%' and RFCDEST not like '%SAP%' and RFCDEST not like

'%TMS%';

commit;

The below screen shows the before and after results of the target host of one RFCExecute /$sync







7.3.5 Disable SMTP Node and FAX (SCOT)

This step is to disable the sending of email from SAP system. Uncheck the Node in use button.

Carry out this setting in all relevant clients of the upgrading system.

7.3.6 Disable Outbound Queue (Program: RSTRFCQ1)







7.3.7 Disable Inbound Queue (Program: RSTRFCI1)







7.3.8 Stop CCMS

To stop the CCMS, execute below steps:

Command:

su – s2padmsapccm4x -stop pf=/sapmnt/S2P /profileS2P_DVEBMGS00_scap02

7.3.9 Stop Solution Manager Agent

To stop the Solution Manager Agent, execute the command (logon as smdadm):

Command:

cd /usr/sap/SMD/<SID>/

./smdstop.sh

7.3.10 Check and Stop All Active Batch Jobs (SM37/SM66)

This step is to check and stop all active batch jobs which are still running.







7.3.11 Check and Clear Update Requests (SM13)

You will need to clear the queue because the SUM tool will stop and will not proceed further until you have cleared

them.

7.3.12 Check and Clear Lock Entries (SM12)


them.







7.3.13 Check and Clear Mass Processing (SE14)

7.3.14 Check and Clear Outbound Queue (SMQ1)


them.

For SAP system with more than 1clients, please logon to the client and delete all queues.







7.3.15 Check and Clear Inbound Queue (SMQ2)


them.

7.3.16 Check for unprocessed logistics extraction data (Program: RMCEXCHK)







We will need to clear the structure if the above screen appears by executing program RMCSBWSETUPDELETE for

each of the structure number highlighted in the list. Go to SE38 and execute

Program: RMCSBWSETUPDELETE

Run the program RMCEXCHK again to ensure that all status is green.







7.3.17 Check and Stop Active User Session (AL08/SM04)

This step is to check and stop any active user (not authorized users) still logged into the system.

7.3.18 Disable Database Backup Job

Disable regular backup Schedule by informing SCA IT team

7.3.19 Shutdown SAP Application Servers (stopsap)

This procedure is executed for production system if any additional App servers.

Logon to all dialog instances as <SID>adm and shutdown the instance including the saposcol and sapstartsrv. Ensure

that there is no sap processes running by executing ps –ef|grep sap.

Command:

stopsap D<nr>

saposcol –k (DO not execute this command the kernel is 720)

sapcontrol –prot NI_HTTP –nr <instance number> -function StopService

7.3.20 High Availability







We will use the ASCS standalone enqueue server during upgrade.

7.3.21 High Availability (Disable HA Clustering Process)

This procedure is executed by SCA UNIX administrator.

The setup of the clustering is based on HACMP script which will monitor the heartbeat of the 2 clustered nodes

(Node A and Node B) and failover will only take place when the first node (Node A) is down (where ASCS00, CI and

Database is running).

The HACMP script does not monitor critical processes (example ASCS and oracle pmon) and will not failover if we

manually shutdown the ASCS and database.

Based on the above HACMP script, we will not disable HA but if there is any changes to the HACMP script which

monitor critical processes, you will need to disable HA cluster.

During this step, we will test that the cluster resources will not failover by shutting down the ASCS00 and wait for a

few minutes.

7.4 End Internal Isolation

After confirming all external and internal isolation tasks have completed, the next step is to start the technical

downtime phase.

7.5 Start Technical Downtime

7.5.1 Define Central Instance Server in SM61 (Productive System Only)

The central instance server will be added in transaction code SM61 (background processing group) under server

group SAP_DEFAULT_BTC if it does not exist.

This will ensure that the background job is able to execute on the central instance during the downtime phase. If this

is not defined, during TABIM_POST phase the process will wait for RDDIMPDP job to run.

7.5.2 Pre-processing Phase Part III – [Live Cache Upgrade Section B]













Login to SAP client 800 with DDIC

T-Code SE38 and Execute the Report /SAPAPO/OM_LC_UPGRADE_70

Section B:-







Step 1].

Execute -> F8













SM37

Display Spool for Planning Version 000















Step 2].

Click Stop LiveCache







Section B completed.

Continue with the Upgrade Steps













In this sub-phase MAIN_DTTRANS/SUBMOD_DOWNTRANS/DOWNCONF_DTTRANS_BCK, we will need to backup the

Software Update Manager director (SUM). This is to ensure that we can rollback to this point-in-time if we have

problems with the update which prevent us from proceeding further.

We also need to ensure that the database is backed up.







***** Pre-Processing Phase Completed Successfully *****

7.6 Execution (Downtime) Phase







Prompt for the time to Upgrade the LiveCache Instance

A]. Upgrade of Live Cache

Step 1] Login to the Live Cache Host

Step 2]







Step 3] Execute the LCUPDATE script

Step 4] Select Yes to continue with Upgrade

Step 5] Enter SAP LiveCache Name i.e., S3P







Step 6] Provide the SID / DBM User ID & Password i.e., SID = S3P & DBM User = control

Step 7] Provide the Installation Name & Network Port i.e., S3P & Port 7200







Step 8] Upgrade Continues and Successfully Completed







***** LiveCache Upgrade Completed *****

B]. Patching of the Upgraded Live Cache with the Latest Build

Start the LiveCache from OS commands







C]. Post Live Cache Upgrade & Patch Set Parameters

Post Live Cache Upgarde activity as per Guide

1567117 - Parameter values for SAP liveCache Version 7.9

1111426 - Parameter check for SAP MaxDB/liveCache instances

LoadBalancingCheckInterval = 4

InitialAllocatorSize = 1024000

LogQueues = 2

LogQueueSize = 2000

MaxCPUs = Number of liveCache server processors UseableCPUs = MaxCPUs

MaxCPUs = 2

MaxExclusiveLockCollisionLoops = -1

MaxSQLLocks = 300000

MaxUserTasks = 55 (Number of SCM work processes)*3 + 4.

OmsSubHeaps = 2

OmsMaxHeapSize = 3072000

UseDynamicCommunicationSegments = YES

UseSharedSQL = NO

UseSystemTrigger = YES

Tcode LC10 Administration Parameters







Select the Parameter and Switch to change mode

Store and Continue with other Parameters

D]. SCM ABAP Host Update the LC Client

Step 1] stopsap r3







Step 2] Execute the LCUPDATE script with the below command to update the client libraries

Step 3]







Step 4] LC Client Updated successfully

Step 5] Start SAP

E]. Execute the Steps of Section C for the Program /SAPAPO/OM_LC_UPGRADE_70









Step 2]

Step 3]

Step 4]













Tcode SM37

Check the Spool of above Jobs and compare with the expected Results for each and every Planning version in all

clients.







Step 5]









Check the Spool of above Jobs and compare with the expected Results for each and every Planning version in all

clients.









Step 8]

Completed the Section C







Continue with the Downtime Upgrade Phase

Click Continue once you have completed the Section C Successfully















7.7 Post-Processing Phase







Import the SPAU Transport

We will continue the update and let ABAP make the SPAU adjustment after the update has completed. Click

‘Adjustments completed’ button.











***** Post-Processing Phase Completed Successfully *****

7.8 Finalization Phase













***** Finalization Phase Completed Successfully *****

7.9 End Technical Downtime

We have completed the SCM upgrade activities. The next phase will be the Follow-up Activities.

7.10 Follow-up Activities

7.10.1 Generating Loads (SGEN)

Before starting the SGEN, you will need to apply SAP Note 1630356 – SGEN Terminates after 500 generation errors.

If you have already placed this change in a transport, please perform the transport instead. The below instruction is

valid if there is no transport created yet.













7.10.2 Update Oracle statistics

Logon as ora<SID> and execute the below command

Command:

su – oras2p

brconnect -c -u / -f stats -t oradict_stats

brconnect -c -u / -f stats -t system_stats -i 0







brconnect -c -u / -f stats -t all -f collect -p 16

7.10.3 Check Oracle database archive log mode enabled

This step is to verify that the archive log mode is turned on after the SCM upgrade. SUM tool should have enabled

the archive log mode.

7.10.4 Enable ICF Services (SICF)

The SUM tool disables services of the Internet Communication Framework (ICF) for security reasons. You have to re-

activate the services you require again after the SCM upgrade completed.Call transaction SICF and activate the required services.

Services to be re-activated.







Refer to Health Check section for those ICF screenshot.

7.10.5 Replace new kernel in dialog instances and verify kernel version

In case of Sumitomo – SCM Production system is not having any Additional Dialogue Instances

*** Production system only if any additional Dialog Instances****

On ALL Dialog Instances

1) On Central Instance, copy /sapmnt/<SID>/exe to all Dialog Instances /sapmnt/<SID>/exe

2) Execute Sapcontrol –prot NI_HTTP –nr <instance number> -function StopService

3) If there is an error, execute sapcontrol –prot NI_HTTP –nr <instance number> -function StartService

4) Execute stopsap r3 <SID>

5) Goto /sapmnt/<SID>/exe and change the ownership and security mode of icmbnd.

cp -pR icmbnd.new icmbnd

chown root:sapsys icmbnd

chmod 4750 icmbnd

Verify kernel version on ALL Dialog Instances

disp+work –version

R3trans –v

Igsmux_mt –version

brtools –version

tp -version

7.10.6 Execute SAPDBA_ROLE.SQL

Please execute the query file SAPDBA_ROLE.SQL in /sapmnt/<SID>/exe in the central instance. This is to prevent

error when executing DBCHECK. Execute the SQL using ora<SID> user.

Command:

su – oras2p

sqlplus /nolog @sapdba_role.sql S2P

7.10.7 Follow-Up Activities for User root

1) Activities for OS user root (only in central instance)







2) Go to the SAP exe directory and perform the following:-

3) Change the security mode for OS password file which was performed under Extraction phase (check if

the task is performed in Extraction Phase, if not do not execute the command below).

Command:

chmod 600 /etc/security/passwd

7.10.8 Install SAPHOSTAGENT

Install SAPHOSTAGENT (https://service.sap.com/sap/support/notes/1031096)

For * PRODUCTION systems which does not have SAPHOSTAGENT installed, you will need to perform the steps

below on all the production systems.

https://service.sap.com/sap/support/notes/1031096










*** If SAPHOSTAGENT was already installed in all the production systems, you will need to perform the steps 1 to 4

above. As for step 5, you will need to execute saphostexec –upgrade instead of –install ***

For Your Information

SAPHOSTAGENT installation will create OS automatic startup file sapinit in the

directory ./rc.d/init.d/. Do not kill the saphostagent process manually and note that starting the SAP

instance will not start the saphostagent. Perform the below steps as root OS user.

To stop saphostagent, execute the command saphostexec –stop in director /usr/sap/hostctrl/exe.

To start saphostagent manually, execute hostexecstart

To check the status of saphostagent, execute saposcol –s







7.10.9 Verify updated SAP component version

7.10.10 Verify Kernel/IGS/BRTOOLS/DBSL Version

7.10.11 Verify Workflow Configuration (SWU3)

In case of Sumitomo we don’t have Workflow configured.

Recheck workflow configuration setting and it will show that the configuration is still down due to batch job still

suspended.







7.10.12 Clear the Shadow system details from Secure Storage

7.11 High Availability – Only for Production System

Test the High Availability with the SCA Vendor.

7.12 SPAU Adjustment

SPAU adjustment will be performed by ABAP team. Once the adjustment has completed, ABAP Team will inform us

and we will proceed to the next activity of de-isolation.

***IMPORTANT (BASIS ACTIVITY) *****

This task needs to be performed after that FIXES transports have been transported to the system especially the list of

Identified transports.







7.13 Start De-Isolation

Internal de-isolation task will be performed by SCA & IBM. Please refer to the project plan for activities prior to thebelow tasks we will perform.

7.13.1 Prior to LiveCache Upgrade

Note Prior SP Short Text

1556356 3 Upgrade error in "Refresh Database Statistics"

1513031 3 Upgrade: Error in /SAPAPO/OM_CONSTRAINT_MODIFY

1710640 2 12 Extraction with parallel processing, temporary timegrids

1673418 3 .11 Performance low during CTP check or release to SNP.

1507924 4 9 Runtime of /SAPAPO/OM_CDP_41_UPD_DB_STATS1493975 3 9 Upgrade SCM APO: Performance improvement

1484487 4 8 Runtime of /SAPAPO/OM_CDP_41_UPD_DB_STATS

1481197 3 7 /SAPAPO/OM_LC_UPGRADE_70: Section D cannot be accessed.

1461035 4 9 Performance improvements during upgrade

1449190 2 7 Inconsistencies for plng matrixes after migration or upgrade

1406124 4 6 Enhancement /SAPAPO/OM_UPGR_UPLOAD_ANALYSE

1403993 2 6 Upgrade: Comparison indicates error w/ external constraints

1393161 3 6 Demand Planning (DP) upgrade: Non-initial flag is not set

1382941 3 5 Upgrade: Locking conflict when creating stocks

1358960 2 4 Global time interval is too long

1356242 3 4 /SAPAPO/RESOURCES_LC_CREATE runs indefinitely

1353440 4 4 Upgrade: Automatic execution is inactive1351537 2 4 Upgrade of Demand Planning: Incorrect conversion of flags

1337202 3 4 Upgrade: Activity status has changed

1290534 4 3 Upgrade: Error-tolerant job overview

1287390 3 3 Dynamic verification of bucket parameters for FCS

1267317 2 6 Superfluous time bucket generated by background jobs

1267136 4 2 Upgrade: Behavior during connection problems

1264474 4 2 /SAPAPO/OM_UPGR_COMPARE_TIME: Application functions improved

1257293 3 * Notes regarding resource time stream, relevant for upgrade

1241534 4 2 Rescheduling at the end of the upload (upgrade)

1229835 3 7 Time shifts during upload

955473 3 3 Resources not created in liveCache

7.13.2 System Sanity Checks (in parallel with SPAU)

The following checks will be performed by IBM.

Transaction Code: SICK







Transaction Code: SM21

Transaction Code: ST22





Transaction Code: DB02 / DBACOCKPIT



Transaction Code: SMQ1

Transaction Code: SMQ2

Transaction Code: RZ12

Please verify that the Logon Groups are defined for the Instance: SMLG

7.13.3 Verify SAP startsap and stopsap scripts

This procedure is to test the new kernel script is working properly.

7.13.4 SAP HA Cluster Failover Test (Productive System Only)

This task will be executed by SCA AIX Team. Please refer to project plan.

7.13.5 Start SAP Host Agent

Command:







sapccm4x –DCCMS pf=<SID>_DVEBMGS00_<hostname>

7.13.6 Start Solution Manager Agent

Logon as smdadm and execute the command:

Command:

/usr/sap/SMD/J98/script/smdstart.sh

7.14 End De-Isolation (Internal – ERP)

7.15 Backup

Backup will be activated by SCA IT Team. Please refer to project plan for the sequence of the activity.

7.16 De-Isolation (External)

This step will be performed by both IBM and SCA for external systems connectivity to ERP system & LES (example

starting BW batch jobs, enable RFCs etc)

7.16.1 Enable Inbound Queue (Program: RSTRFCI3)







7.16.2 Enable Outbound Queue (Program: RSTRFCQ3)







7.16.3 Enable Node for SMTP (SCOT)

This is to enable the sending of email from SAP system.







7.16.4 Restart Batch Jobs (Program: BTCTRNS2)

7.16.5 Implementation of SSFS Mode for Oracle

Note 1611877 - Support for ABAP SSFS during database connect

Note 1622837 - Secure connection of AS ABAP to Oracle via SSFS

Note 1639578 - SSFS as password storage for primary database connect

Note 1764043 - Support for secure storage in BRTools

7.16.6 Enable Backup Job (OS cronjob)

Enable the regular backup schedule by informing the SCA IT team

7.17 Unlock Business Users Account (refer to Project Plan)

The last step is to unlock business users’ account.







8 End Downtime







9 Appendix A (Errors Resolution or Manual Tasks or Additional Information)

This section will capture all the SCM upgrade errors or manual tasks needed to be performed in each Software

Update Manager Phase. For new errors which surfaced for other systems, please add into the list.

9.1 Initialization Phase

NIL

9.2 Extraction Phase

NIL

9.3 Configuration Phase

NIL

9.4 Checks Phase

NIL

9.5 Pre-processing Phase

NIL

9.6 Downtime Phase

NIL

9.7 Post-processing PhaseNIL

9.8 Finalization Phase

NIL

9.9 OSS Messages Raised

The below table are the list of Technical OSS raised against the whole SAP SCM Upgrade project. The below table can

help as a quick reference for any issue and solution provided by SAP.

9.10 Post Upgrade Error & Solutions

A]. ST22 Dump – LOAD_PROGRAM_NOT_FOUND







Solution:

De-schedule the Jobs SAP_REORG_SCM_LC_LOG & B76200

Select the Released Job and Delete it from the Job Menu

YES

B]. ST22 Dump – LOAD_PROGRAM_NOT_FOUND - Program "RSORA811" not found

Solution:

1300273 - SAP_COLLECTOR_FOR_PERFMONITOR: New architecture as of 7.20

1841778 - LOAD_PROGRAM_NOT_FOUND in RSCOLL00







966309 - Content of table TCOLL in SAP_BASIS 700 - 7.02 and 7.31+

Goto SNOTE and apply the Note B299 in client 100 (Dev client)

SE16

C]. ST22 Dump – SYNTAX_ERROR - Syntax error in program "/SAPAPO/SAPLATPT "







Solution:

This Dump was for application team to check

ABAP team fixed the program through SPAU

D]. ST22 Dump – DBIF_DSQL2_OBJ_UNKNOWN with T-Code OM03

Solution:

LC Patched to the Latest Build Build 13 Patch level 3 with Kernel 7.9.08.10

1529690 - Importing SAP liveCache Version 7.9

1865684 - SAP liveCache 10.0 LCA build 13

E]. DBACOCKPIT – ALERT Monitor Grey out







Solution:







F]. TABLESPACE – PSAPSR3700

Solution:

Dropped the Tablespace PSAPSR3700

Brtools Command

G]. SM21 Error







Solution:

Deleted the below unrequired TCP/IP RFC destination from SM59

H]. DBACOCKPIT Central Calendar Log Collector Error

Solution:

Schedule the Job daily to collect the Calendar Log for DBACOCKPIT purpose

I]. Dump ST22 IN_WRONG_TABLESPACE

Solution:

SE16







Click Change in Debug Mode to change the Tablespace name from PSAPSR3700 to PSAPSR3731.













J]. Error Table has no index







Solution:

GOTO SE14:- Table name SNAP_KRN_PROJ and create the Missing Index

K]. Production LiveCache HA Testing Error

# ./dbmcli -d S3P -u control,control db_state

Error! Connection failed to node (local) for database S3P:

-24700,ERR_DBMSRV_NOSTART: Could not start DBM server.-24832,ERR_SHMNOTAVAILABLE: Shared memory not available

-24993,ERR_RTEEXT: Runtime environment error







1,could not change dir:/var/lib/sdb

2,No such file or directory

Solution:

Copy the sdb directory and subdirect from /var/lib of Primary Node to Secondary node to resolve the above issue1041650 - DBM Server utilizes 100% processor time

9.11 List of Transports for Production

STMS Transport Import Status





9.12 Unlock of Production Users

Post all activity and Error and solution before releasing and Declaring Go-Live unlock the Users of Production as

below: