How to Install ERP Enhancement Pack 4

8/11/2019 How to Install ERP Enhancement Pack 4

http://slidepdf.com/reader/full/how-to-install-erp-enhancement-pack-4 1/45

How to install SAP Enhancement

Package 4 for SAP ERP A practical guide

EHP4 Ramp-Up Technology BackofficeSAP AG

Version 1.2, 17.03.2009



Legal Disclaimer

This presentation is not subject to your license

agreement or any other agreement with SAP. SAP hasno obligation to pursue any course of business outlined

in this presentation or to develop or release any

functionality mentioned in this presentation. This

presentation and SAP's strategy and possible future

developments are subject to change and may be

changed by SAP at any time for any reason without

notice. This document is provided without a warranty of

any kind, either express or implied, including but not

limited to, the implied warranties of merchantability,

fitness for a particular purpose, or non-infringement.

SAP assumes no responsibility for errors or omissions in

this document, except if such damages were caused by

SAP intentionally or grossly negligent.



Key facts on the EhP4 installation

EhP 4 requires a Solution Manager (at least SP 15) Maintenance Optimizer must be set up and running

(check Note 1122966)

The System Landscape in Solution Manager (SMSY)

must be defined and up to date

Maintenance Optimizer analyzes the ERP’s software

components and calculates a list of packages

Enhancement Package 4 is installed with a new tool

(SAPehpi).

SAINT is not supported anymore (see Note 1256600).

SAPehpi tool reads the list of packages from SolutionManager

The SAPehpi tool reduces the downtime dramatically

Always combine the installation of Enhancement Packages

with the installation of the latest Support Package Stack



Recommendations on implementation

procedure of SAP enhancement packages

Reading sequence:

How to install SAP

Enhancement Package 4

EHP 4 Master Guide EHP Installation

Guide

1

2

3

To get a quick start and overview of the EHP technology

and installation essentials read the Must Know Guide

The documentation can be found via: http://service.sap.com/erp-inst

http://service.sap.com/~sapidb/011000358700000293582009E.PDF


http://service.sap.com/~sapidb/011000358700000782642007E




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












Agenda

SAP Solution Manager

- Prepare Solution Manager

- SMSY- Maintenance Optimizer

- Troubleshooting

SAP Enhancement Package Installation

- EHP Installer - Troubleshooting

1

2



Overview About Main Steps Of EHP

Installation Procedure

SAP

Solution Manager

ABAP + JAVASLD

Portal 7.0*

ECC

Server

SAP ERP 6.0

ABAP

SAP NetWeaver

Portal

Java

EP

Stack.XML

SAPehpi

Mopz

SAPehpi

Sample system landscape

4. Update systems

5. SAPehpi Troubleshooting

1. Prepare Solution Manager

2. Download packages and generate Stack

XML via Maintenance Optimizer

3. Solution Manager Troubleshooting



Getting started with EHP Installation:Summary of the most important preparation steps

1. Solution Manager Preparation

-In general: review the set up of your Solution Manager

System and System landscape (Transaction SMSY), note

1022072 gives for further information (e.g. Product

version of your system has to be = ERP 6.0 NOT ECC

6.0)

-Download of EHPs & SP Stacks only with use of

Maintenance Optimizer when using SAPehpi

-Solution Manager generates a XML file. This is arequirement for the installation!

-Up-to-date Solution Manager System (Patches), more

information: Note 1165438

-XML file is generated and stored in /EPS/in of Solution

Manager System (configuration required!)

Further help:Implement Note 1233954 (No XML in EPS Inbox)

Note 1134872 (FAQ for Stack Delta Files in EPS)

Note 1122966 (Maintenance Optimizer for EHP)

Note 1090202 (MOPZ: adjust stack delta XML)

Note 1165587 (MOPZ: EHP stack selection)

Note 1277035 (EHP4 product data missing)

2. Download Enhancement Package

- Download the Enhancement Packages via selection

of “Technical Usage”, for more information see Note

1165438

3. Get familiar with the EHP Installer

- Download & Study EHP Installer Guide provided on SAP

Service Marketplace: http://service.sap.com/erp-inst

Go to SAP ERP 6.0 SAP enhancement packages forSAP ERP 6.0 SAP enhancement package 4 for

SAP ERP 6.0

- Download your EHP Installer tool provided on SAP

Service Marketplace: http://service.sap.com

Go to Support Packages and Patches Additional

Components Upgrade Tools SAP EHP INSTALLER 7.00

Prepare free space for… Installation directory “EHPI” of app. 10-15 GB *

“Download” directory for EHP & SPs of app. 10-30

GB *

Shadow instance of app. 100 GB (depends on

customer situation)*

Additional space for existing tablespaces (depends on

available freespace in each tablespace)

Autoextend setting for tablespaces recommended* temporary space



Solution Manager Preparation


• In general: review the set up of your Solution Manager System and System landscape (Transaction SMSY),

note 1022072 gives for further information (e.g. Product version of your system has to be “ERP 6.0” and not

“ECC 6.0”)

• Download of EHPs & SP Stacks only possible with use of Maintenance Optimizer in Solution Manager.

• The Solution Manager generates a XML file. This is a requirement for the installation.

• Up-to-date Solution Manager System (SP 15), more information: Note1165438

• SAP Notes to apply: See note 1122966

• XML file is generated and stored in /EPS/in of Solution Manager System (configuration required!)

Further help:

Implement Note 1233954 (No XML in EPS Inbox)



Note 1090202 (MOPZ: adjust stack delta XML)

Note 1165587 (MOPZ: EHP stack selection)





1. In transaction SMSY, check the server :

Before you can check the set up of your system, it

is essential to review, if an entry for your server

was created or to create it.

1) in “SMSY”, navigate in the left frame to“Landscape Components Server”

Check if the Server name is in place

2) To create a new entry, cl ick with r ight mo use

button on server, choose “Create New Server” andfill in the dialog with your server’s data (hostname).

2. After having checked your server, proceed to

check the system in transaction SMSY.

1) in “SMSY”, in the left frame navigate to“Landscape Components Systems”

Open SAP ERP and check if the SID is in

place

2) To create a new entry, click with r ight mou se

button on “Systems” and fill in your system’s data

(even if you are already on ERP EHP, register as

regular ERP!)




3. Switch to the tab “Clients” and maintain at least client 000. As soon as you have

maintained this client.

4. Then click on the RFC wizard

and create an RFC connection to

that system and client 000 (or any

other client).5. Now you can automatically

read the system data via the

button „Read System DataRemote“.

This should remotely read the system data and update the information about this system.

Check the tab “Clients” and/or “Software Components” and verify that the information therehas been updated. It is important to have the exact versions of the Software Components

maintained. Only then a valid stack of support packages and enhancement packages can be

calculated!




6. Create a new logical component.

Also in “SMSY”, click on “SystemGroups and Logical Components”.

With the right mouse button click

on “Logical Components” andcreate a new logical component.

Fill in your system data, let the

name for your logical component

start with “Z...”.

7. In the “Current System Assignments” of the newly created logical component, add

your system with the appropriate role (e.g. as “Production System”).




8. Check transaction “solution_manager”for an existing solution. If you do not have

a solution yet, create one.

9. In transaction “solution_manager”, click on your solution and go to “SolutionLandscape” and “Solution Landscape Maintenance”.




• Change into edit mode

• Select line (new line in

field logical

component, F4 help)

• Select your system

from list (SAP ERP,logical component)

• Save selection

• Click on button

“complete system datareplication” beforesaving

10. Then add your ERP system to the solution as follows:

Further help:







If you have a Dualstack

system, then make sure that

the Java part is correctly

maintained in SMSY.

The correct way is toregister both the Java

system and the ABAP

system in a central SLD (via

Visual Administrator) and to

schedule SLD update jobs

from within SMSY_SETUP.

On the right side you cansee how a properly

maintained Java system

looks like.

11. Java systems



Agenda




- Troubleshooting



1

2



Download packages and generate Stack XML

via Maintenance Optimizer

Generation of the XML stack file

Solution Manager generates a XML file. This is a requirement for the installation!

XML file is generated and stored in /EPS/in of Solution Manager System (configuration required!)

Go to transaction “solution_manager” and select your solution. Then go to“Operations”, “Change Management”, “Maintenance Optimizer” and create anew Maintenance Transaction.



Set up initial data for the new Maintenance

Transaction:

1) Select product version “SAP ERP 6.0”2) Select your system

3) Press continue



If you have a landscape of systems

(Development, Quality Assurance,Production) the recommended way

is to generate a single XML file for

all of the systems.

Therefore, select all the systems

where you want to generate the

XML file for.



1) Select the Product Version which

should be installed (combinations

that are not compatible with yoursetup can’t be selected)

2) Tick the checkbox of the Technical

Usage that you want to install

3) Click the button “Find DownloadFiles”

A note on the product version:

EHP 4 for SAP ERP 6.0

EHP 4 for SAP ERP 6.0 / NW 7.01

If you are using ECC on ABAP only, you can

choose either product version. Check the

EHP4 Master Guide for more information.



1) For ERP Enhancement Packages

choose the radio button

“Enhancement PackageInstallation”

2) Click on “Find Download Files”



Download Enhancement Package

Download the Enhancement Packages via selection of “Technical Usage”, more information: Note 1165438

Prepare free space for… “Download” directory for EHP & SPs of app. 10-30 GB *

* temporary space

1) Select the correct OS/DB Kernel Parts

Note: DB2 IBM DB2 for z/OSDB4 IBM DB2 for i5/OS

DB6 IBM DB2 UDB for

Linux, Unix, and

Windows

2) Click on „Continue“3) Step through „Select Files w/o Stack

Dependence“





1) Confirm the calculated package queue by clicking “Continue”

2) Tick the radio button for downloading the software via the Download Manager3) Click the button “Select Download Type”



Further help:



Note 1233954 (No XML in EPS Inbox)



1) Click “Continue”2) Click button “Confirm Files in Download Basket”3) In the new window, tick the upper left checkbox to select all

files

4) Click on “Confirm Download”5) Now you can download the files with Download Manager

At that point of time the stack information has been written into the

database of Solution Manager and additionally as physical files

(XML file & TXT file) provided to directory …/usr/sap/trans/EPS/in





Agenda




- Troubleshooting



1

2



Solution Manager Troubleshooting

If you want to install a Technical

Usage but you are not able to check

it, move the cursor over it and see

which main instances you are

missing.

In this case, go back to transaction

“SMSY” and mark the missing maininstances as being relevant. If you get a

warning doing that, mark the main

instance as “Also Installed”.

MOPZ cannot find some required

main instances on your system.

“A Technical Usage cannot be selected”




“Only one EHP release is allowed”

This problem is documented in Note

1139602.

If you get this error message, then you

already have installed another enhancement

package on this system before (for example

EHP3).

The error tells you that you have chosen too

few Technical Usages. If you continued with

this selection, you would not update all of the

software components to EHP4 that are

currently on EHP3. So in the end, some

software components would be on EHP3

while others would be on EHP4. That way you

would have several EHP versions in one

system which is a state that is not supported.

MOPZ requests you to select more Technical

Usages and proposes you a list to choose

from.

If you have implemented Note 1287216 as

proposed here in the screenshot by

Maintenance Optimizer, then it will

automatically detect the Technical Usages

that are already installed on your system.

You can always install the same or more

Technical Usages than you had installed

previously with the older enhnacement

package, but never less.






“No XML Stack file is generated”

If it is not generated, make sure that you

have performed the IMG activitySOLMAN_MOPZ_SLM_CONF. This is

documented in SAP Note 1134872.

Make sure that you have implemented the

correction of SAP Note 1233954.

The XML Stack file is generated right before you are asked to confirm the files of your

download basket.

The XML Stack file is written to the subfolder “in” of $(DIR_EPS_ROOT) of your SAP SolutionManager system. You can use transaction RZ11 to check the value of that variable.

The name of the XML Stack file is like in the following example:

SMSDXML_SID_20090112140052.532.xml





Agenda




- Troubleshooting



1

2



Overview About Main Steps Of EHP

Installation Procedure

SAP

Solution Manager

ABAP + JAVASLD

Portal 7.0*

ECC

Server

SAP ERP 6.0

ABAP

SAP NetWeaver

Portal

Java

EP

Stack.XML SAPehpi

Mopz

SAPehpi

Sample system landscape

4. Update systems

5. SAPehpi Troubleshooting

1. Prepare Solution Manager

2. Download packages and generate Stack

XML via Maintenance Optimizer

3. Solution Manager Troubleshooting



© SAP 2008 / Page 30

Using the Enhancement Package Installer

SAPehpi)

Get familiar with EHP Installer

Download & Study EHP Installer Guide provided on

SAP Service Marketplace:


Go to SAP ERP 6.0 SAP enhancement

packages for SAP ERP 6.0 SAP enhancement

package 4 for SAP ERP 6.0

Download your EHP Installer tool provided on SAPService Marketplace: http://service.sap.com

Go to Support Packages and Patches AdditionalComponents Upgrade Tools SAP EHP INSTALLER 7.00

Prepare free space for…

Installation directory “EHPI” of app.10-15 GB *

“Download” directory for EHP &

SPs of app. 10-30 GB *

Shadow instance of app. 100 GB

(depends on customer situation)*

Additional space for existing

tablespaces (depends on available

freespace in each tablespace) Autoextend setting for

tablespaces recommended

* temporary space



Ways to install Enhancement Package 4

Case Enhancement Package Level Tool

Installation of … on existing SAP ERP 6.0 system landscape

Enhancement Package 4 for SAP ERP 6.0 ABAP: SAPehpi*

Java: SAPehpi**

Upgrade to SAP ERP 6.0 and inclusion of …

Enhancement Package 4 for SAP ERP 6.0 ABAP: SAPup

Java: SAPJup

*Using transaction SAINT for the installation of Enhancement Package 4 is NOT supported (except for 32-bit systems).

** If technology update is not intended, you have to use JSPM.

With Enhancement Package 4, SAP delivers the Enhancement Package Installer

(SAPehpi). SAPehpi is mandatory for the installation of Enhancement Package 4.



Starting the SAPehpi

Extract the SAPehpi

package.

Note that SAP

Enhancement Package

Installer installation

directory path must not be

longer than 45 characters.

SAPehpi has to be

executed by user

<SID>adm

Before you start, please

remove any old and

outdated profile files from

the profile directory (even

if they are renamed).

Startup procedure (also check SAP Note 1245473)

On Unix EHPI>./STARTUP jce_policy_zip=<Policy-Zip file>

On

Windows

EHPI> STARTUP.BAT "jce_policy_zip=<Policy-Zip file>"

(mind the double quotes)

S S



Starting the SAPehpi

Start the SAPehpi front end.

The web page offers you to:

Read the manual on the

Service Marketplace

Start the SAPehpi GUI

Read the SAPehpi

documentation (ABAP part)

Java EE Enhancement

Package Installation

evaluation

EHP I t ll



EHP Installer

Before the system

analysis… Only the Monitor tab is

shown

To initialize the process,

press Next

EhP I t ll ti U i SAP h i



EhP Installation Using SAPehpi

– the Main Blocks

EhP installation – main blocks: Preparation

All objects and passwords are provided

Shadow system (ABAP) are created and filled

System prerequisites are checked and can be adjusted if necessary Hint : Therefore its recommended to run this block as soon as possible. All steps can be repeated if necessary.

Processing

Point of no-return is reached (later than before)

Downtime:

– System is switched (ABAP)

– Deployment is executed with JSPM (JAVA)

Postprocessing

In AS ABAP based systems SGEN runs (optional step)

SAPehpi finalizes

1 2 3 4 5 6 7 8

Processing PostprocessingPreparation (no changes to the system)

Initialization Extraction Configuration Checks Preprocessing Downtime Postprocessing Finalization

EHP I t ll



EHP Installer

System analysis:

Step completed

AS ABAP identified

Note, that in systems based

on AS ABAP and AS Java,

both stacks will be updated

synchronously – you will see

tabs “ABAP” and “J2EE” nextto the “Monitor”.

EHP I t ll



EHP Installer

Performance parameters:

In the configuration phase youare prompted to select one ofthree performance models.

Your choice influences thenumber of parallel processesthat will work during the

installation.

It is always recommended to gofor the “Manual selection ofparameters” since that way youcan best adapt the number ofprocesses to your specificsystem.

For additional information,please refer to Troubleshootingand Administration Guide,chapter 3.2.3 BackgroundProcess and Tool Parameters.(located in the EHPI Installationdirectory).

EHP I t ll



EHP Installer

Observer mode and Alert

mechanism

It is possible to monitor theinstallation of SAPenhancement package 4 forSAP ERP 6.0.

You can also configure analerting mechanism thatinforms you if the installationis stopped and is waiting forinput. The alerting could bedone via e-Mail or SMS forexample.

For more information, checkout the Blog entry at

https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/12870

A d









Agenda




- Troubleshooting



1

2

SAPehpi Troubleshooting




During the installation of EHP4 you will be asked how to deal with Add-Ons. You have

two possibilities

Keep the current version

Upgrade the Add-On with a SAINT package

Not all Add-Ons are released for EHP4, check Note 1226284 for details.

How to deal with Add-Ons





You do not need to transfer the XML-Stack file manually from Solution Manager to the target system.

EHPI can get that file automatically by an RFC call.

Retrieving the stack from SAP Solution Manager by RFC

If you cannot get this to work, then log in to

the target system and check table

BCOS_CUST via transaction SM30 and

make sure that you see the name of the

RFC connection to SAP Solution Manager.





HR support packages

(software components

SAP_HR and EA_HR) are

released more often than a

complete SAP enhancement

package support package

stack.

You can manually download

and then include those

Support Packages in EHPI. In

phase BIND_PATCH you are

prompted if you want to add

further Support Packages tothe target release.

Including the latest HR Support Packages into the installation

Extract the Support Packages to the EPS/in directory, choose “Yes” and click the “Ok”

button. EHPI will now propose you to add the extracted Support Packages to the

installation queue.





You can find more information about EHPI

troubleshooting in the EHPI Troubleshooting

Guide.

See http://service.sap.com/erp-inst “SAPERP 6.0” “SAP enhancement packages for

SAP ERP 6.0” “SAP enhancement

package 4 for SAP ERP 6.0”

You can find the Troubleshooting Guide at the

bottom of the page.

SAPehpi Troubleshooting Guide

Thank you for your time







Questions or

Feedback?

Thank you for your time.

EHP4 Ramp-Up Technology Backoffice:

Christian Oehler ([email protected])

Martina Kerner ([email protected])

Uwe Cudok ([email protected])

Joachim Wieland ([email protected])

Further Information On SAP Enhancement

mailto:[email protected]










Further Information On SAP Enhancement

Packages

What IT professionals must know

about SAP Enhancement PackagesSAP Enhancement Packages -

Frequently Asked Questions

Lifecycle of SAP

Enhancement Packages

SAP Enhancement Package

Strategy for SAP ERP

ERP@BPX: EHP Forum & Wiki

1

2

3

5

6

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



http://download.sap.com/SMIGlobal/download.epd?context=08D5201C4C9004729A98E8E688C8F275134ECE07E585B6ED15C59860F5810EB5F5A1DFC0D66A2E6EA6182BAE17A25F13D717D57F51E6ACA7






http://www.sdn.sap.com/irj/bpx/bpx-erp





http://www.sdn.sap.com/irj/bpx/bpx-erp














Documents

How to Install ERP Enhancement Pack 4