ecc6.0 ehp5 inst

How to Install SAP Enhancement Package 5 for SAP ERP 6.0A Practical Guide

Target Audience ■ System administrators ■ Technology consultants

PUBLICDocument version: 1.0 – 2010-12-16

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.

You can find the latest version at the following location: http://service.sap.com/erp-inst

SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP enhancement package 5 for SAP ERP

6.0. .

The following table provides an overview of the most important document changes.

Version Date Description

1.0 2010-12-16 First version.

2/44 PUBLIC 2010-12-16

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

Table of Contents

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.2 The Overall Process at a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.3 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.4 Reading Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2 Quick Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.1 Checking Prerequisites for the Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.2 Installation in an SAP System Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.1 Preparing SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.1.1 SAP Solution Manager Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.1.2 Installation of Landscape Verification 1.0 for SAP Solution

Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.1.3 Configuration of the Maintenance Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.1.4 Maintaining System Landscape Information . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.2 Selecting and Downloading Software Packages . . . . . . . . . . . . . . . . . . . . . . . . 22

4.3 Evaluating Business Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

5.1 Additional Application-Specific Information . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5.1.1 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5.1.1.1 SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5.1.1.2 Free Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5.1.1.3 SAP ECC: Backing Up Wage Types in HR (T512W) (HR

Customers) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5.1.2 Performing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5.1.2.1 Vendor Keys for Add-Ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5.1.3 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2010-12-16 PUBLIC 3/44

5.1.3.1 Updating Dialog Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 6 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 7 Update of Further Software Units in your System Landscape . . . . . . . . . 35

7.1 Importing Process Integration Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

7.2 Updating the BI Content Add-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

7.3 Updating Portal Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

A.1 List of Referenced Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

A.2 List of Referenced SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter B Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4/44 PUBLIC 2010-12-16

1 Getting Started

1.1 About this Document

This document guides you through the implementation of SAP enhancement package 5 for SAP ERP

6.0. It contains all required steps with references to detailed documentation or SAP Notes, where

necessary.

Integration

This document assumes that you are familiar with the contents of the Master Guide for SAP Enhancement

Package 5 for SAP ERP 6.0 and the document SAP Business Suite 7 i2010 – Landscape Implementation – Technical

Planning Guide. In particular, the business requirements have been mapped to the technical usages and

you are aware which technical usages of enhancement package 5 are to be installed in the system you

want to update.

The documents are available at http://service.sap.com/erp-inst SAP ERP 6.0 SAP enhancement

packages for SAP ERP 6.0 SAP enhancement package 5 for SAP ERP 6.0 .

Constraints

Install enhancement packages for SAP NetWeaver 7.0 ABAP systems only in standalone SAP NetWeaver

systems.

For existing SAP Business Suite ABAP systems (for example, SAP ERP 6.0) that are based on SAP

NetWeaver 7.0, enhancement packages for SAP NetWeaver must not be installed separately for the

following reasons:

■ For the SAP Business Suite applications, the relevant parts of the SAP NetWeaver enhancement

packages are automatically included in the download stack for the Business Suite enhancement

package. You have to install the complete stack, consisting of the enhancement package for SAP

NetWeaver, the enhancement package for the SAP Business Suite application and the required

Support Package Stacks in a single installation step.

■ The installation of the SAP NetWeaver enhancement package is part of the upgrade procedure for

SAP Business Suite applications that are based on a specific enhancement package for SAP

NetWeaver. For example, when you upgrade from SAP SRM 6.0 to SAP SRM 7.0 including EHP1,

the underlying SAP NetWeaver 7.0 is automatically updated with enhancement package 2 for SAP

NetWeaver 7.0.

Installing enhancement packages for SAP NetWeaver in an SAP Business Suite ABAP system without

installing the enhancement package for the SAP Business Suite application will result in malfunctioning

of the installation procedure and/or the final system state.

1 Getting Started

1.1 About this Document

2010-12-16 PUBLIC 5/44

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

Regarding Java systems, it depends on the landscape pattern (hub or sidecar) whether you can update

the SAP NetWeaver Java system independently of the application on top of it. A hub system can be

updated independently of the application, whereas a sidecar system (as well as the Java stack of a dual

stack system) can only be updated along with the application.

1.2 The Overall Process at a Glance

The following graphic shows the main steps that are involved in the installation process and which are

explained below:

Figure 1: Overview of Main Steps of the Installation Process

1. To install an enhancement package, you need an SAP Solution Manager 7.0 system with the latest

available Support Package stack level and the SAP Solution Manager Maintenance Optimizer needs

to be configured.

2. You register your systems in SLD and transfer the system data to SAP Solution Manager.

3. Optional: You run the landscape verification 1.0 for SAP Solution Manager (add-on to SAP Solution

Manager) which checks the system data that is maintained in the Solution Manager System

Landscape (transaction SMSY).

4. You check the system data using transaction SMSY and, if necessary, update them.

5. As soon as the system data in SMSY is maintained correctly, you start a new maintenance

transaction in SAP Solution Manager.

1 Getting Started

1.2 The Overall Process at a Glance

6/44 PUBLIC 2010-12-16

6. As part of the maintenance transaction, you have to select the required technical usages as well as

the target Support Package level.

7. This selection is used by the Maintenance Optimizer to generate a stack configuration file and to

calculate the software components as well as the Support Packages.

8. You download the files using the Download Manager.

9. You provide all downloaded files to the SAP Enhancement Package Installer.

10. The SAP Enhancement Package Installer updates the system with the enhancement package files

and Support Packages.

1.3 Glossary

Here is a short overview of some technical terms used in this document:

Term Explanation

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.

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 system on which you are going to install the enhancement package.

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.

Product Used in SAP solutions. Generally speaking, a product fulfills business requirements.

Product Version A concrete release of a given product. It bundles together software component versions made available at the same time for implementing a well defined scope of functionality.

Technical Usage A grouping that is used to bundle together dependent product instances as part of a product.

Product Instance A part of a product version and the smallest element for designing system landscapes. It groups technically dependent software component versions which have to be installed and operated on a single technical system.

Software Component (SC) Reusable component of the product.

1 Getting Started

1.3 Glossary

2010-12-16 PUBLIC 7/44

Term Explanation

Technical System The runtime environment in which SAP applications are executed. It is identified with a system identifier (SID). It must be assigned manually to a product system.

Product System A group of technical systems on which one product version is installed.

Logical Component A group of technical systems on which the same product instance has been installed. The technical systems have different roles, for example, development, test or production system.

Landscape Patterns Describe how systems are used in a landscape.Landscape pattern “hub”: Technical system used by two or more product systems.Landscape pattern “sidecar”: Technical system that is used by a single product system and is not running on the ABAP stack.

1.4 Reading Sequence

In the different phases of your enhancement package implementation project, different documents

and information sources support you with information. We recommend you read the documents in

the following order, which leads you from overview documentation to detailed documentation.

Figure 2: Reading Sequence

Document(s) Content /Target

Master Guide (Including Upgrade Information) – SAP ERP 6.0 Including SAP Enhancement Package 5

Provides information about the enhancement package concept, business functions, and how they are related to technical usages, and the implementation procedure at a glance.You are directed to information sources that enable you to define the business functions to be implemented.

1 Getting Started


8/44 PUBLIC 2010-12-16

Document(s) Content /TargetAs a result, you know which business functions you want to implement and activate in your system. You have mapped the business functions to technical usages.

SAP Business Suite 7 i2010 – Landscape Implementation – Technical Planning Guide

Amongst other topics, you find information about the landscape patterns: hub system, local sidecar system and embedded deployment.This information is important for the correct modelling of your system landscape in SAP Solution Manager.

How to Install SAP Enhancement Package 5 for SAP ERP 6.0(this guide)

You are guided through the implementation process with special focus on the SAP Solution Manager setup and use for your enhancement package implementation.Provides product-specific information that is not covered by generic documentation and you are directed to separate guides with detailed information where necessary.

Individual documents and SAP Notes as referenced in this How-to Guide, for example, theInstallation Guide – SAP Enhancement Package Installation Using SAP Enhancement Package Installer 7.0

You find detailed procedures for the individual steps required for the enhancement package implementation in these guides.

1 Getting Started


2010-12-16 PUBLIC 9/44

This page is left blank for documents that are printed on both sides.

2 Quick Guide

This section contains a checklist with all the actions you need to perform. For more information, follow

the links to the descriptions of the actions. Read this list completely before you begin with the activities

to get a thorough understanding of the process and to plan your schedule and resources accordingly.

Checklist

☐ 1. You check the add-on compatibility and availability of Support Packages [page 13] as described in SAP

Notes 1318299, 1064635, and 1440337.

☐ 2. You plan the implementation of the enhancement package in your system landscape [page 13]. You provide

additional temporary systems for dual maintenance and educate developers about the impact

of the enhancement package installation on the development activities.

☐ 3. You update SAP Solution Manager [page 17] to at least SAP Solution Manager 7.0 Support Package

Stack 23.

☐ 4. You run transaction SOLMAN_SETUP after the SAP Solution Manager update.

☐ 5. Optional: You install the landscape verification 1.0 add-on [page 17] on top of your SAP Solution

Manager system.

☐ 6. You configure the Maintenance Optimizer [page 18].

☐ 7. You check the composite SAP Note 1436297 for corrections for the maintenance optimizer and

apply the required SAP Notes.

☐ 8. You Maintain your system landscape data in SAP Solution Manager [page 18]:

1. Make your systems known to SAP Solution Manager using SLD.

2. Optional: Run the landscape verification 1.0 for SAP Solution Manager to check the entries

in transaction SMSY.

3. Correct the SMSY entries, if necessary.

☐ 9. You create a new maintenance transaction [page 22] in SAP Solution Manager and download the

enhancement package and Support Package stack files and the stack configuration file.

☐ 10. You test the enhancement package installation and the business functions [page 26] in an evaluation system

which is a copy of the production system.

☐ 11. You prepare your system [page 29] for the enhancement package installation as described in this

guide and in the Installation Guide — SAP Enhancement Package Installation Using SAP Enhancement Package

Installer.

This includes preparation activities for the hardware (for example, checking disk space

requirements), activities for the database (for example, preparing free space, updating statistics,

2 Quick Guide

2010-12-16 PUBLIC 11/44

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1318299&_NLANG=en&_NVERS=0




planning backups) and for the SAP system itself (for example, preparing the modification

adjustment, checking the number of background processes).

☐ 12. You perform the enhancement package installation with the latest available SAP Enhancement

Package Installer [page 29].

☐ 13. Perform follow-up activities [page 29] as described in this guide and in the Installation Guide — SAP

Enhancement Package Installation Using SAP Enhancement Package Installer

☐ 14. You configure the newly introduced functions [page 33] using SAP Solution Manager.

☐ 15. You update further software units [page 35], if necessary: SAP NetWeaver Process Integration content,

BI Content Add-On, and SAP NetWeaver Portal content.

☐ 16. You perform regression tests.

2 Quick Guide

12/44 PUBLIC 2010-12-16

3 Planning

3.1 Checking Prerequisites for the Update

Procedure

Checking the Add-On Compatibility

If you have add-ons installed in your system, check if the add-ons are released for enhancement package

5 for SAP ERP 6.0. For information about the add-on compatibility, see SAP Note 1318299.

Checking the Required Target Support Package Stack

When you update your SAP system with an enhancement package, you have to include a minimum

Support Package stack for the target release into the update. If your source release system has the most

recent Support Package Stack level, make sure that this equivalent Support Package stack for the target

release is already released.

Proceed as follows:

1. Check SAP Notes 1064635 and 1440337 for the required Support Package stacks.

2. Check the Support Package stack schedule on SAP Service Marketplace at http://

service.sap.com/sp-stacks SP Stack Schedule for release date of the Support Package Stack you

require.

NOTE

Do not apply the latest Support Package stack to the system that you want to update shortly

before the enhancement package installation.

3.2 Installation in an SAP System Group

If you have an SAP system group consisting, for example, of a production system, a quality assurance

system, and a development system, you must consider the entire system group regarding the sequence

of the enhancement package installation.

In addition, the enhancement package installation influences the development activities, for example,

dual maintenance might be temporarily necessary to ensure that your production system is supported

with emergency corrections.

Procedure

Sequence of Enhancement Package Installations

Install the enhancement packages in your systems in the same sequence in which you transport your

modifications. Install the same software packages on each system.

3 Planning

3.1 Checking Prerequisites for the Update

2010-12-16 PUBLIC 13/44



http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1440337%20&_NLANG=en&_NVERS=0

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

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

If your system group consists of three SAP systems and includes a quality assurance system that has

been set up between the development and production system, work in the following order:

1. Development system

2. Quality assurance system

3. Production system

RECOMMENDATION

We strongly recommend that you perform transports only between systems of the same release

or enhancement package level, and where the same business functions are activated. If you do

not follow this recommendation, you do so at your own risk regarding potential problems.

If you have made modifications to SAP objects that you want to retain, you must proceed in the above

sequence. The version management functions of the SAP system record all the changes you make only

in the system in which you made the modifications (the development system). Only this SAP system

offers you optimal support when you adjust modifications.

Changes made in the development system after the installation of enhancement packages can be

transported automatically to your other SAP systems. If you use this procedure, you no longer need

to perform time-consuming adjustments in the production system.

CAUTION

If you have modified SAP objects, make sure that you keep your development system. Do not

copy your production system to your development system for test purposes.

Impact on Development

At a certain point in time during the enhancement package installation, the development environment

of the system that is updated is locked. Consider this development freeze in your project plan and

inform your developers about it.

To avoid the development system being unavailable during the installation, we recommend that you

add a temporary copy of your development system to your system landscape. This temporary

development system can supply your production system with emergency corrections or support a

phased development go-live after you have updated the original development system with the

enhancement package. You then have to make any corrections in the original development system as

well as in the temporary development system. Make sure that your developers are notified about the

dual maintenance.

3 Planning


14/44 PUBLIC 2010-12-16

Figure 3: Dual Maintenance

3 Planning


2010-12-16 PUBLIC 15/44

4 Preparation

4.1 Preparing SAP Solution Manager

The following sections explain how you have to prepare SAP Solution Manager and the Maintenance

Optimizer.

4.1.1 SAP Solution Manager Update

You require at least SAP Solution Manager 7.0 EHP1 Support Package Stack 23 and the implementation

content ST-ICO 150_700 SP 25. Note that ST-ICO 150_700 SP 25 is not included in the Support Package

Stack 23, that is, you have to download it separately.

We recommend that you always update your SAP Solution Manager to the latest Support Package

Stack.

Make sure that you run the guided procedure SOLMAN_SETUP after every installation or update of

SAP Solution Manager and that it completes successfully.

Related Documents Available at...

Upgrade Guide – SAP Solution Manager 7.0 incl. Enhancement Package 1Describes the upgrade from source releases SAP Solution Manager 3.1 and 3.2. You can include the installation of the required Support Package stack in the upgrade procedure.

http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP1 -

Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0Describes the update from source releases SAP Solution Manager 7.0. You can include the installation of the required Support Package stack in the update procedure.

http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP1 -

Solution Operations Guide – SAP Solution Manager 7.0 EHP1, section Software Change ManagementDescribes the actions required after the update to SAP Solution Manager 7.0 EHP1.

http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP1

4.1.2 Installation of Landscape Verification 1.0 for SAP Solution Manager

Landscape verification 1.0 is an add-on to your SAP Solution Manager system. It supports you in

maintaining your system landscape data. The use of this tool is optional.

4 Preparation


2010-12-16 PUBLIC 17/44

http://service.sap.com/instguides



For information about the installation, see SAP Note 1468605.

4.1.3 Configuration of the Maintenance Optimizer

If you have not already done so, configure the Maintenance Optimizer. For a list of configuration tasks,

see the Maintenance Optimizer Configuration Guide.

In any case, check SAP Note 1436297 Maintenance Optimizer: Notes for Enhancement Packages whether it contains

any corrections for the SAP Solution Manager 7.0 Support Package level you are using.


Maintenance Optimizer Configuration Guide http://service.sap.com/mopz (link at the bottom of the page)

SAP Note 1436297 http://service.sap.com/notes

4.1.4 Maintaining System Landscape Information

The Maintenance Optimizer relies upon up-to-date information about your system landscape.

Therefore, it is crucial that this data is correctly maintained in SAP Solution Manager’s system landscape

(transaction SMSY). If you have already maintained the system landscape data, check carefully if this

data is correct.

Proceed in the following order:

1. If you have not already done so, capture the system data using the System Landscape Directory

(SLD).

2. Optional: Run the landscape verification 1.0 to check the system landscape data.

3. Maintain the system data in SAP Solution Manager.

Procedure

Capturing System Data Using SLD

1. Register all systems that you want to update in your central SLD. In case of a dual stack system,

you have to register both the ABAP stack and the Java stack.

Depending on your applications, this can either be the SLD of your SAP Solution Manager system

(if there are no dependencies of productive runtime systems), or you have separate SLD systems

for productive and non-productive use (default recommendation).

If you use a central runtime SLD, distribute the data of all technical systems that are registered in

the central SLD, from the central SLD to the development SLDs and to the local SLD in SAP Solution

Manager.

For more information about the SLD topology options and synchronization, see the Planning Guide

– System Landscape Directory available at http://sdn.sap.com/irj/sdn/nw-sld.

To register Java systems, you use the Visual Administrator. To register the ABAP system you use

transaction RZ70.

4 Preparation


18/44 PUBLIC 2010-12-16



http://service.sap.com/mopz


http://service.sap.com/notes

http://sdn.sap.com/irj/sdn/nw-sld

For more information, see http://help.sap.com/nw70 SAP NetWeaver Library <Language> SAP

NetWeaver by Key Capability Solution Lifecycle Management by Key Capability Software Life Cycle Management

System Landscape Directory Configuring Systems to Connect to SLD

If the registration was successful, both the ABAP system and the Java system appear in the SLD

under Technical Systems.

2. To transfer the data from the SLD to the SAP Solution Manager system landscape, schedule SLD

update jobs in the SAP Solution Manager transaction SMSY_SETUP.

For more information, see the SAP Solution Manager Library at http://help.sap.com SAP

Solution Manager 7.0 <Language> Basic Settings Solution Manager System Landscape Set Up Automatic Data

Capture for System Landscape .

Figure 4: Capturing System Data Using SLD

Running the Landscape Verification 1.0

Running the landscape verification 1.0 is an optional step. This tool checks how your systems are

maintained in the SAP Solution Manager system. If it detects any inconsistencies, you are prompted to

correct existing entries or enter missing data. The tool provides you with information how to maintain

the data.

As of SP01 for landscape verification 1.0 for SAP Solution Manager, two additional wizards are available,

which enable you to correct the detected problems directly. These wizards enable you to correct the

description of technical systems and product systems in which problems were detected. The wizards

also include help for making the correct settings.

To start the landscape verification, call transaction LVSM in SAP Solution Manager.

For more information about the landscape verification, choose the Help link from within the

application.

4 Preparation


2010-12-16 PUBLIC 19/44

http://help.sap.com/nw70

http://help.sap.com

Figure 5: Landscape Verification 1.0

Maintaining System Data

When your product systems are known in SAP Solution Manager, you have to check and maintain the

system data, add your system to a logical component and to a solution.

1. In transaction SMSY, choose Landscape Components Product System <System> .

2. Check whether the product version is correct. The product version is displayed in the right pane

below the name of your system.

3. Choose the Selection of Product Instances tab and check that everything that is installed in your system

is flagged as Relevant. Make sure that no instance is marked as relevant that is not installed in your

system, as this would lead to the installation of unwanted software components in your system.

NOTE

You can only select one ABAP instance as relevant. You have to flag further ABAP instances

as Also Installed in Relevant ABAP Product Instance.

For more information about selecting the instances and required settings, see SAP Note 1344564 -

Maintenance Optimizer: Check system landscape and SAP Note 1429764 -Automatic assignment of products in

SMSY.

4. Java–based systems connected to SAP Business Suite Application ABAP Systems: Checking the

Landscape Patterns

Make sure that you have correctly modeled the connected Java systems as hub systems or sidecar

systems. A sidecar system is a system that is used by only one SAP Business Suite product (for example

an SAP Netweaver 7.0 Portal or Business Intelligence system used exclusively by one SAP ERP 6.0

system). In contrast, a hub system is used by several SAP Business Suite products. This has

implications for the Maintenance Optimizer’s update strategy for your landscape: A sidecar system

only receives updates along with its associated SAP Business Suite system, whereas you can update

4 Preparation


20/44 PUBLIC 2010-12-16



a hub system independently. However, the SAP Business suite software that is installed on the hub

system (for example, SAP XSS on an SAP NetWeaver Portal) is updated along with its associated

SAP Business Suite system.

For more information, see the document SAP Business Suite 7 i2010 Landscape Implementation – Technical

Planning Guide.

To check the landscape pattern of the connected Java systems, proceed as follows:

1. Log on to SAP Solution Manager and call transaction SMSY.

2. Choose Landscape Components Product Systems <System>

3. On the Product Instance Selection tab, double-click on the relevant Java product instances and

choose the Other Attributes tab.

4. Select the appropriate landscape pattern.

5. Creating the logical component

1. In transaction SMSY, choose System Groups and Logical Components

2. In the context menu of Logical Components choose Create New Logical Component.

3. Enter your system data.

The name of your logical component must start with “Z...”.

6. 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).

RECOMMENDATION

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.

7. Optional: Adding the product system to a solution

It is no longer mandatory to create a solution and to add your product system to a solution.

However, if you already have a solution, then add your product system to it. When you later create

a maintenance transaction, you can select this solution and thus restrict the number of product

systems displayed.

1. Call transaction solution_manager and create a solution, if it does not yet exist.

2. Choose Solution Landscape and Solution Landscape Maintenance.

3. Add your SAP system to the solution as follows:

1. Change to edit mode.

2. Place the cursor on a new line in the Logical Component column.

3. Use the input help to select your system from the list (product, logical component).

4. Choose Complete System Data Replication.

5. Save your selection.

4 Preparation


2010-12-16 PUBLIC 21/44

4.2 Selecting and Downloading Software Packages

Create a maintenance transaction in SAP Solution Manager Maintenance Optimizer to calculate the

required software packages and the stack configuration file. The complete stack consists of Support

Packages of the start release, SAP enhancement packages, and Support Packages for the enhancement

packages.

Procedure

NOTE

The screenshots below are an example taken from a maintenance transaction for enhancement

package 5 for SAP ERP 6.0. They illustrate the general appearance of the Maintenance Optimizer

which is the same for all applications.

1. In SAP Solution Manager, start transaction solman_workcenter and choose Change

Management

2. Choose New Maintenance Transaction.

Figure 6: Creating a New Maintenance Transaction

3. If you have maintained a solution, choose the solution for which you want to download the

software packages.

4. Select the system(s) that you want to include in the maintenance transaction.

The product version dropdown box displays all product versions of the selected solution and,

depending on the product version, the systems are displayed. You can run a maintenance

transaction for one or multiple systems of one product version of exactly one solution.

RECOMMENDATION

Create a single stack configuration file for all systems of a track (development system, quality

assurance system, and production system). In addition, run your Maintenance Optimizer

transactions for every affected system at the same point in time, ideally also in the same

maintenance transaction. That way you make sure that all systems are updated with exactly

the same software.

4 Preparation


22/44 PUBLIC 2010-12-16

If you run the same Maintenance Optimizer transaction at different points in time, the

Maintenance Optimizer might include slightly different software. This is due to the fact that

SAP changes Support Package stacks whenever a critical issue in the currently delivered

software arises.

5. ChooseCalculate Files Automatically as the file selection mode.

RECOMMENDATION

Check the Log tab regularly to see if any severe issues have occurred. In case you are unsure,

create a customer message and assign it to component SV-SMG-MAI (Maintenance

Optimizer).

In addition, the Systems tab provides valuable information about the systems to be updated.

6. Select the Enhancement Package Installation update option.

7. Select the target enhancement package version and target Support Package stack level.

As the selected Support Package Stack for the enhancement package is equivalent to a dedicated

Support Package Stack of the underlying product version, Maintenance Optimizer displays the

equivalent Support Package Stack of the underlying product version.

Figure 7: Selection of Target Enhancement Package and Support Package Stack

8. Select the technical usages.

A technical usage provides a set of business functions. Therefore, the decision which technical

usages should be installed derives from the business requirements. From a technical point of view,

a technical usage consists of product instances which in turn consist of software components.

For information about the mapping of business functions to technical usages to software

components, see SAP Note 1324838.

If you cannot select a technical usage, a required instance is either not installed in the system, or

you have not configured your system landscape correctly. To check the requirements, click on

the name of the technical usage.

EXAMPLE

If a technical usage includes software components that have to run on an SAP NetWeaver

Portal but this is not installed in your system, then you are unable to select this technical

usage.

Correct the system landscape configuration or install the missing instances as part of your

maintenance transaction (see next step).

4 Preparation


2010-12-16 PUBLIC 23/44


Figure 8: Selection of Technical Usages

9. Choose any additional Java instances that you want to install. If you choose additional Java

instances, you can choose from a broader selection of technical usages.

10. Check and confirm the target constellation for your system.

If you find out here that a connected SAP NetWeaver system (for example an SAP Netweaver Portal,

or an SAP Business Intelligence system) is supposed to be updated to a release that you did not

expect, check that you have correctly maintained the type of the system (hub or sidecar). This

information is also available on the “Systems” tab.

Figure 9: Confirm the Target Constellation

11. Select any add-ons that you want to install as part of this maintenance transaction.

Maintenance Optimizer offers you to include add-ons directly into your maintenance operation

so you can make use of the same downtime window instead of installing the add-ons separately

afterwards.

When you select an add-on, you can choose the system on which the add-on will be installed using

the Assign System link.

4 Preparation


24/44 PUBLIC 2010-12-16

Figure 10: Add-On Selection

12. Select the files that correspond to the combination of your operating system and database.

In addition, select the files for SAP IGS and SAP HOST AGENT.

If you run application servers on different operating systems, make sure that you also include their

kernels files. When you slide with the mouse pointer over the kernel files, a quick info text displays

for which system the kernel files have been calculated.

13. Select the stack-independent files and files for the add-on update or add-on installation.

In most cases, the stack-independent files include a SPAM/SAINT update for the target release.

If you have decided to install new add-ons, Maintenance Optimizer displays now the corresponding

files.

NOTE

The stack-independent files are not automatically included in the update of your system.

You have to include them manually during the Configuration roadmap step of the SAP

Enhancement Package Installer.

14. Decide about the stack-dependent files.

These files directly correspond to the technical usages that you have selected. You also see the

Support Packages for the basis release that Maintenance Optimizer calculated for those software

components you do not want to update with the enhancement package.

RECOMMENDATION

We recommend you keep the selection.

However, you can deselect any Support Package that you do not want to be applied to your system.

Components of an SP Stack that are not used for productive use do not need to be patched during

the implementation of the SP Stack, unless there is a technical or logical dependency to the used

components.

If Support Packages of a software component are grayed out and cannot be deselected, the

previously selected technical usages and the target support package level indirectly determine that

these Support Packages are required.

4 Preparation


2010-12-16 PUBLIC 25/44

NOTE

Do not deselect the files for the software components SAP_BS_FND and WEBCUIF as they

are required for the enhancement package.

The Add Java Patches pushbutton allows you to search for appropriate Java patches and add them to

the download basket. As these patches are not added to the stack configuration file, they are not

implemented during this maintenance transaction. Their implementation is a separate step

afterwards.

Figure 11: Selection of Stack-Dependent Files

15. To download the files, select whether you want to download them with the Download Basket or

with the Software Lifecycle Manager (only available if configured).

16. To access the stack configuration file, choose the Stack Files tab.

Use the XML file. The text file is only needed for an upgrade with source release SAP R/3 4.6C.

17. Download the files. We recommended starting the download shortly after you have run the

maintenance transaction.

4.3 Evaluating Business Functions

It is not possible to uninstall an enhancement package. Furthermore, you cannot revoke the activation

of most business functions and it is only possible to transport complete business function switch settings

across your system landscape. For these reasons, we recommend testing the business functions

thoroughly in a dedicated evaluation system (not the development system), until you are sure that

you definitely want to use them. It makes sense to use a copy of your production system as evaluation

system.

The following figure shows the evaluation of business functions in your system landscape:

4 Preparation


26/44 PUBLIC 2010-12-16

Figure 12: Test of Business Functions in an Evaluation System

4 Preparation


2010-12-16 PUBLIC 27/44

5 Installation

Perform the enhancement package installation using the SAP Enhancement Package Installer as

described in the Installation Guide – SAP Enhancement Package Installation – Using SAP Enhancement Package Installer

(SAPehpi). This installation guide is product-independent: it describes the handling of the installation

tool as well as preparation and follow-up activities that are generally necessary, regardless of the

enhancement package you want to install.

In addition to this guide, note the application-specific information for installing enhancement package

5 for SAP ERP 6.0 below.

CAUTION

The SAP Enhancement Package Installation Guide describes preparation activities that you have to perform

before you can start the SAP Enhancement Package Installer. Make sure you start with these

preparations in good time. You can also consider performing these preparations in parallel to the

preparation of SAP Solution Manager and download of the enhancement package stack.

SAP Enhancement Package Installer

The SAP Enhancement Package Installer (SAPehpi) installs 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.

To install enhancement packages in Java systems, the SAP Enhancement Package Installer uses a

deployment-based procedure.

SAPehpi comprises eight roadmap steps: Initialization, Extraction, Configuration, Checks,

Preprocessing, Downtime, Postprocessing, Finalization.

Figure 13: Roadmap Steps of SAP Enhancement Package Installer

Until the roadmap step Preprocessing, no changes are made to your original system. While in one of the

first five roadmap steps, you can still reset the installation at any time. The shadow system is built up

in roadmap step Preprocessing.

Note that at the beginning of the Preprocessing roadmap step, the Transport Management System is

locked. From then on you cannot develop and transport anything in the system anymore.

5 Installation

2010-12-16 PUBLIC 29/44

During the Downtime roadmap step, the installation process exchanges the kernel and restarts the system.

SAPehpi 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. If you have a dual-stack system, both stacks

are updated at the same time by SAPehpi.

Document Available at…

Installation Guide – SAP Enhancement Package Installer

http://service.sap.com/erp-ehp-inst SAP Enhancement Package 5 for SAP ERP 6.0

SAP Note 1302772 Central Note - SAP Enhancement Package Installer

Installation of Additional Technical Usages

ABAP

To install additional technical usages after you have already installed technical usages of enhancement

package 5 with SAPehpi, use the following tools:

■ If the technical usage Central Applications of enhancement package 5 is already present in your system,

use transaction SAINT.

Make sure you import the newest SPAM/SAINT update before installing additional technical usages

with transaction SAINT. You also have to generate a stack configuration file with the SAP Solution

Manager Maintenance Optimizer. If you want to use the parallel import feature of R3trans, follow

the instructions of SAP Note 1309506.

■ If the technical usage Central Applications is not yet installed in your system, use the SAP Enhancement

Package Installer.

If you have a dual stack system and want to install additional technical usages for ABAP only, you

can disable the Java stack handling. Start the SAPehpi by entering the following additional

parameter for executing the STARTUP script: -srvarg=/DSUService/javadisabled=true

Java

To install additional technical usages for Java, use the Java Support Package Manager (JSPM).

5.1 Additional Application-Specific Information

5.1.1 Preparations

5.1.1.1 SAP Notes

SAP Note Title

1298878 Installation of SAP Enhancement Package 5 on SAP ERP 6.0

5.1.1.2 Free Space Requirements

Make sure, that at least the following free space is available in the system that you want to update:

EHPI Directory Approximately 15 GB

5 Installation


30/44 PUBLIC 2010-12-16

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




Download Directory (temporary space requirement)

Approximately 20 GB

DIR_TRANS Approximately 30 GB

Shadow System Approximately the space required for your source release instance, that is, the size of the following directory: ■ Unix: usr/sap/<sapsid> ■ Windows: <drive>:\usr\sap\<sapsid> ■ IBM i: usr/sap/<sid>

Free space in the database

Approximately 50 GB

5.1.1.3 SAP ECC: Backing Up Wage Types in HR (T512W) (HR Customers)

We recommend that you back up the wage type table T512W before the enhancement package

installation. You must back up this table in the following cases:

■ You have modified technical wage types, that is, wage types beginning with '/' (adjustment of

processing class, evaluation class, and so on).

■ You are using SAP model wage types, that is, wage types beginning with a letter, and have modified

these wage types.

■ You have defined wage types that do not lie within the customer name range. To find out if this

applies, check in table TRESC by entering T512W as the table name and TABU as the object.

Prerequisites

You use the SAP component Human Resources (SAP HR).

Procedure

1. Before the enhancement package installation, back up table T512W or selected areas of this table.

To do this, use report RPU12W0S. The documentation on the report includes instructions on how

to proceed.

NOTE

Table T512W is client-specific. Make sure that you back up the data in all the SAP HR clients

in the system.

2. Document exactly which wage types you have modified.

3. After the enhancement package installation, you can restore your backup copy.

To do this, you can use report RPU12W0C. It reloads selected parts of table T512W. This method

is particularly suitable if you have exact documentation about the wage types you have modified.

NOTE

If you are not sure whether you have to reload the table data, contact your HR application

consultant.

5 Installation


2010-12-16 PUBLIC 31/44

5.1.2 Performing the Installation

5.1.2.1 Vendor Keys for Add-Ons

If ABAP add-ons are installed in your system, you are prompted to take a decision about these add-ons

in Phase IS_SELECT. If you want to keep the existing add-on versions, you need a vendor key. See SAP

Note 1262124 for the vendor keys for all released add-on versions.

5.1.3 Follow-Up Activities

5.1.3.1 Updating Dialog Instances

When you install new dialog instances, make sure that you use the correct installation DVDs.

The DVDs that you use for installing dialog instances have to correspond to the SAP NetWeaver release

and enhancement package level that is underlying your SAP Business Suite application system on the

central instance. So if you have only updated the Business Suite application without the underlying

SAP NetWeaver, you have to use the installation DVDs that match the release and enhancement

package level of SAP NetWeaver. Using the SAP Business Suite 7 i2010 installation DVDs would lead to

problems due to changes in the kernel structure.

5 Installation


32/44 PUBLIC 2010-12-16


6 Configuration

After you have performed all follow-up activities and activated the business functions, you need to

configure the introduced functions. Use the SAP Solution Manager to find the configuration

instructions.

Procedure

To access the configuration tasks, you create a project and a project structure in SAP Solution Manager.

In the configuration phase, you select configuration structures with pre-delivered SAP content for

your project.

Check the configuration for those functions and scenarios that provide enhancements according to

the release notes for enhancement package 5 for SAP ERP 6.0.


SAP Library for SAP Solution Manager: SAP Solution Manager Implementing and Upgrading SAP Solutions Configuration

http://help.sap.com SAP Solutions SAP Solution ManagerDocumentation for SAP Solution Manager <current release>

How to Create a Configuration Guide using SAP Solution Manager

http://service.sap.com/solutionmanager Media Library How-To Documents

6 Configuration

2010-12-16 PUBLIC 33/44

http://help.sap.com

http://service.sap.com/solutionmanager

7 Update of Further Software Units in your System Landscape

7.1 Importing Process Integration Content

Some business functions require an update of the Process Integration content (XI content). You have

to import the new content into the Integration Repository of SAP NetWeaver Process Integration.

Procedure

For a detailed description, see SAP Note 836200.

7.2 Updating the BI Content Add-On

Some business functions require the update of the BI Content Add-On. The BI Content Add-On

Support Packages are applied as common Support Packages using the Support Package Manager

(SPAM).

Procedure

For a more information, see SAP Note 1000822.

7.3 Updating Portal Content

To update Portal Content, you use the Java Support Package Manager.

For information about using Java Support Package Manager, see the SAP NetWeaver Library at http://

help.sap.com/nw70 SAP NetWeaver 7.0 Library <Language> SAP NetWeaver Library SAP NetWeaver

by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software

Maintenance Java Support Package Manager

7 Update of Further Software Units in your System Landscape

7.1 Importing Process Integration Content

2010-12-16 PUBLIC 35/44





A Appendix

A.1 List of Referenced Documentation

The following table lists all documents that are referenced in the present document.

Documentation Location

What IT Professionals Need to Know About SAP Enhancement Packages for SAP ERP


SAP enhancement package 5 for SAP ERP 6.0

Master Guide for SAP Enhancement Package 5 for SAP ERP 6.0 http://service.sap.com/erp-ehp-inst


SAP Business Suite 7 i2010 – Landscape Implementation – Technical Planning Guide



Planning Guide – System Landscape Directory http://sdn.sap.com/irj/sdn/nw-sld

Installation Guide – SAP Enhancement Package Installation – Using SAP Enhancement Package Installer (SAPehpi)



Upgrade Guide – SAP Solution Manager 7.0 incl. Enhancement Package 1

http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP1 -Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0

Solution Operations Guide – SAP Solution Manager 7.0 EHP1, section Software Change Management

Maintenance Optimizer Configuration Guide http://service.sap.com/mopz (link at the bottom of the page)

How to Create a Configuration Guide using SAP Solution Manager http://service.sap.com/solutionmanager

Media Library How-To Documents

A.2 List of Referenced SAP Notes

SAP Note Number Title

1324838 Enhancement package 5 for SAP ERP 6.0: Required SWC

1064635 SAP ERP Enhancement Packages: SP Stacks Release Info Note

1298878 Installation of SAP Enhancement Package 5 on SAP ERP 6.0

1318299 SAP Enhancement Package 5 for SAP ERP 6.0:Compatible Add-ons

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

1436297 Maintenance Optimizer: Notes for Enhancement Packages

1344564 Maintenance Optimizer: Check system landscape

1468605 Installing ST-LV 100 on SAP Solution Manager 7.0

1309506 SPAM/SAINT with parallel R3trans

836200 SAP NetWeaver 7.0: Importing Process Integration Content

A Appendix

A.1 List of Referenced Documentation

2010-12-16 PUBLIC 37/44




http://sdn.sap.com/irj/sdn/nw-sld



http://service.sap.com/mopz

http://service.sap.com/solutionmanager











SAP Note Number Title

1000822 Overview: Notes for BI_CONT add-on

A Appendix

A.2 List of Referenced SAP Notes

38/44 PUBLIC 2010-12-16


B Reference

B Reference

2010-12-16 PUBLIC 39/44

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

■ Cross-references to other documentation or published works

Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

40/44 PUBLIC 2010-12-16

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

2010-12-16 PUBLIC 41/44

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

42/44 PUBLIC 2010-12-16


SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2010 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.