mysap ERP Upgrade Project Guide

Transcription

1

2 mysap ERP Upgrade Project Guide Bert Vanstechelman, Mark Mergaerts, Dirk Matthys Contents 1 About This Book... 7 Download... 8 Acknowledgements Upgrading SAP: The Project Perspective Why Upgrade? What is the Effort? To Which Release? The Technical SAP Upgrade in a Nutshell Legend The SAP Upgrade Project Project Planning Planning Levels Critical Success Factors Aspects to Consider Ongoing Development and Customizing Testing Compatibility of SAP Plug-in Compatibility of Operating System and Database Hardware Capacity Front-End ( SAP GUI ) System Landscape During the Upgrade 15 Often Forgotten Where to Start? The Master Project Plan The Project Team The Testing Phase The Main Business Processes Test Strategy Test Scenarios Tools Status Reporting Global Status Reporting ( the Test Cockpit ) Make Your Progress Visible Estimate the Effort The Number of SAP Objects Modified ABAP Unicode Syntax Requirements Customer Developments Estimating the Functional Effort Business Example Estimating the Technical Upgrade Runtime for the Production System Capacity Planning when Upgrading to mysap ERP Finally Seek Assistance and Information What are the Usual Suspects that Need Extra Attention? Technical Background Information The SAP NetWeaver Architecture People Integration Portal Infrastructure SAP NetWeaver Collaboration Multi-Channel Access or the Mobile Infrastructure Information Integration Knowledge Management Business Intelligence with the SAP Business Information Warehouse ( SAP BW )

3 Contents Master Data Management Process Integration SAP Exchange Infrastructure Business Process Management Java ABAP DB and OS Abstraction Introducing mysap ERP Names and Numbers: An Overview of SAP Releases Support Packages and Add-ons The System Switch Upgrade Consequences of the System Switch Upgrade Upgrade Strategy Planning Features of Upgrade Strategy Resource-Minimized Features of Upgrade Strategy Downtime-Minimized Database-Specific Aspects Upgrades in an MCOD System Landscape The SAP Landscape During the Upgrade The Impact of the Upgrade on the Landscape Scenarios for the Landscape Set-Up Scenario 1: The Sandbox System Scenario 2: Extra Development and Quality-Assurance Systems Scenario 3: Contingency System Upgrading the Front-End Software The Upgrade Tools The SAP Upgrade Guides SAP Solution Manager and the SAP Upgrade Roadmap The PREPARE The Upgrade Assistant and Upgrade Monitor The Upgrade Executables The JOB_ or RUN_ phases The Import Phases Transport Phases The Bulk Import Phases Incremental Table Conversion ( ICNV ) The Application Specific Upgrade ( ASU ) The Customer Based Upgrade ( CBU ) The SAP Web Application Server Java SAP NetWeaver Application Server 7.00 and Above Upgrade Process Profile Changes and Kernel Switch Beginning of Downtime and Uptime Reset of the Upgrade in Case of Disaster Upgrading Other R/3 Systems Upgrade of mysap CRM Upgrade of SAP Business Information Warehouse ( BW ) Introduction Add-ons BW-Specific Tasks Upgrade of mysap SCM Planning the Upgrade of SAP livecache Optimizers The Upgrade Process in Detail Top-level view Downtime-Minimized Versus Resource-Minimized Database Archiving Mode Which Strategy Is the Best? Time Schedule for Technical Upgrade Contents of the Following Chapters Preparing the Upgrade Upgrade Services SAP GoingLive Functional Upgrade Check SAP Safeguarding for Upgrade SAP Upgrade Service Portfolio Galileo Press All rights reserved.

4 Contents Information Links for SAP Upgrade Services Platform Support SAP Platform Availability Matrix Platform Support Notes Resource Requirements Upgrade Documentation Upgrade Guide Upgrade Notes SAP Solution Manager System Software for the Upgrade Upgrade Media Support Packages R3up Fix and Correction Transports Java Development Kit Front-End Software ( SAP GUI ) The Upgrade Directory Purpose Path and Subdirectories Naming Convention in this Book Changing the Path Name Symbolic Link ( UNIX ) Disk Space Other Directories Upgrade Media Other Files Needed for the Upgrade Example of Directory Structure Disk-Space Requirements Space in the Database Space for the Upgrade Directory Space for the Upgrade Media and Downloads Extra Space in /usr/sap/trans Pre-Upgrade Downtime Review of Transport Requests Activities in the SAP System Create a User for the Upgrade Create a Development Class ( Package ) for the Upgrade Repairs Updates Pending DB Conversions Substitution Tables in Wrong Database Space Generating the Upgrade Key in SAP Solution Manager Ready to Go! The PREPARE Process The Upgrade Assistant Description Administrator and Observer Modes Scroll Mode The Initial Extraction Script R3up and Correction Transports Replace R3up Correction Transports Copy Phase List Files to PC ( Optional ) Install UA GUI on Workstation ( Optional ) Start the UA Server Start UA GUI and Log In Starting from a Browser Starting as a Standalone Application Run Time of PREPARE Input Up to Phase Selection Entering the CD/DVD Mount Points Kernel Extraction and Optional Replacement Input for Server and Path Names Input for Parallel Processing Further Input for Path Names Upgrade Key ( from SAP Solution Manager ) Input for MCOD Tool Import Input for Language Selection Add-on and Patch Binding Add-on Components Patch Binding Input for Modification Adjustment ( SPDD/SPAU ) Input for Shadow Instance Application Specific Upgrade ( ASU ) Result of PREPARE Correcting Errors Reported by PREPARE The CHECKS.LOG File

5 Contents PREPARE Errors Database Extensions Change the Permissions of Executables 92 Target Kernel Too Low SAP Objects Locked in Repairs Doomed Dictionary Objects Pending Update Records Address Conversion Overlap in Address Number Range Number of Objects for Modification Adjustment Repeating PREPARE After the End of PREPARE Post-PREPARE Activities Back Up Database and Upgrade Directory Clean Up Database Archives SAP Start and Stop Scripts ( UNIX ) Resetting PREPARE The Upgrade Process ( R3up ) Uptime or Downtime? Starting R3up Without an Error-free PREPARE Upgrade Assistant Starting the Upgrade Interaction until Start of Import Data Import The Shadow Instance First Start ( Phase START_SHDI_FIRST ) Manually Starting and Stopping the Shadow Instance Service for Shadow Instance on Windows Stop for Modification Adjustment ( Transaction SPDD ) The Activation Phase Handling Activation Errors Open the System and Call Transaction SE Identifying the Problem Field Defined Twice Identical Indexes Object Incorrect in Source Release References to an Object Deleted in the Upgrade Objects Listed in SAP Notes Repeat the Activation Shadow Instance Stopped Incremental Conversion ( ICNV ) Import Language Data and Support Packages Upgrade Reaches Downtime Point Isolating the Central Instance Final Checks Lock the Users Disable Background Jobs ( 3.1I 4.0B ) Operation Modes Back Up Database, Upgrade Directory, and Source Kernel Open Client 000 for Development Other Activities Entering Downtime Logging on to SAP During Downtime Unlock the System to Correct Errors User Interaction and Monitoring During Downtime The Switch Phases: EU_SWITCH and KX_SWITCH Table-Conversion Phase: PARCONV_UPG Import Control Data: TABIM_UPG Conversion Programs: XPRAS_UPG XPRAs: Purpose and Behavior Dealing with XPRA Errors Action after an Error Postponing an XPRA The Final Phases Upgrade Information Files Closing the Upgrade Assistant Resetting the Upgrade Upgrade Post-Processing Actions at Operating System Level The saproot.sh Script ( UNIX ) Upgrade the Kernel on the Application Servers Galileo Press All rights reserved.

6 Contents 11.2 Actions at Database Level Back Up the Database Update Statistics Parameter Changes Dropping the Old Repository Activities in the SAP System Parameter Changes ABAP Load Generation ( SGEN ) Configure the Transport Management System ( TMS ) Non-fatal ( Type P ) Upgrade Errors Glossary and Terminology Data Language Supplementation Install/Upgrade Add-ons Apply Additional Support Packages Reschedule Background Jobs Import the Transport Queue Cleanup Save the Upgrade Logs Modification Adjustment The Modification Browser SPDD Selection Screen SPDD Object List Modification State Object Type Object Attribute Modification Adjusting Objects Proposals for Table and Structure Fields New Fields Added in Standard Proposals for Different Data Element Proposals for Technical Settings Objects Without Proposals Returning an Object to the SAP Standard Keep Transport for Upgrade of Next System Documenting Your Modifications Modification Adjustment with SPAU A Resetting the Upgrade A.1 Reset during PREPARE A.2 Reset R3up before MODPROF_TRANS A.3 Reset R3up after MODPROF_TRANS B Database Transaction Log Modes C References C.1 Presentations C.2 Manuals C.3 How-to Guides C.4 Articles Index

7 9 The PREPARE Process The PREPARE is the first major part of the upgrade. Data and programs are copied to the upgrade directory, tools are imported into the database, and the shadow instance is installed. Add-ons, support packages, and languages are integrated into the upgrade. After the initial configuration of the upgrade, PREPARE verifies that the source system meets the requirements of the upgrade process and of the target release. This produces an action list that must be taken care of before the actual upgrade can start. Note: PREPARE is executed with the system running. End users are not affected. 9.1 The Upgrade Assistant Description The application that manages the upgrade process is the Upgrade Assistant ( UA ). The UA is delivered on the Upgrade Master CD, and it is installed into the ua subdirectory of the upgrade directory. The UA has two components: the server and the client. The UA Server runs on the upgrade host. It drives and controls the technical upgrade program ( R3up ) and interacts with the UA Clients The UA Client is the graphical user interface ( GUI ) used to control and monitor the upgrade. In subsequent chapters, we refer to it as the UA GUI. The GUI can run on the same host as the server, but also on a different host ( typically an administrator s PC ). The UA GUI communicates with the UA Server via TCP/ IP ports. It can run as a standalone application or as an applet started from a Web browser. You ll find screenshots of the Upgrade Assistant and the Upgrade Monitor in Section 5.4. Tip: The UA for mysap ERP 2004 has few differences with that of previous releases. If you already used the UA for past upgrades, then you will be immediately familiar with it. Administrator and Observer Modes Any number of UA GUI sessions can connect to the UA Server simultaneously. Only one session, however, can be in control of the upgrade at any one time. This session is the upgrade administrator. Whenever the UA Server needs user input, a data entry window will open automatically in the administrator session. All other UA GUI sessions are observer s. They show the current phase of the upgrade and will also show ( but in read-only ) the user interaction that takes place with the administrator session. When you log on to the UA GUI, you specify the role you want your session to take on by entering a password. The UA has a separate password for each role. The initial passwords ( which can be changed in the UA GUI ) are: Administrator: admin Observer: observer Provided he or she knows the administrator password, it is possible for an observer to take over the administrator role. The current administrator is then automatically demoted to observer. This happens without interaction; that is, the UA GUI will not ask the current administrator to allow or acknowledge the take-over and his or her own demotion. This may seem a bit drastic, but it is actually quite smart. Imagine that during a long-running upgrade the workstation currently running the UA GUI in administrator mode at some point becomes out of reach ( you have gone home and want to continue the upgrade from your home PC via a VPN connection ). In such a 81

8 9 The PREPARE Process case, it makes perfect sense not to interact with the current administrator when switching roles. Scroll Mode It is possible to run the upgrade, and to interact with it, from a plain command window, such as a Telnet session or a DOS shell. In this case, you do not use the UA GUI. This method is called scroll mode, and is similar to the old method used up to SAP release 3.x, when R3up was a terminal-based process. There is really no reason to run in scroll mode, because the disadvantages are significant. Apart from the fact that user interaction is much less user-friendly, the upgrade process is also far more vulnerable because it depends on the network connection of the terminal session. If this connection fails or you accidentally close the session window, the upgrade stops and specific recovery actions are necessary before you can safely restart it R3up and Correction Transports Before you continue with the technical upgrade, now is the time to replace the R3up from the upgrade kit with the fixed version ( see Section 8.5, under the heading R3up Fix and Correction Transports ) and also to copy the SAR archive with the correction transports ( see same section ) to its proper location. Replace R3up Caution: You should only replace R3up before the first run of PREPARE. Never replace R3up during the upgrade unless instructed to do so by SAP! 1. Go to directory <PUTDIR>/bin. 2. Rename R3up, for example to R3up.orig. 3. Copy the fixed R3up you downloaded earlier to <PUTDIR>/bin. Make sure that ownership and file access are the same as for the original R3up file. 9.2 The Initial Extraction Script The very first step in the technical upgrade process is to run a script that extracts a minimum set of files ( including the UA ) to the upgrade directory and also performs some basic checks of the server. This script is located on the Upgrade Master CD and is somewhat confusingly called PREPARE ( it is not the same as the PREPARE process, which is the first major step of the upgrade and is not run via this script ). As a starting condition the upgrade directory must be empty. 1. In a command window ( Telnet session, DOS shell ) log on as the SAP administrator account ( <sid>adm ). 2. Locate the PREPARE script for your O/S platform on the Upgrade Master CD. 3. Execute the script. Example ( user input is shown in bold ): The mounted CD Set is for database <DBMS> only. Does your system run on DB <DBMS>? YES Select operation mode EXIT 1 For details, see section Restarting the Upgrade in Scroll Mode in the SAP Upgrade Guide. Correction Transports Unpack the ECC_500*.SAR archive that contains the correction transports to the top level of the upgrade directory: (logged on as <sid>adm) cd <PUTDIR> SAPCAR xvf <path>/ecc_500*.sar Two files will be extracted. One has extension.info, the other is again an SAR archive named FIX_ECC500SR1. SAR. Do not unpack this file yourself. PREPARE will do this for you. 9.4 Copy Phase List Files to PC ( Optional ) The list of upgrade phases is no longer in the upgrade manual; instead it comes as a set of HTML files, which you can transfer to the PC. Copy the following files to your PC: <PUTDIR>/htdoc/phaselist.htm <PUTDIR>/htdoc/phase_toc.htm PHASE_TOC.HTM lists all upgrade phases as hyperlinks to the detailed phase list. PHASELIST.HTM contains the actual phase list for PREPARE and R3up, divided into major 82 Galileo Press All rights reserved.

9 9.7 Start UA GUI and Log In sections. This corresponds to the phase list that used to be part of the upgrade manual in earlier releases. PROP((os400.file.io.mode TEXT)(os400.verify. checks.disable 3)) 9.5 Install UA GUI on Workstation ( Optional ) This step is only necessary if you want to run the UA GUI as a standalone application from your workstation. If you choose to run the UA GUI as an applet from a browser, then you may skip this step. 1. Create a folder on the PC to hold the UA GUI files ( e. g. C:\UAGUI ). 2. Transfer ( in binary mode ) the following file from the server to the folder you have just created: <PUTDIR>/ua/uagui.jar 3. Open a DOS shell and try starting the UA GUI: cd C:\UAGUIjava cp uagui.jar UaGui ( with standard Java VM : jview /cp uagui.jar UaGui ) The UA GUI logon screen must appear. Exit for now, because you haven t got the server running yet. 9.6 Start the UA Server Follow these instructions to start the Upgrade Assistant server. UNIX ( see note below ): (logged on as <sid>adm) java cp <PUTDIR>/ua/ua.jar UaServer Note for UNIX: It is not a good idea to run the UA Server in a dedicated terminal window, because the server then would abort if the terminal window was closed or if the network connection to the PC failed ( see also Section Scroll mode above ). Start the UA Server as a detached background process: nohup java cp <PUTDIR>/ua/ ua.jar UaServer &. Look at the standard output of the UA Server to see whether it starts up correctly. The last message shows that the server is ready to receive UA GUI connections. UaServer> Upgrade Assistant Server (Version 2.0) UaServer> Running on host horizon.saptest.be ( ) UaServer> Temporary directory is '/usr/sap/ put/ua' UaServer> Upgrade directory is '/usr/sap/ put' UaServer> Stable storage file '/usr/sap/put/ ua/uastate' read UaServer> Property file '/usr/sap/put/ua/ UaServer.properties' read UaServer> Property file '/usr/sap/put/ua/ UaTextE.properties' read UaServer> Waiting for UaGuis to connect at port 4241 Windows with Java SDK: (logged on as <sid>adm) java cp <PUTDIR>\ua\ua.jar UaServer Windows with Standard Java VM: (logged on as <sid>adm) jview /cp <PUTDIR>\ua\ua.jar UaServer iseries: ADDLIBLE R3UP ADDENVVAR ENVVAR(PASE_LIBPATH) VALUE('<PUTDIR>/bin') JAVA CLASS(UaServer) CLASSPATH('<PUTDIR>/ua/ ua.jar') Port 4241 is the port used when the UA GUI runs in stand-alone mode. When it is started as a browser applet, a different port number ( 4239 ) is used. Section 9.7 provides more detail. 9.7 Start UA GUI and Log In The procedure to run the UA GUI and log on to the UA Server is slightly different depending on whether you run the UA GUI as a stand-alone application or via a browser. Starting from a Browser Open a Web browser and enter the URL:

10 9 The PREPARE Process <upghost> is the host name or IP address of the host where the UA Server runs. The HTTP port of the UA Server is The SAP Upgrade main page is displayed ( see Figure 9.1 ). You can also pass the host name and port number on the command line in the form of a SAP route string, for example: java cp C:\UAGUI\uagui.jar host /H/ sapdev01/s/4241 This will skip the first screen; that is, the UA GUI will now behave as it does when you run it from a browser. 9.8 Run Time of PREPARE Figure 9.1 Initial Browser Screen For Upgrade To start the UA GUI, click on Start Upgrade Assistant. A login screen appears. On this screen enter: A freely chosen user name ( this can be your real name, as the only purpose is to identify who is currently connected to the UAGUI ) Your telephone number ( optional ) The password for the administrator role ( default: admin ) Choose Login and continue with the instructions in Section 9.9. Note: To call the UA GUI directly, use the URL <server>:4239/ua/uagui.html. Starting as a Standalone Application Open a command shell on the PC and type the command to start the UA GUI as shown earlier in Section 9.5. Because at this point you have not yet identified the upgrade host a window opens asking for the upgrade host and port: Host name: Name or IP address of the host where the UA Server runs Port number: Accept the default 4241 ( notice that different ports, 4239 and 4241, are used depending on how you run the UA GUI ). Many factors influence the total runtime of PREPARE, and it is difficult to make a prediction. You should typically expect a runtime of between four and eight hours. Although there are some lengthy phases during which PREPARE runs unattended, the program will request user input at many different points. This means that PREPARE is not suitable to run overnight without human monitoring. 9.9 Input Up to Phase Selection Note: For better readability, the PREPARE dialogs in this section are shown as text ( not as actual screen shots ) on a shaded background. User input appears in bold. Whenever an input screen requires further explanation, this information is presented in plain text. In the UA GUI window, choose Administrator Start PREPARE. Welcome to the SAP upgrade control program. Continue. SAP System ID Confirm the system ID. Select type of database Select your DBMS, click OK. Start import of data from Data Carrier? Choose Import, click OK. Enter mount point for Data Carrier : Type the path of the Upgrade Master CD. The archives are unpacked. SAP UPGRADE CONTROL PROGRAM Continue. 84 Galileo Press All rights reserved.

11 9.13 Input for Parallel Processing The following options are available: select: Display screen for selecting PREPARE modules status: Display the statuses of the PREPARE modules exit: Exit PREPARE help: Getting help about PREPARE Choose Select. Select the PREPARE modules Mark all phases and click OK. Note: Ignore the fact that some phases are marked as mandatory and others are not. Always execute all phases. You selected the following PREPARE modules: ( The phase list follows scroll down to see the radio buttons. ) Choose Execute, click OK. SAP System ID SAP System Host Instance number The values shown should be OK. At this point you can upload the new kernel ( see below ). To bind the new kernel into the upgrade, do the following: 1. Log on as sidadm. 2. Unpack the SAPEXE*.SAR and SAPEXEDB.* packages you downloaded from the SAP Service Marketplace ( see Section 8.5; heading Support Packages ): cd <PUTDIR>/exe SAPCAR xvf <downloadpath>/sapexe*.sar SAPCAR xvf <downloadpath>/sapexedb*.sar If the extraction was successful for both archives, reply OK in the PREPARE window Input for Server and Path Names 9.10 Entering the CD/DVD Mount Points Mount points for DVDs Enter the paths of the online copies of the upgrade media. The path of the Upgrade Master medium is already filled in. You must still enter the paths for the kernel medium, the language media and the eleven upgrade media. Fortunately you only have to do this once! Unlike earlier versions of the UA GUI, this one lets you copy/paste path names. For this, use the right mouse button, not Control- C/Control-V. Fill in the paths for all media. When you are done, press > or >> till you reach the last screen; here the OK button is enabled Kernel Extraction and Optional Replacement The extraction of the kernel now begins. If you plan to upgrade the SAP kernel to a higher level than the one delivered on the upgrade media, then you can already bind the new kernel into the upgrade when PREPARE next stops for further input. PREPARE now requests information about the server environment and various directory paths needed for the upgrade. Kernel path Press OK. Database ID Database host Values shown should be OK. DDIC password Enter and confirm password of user DDIC in client 000. Instance profile Default profile Start profile Values shown should be OK. Batch host Set to host of Central Instance ( default ) Input for Parallel Processing Maximum uptime processes See below. 85

12 9 The PREPARE Process R3trans processes See below. Maximum SYNC time Enter 120. The value for Maximum uptime processes determines the number of parallel tasks that will run in the shadow instance during the dictionary activation phase. With the downtime-minimized strategy, these tasks will run together with normal use of the system. Values of 3 to 5 are reasonable. R3trans processes sets the number of parallel import processes ( R3trans ) during the upgrade. The phases most affected by this are SHADOW_UPGRADE ( an uptime phase in the downtime-minimized mode ) and TABIM ( table data import; always in downtime ). Too high a number may overload the server and also lead to contention between the different imports. Too low a value needlessly lengthens the duration of the upgrade. A suitable value in most cases is 4. The SYNC time controls internal buffer synchronization. Do not change this value Further Input for Path Names EPS root Local SYSLOG path Values shown should be OK. Central SYSLOG path Press OK. STARTSAP path Path ( kernel directory ) should be OK. The vague reference to the SAP Service Marketplace in this prompt is not of much use. Note is more informative. SAP Solution Manager Key = Enter the upgrade key. See Section 8.12 for instructions Input for MCOD Is there more than one system running in this database? (MCOD: Multiple components in one database) Enter No unless you are upgrading an MCOD system. The dialog shown here is for a non-mcod configuration. This covers most situations Tool Import The PREPARE module Import will be started now. During this module programs, structures, and table entries required by PREPARE are imported (the so-called "tool import"). Note: This can cause a loss of performance in R/3 In rare cases, a concurrent transport via the transport directory may disturb the tool import. Please avoid any concurrent import during this PREPARE module. Continue Upgrade Key ( from SAP Solution Manager ) The SAP Solution Manager Key is required for the upgrade. Further informations can be found in the upgrade guide, the SAP Service Marketplace and SAP note ! Continue. PREPARE will duly warn you that the import may cause some pressure on the server. Although in practice this is rarely problematic, you may choose to wait for a quieter period before confirming this prompt. Also pay heed to the warning about concurrent transports Input for Language Selection The following input screen concerns additional languages found in the system. If the system only contains the stan- 86 Galileo Press All rights reserved.

13 Index A ABAP 28 ABAP Dictionary objects 32 ACT_ Add-ons 30, 32 ADJUSTCHK 47 ALNTAB_FILL 47 Alpha Conversion 57 Application Specific Upgrade (ASU) 50 archiving 34 archiving mode 63 archiving strategy 34 ASU toolbox 50 B BAPIs 22 BASIS Plug-in 56 batch input 22, 26 bulk import phases 47 Business Content 56 Business Process Management 28 C Capable to Match (CTM) 59 capacity planning 24 CATT 19 CCMS 42 Change Request Management 42 CHK_POSTUP 48 compatibility OS and DBMS 14 SAP Plug-in 14 contingency system 37, 39 CRM Mobile Clients 56 CRM server 55 Customer Based Upgrade (CBU) 51 customer developments 21 customizing 14 D database disk space 76 DB and OS Abstraction 29 DB conversions, pending 78 DDIC_ development 14 development class (for upgrade) 78 development system 37, 38 DIFFEXP 46 DIFFEXP.. 47 DIFFEXP 47 directory structure 76 disk space 76 downtime 62 Downtime minimized 10, 33, 62 downtime phases 48 E ecatt 19 Enterprise Extensions 29 Enterprise Portal Plug-in 56 EU_IMPORT 47 EU_IMPORT1 34, 64 EU_SWITCH 48 EXIT 48 EXITINFO 48 extended maintenance 9 F fixes 73 FREECHK_X 47 front-end 14 front-end upgrade 40 functional effort 22 H hardware capacity 14 I ICNV 48 ICNVINIT 47 ICNVREQ 49 ICNVREQ_GO 47 import phases 46 incremental conversion 79 Incremental Table Conversion (ICNV) 32, 48 Industry Solutions 30 InfoObject 57 Information Integration 28 INITPUT 47 INITSUBST 47 Internet Communication Manager 28 Internet Pricing and Configurator 55 issue lists 19 J J2EE Engine 28, 52 Java 28 Java Development Kit 73 Java Upgrade Management Program 52 K kernel switch 53 KEY_CHK 47 Knowledge Management 27, 28 KX_SWITCH 48 L LAN Check by Ping 25 landscape set-up

14 Index LOCKEU_PRE 47 log 64 M maintenance 9 Master Project Plan 16 Mobile Sales 56 Modification Adjustment 20, 33 Modification Browser 20 modified SAP objects 20 MODPROF_TRANS 34, 48, 62, 64 MODPROFP_UPG 48 Multi-Channel Access 28 Multiple Components in One Database 35 mysap CRM 55 mysap ERP 29 mysap ERP mysap ERP 2005 Upgrade Master Guide 70 mysap ERP Upgrade Portal 16 mysap Supply Chain Management (SCM) 30, 57 P PAM 68 PARCONV_UPG 48 PARDIST_SHD 47 PARMVNT_SHD 47 People Integration 27 Platform Availability Matrix 68 platform support notes 69 PORT_IMP_SHD 46, 47 Portal Infrastructure 27 post-processing activities 10 pre-upgrade 77 pre-upgrade phase 61 preparation 67 PREPARE 8, 10, 43, 46, 61 modules 43 upgrade key 80 Web AS Process Integration 28 Production Planning/Detailed Scheduling (PP/DS) 59 project plan 16 project planning 13 Q Quality Assurance System 37, 38 Quick Sizer 25 R R3load 47 R3up 8, 44, 46, 61 Web AS release support 9 repairs 78 repository switch upgrade 31, 32 REQGENLD 48 REQJOBRES 48 REQSTOPPROD 34, 64 resource-minimized 10, 32, 62 Reverse Business Engineer 18 RSUPGSUM 23, 49 RUN_RDDIT S sandbox system 37 TMS configuration 38 SAP Accelerated Value Assessment 67 SAP Business Information Warehouse 28, 56 SAP Business Intelligence 28 SAP Component Upgrade Guide 41 SAP ECC 29 SAP End-User Delta Training 68 SAP Enterprise Portal 27 SAP ERP Central Component (SAP ECC) 29 SAP Exchange Infrastructure 28 SAP Functional Upgrade Service 25 SAP GoingLive Functional Upgrade Check 67 SAP GUI 14, 40, 74 SAPJup 53 SAP livecache 57 SAP Master Data Management 28 SAP Master Upgrade Guide 41 SAP Mobile Infrastructure 28 SAP NetWeaver 27 SAP NetWeaver SAP NetWeaver Collaboration 27 SAP Plug-in 14 SAP R/3 29 SAP R/3 Enterprise 7, 29 SAP Safeguarding for Upgrade 67 SAPSetup 40 SAP Solution Manager 19, 42, 71, 80 SAP Strategic Enterprise Management (SEM) 56 SAP Test Management Optimization 19 SAPup 53 SAP Upgrade Guides 41 SAP Upgrade Hosting 68 SAP Upgrade Roadmap 16, 42, 43 SAP Upgrade Weekend Support 68 SAP Value Assessment 67 SAP Web Application Server 27, 28 SAP Web Application Server kernel switch 53 reset of upgrade 53 synchronisation points 53 upgrade process 53 SAP Web Application Server Java 52 SAVELOGS 48 SCM optimizers 59 SHADOW_IMPORT_INC 47 SHADOW_IMPORT_UPG 46 SHADOW_IMPORT_UPG1 47 SHADOW_IMPORT_UPG2 47 Shadow Instance 32 SHD_FIX_IMP 47 solution gap 9 SPAUINFO 48 STAD 25 START_SHDI_FIRST 47 STARTR3_NBAS 48 status reporting 19 success factors 13 Supply Network Planning (SNP) 59 Support Packages 9, 30, 32, 72 Support Package Stacks (SP Stacks) 31, 72 symbolic link (UNIX) 75 synchronization points 53 system landscape 15 System Switch Upgrade 31, 32, 48, 62 T TABIM_UPG 46, 48 Table Browser 21 technical upgrade 10 runtime 23 schedule Galileo Press All rights reserved.

15 Index technical upgrade process 61 testing 14, 18 scenarios 19 strategy 18 tools 19 time schedule 65 TP_ACTION_CP2STAB 47 transaction DB02 25 ICNV 49 RSD1 57 SAMT 21 SE16 21 SE37 21 SE38 22 SE95 20 SM04 25 SM13 78 SPAU 77 SPDD 8 ST02 25 ST03N 25 ST04 25 ST06 25 transaction logging 63 transport phases 46 transport requests 77 TREX 28, 55 U UCCHECK 21 Unicode 21 updates 78 upgrade driving forces 9 front-end 40 MCOD 35 mysap CRM 55 runtime 34 user 78 why? 9 Upgrade Assistant (UA) 44, 45 Upgrade Assistant Server 46 upgrade coach 67 Upgrade Control Program R3up upgrade directory 74 disk space 76 path name 75 upgrade guides 70 upgrade key 80 upgrade manual 41 upgrade media 72 directories 75 upgrade methodology 10 Upgrade Monitor 44, 45 upgrade notes 70 upgrade phase 61 upgrade project 13 main phases 17 team 17 upgrade services 67 upgrade strategy 34, 35 upgrade tools 41 uptime phases 47 user exits 21 User Management Engine (UME) 53 V Variant Save Tool 50 VIEWIMP_BAS 46, 47 virtual system 39 W Workplace Plug-in 56 X XPRAS_UPG