Skip to Content
Author's profile photo Former Member

SAP R/3 –> ECC EHP5 Upgrade

SAP R/3 –> ECC EHP5 Upgrade

The upgrade program upgrades an ABAP system using a system cloning and switch procedure.

This procedure installs a copy of the system, the shadow system, in parallel with the original system.

The shadow system is used to update the affected software components and to install the additional components, while the original system is still in production operation.Operating two instances in parallel places increased demands on free space in the file system, in the database, and on the system resources. No precise guidelines can be given for the duration of an upgrade

The duration of the system cloning depends to a great extent on the amount of data, the database system, and the hardware and can take several hours.

Although the system can still be used in production operation, you have to take into account a possible performance decrease during this cloning process.

If necessary, some parameters in the production system might need to be adjusted to enable you to operate the production and the shadow systems in parallel.

Checklist –

1 Find SAP Notes

2 Plan the upgrade

3 Prepare the upgrade

4 Upgrade the SAP system

5 Perform the follow-up activities

SAP Notes for the Upgrade Notes: No.

1 Central Upgrade Note 1299009

2 Upgrade Note for your application 1341975

3 The relevant database-specific SAP Note 819655

4 Resource requirements for R/3 Enterprise 4.70 x 1.10 517085

5 Combined Upgrade and Unicode conversion 928729

Upgrade Planning

1 decide on the sequence of upgrades in SAP system group Dev-QA-PR Approach (STMS)

2 familiarize with the features of the upgrade program (SAPup) and its effect on the way we upgrade the system with the upgrade GUI , the communication between backend processesand the GUI , and the upgrade directory

3 prepare the use of the SAP Solution Manager

4 familiarize with the technical details of the upgrade process

5 decide on a preconfiguration mode

6 upgrade the front-end software after getting software package.(720 Rel.)

Before starting the upgrade,   check the database-specific aspects and include them in upgrade schedule, if necessary.Archive Sizes: 35 GB up to the DOWNCONF_TRANS phase and 43 GB to the end of the upgrade.

7 These sizes are an estimation based on sample data.

8 plan data management measures to reduce the amount of data, if necessary.(Reorg??)

9 plan the modification adjustment for ABAP, if necessary.

10 Plan for CU & UC method, if your system is non unicode In Our case it is single code page – SE11-TCPDB-1100-single code page

11 plan the handling of customer-specific translations and Z languages in ABAP during the upgrade.

12 check the Support Package or patch level of the components included in the upgrade export.

13 plan the use of the application-specific upgrade toolbox (ASU toolbox).

Upgrade Preparation

Actions Before Starting the Upgrade Program

1 Prepare the sandbox system for upgrade.

2 Check h/w requirements includes CPU, main memory, swap size, disk space

3 Check s/w requirements which includes patch levels

4 make preparations at the database level like update statistics

5 check the structural requirements for ABAP

6 call transaction RZ04 to set the operation mode for upg

7 check the number of the background processes

8 make sure that the requirements for the modification adjustment

9 fill the download directory with required software packages like DVD’s, Latest kernel files, sapUP tool

10 prepare the migration of the workload statistics data of the ABAP part of the SAP system.

11 meet the requirements for the SAP Internet Transaction Server

12 make the required preparations for a system that is secured by SAP Cryptographic Library

Upgrade Process

ProcessActions for Starting and Using the Upgrade Program

1 meet the requirements for the upgrade directory

2 start the upgrade from the Upgrade Master DVD

3 monitor the upgrade using Different adv options

4 In case of extra software after starting the upgrade, import or install it.

User Actions During the Extraction Roadmap Step

1 make the entries for the Extraction roadmap step.

enter the keyword from the current Upgrade

enter mount directories.

enter Media List

enter the password for user DDIC.

select the SAP Cryptographic Library that is to be used in the target system.

User Actions During the Configuration Roadmap Step

1 enter paths and parameters

choose preconfiguration mode (Downtime minimized, high resource)

enter the port number for internal communication.

enter the password for user system.

check the version of the SAP kernel, tp, and R3trans.

check the SAP Notes for the add-ons.

For the SAP ECC Extension Add-Ons listed in phase IS_SELECT, use the standard settings.

In case of Combined Upgrade & Unicode Conversion, confirm the question.

2 specify the software you want to include in the upgrade.

enter mount directories for the languages.

check the SPAM version.

upload additional packages.

include enhancement packages, if necessary.

decide about the add-ons.

confirm the required Support Packages, if necessary.

include Support Packages, if necessary.

enter the single change request for the modification adjustment, if necessary.

3 make entries for the shadow instance installation

decide about reusing the shadow instance profiles.

User Actions During the Checks Roadmap Step

1 continue with the roadmap step Checks and make entries if necessary. At the end of the step, perform the user actions requested on the SDTExecution Intervention screen.

2 start the Application-Specific Upgrade Toolbox.

3 decide about using the RASUVAR<x> reports to save variants.

4 check the results of the system check.

Actions After Performing the Preparation Roadmap Steps

1 evaluate the results of the preparation roadmap steps in the window that appears after the Checks roadmap step has completed.

Actions During the Preprocessing Roadmap Step

1 check the central and the product-specific Upgrade Notes and your database-specific SAP Note for new information and changes.

2 confirm any unconfirmed Support Packages.

3 enter the keywordsfor add-ons, if necessary.

4 update your operating system or database to the required version now at the latest, or you import any software you still need.

5 remove conflicts between customer tables and new views by deleting the customer tables.

6 release the locked objects and confirm repairs. You must do this in the REPACHK2 phase at the latest.

7 clean up outstanding updates. You must do this in the JOB_RSVBCHCK_R or JOB_RSVBCHCK_D phase at the latest.

8 make sure that you can recover the old SAP kernel if this becomes necessary.

9 release and confirm all open repairs in phase REPACHK2 at the latest.

10 For downtime-minimized: You lock the ABAP Workbench in phase REPACHK2 at the latest.

11 process any uncompleted conversion requests and restart logs.

12 Modifications: You confirm the request, if necessary.


As of this phase, you can only log on with front-end software that is compatible with the target release.

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

15 Modifications: If you selected preconfiguration mode standard resource use or high resource use during the Configuration roadmap step, you adjust modified SAP objects with the SAP standard versions.

16 start the ICNV, if necessary.(Incremental conversion of ABAP tables (transaction ICNV))

17 check the RSINDCRE.<SAPSID> log file for any errors that may have occurred during the creation of secondary database indexes.

18 When asked to isolate the central instance, stop the application servers, and back up the usr/sap/<SAPSID> directory including the complete upgrade directory. You may also need a backup of the home directory of user <sapsid>adm.

Actions During the Downtime Roadmap Step

1 To adjust the instance profile during or after the upgrade using transaction RZ10, you reimport the current version of the profile into your SAP system.

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

3 Modifications: If you selected preconfiguration mode low resource use during the Configuration roadmap step, you adjust modified SAP objects with the SAP standard versions.

4 Changes made to the environment of user <sapsid>adm before the upgrade are saved. You can repeat them after the upgrade, if necessary.

5 upgrade program asks to perform the following actions:

back up the database.

change the database recovery mode.

start the dialog instances.

Actions During the Postprocessing Roadmap Step

1 configure the automatic start of the SAP start service with the start of the operating system, if required.

2 If prompted, start to generate loads for your SAP system.

3 remove the P errors.

4 perform the modification adjustment for repository objects now and use the related transport request during subsequent enhancement package installations.

5 Optional: You send the evaluation of the upgrade runtime to SAP.

Follow-Up Activities

The upgrade program stops at the latest in the MODPROFP_UPG phase and prompts you to start the follow-up activities. The upgrade program then executes the last phases and

completes the upgrade. At the same time you can perform the follow-up activities specified by the upgrade program.

Actions Before Restarting Production Operation

1 perform the follow-up activities for user root

2 perform the database-specific actions Amongst others, create or update the SAPDBA role, check the environment variables for BR*Tools, and back up the database.

3 perform follow-up activities for the SAP kernel

4 perform follow-up activities in the monitoring area

5 activate the ICF service

6 install the Java components if necessary.

7 reimport additional programs such as RFC-SDK or CPIC-SDK from the SAP NetWeaver Presentation DVD, if necessary.

8 call transaction SPAU to adjust modifications to Repository objects, if necessary.

9 perform follow-up activities for the SAP system security

10 check application Release Notes for specific follow-up activities.

11 adjust the Customizing settings

12 adjust your own developments

13 update the where-used list

14 migrate the workload statistics data

15 discuss the activation of SAP ECC Extensions with your business consultants and the project team.

16 perform follow-up activities for SAP Solution Manager

17 execute the conversion program for the product master

18 adjust the user and role administration

19 activate the VMC for the Internet Pricing Configurator, if required.

Actions After Restarting Limited Production Operation

1 reschedule background jobs

2 perform actions for the Cost-Based Optimizer

3 generate loads using transaction SGEN and report RSGENINVLAS

4 install the online documentation for the target release.

5 configure the SAP Internet Transaction Server

6 perform follow-up activities in the authorizations area

adjust the assignments between check flags and transactions.

Upward compatibility for authorization checks: adjust SAP_NEW.

handle problems with user buffers.

7 perform follow-up activities for Application Link Enablin

8 use SAPinst to upgrade or install dialog instances

Actions After Restarting Production Operation

1 import Support Packages, if necessary.

2 Transport Management System (TMS): You distribute the configuration to all systems in the transport domain.

3 Language transport: copy glossary and terminology data from container tables to database tables.

4 delete old tablespaces

5 save files for follow-up upgrades and make a backup of the subdirectory that contains the shadow instance profiles, if necessary.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Gaurav Rana
      Gaurav Rana


      Nice document from your end.Thanks for sharing.



      Author's profile photo Former Member
      Former Member

      nice document...very helpful