Embed Size (px)
Citation preview
How to Install SAP Enhancement
Package 4 for SAP ERP 6.0
A Practical Guide
This document serves as a set of step-by-step instructions
for the installation of SAP enhancement package 4 for SAP
ERP 6.0. It describes the necessary actions for configuring
and using SAP Solution Manager as well as the most
important steps in the SAP Enhancement Package installer.
Version 1.07
2009-08-26
Page 2
Table of Contents
1 Introduction ....................................................................................................................3
1.1 Purpose of This Document ..................................................................................................3
1.2 Target Group ......................................................................................................................3
1.3 The Big Picture – Step by Step ...........................................................................................4
2 Pre-Installation Tasks .....................................................................................................6
2.1 Identification of Required Functionality ............................................................................6
2.2 SAP Solution Manager .......................................................................................................6
3 SAP Solution Manager ...................................................................................................7
3.1 Support Package Level of SAP Solution Manager .............................................................7
3.2 System Landscape (SMSY) of SAP Solution Manager ......................................................7
3.3 SAP Solution Manager Maintenance Optimizer .............................................................. 11
3.4 SAP Solution Manager Troubleshooting.......................................................................... 17
4 The SAP Enhancement Package installer ..................................................................... 21
4.1 How SAP Enhancement Packages are installed ............................................................... 21
4.2 Prerequisites ...................................................................................................................... 21
4.3 Where to Get SAPehpi and Its Documentation................................................................ 22
4.4 Roadmap Steps of SAPehpi .............................................................................................. 24
4.5 Installation Prerequisites .................................................................................................. 24
4.6 Startup of SAPehpi ........................................................................................................... 24
4.7 SAPehpi Tips & Tricks ..................................................................................................... 25
4.8 SAPehpi Troubleshooting ................................................................................................. 26
5 Further Information ..................................................................................................... 28
5.1 Relevant SAP Notes .......................................................................................................... 28
5.2 Relevant SAP Documentation .......................................................................................... 29
5.3 SAP Support...................................................................................................................... 29
5.4 Feedback ........................................................................................................................... 30
5.5 Disclaimer ......................................................................................................................... 30
Page 3
1 INTRODUCTION
SAP enhancement packages represent a new software delivery strategy that allows you to add
innovations on top of SAP ERP 6.0 without the need for fully upgrading your current release. SAP
enhancement packages for SAP ERP include functional enhancements, industry-specific
enhancements, UI simplifications, as well as enterprise service bundles. To discover and evaluate
which innovations are shipped in which SAP enhancement package, visit the SAP Service
Marketplace: http://service.sap.com/erp-ehp.
1.1 Purpose of This Document
This document serves as an end-to-end guide and describes the necessary steps for installing SAP
enhancement package 4 for SAP ERP 6.0. Therefore, it not only covers the actual installation, but
also explains the setup of SAP Solution Manager, now a mandatory requirement for the installation of
SAP enhancement package 4. However it does not replace the Installation Guide for SAP
Enhancement Package Installation.
Furthermore, this document links to the guides and SAP Notes that SAP provides. Getting familiar
with that documentation will help you to minimize implementation efforts.
This document contains screenshots to better visualize the installation procedure. Please note that of
course all screenshots are for demonstration purposes only, all shown hostnames, system IDs, software
patch versions and similar information only serves as an example and might be different in your case!
1.2 Target Group
This document is written for technical consultants and SAP administrators, so
you should be experienced in SAP technology, installations and ideally also in
upgrades.
This document assumes that you have read the SAP enhancement packages
Must-Know-Guide. Further important sources of information are the SAP
enhancement packages Technology Facts presentation and the Lifecycle of an
SAP Enhancement Package for SAP ERP presentation.
Page 4
1.3 The Big Picture – Step by Step
With SAP enhancement package 4, a new installation procedure became mandatory. See below for the
interaction of all involved parties.
1. First, you have to
select the required technical
usages in the Maintenance
Optimizer functionality
from SAP Solution
Manager. Maintenance
Optimizer calculates a
system-specific list of
packages that have to be
installed on the target
system. This system-
specific list is saved in a
stack configuration file.
Maintenance Optimizer also
places all packages that
have to be installed in your
download basket in order to facilitate an easy download of all required packages. To calculate
that stack configuration, SAP Solution Manager relies on the information of SMSY and from
the SLD about the target system.
2. You install the software on the target system with the SAPehpi (SAP enhancement package
installer) tool. It imports the software components into the target system. This could be an
SAP ERP 6.0 system or an SAP NetWeaver system (such as a Portal or a BI system).
Here is a short overview of some technical terms used in this document:
SMSY The SAP Solution Manager System Landscape collects information about the SAP systems in the landscape. (SMSY is the name of the transaction in SAP Solution
Manager.)
SLD The System Landscape Directory is a Java software component that is installed on any SAP NetWeaver Java system. It can be configured to contain information
about all the Java systems in a landscape. It can also contain information about
ABAP systems. Usually you use one central SLD for your whole SAP system
landscape.
Maintenance
Optimizer
The SAP Solution Manager Maintenance Optimizer is a functionality that guides
the user through maintenance procedures for any system in the landscape.
Maintenance Optimizer is part of SAP Solution Manager and uses the information that is stored in the SAP Solution Manager System Landscape.
Page 5
Stack
configuration
file
The stack configuration file is created by the Maintenance Optimizer and is
system-specific. Depending on the software components that are installed in a
system, the Maintenance Optimizer calculates the required software components
that have to be installed additionally in order to reach a certain target configuration.
Target
system
The SAP ERP 6.0 system on which you are going to install SAP enhancement
package 4 for SAP ERP 6.0.
SAPehpi The SAP enhancement package installer is the tool that installs the SAP
enhancement packages in the systems. It can drastically minimize the downtime of
the system compared to the previous installation method. It reads the software components to install from the stack configuration file.
For a complete overview of the architecture of SAP enhancement package 4 please read the SAP
enhancement package 4 Master Guide. See the chapter “Relevant Documentation” further down in this
document for information about where you can find the Master Guide and other SAP enhancement
package 4 related documents.
If you have questions on SAP enhancement package 4 feel free to contact the SAP EHP Technology
Backoffice. You can find more information about the Backoffice in the section “EHP Technology
Backoffice”.
Page 6
2 PRE-INSTALLATION TASKS
2.1 Identification of Required Functionality
SAP enhancement packages contain new functionality. In order to use the new functionality, you have
to activate a business function in your ABAP system1.
From a technical point of view, you do not install single business functions, but instead you install a
technical usage. Business functions are grouped into technical usages. You can map the business
functions that you want to activate to the technical usages that you have to install in the system using
the attachments of SAP Note 1165438 (EHP4).
The technical usages that you are going to install contain the software components that you have to
install in your system. Even though this mapping is described in SAP Note 1165438 as well, you do
not really need to deal with that part of the SAP Note by yourself, because in the Maintenance
Optimizer of your SAP Solution Manager you only select the required technical usages. All software
components that are contained in those technical usages are added to the stack automatically.
The concept of SAP enhancement packages is to enable the customer to enhance only specific
software components of the system with new functionality. In accordance to that strategy, you should
always install a very limited number of technical usages and never need to install the complete set (i.e.
all or most of the technical usages). Even though this is technically possible, you should try to be as
conservative as possible with regards to the number of technical
usages that you select. This is especially true for Industry Solutions:
If you have already activated an Industry Solution or plan to do so in
the near future, then please select only the technical usage of that
Industry Solution. If you have not yet activated an Industry Solution
in your system and you are not planning to do so, then there is no
need to install the technical usage of any Industry Solution at all.
2.2 SAP Solution Manager
SAP Solution Manager 7.0 plays a central role in the SAP enhancement package 4 installation process.
You use the Maintenance Optimizer of SAP Solution Manager in order to calculate a system-
dependant stack of software components to be installed in the target system. Therefore, of course, SAP
Solution Manager must be up to date, must be set up correctly, and needs to have up-to-date
information about the system landscape. This will be described in the next section.
1 Note that switchable business functions only exist for ABAP systems. In Java all installed software is
automatically switched on.
Please make sure that you have performed all activities that are listed in the “Planning” section of
the respective installation guide. See section “Getting the Documentation for the SAPehpi
Installation” for information on where to find the respective installation guide (different versions
for different operating systems and databases exist).
You should try to be as
conservative as possible
with regards to the
number of technical
usages that you select.
Page 7
SAP recommends
using the latest
version of SAP
Solution Manager
7.0.
3 SAP SOLUTION MANAGER
This section gives you an overview of the steps for successfully installing SAP enhancement
package 4 for SAP ERP 6.0. First, we provide an overview of how to set up and use SAP Solution
Manager 7.0. Then we sketch the installation process itself.
3.1 Support Package Level of SAP Solution Manager
In order to calculate the individual software stack for an SAP enhancement
package installation, the SAP Solution Manager must meet certain
prerequisites.
The requirements are described in SAP Note 1165438. It is SAP’s
recommendation to always use the latest Support Package level for SAP
Solution Manager 7.0. In addition, the corrections listed in the collective
SAP Note 1122966 and SAP Note 1172948 should be implemented. Also
make sure to execute the guided setup procedure SOLMAN_SETUP.
3.2 System Landscape (SMSY) of SAP Solution Manager
The target system for the SAP enhancement package installation must be maintained correctly within
the SAP Solution Manager’s system landscape (transaction SMSY).
If you have your system already registered in SMSY, use this documentation to check for the correct
registration.
If your target system is not yet registered, you can also use
the assistant that guides you through the following steps. In
order to use the assistant, in transaction SMSY, navigate to
Landscape Components and right click on Systems. Select
Create System with Assistant to start the guided procedure.
This example assumes that you are already on SAP ERP 6.0
and only want to install SAP enhancement package 4. If you
are combining the installation of SAP enhancement package 4 with an upgrade, you have to register
the system according to the start release of the upgrade.
3.2.1 Server
Before you can check the set up of your system, it is essential to
review if an entry was created for your server:
1. Go to transaction SMSY and in the left frame choose
Landscape Components → Server.
2. Check if the server name is listed.
If it has not yet been created, then create it as follows:
Page 8
3. To create a new entry, click with the right mouse button
on Server, choose Create New Server and enter your
server’s data (usually this is the host name).
3.2.2 Product Version and System
After having checked your server, check the system in transaction SMSY.
1. Go to transaction SMSY and in the left frame choose Landscape Components → Systems.
2. Open the subtree SAP ERP and check if the system ID of your target system is in place.
If there is no SAP ERP entry yet, then create it as follows:
3. To create a new entry, click with the right mouse button on Systems and fill in your system’s
data.
The ERP 6.0 system must have the product version SAP ERP 6.0. Make sure that it is not accidentally
maintained as SAP ECC 6.0.
3.2.3 RFC Wizard
Choose the tab Clients and maintain at least client 000.
Now you can use the RFC wizard to create the
required RFC connections between the SAP Solution
Manager system and the target system.
Click the button for the RFC wizard to start the wizard.
Even if you already have installed SAP
enhancement packages, register the
system as a regular SAP ERP 6.0
system!
Also, make sure that your system is not
registered as an SAP ECC 6.0 system!
Page 9
3.2.4 Data Transfer
After you have created the required RFC connections, SAP Solution Manager can log in to the target
system and read the system data remotely. To initiate the transfer, click on the button Read System
Data Remote.
You should schedule automatic data transfers using transaction SMSY_SETUP.
3.2.5 Java Systems
If you have a dual-stack system, then make sure that the Java part is correctly maintained in SMSY.
The correct way is to register both the Java system and the ABAP system in a central SLD and to
schedule SLD update jobs from within SMSY_SETUP (see SAP Help).
The Java system is registered via Visual Administrator (see SAP Help) and the ABAP system is
registered via transaction RZ70 (see SAP Help).
On the left, you
can see an
example for a
properly
maintained Java
system.
Page 10
3.2.6 Creating the Logical Component
Create a new logical component or check
your existing setup as follows:
1. Also in transaction SMSY, choose
System Groups and Logical
Components.
2. With the right mouse button click on
Logical Components and create a
new logical component.
3. Enter your system data. The name of
your logical component should start
with “Z...”.
3.2.7 Assigning the System to the Logical Component
In the Current System Assignments of the newly created logical component, add your systems with the
appropriate roles (such as Development System or Production System). We recommend adding all
systems of one product to one Logical Component. This means that you create one Logical
Component and add the Development system, the Quality Assurance system and the Production
system to the same Logical Component.
3.2.8 Adding the System to a Solution
Use transaction “solution_manager” to
check for an existing solution. If you do not
have a solution yet, create one.
In transaction “solution_manager”, choose your solution and go to Solution Landscape and Solution
Landscape Maintenance.
Then add your SAP ERP 6.0 system to the solution as follows:
1. Change to edit mode.
2. Place the cursor on a new line in the column Logical Component.
3. Use the input help to select your system from the list (SAP ERP, logical component).
4. Save your selection.
5. Choose Complete System Data Replication before saving.
Page 11
3.3 SAP Solution Manager Maintenance Optimizer
3.3.1 Overview
For each SAP enhancement package installation, a system-specific SAP enhancement package stack
definition has to be calculated by SAP Solution Manager Maintenance Optimizer. The SAP
enhancement package stack definition consists of Support Packages of the start release (Support
Packages of SAP ERP 6.0), SAP enhancement packages, and Support Packages for the SAP
enhancement packages. The stack definition is then used by the SAP enhancement package installer
(SAPehpi) and informs the installer about the packages that have to be installed on the target system.
3.3.2 Navigation
Log on to your SAP Solution Manager system and start transaction DSWP (or
SOLUTION_MANAGER). In the left frame, select Solution Overview. Then choose the solution that
contains the SAP ERP 6.0 system on which you want to install the SAP enhancement packages.
1. In the left frame switch to Operations.
2. Then, choose the tab Change Management.
3. Choose Maintenance Optimizer.
4. Choose Create New Maintenance Transaction.
Page 12
3.3.3 Setting up Initial Data
To set up initial data for the new Maintenance
Optimizer transaction, you can assign a priority
and a short text to the Maintenance Optimizer
transaction.
In the lower part of the screen, select the Product
Version from the drop-down list. Select your SAP
ERP 6.0 target system from this list.
Choose the button “Continue”.
We recommend creating one maintenance transaction for the entire
system landscape (development, quality assurance, production).
This will result in a single stack definition file for all of the systems.
Therefore, select all the systems for which you want to generate the
stack definition.
On the next screen, choose Enhancement Package
Installation as the desired action. Choose Find Download
Files. If you do not see the option Enhancement Package
Installation, but instead only Maintenance, check the SAP
Solution Manager Troubleshooting chapter further down in
this document.
Page 13
3.3.4 Selecting the Target Configuration
On the next screen, you select the target configuration that you want to reach on the system where you
want to install SAP enhancement package 4. A target configuration consists of:
A product version (for example SAP enhancement package 4)
A Support Package stack number for that product version
One or more technical usages that should be installed
1. Select the product version which should be installed
You can choose one of the following two product versions for SAP enhancement package 4:
EHP 4 for SAP ERP 6.0
o Use this product version for ABAP-only systems and if you do not want to update
your connected Portal or BI to 7.01.
EHP 4 for SAP ERP 6.0 / NW 7.01
o Use this option for dual-stack systems.
o Use this option if you want to update your Portal or your BI system to 7.01.
SAP always recommends downloading the latest available Support Package stack.
2. Select the checkbox of the technical usage(s) that you want to install.
In order to be able to select the technical usages, you should know which business functions will
be activated in the system after the installation. If you do not yet know, you can refer to the blog
“How Techies can select "relevant" Technical Usages of SAP enhancement packages”. In any case
you should have read the SAP enhancement packages Must Know Guide. Please note that
restrictions apply regarding the selection of technical usages: It is not allowed to have different
versions of technical usages in one system. That means that if you have already installed a
technical usage on some enhancement package release, you will always have to include this
technical usage and update it to the latest enhancement package release. Also note that if you have
If you are using an ABAP
only system and if you don’t
want to update connected
systems (like Portal or BI
systems) then choose the
product version “EHP4
FOR SAP ERP 6.0”
When you are using the
“Back” button, then
Maintenance Optimizer
might switch back to
“EHP3”. Make sure that
you have still selected
“EHP4” before proceeding.
Page 14
activated an industry solution in your system, you always have to include the corresponding
technical usage.
3. Choose the button Find Download Files.
After you choose the button Find Download Files, a stack calculation takes place on SAP Service
Marketplace. This may take a few moments.
3.3.5 Select OS/DB-Dependent Files
When the calculation is finished, SAP Solution Manager prompts you to select the kernel that you
want to use. Select the operating system, the database type, and whether you want to use a Unicode or
a non-Unicode kernel.
1. Select the correct OS/DB kernel parts. It is sufficient to only select the database-dependent
part. SAP Solution Manager Maintenance Optimizer then automatically selects the database-
independent part of the kernel for you.
If you are on IBM DB/2, please note the following SAP internal technical names for the
various IBM DB/2 products:
DB2 IBM DB/2 for z/OS
DB4 IBM DB/2 for i5/OS
DB6 IBM DB/2 UDB for Linux,
Unix, and Windows
2. Choose Continue.
Page 15
3.3.6 Select Files Without Stack Dependence
In the next step you are asked to confirm
the files that do not depend on the stack of
files to be installed. An update for the
transactions SPAM and SAINT is a
common example for that. In most cases
you can just confirm by choosing the button
Continue.
3.3.7 Check Files with Stack Dependence
In this step, SAP Solution Manager Maintenance Optimizer displays the result of the stack calculation
from SAP Service Marketplace.
SAP Note 1301879 helps you identifying required software components (the SAP Note is only valid
for Solution Manager SP16 to SP18 – part of Solution Manager SP19).
Be careful not to
unselect a software
component that is
necessary for SAP
enhancement package 4.
If you do unselect such a
required software
component, you will get
an inconsistent queue!
Page 16
3.3.8 Confirming the Selection
You can download the calculated software components either by means of SAP Solution Manager
Software Lifecycle Manager or via SAP Download Manager. If SAP Solution Manager Software
Lifecycle Manager is not completely set up, this type is not selectable.
1. Choose the download type
and choose the button
Select Download Type. On
the next screen, you get a
confirmation of your
choice. There, proceed by
choosing the button
Continue.
2. Before you are able to download the files, you need
to confirm the files in your download basket.
Choose the button Confirm Files in Download
Basket.
3. Instead of selecting every single line, you can also
just select the checkbox in the upper left corner to
select all entries in the list.
4. Then choose the button
Confirm Download to
confirm the download for
the selected files.
5. You can download the files
either using SAP Solution
Manager Lifecycle
Manager or you choose the
traditional way and use the
SAP Download Manager
to download the software
to your local computer.
Page 17
3.3.9 Download Directory
When the download is finished, you have to move the files to the server where you want to run the
SAP enhancement package installer (SAPehpi). However, you do not need to extract the files.
SAPehpi prompts you for the download directory (that is, the directory that contains all of the archives
that you have downloaded). When you provide SAPehpi with the download directory, SAPehpi starts
to extract the files and places the extracted files in the EPS-Inbox directory of the system. Make sure
you have enough free space in that file system (check the SAPehpi prerequisites further down in this
document for details on the space requirements).
SAPehpi also prompts you for the stack configuration file that has been created by SAP Solution
Manager Maintenance Optimizer. SAPehpi can automatically download the file from SAP Solution
Manager, but you can also copy the stack configuration file manually and specify the path to the file in
SAPehpi.
3.4 SAP Solution Manager Troubleshooting
This section lists some common and known problems that can occur with SAP Solution Manager’s
Maintenance Optimizer.
3.4.1 A Technical Usage cannot be selected
Issue: You would like to select a technical usage, but the checkbox is grayed out.
Reason: Move the cursor over the name of the technical usage in order to see which main instances
are required for that technical usage. If not all of the required technical usages are available, you
cannot select this technical usage. See the following example:
SAP Solution Manager
Maintenance Optimizer
cannot find some required
main instances on your
system. The main instances
that have an asterisk (*) are
not available because they are
not marked as relevant on the
system.
Solution: The solution is to go back to
transaction SMSY and mark the missing
main instances as being relevant. If you get
a warning, you might have to select the
column to the right, Also installed.
Page 18
3.4.2 Only one EHP release is allowed
Issue: You get the error message: “Only one
EHP release is allowed”
Reason: This problem is documented in SAP
Note 1139602.
If you get this error message, then you already
have installed another SAP enhancement
package on this system before (for example
SAP enhancement package 3 for SAP ERP 6.0).
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 SAP enhancement package 4 that are currently on SAP enhancement package 3. So in
the end, some software components would be on SAP enhancement package 3 while others would be
on SAP enhancement package 4. That way you would have several SAP enhancement package
versions in one system, which is a state that is not supported.
Solution: SAP Solution Manager Maintenance Optimizer requests you to select more technical usages
and proposes a list for you to choose from.
If you implement SAP Note 1287216,
then Maintenance Optimizer
automatically pre-selects the technical
usages that are already installed on
the system. In the example here, the technical usage Central Applications has been installed on a
previous version of SAP enhancement packages.
In rare cases you still get the error after accepting what SAP Solution Manager proposes. The reason
for this is that you updated software components without properly covering technical usages2.
3.4.3 Old product data in SAP Solution Manager
Make sure that you update the product data in
SAP Solution Manager. This is described in SAP
Note 1277035 which is referenced from the
collective SAP Note 1122966. If you do not
update the product data, you might get an error
message after the stack calculation. The message
text explains the problem in more detail.
2 If you select all proposed technical usages and still get the error, the following could be the reason: You have installed
software components of a previous SAP enhancement package without a clear mapping to technical usages, that is, you have
installed only parts of technical usages. Now not all technical usages are completely installed. For example, a technical usage consists of three software components but you have installed only two of them. In this case, Maintenance Optimizer does not preselect this technical usage for you. However, if you continue to the next screen, Maintenance Optimizer displays this error and shows a list of technical usages that are only partly installed on your system.
Page 19
There is another case however. SAP
Solution Manager Maintenance
Optimizer tells you to select the product
version “SAP enhancement package 4
for ERP 6.0 / NW7.01” but you cannot
find it in the list of the Target Stacks.
Here, the reason is outdated product
data as well.
In both cases, update your product data as described in SAP Note 1277035 and try again. If you have
already the current product data and still get this error message, the problem might also be the one
documented in SAP Note 1326123.
3.4.4 No Stack Configuration File is generated
The stack configuration of SAP Solution Manager Maintenance Optimizer is also written to a file. You
pass this file to the SAP enhancement package installer. The file is generated just before you are asked
to confirm the files of your download basket.
The stack definition file is written to the subfolder “in” of $(DIR_EPS_ROOT). You can use
transaction RZ11 to check the value of that variable.
The name of the stack configuration file is as in the following example:
SMSDXML_SID_20090112140052.532.xml
Issue: The stack configuration file is
not generated by SAP Solution Manager
Maintenance Optimizer.
Reason: Configuration of SAP Solution
Manager is missing.
Solution: If the file is not generated,
make sure that you have performed the
IMG activity
SOLMAN_MOPZ_SLM_CONF
(Configuration of Extended Functions). This is documented in SAP Note 1134872.
Additionally, make sure that you also have implemented the correction of SAP Note 1233954.
3.4.5 System is registered as SAP ECC 6.0, not as SAP ERP 6.0
Issue: You do not get the option Enhancement Package Installation in SAP Solution Manager
Maintenance Optimizer.
Reason: Your system is not registered as “SAP ERP 6.0” in SMSY.
Solution: As mentioned earlier in this document, the required product version is “SAP ERP 6.0”. The
selection item Enhancement Packages appears in the Maintenance Optimizer only if you registered
this product version.
Page 20
Selection in SAP Solution Manager Maintenance
Optimizer for an SAP ECC 6.0 system.
Selection in SAP Solution Manager Maintenance
Optimizer for an SAP ERP 6.0 system.
You can either re-register your system as an
“SAP ERP 6.0” system or you could just
configure “SAP ERP 6.0” as an additional
product version for your existing “SAP ECC
6.0” system.
Go to transaction SMSY and select your
system (select the system ID). Go to Header
Data and choose Installed Product Versions.
Add the product version “SAP ERP 6.0” by
choosing the Copy button.
Afterward, you still have to add your new SAP ERP 6.0 system to a Logical Component, which in turn
has to be added to a solution. On that solution you can create a Maintenance Transaction and then you
are offered the selection Enhancement Package Installation.
3.4.6 The latest Support Package Stack is not visible in Maintenance Optimizer
Issue: You cannot see the latest Support Package Stack in Maintenance Optimizer
Reason: Maintenance Optimizer retrieves the list of available Support Package Stacks from Service
Marketplace. However it caches that information and retrieves a new version only once a day.
Solution: You can delete the cached information. That way you force Maintenance Optimizer to
reread the list of Support Package Stacks from Service Marketplace. This issue is documented in SAP
Note 1165587.
Page 21
4 THE SAP ENHANCEMENT PACKAGE INSTALLER
4.1 How SAP Enhancement Packages are installed
The SAP enhancement package installer (SAPehpi) installs the enhancement packages in 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.
In comparison to the previously used method of implementing SAP enhancement packages with
transaction SAINT, SAP enhancement package installer offers further advantages:
The downtime is reduced drastically, the system can stay up and operate for a longer time.
The point-of-no-return is reached very late. Even when the shadow system has been built up
you can still reset the installation completely.
The old method of installing SAP enhancement packages via transaction SAINT is valid if the
following conditions are met:
SAP_APPL 604 is not in the installation queue
the software components of SAP NetWeaver are already on the release SAP Netweaver
enhancement package 1.
you provide a valid stack configuration file from SAP Solution Manager Maintenance
Optimizer to transaction SAINT.
This gives you the possibility to additionally install technical usages that do not include SAP_APPL
604 with transaction SAINT once the system does already have other technical usages installed on
version 604 or – as a special case – once the system has been installed from scratch with “SAP ERP
6.0 EHP4 Ready” media.
4.2 Prerequisites
Space requirements:
Prepare free space for the Installation directory “EHPI” of approximately 10-15 GB
(temporary requirement).
Prepare free space for the download directory for SAP enhancement package 4 and additional
Support Packages of approximately 10-30 GB (temporary requirement).
Prepare free space for the extraction directory (DIR_TRANS) for SAP enhancement package
4 and additional Support Packages of approximately 10-30 GB (temporary requirement).
Please note that this document does not intend to replace the installation guide for SAP
enhancement package 4 but just gives additional information especially on the relationship
between SAP Solution Manager and SAP enhancement package installer. For in-depth
information about the installation process, please refer to the “Installation Guide - SAP
Enhancement Package Installation”.
Page 22
Prepare free space for the shadow instance of approximately 100 GB. (Note that the size
required depends heavily on the customer situation – temporary requirement)
Prepare additional space for existing tablespaces (depends on available freespace in each
tablespace). We recommend setting the autoextend setting for tablespaces.
Increase the size of the Archive Log / Transaction log directory (for example: /oraarch) before
starting the EHP Installation.
4.3 Where to Get SAPehpi and Its Documentation
The central point for all installation related material is the page of SAP enhancement package
installation on SAP Service Marketplace. You can get there directly using the quick link
http://service.sap.com/ehp-inst. In the navigation tree on the left of the page, select “SAP enhancement
package 4 for SAP ERP 6.0”.
There, check the section “SAP Enhancement Package Installer (SAPehpi) Tool and Documentation”.
There are two links in the text, one for downloading the tool and the other one for the documentation.
4.3.1 Downloading SAPehpi
On SAP Service Marketplace http://service.sap.com/swdc go to
→ Support Packages and Patches
→ Entry by Application Group
→ Additional Components
→ Upgrade Tools
→ SAP EHP INSTALLER
→ SAP EHP INSTALLER 7.00
The version you download depends on the operating system and the database that you are using.
Also read SAP Note 1245473 for further, up-to-date information on SAP enhancement package
installer.
Make sure that you download the latest available tool version. The tool is updated regularly, we
recommend that you use the latest one.
4.3.2 Getting the Documentation for the SAPehpi Installation
On the documentation page that you access as described above, you will find the following types of
documentation:
SAP Enhancement Package Installation using SAPehpi
a) Installation on an ABAP only system
Attention: To avoid an “archiver stuck” or data overflow, we recommend a continuous
monitoring of the filling degree of the database directories.
Especially during the EHP Installation step Postprocessing, the phases “RUN_RSDBSCPY”
and “SHADOW_IMPORT_INC” can produce a high value of archive logs or transaction logs.
Page 23
If you have a 64-bit system with an ABAP stack only, use the documentation from
this section. The documentation depends on the operating system and the database you
are using.
b) Installation on an ABAP + Java system
If you have a 64-bit dual-stack system, use the documentation from this section. The
documentation depends on the operating system and the database you are using.
c) Installation on a Java only system
If you have a 64-bit Java only system, use the documentation from this section.
SAP Enhancement Package Installation on ABAP/Java Systems (using SAINT and
JSPM)
This documentation is only relevant for 32-bit systems. If you are on 64-bit, using
transaction SAINT is not supported! You have to use the SAPehpi tool to install SAP
enhancement package 4 for SAP ERP 6.0. On 32-bit systems you install the ABAP part
of the system with transaction SAINT and the Java part with JSPM.
Also, to install Java components of SAP enhancement package 4 on a NetWeaver 7.0
system (such as. Portal Content) you would use JSPM.
Troubleshooting and Administration
The Troubleshooting guide contains important information on how to correct errors in
different phases of the installation as well as general recommendations about topics like
downtime reduction or performance improvements.
The SAPehpi archive also contains technical documentation that you can find in the /EHPI directory
after extracting SAPehpi.
Troubleshooting and Administration
(see above)
Phase list of the installation
SAP provides a detailed phase list of the whole installation. This documentation is
located in the directory “EHPI/abap/htdoc”. It delivers background information of each
single installation step and refers to the error log and log files of each phase. This phase
list (“phaselist.xml”) requires the SAPupPhaselist.xsl for display, also located in the same
directory. Every technical consultant or Administrator working with the SAP
enhancement package installer should be familiar working with this phase list!
Page 24
4.4 Roadmap Steps of SAPehpi
SAPehpi contains the following Roadmap Steps:
Until you reach the Roadmap Step Preprocessing, no changes are made to your SAP ERP 6.0 system.
While in one of the Preparation Roadmap Steps, you can still reset the installation at any time.
During the Preparation Roadmap Steps, the shadow system is built up. Please note that at the
beginning of the Preprocessing Roadmap Step, the Transport Management System is locked (phase
REPACHK2). From then on you can not develop or transport anything in the system anymore.
During the Downtime Roadmap Step, the installation process exchanges the kernel and restarts the
system. It also moves and converts dictionary objects. In the end, the old system no longer exists and
the previous shadow instance has become the new system.
Note that if you have a dual-stack system, both stacks are updated at the same time by SAPehpi.
4.5 Installation Prerequisites
Please note that there exist several mandatory activities that you have to perform for a successful
installation.
Additionally it is a good idea to update SPAM to the latest release and to empty the $(DIR_TRANS)
directory.
If you are running a dual-stack system, check the stack configuration file and make sure that it also
contains Java components. If it does not, then check your SMSY configuration!
4.6 Startup of SAPehpi
After downloading the archive, you first have to extract it. Before starting SAPehpi, make sure you
have read SAP Note 1245473 which contains additional information on the installer tool.
Make especially sure that your profile directory is cleaned up. You should not still have old profiles in
the directory, even if they are renamed.
SAPehpi has to be run as the <sid>adm user. When you start the tool for the first time, you must
provide the JCE policy file (see SAP Note 1240081) as shown in the following table:
Attention: Please make sure that you have performed all activities that are listed in the
“Preparation” section of the respective installation guide before you start the SAPehpi program.
Page 25
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)
You only have to provide the JCE policy file the first time you start SAPehpi.
After you have started the server process, you can start the GUI process either from the command line
or via a web browser, as described in the installation guide.
4.7 SAPehpi Tips & Tricks
This section lists some possibilities that SAPehpi offers that you should be aware of.
4.7.1 Setting the Performance Parameters
During the configuration Roadmap
Step you are prompted to select one of
three performance models.
Your choice influences the number of
parallel processes that work during the
installation.
It is always recommended that you
choose the Manual selection of
parameters since that way you can best
adapt the number of processes to your
specific system.
For additional information, refer to the Troubleshooting and Administration Guide, chapter 3.2.3
Background Process and Tool Parameters (located in the SAPehpi Installation directory).
4.7.2 Including the Latest HR Support Packages in the Installation
HR Support Packages (software
components SAP_HR and EA_HR) are
released more often than complete SAP
enhancement package Support Package
stacks.
You can manually download and then
include those Support Packages in
SAPehpi. During the installation
process, in phase BIND_PATCH you are prompted if you want to add further Support Packages to the
target release.
Therefore you have to download the Support Packages manually from Service Marketplace. Extract
the Support Packages to the EPS/in directory, and in SAPehpi, answer “Yes” to the question: “Do you
Page 26
want to add further Support Packages to the target release”. SAPehpi scans the EPS/in directory and
should now propose that you add the extracted Support Packages to the installation queue.
4.7.3 Observer Mode and Alert Mechanism
It is possible to monitor the installation of SAP enhancement package 4 for SAP ERP 6.0.
You can also configure an alert mechanism that informs you if the installation is stopped and is
waiting for input. You can be alerted by e-mail or SMS, for example.
For more information, check out the blog entry at
https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/12870
4.8 SAPehpi Troubleshooting
This section lists some common and known problems with SAP enhancement package installer. Note
that there is a guide called Troubleshooting & Administration. See the chapter on the available
documentation for more details.
4.8.1 Dealing with Add-Ons
During the installation of SAP enhancement package 4, you are asked how to deal with add-ons. You
have two options:
You can keep the current version (but a vendor key is required for that). See SAP Note
1262124 for a list of vendor keys for add-ons that are released to be installed with SAP
enhancement package 4.
You can upgrade the add-on with a SAINT package.
Note that not all add-ons are already released for SAP enhancement package 4. Check SAP Note
1226284 for details.
Page 27
4.8.2 Retrieving the Stack from SAP Solution Manager by RFC
You do not need to transfer the stack configuration file manually from SAP Solution Manager to the
target system.
SAPehpi can get that file automatically by an RFC call.
If you cannot get this to work,
then log on to the target system
and check table BCOS_CUST
using transaction SM30, and
make sure that you see the name
of the RFC connection to SAP
Solution Manager. Maintain the
other columns as you can see in the screenshot here (the name of the RFC connection can differ in
your case, but make sure that the other columns have the exact same value as in the screenshot). Then
check this RFC connection via SM59.
Page 28
5 FURTHER INFORMATION
5.1 Relevant SAP Notes
5.1.1 For General Information on SAP Enhancement Package 4
SAP Note 1165438
SAP Note 1224284
Enhancement package 4 for SAP ERP: Required SWC
ES Bundles - Required Technical Usages and BFs
SAP Note 1165067 Release Info SAP Enhancement Package 4 for SAP ERP 6.0
SAP Note 1064635 SAP ERP Enhancement Packages: SP Stacks Release Info Note
SAP Note 1165437 Enhancement package 4 for SAP ERP: Required support packages
SAP Note 1160106 Enhancement package 4 for SAP ERP: Installing JAVA
SAP Note 1326576 SAP NetWeaver Systems Containing SAP ERP Software Components
SAP Note 1226284 SAP Enhancement Package 4 for SAP ERP 6.0: Compatible Add-ons
5.1.2 For SAP Solution Manager
SAP Note 1122966 Maintenance Optimizer: Notes for Enhancement Packages
SAP Note 1287216 Maintenance Optimizer: pre-select technical usages
SAP Note 1139602 Several enhancement package releases on one system
SAP Note 1134872
SAP Note 1233954
Maintenance Optimizer: FAQ for Stack Delta Files
Maintenance Optimizer: No XML Generated in EPS Inbox
SAP Note 1172948 SAP Solution Manager - Basic functions
5.1.3 For SAP Enhancement Package Installer
SAP Note 1143022 Installation of Enhancement Package 4 on SAP ERP 6.0 (ABAP)
SAP Note 1245473 Add. Info. - SAP Enhancement Package Installer (7.10/2)
SAP Note 1262124 Vendor Keys for Add-ons released with Enhancement Packages
SAP Note 1156968 Add. info. on upgrading to EHP 4 for SAP ERP 6.0 ABAP
SAP Note 1066110 ERP Enhancement Package: Installing the SAP Library
SAP Note 1256600 Using transaction SAINT to install SAP ERP 6.0 EHP4
SAP Note 1240081 "Java Cryptography Extension Jurisdiction Policy" files
Page 29
5.2 Relevant SAP Documentation
The SAP enhancement packages Must Know Guide
On SAP Service Marketplace http://service.sap.com/ehp-inst go to
→ SAP enhancement package 4 for SAP ERP 6.0 (in the navigation tree to the left)
→ Must Know Guide - SAP enhancement packages for SAP ERP 6.0
The SAP enhancement package 4 Master Guide
On SAP Service Marketplace http://service.sap.com/ehp-inst go to
→ SAP enhancement package 4 for SAP ERP 6.0 (in the navigation tree to the left)
→ Master Guide - SAP enhancement package 4 for SAP ERP 6.0
The SAP enhancement packages Lifecycle presentation
On SAP Service Marketplace http://service.sap.com/erp-ehp go to
→ Media Library – SAP enhancement packages (in the navigation tree to the left)
→ Enhancement Packages: General
→ Lifecycle of an Enhancement Package
The SAP enhancement packages Technology Facts presentation
On SAP Service Marketplace http://service.sap.com/erp-ehp go to
→ Media Library – SAP enhancement packages (in the navigation tree to the left)
→ Enhancement Packages: Technical
→ SAP Enhancement Packages Technology Facts IT
5.3 SAP Support
If none of the measures described in the documentation solves your problem then please open a
customer message describing your problem.
To enable SAP Support to help you as quickly and efficiently as possible, please follow the procedure
given here.
Procedure
To create the customer message, please go to SAP Support Portal (http://service.sap.com/support) and
assign your customer message to the correct component. Here is a list of the most common
components related to SAP enhancement packages:
Page 30
SV-SMG-SYS – Solution Manager System Landscape
SV-SMG-MAI – Solution Manager Maintenance Optimizer
BC-EHP-INS-TLA – SAP enhancement package installer tools for ABAP
BC-EHP-INS-TLJ – SAP enhancement package installer tools for Java
Please answer the following questions and put these answers in your customer message:
1. For which SAP component do you want to install an enhancement package (i.e. which
Technical Usages have you selected)?
2. What is the release of your SAP system? (e.g. Enhancement package 3 for SAP ERP 6.0)
3. Which operating system type and version are you using? Which database are you using?
4. In which installation program phase does the error occur? This information is listed at the end
of the SAPehpiConsole.log file located in the installation directory “EHPI/abap/log”.
In general, SAP Support can find the cause of the issue more quickly if you set up an online
connection to the SAP system. If you are certain that the problem is not an installation-specific one but
a product-specific one, then please assign your message to the appropriate product-specific
component.
5.4 Feedback
SAP is interested in improving its documentation and welcomes your comments and suggestions. To
share your comments, you can send feedback directly to [email protected]. Please provide the
document title in your e-Mail.
5.5 Disclaimer
This documentation is not subject to your license agreement or any other agreement with SAP. SAP
has no 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.
