upgrade guide for sap ecc 6.0 enhancement package 4

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 1

Upgrade Guide for SAP ECC 6.0

Enhancement Package 4

Applies to:

SAP ECC 6.0 with NetWeaver 7.0 (ABAP +JAVA stack)

Summary

SAP ECC 6.0 with NetWeaver 7.0 actively controls the administrative and operational environment to increase the efficiency and profitability thus helps in attaining new heights of business processes and technology integration while laying a concrete foundation of incremental evolution of the solution. The enhancement packages (EHP) are introduced to simplify the management and deployment of new software functionalities.

Author: Gunjan Yaduwanshi

Company: Deloitte

Created on: 25 April 2011

Author Bio

Gunjan Yaduwanshi is working at Deloitte Company.

Experience –SAP Basis Consultant with 22 months of experience. Apart from SAP Basis, also have experience in ECC Security and HR Security.

Upgrade Guide for SAP ECC 6.0 Enhancement Package 4


© 2011 SAP AG 2

Table of Contents

Prerequisites ....................................................................................................................................................... 3

Important OSS Notes: ......................................................................................................................................... 3

Initial Preparation ................................................................................................................................................ 4

Generating Stack file (.xml file) ........................................................................................................................... 4

Upgrade - EHP Installer ...................................................................................................................................... 6

Starting the EHPI ................................................................................................................................................ 6

Errors and their resolution ................................................................................................................................ 25

Related Content ................................................................................................................................................ 30

Disclaimer and Liability Notice .......................................................................................................................... 31



© 2011 SAP AG 3

Prerequisites

A Solution Manager system is required to complete the EHP4 upgrade.

Maintenance Optimizer (MOPZ) must be configured in Solution Manager before starting the EHP4 upgrade. OSS Notes 1134872 and 1233954 must be applied in Solution Manager.

The ST & ST-ICO components of Solution Manager must be at level SP19 or above (See note 1165437 for the latest information).

The ERP Server on which EHP4 is installed should have at least 8GB of memory.

The system is 64-bit and SAP‟s Enhancement Pack Installer will be used for the upgrade.

A large amount of free disk space should be available to accommodate a shadow instance and other temporary files which are created during the upgrade. This amount will vary depending upon initial database size, operating system/database platform, number of developments, and number of support packs/add-ons to be included in the upgrade. The ERP system used for testing this guide required 110 GB free space to complete the upgrade.

The disk or partition where the SAP\EHPI directory will reside has 10-15 GB free space.

The ERP system is at patch SP12 or higher.

The Database has been patched to the latest level.

TP.EXE and R3TRANS.EXE are patched to latest level.

SPAM has been patched to level 34 or higher.

Important OSS Notes:

Note # Note Title

1245473 Add Info. Enhancement Package Installer

1161052 Add Info. SAPehpi for Systems on Oracle

1165438 Enhancement Package 4 for SAP ERP : Required SWC

1122966 Maintenance Optimizer: Notes for Enhancement Packages

485741 Handling customer translations in the upgrade

195157 Application logs - Deletion of logs

211077 Exchanging Target release kernel during upgrade

62519 Correction locks do not belong to system

1143022 SAP up Key word

1275873 Memory bottleneck during DDIC activation during EHP import

1134872 Maintenance Optimizer: FAQ for Stack Delta Files

1233954 MOPZ: No XML Generated in EPS Inbox

1122966 Maintenance Optimizer Notes for Enhancement Packages

1139493 Information about maintenance of Enhancement Package systems

1161733 SQL Server SAP EHPI for SAP Netweaver 7.0-7.1-Based Systems

1165437 Enhancement package 4 for SAP ERP - Required support packages

1156968 Add info on upgrading to EHP 4 for SAP ERP 6.0 ABAP

1240081 “Java Cryptography Extension Jurisdiction Policy” files

1287216 Maintenance Optimizer: pre-select technical usages

1233954 Maintenance Optimizer: No XML Generated in EPS Inbox

1172948 SAP Solution Manager – Basic functions



© 2011 SAP AG 4

1165067 Release Info SAP Enhancement Package 4 for SAP ERP 6.0

1064635 SAP ERP Enhancement Packages: SP Stacks Release Info Note

1160106 Enhancement package 4 for SAP ERP: Installing JAVA

1321756 Mass activation: Object activated instead of deleted

1263115 Technical settings cannot be activated

1262124 Vendor Keys for Add-ons released with ERP Enhancement Packages.

Initial Preparation

Download Enhancement Pack 4 files from SAP Service Marketplace. 1. Go to http://service.sap.com/swdc -> Download -> Installations and Upgrades -> Entry by Application

Group -> SAP Application Components -> SAP ERP -> SAP ERP Enhance Package -> EHP4 for SAP ERP6.0 / NW7.01 --> Installation and Upgrade

2. Download the 51033594 multispanning archives and extract the files. See note 886335 for information on multispanning archives.

3. Download the EHP4 patches from http://service.sap.com --> Download --> Support Packages and Patches --> Entry by Application Group -> SAP Application Components -> SAP ERP -> SAP ERP Enhance Package -> EHP4 FOR SAP ERP6.0 / NW7.01 --> Select the technical uses for which EHP4 updates will be applied and download the .sar files.

4. Validate the system in Solution Manager System.

Generating Stack file (.xml file)

1. Log into the Solution Manager system 2. Execute transaction SOLUTION_MANAGER 3. Select the System Solution 4. In the left frame select Operations 5. In the right frame select tab Change Management 6. Select Maintenance Optimizer 7. Click on Create New Maintenance Transaction

8. Click on Save 9. Select the Product Version and the system then click on Continue 10. Select Calculate Files Automatically and then Continue 11. Select Enhancement Package Installation and then click on the Find Download Files button 12. Select Target Configuration

http://service.sap.com/swdc

http://service.sap.com/



© 2011 SAP AG 5

13. After you have selected the Product Version, Target Stack, Add on, OS/DB-Dependent Files,

Independent Files, and Techincal Uses click on the Find Download Files for the stack version button

14. Once the calculation has finished you are prompted to select the kernel that you want yo use. Select

the relative kernel files for your operating system and database and then click Continue 15. Select any stack independent files if there are any and then click Continue 16. MOPZ now displays the results for the stack calculation from the SAP Service Marketplace. Be

careful to not deselect any software component that is necessary for EHP4. Click on Continue 17. Chose the download type and then click on Select Download Type

18. You will receive a confirmation that the files have been added to your Download Basket, click

Continue 19. Confirm the files in your Download Basket by clicking on the Confirm Files in Download Basket

button 20. Select all files by click on the check box next to the word File at the top of the list. Click on the

Confirm Download button 21. You will be returned to the previous screen, click on Continue



© 2011 SAP AG 6

22. The stack files now need be downloaded using the SAP Download Manager. Once the download has completed the files need to be copied to a directory on the ERP system. The files do not need to be un-carred.

Note – Download the .txt version for the Stack information file as well, and make sure that the packages mentioned in the Stack files to be upgraded are available on the server, to avoid errors.

Upgrade - EHP Installer

1. Download Enhancement Package Installer to the ERP system. a. Go to http://service.sap.com/swdc --> Download --> Support Packages and Patches --> Entry by Application Group --> Additional Components --> Upgrade tools --> SAP EHP Installer; select the appropriate version and platform, then download the .sar file.

b. Unpack the file on a disk/partition with 10-15 GB free space. An „EHPI‟ folder is created. 2. Download jce_policy 1.4.2 from http://java.sun.com and save on the ERP system.

Starting the EHPI

1. Go to folder '<drive>:\EHPI'. 2. Execute the following command from the operating system command prompt: 3. STARTUP jce_policy_zip=<path of jce policy file> 4. Once the controller is started, execute the following command.

a. Go to directory EHPI\sdt\exe b. Execute the command DSUGui.bat


http://java.sun.com/



© 2011 SAP AG 7

The SL Controller will be started on Port 4241. This is the port which we will connect to while starting the Upgrade.

5. The Installation through GUI will start and following screen will appear. Click “Logon”.

6. Click “Accept”



© 2011 SAP AG 8

7. Enter user - <SID>ADM and valid password and click “OK”.

8. Initialization Phase will start, Click “Next”.



© 2011 SAP AG 9

9. Once the phase is complete, click “Next”

10. The next phase “Extraction” the support packages are extracted in the /usr/sap/trans/EPS/in

folder



© 2011 SAP AG 10

11. Enter the pass key from the note “1302772 “ and the path for stack information file (.xml file)



© 2011 SAP AG 11

12. Once extraction is complete, the third phase “Configuration” will start where EHP Stack configuration takes place

13. Enter the valid DDIC password in the next screen and click “Continue”



© 2011 SAP AG 12

14. The “Checks” Phase will check if all the patches and software are present as per the stack information file. Once this phase is completed, click “Next” for the next phase

15. In the next phase “Preprocessing” a Shadow system is installed. For this phase, lock the

development environment when prompted during this phase. Ensure all change requests (transports) have been released before starting this phase. Ensure enough disk space exists to create a shadow instance.



© 2011 SAP AG 13

16. The Kernel information will be prompted by the system. If the Kernel patch is above the required click “OK”



© 2011 SAP AG 14

17. It will prompt for Locking the development, select “Lock now” and click on “Continue”

18. The system will prompt for the following activities to be completed

Stop all production activity

All the users should be locked out

Isolate the central instance



© 2011 SAP AG 15

Once all the above activities are performed, select “Action completed” and click on “Continue”



© 2011 SAP AG 16

19. Once the backup is successfully taken at this stage select “Backup completed” and click “Continue”. This backup is important as during the downtime, when a shadow instance will be created, if anything goes wrong the system will not come up. Hence we can bring back the system by restoring the backup taken during this phase.

20. Click “Next” on the next screen



© 2011 SAP AG 17

21. In the next phase “Downtime”, the main ABAP instance is shut down and EHP4 components are switched from the shadow instance to main instance. Ensure database logging or

archive mode is off before starting this phase.



© 2011 SAP AG 18

22. In the next screen, after taking the database back up, select “Action Completed” and click “Continue”

Note – Make sure you continuously monitor the DB space during this phase.



© 2011 SAP AG 19

23. Post Processing - During this phase, Modification adjustments are completed (by ABAP person as Basis is not responsible for this). If the system has unmodified objects, then

transactions SPAU and SPDD are executed to adjust the modifications.



© 2011 SAP AG 20

24. The system will prompt for SPAU/SPAD adjustments (performed by ABAP person), once completed select “Adjustment completed” and click “Continue”

25. The system will provide the system information in the next screen. Please go through the information and click “Close”



© 2011 SAP AG 22

26. The Enhancement Package Installation Evaluation page will open at the last stage of Post processing phase

27. The EHP Installation Information will have all the information related to upgrade



© 2011 SAP AG 23

28. Save the EHP Upgrade information file and click “Continue” in the next screen.

29. Click “Exit” in the next screen. And “Next” in the proceeding screen



© 2011 SAP AG 25

Errors and their resolution

Error - Unable to execute SDT on ABAP configuration

Resolution – Check the logs, add the missing ABAP package at usr\sap\trans\EPS\in forlder and re-start the installer.



© 2011 SAP AG 26

Error - User <SIDADM> is locked in the system

Resolution – Follow the below mentioned steps

a. Remove the following (in the directory put\ua) files to another place: UaState ks

b. Stop Upgrade assistant server; c. Run the following command in the OS level with <sid>adm user to restart the Upgrade Assistant

Server: java -cp ua.jar UaServer

d. You will be promoted to input a new password and the uagui.jar file will be re-signed. Then you can start UA gui to logon the upgrade assistant.



© 2011 SAP AG 27

Error - Import prerequisites not fulfilled

Resolution – Download the mentioned prerequisite as per the log file and restert the phase from the beginning. For this and all similer error, plese follow the same step.

To avoid this error, make sure, you have all the packages and their prerequisite at EPS/in before starting the upgrade



© 2011 SAP AG 28

Error - during Downtime phase – “Checks after phase MAIN_NEWBAS/XPRAS_UPG were negative

Resolution – Note '1467470 - NR: Check of subobject value table' must be applied manually, follow the below steps

1. Unlock the system, by executing following commands:

/usr/sap/<SID>/SYS/exe/run/tp pf=<EHPI directory>/ abap/bin/DEFAULT.TPP unlocksys <SID>

/usr/sap/<SID>/SYS/exe/run/tp pf=<EHPI directory>/ abap/bin/DEFAULT.TPP unlock_eu <SID>

2. Now you should be able to logon into the system with a user different from DDIC.

3. Apply the note's changes manually. Please take into account the note's prerequisites' corrections from note 1467470 have to be applied also.

4. Lock the system with the following commands: tp locksys <SAPSID> pf=D:\usr\sap\trans\bin\TP_DOMAIN_ECS.PFL tp lock_eu <SAPSID> pf=<transport profile> D:\usr\sap\trans\bin\TP_DOMAIN_ECS.PFL

5. Repeat the failing phase.



© 2011 SAP AG 29

Error - During the downtime, continue monitoring the DB space, because due to space constraint the upgrade might get stuck at one particular phase without giving any error message

Resolution – To free some space, you can shrink the DB

1. Go to SQL Server Management Studio –> ECS-Task –> Srink –> Database



© 2011 SAP AG 30

Related Content

http://service.sap.com/erp-ehp

http://service.sap.com/instguidesNw70

http://service.sap.com/erp

http://service.sap.com/sp-stacks


http://wiki.sdn.sap.com/wiki/display/ESpackages/SAP+ERP+6.0

SAP enhancement package 4 for SAP ERP 6.0

Enhancement Packages

http://service.sap.com/erp-ehp

http://service.sap.com/instguidesNw70

http://service.sap.com/erp

http://service.sap.com/sp-stacks


http://wiki.sdn.sap.com/wiki/display/ESpackages/SAP+ERP+6.0

http://wiki.sdn.sap.com/wiki/display/ESpackages/SAP+enhancement+package+4+for+SAP+ERP+6.0

http://wiki.sdn.sap.com/wiki/display/ESpackages/Enhancement+Packages



© 2011 SAP AG 31

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

upgrade guide for sap ecc 6.0 enhancement package 4

Documents