SCM Server 40 UX Upgrade

8/9/2019 SCM Server 40 UX Upgrade

1/232

Component Upgrade Guide

SAP

Supply Chain

Management 4 0:

UNIX

Document Version 1.01 September 03 , 2003


2/232

SAP AG

Neurottstrae 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www sap com

Copyright 2003 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and

SQL Serverare registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,

MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere,

Netfinity, Tivoli, Informix and InformixDynamic ServerTM

are

trademarks of IBM Corp. in USA and/or other countries.

ORACLEis a registered trademark of ORACLE Corporation.

UNIX, X/Open, OSF/1, and Motifare registered trademarks of

the Open Group.

LINUX is a registered trademark of Linus Torvalds and others.

Citrix, the Citrix logo, ICA, Program Neighborhood , MetaFrame,

WinFrame, VideoFrame, MultiWinand other Citrix product names

referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered

trademarks of W3C, World Wide Web Consortium, Massachusetts

Institute of Technology.

JAVAis a registered trademark of Sun Microsystems, Inc.

J2EEis a registered trademark of Sun Microsystems, Inc.

JAVASCRIPTis a registered trademark of Sun Microsystems, Inc.,

used under license for technology invented and implemented by

Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP

AG and Commerce One.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, xApps, mySAP

Business Suite, and other SAP products and services mentioned herein

as well as their respective logos are trademarks or registered

trademarks of SAP AG in Germany and in several other countries all

over the world. All other product and service names mentioned are the

trademarks of their respective companies.

Disclaimer

Some components of this product are based on Java. Any code

change in these components may cause unpredictable and severe

malfunctions and is therefore expressively prohibited, as is any

decompilation of these components.

Any Java Source Code delivered with this product is only to be used

by SAPs Support Services and may not be modified or altered in any

way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following address:http://service.sap.com/instguides


3/232

Typographic Conventions

Type Style Represents

Example Text Words or characters thatappear on the screen. Theseinclude field names, screentitles, pushbuttons as well asmenu names, paths andoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrasesin body text, titles of graphicsand tables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, tablenames, and individual keywords of a programminglanguage, when surrounded by

body text, for example,SELECT and INCLUDE.

Exampl e t ext Screen output. This includesfile and directory names andtheir paths, messages, namesof variables and parameters,source code as well as namesof installation, upgrade anddatabase tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLE TEXT Keys on the keyboard, forexample, function keys (suchas F2) or the Ent er key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax


4/232

Upgrade to SAP Supply Chain Management 4.0: UNIX

Contents

Upgrade to SAP Supply Chain Management 4.0: UNIX .................8

1 Introduction .........................................................................................9

1.1 Naming Conventions for the SAP SCM Upgrade............................... 10

1.2 How to Use this Documentation ......................................................... 12

1.3 New Features in the SAP SCM Upgrade............................................. 14

2 Upgrade - Step by Step.....................................................................18

3 SAP Notes for the SAP SCM Upgrade.............................................29

4 Product-Specific Information for the SAP SCM Upgrade .............344.1 SAP SCM: Upgrade Planning .............................................................. 354.1.1 Upgrade Strategy Planning.........................................................................................354.1.2 Database Backup........................................................................................................364.1.3 Upgrade Schedule Planning.......................................................................................364.1.4 Runtime for the Import of the Substitution Set............................................................374.1.5 Planning the Backup of DP and SNP Time Series in InfoCubes................................374.1.6 Changing Bucket Limits for Product Availability Check..............................................384.1.7 Planning the Upgrade of SAP liveCache and Optimizer ............................................384.1.8 Checking the Hardware Requirements.......................................................................394.1.9 Checking the Source Release of the SAP System.....................................................404.1.10 Meeting the Requirements for the SAP liveCache ...................................................414.1.11 Upgrade of the Operating System and Database System: Overview ......................42

4.2 SAP SCM: Upgrade Preparations .......................................................464.2.1 Creating the Upgrade Directory..................................................................................464.2.2 Checking the Database-Specific Requirements for PREPARE .................................474.2.3 Making Preparations for SAP BW-Specific Objects ...................................................474.2.4 Converting Inconsistent Characteristic Values...........................................................484.2.5 Making Entries for the Parameter Input Module.........................................................494.2.6 Making Entries for the Extension Module...................................................................504.2.7 Making Entries for the General Checks Module.........................................................504.2.8 Making Entries for the Necessary Checks for Conversion Module ............................504.2.9 Making Preparations for Using Global ATP................................................................524.2.10 Meeting the Requirements for Workforce Management...........................................53

4.3 SAP SCM: The Upgrade....................................................................... 54

4.3.1 Phase REQ_APOUPG ...............................................................................................544.3.2 Phase JOB_MC01_CACL_CDP_POST ..............................................................564.3.3 EU_IMPORT Phases..................................................................................................564.3.4 Phase REQ_LCUPG: Installing SAP liveCache 7.4.3................................................ 574.3.5 Phase MODPROF_TRANS........................................................................................62

4.4 SAP SCM: Post-Upgrade Activities .................................................... 634.4.1 Actions for SAP liveCache..........................................................................................634.4.2 Performing Post-Upgrade Activities for the Applications............................................634.4.3 Deleting Download Data Table...................................................................................65

5 General Upgrade Information ..........................................................66

5.1 Upgrade Planning................................................................................. 675.1.1 Time Frame for Upgrading the Front-End Software ...................................................68

5.1.2 System Switch Upgrade .............................................................................................69

4 September 2003


5/232


5.1.3 Upgrade Strategy Planning.........................................................................................725.1.4 Database Backup........................................................................................................755.1.5 Database-Specific Aspects.........................................................................................765.1.6 Upgrades in an MCOD System Landscape................................................................785.1.7 Incremental Table Conversion....................................................................................795.1.8 Upgrade Schedule Planning.......................................................................................815.1.9 Runtime for the Import of the Substitution Set............................................................835.1.10 Upgrade in an SAP System Group...........................................................................845.1.11 Modification Adjustment Planning.............................................................................855.1.12 Checking the Structural Requirements.....................................................................875.1.13 Checking the Hardware Requirements.....................................................................875.1.14 Checking the Software Requirements ......................................................................88

Checking the Source Release of the SAP System ...........................................................88Meeting the Requirements for the Upgrade Assistant ......................................................89Meeting the Operating System-Specific Requirements ....................................................90

Upgrading the Operating System and Database System: Overview ................................925.1.15 Accessing Documentation Before and During the Upgrade.....................................935.1.16 Meeting the Requirements for the SAP Internet Solution.........................................935.1.17 Importing Additional Languages ...............................................................................94

5.2 Upgrade Preparations.......................................................................... 965.2.1 Determining the Host for the Upgrade Preparations ..................................................975.2.2 Making Preparations for Reading the Upgrade CDs..................................................985.2.3 Creating the Upgrade Directory..................................................................................985.2.4 Checking the Database-Specific Requirements for PREPARE ...............................1005.2.5 Importing the Latest SPAM Update (Source Release 4.x and Higher) ....................1005.2.6 Starting PREPARE from the CD...............................................................................1015.2.7 Starting the Upgrade Assistant Server .....................................................................1025.2.8 Starting the Upgrade Assistant GUI..........................................................................1035.2.9 Starting the Upgrade Assistant.................................................................................104

5.2.10 Restarting PREPARE from the Upgrade Assistant GUI .........................................1055.2.11 Resetting PREPARE...............................................................................................1065.2.12 Importing Software After Starting PREPARE .........................................................1065.2.13 Making Entries for the Parameter Input Module .....................................................1075.2.14 Making Entries for the Initialization Module ............................................................1145.2.15 Making Entries for the Import Module.....................................................................1165.2.16 Making Entries for the Extension Module ...............................................................1175.2.17 Making Entries for the Installation Module..............................................................1255.2.18 Evaluating the Results of PREPARE......................................................................1275.2.19 Making Preparations at the Operating System Level .............................................1355.2.20 Making Preparations at the Database Level...........................................................1355.2.21 Making Preparations at the SAP System Level......................................................138

Checking the User for the Upgrade.................................................................................138

Checking the Requirements for the Modification Adjustment .........................................138Setting the Operation Mode for the Upgrade ..................................................................139

Processing Batch Input Sessions (Source Release 3.1I) ...............................................139Converting the Translation Proposal Pool (Source Release 3.1I) ..................................140Processing Direct Input Error Data (Source Release 3.1I) .............................................140

5.3 The Upgrade ....................................................................................... 1415.3.1 Starting the Upgrade.................................................................................................1435.3.2 Stopping the Upgrade...............................................................................................1435.3.3 Restarting the Upgrade.............................................................................................1445.3.4 Phase INITPUT.........................................................................................................1455.3.5 Phase PATCH_CHK.................................................................................................1465.3.6 Phase KEY_CHK......................................................................................................146

September 2003 5


6/232


5.3.7 Phase INITSUBST....................................................................................................1475.3.8 Phase CONFCHK_X.................................................................................................1485.3.9 Phase VIEWCHK1....................................................................................................1495.3.10 Phase REPACHK1 .................................................................................................1495.3.11 Phase JOB_RSVBCHCK2......................................................................................1495.3.12 Phase FREECHK_X...............................................................................................1505.3.13 Phase LOCKEU_PRE ............................................................................................1505.3.14 EU_IMPORT Phases..............................................................................................1515.3.15 Phase REPACHK2 .................................................................................................1525.3.16 Phase CNV_CHK_XT.............................................................................................1525.3.17 Phase ADJUSTCHK ...............................................................................................1535.3.18 Phase ACT_..................................................................................................1535.3.19 Phase VIEWCHK2..................................................................................................1555.3.20 Phase MODPROF_TRANS....................................................................................1555.3.21 Phases JOB_RSVBCHCK_R and JOB_RSVBCHCK_D .......................................1565.3.22 Phase ENVCHK......................................................................................................1565.3.23 Continuation of the Upgrade After the MODPROFP_UPG Phase .........................157

5.3.24 Phase CHK_POSTUP ............................................................................................1585.4 Post-Upgrade Activities..................................................................... 1595.4.1 Executing the Script saproot.sh................................................................................1615.4.2 DB2 UDB for UNIX and Windows: Performing Specific Actions ..............................1635.4.3 DB2 UDB for OS/390 and z/OS: Performing Specific Actions .................................1655.4.4 Informix: Performing Specific Actions.......................................................................1675.4.5 Oracle: Performing Specific Actions .........................................................................1685.4.6 SAP DB: Backing Up the Database..........................................................................1705.4.7 Distributing SAP Programs.......................................................................................1705.4.8 Renaming the Local System Log (Source Release 3.1I)..........................................1715.4.9 Checking the Profile Parameters with Transaction RZ10.........................................1725.4.10 Reimporting Additional Programs...........................................................................1725.4.11 Adjusting Repository Objects..................................................................................173

5.4.12 Performing Post-Upgrade Activities for the Applications........................................ 1735.4.13 Rescheduling Background Jobs .............................................................................1745.4.14 Rescheduling DB13 Jobs (Source Release 3.1I) ...................................................1745.4.15 Migrating Matchcodes in Search Help Objects (Source Release 3.1I) ..................1755.4.16 Informix: Updating Statistics ...................................................................................1765.4.17 Oracle: Actions for the Cost-Based Optimizer........................................................1765.4.18 SAP DB: Updating Optimizer Statistics ..................................................................1785.4.19 Generating ABAP Loads.........................................................................................1785.4.20 Generating BSP Applications .................................................................................1795.4.21 Performing Actions for the SAP Online Documentation .........................................1795.4.22 Performing Post-Upgrade Activities in the Authorizations Area .............................1805.4.23 Processing Table Clusters After the Upgrade (Source Release 3.1I)....................1815.4.24 Installing More Dialog Instances.............................................................................182

5.4.25 Importing Support Packages After the Upgrade.....................................................1825.4.26 Transport Management System: Distributing the Configuration.............................1835.4.27 Performing Post-Upgrade Activities for the Language Transport...........................1835.4.28 DB2 UDB for OS/390 and z/OS: Removing Empty Database Objects ..................1845.4.29 Oracle: Deleting Tablespaces.................................................................................1845.4.30 Converting Batch Input Logs ..................................................................................1855.4.31 Saving Files for Follow-Up Upgrades.....................................................................1855.4.32 Evaluating the Upgrade Runtime............................................................................186

6 Additional Information....................................................................188

6.1 Troubleshooting................................................................................. 1886.1.1 Upgrade Logs ...........................................................................................................1896.1.2 Evaluating the ELG Log Files ...................................................................................191

6.1.3 Correcting Errors in the RFCCHK Phase .................................................................192

6 September 2003


7/232


6.1.4 Correcting Entries Made in the INITPUT and INITSUBST Phases ..........................1936.1.5 Correcting Errors in the DBCHK Phase....................................................................1946.1.6 Correcting Errors in the BATCHCHK Phase ............................................................1956.1.7 Correcting Errors in the INTCHK and INTCHK_SW Phases....................................1956.1.8 Correcting Errors in the SPACECHK_ALL Phase....................................................1966.1.9 Correcting Errors in the JOB Phases........................................................................1966.1.10 Cleaning Up Terminated Conversions in the DB Conversion Phases ...................1976.1.11 Correcting Errors in the TRBATCHK_XT Phase ....................................................1996.1.12 Correcting Errors in the ACT Phase .......................................................................2006.1.13 Correcting Conversion Errors in the PARCONV Phase .........................................2016.1.14 Correcting Errors in the XPRAS Phase ..................................................................2026.1.15 Preparing the Restart of the Upgrade After a System Failure................................2036.1.16 Resetting the Upgrade............................................................................................2046.1.17 Restarting the Upgrade in Scroll Mode...................................................................2076.1.18 Correcting Problems when Processing ABAP Steps..............................................2086.1.19 Correcting Problems when Starting the SAP System.............................................2096.1.20 Correcting Problems when Copying SAP Programs..............................................210

6.1.21 Correcting Administrator Profile Problems on Application Servers ........................2106.1.22 Providing SAP Support with Information ................................................................211

6.2 Upgrade Administration .................................................................... 2136.2.1 Alert Function............................................................................................................2136.2.2 Determining Versions................................................................................................2146.2.3 Executing PREPARE and R3up in Scroll Mode.......................................................2156.2.4 Isolating the Central Instance ...................................................................................2166.2.5 Changing the Database Recovery Mode..................................................................2186.2.6 Deleting Archived Upgrade Logs..............................................................................2206.2.7 Using a Different Upgrade Directory.........................................................................2206.2.8 Releasing and Confirming Open Repairs and Requests..........................................2216.2.9 Using the Phase List for the Upgrade.......................................................................222

6.3 Upgrade Tools.................................................................................... 2256.3.1 PREPARE.................................................................................................................2256.3.2 R3up .........................................................................................................................2276.3.3 Upgrade Assistant.....................................................................................................228

Using the Upgrade Assistant...........................................................................................2296.3.4 Upgrade Monitor.......................................................................................................230

Starting the Upgrade Monitor ..........................................................................................232Understanding the Upgrade Monitor Display..................................................................232

September 2003 7


8/232

1 Introduction

Upgrade to SAP Supply ChainManagement 4.0: UNIXPurpose

This documentation describes how to upgrade to SAP Supply Chain Management 4.0(SAPSCM 4.0) from Source Release SAP APO 3.0 and higher. It also contains additional usefulinformation about the upgrade. The information in this documentation is intended for SAPsystem administrators with operating system, database, and SAP Web Application Serverknowledge.

The Upgrade Step by Step [page 18]section is a list of all actions that you must perform toupgrade your system successfully. The actions are placed in chronological order, so that youcan work through them just like a checklist.

The following two parts of this documentation explain the upgrade procedure in detail:

! Product-Specific Information for the SAP SCM Upgrade [page 34]

! General Upgrade Information [page 66]

The last part of this documentation,Additional Information [page 188], gives you informationon troubleshooting, the administration tasks you need to perform before and after theupgrade, and the tools you use to upgrade the system.

Both the structure of the documentation [page 12]and the upgrade procedure[page 69]itself have changed significantly as of SAP Web Application Server6.10.

IntegrationIf you want to upgrade the component SAP Supply Chain Management 4.0 in the context ofthe uprade of a mySAP Business Suite solution or one of its business scenarios, it isessential that you familiarize yourself with the contents of the corresponding SolutionUpgrade Guide before starting to upgrade.

The Solution Upgrade Guide is the central document for the upgrade of mySAP BusinessSuite solutions and business scenarios. It lists the components and third-party applicationsrequired by each business scenario of a mySAP Business Suite solution, and refers to therequired installation and upgrade guides. It also defines the upgrade sequence of thebusiness scenarios of the corresponding mySAP Business Suite solution.

Constraints

This documentation only applies if you are upgrading your SAP system on UNIX.

To find the latest version of this documentation, see the SAP ServiceMarketplace at the Internet address service.sap.com/instguides .

In addition to this documentation, you also require other information, such as the ReleaseNotes for the applications that you implement, the SAP Implementation Guide (IMG), the SAPNotes [page 29]that are specific to this upgrade, and any other documentation referred to inthis documentation.

8 September 2003


9/232

1 Introduction

1 IntroductionThis section of the documentation contains general information on:

! Naming conventions [page 10]This section explains the terminology and abbreviations used in this documentation.

! How to use this documentation [page 12]

In SAP Web Application Server 6.10 the structure of the upgrade documentation hasbeen changed from a process flow description with additional information to aninformation pool.

! New features in the upgrade procedure [page 14]

The upgrade procedure is continually being enhanced. This section contains the mostimportant changes to the procedure, for both current and previous releases.

September 2003 9


10/232

1 Introduction

1.1 Naming Conventions for the SAP SCMUpgrade

SAP SCM and SAP APO

As of Release 4.0 SAP Advanced Planning and Optimization(SAP APO) has been renamedto SAP Supply Chain Management (SAP SCM). In this documentation the term SAPAdvanced Planning and Optimization(or the abbreviation SAP APO) is used when referringto Release 3.1 and lower, and SAP Supply Chain Management(or the abbreviation SAPSCM) when referring to Release 4.0.

SAP liveCache Application Routines (COM / LCA)

As of SAP SCM 4.0, the name COMis no longer used. Instead the SAP liveCacheapplication routines are now called liveCache applications(LCA). The application areas in theSAP Service Marketplace have changed accordingly from APO-COM to BC-DB-LCA, where

the abbreviations have the following meanings:! BC means Basis components

! DB means database

! LCA means liveCache applications

Release

Unless otherwise specified, the term releaseis used in the product-specific part of thisdocumentation to refer to the release of the SAP SCM or SAP APO system.

In the general part of the documentation, releaseis used to refer to the release of the SAPBasis or SAP Web Application Server system.

Release Description

The Basis or SAP Web Application Server releases correspond to the following SAP SCM orSAP APO releases:

SAP Basis / SAP Web ApplicationServer Release

SAP APO / SAP SCM Release

4.6A 2.0A

4.6C 3.0A

4.6D 3.1 / 3.1 SR1

6.20 4.0

SAP Basis and SAP Web Application Server

Release 6.10 renames the SAP Basis Component as the SAP Web Application Server. In thisdocumentation the term SAP Basis(or the abbreviation Basis) is used when referring toRelease 4.6D and lower, and SAP Web Application Server(or the abbreviation SAP Web AS)when referring to Release 6.10 and higher.

SAP SCM System and SAP System

In this documentation, the term SAP systemis the same as SAP SCM system. SAPis alsoused as a synonym for SAP SCM in terms such as SAP start profileor SAP system language.

10 September 2003


11/232

1 Introduction

SAP System ID

In this documentation, the SAP system ID is abbreviated as SAPSIDor sapsid. If isused, your SAP system ID must be in lowercase letters, for example prd. If isused, you must write in uppercase letters, for example PRD.

ID for the SAP Web Application Server Release

In this documentation, stands for the relevant SAP Web Application Server release,without a decimal point, such as 620.

Support Packages and Patches

As of Release 4.6, SAP uses the term Support Packagesinstead of SAP patches. HotPackagesare now called R/3 Support Packages, and Legal Change Patchesare called R/3HR Support Packages. There are other types of Support Packages, such as Basis SupportPackagesorAdd-On Support Packages.

IBM DB2 Universal Database for UNIX and Windows and Abbreviations

In this documentation and in the upgrade dialogs, the short form DB2 UDBfor UNIX andWindowsis used for the database IBM DB2 Universal Database for UNIX and Windows, and,in certain cases, the SAP ID DB6is used as well. In previous versions of this documentation,IBM DB2 Universal Database for UNIX and Windows was referred to asDB2 UniversalDatabase for UNIX, Windows.

IBM DB2 Universal Database for OS/390 and z/OS and Abbreviations

In this documentation and in the upgrade dialogs, the short form DB2 UDB for OS/390isused for the database IBM DB2 Universal Database for OS/390 and z/OS, and in certaincases, the SAP ID DB2is used as well.

z/OS CI Host and AIX CI Host

This documentation describes the host computers as AIX central instance hosts (AIX CI host)and z/OS central instance hosts (z/OS CI host). This means you can distinguish between theAIX host and the z/OS host if your source release is lower than 4.6A.

September 2003 11


12/232

1 Introduction

1.2 How to Use this DocumentationThe documentation on upgrading the SAP system contains a large amount of information. Itsaim is to give you both the information you need immediately at your fingertips, as well asproviding additional background information when required. Treat the documentation as apool of information.

If you have a lot of experience in upgrading the SAP system, you will probablyonly need the parts Upgrade Step by Step [page 18], Product-SpecificInformation [page 34]and SAP Notes for the Upgrade [page 29].

Structure of the Documentation

Product

Specific

Information

Introduction

Upgrade Documentation

Upgrade - Step by Step

Minimuminformationrequired

Legend:

General

Upgrade

Information

Connected withlinks

Additionalinformation

SAP Notes

Additional Information:

TroubleshootingUpgrade Administration

Upgrade Tools

The documentation consists of the following parts:

!

IntroductionThe first sections of this documentation are as follows:

! New Features in the SAP SCM Upgrade [page 14]

! Naming Conventions for the SAP SCM Upgrade [page 10]

They contain information on new features in the upgrade for the last few releases, andon the naming conventions used in the documentation.

! Upgrade Step by Step [page 18]

This section is the core of the documentation. It is a list of all actions that you mustperform to upgrade your system successfully The short descriptions of the individualactions contain the following:

12 September 2003


13/232

1 Introduction

! Important information, such as user entries

! Links to a detailed description of the action

! Links to any product-specific information about the action

The upgrade actions are listed chronologically. Use the Upgrade Step by Step[page 18]section as a checklist for upgrading the system. This ensures that youdo not miss important information.

Use the links to the general descriptions of the actions and to any additionalproduct-specific information to help you perform the actions.

! SAP Notes for the SAP SCM Upgrade [page 29]

This section contains a list of SAP Notes relevant for the upgrade.

! Product-Specific Information for the SAP SCM Upgrade [page 34]

This part of the documentation contains additional information or restrictions on thedescriptions in General Upgrade Information, which only affect this specific SAPproduct.The headings of the sections are the same as the corresponding sections in GeneralUpgrade Information. Each product-specific text contains a link to the generaldescription of the action.

The information in the product-specific part takes priorityover the information inthe general part of the documentation.

! General Upgrade Information [page 66]

This part of the documentation is a general description of the upgrade of an SAPsystem. It contains procedures and background information about the upgrade processflow and the individual actions. However, it does not contain all the information youneed for the upgrade of your specific SAP product. For information on any extra detailsabout the upgrade of your product, see the Product-Specific Information [page 34].

! Additional Information [page 188]

This part of the documentation contains three sections:

! Troubleshooting [page 188]

! Upgrade Administration [page 213]

! Upgrade Tools [page 225]

These sections contain information on troubleshooting, the administration tasks youneed to perform before and after the upgrade, and the tools that you use to upgradethe system.

Use the links from section Upgrade Step by Step [page 18]to the general descriptions ofthe actions and to any additional product-specific information to help you perform the actions.

September 2003 13


14/232

1 Introduction

1.3 New Features in the SAP SCM Upgrade

New Features in the Upgrade Based on SAP Web Application Server

6.20! DB2 UDB for OS/390 and z/OS: Supported operating systems during the upgrade

The complete upgrade, including PREPARE, has to be performed on z/OS USS orWindows. AIX, zLinux, and Solaris are notsupported.

For more information, see specific information in the DB2 UDB for OS/390 and z/OSsections in this documentation, especially under Upgrade of the Operating System andDatabase System: Overview [page 41]#Important Information, as well as SAP Note580989.

! For Oracle only: Early creation of secondary indexes

With strategy downtime-minimized, some of the secondary indexes will already be

created during uptime. This applies to secondary indexes that are new in the targetrelease and whose fields already exist in the source release. The background job thatcreates the indexes will not lock the tables concerned.

! Phase list for the upgrade in HTML format

The phase list [page 222]is no longer part of the upgrade documentation. Instead, it iscontained in the htdocsubdirectory of the upgrade directory in the form of HTML files.You can also create the phase list yourself by using the htmlphloption to call R3up.

! Reading the upgrade CDs

The contents of the upgrade CDs are read using a new procedure. You have to installa Java Development Kit (JDK) on the host where the upgrade is performed, and youhave to adjust certain environment variables.

! New procedure for dealing with add-ons

In the I S_SELECTphase, you can also include SAINT packages in the upgrade thatyou put into the transport directory before the upgrade.

! Calculating an add-on queue

If you made a decision for all add-ons in the I S_SELECTphase, a new queuecalculation is triggered. This calculation checks whether the import prerequisites can bemet for the add-ons, and determines the sequence in which the correspondingrequests are imported.

! New functions for including Support Packages

To import Support Packages in the BI ND_PATCHphase, the following SupportPackage levels are determined and taken into consideration for each component:

a. Minimum required Support Package level

Support Package level that the included add-ons of the target release require asan import prerequisite. The add-on queue calculation determines the minimumrequired Support Package level.

You are not allowed to select a Support Package level that is lower than theminimum level.

b. Equivalence Support Package level

You can define attributes for the Support Packages of the source release that

determine which Support Package in a higher release corresponds to the one in

14 September 2003


15/232

1 Introduction

the source release. This Support Package must be included so that no data islost in the upgrade.

PREPAREdetermines this equivalence Support Package level in thePATCHK_EQUI phase.

The minimum and the equivalence Support Package level for each component aredisplayed on the dialog box (wizard).

! Restrictions for an upgrade without changing the software layer SAP BASIS

When you upgrade from a source release based on SAP Web Application Server 6.20,for example, when you upgrade the SAP Event Manager, the releases of the softwarecomponents SAP_BASIS and SAP_ABA remain unchanged.

If required, you can include additional Support Packages for these softwarecomponents. As with all other Support Packages, the level of the Support Packagesbound to the upgrade must be higher than the current Support Package level.

There may be add-ons in your system, which refer to software components that did not

undergo a release change during the upgrade. If one of these add-ons already has amore up-to-date version than the version on the CD shipped by SAP, then the add-oninstalled on the system is automatically copied and kept. However, you can alsoinclude an additional update for the add-on.

! Including a SPAM update

In the BI ND_PATCHphase you can include a SPAM update for the target release.

! Conflict check

To check whether the add-on requests and CRTs are complete, PREPAREtriggers aconflict check. You are then prompted to include the corresponding CRTs for theincluded add-ons, if necessary.

! ModificationsThe procedure for copying modifications to the standard SAP system has changed.Modified objects, that belong to software components whose release does not changeduring the upgrade are copied automatically and therefore do not need to be adjustedagain. Modified objects, that belong to software components that are being upgradedare no longer copied automatically. Instead, all of these modifications are offered foradjustment, including modifications to objects, that are deleted by the upgrade and thatare not shipped by SAP in a more up-to-date version.

This new procedure may cause more objects to be offered in the modificationadjustment than was previously the case. Customer objects are not affected by thischange and are retained as usual.

Important Changes before SAP Web Application Server 6.20! Changed structure of the upgrade documentation

To make it easier to access important information, the structure of the upgradedocumentation has been changed in many places. Instead of describing the processflow of the upgrade, the documentation is now structured as an information pool. Thedescription of the upgrade procedure as been split into two areas, a product-specificpart and a general description. The section Upgrade Step by Step [page 18]is yourcentral guide and summary of the upgrade.

The information in the product-specific part takes priorityover the information in

the general part of the documentation.

September 2003 15


16/232

1 Introduction

For more information, see How to Use this Documentation [page 12].

! New upgrade procedure

The new System Switch Upgrade installs an instance of the target release, the shadow

system, in parallel with the current source release system in the same database. Thisparallel system contains all the software of the target release and is used to integrateSupport Packages that are included in the upgrade, add-ons, and customermodifications into the target release.

In the production database, the tables of the target release that contain both thedescriptions of the ABAP Dictionary and the ABAP programs are imported as shadowtables under an alternative name. The shadow system enables you to access thesetables. Depending on the upgrade strategy you choose, you can perform upgradeactions before downtime starts that previously had to be performed during downtime.

You can choose between two upgrade strategies in the System Switch Upgrade. Thedowntime-minimizedstrategy enables you to run the production system and shadowsystem in parallel. This requires extra system resources, but reduces downtime. The

resource-minimizedstrategy only enables you to run either the production system orthe shadow system. This strategy requires no extra system resources. However thedowntime is longer, since you can only run the shadow instance during downtime.

In the new procedure, the archiving strategy for the database is no longer coupled withthe upgrade strategy. However, you should use the recommended archiving strategiesexcept in certain cases.

! New command for starting and stopping the SAP system

The command for the SAP system start and stop procedure has changed in SAP WebApplication Server 6.10. Up until the ENVCHKphase, the SAP system is started andstopped with the old commands. As of the KX_SWI TCHphase, you can start the SAPsystem with command startsap r3 DVEBMGS, and stop it

with command


17/232

1 Introduction

that Add-On Patches (AOPs) and Conflict Resolution Transports (CRTs) are importedconsistently.

! Mass activation of ABAP Dictionary objects

The mass activation of ABAP Dictionary objects is performed in parallel. Thedependencies among the ABAP Dictionary objects do not allow multiple activationprograms to be started as background jobs in parallel, unlike other tools (such as theconversion program). The objects are sorted by their dependencies and split intodifferent levels. These levels are then activated in sequence, with each of the levelsbeing made parallel with asynchronous RFC.

The number of parallel processes is controlled by the work process resources and theestimated capacity needed to activate the objects in one level.

The minimum number of dialog processes needed to start mass activation of Dictionaryobjects in parallel is 6. The upgrade tools automatically make this resource available ifat least three background processes are permitted for the upgrade.

! Language transport

The technical basis of the language transport has been changed completely.Languages are now imported with the transport programs R3t r ansand t pas part ofthe table import phases. This makes the separate language import phases obsolete.

For information on the language transport, see the SAP online documentation underHelp#SAP Library#SAP Web Application Server#Change and Transport System#Language Transport.

! Shadow import

To minimize the longer downtimes caused by including transport requests, shadowimports are used as of Release 4.6B when upgrading the SAP system. For theA_switchandA_onstrategies (corresponds to the downtime-minimizedstrategy as of

Release 6.10), the transport requests for Support Packages, Industry Solutions, andthe modification adjustment are now imported into the SAP system during productionoperation. The import (ABAP Dictionary and main import) is not made into the originalRepository (source release). Instead it occurs in the shadow Repository (newRepository of the target release), which is loaded into the SAP system during theEU_I MPORTphase. This shadow import is performed in the SHADOW_I MPORT_ALLupgrade phase.

New technology implemented in R3t r ans allows you to use the shadow import andinclude the transport requests during production operation. This technology will also beused in other cases to minimize upgrade downtime as much as possible.

September 2003 17


18/232

2 Upgrade - Step by Step


Purpose

If you have a lot of experience in upgrading the SAP system, you will probablyonly need the parts Upgrade Step by Step, Product-Specific Information [page34]and SAP Notes for the Upgrade [page 29]. All other sections containadditional information on the upgrade, troubleshooting, and administration tasks.

This section is constructed as a checklist and contains all the actions you need to do:

! Find SAP Notes [page 29]

! Plan the upgrade (SAP SCM-specific [page 35]/ general [page 67])

! Prepare the upgrade (SAP SCM-specific [page 46]/ general [page 96])

! Upgrade the SAP system (SAP SCM-specific [page 54]/ general [page 141])

! Perform post-upgrade activities (SAP SCM-specific [page 63]/ general [page 159])

The actions are placed in chronological order, so that you can work through them just like achecklist. Use the links to the general descriptions of the actions and to any additionalproduct-specific information to help you perform the actions.

The last part of this documentation,Additional Information [page 188], contains three sectionswith information on how to proceed with errors, perform administration tasks and use theupgrade tools:

! Troubleshooting [page 188]

! Upgrade Administration [page 213]

! Upgrade Tools [page 225]

Process Flow

SAP Notes for the Upgrade

This upgrade documentation is enhanced and updated by SAP Notes in SAPNet R/3Frontend. These SAP Notes are an important source of information when you plan andprepare your upgrade, and also help you perform the actual upgrade.

Action

You request the current SAP Notes for the upgrade [page 29]. You require at least thefollowing SAP Notes:

! General UpgradeNote 603852

! The relevant database-specific SAP Note:

! 490095(DB2 UDB for UNIX and Windows)

! 603278(DB2 UDB for OS/390 and z/OS)

! 486274(Informix)

! 575280(Oracle)

! 490325(SAP DB)

18 September 2003


19/232


Upgrade Planning

Before you start the actual upgrade, you must plan it carefully so that downtime is reduced toa minimum, and the upgrade runs as efficiently as possible.

The Upgrade Planningpart of this documentation contains additional SAP SCM-specific[page 35]and general [page 67]information.

Action

You can upgrade the front-end software [page 68]as soon as you receive the softwarepackage.

You familiarize yourself with the features of the System Switch Upgrade [page 69]andits effect on the way you upgrade the system.

You decide on an upgrade strategy, taking into account your operating system anddatabase upgrade (SAP SCM-specific [page 35]/ general [page 72]).

You define an archiving strategy [page 75]for your database. Before you backup yourdatabase during the upgrade, stop the CIF queues [page 35].

Before you start the upgrade, you check the database-specific aspects [page 76]andinclude them in your upgrade schedule, if necessary.

You check whether your system is an MCOD system [page 78].

You plan the incremental table conversion [page 79], if necessary.

You plan the upgrade schedule (SAP SCM-specific [page 36]/ general [page 81]).

Depending on your chosen upgrade strategy, you plan the runtime for the import of thesubstitution set (SAP SCM-specific [page 37]/ general [page 83]).

You decide on the sequence of upgrades in your SAP system group [page 84].

You plan the modification adjustment [page 85], if necessary.

You plan the upgrade of the liveCache and the Optimizer [page 38].

You plan the backup of DP AND SNP time series in InfoCubes [page 37], if necessary.

You plan the definition of Global ATP bucket limits [page 37], if necessary.

You check the structural requirements [page 87].

You check the hardware requirements (SAP SCM-specific [page 39]/ general [page87]):

! CPU, main memory and swap space see SAP Service Marketplace underservice.sap.com/quicksizing

! UNIX kernel parameters according to SAP Software on UNIX OS Dependencies

! Disk space in the file system for the upgrade directory: about 1,400 MB

! Space requirements in the database:

! DB2 UDB for UNIX and Windows: See SAP Note 603852

! DB2 UDB for OS/390 and z/OS: See SAP Note 603280

! Informix: See SAP Note 603852

! Oracle: See SAP Note 603852

! SAP DB: See SAP Note 603852

September 2003 19


20/232


You check the software requirements [page 88].

! Source release of the SAP system (SAP SCM-specific [page 40]/ general [page88]):3.0A SR33.1 SR1

! Upgrade Assistant [page 89]: Java Virtual Machine (at least Version 1.3.x)

! Operating system [page 90]:

AIX: AIX per f agent package must be installed

HP-UX and HP-64: at least HP-UX 11 with 64 bit

z/OS UNIX System Services: At least z/OS Version 1.2

DB2 UDB for OS/390 and z/OS: The complete upgrade, including

PREPARE, has to be performed on z/OS USS or Windows. AIX, zLinux,and Solaris are notsupported. For more information, see Upgrade of theOperating System and Database System: Overview [page 41]#ImportantInformationand SAP Note 580989.

! liveCache [page 41]: at least Version 7.2.05.15;If you are using AIX 5.1: at least Version 7.4.02

You plan or perform the upgrade of the operating system and database system, ifnecessary (SAP SCM-specific [page 41]/ general [page 92]):

! For the operating system requirements, see the SAP Service Marketplace atservice.sap.com/platforms.

! Database version:

$ DB2 UDB for UNIX and Windows

At least Version 7.2, FixPak 8; migrate before PREPARE

$ DB2 UDB for OS/390 and z/OS:

At least Version 6.1.0; migrate before PREPARE

$ Informix

See SAP Note486274; migrate before PREPARE

$ Oracle

At least Version 9.2.0, for detailed information, see SAP Note

407314migrate before PREPARE

$ SAP DB

At least Version 7.4.03.020; migrate before PREPARE

You meet the requirements for installing the online documentation [page 93]asdescribed in the documentation Installing the SAP Library.

You meet the requirements for the SAP Internet Transaction Server and theSAP@Web Studio [page 93]according to the SAP@Web Installation Guide, ifnecessary.

You meet the requirements for importing additional languages [page 94], if necessary.

20 September 2003


21/232


Upgrade Preparations

You can prepare for the upgrade while the system is in production operation. The PREPARE

program supports you here by making most of the necessary checks automatically. StartPREPAREas soon as possible before the upgrade so that you can initiate or perform thenecessary preparations in time.

The Upgrade Preparationspart of the documentation contains additional SAP SCM-specific[page 46]and general [page 96]information.

Preparations for PREPARE

Action

You choose the host [page 97]for PREPAREand the Upgrade Assistant.

You make preparations for reading the upgrade CDs [page 98].

You create an empty upgrade directory on the host with the central instance (SAPSCM-specific [page 46]/ general [page 98]):

! With admas owner

! With a total of 1400 MB free disk space

! DI R_PUThas the value in the instance profile of thecentral instance.

! If you have made a lot of customer developments, include approximately 20%extra space in the file system. Also do this if you want to include SupportPackages and add-ons.

! If you want to import languages other than English and German, provide an extra

150 MB of memory in the file system for each language.

! z/OS UNIX System Services: Among other things, use a local file system.

You check the database-specific prerequisites for PREPARE(SAP SCM-specific [page47]/ general [page 100]). Among other things, the following free space must beavailable:

!

!

!

DB2 UDB for UNIX and Windows, DB2 UDB for OS/390 and z/OS, Oracle: 500 MB

Informix: At least 200 MB

SAP DB: 800 MB (corresponds to 100,000 pages)

You perform the preparations for the SAP BW-specific objects [page 47].

You convert inconsistent characteristic values [page 48].

You import the latest SPAM update [page 100].

Actions for Starting PREPARE

Action

When you start PREPAREfor the first time, you must start it from the CD.......

1. You start PREPARE from the Upgrade Master CD [page 101]as useradmon the host with the central instance.

September 2003 21


22/232


2. You start the Upgrade Assistant server [page 102].

3. You start the GUI of the Upgrade Assistant [page 103].

4. You start the Upgrade Assistant [page 104].

If you want to restart PREPARE [page 105], for example, if the results from its first runmake you want to repeat some checks, you can execute it directly.

You can reset PREPARE [page 106]at any time.

If you need extra software after starting PREPARE, you import it now [page 106].

PREPAREneeds certain information from you so that it can run the modules. If possible,default values appear that you can confirm or change. For a complete list of all PREPAREmodules and phases, see Using the Phase List for the Upgrade [page 222].

User Actions During PREPARE

Action

You make the entries for the Parameter Inputmodule (SAP SCM-specific [page 49]/general [page 106]). This includes entering CD mount directories. You require thefollowing CDs for PREPARE:

CD Upgrade Master CD, CD SAP Kernel, upgrade CDs 1 - 4, language CD(s), anyadd-on CD(s)

You make entries for the Initialization module [page 114].

! You check the version of SAP Kernel, t p, and R3t r ans.

! You check the SAP Notes for the add-ons.

! DB2 UDB for OS/390 and z/OS: Among other things, you create or extendstogroups, if necessary.

You make entries for the Import module [page 116].

You make the entries for the Extensionmodule (SAP SCM-specific [page 50]/ general[page 116]), such as including Support Packages.

You make the entries for the Installation module [page 125], such as the instancenumber and the port numbers for the shadow system.SAP DB: If necessary, you change the database parameters MAXUSERTASKSandMAXLOCKS.

You make entries for the General Checks module [page 50].

If you are using Characteristics Dependent Planing, check log fileMC01_CACL_CDP_CONSI ST. .

You make entries for the Necessary Checks for Conversion Module [page 50].

You execute report /SAPAPO/OM_LC_UPGRADE_3X_40 and perform at least allmandatory activities of section A to prepare the upgrade of the SAP liveCache.

22 September 2003


23/232


Checks Not Supported by PREPARE

Action

You evaluate the results of PREPARE [page 127]in the log file CHECKS. LOG.

You make preparations at the operating system level [page 135]:

! You make a backup copy of the old SAP kernel.

! If changes are made to the standard SAP system, you back up the SAP start andstop scripts.

! You make the operating system-specific preparations.

You make preparations at the database level [page 135].

! You make sure that you can recover the database to the state it had before theupgrade.

!

You make the database-specific preparations.You make preparations at the SAP system level.

! You make preparations for using Global ATP [page 52].

! You make sure that user DDIC [page 138]can log on to client 000.

! You make sure that the requirements for the modification adjustment [page 138]have been met.

! You call transaction RZ04 to set the operation mode [page 138]for the upgrade.

! You import the new front-end software [page 68], if necessary.

! You make preparations for the use of Workforce Management [page 53], if

necessary.

The Upgrade

TheUpgradepart of the documentation contains additional SAP SCM-specific [page 54]andgeneral [page 141]information.

For a complete list of all the upgrade phases, see the htdocsubdirectory of the upgradedirectory. For details about the procedure, see Using the Phase List for the Upgrade [page222].

Action

You check the General Upgrade Note and your database-specific SAP Note for newinformation and changes [page 29].

You choose the host for the upgrade [page 97].

You get the following CDs [page 49], if you have not already mounted them:

Upgrade CDs 1-4, any language CD(s)

You start R3up [page 143]from the central instance as user adm.

If errors occur, you can stop [page 143]and restart [page 144]the upgrade.

Phase INITPUT [page 145]:

You enter the system-specific parameters.

September 2003 23


24/232


25/232


Before you perform a database backup, stop the CIF queues [page 56].

All EU_I MPORTphases (SAP SCM-specific [page 56]/ general [page 151]):

If the relevant CD is not mounted on one of the specified mount directories, you are

prompted to change the CD.

Phase REPACHK2 [page 152]:

! You release and confirmall open repairs in this phase at the latest.

! For downtime-minimized: You lock the ABAP Workbench in this phase at thelatest.

Phase CNV_CHK_XT [page 152]:

You process any uncompleted conversion requests and restart logs.

Phase ADJUSTCHK [page 153]:

Modifications: You confirm the request, if necessary.

Phase START_SHDI _FI RST:

As of this phase you can only log on with the new front-end software [page 68].

Phase ACT_ [page 153]:

Modifications: You adjust modified SAP objects with the SAP standard versions.

Phase VIEWCHK2 [page 155]:

You remove conflicts between customer tables and new views by deleting thecustomer tables in this phase at the latest.

Phase MODPROF_TRANS (SAP SCM-specific [page 62]/ general [page 155]):

! For downtime-minimized: You isolate the central instance, stop the applicationservers and change the database recovery mode, if necessary. Also make surethat you can recover the database to its current state.Before you perform a database backup, stop the CIF queues [page 62].

! You back up the upgrade directory.

! You check the percentage of tables converted in transaction ICNV, if necessary.

Phases JOB_RSVBCHCK_R and JOB_RSVBCHCK_D [page 156]:

You clean up outstanding updates and outbound queue RFC calls in this phase at thelatest.

Phase ENVCHK [page 156]:

You repeat any changes made to the environment of user admbefore theupgrade, if necessary.

Phase REQ_LCUPG [page 57]:

You upgrade the liveCache to at least version 7.4.03.019.

You change the bucket limits, if necessary.

You initialize SAP liveCache and load transaction data using report/SAPAPO/OM_LC_UPGRADE_3X_40 section C.

You upgrade the APO Optimizer.

Phase MODPROFP_UPG [page 157]:

In the phases MODPROFP_UPG, STARTR3_PUPG, and CHK_POSTUP you perform the

September 2003 25


26/232


following actions:

! You back up the database.

! You determine P errors.

! You change the database recovery mode.

! You start the secondary application servers.

Phase CHK_POSTUP [page 158]:

Remove the P errors before you restart production operation of the system.

Post-Upgrade Activities

The Post-Upgrade Activitiespart of the documentation contains additional SAP SCM-specific[page 63]and general [page 159]information on how to proceed after R3up has finished.

R3upstops at the latest in the MODPROFP_UPGphase and prompts you to start the post-upgrade activities. R3upthen executes the last phases and completes the upgrade. At thesame time you can perform the post-upgrade activities specified by R3up.

Actions Before Restarting Production Operation

Action

You execute the saproot.sh script [page 161].

You perform the database-specific actions:

! DB2 UDB for UNIX and Windows [page 163]:You install or update the DB2 Admin Tools, switch on log archiving, back up thedatabase, delete substitution tablespaces, update statistics, and schedule updatestatistics jobs.

! DB2 UDB for OS/390 and z/OS [page 165]: You back up and reorganize thedatabase and update statistics, import correction transports, and adjust memoryattributes of new tables.

! Informix [page 167]: You delete the dbspaces and back up the database.

! Oracle [page 168]:You create or update the SAPDBArole, check the environment variables forSAPDBA, add new parameters to the profile i ni t . sap, and back up thedatabase.

! SAP DB [page 170]: You set the database parameters to their pre-upgrade state

and restore the ability of the database to be recovered.If there is no central software storage point: You distribute the SAP programs [page170].

You use transaction RZ10 to check the profile parameters [page 172]and reset themto their default values, if necessary.

You reimport additional programs [page 172]such as RFC-SDK or CPIC-SDK from thePresentationCD, if necessary.

You call transaction SPAU to adjust modifications to Repository objects [page 173], ifnecessary.

You perform actions for SAP liveCache [page 63].

26 September 2003


27/232


You perform application-specific post-upgrade activities (SAP SCM-specific [page 63]/general [page 173]).

! You restart the CIF queues.

! You retransfer the classes master data.

! You check application Release Notes for specific post-upgrade activities.

! You perform upgrade and delta Customizing activities, if necessary.

! You adjust the initial menu.

! Source Release 3.0: You adjust SNP Optimizer profile.

! You adjust your own developments,if necessary.

You can perform the following post-upgrade activities during limited production operation[page 159]of the system.

Actions After Restarting Limited Production Operation

Action

You reschedule background jobs [page 174]whose release you reset when youisolated the central instance.

You perform database-specific actions:

! Informix [page 176]: You update statistics.

! Oracle: You perform actions for the Cost-Based Optimizer [page 176].

! SAP DB [page 178]: You update the optimizer statistics.

You call transaction SGEN to generateABAP loads [page 178].

You call transaction SGEN to generate the BSP applications [page 179], if necessary.

You perform actions for the online documentation [page 179]as described in thedocumentation Installing the SAP Library.

You install the SAP Internet Transaction Server [page 93]and the SAP@Web Studioas described in the documentation SAP@Web Installation, if necessary.

You perform post-upgrade authorization activities [page 180].

! You adjust the assignments between check flags and transactions.

! Upward compatibility for authorization checks: You adjust SAP_NEW.

! You handle problems with user buffers.

You use SAPinst to install more dialog instances [page 182], if necessary.

You can perform the following post-upgrade activities during normal production operation ofthe system.

Actions After Restarting Production Operation

Action

You import Support Packages [page 182], if necessary.

If you want to install additional languages, you import them before you import the

September 2003 27


28/232


Support Packages as described in the language transport documentation.

Transport Management System (TMS) [page 182]: You distribute the configuration toall systems in the transport domain.

Language transport [page 183]: You copy glossary and terminology data fromcontainer tables to database tables.

You perform database-specific actions:

! DB2 UDB for OS/390 and z/OS [page 184]:You remove database objects that you no longer need.

! Oracle: You delete old tablespaces [page 184].

You convert old batch input logs [page 185]to the new procedure in all clients, ifnecessary.

You make a backup of the subdirectory containing the shadow instance profiles [page185], if necessary.

There are some post-upgrade activities that you do not need to perform directly after theupgrade. You can leave these activities until later.

Action

You send the evaluation of the runtime of the upgrade [page 186]to SAP.

About four weeks after the upgrade, you execute report/SAPAPO/OM_LC_UPGRADE_3X_40 section D [page 65]to delete the tablecontaining the download data.

28 September 2003


29/232

3 SAP Notes for the SAP SCM Upgrade


Definition

To prepare and perform the upgrade of your system, you require some additional information,not included in the documentation. This information is in a range of SAP Notes in SAPNet R/3 Frontend, some of which you must read before you prepare the upgrade. The generalUpgrade Note contains current cross-database information on preparing the upgrade. Thereare separate SAP Notes for the database-specific sections. When you actually upgrade theSAP system, you need information from some additional SAP Notes. These SAP Notes arenamed at the appropriate places in this documentation.

SAP Notes for Preparing the Upgrade

You must request the following SAP Notes from SAPNet R/3 Frontend before you start yourupgrade: the general upgrade note and the note for your database. Since these SAP Notesare updated regularly, make sure you always use the newest version. The following list

contains the SAP Notes you needto prepare for the upgrade:

SAP Note Number Database SAP Note Type

603852 Upgrading to SAP SCM 4.0:Additional Information

SCM-specific/specific to this upgrade

490095 DB2 UDB for UNIX andWindows

DB2 UDB for UNIX and Windows-specific/specific to this upgrade

603278 DB2 UDB for OS/390 andz/OS

DB2 UDB for OS/390 and z/OS-specific/specific to this upgrade

486274 Informix Informix-specific/specific to this

upgrade

575280 Oracle Oracle-specific/specific to thisupgrade

490325 SAP DB SAP DB-specific/specific to thisupgrade

599468 Additional information aboutupgrading to liveCache 7.4.3

liveCache-specific/specific to thisupgrade

Keyword for the Upgrade

When you start the upgrade, you are asked to enter a keyword, which you can get from thecurrent general Upgrade Note 603852. You cannot start the upgrade until you have enteredthe keyword.

Other SAP Notes

As well as the SAP Notes you need for preparing for the upgrade, this documentation alsorefers you to other SAP Notes that contain additionalinformation. The following list containsthese SAP Notes, organized by database:

September 2003 29


30/232


SAP Notes for All Databases

SAP NoteNumber

Description SAP Note Type

487261 Blocking R/3 data transfer during SNP,CTM, PP/DS

SCM-specific

528913 Lock R/3 data transfer during SNP, CTM,PP/DS

SCM-specific

505304 Disk space for Core interfacecommunication

SCM-specific

436949 Upgrading the APO 3.0 SNP optimizer toAPO 3.1/4.X

SCM-specific

573512 Upgrade from APO 3.1 to SCM 4.0 forSNP Optimizer

SCM-specific

426806 Memory problems when extracting data SCM-specific

26417 SAP GUI resources: Hardware andsoftware

Front end/SAP GUI

102461 Installation of a 4.0B_COM kernel SAP kernel

318846 Installation of a 4.6D kernel SAP kernel

83458 Downloading Support Packages from theSAP Service Marketplace

SAP Support Packages

125971 Service connection in Upgrade Assistant inSAPNet R/3 Frontend

Remote support for upgrade

133402 Using the Upgrade Assistant withSAProuter

Upgrade Assistant

62519 Correction locks do not belong to system Workbench Organizer

51046 Copying the modification adjustmentwithout a central transport directory

Change and Transport System

96905 Error message TG063 in the upgradephaseJ OB_RADDRCHK

ABAP Dictionary

97032 Conversion of address tables, runtime Address management

82167 Conversion of address tables, runtime Address management

24864 No conversion of table BSEG ABAP Dictionary/phasePARCONV_UPG

10187 User buffer too small User administration

197746 Maintenance Strategy Internet TransactionServer (ITS)

SAP@Web

399578 Publishing IAC objects on the ITS after theupgrade

SAP@Web

86627 Transaction types: Customizing for releaseupgrades

Customizing

482462 Current Note on the 6.20 language import Language transport

30 September 2003


31/232


352941 Language import and Support Packages Language transport

322982 Install language during upgrade Language transport

485741 Dealing with customer translations in the

upgrade

Language transport

73999 Upgrade phase PARDI ST_SHD: TG450 toTG453

General upgrade

177680 Correcting conversion problems in thePARCONV_UPGphase

General upgrade

417670 Additional information about resetting theupgrade

General upgrade

186066 Increased free space requirements duringthe upgrade

General upgrade

493387 Potential effects of changes to table and

structure extensions

Activation

490788 ICNV in the upgrade to SAP Web AS 6.20 ICNV

430318 Shadow instance on another operatingsystem

General upgrade

94998 Requesting a license key for a system General upgrade

175596 Switch to a new batch input log General upgrade

122597 Ignore errors in the XPRAS_UPGphase General upgrade

367676 Upgrade from 4.6 to 6.10 for customerprograms

Adjusting customerdevelopments

452229 Upgrade from 6.10 to 6.20 for customerprograms

Adjusting customerdevelopments

SAP Notes for liveCache

SAP NoteNumber


533076 Importing a liveCache version as of 7.2.5B15

liveCache-specific

492320 SAPAPO 3.0 COM object Build 28 liveCache-specific

500843 Composite SAP note for COM and SAPliveCache 7.2 or higher

liveCache-specific

496318 Parameter values as of liveCache version7.4.2

liveCache-specific

337445 liveCache and storage management liveCache-specific

487972 Operating system parametrization ofliveCache

liveCache-specific

September 2003 31


32/232


SAP Notes for DB2 UDB for UNIX and Windows

SAP NoteNumber


407322 Released operating systems for SAPKernel 6.x DB2 UDB

DB2 UDB for UNIX andWindows-specific

455506 DB6: Installation of latest admin tools 6NNDB2

DB2 UDB for UNIX andWindows-specific

SAP Notes for DB2 UDB for OS/390 and z/OS

SAP NoteNumber


407325 Released operating systems for SAP kernel

6.x DB2/390

DB2 UDB for OS/390 and

z/OS-specific

81737 DB2/390: APAR list DB2 UDB for OS/390 andz/OS-specific

183311 DB2/390: Automatic PTF Check DB2 UDB for OS/390 andz/OS-specific

113008 DB2/390: Maintaining catalog statistics DB2 UDB for OS/390 andz/OS-specific

103135 DB2/390: Manual saposcol installation DB2 UDB for OS/390 andz/OS-specific

122599 DB2/390: Performance of the update DB2 UDB for OS/390 and

z/OS-specific

434946 DB2/390: R3szchk & R3ldclt for upgrade to>= 6.10

DB2 UDB for OS/390 andz/OS-specific

184399 DB2/390: DDIC corrections (4.6A, 4.6B,4.6C, 4.6D)


407663 DB2/390: DDIC corrections (6.10, 6.20) DB2 UDB for OS/390 andz/OS-specific

603280 DB2/390: Upgrade to SCM 4.0 - free space DB2 UDB for OS/390 andz/OS-specific

400565 DB2/390 Upgrade: Optional checks DB2 UDB for OS/390 and

z/OS-specific

493577 DB2/390: Transports for 6.20 DB2 UDB for OS/390 andz/OS-specific

529267 DB2/390: Upgrade to 6.x Troubleshooting DB2 UDB for OS/390 andz/OS-specific

569821 DB2/390: MCI upgrade DB2 UDB for OS/390 andz/OS-specific

580989 DB2/390: Upgrade to 6.x on non-z/OSUNIX systems


32 September 2003


33/232


SAP Notes for Informix

SAP NoteNumber


50157 Using recommended versions of Informix Informix-specific

407317 Released operating systems for SAP kernel6.x Informix

Informix-specific

22941 Reorganization of tables and dbspaces Informix-specific

115619 Informix Client versions Informix-specific

SAP Notes for Oracle

SAP NoteNumber


407314 Released operating systems for SAPkernel 6.x Oracle

Oracle-specific

11777 Changing the storage parameters NEXTand MAX EXTENTS

Oracle-specific

16951 Oracle - Problems with Rollback segments Oracle-specific

406140 Installation of the Oracle Client Software Oracle-specific

521230 FAQ: Oracle Client Software on UNIX Oracle-specific

SAP Notes for SAP DB

SAP NoteNumber


407320 Released operating systems for SAPKernel 6.x SAP DB

SAP DB-specific

528433 SAP DB release upgrade to 7.3.00 Build028

SAP DB-specific

34690 Add Devspace under SAP DB (ADABASfor R/3)

SAP DB-specific

46430 SAP DB load with parallel R3LOADS SAP DB-specific

201388 Change a database parameter in SAP DBRelease

SAP DB-specific

201390 Back up the database SAP DB SAP DB-specific

352081 Additional functions relevant to services forSAP DB

SAP DB-specific

362542 Analysis of table sizes and growth SAP DB-specific

September 2003 33


34/232

4 Product-Specific Information for the SAP SCM Upgrade

4 Product-Specific Information for the SAPSCM UpgradeThis part of the documentation describes the information and restrictions specific to anupgradeof the SAP SCM system.

Among other things, this includes SAP SCM upgrade-specific directory sizes, database andoperating system versions, as well as restrictions on and additions to the general upgradeprocedure.

The information in the product-specific part takes priorityover the information inthe general part of the documentation.

This part of the documentation has a similar structure to the General UpgradeInformation [page 66]. The same section headings contain comments, additionalinformation or restrictions on the upgrade. Each product-specific text contains alink to the description of the procedure in the general part of the documentation.

The following parts of the documentation contain additional information:

! SAP SCM: Upgrade Planning [page 35]

! SAP SCM: Upgrade Preparations [page 46]

! SAP SCM: The Upgrade [page 54]

! SAP SCM: Post-Upgrade Activities [page 63]

34 September 2003


35/232


4.1 SAP SCM: Upgrade PlanningThis part of the documentation gives you SAP SCM-specific information on planning theupgrade. The following sections include additional information, or restrictions placed on thegeneral procedures:

Upgrade Strategy Planning [page 35]!

Database Backup [page 35]!

Upgrade Schedule Planning [page 36]!

Runtime for the Import of the Substitution Set [page 37]!

Planning the Backup of DP AND SNP Time Series in InfoCubes [page 37]!

Changing Bucket Limits for Product Availability Check [page 37]!

Planning the Upgrade of SAP liveCache and Optimizer [page 38]!

Checking the Hardware Requirements [page 39]!

Checking the Source Release of the SAP System [page 40]!

Meeting the Requirements for the SAP liveCache [page 41]!

Upgrade of the Operating System and Database System: Overview [page 41]!

Start planning your upgrade at least two to three weeksbefore you want tobegin with the upgrade.

See also:

Upgrade Planning (General Information) [page 67]

4.1.1 Upgrade Strategy Planning

Sizes for comparing the archives up to the MODPROF_TRANSphase and to the end of theupgrade can be found in SAP Note 603852.

Sizes are available for the databases DB2 UDB for UNIX and Windows, Informix, Oracle, andSAP DB. These sizes are based on sample data.

See also:

Upgrade Strategy Planning (General Information) [page 72]

September 2003 35


36/232


4.1.2 Database Backup

Stopping the CIF-Queues

Before performing a backup of the database, you have to stop the CIF queues of your SAPSCM system to ensure a consistent recovery state. To stop the queues, use the followingreports:

! For outbound queues, use report /SAPAPO/CIFSTOPQUEUES. For parameter QNAME,enter CF*. Enter other parameters as requested.

! For inbound queues, use report RSTRFCI1. For parameter QNAME, enter CF*. Forparameter FORCE, enter blank.

Prerequisite is SAP Note 487261. For further information about how and where to run thereports, see section Solution of SAP Note 528913and SAP Note 505304.

As there are two possible types of CIF queues, inbound and outbound, you should ensure

that you stop both queue types in your system.You also need to ensure that you stop the CIF queues not only in the SAP SCM system, butalso in all the connected SAP systems.

If your SAP SCM system is connected to other systems than an SAP R/3 system, forexample, a SAP CRM or legacy system, make sure that these connections are stopped aswell.

See also:

Database Backup (General Information) [page 75]

4.1.3 Upgrade Schedule Planning

When planning your upgrade schedule, you must consider the following:

! Upgrade preparations (see step 1 in the general description [page 81])

Start your preparations for the upgrade at the latestone week before you upgradeyour system.

! Starting the upgrade (see step 2 in the general description [page 81])

If you decide to use upgrade strategy resource-minimized, start the upgrade on the last

day of production operation with the old release. On the evening of this day, you canstart the import of the substitution set.

If you decide to use upgrade strategy downtime-minimized, start the upgrade in goodtime before the scheduled start of downtime. This ensures that all activities that can beperformed during production operation are completed in time.

If you did not enter any mount directories during PREPARE, you are prompted atthe beginning of some of the EU_I MPORTphases to change the CD. If you missthis prompt, your time schedule could be seriously disrupted.

36 September 2003


37/232


The minimum runtime of the import in the SHADOW_I MPORT_ALLphase increases with everySupport Package, add-on, and language that is included. Each language that you importincreases the minimum duration of the import by about 30 minutes.

See also:

Upgrade Schedule Planning (General Information) [page 81]

4.1.4 Runtime for the Import of the Substitution SetThe import of the substitution set takes about 6.5 hours, depending on your hardware.

Upgrade strategy downtime-minimizedprompts you to specify a total runtime for the import ofthe substitution set. Set the time required for the import so that it ends at least 5 hours before

the planned shutdown of production operation. Depending on the start time of the upgrade,specify total runtimes of about 24 hours.

See also:

Runtime for the Import of the Substitution Set (General Information) [page 83]

4.1.5 Planning the Backup of DP and SNP Time Seriesin InfoCubes

Use

If you have created DP time series or SNP time series, or both, in SAP liveCache and want touse them again after the upgrade, you must extract [page 54]the data into an InfoCubeduring the upgrade and before you import the 4.0 programs, and then restore [page 57]themto SAP liveCache after the upgrade. You must discuss the extent of this data extraction withthe individual departments before the upgrade.

Procedure

1. Discuss which key data is extracted during the upgrade in the REQ_APOUPGphasewith representatives from the departments.

2. Schedule the data extraction in your upgrade planning.

September 2003 37


38/232


4.1.6 Changing Bucket Limits for Product AvailabilityCheck

UseThe product availability check is normally based on daily data. As of SAP SCM 4.0 you candefine the limits of daily buckets system-wide for receipt and issue buckets. Additionally, youcan define whether receipts are available at the start or the end of a bucket.

If you are using locations in other time zones than UTC, you can set a date for the bucketlimits that is not within office hours for most of the locations (at night, for example).

You can only activate changes of bucket limits with either deleting the old and creating a newplan version 000 or with activating SAP liveCache. As upgrading the SAP SCM systemrequires initializing the SAP liveCache, this is a perfect opportunity to change bucket limitswithout causing extra system downtime.

For more information on changing bucket limits, see the online documentation of the targetrelease under Help#SAP Library #SAP Advanced Planner and Optimizer #GlobalAvailable-to-Promise (Global ATP)#Settings for Global ATP #General Settings for GlobalATP #Definition of Buckets for ATP Time Series #Valuation of Receipts and Issues inBuckets.

4.1.7 Planning the Upgrade of SAP liveCache andOptimizer

SAP liveCache

To upgrade the SAP liveCache, you have to perform a number of activities before, during,and after the upgrade of the SAP system. For example, you can upgrade the liveCache onlyafter the liveCache transactional data has been saved. Therefore, one of the main activities isto download the transactional data before the liveCache upgrade and upload the data beforeproduction operation resumes.

Report /SAPAPO/OM_LC_UPGRADE_3X_40 lists all actions necessary to perform theupgrade. The activities are grouped in sections according to when they have to be performed:

! Section A: Maximum Two Weeks Prior to Upgrade

! Section B: Immed. Prior to Downtime

! Section C: At End of Upgrade

! Section D: At Least Four Weeks After Upgrade

As most of the activities require user action, the report will notbe executed automatically.Refer to Upgrade Step by Stepfor when to perform the relevant sections of the report.During the upgrade, R3upstops and prompts you to execute the report whenever necessary.

Pushbuttons for activities, which can technically not be performed at a given point of time,turn grey and become inactive. All other pushbuttons are active, so make sure to perform theactions of the different sections exactly at the point of time stated in the upgradedocumentation. For example, do not perform Section B right after Section A, but during phaseREQ_APOUPG1.

38 September

Date post:	01-Jun-2018
Category:	Documents
Upload:	sanjaymurthy
View:	228 times
Download:	0 times

SCM Server 40 UX Upgrade

Documents