Академический Документы
Профессиональный Документы
Культура Документы
Version 1.03
2009-06-26
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
5 Further Information......................................................................................................... 29
5.1 Relevant SAP Notes .............................................................................................................. 29
5.2 Relevant SAP Documentation.............................................................................................. 30
5.3 EHP Technology Backoffice ................................................................................................ 30
5.4 Feedback ................................................................................................................................ 31
Page 2
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.
Page 3
1.3 The Big Picture – Step by Step
With SAP enhancement package 4, the installation steps have changed from previous SAP
enhancement packages. See below for the interaction of all involved parties.
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).
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 The SAP Solution Manager Maintenance Optimizer is a functionality that guides
Optimizer 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 4
Stack The stack configuration file is created by the Maintenance Optimizer and is
configuration system-specific. Depending on the software components that are installed in a
file system, Maintenance Optimizer calculates the required software components that
have to be installed additionally in order to reach a certain target configuration.
Target The SAP ERP 6.0 system on which you are going to install SAP enhancement
system 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 5
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 system 1 .
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
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 Maintenance Optimizer
of 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: You should try to be as
If you have already activated an Industry Solution or plan to do so conservative as possible
in the near future, then please select only the technical usage of that with regards to the
Industry Solution. If you have not yet activated an Industry number of technical
usages that you select.
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.
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).
1
Note that switchable business functions only exist for ABAP systems. In Java all installed software is
automatically switched on.
Page 6
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.
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.
Page 7
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).
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.
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.
Page 8
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.
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).
Page 9
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...”.
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:
Page 10
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.
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.
Page 11
1. In the left frame switch to Operations.
2. Then, choose the tab Change Management.
3. Choose Maintenance Optimizer.
Therefore, select all the systems for which you want to generate the
stack definition.
Page 12
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.
You can choose one of the following two product versions for SAP enhancement package 4:
Page 13
• 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.
SAP recommends to always download 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 usages and update it to the latest enhancement package release. Also note that if you
have activated an industry solution in your system, you always have to include the corresponding
technical usage.
After you choose the button Find Download Files, a stack calculation takes place on SAP Service
Marketplace. This may take a few moments.
Page 14
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
Check Files with Stack Dependence
In this step, SAP Solution Manager Maintenance Optimizer displays the result of the stack calculation
from SAP Service Marketplace.
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!
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).
Page 16
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.
Page 17
3.3.8 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.
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 usages 2 .
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.
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.
Page 20
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.
Selection in SAP Solution Manager Maintenance Selection in SAP Solution Manager Maintenance
Optimizer for an SAP ECC 6.0 system. Optimizer for an SAP ERP 6.0 system.
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:
• 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.
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”.
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).
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.
Page 23
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:
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.
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.
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!
Page 25
Startup procedure (also check SAP Note 1245473)
Page 26
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
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.
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
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.
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.
Page 28
5 FURTHER INFORMATION
5.1 Relevant SAP Notes
SAP Note 1165438 Enhancement package 4 for SAP ERP: Required SWC
SAP Note 1224284 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
SAP Note 1134872 Maintenance Optimizer: FAQ for Stack Delta Files
SAP Note 1233954 Maintenance Optimizer: No XML Generated in EPS Inbox
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
Page 29
5.2 Relevant SAP Documentation
If none of the measures described in the documentation solves your problem or if you have questions
regarding EHP technology in general, feel free to contact EHP Technology Backoffice. The
Backoffice is led by Christian Oehler (christian.oehler@sap.com) and you can reach it by sending an
e-Mail to EHP-TECH@sap.com.
To enable us to help you as quickly and efficiently as possible, please follow the procedure given here.
Procedure
If you encounter problems that are specific to the enhancement package installation, please open a
customer message in SAP Support Portal (http://service.sap.com/support) and assign it 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
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. SAP ERP 6.0 with SAP enhancement package
3)
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.
Note
We 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 christian.oehler@sap.com. Please provide the
document title in your e-Mail.
Page 31