Master Guide

Master Guide

SAP EnhancementPackage 4 for SAPERP 6.0 powered bySAP NetWeaverUsing product versions SAP® ERP 6.0and EHP 4 FOR SAP ERP 6.0, or EHP4FOR SAP ERP 6.0/NW7.01

Target Audience

This documentation contains both overview informationon the solution level and very detailed technicalinformation. The target audience is as following:

• Technology consultants

• System administrators

Document Version 4.00 – February, 2009Material Number 50089319

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

© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or forany purpose without the express permission of SAP AG. The informationcontained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors containproprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks ofMicrosoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX,S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER,POWER5, OpenPower and PowerPC are trademarks or registered trademarks ofIBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks orregistered trademarks of Adobe Systems Incorporated in the United States and/orother 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, andMultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks ofW3C®, 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 licensefor technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAPproducts and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several othercountries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.

These materials are subject to change without notice.These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposesonly, without representation or warranty of any kind, andSAP Group shall not be liable for errors or omissions withrespect to the materials. The only warranties for SAPGroup products and services are those that are set forth inthe express warranty statements accompanying suchproducts and services, if any. Nothing herein should beconstrued as constituting an additional warranty.

DisclaimerSome components of this product are based on Java™.Any code change in these components may causeunpredictable and severe malfunctions and is thereforeexpressly prohibited, as is any decompilation of thesecomponents.

Any Java™ Source Code delivered with this product isonly to be used by SAP’s Support Services and may notbe modified or altered in any way.

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

http://www.sap.com/

Typographic ConventionsType Style Represents

Example Text Words or characters thatappear on the screen. Theseinclude field names, screentitles, pushbuttons as well asmenu names, paths andoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrasesin body text, titles of graphicsand tables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, table names,and individual key words of aprogramming language, whensurrounded by body text, forexample, SELECT andINCLUDE.

Example text Screen output. This includes fileand directory names and theirpaths, messages, names ofvariables and parameters,source code as well as namesof installation, upgrade anddatabase tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Example text> Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLE TEXT Keys on the keyboard, forexample, function keys (such asF2) or the ENTER key.

IconsIcon Meaning

Caution

Example

Note

Recommendation

Syntax

Master Guide: SAP Enhancement Package 4 for SAP ERP 6.0

4 February, 2009

History of ChangesYou find updated versions of this Master Guide in SAP Service Marketplace athttp://service.sap.com/erp-inst.

Make sure you have the latest version of the Master Guide by checking SAPService Marketplace immediately before you start to plan the installation ofthis enhancement package.

SAP enhancement packages are cumulative. SAP recommends that youalways install the latest available enhancement package. Before you installthe current enhancement package, or before you continue with this guide,check for the latest enhancement package on SAP Service Marketplace athttp://service.sap.com/erp-inst.

The following table provides an overview of the most important changes made in the latestversions.

Master Guide Version Important Changes

4.00 (February 03, 2008) Different updates in Section 2.2.3 SAP NetWeaverEnhancement Packages

Update Figure: Entity Relationship Model

New SAP Note 1122966

Several minor corrections

3.00 (January 19, 2009) Textual enhancements and revisions

2.00 (December 12, 2008) Added Notes 1273780, 1164532, 1280819, 1161294,1155041, 1156407, 1164979

Removed Notes 503468, 700778, 830593 (alreadydocumented in SAP ERP 6.0 Master Guide)

Name chg, SAP Solution Manager 4.0 to SolutionManager 7.0

Change in required software components for SWIFTand BCONS

Installation requirements for ABAP Product Instances

Manual process to load ECC-SE from DVD

SRM Add-On installation

Embedded Search in Section General ProductInstances

Textual enhancements

1.20 (November 21, 2008) Initial version Ramp-Up customers SAPenhancement package 4 for SAP ERP 6.0

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


Master Guide SAP Enhancement Package 4 for SAP ERP 6.0

February, 2009 5

ContentsHistory of Changes ................................................................................4

1 Getting Started.................................................................................71.1 About this Document.......................................................................71.2 Related Information .........................................................................9

1.2.1 Planning Information .......................................................................... 91.2.2 Further Useful Links ........................................................................... 91.2.3 Related Master and Upgrade Master Guides .................................. 10

1.3 Important SAP Notes .....................................................................112 SAP Enhancement Package for SAP ERP Overview.................14

2.1 New Enhancement Package Delivery Architecture ....................142.1.1 Selective Installation or Update of Software Components............ 152.1.2 Selective Activation of Features Installed....................................... 15

2.2 Integration into Overall Architecture............................................162.2.1 Relationship between Enhancement Package Versions ............... 162.2.2 Software Corrections, Legal Changes and Minimum SupportPackages..................................................................................................... 172.2.3 SAP NetWeaver Enhancement Packages........................................ 19

2.3 Installation and Upgrade ...............................................................212.3.1 New Installation of SAP ERP 6.0 with Enhancement Packages .... 232.3.2 Installation of Enhancement Packages with the Upgrade to SAPERP 6.0........................................................................................................ 252.3.3 Installation of Enhancement Packages in an existing SAP ERP6.0 System Landscape............................................................................... 262.3.4 SAP Enhancement Package Installer and MaintenanceOptimizer in Detail...................................................................................... 27

3 Software Units, Systems and Installation...................................303.1 Software Units of SAP Enhancement Package 4 for SAP ERP6.0 ..........................................................................................................30

3.1.1 Technical Usages.............................................................................. 323.1.2 ABAP Product Instances .................................................................. 363.1.3 General Product Instances............................................................... 413.1.4 Content Instances ............................................................................. 58

3.2 Software Component Matrix .........................................................733.3 System Landscapes.......................................................................753.4. Overall Installation Sequence ......................................................77

3.4.1 Phase 1: Planning the Enhancement Package Installation ........... 793.4.2 Phase 2: Enhancement Package Installation.................................. 833.4.3 Phase 3: Enhancement Package Testing and Activation .............. 87

Master Guide: SAP Enhancement Package 4 for SAP ERP 6.0

6 February, 2009

4 Solution-Wide Topics...................................................................904.1 Planning and Optimizing System Landscapes ...........................90

4.1.1 The Enhancement Package in a SAP Business Suite SystemLandscape .................................................................................................. 904.1.2 General Planning Approach ............................................................. 93

4.2 Generic Business Processes, Scenarios and Role-BasedWork Centers........................................................................................95

4.2.1 Processes and Role-Based Work Centers with Enhancements.... 954.2.2 Role-Based Work Centers and Automatic Roles............................ 974.2.3 Industry Solution Scenarios in SAP enhancement package 4for SAP ERP 6.0.......................................................................................... 99

4.3 Service-Oriented Architecture (SOA) .........................................1024.4 Add-On Products ........................................................................1044.5 Software Architecture.................................................................1054.6 Additional Products and Third-Party Products........................108

5 Media List .....................................................................................1115.1 EHP 4 for SAP ERP 6.0 [Easy Adoption]....................................1125.2 EHP 4 for SAP ERP 6.0/ NW 7.01 [Continuous Innovation] .....112

6 References ...................................................................................1186.1 List of Documents........................................................................1186.2 List of SAP Notes .........................................................................1196.3 Terminology Concept ..................................................................1256.4 Glossary........................................................................................126

7 The Main SAP Documentation Types .......................................130


7 February, 2009

1 Getting StartedSAP is adapting the major release strategy for the SAP ERP Application to better fit thecustomer adoption cycle. To ensure that customers still benefit from new developments andinnovations while minimizing the impact on core operational systems, SAP will accelerate thedelivery of new functions through enhancement packages for SAP ERP (short enhancementpackages), which customers can choose to implement in addition to SAP ERP 6.0.Enhancement packages contain functional enhancements and enterprise services in areassuch as shared services, or end-to-end business processes such as order-to-cash or hire-to-retire, or supplier collaboration. They furthermore contain industry-specific functions.SAP’s new enhancement package delivery-model will deliver new developments morequickly and in a more accessible way.

1.1 About this DocumentPurposeThis Master Guide is the central starting point for the technical Installation of the currentenhancement package. You can find here cross-scenario installation information, which isenhancement package specific.

The overall Master Guide design distinguishes the following major tasks: Starting point for the Technical Upgrade of your existing SAP ERP

application is the Upgrade Master Guide SAP ERP 6.0, Orientation for the Technical Installation of SAP ERP 6.0 is the

Master Guide SAP ERP 6.0You find this supplemental documentation on SAP Service Marketplace athttp://service.sap.com/erp-inst.

Use this Master Guide to get an overview of the enhancement package, its software units, itsscenarios, processes, and role-base work centers from a technical perspective. As a planningtool, the Master Guide prepares you to install the enhancement package in your existing SAPERP system landscape. It refers you to the detailed documentation required to install it.These are mainly:

Installation guides for single software units

SAP Notes

Configuration documentation

SAP Library documentation

Related Master Guides

For a general overview of the available SAP documentation, see The Main SAPDocumentation Types.

StructureThis Master Guide consists of the following main sections:

Section 1 - Getting Started explains how to use this document and relatedinformation (documentation and SAP Notes) that is crucial to the installation andupgrade.

Section 2 - SAP Enhancement Package for SAP ERP Overview concentrates onnecessary information relating to the Enhancement Package overview, the deliveryarchitecture, the structuring of the SAP ERP software, and important definitions. It


1 Getting Started

8 February, 2009

furthermore describes the essential tools as well as the option to install theenhancement package with an upgrade to SAP ERP 6.0.

Section 3 - Software Units, Systems and Installation concentrates on information forspecial cases. It provides information about the software and software componentsdelivered. It also helps you understand the relationship between business functionsand the changes affecting the corresponding systems.

Section 4 - Solution-Wide Topics addresses topics relevant to the completeenhancement package on a case-to-case basis, such as the introduction of theService-Oriented Architecture (SOA), or the system landscape planning approach. Itgives you a conceptual understanding of applications and solutions enabled by thecurrent enhancement package and the software architecture.

Section 5 - Media List explains the physical delivery and the technical prerequisitesfor installation.

Section 6 - References lists all relevant SAP Notes or external references anddefines important terminology

Section 7 - The Main Documentation Types gives you further insight into thecomplete SAP Documentation concept.

ContextThe current enhancement package guide covers the following areas of interest:

Concept for the installation of software components for the generic SAP ERP and themethods to enable new or changes Business Functions in your system landscape

Installation of the different parts of the enhancement package in an existing SAPERP 6.0 system landscape

The new software delivery architecture for the enhancement packages and theinstallation

Planning information, which is depending on the functional scope which you intend toinstall

Scope of the enhancement package

This Master Guide does not cover the following information:

Separate Master Guides support you with SAP Industry Solutions, other SAPApplications, SAP NetWeaver, or cross application developments such as theinstallation of the Service-Oriented Architecture (SOA).

More information about the installation of or the upgrade to SAP ERP is part ofadditional guides for SAP ERP 6.0 and for SAP NetWeaver 7.0

Separate documentation is available to cover the functional perspective of theenhancement packages.

Installation and Configuration guides are available with detailed instructions, whichguide you through the installation process.

For information about limitations to the current enhancement package, if any, seeSAP Service Marketplace at http://service.sap.com/notes SAP Note998833.

Keep the following in mind, when using this Master Guide

Additional software dependencies, which are not mentioned explicitly in the presentdocument, might exist

http://service.sap.com/notes


9 February, 2009

The business scenarios and processes presented here serve as examples of howyou can use SAP software in your company. The business scenarios intend to serveas models. They will not necessarily run in your customer-specific system landscapeas described here. Make sure you check your requirements and systems todetermine whether you can use these scenarios productively at your site.

SAP recommends that you test these scenarios and the installation of theenhancement package thoroughly in your test systems to ensure they are completeand free of errors before going live.

1.2 Related Information1.2.1 Planning InformationSAP delivers the Master Guide for this enhancement package for SAP ERP as an extensionto the Master Guide for SAP ERP 6.0. For additional mandatory planning topics not coveredin this guide, see the following content on SAP Service Marketplace:

Content Location on SAP Service Marketplace

General Information about SAP ERP http://service.sap.com/erp

Content of SAP enhancement packages forSAP ERP/Evaluation information

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

Master guides, installation guides andupgrade master guides

http://service.sap.com/instguides,

Latest versions of installation and upgradeguides SAP ERP, including updated versionsof the Upgrade/Master Guide for SAP ERP6.0.


Installation information SAP NetWeaver andMaster Guide for SAP enhancement package1 for SAP NetWeaver 7.0.

http://service.sap.com/instguidesnw

Master Guide for SAP NetWeaver 7.0(formerly SAP NetWeaver 2004) includingTechnology Consultant's Guide

http://service.sap.com/instguidesnw70

Product Availability Matrix http://service.sap.com/pamScenario and Process Component List http://service.sap.com/sclSupport Package Stacks, latest softwareversions and patch level requirements

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

Release Information SAP enhancementpackage 1 for SAP NetWeaver 7.0

help.sap.com SAP NetWeaverSAP enhancement package 1 for SAPNetWeaver What's New - ReleaseNotes

1.2.2 Further Useful LinksThe following table lists further useful links on SAP Service Marketplace:

Content Location on SAP Service MarketplaceSAP Developer Network with informationabout the Service-Oriented Architecture(SOA)

sdn.sap.com/irj/sdn/developerareas/esa (registration required)

Information about SAP Industry Solutions,and Industry Solution Sets

http://service.sap.com/industries

http://service.sap.com/erp


http://service.sap.com/instguide




http://service.sap.com/pam

http://service.sap.com/scl


http://service.sap.com/industrie

1 Getting Started

10 February, 2009

Information about creating producterror/customer messages

http://service.sap.com/message

SAP Support Portal with further supportfunctions

http://service.sap.com/support

SAP Notes search engine http://service.sap.com/notes

SAP Software Distribution Center (softwaredownload and ordering of software)

http://service.sap.com/swdc

Security Guides and Network security http://service.sap.com/securityguide

Ramp-Up Knowledge Transfer (RKT) - theRKT program is a crucial element of the SAPSolution Ramp-Up process

http://service.sap.com/rkt

SAP Solution Browser solutionbrowser.erp.sap.fmpmedia.com/

SAP Business Maps - blueprints visualizingkey business solutions

http://service.sap.com/businessmaps

Information about Unicode technology -Unicode Code Page Technology for YourSystem Landscapes

http://service.sap.com/unicode@sap

Released platforms and technology-relatedtopics such as maintenance strategies andlanguage support

http://service.sap.com/platforms

To access the PlatformAvailability Matrix directly,enterhttp://service.sap.com/pam.

High Availability http://service.sap.com/ha, orhttp://www.sdn.sap.com/irj/sdn/netweaver

Performance for SAP Business Suite http://service.sap.com/performance

Sizing, calculation of hardware requirements -such as CPU, disk and memory resource withthe Quick Sizer tool

http://service.sap.com/quicksizer

1.2.3 Related Master and Upgrade MasterGuidesYou install SAP Industry Solutions in system landscapes for SAP ERP 6.0. Selected industryspecific scenarios might require the installation of software components from other SAPApplications or SAP Solutions.

The enhancement package includes developments for SAP Industry Solutions as shown inthe following table.SAP Industry Solution As of SAP enhancement package <n>

for SAP ERP

SAP for Aerospace & Defense 2, 3, 4SAP for Automotive 2, 3, 4SAP for Consumer Products 3

http://service.sap.com/message

http://service.sap.com/support



http://service.sap.com/securityg

http://service.sap.com/rkt

http://service.sap.com/businessm

http://service.sap.com/unicode@s

http://service.sap.com/platforms

http://service.sap.com/pam.

http://service.sap.com/ha

http://www.sdn.sap.com/irj/sdn/n

http://service.sap.com/performan

http://service.sap.com/quicksize


11 February, 2009

SAP Industry Solution As of SAP enhancement package <n>for SAP ERP

SAP for Defense & Security 3SAP for Higher Education 4SAP for Insurance 3, 4SAP for Media 2, 4SAP for Mill Products 2SAP for Public Sector 1, 2SAP for Professional Services 3SAP for Retail 1, 2, 3, 4SAP for Telecommunications 2, 4SAP for Utilities 2, 4SAP for Waste & Recycling 2SAP for Wholesale Distribution 2, 3

This Master Guide concentrates on cross-industry contents such as information aboutactivation or upgrade. You can find industry specific information and information about relatedSAP applications in the following documents:

Title Location

Information about SAP Industry Solutions http://service.sap.com/industries

Master Guides for SAP Industry Solutions,including SAP Industry Master Guides areavailable for the specific enhancementpackage for SAP ERP

http://service.sap.com/instguides(use the index to navigate)

Master Guides for other SAP Applicationswith information about non-SAP ERPsystem landscape elements

http://service.sap.com/instguides(use the index to navigate)

1.3 Important SAP NotesAfter you have planned the installation with the help of this guide, you start to implement theenhancement package. Make sure, to read the following SAP Notes before you start with theinstallation. These SAP Notes contain the most recent information on the installation, as wellas corrections to the installation documentation. In References can you find further SAPNotes with optional characters.

You can find the most up-to-date version of each SAP Note on SAP Service Marketplace athttp://service.sap.com/notes or by following the links below.

SAPNoteNumber

Title Content

824757 Dependencies between SAPERP component lists

Dependencies of Role-Based Work Centerswith generic SAP ERP Processes

849887 SAP ERP 6.0: Support PackageStacks Release and Info Note

Contains a list of all SAP ERP 6.0 Releaseand Information Notes (RIN) issued for SAPERP 6.0

883072 Globalization information onSAP ERP

Detailed information about translation andcountry availability of SAP ERP

998833 Release Restrictions SAP ERP Information about the limitations for


http://service.sap.com/instguides



1 Getting Started

12 February, 2009

SAPNoteNumber

Title Content

6.0 - Enhancement Packages enhancement packages for SAP ERP 6.0

1064635 SAP ERP EnhancementPackages: SP Stacks ReleaseInfo Note

Release Information Notes for: SAP ERPEnhancement Package Releases, SAP ERPEnhancement Package Support Package(SP) Stacks and corresponding orequivalent SAP ERP 6.0 Support PackageStacks

1066110 ERP Enhancement Package:Installing the SAP Library

Enhancement Package 2 for SAP ERP 6.0or the Enhancement Package 3 for SAPERP 6.0 and information about installing theSAP Library on your customer server

1122966 Maintenance Optimizer: Notesfor Enhancement Packages

You want to import ERP 6.0 EnhancementPackages using the Maintenance Optimizer.The import is possible as of SolutionManager 4.0 Support Package 13.

1117309 Compatibility of Add-Ons vs.enhancement packages for ERP6.0

Information, which you need, when youintend to apply an enhancement package toa system instance, which already includes adifferent Add-On.

1143022 Installation of EnhancementPackage 4 on SAP ERP 6.0

Information about enhancing existingsoftware components using EnhancementPackage 4 on SAP ERP Central ComponentECC 600 (referred to here as SAP ECC600)

1150349 ECC-SE 604 Add-On Installation/Delta upgrade

How to install/upgrade to ECC-SE 604 onSAP ERP Central Component ECC 600using transaction SAINT

1150350 Upgrade to SAP ECC 600 withAdd-On ECC-SE 604

Information about the upgrade to ReleaseSAP ERP Central Component ECC 600(referred to in this note as SAP ECC 600)using ECC-SE 603

1156407 SAP ERP Enhan. Pk. 4 SPStacks - Release & InformationNote

This Release Information Note (RIN)contains information and references tonotes for applying Support Package (SP)Stacks of SAP Enhancement Package 4 forSAP ERP 6.0 (Initial shipment). SAP Note1064635 lists further SAP notes withRelease Information.

1160106 Enhancement package 4 forSAP ERP: Installing JAVA

Importing components of enhancementpackage 4 for SAP ERP 6.0 created in Javato a central J2EE server

1164532 Release restrictions of SAP EHP1 for SAP NetWeaver 7.0

At the time of the release of SAPenhancement package 1 for SAPNetWeaver 7.0 limitations existedconcerning the productive usage of certainfunctions. This note provides customerinformation on these restrictions.


13 February, 2009

SAPNoteNumber

Title Content

1165067 Release Info SAP EnhancementPackage 4 for SAP ERP 6.0

Enhancement package 4 for SAP ERP 6.0complements the SAP ERP 6.0 release in anumber of focus areas. It is easy to installand immediately adds incremental value toyour business processes without disruption

1165437 Enhancement package 4 forSAP ERP: Required supportpackages

Information on installation prerequisites forEnhancement Package 4 for SAP ERP 6.0

1165438 Enhancement package 4 forSAP ERP: Required SWCV

How to install dedicated parts ofenhancement package 4 for SAP ERP 6.0

1165442 Enhancement package 4 forSAP ERP: Info for portal content

Enhancement package 4 for SAP ERP 6.0includes new portal roles and functions

1258912 PLM Core 7.00 Release Notesand Information

Information and references to other notesabout installing PLM Core 7.00 andimporting PLM Core 7.00 SupportPackages. We update the SAP notewhenever new information is available, andwe will add Support-Package-specificinformation.

1275873 Memory bottleneck during DDICactivation during EHP import

For the installation of ERP 6.0Enhancement Package 4 in particular, youmust assign sufficient memory to the workprocesses.

2 SAP Enhancement Package for SAP ERP Overview

14 February, 2009

2 SAP Enhancement Package for SAPERP OverviewPurposeEnhancement packages for SAP ERP make additional high-value applications available toorganizations that have implemented SAP ERP 6.0, or that are in the process of upgrading toSAP ERP 6.0. It is possible to view enhancement packages from different perspectives:

Installation view

Enhancement packages represent a new delivery model for SAP software, whichsimplifies the installation, and lowers the total cost of ownership. The enhancementpackage software-delivery relies on new principles and installation tools, which letcustomers enhance the existing system landscape with new features withoutdisrupting the productive use.

Functional/Business view

Enhancement Packages are packages that make new and enhanced softwareavailable to customers. They include the following types of software:

o Functional enhancements to existing functions

o New functions and features

o Enhancements to enable SAP Applications or Solutions other than SAPERP, or SAP Industry Solutions

OverviewThe following sections will concentrate on the installation view. It will give an overview overthe different key changes, introduced with the enhancement packages.

Find information about the functional/business view –in Business Processes and Role-BasedWork Centers of SAP ERP. This section explains how the system administrator installs theenhancement package in special cases.

With the current enhancement different new options exist, which go beyond the enhancementof an existing SAP ERP 6.0 system landscape, which was in focus until SAP enhancementpackage 3 for SAP ERP 6.0. Keep in mind that this guide will concentrate on general options,while other Master Guides are available for further options.

The enhancement package for SAP ERP bases on the enhancementpackage 1 for SAP NetWeaver 7.0 (product version SAP EHP1 FOR SAP NW7.0 FOR BPC). A separate guide is available, for the latter enhancementpackage..

2.1 New Enhancement Package DeliveryArchitecturePurposeSAP has based the enhancement package concept on several new key features and conceptchanges in the area of software delivery and installation. A better understanding of thesechanges enables the system administrator to verify the different advantages and to define hisown Installation strategy for these packages.


15 February, 2009

These changes affect the following areas

Installation of the enhancement package on SAP ERP 6.0

Embedding of SAP ERP 6.0 into a SAP Business Suite system landscape

This section concentrates on the first area.

2.1.1 Selective Installation or Update ofSoftware ComponentsOverviewPrior to the availability of the enhancement package delivery-architecture, it was necessary toupgrade the complete SAP system instance to a new release. With the enhancementpackages, it is possible to update system instances selectively within a highly automatedprocess and to enhance the system with new features. The selective installation/upgradesimplifies the installation process.

In order to allow for the selective installation and upgrade of existing system instances,enhancement packages contain either new versions of software components of SAP ERP 6.0or additional software components. When you install an enhancement package, you onlyupdate the used software components in the existing SAP ERP 6.0 system instance.

Instead of upgrading the SAP ECC Server system instance completely, thenew installation tools enable you to update those selected parts your SAPECC Server, which are appropriate from a business point of view.

Tool SupportEach function and feature of the enhancement package relates to the appropriate BusinessFunction. The Business Functions, and thus the business related features, which you plan touse, will dictate which software and software components you to install in your existingsystem instances.

A new installation tool, called the Solution Manager - Maintenance Optimizer, supports both,the selection of business functions and the installation of the required software components.This tool identifies the following information automatically:

The installation packages and the support packages, which correspond to the currentsystem status

The software components chosen for installation

The entire installation procedure is highly automated and after completion, the MaintenanceOptimizer provides a configuration file for the corresponding installation tools.

2.1.2 Selective Activation of Features InstalledOverviewBefore availability of the new enhancement package delivery-architecture, the completefunctionality, including all user interface changes and business process alterations wereavailable and active only after the installation process was finished. In order to allow for aninternal rollout out of newly installed features it was necessary to separate productivesystems from systems in upgrade. Now with the enhancement package delivery-architecture,the following steps are uncoupled:

Upgrade/installation step of new functions or user interface changes


16 February, 2009

Installation and activation step for these system changes.

The selective activation principle of enhancement packages allows the system administratorplan the internal rollout of newly installed features in advance as well as to see it as a stepseparate from the installation. It is thus possible to install software features alongside normalsystem maintenance activities and then to roll them out in a separate step.

Important Software Architecture ChangesEach installed part of an enhancement package remains hidden in the corresponding systeminstance until you activate it. On an architectural level:

SAP uses the Enhancement and Switch Framework of SAP NetWeaver 7.0 to deliverenhancements, so that this has no impact on existing business processes or userinterfaces as long as you did not activate the appropriate Business Function. In SAPERP 6.0 this framework is used to activate SAP Industry Solutions and is now alsoextended to activate other functional enhancements

On a technical level, we have linked each code enhancement of an enhancementpackage to one or more switches. The activation of a business function alters theseswitches and controls which parts of the software installed are active and visible

The system ensures that no side effects exist between different business functions. Itis furthermore ensured that the installation of an enhancement package has noimplications for the underlying SAP NetWeaver platform

RecommendationsThe following recommendations relate to the activation of installed parts of an enhancementpackage:

Before starting the activation process note that it is not possible to reverse theactivation of a business function

Review the functional changes and business functions in the SAP documentation inorder to identify which activations are possible

Run the activation process as a central activity in your SAP system instances, so thatall required activations in these system instances are made automatically withoutfurther action on your part

2.2 Integration into Overall ArchitecturePurposeEnhancement packages are part of the existing overall software architecture of SAP ERP. Anoverview of the integration points between the enhancement package delivery-architectureand the overall architecture helps an experienced system administrator to understand the bigpicture as well as to understand the areas enhanced from the existing concept.

2.2.1 Relationship between EnhancementPackage VersionsOverviewEnhancement packages are available for a specific Go-To release of the principle underlyingSAP Application, such as SAP ERP 6.0. Over time, different enhancement package versionswill be available, each focusing on different functional enhancements. From time to time, youmight be interested in implementing a new business function, introduced in a previousenhancement package. In these cases you need to know if and how it is possible to


17 February, 2009

implement functional enhancements from different enhancement package versions in one-step.

Accumulation ParadigmThe following relationship between enhancement package versions is part of theenhancement package design:

Enhancement package versions are cumulative, so that the current enhancementpackage contains the entire content of all earlier enhancement packages

Each enhancement package has the same maintenance duration as the underlyingcore application release SAP ERP 6.0.

The installation documentation, such as the Master Guides are also cumulative. Inmost cases, it is sufficient to read the latest installation and upgrade documentationfor a specific enhancement package because adapted information from earlierversions is included as well.

Due to the cumulative design

SAP recommends that you always install the latest enhancement package for SAPERP 6.0 available

It is not possible to mix the installation of different enhancement package versions

Exceptions to the Accumulation ParadigmIn very early enhancement packages, SAP has made exceptions to the accumulationparadigm. These exceptions are relevant to few early adaptors of the first enhancementpackage using these specific functions:

We have introduced the product instance SAP FinServ Claims Mgmt with the productversion for enhancement package 1 for SAP ERP 6.0 (software component IS-FS-CM). It is not available in Enhancement Package 2005.2 or subsequent productversions. From a functional perspective, refer to the deliveries with product versionSAP ERP 6.0.

For certain installation or upgrade scenarios, a two-step approach is required, which consistsof the consecutive installation of several enhancement packages. Find below moreinformation about these scenarios.

2.2.2 Software Corrections, Legal Changes andMinimum Support PackagesOverviewThe software maintenance makes high prioritization changes, such as legal changesavailable in existing productive system instances. Continuous improvements on the otherhand are software alterations, which might take time to implement or which need to be rolled-out internally. However, both types of developments typically depend on each other.

Before the enhancement package delivery-architecture was available, the softwaremaintenance and the continuous improvement of the SAP customer system landscape wasbased on support packages. In effect, there was no choice but to install legal changes andenhancements simultaneously, sometimes generating an unwanted overhead in terms of theneed to roll out changes internally.

The recommendations in the following section are the result of the separation of thedependencies between Support Packages and Enhancement Packages.


18 February, 2009

Support Packages versus Enhancement PackagesWith the introduction of the enhancement package delivery-architecture, SAP has refocusedthe support packages as follows:

Continuous improvements to SAP ERP 6.0 are now being made available as part ofthe enhancement packages

Legal changes and software corrections for SAP ERP 6.0 continue to be part of thesupport package framework

Synchronized, but separate support package stacks are available for both SAP ERP6.0 and the enhancement packages. Both types of package are independent andavailable for a unique maintenance period. An equivalence level defines thesynchronization of the different support package stacks. The deviation in thenumbering of Support Package Stacks for Human Capital Management and SAPERP 6.0 reflect the more frequent legal change deliveries in that area.

When you analyze your system instances after having installed theenhancement package, you will find both software component versions 600(with a given Support Package level) and software component version 604(with a given Support Package level).

The version number normally indicates the component version (here SAPERP 6.0 and enhancement package 4 for SAP ERP 6.0).

It also holds that the latter Support Package level for the enhancementpackage contains corrections for software component version 604, which areequivalent to those in the corresponding Support Package level of the samesoftware component in version 600.

Recommendations for the installationThe relationship between functional enhancements and legal changes/software corrections isas follows:

As certain continuous improvements might require a defined legal change,dependencies between both package-types are possible. This is the reason whyenhancement packages generally require a defined Support Package Stack of SAPERP as a basis. This Support Package Stack includes a predefined set of supportpackages for SAP ERP and for the underlying SAP NetWeaver platform

In order to reduce the downtime and the manual effort for the entire installationprocedure, you should combine the installation of the enhancement package, and theInstallation of the Support Package Stack in one queue. This strategy ensures also,that the modification adjustment is only required once. You perform the combinationin the enhancement package installation tool, which you used (see Installation andUpgrade)

If your systems include modifications, for both the support package installation andthe enhancement package installation it may be necessary to adjust thesemodifications

Documentation ReferencesThe following includes information about the minimum support package requirements for thecurrent enhancement package:

The technical and support package prerequisites for installing the differentenhancement packages are documented in the following SAP Notes:


19 February, 2009

Enhancement package 2 for SAP ERP 6.0: SAP Note 1052522



For more information about SAP support package stacks, including equivalencelevels, see the specific Release and Information Notes accessible from SAP Note1064635 on SAP Service Marketplace at http://service.sap.com/sp-stacks(For the initial shipment of the current enhancement package see the SAPRelease Information Note 1156407).

For additional information about the design of support package stacks, and theirdownload, see the SAP Service Marketplace http://service.sap.com/swdc-addinfo.

Important SAP Notes, to be considered with the Installation of an enhancementpackage are summarized in the release information:




2.2.3 SAP NetWeaver Enhancement PackagesOverviewEnhancement packages include new and changed features for a specific go-to release of thecorresponding SAP application. SAP ERP 6.0 is the go-to release for the SAP ERPapplication. You install SAP ERP 6.0 in system landscapes on SAP NetWeaver 7.0.

With enhancement package versions prior to enhancement package 4 for SAP ERP 6.0, theunderlying SAP NetWeaver 7.0 release level of SAP ERP was unchanged. As of the currentenhancement package for SAP ERP, enhancement packages for SAP NetWeaver 7.0 areavailable. Over time, different enhancement package versions will be available for both SAPERP and SAP NetWeaver, and dependencies are possible.

The following installation options exist:

Easy Adoption path

Continuous Innovation path

These options avoid situations, in which the installation of an enhancement package for SAPNetWeaver 7.0 requires you to update Java-based system instances, although you do notneed to update them from the functional perspective.

SAP Enhancement Package 1 for SAP NetWeaver 7.0 and the SAPEnhancement Package 4 for SAP ERP 6.0SAP product versions include all installable software units for a business application. Productversion SAP ERP 6.0 includes the software components for the business application SAPERP 6.0. For each enhancement package, at least one separate product version is available.

Among others, the SAP ERP 6.0 product version includes those parts of the SAP NetWeaverplatform, which are necessary to enable the different SAP ERP business processes. Keep inmind that further SAP NetWeaver features are available, which you use in addition to SAPERP or other SAP Business Suite applications.

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

http://service.sap.com/swdc-


20 February, 2009

The SAP ERP process Group Close among others requires a systeminstance, based on the SAP NetWeaver usage type EP Core. Productinstance SAP NW – EP Core includes this usage type and is part of theproduct version SAP ERP 6.0.

Different mobile functions are available in addition to the SAP ERPApplication. The required SAP NetWeaver usage types are not necessarilypart of product version SAP ERP.

The current enhancement package supports different installation options and systemlandscape alternatives in terms of system instances on the usage type AS Java. Therationale behind this distinction is as follows:

Easy Adoption: When installing an enhancement package in an existing systemlandscape on SAP NetWeaver 7.0, dependencies might be relevant. In these cases,you might require that as many as possible system instances remain unchanged onSAP NetWeaver 7.0

Continuous Innovation: New installations can use software components of the currentenhancement package, without having to consider dependencies to older versions. Inthis situation, you install the enhancement package together with the enhancementpackage for SAP NetWeaver in all system instances

In order to enable these different options, the following product versions are available with thecurrent enhancement package:

Product Version EHP 4 for SAP ERP 6.0 [Easy Adoption]

Product Version EHP 4 for SAP ERP 6.0/ NW 7.01 [Continuous Innovation]

A complete installation requires product instances from the product version SAP ERP 6.0,and from one of these abovementioned Add-On product versions. On technical level, thedifference between these Add-On product versions is as follows:

Using the Easy Adoption product version, all system instances on usage type ASJava remain on SAP NetWeaver 7.0, while you update the system instances onusage type AS ABAP with the enhancement package 1 for SAP NetWeaver 7.0

Using the Continuous Innovation product version, you install the enhancementpackage 1 for SAP NetWeaver 7.0 in all system instances on usage type AS ABAPand on usage type AS Java

Both product versions include the same software components in differing releases. You canthus install them in the same installation process. Structural differences between theseproduct versions are possible with some product instances on AS Java, which are not part ofa predecessor enhancement package.

Product instances BI Java and SAP XECO are included in the productversions SAP ERP 6.0, and in EHP4 FOR SAP ERP 6.0/ NW 7.01. As theseversions are not part of any predecessor enhancement package, they are notpart of product version EHP4 FOR SAP ERP 6.0.

Installation of the SAP Enhancement Packages for SAP NetWeaverAs mentioned before, you install product instances for the enhancement package for SAPERP selectively in addition to product instances for SAP ERP 6.0 (selectiveinstallation/upgrade).

Starting with the current enhancement package, the different product instances of theenhancement package include software components for the SAP enhancement package 1for SAP NetWeaver 7.0 as well as the different usage types, which are required for that


21 February, 2009

particular product instance. The installation process for the enhancement package for SAPERP takes care of the update of these SAP NetWeaver software-components.

The SAP ERP 6.0 product instance SAP ECC Server bases on the SAPNetWeaver 7.0 usage type AS ABAP. Among others, it includes the softwarecomponent SAP WEB AS 7.00 – SAP WEB AS ABAP.

With the current enhancement package, you install the ABAP ProductInstance Central Applications on the SAP ERP 6.0 – SAP ECC Server. Thisproduct instance requires the availability of enhancement package 1 for SAPNetWeaver 7.0 on the usage type AS ABAP (Software component SAP WEBAS 7.01 – SAP WEB AS ABAP).

The installation tools take care to install the required enhancement packagefor SAP NetWeaver. After the installation of Central Components, you haveupdated the underlying SAP System to SAP enhancement package 1 for SAPNetWeaver 7.0.

Documentation References Dedicated Master Guides are available, which describe the installation of

enhancement packages for SAP NetWeaver 7.0. You find them in the SAP ServiceMarketplace at http://service.sap.com/instguides.

For more information about the related functional changes, and enhancements, seethe Release Information SAP enhancement package 1 for SAP NetWeaver 7.0 onhelp.sap.com SAP NetWeaver SAP enhancement package 1 for SAPNetWeaver What's New - Release Notes.

For more information about the system landscapes, see The Enhancement Packagein a SAP Business Suite System Landscape.

2.3 Installation and UpgradeOverviewThe following scenarios are possible in terms of the installation of the enhancementpackages for SAP ERP and for SAP NetWeaver:

New Installation of SAP ERP 6.0 with enhancement package 4 for SAP ERP 6.0,based on enhancement package 1 for SAP NetWeaver 7.0 in all system instances

Upgrade to SAP ERP 6.0 with enhancement package 4 for SAP ERP 6.0, based onenhancement package 1 for SAP NetWeaver 7.0 in all system instances

Installation of enhancement package 4 for SAP ERP 6.0 in an existing SAP ERP 6.0system landscape:

System instances on usage type AS ABAP are made available onenhancement package 1 for SAP NetWeaver 7.0

System instances on usage type AS Java might reside on SAP NetWeaver7.0

Both, the approach and the installation tools differ by scenario as described in this section.

Scenarios and ToolsFor more information about the installation tools, the resulting state of the target systeminstance, and the required installation guides see the following table.

http://service.sap.com/instguides.


22 February, 2009

Table 1: Installation/ Update Scenarios and Tools

Case Activity [Guide fromhttp://service.sap.com/erp-inst]

Tool

NewInstallation ofSAP ERP 6.0withenhancementpackage 4 forSAP ERP 6.0

Installation of SAP ERP 6.0 on SAPenhancement package 1 for SAPNetWeaver 7.0

With technical usage ABAP Technologyfor ERP EHP4 from Product VersionEHP4 for SAP ERP 6.0

[Installation Guide – SAP EnhancementPackage 4 for SAP ERP 6.0]

New System Installation(SAPInst)

Upgrade toSAP ERP 6.0withenhancementpackage 4 forSAP ERP 6.0

Upgrade from Release < SAP ERP 6.0to SAP ERP 6.0

On SAP enhancement package 1 forSAP NetWeaver 7.0with installation oftechnical usages from Product VersionEHP4 for SAP ERP 6.0

[Upgrade Guide – SAP EnhancementPackage 4 for ERP 6.0]

Standard Upgrade (SAP Up/SAP Jup)

Installation ofenhancementpackage 4 forSAP ERP 6.0on existingSAP ERP 6.0

Easy Adoption – 64 bit

Installation of Technical Usages fromEHP4 for SAP ERP 6.0

SAP ERP 6.0 ABAP System Instanceson SAP EHP1 for SAP NW 7.0, and JavaSystem Instances remain on SAPNetWeaver 7.0

[Installation Guide – SAP EnhancementPackage Installation (Using SAPehpi)] or[…. (Using SAINT/JSPM)] depending onthe case

ABAP

SAP enhancement packageinstaller (SAPehpi) for asingle step update toenhancement package 4 forSAP ERP 6.0

(SAINT not supported)

Java

JSPM with single stepupdate to enhancementpackage 4 for SAP ERP 6.0

Easy Adoption – 32 bit

Installation of Technical Usages fromEHP4 for SAP ERP 6.0

SAP ERP 6.0 ABAP System Instanceson SAP EHP1 for SAP NW 7.0, and JavaSystem Instances remain on SAPNetWeaver 7.0

[Installation Guide – SAP EnhancementPackage Installation (Using SAPehpi)] or[…. (Using SAINT/JSPM)] depending onthe case

ABAP

SAINT for a two-step update(Memory Reasons) -enhancement package 3 forSAP ERP 6.0 first, thenenhancement package 4 forSAP ERP 6.0

Java

JSPM for a single stepupdate to enhancementpackage 4 for SAP ERP 6.0.

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


23 February, 2009

Case Activity [Guide fromhttp://service.sap.com/erp-inst]

Tool

Continuous Innovation – 64 bit

Installation of Technical Usages fromProduct Version EHP4 for SAP ERP 6.0/NW 7.01

ABAP and Java Product Instances onSAP EHP1 for SAP NW 7.0

[Installation Guide–SAP EnhancementPackage Installation (Using SAPehpi)]

ABAP

SAP enhancement packageinstaller (SAPehpi) for asingle step update toenhancement package 4 forSAP ERP 6.0.

(SAINT not supported)

Java

SAP enhancement packageinstaller (SAPehpi) withsingle step update toenhancement package 4 forSAP ERP 6.0.

Continuous Innovation – 32 bit

Installation of Technical Usages fromProduct Version EHP4 for SAP ERP 6.0/NW 7.01

ABAP and Java Product Instances onSAP enhancement package 1 for SAPNetWeaver 7.0

[Installation Guide – SAP EnhancementPackage 4 for SAP ERP 6.0 (UsingSAINT/JSPM)]

ABAP

SAINT for a two-step update(Memory Reasons) -enhancement package 3 forSAP ERP 6.0 first, thenenhancement package 4 forSAP ERP 6.0

Java

JSPM for a single stepupdate to enhancementpackage 4 for SAP ERP 6.0.

You use SAPehpi for the installation of ABAP software components in 64-bitsystem landscapes (normal case), and you employ SAINT in 32-bit systemlandscapes (exception). For the installation of ERP 6.0 EnhancementPackage 4 in particular, you must assign sufficient memory to the workprocesses (see SAP Note 1275873).

The descriptions in the current guide concentrate on the installation processfor the Easy Adoption path/ product version. We do not describe theinstallation process for the Continuous Innovation path/ product version indepth, as it works similar.

The new installation of upgrade of SAP ERP 6.0 is part of the Master andUpgrade Guides for SAP ERP 6.0 (see http://service.sap.com/erp-inst).

After SAP ERP 6.0 is available, you install the current enhancement packagefor SAP ERP 6.0. This documentation for the enhancement package is part ofthe current Master Guide.

2.3.1 New Installation of SAP ERP 6.0 withEnhancement Packages




24 February, 2009

GeneralBefore the current enhancement package 4 for SAP ERP 6.0 was available, the installationoption new installation of SAP ERP 6.0 including business functions from an enhancementpackage consisted of the following separate steps:

(Partial) installation of SAP ERP 6.0

In this step, you install SAP ERP 6.0 based on SAP NetWeaver 7.0.

(Partial) installation of the particular enhancement package, with activation of therequired business functions

In this step, you install the technical usages, which represent the functional scope ofthe chosen business functions.

From the tool perspective, you were using the installer tools SAPInst, Java Support PackageManager (JSPM), and the Maintenance Optimizer.

The installation process for the current enhancement package works as follows:

(Partial) installation of SAP ERP 6.0 with the enhancement package 1 for SAPNetWeaver 7.0

In this step, you install SAP ERP 6.0 based on the enhancement package 1 for SAPNetWeaver 7.0. In addition, you install the Technical Usage ABAP Technology forERP EHP4 from the corresponding EHP4 for SAP ERP 6.00 product instance.

(Partial) installation of the functional parts of the particular enhancement package,with activation of the required business functions

ABAP Technology for ERP EHP4 has a technical function. In order to use theenhancement package in productive business processes, you normally need furtherBusiness Functions and Technical Usages. These are installed in a second step asbefore, and as described in this guide.

Specific RequirementsThe following specific requirements apply as of the current enhancement package:

Using the previous SAPInst installation service, named Java Add-In in SAP ERP6.0/SAP NetWeaver 7.0, it was possible to add Java usage types such as EPC, orEP, to existing ABAP-only systems, provided, that you added AS Java at the sametime. This option of a Java Add-In installation is not available as of the currentenhancement package, so that it is not any longer possible, for example, to add EPCand EP together with AS Java to an ABAP-only system.

Dual stack systems include the usage types AS ABAP and AS Java in one systeminstance. It is possible to install product instances, based on the usage types ProcessIntegration, or Mobile (product instances SAP NW – Process Integration and SAPNW - Mobile Infrastructure) in a dual stack system.

It is possible to install standalone system instances for both AS ABAP and AS Javawith the same tools.

Documentation ReferencesFor more information about the installation of SAP ERP 6.0, review the Master Guide for SAPERP 6.0, published on SAP Service Marketplace at http://service.sap.com/erp-inst.

There you find the following information:

Example System Landscapes



25 February, 2009

Installation Sequences

Documentation and further information

For more information about a case, where SAP ERP 6.0 is installed in a system landscapetogether with other SAP Applications see The Enhancement Package in a SAP BusinessSuite System Landscape.

For information about the direct installation of the enhancement package 1 for SAPNetWeaver 7.0 using SAPInst, you find documentation on SAP Service Marketplace

http://service.sap.com/erp-inst Installation Guide – SAP EnhancementPackage 4 for ERP 6.0

http://service.sap.com/upgradenw70 Upgrade Guide SAP NetWeaver7.0 including SAP Enhancement Package 1.

2.3.2 Installation of Enhancement Packageswith the Upgrade to SAP ERP 6.0GeneralPrior to Support Release 3 of SAP ERP 6.0, it was necessary to install the particularenhancement package for SAP ERP in an existing system landscape for SAP ERP 6.0. Forcustomers who were upgrading from a lower release to SAP ERP 6.0, the following stepswere required:

Upgrade the relevant system instances to SAP ERP 6.0

(Partial) installation of the particular enhancement package, and activation of thenecessary business functions

As of Support Release 3 of SAP ERP 6.0, and as of enhancement package 3 for SAP ERP6.0, SAP has enhanced the following tools:

SAP Solution Manager Maintenance Optimizer

Installation tools SAPup and SAPjup

With these enhancements in place, it is now possible to install enhancement packages forSAP ERP directly in an upgrade. The new features simplify updates between enhancementpackages as well. The following 1:1 relation between application and enhancement packageexist:

The upgrade to SAP ERP 6.0/ SR 3 release (SAP Business Suite 2005) includes theenhancement package 3 for SAP ERP 6.0

The upgrade to the subsequent SAP Business Suite release includes the correspondingsubsequent enhancement package for SAP ERP 6.0 (i.e. SAP Business Suite 7 includesenhancement package 4 for SAP ERP 6.0),

InstallationThe modified installation strategy for enhancement packages is available to SAP ERP 6.0customers. The prerequisites for the use of the modified installation strategies are as follows:

The enhancement package lies at or above enhancement package 3 for SAP ERP6.0, and

You install at least the support package stack, which corresponds to SAP ERP 6.0Service Release 3.


http://service.sap.com/upgradenw70


26 February, 2009

Depending on the selection at run-time, the upgrade procedure for the current enhancementpackage installs packages from the product versions EHP 4 for SAP ERP 6.0, or EHP 4 forSAP ERP 6.0/ NW 7.01. The installation procedure uses the installation tools SAP Up andSAP Jup.

Documentation ReferencesFor more information about the resulting upgrade procedure to SAP ERP 6.0, review theUpgrade Master Guide for SAP ERP 6.0, published on SAP Service Marketplace athttp://service.sap.com/erp-inst.

Here you can find the following reference materials:

Example of a Target System Landscape for an enhancement package for SAP ERP

Overall Upgrade Sequence

Documentation and further information

Find documentation about the upgrade using SAPup and SAPjup in the SAP ServiceMarketplace

http://service.sap.com/erp-inst Upgrade Guide – SAP EnhancementPackage 4 for ERP 6.0

http://service.sap.com/upgradenw70 Upgrade Guide SAP NetWeaver7.0 including SAP Enhancement Package 1.

For a description of the SAP Solution Manager Maintenance Optimizer, see the SectionInstallation of Enhancement Packages in an existing SAP ERP 6.0 System Landscape.

For more information about the tool-related changes, review the following information:

SAP Notes 1093628 and 1122966,

Documentation for SAP NetWeaver 7.0 Maintenance Optimizer in the SAP Library, athttp://help.sap.com

For information about the documentation of the Solution Manager Maintenance Optimizer,refer to SAP Note 1155041.

2.3.3 Installation of Enhancement Packages inan existing SAP ERP 6.0 System LandscapeOverviewThe installation of enhancement packages consists of different steps. Solution ManagerMaintenance Optimizer (transaction DSWP) supports the installation. The use of this tool is aprerequisite for downloading support packages in general. For the enhancement packageinstallation SAP strongly recommends, that you use the Maintenance Optimizer.

During the enhancement package installation, the Maintenance Optimizer simplifies thedownload of all necessary software components and required support packages as well assupporting the creation of the import queue.

Prior enhancement packages use the following transactions, to install the downloadedsoftware components and support packages in the corresponding system instances:

ABAP based software components are installed with transaction SAINT (SAP Add-On Installation Tool)

The Java Support Package Manager (JSPM) is used to update Java softwarecomponents and to install Portal Content for the current enhancement package

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


http://service.sap.com/upgradenw70

http://help.sap.com/


27 February, 2009

Both the JSPM tool and the transaction SAINT are capable of using an XML document. Yougenerate the XML document with the Solution Manager Maintenance Optimizer.

As of enhancement package 4 for SAP ERP 6.0, a new enhancement package installation-tool (SAPehpi/ SAP Enhancement Package Installer) is available. This tool takes over therole of these previously separate installers. This recommended tool is used

When installing the enhancement package together with an enhancement packagefor SAP NetWeaver.

When updating the system instances from one enhancement package to another(Previously, these upgrade tasks had to be organized as separate activities).

Depending on the specific situation, a different set of installation tools are required:

The SAP enhancement package installation tool (SAPehpi), and the MaintenanceOptimizer (MOPz) is used, when installing the current enhancement package on SAPERP 6.0 system instances with or without prior enhancement packages installed.

In systems which are based on the SAP NetWeaver 7.0 usage type AS Java, youuse the JSPM installer tool together with the Solution Manager - MaintenanceOptimizer (Easy Adoption path)

You install product instances from SAP ERP 6.0 within an existing system instance on thecurrent enhancement package, by

Using the Additional Usage Type Deployment feature of the JSPM installer tool

After making sure that, you have installed the correct Support Package stack.

2.3.4 SAP Enhancement Package Installer andMaintenance Optimizer in DetailGeneralWith the current enhancement package, a new installation tool is available, which takes overthe role of the previous SAINT and JSPM installation tools. The guiding principles for usingthe new SAP enhancement package installer (SAPehpi) are as follows:

Use the new SAP enhancement package installer

Use a one-step procedure wherever possible.

Consider the following exceptions:

SAP enhancement package installer (SAPehpi) is not available on 32-bit platforms.

SAP enhancement package installer (SAPehpi)-Java is not available on SAPNetWeaver 7.0 (Easy Adoption installation option)

Due to memory reasons, the single-step update procedure is not possible for ABAPon 32-bit platforms.

In these exceptional cases, only, you use alternative installation tools (see Installation andUpgrade)

SAP Enhancement Package Installer: Functioning PrincipleFor the installation of enhancement packages on an ABAP system, the SAP EnhancementPackage Installer (SAPehpi) uses a system cloning and switch procedure. SAP has derivedthis procedure from a proven SAP upgrade technology, which works as follows:

It installs a copy of the system, a shadow system, in parallel with the original system.In this phase;


28 February, 2009

The shadow system is used to update the affected software componentsand to install the additional components

The original system is still in productive operation

At a certain point during downtime, the switch to the new system is made

After switching to the new system, any parts of the original system that are no longerrequired are deleted

The enhancement package installation on a Java system is deploy-based, and no shadowsystem or switch procedure is used.

The installation on a dual stack system consisting of AS ABAP and AS Java is highlysynchronized, in order to decrease the overall installation runtime and the downtime.

Use of the Solution Manager Maintenance OptimizerYou use the SAP Solution Manager Maintenance Optimizer as follows:

Phase 1 (Identification): Each business function is assigned to a Technical Usage,which groups all software component versions, which are required for that businessfunction. Proceed as follows, in order to identify all software components to beinstalled:

o Define the business function to be installed

o Identify and select the Technical Usage, which include the softwarecomponent versions, which are required for that business function

Phase 2 (Installation): Using a guided procedure, you

o Create a new maintenance transaction for updating the relevant systems withthe enhancement package software-components. You need to select allsystem instances which are affected by the enhancement package

o Select the Technical Usages, which include the software components thatyou want to install in your system instances. The Solution ManagerMaintenance Optimizer calculates all necessary support packages and newsoftware component versions that are required to install the selectedTechnical Usages

o In the final step, the Solution Manager Maintenance Optimizer creates anXML document. This document is later read by the installation tools andcreates a valid import queue

Documentation ReferencesFor more information about the SAP Enhancement Package Installer, see the InstallationGuide - SAP Enhancement Package Installation for your operating system, database andtechnology. You find the guide in the SAP Service Marketplace athttp://service.sap.com/erp-inst -> SAP ERP 6.0 -> SAP enhancement packagesfor SAP ERP 6.0 -> SAP enhancement package 4 for SAP ERP 6.0 -> EnhancementPackage Installation on Existing SAP Systems

For more information about the conventional Installation tools, see the SAP Libraryhelp.sap.com -> SAP NetWeaver -> SAP NetWeaver 7.0.

For the SAP Add-On Installation Tool navigate to SAP NetWeaver by Key Capability-> Solution Life Cycle Management by Key Capability -> Software Life CycleManagement -> Software Maintenance -> Add-On Installation Tool.



29 February, 2009

For the Java Support Package Tool navigate to SAP NetWeaver by Key Capability ->Solution Life Cycle Management by Key Capability -> Software Life CycleManagement -> Software Maintenance Java Support Package Manager.

For more information about the Solution Manager Maintenance Optimizer, see the following:

SAP Library, at help.sap.com, under SAP Solution Manager ChangeManagement Maintenance Optimizer

SAP Service Marketplace, at http://service.sap.com/solutionmanagerMedia Library Documentation

SAP Service Marketplace at http://service.sap.com/solman-mopz

Normally, you use the SAPehpi to update an existing system on SAP NetWeaver 7.0. Indefined exceptional cases, you need to use the former transactions SAINT/JSPM (seeInstallation and Upgrade). You find additional documentation on SAP Service Marketplace asfollows:

http://service.sap.com/installnw70 Installation Guide – SAPEnhancement Package Installation)

http://service.sap.com/erp-inst Installation Guide – SAPEnhancement Package 4 for SAP ERP 6.0 (Using SAINT/JSPM)

http://service.sap.com/erp-inst Installation Guide–SAP EnhancementPackage Installation (Using SAPehpi)

For additional information about SAPehpi, refer to SAP Note 1175848 (or successor notes).

http://service.sap.com/solutionmanager

http://service.sap.com/solman-mopz

http://service.sap.com/installnw70



3 Software Units, Systems and Installation

30 February, 2009

3 Software Units, Systems andInstallationOverviewThis section concentrates on the following information:

Software components of the current enhancement package/product versions

System landscape requirements and Software Component Matrix

Installation methodologies and generic installation sequences

The information helps the system administrator to understand the software architecture forthe current enhancement package, and it enables him to plan the installation.

3.1 Software Units of SAP EnhancementPackage 4 for SAP ERP 6.0OverviewThe main software component types of an enhancement package are as follows:

ABAP software components are installed in system instances based on the SAPNetWeaver usage type AS ABAP

Java software components are installed in system instances based on the SAPNetWeaver usage type AS Java

Additional software components, which are generally installed in front-end systems

Product Versions for the Current Enhancement PackageYou install the enhancement package in different system landscape types. The followingproduct versions of the current enhancement package support this ability:

EHP 4 for SAP ERP 6.0 [Easy Adoption]

EHP 4 for SAP ERP 6.0/ NW 7.01 [Continuous Innovation]

Both product versions are identical with the following exceptions:

Both versions update the usage type AS ABAP to the enhancement package 1 forSAP NetWeaver. The systems on AS Java are handled differently as follows:

o When installing the product version for the Easy Adoption path, the systemson AS Java remain on the SAP NetWeaver 7.0 kernel

o With the installation of the product version for the Continuous Innovationpath, you update the systems on AS Java with the enhancement package 1for SAP NetWeaver 7.0

Newer versions of certain SAP ERP 6.0 - Java product instances are part of theContinuous Innovation product version, but not the Easy Adoption product version.

As these product versions are almost identical, the following sections concentrate on theProduct Version EHP 4 for SAP ERP 6.0 [Easy Adoption].

Software Components of EHP 4 for SAP ERP 6.0 [Easy Adoption]

Figure 1: Software-Components of Product Version EHP 4 for SAP ERP 6.0


31 February, 2009


32 February, 2009

The figure above provides the complete overview of all software components of productversion EHP 4 for SAP ERP 6.0. You install the software components in SAP ERP 6.0system instances, which are already available (already installed, or in upgrade). Thesesystem instances need to be at least available on the minimum service package level.

Installation ProcessYou install enhancement packages selectively. The installation scope depends on thespecific business function chosen. The installation exchanges those new or changedsoftware components in your customer system landscape that correspond to the businessfunction. The tools use the following entities and groupings to allow for selective installation:

System landscapes consisting of one or many general product instances

Technical usages group all software components, which are required for a specificbusiness function, independently of the system instance. The sub groupings are asfollows:

o ABAP Product Instances are installed together on one general productinstance, which is based on SAP NetWeaver usage type AS ABAP

o Content Instances are installed together on a general product instance,which is either based on SAP NetWeaver usage type AS ABAP or on theusage type AS Java

The following sections document the different parts of the current enhancement package.See Solution-Wide Topics for more information about the software architecture.

You install enhancement packages in available SAP ERP 6.0 systeminstances, but you might currently use parts of SAP ERP 6.0 only. Then notall system instances might be available, which you intend to enhance with theenhancement package. SAP recommends that you verify your systemlandscape capabilities before you decide to install the software componentsfor a particular Business Function.

3.1.1 Technical UsagesOverviewOften, business processes require more than one general product instance of SAP ERP 6.0.Thus, you install the software component versions for a business function on different generalproduct instances. In order to support this need, business functions are associated withTechnical Usages. Technical Usages reference all software component versions and productinstances, which you need to consider for installation for that specific business function.

SAP enhancement package 4 for SAP ERP 6.0 – Technical UsagesThe following table shows the Technical Usages for the current enhancement package. Thetable includes information about

ABAP Product Instances included

General product instances included

The product instance or the particular product version required in order to install theparticular ABAP or general product instance

Consider the following:


33 February, 2009

For installation tool related reasons, Technical Usages might exist, which arealternatives to a Technical Usage listed.

Technical Usages are linked to Business Functions. Enterprise Bundles support theservice enablement of SAP ERP. These Enterprise Service Bundles rely on similarTechnical Usages, but introduce a separate grouping.

Table 2: Technical Usages and Related Product Instances

Technical Usage General or ABAP ProductInstance included

Based on SAP ERP6.0 Product Instance

Financial Supply Chain Mgmt SAP ECC ServerBiller Direct – FSCM

SAP FSCM - Biller Direct SAP FSCM - BillerDirect

Leasing/Contract A/R & A/P SAP ECC ServerBiller Direct - Leasing & CA

SAP FSCM - Biller Direct SAP FSCM - BillerDirect

Media SAP ECC ServerBiller Direct - MediaSAP FSCM - Biller Direct SAP FSCM - Biller

DirectSAP FSCM - Biller Direct SAP FSCM - Biller

DirectBiller Direct - UT

Utilities/Waste&Recycl./Telco SAP ECC ServerCatch Weight Management Catch Weight Management SAP ECC Server

Central Applications SAP ECC ServerCentral Appl - EAM, PSM, SDPortal Content based on Portal

Content, requires SAPNW - EP Core

Central Applications Central Applications SAP ECC ServerCentral Applications SAP ECC ServerCentral Applications - FSLXI Content based on XI Content,

requires SAP NW -Process Integration

Defense Defense SAP ECC ServerDefense & Public Security Defense & Public Security SAP ECC ServerDiscrete Ind.& Mill Products Discrete Ind. & Mill Products SAP ECC Server

ERecruiting SAP ECC ServerERecruiting on ECC ServerSAP E-Recruiting SAP E-Recruiting

ESA ECC-SE SAP ESA ECC-SE SAP ECC ServerFinancial Services Financial Services SAP ECC Server

Financial Supply Chain Mgmt SAP ECC ServerFinancial Supply Chain Mgmt

Portal Content based on PortalContent, requires SAPNW - EP Core

Financials Leasing/Contract A/R & A/P SAP ECC ServerXI Content based on XI Content,


Financials-Contr.Acc.&Leasing

Leasing/Contract A/R & A/P SAP ECC Server


34 February, 2009



Global Trade Global Trade SAP ECC ServerHuman Capital Management SAP ECC ServerHCM - Administrative ServicesPortal Content based on Portal


Learning Solution SAP ECC ServerPortal Content based on Portal


SAP Learning Sol-Client (Auth) SAP Learning Sol-Client (Auth)

SAP Learning Sol-Client (Lern) SAP Learning Sol-Client (Lern)

HCM - Learning Solution

SAP Learning Sol-FrontendCP

SAP Learning Sol-Frontend CP

XI Content based on XI Content,requires SAP NW -Process Integration

HCM - Services

Human Capital Management SAP ECC ServerXI Content based on XI Content,


Human Capital Management SAP ECC Server

HCM - Travel Management


Human Capital Management SAP ECC ServerPortal Content Self Services based on Portal


HCM Self Services

SAP XSS (Self Services) SAP XSS (SelfServices)

Hospital Hospital SAP ECC ServerHuman Capital Management Human Capital Management SAP ECC Server

Insurance Insurance SAP ECC ServerIntegration Package for SWIFT SAP Integration for SWIFT SAP NW - Process

IntegrationKayak successor Kayak successor SAP ECC ServerMedia Media SAP ECC ServerOil & Gas Oil & Gas SAP ECC ServerOil & Gas with Utilities Oil & Gas with Utilities SAP ECC Server

PLM Core SAP ECC ServerPLM CoreSAP Product Visualization Frontend Component

Portal Content Portal Content based on PortalContent, requires SAPNW - EP Core


35 February, 2009



Portal Content Common Portal Content Common based on PortalContent, requires SAPNW - EP Core

Portal Content Self Services Portal Content Self Services based on PortalContent, requires SAPNW - EP Core



Public Sector Accounting

Public Sector Accounting SAP ECC ServerRetail Retail SAP ECC Server


Retail SAP ECC Server

Retail - Store

SAP Retail Store Applications SAP NW - Applic.Server Java

SAP Easy DMS SAP Easy DocumentManagement

Frontend Client

SAP ECC Server VPacksuccessor

SAP ECC Server VPacksuccessor

SAP ECC Server

SAP Frontend Business Client SAP Frontend Business Client Frontend Client

SAP Integration for BCONS SAP Integration for BCONS SAP NW - ProcessIntegration

SAP Learning Sol-FrontendABAP


SAP Learning Sol-Frontend ABAP


SEM - CCD Enhancements

Strategic Enterprise Mgmt SAP ECC ServerSAP SEM SAP SEMStrategic Enterprise MgmtStrategic Enterprise Mgmt SAP ECC ServerXI Content based on XI Content,


Telco - Enhanced CA

Utilities/Waste&Recycl./Telco SAP ECC ServerPortal Content based on Portal


Telco - NLM Roles

Utilities/Waste&Recycl./Telco SAP ECC ServerUtilities/Waste&Recycl./Telco Utilities/Waste&Recycl./Telco SAP ECC Server

SAP Utility Customer E-Service

SAP NW - Applic.Server Java

Utility Customer E-Service

Utilities/Waste&Recycl./Telco SAP ECC Server


36 February, 2009



XI Content XI Content based on XI Content,requires SAP NW -Process Integration


XI Content ESR 710

ESR Content Requires SAPNetWeaver 7.10 - SAPNW - ProcessIntegration

ABAP Technology for ERPEHP4

ABAP Technology for ERPEHP4

SAP ECC Server

EAM config control EAM config control SAP ECC ServerSRM one-client scenario SRM Server SAP ECC Server

Documentation ReferencesFor the information about the latest version about the assignment of software components totechnical usages, refer to the following SAP Notes:

SAP enhancement package 2 for SAP ERP 6.0 - required SWC: SAP Note 1052470



For more information about Enterprise Services Bundles and the required Technical Usagesand Business Functions, see SAP Note 1224284.

3.1.2 ABAP Product InstancesOverviewABAP Product Instances act as a bundle for installable units. They group the ABAP softwarecomponent versions for a specific Technical Usage. You must install ABAP ProductInstances in system instances on the usage type AS ABAP (normally SAP ECC Server).

ABAP Product Instances for SAP enhancement package 4 for SAP ERP6.0The following table lists the ABAP Product Instances of the current enhancement package.The table includes information about the associated software components. The followinginformation is included:

Some software components and software component versions are part of differentABAP Product Instances

Some software components were first shipped with predecessor enhancementpackage and are now repacked with the current enhancement package(accumulation principle)

As identical software components are part of different ABAP product instances,alternative realizations are possible with the same result. Software components froman earlier enhancement package are repacked, in order to support the accumulationparadigm explained previously


37 February, 2009

In addition, each ABAP product instance includes a product instance, which makes sure thatthe installation process updates the usage type AS ABAP to the enhancement package 1 forSAP NetWeaver 7.0 (not shown in the table). This entity is required in order to make the SAPNetWeaver release level available in the systems, as it is required for the currentenhancement package.

Table 3: ABAP Product Instances of the current enhancement package

ABAP Product Instance Introducedwith SAPenhancementpackage <n>for SAP ERP

Software Component Version

SAP WEB UIF 7.0ABAP Technology for ERPEHP4

4

SAP_BS_FOUNDATION 701

IS-CWM 604

FINBASIS 604

SAP APPL 6.04

SAP WEB UIF 7.0


Catch Weight Management 2

SEM-BW 604

EA-APPL 604

SAP APPL 6.04

SAP WEB UIF 7.0

Central Applications 2


EA-DFPS 604

ECC-DIMP 604

EA-APPL 604

SAP APPL 6.04

SAP WEB UIF 7.0

Defense 4


EA-DFPS 604

EA-APPL 604

SAP APPL 6.04

SAP WEB UIF 7.0

Defense & Public Security 3


ECC-DIMP 604

EA-APPL 604

SAP APPL 6.04

Discrete Ind. & Mill Products 2

SAP WEB UIF 7.0


38 February, 2009




ERECRUIT 604

SAP WEB UIF 7.0

ERecruiting 3


EA-FINSERV 604

SAP APPL 6.04

SAP WEB UIF 7.0

Financial Services 2


FINBASIS 604

SEM-BW 604

SAP APPL 6.04

SAP WEB UIF 7.0

Financial Supply Chain Mgmt 2


EA-GLTRADE 604

SAP APPL 6.04

SAP WEB UIF 7.0

Global Trade 2


IS-H 604

SAP APPL 6.04

SAP WEB UIF 7.0

Hospital 2


EA-HR 604

SAP HR 6.04

SAP WEB UIF 7.0

Human Capital Management 2


INSURANCE 604

FI-CA 604

SAP APPL 6.04

SAP WEB UIF 7.0

Insurance 2


LSOFE 604 (FRONT END)Learning Solution 2

EA-HR 604


39 February, 2009



SAP HR 6.04

SAP WEB UIF 7.0


EA-APPL 604

FI-CA 604

FI-CAX 604

SAP APPL 6.04

SAP WEB UIF 7.0

Leasing/Contract A/R & A/P 2


IS-M 604

EA-APPL 604

FI-CA 604

SAP APPL 6.04

SAP WEB UIF 7.0

Media 2


IS-OIL 604

IS-PRA 604

SAP APPL 6.04

SAP WEB UIF 7.0

Oil & Gas 2


IS-OIL 604

IS-UT 604

EA-APPL 604

FI-CA 604

SAP APPL 6.04

Oil & Gas with Utilities 4


PLM WUI 7.0

EA-IPPE 404

SAP APPL 6.04

SAP WEB UIF 7.0

PLM Core 4


Public Sector Accounting 2 IS-PS-CA 604


40 February, 2009



EA-PS 604

FI-CA 604

SAP APPL 6.04

SAP WEB UIF 7.0


EA-RETAIL 604

SAP APPL 6.04

SAP WEB UIF 7.0

Retail 2


SEM-BW 604

FINBASIS 604

SAP WEB UIF 7.0

Strategic Enterprise Mgmt 2


FI-CA 604

IS-UT 604

EA-APPL 604

SAP APPL 6.04

SAP WEB UIF 7.0

Utilities/Waste&Recycl./Telco 2


KAYAK 603

SAP_APPL 604

SAP WEB UIF 7.0

Kayak Successor 3

SAP_BS_FOUNDATION 701 (SAPBusiness Suite Foundation 7.01)

EA_IPPE 404

EA-APPL 604

SAP_APPL 604

SAP WEB UIF 7.0

EAM config control 4


SAP AP 7.00

SAP WEB UIF 7.0

SRM Server 4



41 February, 2009



SRM Server 7.0

SRM_EXT_FUNC 7.0

Installation Considerations From a technical perspective, ABAP Product Instances require a system instance

based on the SAP NetWeaver usage type AS ABAP. With the enhancementpackage, you use the system instance with the SAP ERP 6.0 product instance SAPECC Server as installation target.

As of enhancement package 4 for SAP ERP, the installation process updates theSAP NetWeaver usage type AS ABAP of SAP ECC Server to a higher release levelfor SAP NetWeaver. From a technical perspective, the tools install the enhancementpackage 1 for SAP NetWeaver 7.0.

Dependencies between software component versions may exist, or requirementsmight exist with respect to the minimum support level, which you need to install witha particular software component version. When dependencies occur, it is necessaryto install more than one ABAP Product Instance.

Documentation ReferencesFor information about the required software component versions, refer to the following SAPNotes on SAP Service Marketplace at http://service.sap.com/notes:

Enhancement package 2 for SAP ERP 6.0 - SAP Note 1052470



SAP has split or reorganized several software components from one to the nextenhancement package, leading to specific installation requirements. For the followingsoftware component versions, refer to separate SAP Notes for more information aboutspecific installation prerequisites:

IS-PS-CA 602 or INSURANCE 602: SAP Note 1052470 and SAP Note 1045303.

IS-OIL-PRA (with enhancement package 4 for SAP ERP 6.0 the software component IS-OIL has been split into IS-OIL and IS-PRA), see SAP Note 1175205.

For more information about the ABAP product instance PLM Core, see the Master Guide forSAP PLM Web User Interface on SAP Service Marketplace athttp://service.sap.com/instguides SAP Business Suite Applications SAPPLM.

As by the Master Guide for SAP ERP 6.0, you have different options to install SAP SRM asan add-on to SAP ERP. The current enhancement package includes version 7.0 of thesoftware component SRM add-on. This software component version consists of the softwarecomponents SRM_SERVER 700 and SRM_EXT 700. You install these components insystem instances with usage type AS ABAP, as described in SAP Note 1172901.

3.1.3 General Product InstancesOverview

http://service.sap.com/notes:



42 February, 2009

A general product instance represents the smallest element for designing systemlandscapes. General product instances include all software component versions, which youneed to install on a single logical system or server.

SAP has designed the enhancement packages for SAP ERP 6.0 as Add-Ons to SAP ERP6.0. For this reason, you need to install all product instances and software components of aparticular enhancement package on a SAP ERP 6.0 general product instance. Anenhancement package not only exchanges software components in existing systems. Theycan also include new versions of general product instances, or completely new such entities.

Product Version EHP 4 for SAP ERP 6.0The current section describes each general product instance of the current enhancementpackage in detail. The following table lists these product instances along with informationabout related and required SAP ERP 6.0 product instances. The information about versionsin previous enhancement packages is important for the upgrade from a lower to a higherenhancement package.

Table 4: Product Instances with the Current SAP Enhancement Package for SAP ERP(Product Version EHP4 FOR SAP ERP 6.0)

Product VersionEHP4 FOR SAP ERP6.0 General Product

Instance

Full Name Predecessor Product Version andProduct Instance

SAP ERP 6.0 – SAP E-RecruitingSAP E-Recruiting SAP E-RecruitingSAP ENH PACK 3 for SAP ERP 6.0 –SAP E-RecruitingSAP ERP ENHANCE PACKAGE 2005.1– SAP ECC Server VPack successor(new)

SAP ERP ENHANCE PACKAGE 2005.2– SAP ECC Server VPack successor

SAP ECC ServerVPack successor

SAP ECC ServerValue Packsuccessor

SAP ENH PACK 3 for SAP ERP 6.0 –SAP ECC Server VPack successorSAP ERP ENHANCE PACKAGE 2005.1– SAP ESA ECC-SE (new)SAP ERP ENHANCE PACKAGE 2005.2– SAP ESA ECC-SE

SAP ESA ECC-SE SAP ESA ECC-SE

SAP ENH PACK 3 for SAP ERP 6.0 –SAP ESA ECC-SESAP ERP ENHANCE PACKAGE 2005.2- SAP Frontend Business Client (new)

SAP FrontendBusiness Client

SAP FrontendBusiness Client

SAP ENH PACK 3 for SAP ERP 6.0 –SAP Frontend Business ClientSAP ERP 6.0 - SAP FSCM - Biller DirectSAP FSCM - Biller

DirectSAP FinancialSupply ChainManagement (SAPFSCM) - Biller Direct SAP ENH PACK 3 for SAP ERP 6.0 –

SAP FSCM - Biller DirectSAP ERP ENHANCE PACKAGE 2005.2- SAP Integration for SWIFT

SAP Integration forSWIFT

SAP Integration forSWIFT

SAP ENH PACK 3 for SAP ERP 6.0 –SAP Integration for SWIFT


43 February, 2009

Product VersionEHP4 FOR SAP ERP6.0 General Product

Instance


SAP ERP 6.0 – SAP Learning Sol-Client(Auth)

SAP Learning Sol-Client (Auth)

SAP LearningSolution - ClientAuthoringEnvironment

SAP ENH PACK 3 for SAP ERP 6.0 –SAP Learning Sol-Client (Auth)SAP ERP 6.0 – SAP Learning Sol-Client(Lern)

SAP Learning Sol-Client (Lern)

SAP LearningSolution - ClientOffline Player SAP ENH PACK 3 for SAP ERP 6.0 –

SAP Learning Sol-Client (Lern)SAP ERP 6.0 - SAP Learning Sol-Frontend ABAP



SAP ENH PACK 3 for SAP ERP 6.0 –SAP Learning Sol-Frontend ABAPSAP ERP 6.0 – SAP Learning Sol-Frontend CP

SAP Learning Sol-Frontend CP

SAP LearningSolution - FrontendContent Player SAP ENH PACK 3 for SAP ERP 6.0 –

SAP Learning Sol-Frontend CPSAP ERP ENHANCE PACKAGE 2005.2- SAP Retail Store Applications (new)

SAP Retail StoreApplications

SAP Retail StoreApplications

SAP ENH PACK 3 for SAP ERP 6.0 –SAP Retail Store ApplicationsSAP ERP 6.0 - SAP FSCM - Biller DirectSAP Utility Customer

E-ServiceSAP Utility CustomerE-Services

SAP ENH PACK 3 for SAP ERP 6.0 –SAP Utility Customer E-ServiceSAP ERP 6.0 – SAP SEMSAP SEM SAP Strategic

EnterpriseManagement (SAPSEM) SAP ENH PACK 3 for SAP ERP 6.0 –

SAP SEMSAP ERP 6.0 – SAP XSS (Self Services)SAP XSS (Self

Services)SAP XSS (SelfServices)

SAP ENH PACK 3 for SAP ERP 6.0 –SAP XSS (Self Services)

SAP Easy DocumentManagement

SAP Easy DocumentManagement

SAP ERP 6.0 – SAP Easy DocumentManagement

SAP Integration forBCONS

SAP Integration forBusinessConsolidation

New

SAP ProductVisualization

SAP ProductVisualization

New

Kayak Successor Kayak Successor SAP ENH PACK 3 for SAP ERP 6.0 –Kayak Successor

Product Version EHP 4 for SAP ERP 6.0/ NW 7.01It is possible to install the enhancement package with or without SAP enhancement packagesfor SAP NetWeaver (Easy Adoption versus Continuous Innovation path). The followingdesign supports this possibility:


44 February, 2009

EHP4 for SAP ERP 6.0/ NW 7.01 includes the same product instances as EHP4 forSAP ERP 6.0.

For technical reasons product version EHP4 FOR SAP ERP 6.0/ NW 7.01 includesproduct instances from SAP ERP 6.0, which are not part of product version EHP4FOR SAP ERP 6.0 (these differ in the Java part).

The following table lists the product instances, which are deviations to the general rule. Theinstallation is working as with other product instances, described in detail.

Product VersionEHP4 FOR SAP ERP6.0/ NW 7.01 General

Product Instance


SAP ERP 6.0 – BI JavaBI-Java Java Content BI-Java Based on the SAP enhancement

package 1 for SAP NetWeaver 7.0 –version of BI JavaSAP ERP 6.0 – SAP XECOSAP XECO SAP XECO

Based on the SAP enhancementpackage 1 for SAP NetWeaver 7.0 –version of AS Java

Other Product InstancesBeginning with SAP Business Suite 7 (SAP enhancement package 4 for SAP ERP 6.0), SAPERP is leveraging Embedded Search (SAP NetWeaver scenario variant Enabling EmbeddedSearch). Embedded Search enables SAP ERP to search in a unified way inside all itsstructured data. It features rich out-of-the-box business content as well as the tools to createand modify search models. The capabilities of Embedded Search are limited to indexing andsearching within a single SAP system (single SID).

The use of Embedded Search needs SAP GUI, systems on the usage types AS ABAP, and asystem with TREX. It is mandatory to use TREX 7.1 for Embedded Search, and to install theenhancement package 1 for SAP NetWeaver 7.0 in the AS ABAP system.

SAP ERP 6.0 - SAP NW - Search and Classification includes softwarecomponent version TREX 7.0. If the operating system of your systemlandscape permits it, you can use TREX 7.1 within a SAP ERP systemlandscape. Make sure to check, if your system landscape meets therequirements, before you use Embedded Search.

To enable Embedded Search on the AS ABAP system, we recommend thatyou select and install an ABAP Product Instance, which already includes ausage type AS ABAP on version enhancement package 1 for SAPNetWeaver 7.0.

Documentation ReferencesFor more information about the different installation and upgrade topics, see the followinginformation sources:

For information about product instances of SAP ERP 6.0 and the product concept ingeneral, see the Master Guide SAP ERP 6.0.

For information about the upgrade to SAP ERP 6.0, refer to the Upgrade MasterGuide SAP ERP 6.0.


45 February, 2009

For installation–instructions, see the available component installation guides.

You can find all these guides at the SAP Service Marketplace athttp://service.sap.com/erp-inst.

For more information about the installation of SAP NW - Search and Classification, see theInstallation & Implementation Documentation Center SAP NetWeaver Search andClassification (TREX) on SAP Service Marketplace athttp://service.sap.com\installNW70.

For more information on Embedded Search, see the following information sources:

Master Guide for SAP NetWeaver 7.0 on the SAP Service Marketplace athttp://service.sap.com/installnw70,

SAP Note 1164979 (SAP NetWeaver 7.0 Embedded Search) and referenced SAPNotes.

3.1.3.1 Product Instance: SAP E-RecruitingOverviewYou use the product instance SAP E-Recruiting with different SAP ERP processes but mainlyin the area of the key functional area Human Capital Management. Examples are the processManaging External Recruiting, the Role-Based Work Center Talent Development Specialist,or the new Managing Succession and Talent Development.

Software Component VersionThe product instance SAP E-Recruiting includes software component versions ERECRUIT604, SAP WEB UIF 7.0, and SAP_BS_FOUNDATION 701. SAP E-Recruiting closely relatesto the ABAP product instance E-Recruiting, mentioned above.

Technical PrerequisitesSAP has based the product instance SAP E-Recruiting on SAP ERP 6.0 – SAP E-Recruiting.The ABAP product instance E-Recruiting requires a SAP ERP 6.0 – SAP ECC Server. Bothproduct instances include identical functions, which you install in different system instances.

The installation of SAP E-Recruiting requires a system instance based on enhancementpackage 1 for SAP NetWeaver 7.0 – usage type AS ABAP, and includes the correspondingsoftware components. When you install SAP E-Recruiting, the installation processes andtools make this enhancement package available in the system instances for SAP E-Recruiting/SAP ECC Server.

Documentation ReferencesFor more information on the required software components, software componentversions and combinations with older releases, see SAP Service Marketplace athttp://service.sap.com/scl Scenario and Process Component list.

For interfaces with other processes within Human Capital Management, see SAPNote 824757.

For the different options in regards to Product Instance SAP NW - Search andClassification, see the following SAP Notes

o 568853 (Supported TREX versions in SAP E-Recruiting),

o 1273780 (Talent Management and Talent Development - TREX 7.10)

For information on installation, see SAP Library, at help.sap.com, under SAP ERPCentral Component Business Packages (Portal Content) Business Package for

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

http://service.sap.com/

http://service.sap.com/installnw70



46 February, 2009

Talent Development Specialist, and the information on SAP Service Marketplace athttp://service.sap.com/erp-ehp.

3.1.3.2 Product Instance: SAP ECC Server VPackSuccessorOverviewWith the first enhancement packages for SAP ERP, the deliveries for the SAP ECC Serverproduct instance were part of the add-on product instance SAP ECC VPack. Starting withenhancement package 2 for SAP ERP 6.0, SAP has separated this product instance into thesmaller ABAP Product Instances previously discussed.

The installation replaces the former add-on package SAP ECC VPack during the installationprocess and updates the software components of the new ABAP Product Instances to ahigher version. The particular SAP ECC VPack product instance is necessary whenupgrading from an enhancement package prior to enhancement package 2 for SAP ERP 6.0to a higher enhancement package version.

Software Component VersionProduct instance EHP4 FOR SAP ERP 6.0 - SAP ECC Server VPack successor contains thefollowing software components:

EA-APPL 604

EA-PS 604

EA-RETAIL 604

ECC-VPACK 603

SAP APPL 6.04

SAP WEB UIF 7.0


The upgrade process uses this product instance for internal reason. It has no permanentbusiness related relevance.

Technical PrerequisitesThe installation of SAP ECC Server VPack successor has the following characteristics:

It requires a system instance on usage type AS ABAP, which is updated to theenhancement package 1 for SAP NetWeaver 7.0

It is installed on a system instance with usage type AS ABAP, which includes theSAP ERP Server VPack product instance of product version ERP EnhancementPackage 2005.1 (enhancement package 1 for SAP ERP). In these systeminstances, the installation process updates the AS ABAP usage type to enhancementpackage 1 for SAP NetWeaver 7.0.

3.1.3.3 Product Instance: SAP ESA ECC - SEOverviewSAP ERP is service-enabled by means of service interfaces and services. In earlierenhancement packages for SAP ERP 6.0, SAP ERP has used the product instance SAPESA ECC – SE as a container for all these services. SAP ERP was service enabled bymeans of installing product instance SAP ESA ECC – SE in addition to product instance SAP



47 February, 2009

ECC Server. With the current enhancement package, SAP has moved few service enablinginterfaces from SAP ESA ECC-SE to different other software components or productinstances of product instance SAP EHP PACK 4 FOR SAP ERP 6.0.

The service interfaces are available with the installation of one or more of these softwarecomponents, or product instances.

Software Component VersionThe product instance SAP ESA ECC - SE includes the following software componentversions:

ESA ECC-SE 604 (Service enablement SAP ECC Server)

SAP WEB UIF 7.0 (SAP Web User Interface Framework 7.0)


The product instance is necessary in order to service enable systems, which employ productinstance SAP ECC Server. SAP ESA ECC – SE also includes the update of the usage typeABAP to enhancement package 1 for SAP NetWeaver 7.0.

Technical PrerequisitesYou install SAP ESA ECC – SE, SAP WEB UIF 7.0, and SAP_BS_FOUNDATION 701 asAdd-Ons to product instance SAP ECC Server. With the current enhancement package, theinstallation of SAP ESA ECC – SE requires a system instance in which the usage type ASABAP includes the enhancement package 1 for SAP NetWeaver 7.0. SAP ESA ECC-SEincludes the software components, which are required to meet this need.

Installation ConsiderationsThe service interfaces of SAP ECC Server and of product instance SAP ESA ECC – SE needto match the consuming system instances. It is therefore also necessary to install thematching content from XI Content (here XI CONTENT ESA ECC-SE 604), which is based onProduct Instance SAP ERP 6.0 – SAP NW Process Integration.

As an alternative, it is possible to use product instance ESR CONTENT with a systeminstance on SAP NetWeaver 7.10.

Normally you use the Maintenance Optimizer of SAP Solution Manager to download theenhancement package and the available Support Package stack to your system. A manualprocedure is available which permits you do directly load it from the Media DVD.

Documentation ReferencesFor more information about the Service-Oriented Architecture (SOA), see Solution-WideTopics.

For more information about installing or upgrading SAP ESA ECC-SE product instances, seethe following SAP Notes:

1150349 ECC-SE 604 Add-On Installation

1150350 Upgrade to SAP ECC 600 with Add-On ECC-SE 604

For more information about Enabling Enterprise Services (SOA), see the following:

SAP Library, at help.sap.com, under SAP NetWeaver 7.0 Administrator’s Guide Technical Operations Manual for SAP NetWeaver Enabling Enterprise

Services.

SAP Service Marketplace at http://service.sap.com/instguidesnw70Installation Technology Consultant's Guide.



48 February, 2009

The SAP Developer Network (SAP SDN) athttps://wiki.sdn.sap.com/wiki/x/LQ0 (registration required).

3.1.3.4 Product Instance: SAP Frontend BusinessClientOverviewThe SAP NetWeaver Business Client (NWBC) is part of product instance EHP4 FOR SAPERP 6.0 – SAP Frontend Business Client. It represents a desktop-based SAP integrationplatform that provides end users with a seamless integration of classic SAP GUI-basedtransactions and new applications developed in Web Dynpro. You can integrate existingbrowser-based SAP applications also.

Product instance SAP Frontend Business Client (SAP NetWeaver Business Client) includesthe software component versions SAP GUI FOR WINDOWS 7.10 CORE and NETWEAVERBUSINESS CLIENT 7.10 for the SAP NetWeaver Business Client (NWBC) function. SAP hasfirst shipped this product instance with enhancement package 2 for SAP ERP 6.0. It is thusnot available in systems for product version SAP ERP 6.0.

FeaturesThe product instance includes user interface (UI) software running on the desktop thatcommunicates via HTTP(s) to a server in order to display application interfaces. The softwarerenders interfaces in such a way that the user can start the required application in a verysimple way.

The main components of the Business Client UI are the frame and the canvas:

Frame: The frame contains standard menu entries in the upper area, and miniatureimages of open sessions and transactions that enable simple navigation betweenscreens (session tab area). The left part of the screen contains the role-basedfunctions for the user (home area).

Canvas: The software uses the canvas or application area to display the activescreen or transaction where the user is working in. The canvas represents the nativetechnology in which the source application created its screens. If, for example, aspecific transaction is available in HTML, the user sees the Business Client frame inflash and the canvas in HTML. It is possible to present practically all standard UItechnologies on a canvas.

Technical Prerequisites Operating system

o The NWBC is currently only available for Windows platforms

Hardware

o To use the NWBC without layered windows functionality, the hardwareprerequisites are the same as for the SAP GUI. For more information, seethe SAP Frontend documentation on SAP Service Marketplace athttp://service.sap.com/instguidesnw

o SAP recommends a minimum screen size of 800x600, though your screenshould preferably be larger. SAP advises against using VGA monitoring

Rendering quality can be impaired when using NetMeeting or on terminalservers.

https://wiki.sdn.sap.com/wiki/x/LQ0



49 February, 2009

Server

o You have installed the application server for ABAP (AS ABAP) or Java (AS-Java) for SAP NetWeaver 7.0 SPS12 or higher. For more information, seeSAP Service Marketplace athttp://service.sap.com/instguidesnw70 Installation

o For more information about the required system landscape, see the masterguide for SAP NetWeaver 7.0 at SAP Service Marketplacehttp://service.sap.com/instguidesnw70

o You have installed SAP GUI 7.10

Installation ConsiderationsFor business applications, the SAP NetWeaver Business Client can be an alternative front-end to the SAP NetWeaver Portal client. It offers role-based access to SAP ERP and otherWeb-applications from SAP or third party vendors. You use the SAP NetWeaver PortalContent Directory to define roles for SAP NetWeaver Business Client in a multiple-systemenvironment. In a one-system environment (for example, SAP All-In-One case) roles for SAPNetWeaver Business Client can also be defined in transaction PFCG in the system withproduct instance SAP ECC Server.

The SAP NetWeaver Business Client can render Automatic Roles and Role-Based WorkCenters.

Documentation ReferencesFor more information about installing SAP NetWeaver Business Client, see the SAPNetWeaver documentation on SAP Help Portal at help.sap.com SAP NetWeaverSAP NetWeaver 7.0 (2004s) Functional View SAP NetWeaver by Key CapabilityPeople Integration By Key Capability SAP NetWeaver Business Client (with PCDConnection).

3.1.3.5 Product Instance: SAP FSCM - Biller DirectOverviewIn keeping with prior enhancement packages, the current enhancement package includesfunctions for different generic business processes in the Financials key functional area ofSAP ERP. Some of these processes as well as different SAP Industry Solution scenariosmake use of the product instance SAP FSCM - Biller Direct.

Software component versionThe product instance SAP FSCM - Biller Direct includes the Software Component VersionFSCM-BILLER DIRECT 6.04. It enables processes in the following functional areas:

Credit management

Electronic invoicing and payments

Dispute management

Collections management

Technical PrerequisitesThe installation prerequisite for product instance SAP FSCM – Biller Direct in the context ofenhancement package 4 for SAP ERP 6.0 is product instance SAP FSCM - Biller Direct fromproduct version SAP ERP 6.0. SAP FSCM - Biller Direct requires systems with SAPNetWeaver 7.0 – usage type AS Java.




50 February, 2009

Installation ConsiderationsFor more information about the processes mentioned and their Installation, see SAP Library,at help.sap.com, under SAP ERP Central Component Financials SAP FinancialSupply Chain Management (FIN-FSCM).

For more information about the functions for Financial Supply Chain Management, see theSAP Service Marketplace at http://service.sap.com/fscm.

3.1.3.6 Product Instance: SAP Integration for SWIFTOverviewWith enhancement package 2 for SAP ERP 6.0, SAP has extended the generic SAP ERPbusiness process Processing Outbound Payments Using Bank Communication Managementby functions to enable integration to the SWIFT Gateway. Due to the cumulative character ofenhancement packages, these functions are also available with the current enhancementpackage.

Software Component VersionThe product instance SAP Integration for SWIFT includes the software component versionSWIFT 602 (SAP Integration Package for SWIFT 602), which consists of a file interface to theSwift Gateway.

Technical PrerequisitesYou install product instance SAP Integration for SWIFT on system instances with productinstance SAP NW – Process Integration.

A complete installation of the Processing Outbound Payments Using Bank CommunicationManagement requires XI Content Packages. These include the required XI mapping to ISO20022 messages.

InstallationFor more information about Processing Outbound Payments Using Bank CommunicationManagement see:

SAP Library, at help.sap.com, under SAP ERP Central Component Financials SAP Banking

SAP Service Marketplace at http://service.sap.com/erp

For more information about industry wide e-business process standards like Rosetta Net,PIDX, CIDX, UCCNet, see the SAP Service Marketplace athttp://service.sap.com/industryspeak and see the information about productinstance XI Content in the current guide.

For further information about the installation of the SAP Integration for SWIFT productinstance, see SAP Note 1064419 (SAP Integration Package for SWIFT: Info aboutinstallation).

3.1.3.7 Product Instances for the SAP LearningSolutionOverviewThe SAP Learning Solution supports the following generic SAP ERP business processes:

Managing Enterprise Learning Strategies

http://service.sap.com/fscm

http://service.sap.com/erp

http://service.sap.com/industryspeak


51 February, 2009

Instructor and Tutor

Training Administrator

While the first process exists in SAP ERP 6.0, we have newly created the latter bothprocesses with the current enhancement package.

Software Component VersionSAP has altered different product instances and software components of the SAP LearningSolution beginning with enhancement package 2 for SAP ERP 6.0 (see table).

Product Instance Software component versionSAP Learning Sol-Client(Lern)

SAP LEARNING SOLUTION 6.04 - OFFLINEPLAYER

SAP Learning Sol-Client(Auth)

SAP LEARNING SOLUTION 6.04 - AuthoringEnvironment

SAP Learning Sol-FrontendCP

SAP LEARNING SOLUTION 6.04 - CONTENTPLAYERSAP LEARNING SOLUTION 6.04 - TrainingManagement FrontendSAP WEB UIF 7.0SAP_BS_FOUNDATION 701


SAP enhancement package 1 for SAPNetWeaver 7.0–version of the ApplicationServer ABAP

Technical PrerequisitesThe following technical prerequisites exist for the different product instances:

SAP Learning Solution Backend (LSO): The backend component LSO was aseparate add-on required for the Learning Solution Releases 1.0 and 2.0. Startingwith Learning Solution 3.0, SAP has integrated the function originally contained inthis add-on into product instance SAP ECC Server, originally contained in this add-onso that it no longer requires a supplemental CD. Software component version LSO600 Backend provides you with the following modules:

Training Management Personnel Development HR Master Data Organizational Management

Training Management stores all application data and business functions. This includescourse participants’ master data, learner account, course catalog, qualification catalog, anddetailed data on the individual courses.

Product Instance SAP ECC Server requires a system instance on SAP NetWeaver 7.0 usagetype AS ABAP. Before you can use the new functions for the SAP Learning, you need toinstall the enhancement package 1 for SAP NetWeaver 7.0 – Application Server ABAP on thesystem instance with SAP ECC Server. You update this usage type to enhancement package1 for SAP NetWeaver 7.0 with the installation of the corresponding technical usages.

SAP LEARNING SOLUTION 6.04 - Training Management Frontend (LSOFE): Thisproduct instance represents an add-on installed on the system with product instanceSAP ECC Server or on a separate Web Application Server (standalone installation).LSOFE contains a Web-based Learning Portal that provides the learners withpersonalized access to information and functions. The Learning Portal Frontendbases on Business Server Pages (BSPs). The SAP ECC Server system


52 February, 2009

communicates with SAP Web AS by means of RFC, and provides the dynamiccontent of the BSPs.

You install product instance SAP ECC Server on a system with SAP NetWeaver 7.0 usagetype AS ABAP. Before you can use the new functions for the SAP Learning Solution, youneed to update the usage type AS ABAP of the SAP ECC Server with the enhancementpackage 1 for SAP NetWeaver 7.0. In addition, the tools install the software componentversions SAP WEB UIF 7.0, and SAP_BS_FOUNDATION 701.

A Business Package for Learning (SAP ERP) is available. You can optionally use thisbusiness package with LSO 6.0 in the SAP Enterprise Portal. You must use it, if you wouldlike to set up the access to the Learning Portal of LSO 6.0 through SAP Enterprise Portal.

SAP LEARNING SOLUTION 6.04 - CONTENT PLAYER (LSOCP): This serverapplication enables processing of the learning content on a particular client PC. Thesoftware reads the learner account in the system with product instance SAP ECCServer. This happens to determine the course status before the learner starts withthe learning unit. When the learner has finished playing the learning unit, LSOCPsaves the current course status in the learner account.

You may have to install plug-ins in addition to an Internet browser to use the learning unit,depending on the sort of content you would like to process.

From a technical perspective, LSOCP relies on Java Server Pages. It uses SAP’s own J2EEEngine. This engine is part of the SAP Web AS, as the Servlet Engine.

SAP LEARNING SOLUTION 6.04 - Authoring Environment (LSOAE): You use theAuthoring environment to develop courses. It combines several tools that provide thefunctions for structuring (Instructional Design Editor), editing (Test Author), andtesting (integrated Content Player) course content. You need to install it locally onyour PC. You can use the Authoring Environment offline on your local PC, and onlinethrough direct data exchange between the Publisher Database (SAP ECC) and thecentral Content Repository (CM or a WebDAV server). When you check in thecontents, the Publisher Database in the SAP ECC backend system is receiving data.

You need the Java Development Kit (JDK) for the Authoring Environment. Since thiscomponent is not part of the SAP shipment, you must download and install it separately.

SAP LEARNING SOLUTION 6.04 - OFFLINE PLAYER (LSOOP): With the OfflinePlayer, you enable learners to download Web-based courses from the LearningPortal and to play them locally. The system lists locally stored courses in the courselist. An icon indicates the status of each course.

The Offline Player guides the learner through the course according to the preferred learningstrategy. The Offline Player dynamically adjusts the number and sequence of learning objectsto the learner’s individual learning pattern. If the learner interrupts a course, the ContentPlayer re-enters the course at the point of interruption the next time.

Learners can resynchronize their offline learning progress with the Learning Portal and eithercontinue learning online or set the course to a completed status. The offline course remainslocked on the PC either until the learner decides to delete the course or until he indicatesthrough the Learning Portal that he intends to replay the course.

Java Development Kit (JDK) is required for the Offline Player. Since this component is notpart of the SAP shipment, download and install it separately.

Depending on the enhancement package, different Java software component versions areavailable. Which Java software component version is required, depends on the activation ofthe associated business function. In particular, if you have installed the enhancementpackage, but do not activate the business functions of the SAP Learning Solution, you needto verify that you use the correct Java software component versions.

Documentation References


53 February, 2009

For more information about the solution, see SAP Service Marketplace athttp://service.sap.com/learningsolution.

For additional information, see the following information sources:

SAP Note 529063

SAP Note 503907

Master Guides and Installation/Upgrade Guides from SAP Service Marketplace athttp://service.sap.com/erp-inst

For information about the required Java software component version, see SAP Note1170324.

3.1.3.8 Product Instance: SAP Retail Store ApplicationOverviewIn keeping with previous enhancement packages, the current enhancement package includesenabling functions for SAP Solutions or SAP Business Suite Applications other than SAPERP. The SAP for Retail Industry Solution requires different product instances to supportdifferent industry specific business scenarios. You can consider these industry specificproduct instances as being part of the current product version for the enhancement package.

Software Component VersionSAP ships an unchanged version of the software component IS-R-SRS 602 withenhancement package 2 for SAP ERP 6.0 or subsequent enhancement packages.

Technical PrerequisitesThe product instance SAP Retail Store Applications requires product instance SAP ERP 6.0 -SAP NW - Application Server Java (SAP NetWeaver 7.0 usage type AS Java).

Documentation ReferencesFor more information, see the Master Guides for SAP for Retail, on SAP Service Marketplaceat http://service.sap.com/instguides.

3.1.3.9 Product Instance: SAP Utility Customer E-ServiceOverviewSince enhancement package 2 for SAP ERP 6.0 is available, SAP has developed additionalfunctional enhancements for the SAP for Utilities Industry Solution. You install and operatethe corresponding product instance SAP Utility Customer E-Service on separate systeminstances in order to enable these deliveries.

Software component versionThe product instance SAP Utility Customer E-Service includes the following SoftwareComponent Versions

EHP4 FOR SAP ERP 6.0 (Easy Adoption) includes the software component versionsSAP JAVA DICTIONARY 5.0 and compatible, and SAP UCES 6.02

EHP4 FOR SAP ERP 6.0/ NW 7.01 (Continuous Innovation) includes the softwarecomponent versions SAP JAVA DICTIONARY 7.0, SAP UCES 6.04, and SAP EHP1for SAP NW 7.0 FOR BPC – Application Server Java

http://service.sap.com/learningsolution




54 February, 2009

Technical PrerequisitesYou install product instance SAP Utility Customer E-Service in system instances with usagetype Application Server Java (product instance SAP ERP 6.0 - SAP NW - Applic. ServerJava).

Both, SAP FSCM – Biller Direct and SAP Utility Customer E-Service include the softwarecomponent version FSCM – Biller Direct 6.04. Before installing it in a separate systeminstance, consider installing SAP Utility Customer E-Service in an available system instancebased on SAP FSCM – Biller Direct, which might already be available in your systemlandscape.

Documentation ReferencesFor more information, see the installation information for SAP for Utilities, on SAP ServiceMarketplace at http://service.sap.com/instguides.

3.1.3.10 Product Instance: SAP SEMOverviewYou use the product instance SAP SEM and the related ABAP Product Instance StrategicEnterprise Management to enable generic business processes for analytic capabilities.

Software component versionBoth product instances include identical features, but are installed in different systeminstances separately, or embedded in one system instance. Both product instances includethe following software component versions:

SAP ERP:

SEM-BW 604

FINBASIS 604

SAP WEB UIF 7.0


SAP NetWeaver

SAP enhancement package 1 for SAP NetWeaver 7.0 – Application ServerABAP.

Technical PrerequisitesSAP has based the product instance SAP SEM on product instance SAP ERP 6.0 – SAPSEM. You install the ABAP Product Instance Strategic Enterprise Management in addition toSAP ERP 6.0 – SAP ECC Server.

You install the product instances SAP SEM and SAP ECC Server on the SAP NetWeaver 7.0- usage type AS ABAP. With the installation of the current enhancement package, theinstallation tools update this usage type with the enhancement package 1 for SAPNetWeaver 7.0.

In order to exploit the complete functional capabilities in the Strategic EnterpriseManagement area, a system instance with SAP NW – EP Core needs to be available. Youneed to configure this system instance for SAP NW – BI Java.

SAP NW – BI Java is available in the following product versions:

SAP ERP 6.0



55 February, 2009

EHP4 FOR SAP ERP 6.0/ NW 701

You install the first version in an Easy Adoption system landscape, and the latter version in asystem landscape for the Continuous Innovation path.

Documentation ReferencesFor more information about SAP SEM, or SAP NW – BI Java, see:

The Master Guide for SAP ERP 6.0 on SAP Service Marketplace, athttp://service.sap.com/erp-inst

Business related information is available on SAP Service Marketplace athttp://service.sap.com/sem

Hardware sizing for SAP NW – Business Intelligence, see SAP Note 927530 (BI Javasizing).

3.1.3.11 Product Instance: SAP XSS (Self Services)OverviewYou use product instance SAP XSS (Self Services) for the installation of Role-Based WorkCenters. The installation takes place within system instances, either on product instance SAPNW – Enterprise Portal or on SAP NW – EP Core. It consists of different softwarecomponents, which supply the self-service capabilities into these system instances.

Software component versionThe current product instance SAP XSS (Self Services) includes the software componentversions IS FS ICM APP 603, SAP ESS 603 and SAP PCUI_GP 603. As indicated by theversion, the software components SAP ESS and SAP PCUI_GP remain unchanged,compared to the previous enhancement package.

Technical PrerequisitesSAP has based product instance SAP XSS (Self Services) on product instance SAP ERP 6.0– SAP XSS (Self Services). It requires a system based on SAP ERP 6.0 - SAP NW – EPCore (usage type EP Core) on the same J2EE instance.

Note, that the installation of system instances with SAP NW – EP Core and SAP XSS (SelfServices) follow a certain pattern. In particular, as dependencies exist between SAP XSS(Self Services) and Business Packages from product instance Portal Content Self Services.

Documentation ReferencesFor more information about the installation of SAP XSS (Self Services), see the Master Guidefor SAP ERP 6.0 on SAP Service Marketplace at http://service.sap.com/erp-inst.

3.1.3.12 Product Instance: SAP Easy DocumentManagementOverviewThe quality of documentation and the availability of information are becoming increasinglyimportant.

SAP Easy Document Management 7.0 supports you by letting you use the extensivefunctions of SAP Easy Document Management 7.0 without having detailed knowledge ofSAP Document Management (SAP DMS). You can create public and private folders, whichare documents in DMS, in hierarchical structures, and then save your files there.


http://service.sap.com/sem



56 February, 2009

SAP Easy Document Management 7.0 includes several important features such as: Linking document management with computer-aided development and production

systems prevents redundant data retention and unsatisfactory consistency, andreduces the effort put into entering data and keeping it up-to-date

Integration with CAD desktopNew and strict product liability laws are making it increasingly important to archive documentsduring the life cycle of a product. Making a quality product demands more than just theproduct itself, it also requires a corresponding manufacturing process and organizationalenvironment. A company that supports certifiable quality management (such as the ISO 9000to 9006 series of standards) cannot fulfill the high quality requirements without a powerfuldocument management system.

SAP Easy Document Management 7.0 is more than equal to these complex requirements. Itdoes more than just manage it also coordinates. You can automate the complete life cycle ofa document - from creation to successful check-in, from access to update. You can accessevery document from every work center in a network.

Software component versionThe product instance SAP Easy Document Management consists of product instance SAPEASY DOCUMENT MGMT 7.00 - EASY DOCUMENT MGMT. It consists of an update to thecorresponding product instance in product version SAP ERP 6.0.

Technical PrerequisitesYou use SAP Easy Document Management to support the exchange of documents betweenSAP cFolders, and a backend system based on SAP R/3 or SAP ECC Server. You install itas an optional front-end component within your own intranet. Keep in mind that, before youinstall the current SAP Easy Document Management version on your system instances, youneed to uninstall existing prior versions.

Documentation ReferencesYou access the newest installation guide in the SAP Service Marketplace athttp://service.sap.com/instguides under SAP Business Suite Applications SAPERP SAP ERP 6.0 Installation Installation SAP Easy Document Management 7.0.

For more information about@

Functions and features see the business function documentation in the SAP Libraryhelp.sap.com.

Previous software component versions and related product versions, or about thesystem landscapes see the Master Guide for SAP ERP 6.0 on SAP ServiceMarketplace, at http://service.sap.com/erp-inst SAP ERP 6.0Installation Installation SAP Easy Document Management 7.0.

3.1.3.13 Product Instance: SAP Integration for BCONSOverviewThe SAP Integration for BCONS product instance allows you to exchange businessdocuments by connecting a SAP ECC Server system instance to a different system instance.This system instance needs to fulfill the following criteria:

It is hosted by a Business Process Outsourcing service provider, and

It is operating the SAP Billing Consolidation solution




57 February, 2009

At current, the system supports the following business document types: orders, orderchanges, order responses, shipping notifications and invoices. The system processes themby means of IDOC processing.

In addition, the solution can verify electronic signatures of digitally signed documents. Itattaches the generated signature verification protocol to the document set. The software isrouting the business documents, packed in Document Sets, by means of a system with SAPNW Process Integration.

Software component versionThe product instance SAP Integration for BCONS (SAP Connector Package for BillingConsolidation 604) includes the software component version BCONS 604. This componentversion includes

A dictionary for storing the CRL data, customizing and signer authorization data in theJ2EE database,

A web services to maintain these tables, and a verification application forsignature verification, or adapter modules for mapping or Document Set verification.

Technical PrerequisitesYou install SAP Integration for BCONS in system instances on SAP NW – ProcessIntegration. The complete installation of all functions for Business Consolidation requires theXI content package, which corresponds to software component SAP_APPL 604.

Documentation ReferencesFor installation information, see SAP Note 1280819. For more business related information,see the business function documentation in the SAP help portal help.sap.com.

3.1.3.14 Product Instance: SAP Product VisualizationOverviewSAP has introduced product instance SAP Product Visualization with SAP enhancementpackage 4 for SAP ERP 6.0. It includes a third party front-end viewer, which requires aseparate license.

You use SAP Product Visualization in different SAP PLM processes, which employ the ABAPProduct instance PLM Core. In particular, you can use the viewer to display CAD graphicsand documents within PLM Web User Interface (PLM WUI).

Software component versionThe product instance SAP Product Visualization includes the software component versionSAP Product Visualization 7.0. SAP has assigned SAP Product Visualization to the technicalusage PLM Core.

Technical PrerequisitesYou need to install SAP Product Visualization on the front-end client.

Documentation ReferencesFor more information about installing this viewer,

Follow the instructions of the installation wizard

See the installation guide for SAP enhancement package 4 for SAP ERP 6.0 on SAPService Marketplace http://service.sap.com/erp-inst

For installation information, refer to SAP Note 1179524.



58 February, 2009

3.1.3.15 Product Instance: Kayak SuccessorOverviewWith enhancement package 3 for SAP ERP 6.0, certain development objects from theseparate product version ENABLEMENT KIT FOR SAP AIO 1.2 have been migrated to SAPECC Server (software component SAP APPL). Product instance Kayak Successor is aspecial ABAP product instance. Kajak Successor is available since enhancement package 3for SAP ERP 6.0. You require the product instance Kayak Successor if you have installed theseparate product version ENABLEMENT KIT FOR SAP AIO 1.2, and if you intend to installenhancement packages as of enhancement package 3 for SAP ERP 6.0. As a productinstance with pure technical function, its function is to remove software component versionsfrom the system, which are not any longer used.

Software component versionThe product instance Kayak Successor includes the following software component versions

KAYAK 603

SAP APPL 6.04

SAP WEB UIF 7.0

SAP_BS_FOUNDATION 701 (SAP Business Suite Foundation 7.01)

Technical PrerequisitesThe product version Kayak Successor requires a system with usage type AS ABAP, and youinstall it in SAP ECC Server system instances.

The installation process for Kayak Successor updates the usage type AS ABAP of the SAPECC Server with the enhancement package 1 for SAP NetWeaver 7.0.

Documentation ReferencesFor more information about the Upgrade process, see the SAP Notes 1083533 and 1082916.

The upgrade tools install enhancement package 3 and enhancement package 4 togetherduring the upgrade from enhancement packages prior and including enhancement package 2for SAP ERP. Thus, the latter note is valid for the current enhancement package as well.

3.1.4 Content InstancesOverviewThe current enhancement package includes content product instances listed in the tablebelow in short content instances. Typically, you install the content instances together withother general product instances. They supply pre-configurations or predefined businesscontent to the corresponding system instances.

Table 5: Content Product Instances and Installation Prerequisites

Product Instance EHP4 FOR SAPERP 6.0

Related/Predecessor Product Version andProduct Instance

Used in conjunction with theproduct instances SAP ERP 6.0 –SAP NW – EP Core, or SAP NW –Enterprise Portal

SAP ERP 6.0 – Portal Content

SAP ERP ENHANCE PACKAGE 2005.1- PortalContent


59 February, 2009

Product Instance EHP4 FOR SAPERP 6.0

Related/Predecessor Product Version andProduct Instance

Portal Content,

Portal Content Common

Portal Content Self-Services

SAP ERP ENHANCE PACKAGE 2005.2- PortalContent

SAP ENH PACK 3 FOR SAP ERP 6.0- PortalContent

XI Content (used in conjunctionwith product instance SAP ERP 6.0– SAP NW – ProcessIntegration/SAP NetWeaver 7.0usage type Process Integrationbased on SAP enhancementpackage 1 for SAP NetWeaver 7.0)

SAP ERP 6.0 – XI Content

SAP ERP ENHANCE PACKAGE 2005.1 – XIContent

SAP ERP ENHANCE PACKAGE 2005.2 – XIContent

SAP ENH PACK 3 FOR SAP ERP 6.0-Conventional XI Content

ESR Content (used in conjunctionwith SAP NetWeaver 7.10 usagetype Process Integration, and XIContent for Service Enablementwith ESR based on SAPNetWeaver 7.10)

SAP ENH PACK 3 FOR SAP ERP 6.0 - ESR7.10

SAP ENH PACK 3 FOR SAP ERP 6.0 - ESR 7.10 includes both, XI contentpackages for SAP NetWeaver 7.0, and for SAP NetWeaver 7.10. With thecurrent enhancement package, the grouping product instance has beenrenamed to ESR Content, and it has been reduced to content for SAPNetWeaver 7.10. The new technical usage XI Content ESR 710 includes bothproduct instances.

3.1.4.1 Product Instance: Portal ContentOverviewA complete installation of a Role-Based Work Center in the system with product instanceSAP NW - EP Core requires the installation of one or more Business Packages with businesscontent. Up to and including enhancement package 3 for SAP ERP 6.0 SAP we use oneproduct instance Portal Content to group all Business Packages for a product version. As ofenhancement package 4 for SAP ERP 6.0, several different content instances are available,which have similar functions.

Software Component VersionThe product instance Portal Content for enhancement package 4 for SAP ERP 6.0 extendsthe product instance Portal Content, which is available in lower product versions. It includesall software component versions for both SAP ERP, and different SAP Industry Solutions(see table).

Table 6: Portal Content of the product version for SAP enhancement package 4 forSAP ERP 6.0


60 February, 2009

Area Business PackageName

SoftwareComponentVersion

Role Originating SAPEnhancementPackage<n> forSAP ERP

BP for SimplifiedReporting

BP ERPSIMPLFYDREPORTING1.30

SimplifiedReporting(Workset)

3SAP ERP

BP TechnicalInformation

BP ERPTECHNICALINFORMATION 1.41

n/a 3

SAP ERP -CorporateServices

BP for QualityInspector

BP ERP05QUALITYINSPECT1.31

QualityInspector

3

SAP ERP - End-User ServiceDelivery

BP for TransportationPlanner

BP IS TRP1.40

Transportation Planner

4

BP for BusinessConsolidation

BP ERPBUSINESSCONSOLIDATION1.30

Consolidation Monitor(Workset)

3

BP for Cash Manager BP ERPCASHMANAGER1.20

CashManager

2

BP for Closing Cockpit BP ERPCLOSINGCOCKPIT1.30

ClosingCockpit(Workset)

3

BP for Credit Manager BP ERPCREDITMANAGER1.41

CreditManager

2

BP for DisputeManager

BP ERPDISPUTEMANAGER1.41

DisputeManager

2

BP for Financial MDM BP ERP FINMDM 1.40

FinancialMDM(Workset)

4

SAP ERP -Financials

BP for XBRL Reporting BP ERPXBRLREPORTING1.30

XBRLReporting(Workset)

3


61 February, 2009




BP for EmployeeInteraction Center

BP ERP HREIC 1.40

EmployeeInteractionCenter

4

BP for Instructor andTutor

BP ERPINSTRUCTOR TUTOR1.41

Instructorand Tutor

2

BP for Recruiter BP ERPRECRUITER1.40

Recruiter 4

BP for E-RecruitingAdministrator

BP ERPRECRUITINGADMIN 1.40

E-RecruitingAdministrator

4

BP for TalentManagementSpecialist

BP ERP TMS1.40

TalentManagement Specialist

2

BP for TrainingAdministrator

BP ERPTRAININGADMIN 1.40

TrainingAdministrator

4

BP for HRAdministrator

BP ERP05HRADMINISTRATOR 1.41

HRAdministrator

1

SAP ERP -Human CapitalManagement

BP for TalentDevelopmentManagement

BP ERP05TALENT DEV1.01

TalentDevelopment Specialist

1

SAP ERP -Procurement andLogisticsExecution

BP for SupplierManaged Inventory

BP ERP SMI1.40

SupplierManagedInventory(Workset)

4

BP for BasicMaintenanceProcessing

BP ERPLEANMAINTENANCE 1.20

n/a 2

BP for MaintenancePlanner

BP ERPMAINTENANCE PLAN1.20

Maintenance Planner

2

SAP ERP -ProductDevelopmentandManufacturing

BP for MaintenanceSupervisor

BP ERPMAINTENANCE SUPER1.20

Maintenance Supervisor

2


62 February, 2009




BP for Takeover /Handover of TechnicalObjects

BP ERP THOTECHNICALOBJ 1.30

Takeover/Handover ofTechnicalObjects

3

BP for MaintenanceTechnician

BP ERP05MAINTENANCE TECH 1.2

MaintenanceTechnician

2

BP for ProductionSupervisor

BP ERP05PRODSUPERVISOR 1.41

ProductionSupervisor

4

BP for PLM WebuserInterface

BP_PLMWD7.0

PLM Expert 4

BP for Internal SalesRepresentative

BP ERP05INT SALESREP 1.4

InternalSalesRepresentative

2SAP ERP -Sales andServices

BP for Returns BPERPRET1.40

Returns(Workset)

4

BP for AutomotiveDealer Portal forWarranty

BP ERP ADW1.40

WarrantyClerk

4

BP for AutomotiveDealer Portal for SpareParts

BP IS AADSP1.40

Spare PartsClerk

4

SAP forAutomotive

BP for AutomotiveDealer Portal forVehicle Management

BP ISAADVM 1.40

VehicleSalesRepresentative

4

SAP for Defense& Public Security

BP for Defense &Public Security

BP IS DFPS1.40

Defense &PublicSecurity(Workset)

4

SAP for HigherEducation andResearch

BP for AcademicAdvisor (HigherEducation & Research)

BP ERPACADEMICADVISOR1.30

AcademicAdvisor

3

BP for Student (HigherEducation & Research)

BPISHERST1.40

Student 4


63 February, 2009




BP for Claim CenterAgent (Insurance)

BP ERPCLAIMCENTERAGENT 1.30

ClaimCenterAgent(Insurance)

3

BP for Claim Handler(Insurance)

BP ERPCLAIMHANDLER1.30

ClaimHandler(Insurance)

3

BP for CredentialsManager (Insurance)

BP ERP CRDMNG (INS)1.4

CredentialsManager(Insurance)

3

BP for CredentialsManager

BP ERPCREDENTIALS MNG 1.41

CredentialsManager(Workset)

3

BP for ICM Analyst BP ERP ICMANALYST1.41

ICM Analyst(Workset)

3

SAP forInsurance

BP for SalesCompensation Analyst(Insurance)

BP ERP ICMSALES AL(INS) 1.41

SalesCompensation Analyst(Insurance)

3

BP for ExpenditureCertification (PublicSector)

BP ERPEXPENDITURE CERT1.31

CertificationManager(PublicSector),CertificationAccountant(PublicSector)

3SAP for PublicSector

BP for Tax Officer(Public Sector)

BP ERP TAXOFFICER1.41

Tax Officer(PublicSector)

3

BP for Fresh ItemProcurement

BP ERPFRESH ITEMPROC 1.40

Fresh ItemBuyer

4

BP for RetentionWarehouseAdministration

BP ERP ILM1.40

RetentionWarehouseAdministration(Workset)

4

SAP for Retail

BP for WarehouseOperation Manager

BP ERPWAREHOUSE OP MNGR

WarehouseOperationManager

3


64 February, 2009




1.30

BP for WarehouseOperations

BPERPWHOP 1.40

WarehouseOperations

4

BP for Retail - PowerLists

BP IS RRTPOWL1.40

Retail (WorkSet)

4

BP for Retail Store BP IS-R-SRS1.40

Storemanager

4

SAP for ServiceProvider

BP for ServiceProvider

BPERPSRVPROV 1.40

ServiceProvider(Workset)

4

Technical PrerequisitesTo install portal content (Business Packages) for a particular Role-Based Work Center, youmust typically install the following product instances and software components.

Product instance SAP NW - EP Core is required as a basis. As part of SAP ERP 6.0SAP NW – EP Core based on SAP NetWeaver 7.0 – Usage Type Application ServerJava. As of enhancement package 4 for SAP ERP, the usage type is available onenhancement package 1 for SAP NetWeaver.

Depending on the particular business package, it might also be necessary to installproduct instance SAP ERP 6.0 – XSS (Self Services) with the correspondingenhancement package for SAP NetWeaver.

Business Packages from separate Portal Content Product Instances supportadministrative services for the SAP NW – EP Core product instances:

BP Common Parts

BP ERP05 SELF-SERV ADMIN

BP ERP TECHNICAL INFORMATION

RecommendationsThe different Portal Content product instances include all Business Packages for the currentenhancement package. Using either the Java Support Package Manager (JSPM) or the newSAP Enhancement Package installer, it is possible to:

Install the complete portal content (recommended for installing an enhancementpackage)

Concentrate on the required Business Packages

If you are interested in the latter optimization, you can use the Process Component List onSAP Service Marketplace at http://service.sap.com/scl. The Process Component



65 February, 2009

List provides you with information about individual business packages required by theindividual generic business process or Role-Based Work Center.

The following conditions and recommendations are important:

The installation of individual business packages is possible only with the JSPMinstaller tool, while using the additional usage type option.

As a prerequisite to installing generic business processes or Role-Based WorkCenters with an enhancement package, you must install the content product instanceversion, which corresponds to the specific process. You need to perform thisinstallation in addition to the content instances for the SAP ERP 6.0 product version.

The additional Business Packages (BP Common Parts, BP ERP05 SELF-SERVADMIN, BP ERP TECHNICAL INFORMATION), mentioned above, must be deployedon the same server as the function oriented Business Packages for particular Role-Based Work Center.

When installing individual Business Packages, you also need to install the dependentBusiness Packages of the appropriate release. For more information, see SAP Notes1105694, and SAP Note 1165442 in addition to the Process Component List. Thisnote documents dependencies, such as:

BP for Sales Representative (Insurance) uses BP for ICM-Participant

BP for Sales Compensation Analyst (Insurance) uses BP for ICM-Analyst

Documentation ReferencesFor more information about:

The installation of systems with usage types EP Core, AS Java, and of productinstance SAP XSS (Self Services), as well as specific upgrade recommendations,see the Master and Upgrade documentation for SAP ERP 6.0 on SAP ServiceMarketplace, at http://service.sap.com/erp-inst.

The installation of enhancement package 1 for SAP NetWeaver 7.0, see thecorresponding guides on SAP Service Marketplace, athttp://service.sap.com/instguides.

Installation tools and processes see the installation or upgrade guides on SAPService Marketplace at http://service.sap.com/erp-inst.

For more information about the following additional topics, follow the paths described here:

For assignment of Business Packages to generic business process, see SAP ServiceMarketplace at http://service.sap.com/scl, and for details aboutdependencies between different generic business processes see SAP Note 824757.

Further dependencies may exist between different business packages. For moreinformation, see SAP Notes 1105694, and SAP Note 1165442.

For examples of system landscapes, see the Master Guide for SAP ERP 6.0 on SAPService Marketplace, at http://service.sap.com/erp-inst. Also, review theindustry-specific guides on SAP Service Marketplace, athttp://service.sap.com/instguides.

For the topics Assigning Portal Roles, and the Role and Work Center Concept, seeSAP Library, at help.sap.com, under SAP ERP Central Component BusinessPackages (Portal Content).








66 February, 2009

3.1.4.2 Product Instance: Portal Content CommonOverviewSAP uses the product instance Portal Content Common to group all available generalBusiness Packages. As mentioned before, the installation of a Role-Based Work Center inthe system with product instance SAP NW - EP Core requires the installation of one or morebusiness packages.

Software Component VersionThe first version of product instance Portal Content Common is available with enhancementpackage 4 for SAP ERP 6.0 by splitting the Portal Content product instance from previousenhancement packages, and SAP ERP 6.0. The following table lists the softwarecomponents included.

Table 7: Portal Content Common SAP enhancement package 4 for SAP ERP 6.0

Area BusinessPackageName

SoftwareComponent Version

Role OriginatingSAPEnhancementPackage <n>for SAP ERP

Procurementand LogisticsExecution

BP for Buyer BP ERP05 BUYER1.41

Buyer 3

SAP ERP BP forCommon Parts

BP ERP05COMMON PARTS1.41

ERPCommon

3

Documentation ReferencesYou install Business Packages from product instance Portal Content Common equally tothose business packages from product instance Portal Content. For more information aboutthe installation, see Section 3.1.4.1 Product Instance: Portal Content.

3.1.4.3 Product Instance: Portal Content Self-ServicesOverviewProduct instance Portal Content Self-Services has a function comparable to the portalcontent packages introduced before. SAP uses the product instance to group all BusinessPackages used in self-service scenarios.

Software Component VersionThe product instance Portal Content Self-Services includes the business packages listed inthe following table. The initial version is available with enhancement package 4 for SAP ERP6.0 by splitting the Portal Content product instance from earlier enhancement packages andSAP ERP 6.0.

Table 8: Portal Content Common SAP enhancement package 4 for SAP ERP 6.0


67 February, 2009




BP for Employee Self-Service

BP ERP05ESS 1.41

EmployeeSelf-Service

3End-UserServiceDelivery

BP for Manager Self-Service

BP ERP05MSS 1.41

Manager Self-Service

4

SAP ERP BP ERP UT Definitionfor Self Service BP1.40

BP ERP UTXSS 1.40

UT Definitionfor SelfServices

4

BP for ICM Participant BP ERP ICMPARTICIPANT1.30

ICMParticipant(Workset)

3SAP forInsurance

BP for SalesRepresentative(Insurance)

BP ERP ICMSALESREP(INS) 1.30

SalesRepresentative (Insurance)

3

BP for WorkforceManager(Telecommunications)

BP ERPWORKFORCEMANAGER1.20

WorkforceManager(Telecommunications)

2

BP for NetworkOperation Manager(Telecommunications)

BP ERPNETWORKOP. MNG 1.20

NetworkOperationManager(Telecommunications)

2

SAP forTelecommunications

BP for Site Technician(Telecommunications)

BP ERP SITETECHNICIAN1.20

SiteTechnician(Telecommunications)

2

Documentation ReferencesYou install Business Packages from product instance Portal Content Self-Service as youinstall business packages from product instance Portal Content. For more information, seeProduct Instance: Portal Content.

3.1.4.4 Product Instance: XI ContentOverviewSome generic business processes require a system instance with product instance SAP NW- Process Integration. Each installation of such generic business process requires a specificXI Content software component with context information. SAP has grouped the different XIContent software components available into the product instance XI Content.


68 February, 2009

FeaturesYou already know the XI Content product instance of the current enhancement package asusage type Conventional Service enablement (XI Content). It delivers the following type of XIContent software components:

XI Content, which is directly relevant to using the processes and scenarios of thecurrent enhancement package. The current guide covers these processes andscenarios.

XI Content, which enables scenarios or processes of other SAP Business SuiteApplications. For these applications, additional installation or upgrade guides may beavailable.

Software component versionThe product instance XI Content of the current enhancement package for SAP ERP extendsthe product instance XI Content from product version SAP ERP 6.0. It includes the softwarecomponent versions shown in the following table.

Table 9: Product instance XI Content

XI Content for …

Software ComponentVersion in SAPenhancement package 4for SAP ERP 6.0

Required forBusiness Processesby

Remark

SAP ERP Processes in SAP enhancement package 4 for SAP ERP 6.0

XI CONTENT BI CONT 7.04 Content for SAP NW - BusinessIntelligence

XI CONTENT EA-APPL 604 General content SAP ECCServer

XI CONTENT EA-FINSERV604

Content for Financials

XI CONTENT EA-HR 604 Content for Human CapitalManagement

XI CONTENT ERECRUIT604

Content for SAP e-Recruiting

XI CONTENT ESA ECC-SE604

XI Content for SAP ECC Server(enablement for the Service-Oriented Architecture (SOA))

XI CONTENT FI-CA 604 Content for Financials

XI CONTENT FINBASIS604

Content for Financials

XI CONTENT HR 604 Content for Human CapitalManagement

XI CONTENT HR-XML 604

SAP ERP

Content for Human CapitalManagement (HR Administrator)


69 February, 2009

XI Content for …



Remark

XI CONTENT SAP_APPL604

General content SAP ECCServer

XI CONTENTSAP_BS_FOUND 701

XI Content for SAP ECC Server(SAP Business Suitefoundation)

XI CONTENT SEM-BW 604 Content for SAP SEM

SAP Industry Solutions

XI CONTENT EA-DFPS 604 SAP for Defense &Security

Content for SAP ECC Server

XI CONTENT EA-GLTRADE604

SAP for Global Trade Industry-specific content forSAP ECC Server

XI CONTENT EA-PS 604 SAP for PublicServices

Industry-specific content forSAP ECC Server

XI CONTENT ECC-DIMP604

SAP for DiscreteIndustries


XI CONTENT INSURANCE604

SAP for Insurance Industry-specific content forSAP ECC Server

XI CONTENT IS-H 604 Content for SAP for Healthcare

XI CONTENT IS-H_IC 604

SAP for Healthcare

Content for SAP for Healthcare

XI CONTENT IS-M 604 SAP for Media SAP for Media

XI CONTENT IS-OIL 604 SAP for Oil and Gas Industry-specific content forproduct instance SAP ECCServer

XI CONTENT IS-PS-CA 604 SAP for Public Sector Student Master DataDistribution within SAP CampusManagement

XI CONTENT IS-UT 604 SAP for Utilities Industry-specific content forproduct instance SAP ECCServer

XI CONTENTPROMERLAYINTEG 6.7

Scenarios Promotions Planning& Management, Retail Price &Revenue Management,Demand Modeling andForecasting

XI CONTENT EA-RETAIL604

SAP for RetailIndustry Solution



70 February, 2009

XI Content for …



Remark

XI CONTENT STORECONNECT.2.0

Scenario Point of Sale

XI CONTENT GS1 1.0 The GDS Inbound enablesmass transfer of article masterdata from external data pools orbilaterally from vendors intoretailers’ master data. Itcontains messages according toGS1.

XI CONTENT DEMANDMGMT 1.0

Scenarios Promotions Planning& Management, Retail Price &Revenue Management,Demand Modeling andForecasting and SAP DemandManagement

XI CONTENT UN/CEFACT1.0

The GDS Inbound enablesmass transfer of article masterdata from external data pools orbilaterally from vendors. Itcontains the messagesaccording to UN/CEFACT.

SAP INTEGRATION FOR SWIFT

XI CONTENT ISO20022 1.0 SAP ERP –Financials

XI CONTENT ISO20022ERP 1.0

XI CONTENT SWIFT 602

Content for BankCommunication Management

Technical Prerequisites You install the product instance EHP4 FOR SAP ERP 6.0 – XI Content in system

instances with product instance SAP NW – Process Integration of SAP ERP 6.0. Itdelivers the integration content as a prerequisite for SAP ERP integration scenarios.

SAP NW – Process Integration corresponds to the SAP NetWeaver 7.0 – UsageType Process Integration. The installation of enhancement package 4 for SAP ERP6.0 makes enhancement package 1 for SAP NetWeaver 7.0 available in the system.

The installation process updates existing software component versions with a newerversion, or it adds additional software components. In contrast to these softwarecomponent versions, you must install the relevant content instances in addition to thecontent instances for product version SAP ERP 6.0.

As systems with SAP NW – Process Integration link back to systems with SAP ECCServer, the versions for the individual XI Content packages need to match theversion used for product instance SAP ECC Server or the individual softwarecomponents, which are included there.


71 February, 2009

Documentation References Several software versions delivered with enhancement package 4 for SAP ERP 6.0

are not used directly by processes or scenarios of SAP ERP. SAP has documentedthe installation/upgrade of these indirect scenarios in separate guides. You find themon SAP Service Marketplace at http://service.sap.com/instguides.

For more information about the installation procedure for XI Content, see SAP Note836200 - SAP NetWeaver 7.0: Importing process integration content.

3.1.4.5 Product Instance: ESR ContentOverviewProduct instance ESR CONTENT corresponds to the following entities:

SAP NetWeaver usage type Service Enablement with ESR and is based on SAPNetWeaver 7.10

Product Version ESR FOR SAP NETWEAVER CE 7.1 (Enterprise ServicesRepository for SAP NetWeaver CE 7.1)

It delivers the models and descriptions required for an SAP NetWeaver 7.10 basedEnterprise Service Repository (ESR).

From a content perspective, Service Enablement with ESR based on SAP NetWeaver 7.10 iscomparable to the usage type conventional service enablement (product instance XI Content)but it contains additional ESR content that is only available for SAP NetWeaver 7.10.

In contrast to product instance XI Content, you can install ESR content in systems with SAPNetWeaver 7.10 usage type Process Integration.

As the tools install both product instances XI Content and ESR Content together, SAP hasgrouped them into the technical usage XI Content ESR 710.

FeaturesProduct instance ESR CONTENT delivers the following content:

XI Content directly relevant to processes and scenarios of the particularenhancement package for SAP ERP

XI Content that is the basis for certain scenarios of processes of other SAP Solutionsand which reuse product version SAP ERP 6.0

Software component versionThe product instance ESR CONTENT includes XI Content packages, and includes thesoftware component versions shown in the following table.

Table 10: Product Instance ESR CONTENT

XI Content for …

Software Component Versionin SAP enhancement package4 for SAP ERP 6.0

Required forBusinessProcesses by

Remark

SAP ERP Processes in SAP enhancement package 4 for SAP ERP 6.0

XI CONTENT EA-APPL 604 SAP ERP General content SAP ECCServer



72 February, 2009

XI Content for …



Remark

XI CONTENT EA-FINSERV 604 Content for FinancialsXI CONTENT EA-HR 604 Content for Human Capital

ManagementXI CONTENT ERECRUIT 604 Content for SAP e-RecruitingXI CONTENT ESA ECC-SE 604 XI Content for SAP ECC Server

(enablement for the Service-Oriented Architecture (SOA))

XI CONTENT ESM ERP 604XI Content for SAP ECC Server

XI CONTENT ESMINTEGRATION 2.0

XI Content for SAP ECC Server

XI CONTENT FI-CA 604 Content for FinancialsXI CONTENT FINBASIS 604 Content for FinancialsXI CONTENT HR 604 Content for Human Capital

ManagementXI CONTENT HR-XML 604 Content for Human Capital

Management (HR Administrator)

XI CONTENT SAP_APPL 604 General content SAP ECCServer

XI CONTENT SAP_BS_FOUND701

XI Content for SAP ECC Server(SAP Business Suitefoundation)

XI CONTENT SAPGLOBAL 2.0XI Content for SAP ECC Server

XI CONTENT SAPGLOBALMODEL 2.0

XI Content for SAP ECC Server

XI CONTENT SEM-BW 604 Content for SAP SEMSAP Industry SolutionsXI CONTENT EA-DFPS 604 SAP for Defense &

SecurityContent for SAP ECC Server

XI CONTENT EA-GLTRADE604

SAP for GlobalTrade


XI CONTENT EA-PS 604 SAP for PublicServices


XI CONTENT EA-RETAIL 604 SAP for RetailIndustry Solution


XI CONTENT ECC-DIMP 604 SAP for DiscreteIndustries


XI CONTENT INSURANCE 604 SAP for Insurance Industry-specific content forSAP ECC Server

XI CONTENT IS-H 604 Content for SAP for HealthcareXI CONTENT IS-H_IC 604

SAP for HealthcareContent for SAP for Healthcare

XI CONTENT IS-M 604 SAP for Media SAP for Media


73 February, 2009

XI Content for …



Remark

XI CONTENT IS-OIL 604 SAP for Oil and Gas Industry-specific content forproduct instance SAP ECCServer

XI CONTENT IS-UT 604 SAP for Utilities Industry-specific content forproduct instance SAP ECCServer

XI CONTENT IS-PS-CA 604 SAP for PublicSector

Student Master DataDistribution within SAP CampusManagement

Technical PrerequisitesThe product instance ESR CONTENT of product version EHP4 FOR SAP ERP 6.0 requiresthe availability of an ESR on the SAP NetWeaver 7.10 Usage Type Process Integrationrelease (product version ESR FOR SAP NETWEAVER CE 7.1). It delivers an additionaloption to install the integration content as a prerequisite for installing SAP ERP processes forthe current enhancement package.

It is possible to install the SAP NetWeaver 7.10 - Process Integration system instance anew,or to upgrade it from a SAP NetWeaver 7.0 - Process Integration.

Since systems with SAP NW – Process Integration link back equally to systems with SAPECC Server, the software component versions for XI Content (XI Content or ESR Content)need to match the version used for product instance SAP ECC Server or the individualsoftware components included there.

Documentation ReferencesSeveral processes and scenarios work with product instance ESR CONTENT. For moreinformation, see the following information sources:

Available Master Guides for the Service-Oriented Architecture (SOA) on SAP ServiceMarketplace at http://service.sap.com/instguides

The SAP Library Documentation available athelp.sap.com/content/documentation/esoa/erp/

SAP has based the current enhancement package and the underlying SAP ERP 6.0 onrelease SAP NetWeaver 7.0. Make sure you download and install SAP NetWeaver 7.10usage type Process Integration as described in the respective separate Master Guides onSAP Service Marketplace at http://service.sap.com/instguides, before trying toattempt to install product instance ESR CONTENT. For more information about the requiredXI Content, see SAP Note 1224543.As stated before, the use of product version ESR Content is an additional extending option.The conventional service enablement without Enterprise Service Repository requires SAPNetWeaver 7.0 based software components, with SAP enhancement package 1 for SAPNetWeaver 7.0.

3.2 Software Component MatrixOverview




74 February, 2009

The SAP Business Suite consists of applications, such as SAP ERP and SAP IndustrySolutions, such as SAP for Public Sector.

Generic Business Processes and Role-Based Work Centers structure SAP ERP.

Scenarios structure SAP Industry Solutions. These scenarios reuse the capabilitiesoffered by different SAP Business Suite applications.

Normally, the availability of system instances in the existing customer system landscapedepends on the generic business processes, scenarios, or Role-Based Work Centers, whichyou support with this system landscape.

Process Component ListThe installation process for an enhancement package starts with the selection of businessfunctions, and the Technical Usages to be implemented in existing system instances. Incases where you need to extend the system landscape beforehand, you need the followinginformation:

Software units, to be implemented for the particular business process/role-basedWork Center

Whether the software unit is mandatory or optional

The minimum release for each software unit, which deviates from the generalstandard for the current enhancement package

Information about the latest component version and patch level requirements

System Landscapes used to install these processes and Role-Based Work Center

This Master Guide provides just one way to implement each generic business process, Role-Based Work Center, or business function. The Scenario & Process Component List helps youto find realization alternatives for SAP solutions, business scenarios and processes. It showsyou:

Which functional scope is possible with the already installed system instances

Which application components are required to realize an additional businessscenario or generic business process/role-based Work Center

Documentation References For Installation alternatives, see the Scenario & Process Component List in SAP

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

For the latest component version and patch level requirements, see SAP Note849887 and see the quick link /sp-stacks in the SAP Service Marketplace.

For general documentation, see References.

For conceptual information, see Solution-Wide Topics.

Installation and Upgrade of software component version BI CONT 7.04 see SAPNote 1172899.

For an overview over the different generic business processes, and an assignment tothe different editions/enhancement packages

For SAP ERP, see the SAP Service Marketplace athttp://service.sap.com/erp-ehp Media Library - SAPenhancement packages Enhancement Packages – General.

For SAP Industry Solutions, see Generic Business Processes, Scenariosand Role-Based Work Centers.




75 February, 2009

To ensure system consistency, changes within the underlying instances ofSAP ERP 6.0 may be required. Install a minimum SAP ERP 6.0 - SupportPackage Stack before attempting to install any component of anenhancement package for SAP ERP. For more details, see the description inSAP Note 1064635, and related information.

3.3 System LandscapesOverviewThe SAP Business Suite consists of different applications, such as SAP ERP, or SAP CRM.You can install an enhancement package for SAP ERP in any system landscape capable ofaccommodating SAP ERP 6.0. Together with other SAP Business Suite applications, you canalso distribute the enhancement packages for SAP ERP into system landscapes for the SAPBusiness Suite.

Both, the Master Guide for SAP ERP 6.0, and the Upgrade Master Guide for SAP ERP 6.0scrutinize different system landscapes and focus on the installation of SAP ERP as a whole.They illustrate a number of system landscape types, which you can use, and they show theinstallation or upgrade sequences. The system landscape types include the following:

Minimum System Landscape

Extended System Landscape

Extended System Landscape with Firewall

Individual System Landscape

The following sections cover the topics listed here:

They present the resulting SAP ERP 6.0 individual system landscape extended toaccommodate the complete enhancement package

Help the system administrator to understand the different system related changes,when installing the enhancement package. It furthermore supports the description ofan installation sequence

Document alternative realizations in a SAP Business Suite system landscape

As you implement enhancement packages selectively, each real system landscape will differfrom the general examples. Thus, you need to plan system landscapes individually.

Individual System Landscape for SAP Enhancement Package 4 for SAPERP 6.0In the following figure, you can see that:

The product instances and software components of the current enhancementpackage are installed in addition to the corresponding system instances on SAP ERP6.0

Not all system instances are altered with new software components for the currentenhancement package

As of enhancement package 4 for SAP ERP 6.0, enhancement packages for SAPNetWeaver are also available. The installation process of the enhancement packageupdates SAP ERP system instances on SAP NetWeaver 7.0 to SAP enhancementpackage 1 for SAP NetWeaver 7.0.


76 February, 2009

Figure 2: Individual System Landscape for SAP Enhancement Package 4 for SAP ERP 6.0(Unchanged System Instances Grayed Out)

Individual System Landscape for SAP Industry Solutions and SAPBusiness SuiteThe enhancement package enables various industry scenarios across different SAP industrysolutions. It furthermore includes codeine enhancements for other SAP Applications. You canimplement most of these SAP industry solution and SAP Application scenarios within astandard system landscape for SAP ERP 6.0, when using the SAP ERP Product Versionsdescribed previously.

Scenarios, you need to extend the SAP ERP system landscape with system instances fromother SAP Product Versions. These additional system instances might already exist in yoursystem landscape or you will install them in addition to the enhancement package.

Separate Master Guides on http://service.sap.com/instguides are available, whichdescribe the installation for these system landscapes.

Systems with FirewallThe standard scenarios for web based transactions, such as the PLM Web User Interface, orthe SAP e-Recruiting run in your own intranet. In these scenarios, users need a Web browserto access the different functions. If you also want to grant access to external users due tocooperation with business partners, you need an additional installation of the enhancementpackage system in a demilitarized zone (DMZ). You typically lay out these systems followingthe Extended System Landscape with Firewall example.



77 February, 2009

An enhancement package system with PLM Core activated in a demilitarizedzone (DMZ), allows external users to use the functions with a Web browser.

Note that the system in the DMZ does not require any master and transactiondata or any comprehensive configuration. You solely use a DMZ foraccessing the PLM Web UI. Master and transaction data are stored in thePLM system in the intranet. An authorization framework controls access to thePLM Web User Interface in the DMZ for PLM Web User Interface.

For more information abouto Setting up the system landscape, see the configuration

documentation for PLM processes and scenarios in SAP SolutionManager

o The authorization concept, see the PLM chapters in the SAP ERPsecurity guide on SAP Service Marketplace athttp://service.sap.com/securityguide SAP ERPSecurity Guides

3.4. Overall Installation SequencePurposeYou enhance system landscapes such as the Individual System Landscape for SAP ERP inseveral steps. The installation sequence for an enhancement package consists of thefollowing main phases:

Plan: Identify the software components to be installed, and verify them with the givensystem landscape capabilities. (The verification comprises topics like the availabilityof the needed system instances, or the proper timing in respect to the requiredminimum support package stacks).

Install: Download and install the relevant software component versions from theenhancement package

Activate: Business functions to be used are activated

You require additional planning steps, if your current system landscape capabilities do notsupport the enhancements, which you plan to install.

The specific part of the enhancement package, that you intend to installincludes new SAP Enterprise Portal features. If your current systemlandscape does not include such a system, you need to make a systeminstance with SAP NW – EP Core available first.

The following sections concentrate on the overall installation sequence for the installation ofthe complete enhancement package. Customer-specific optimizations are possible, forexample, with respect to the installation of business packages, the partial use of genericbusiness processes, or the approach taken with respect to the use of the enhancementpackages for SAP NetWeaver 7.0.

AssumptionsThe assumptions define the installation sequence:

A system landscape with product version SAP ERP 6.0 already exists, or theupgrade to SAP ERP 6.0 will take place together with the installation of the currentenhancement package

You install all software units available for the enhancement package. When installingthe enhancement package selectively, as it is recommended, you need a subset ofthese software units only

http://service.sap.com/securityguide


78 February, 2009

You install the enhancement package 1 for SAP NetWeaver 7.0 in all relevantsystem instances of the system landscape. Remember that it is possible to takealternative paths and Installation decisions in terms of systems on AS ABAP and ASJava. Depending on these decisions, you may need to extend selected systeminstances only

Note the following:

All product instances of a specific enhancement package are technically independentof each other with regard to the installation sequence. These instances are installedin any order on the system instances with product version SAP ERP 6.0

Product instances are independent of the other software components of the SAPERP application, if not mentioned differently as prerequisites. For example, when youinstall an ABAP add-on software component, it does not matter whether any otherABAP add-on software component is installed on the same system/system-instance

Recommendations for Enhancement Package InstallationThe following recommendations are specific to the installation of enhancement packages.

Enhancement packages consist of different software components. By selecting theappropriate business function, it is possible to decide which specific softwarecomponent will be installed. It is not required that you install the completeenhancement package without a specific business need. SAP recommends that youselect the required business functions as specific as possible.

The installation of an enhancement package and the activation of the businessfunctions installed are separate activities. This allows you to install the newestfeatures together with the normal maintenance activities, without interrupting theproductive usage.

In order to minimize the test effort, SAP recommends that you apply theenhancement packages in one queue, together with the required Support Packages.

Be aware that you will require additional planning and installation steps if thebusiness function that you plan to enable exceeds the given capabilities of yoursystem landscape (for example, you will need a system with SAP NW – EP Core inorder to install the business packages for a business function that you plan toimplement).

Since software components have dependencies, you must ensure that you install allsoftware components in a way that you maintain the relation to the original softwarecomponent.

It is not possible to mix software components from different enhancement packagesfor SAP ERP arbitrarily. You need to make sure that you install all related softwarecomponents on the release level defined for the current enhancement package. Inthis context, note the following conditions:

If no additional change is available, the current enhancement package mightinclude unchanged software component versions from prior releases.

In particular, the active SAP Industry Solutions require special care, becauseit is not possible to employ system instances with a mixture of softwarecomponent versions from different enhancement packages. Depending onthe specific software component, which you install with a specific TechnicalUsage, you might need to update the software components for these SAPIndustry Solutions to the current enhancement package as well. In order todo so, first check your systems for activated SAP Industry Solutions, in orderto identify the software components which you need to update fordependency reasons.


79 February, 2009

The SAP ERP 6.0 product instance SAP NW - Adobe Document Service includesAdobe Document Services. You deploy this set of runtime services on the same SAPNetWeaver Application Server Java that provides a range of form and documentcreation and manipulation functions as needed by the SAP Interactive Forms byAdobe. If you have implemented your own forms, SAP recommends that you updatethem after installing the current enhancement package. The following documentationis helpful:

SAP NW – Adobe Document Service is described in the Master Guide SAPERP 6.0 on the SAP Service Marketplace athttp://service.sap.com/erp-inst

The recommended updates are laid down in SAP Note 956074

For running the PLM Web User Interface, all users must also have twoadditional applets installed on their local clients. For more information abouthow to prepare the installation and local security settings for these appletscentrally, see SAP Note 1224097.

Once you have installed an enhancement package, you cannot any longeruninstall it. Thus, the planning step prior to installing an enhancementpackage is particularly important if you install the enhancement packagesdirectly in the productive system landscape. SAP recommends that you use aseparate test system in order to test and explore the enhancement packagebefore you install it in your productive system landscape.

You cannot reverse the activation of a business function. SAP recommendsthat you carefully examine the documentation for the business function,before you activate it.

Normally you need to activate business functions before you can use them.Keep in mind that exceptions to this rule are possible. In these cases, thesheer installation of the software components for the business function makesit available to the end user.

Unlike other business functions, the functions implemented with businessfunction DFPS_OF_DEPL_LOG are active immediately when you installsoftware component version EA-DFPS 603. These functions enhance theprevious functional scope of the EA-DFPS software component withoutrequiring additional activation steps. For this reason, no test catalog isavailable for this business function.

For more information about such business functions:

Verify the Master Guide of the particular SAP Solution, or Application In this particular case, refer to the Master Guide for SAP for Defense

& Security, on SAP Service Marketplace athttp://service.sap.com/instguides

3.4.1 Phase 1: Planning the EnhancementPackage InstallationOverview




80 February, 2009

The starting point for the installation of an enhancement package is the decision regardingwhich new business function you want to support in your system landscape. The decisionprocess is as follows:

Get the information from your business experts about all business functions whichthey intend to use in a business process.

With the information about the required business functions you are able to identifythe following information:

The generic business processes assigned to the business function

Before installing the enhancement package, you need to verify whether all requiredsystems are available in your landscape, or whether you would need to extend yourexisting system landscape before installing the enhancement package. The genericbusiness processes, the process component list/software component matrix and theSAP Library documentation for the business function support you with thisinformation.

The associated Technical Usage(s)

SAP has assigned business functions to Technical Usages. These combine allsoftware components, which are required to operate the business function. In theinstallation process for the enhancement package, you need to identify the businessfunction by means of the assigned Technical Usages. In particular, you use theTechnical Usages in the Maintenance Optimizer for the definition of the downloadbasket and installation scope. Furthermore, you use the technical usage in thesoftware component matrix to verify the relation to the generic business processesand role-based work centers used.

Recommendations and Further Information For an overview of the enhancement package data-model, see Software

Architecture.

For information about the business view, see SAP Service Marketplace athttp://service.sap.com/erp-ehp.

For information about the mapping of generic business processes to softwarecomponents or product instances, and for the required system instances, see SAPService Marketplace at http://service.sap.com/scl.

For detailed documentation on the business functions and their activation, seesection Business Function Sets and Business Functions in the SAP Library forenhancement package for SAP ERP available at help.sap.com, under ERPSAP ERP Central Component.

Planning StepsIn the following table, you see one possible resulting sequence when planning the installationof the enhancement package in the Individual System Landscape for SAP ERP. Keep in mindthat it is possible to change the order of the installation sequences up to a certain extend.

Table 11: Planning the Installation of the SAP enhancement package 4 for SAP ERP

Step Activity

1 Predefine the resulting system landscapeThe current enhancement package supports different installation options andsystem landscape alternatives.

With the Easy Adoption system landscape, you keep the system




81 February, 2009

Step Activityinstances on usage type AS Java stable on SAP NetWeaver 7.0, whileyou update the system instances on AS ABAP with the enhancementpackage 1 for SAP NetWeaver 7.0.

In the Continuous Innovation system landscape, you update both ofthese usage types with the enhancement package 1 for SAPNetWeaver 7.0.

The availability of these options is important, if you install the enhancementpackage for SAP ERP together with other SAP applications, or if you employ asystem landscape, which consist of a mixture of system instances on usagetype AS ABAP and AS Java.

With the Easy Adoption path, the installation of the enhancementpackage does not change the SAP NetWeaver version of systeminstances on usage type AS Java. Thus, this installation path requiresless effort than the Continuous Innovation path. SAP recommends it asan alternative for upgrades, in which productive SAP NetWeaver 7.0system instances already exist in the system landscape.

Seen from the functional perspective, the Continuous Innovation pathoffers a target system landscape with a greater functional richness inSAP NetWeaver, than the Easy Adoption path does. SAP recommendsit for new installations, or for upgrades, which start without productivesystem instances on AS Java.

Recommendations and Further InformationFor more information about

The product versions see Integration into Overall Architecture

The installation tools, see Installation and Upgrade

The system landscapes alternatives in the Business Suite context seePlanning and Optimizing System Landscapes.

2 Identification of software components to installAfter you know the required business functions, you need to identify thesoftware components, which you need to install.

You map the business function(s) to the corresponding Technical Usage(s), byusing the following SAP Note as source of information:




Depending on the particular business function, a Technical Usage groups thefollowing types of software components:

ABAP software components

Java software components

Portal content

XI Content

3 Identification of software components for optional


82 February, 2009

Step Activityenablement for the Service-Oriented Architecture (SOA)You service-enable the system instances in the following steps:

Step 1: Identification of software components/technical usages andrelated business functions, which you intend to install or use. SAP hasgrouped these entities by means of Enterprise Services Bundles.

Step 2: Selection of the technical usages and installation of the serviceenabling software components together with the other parts of theenhancement package

Note that not each service interfaces is assigned a business function/technicalusage. In these cases, you need to install the software components without thesupport, offered by the technical usage grouping.

Recommendations and Further InformationFor more information about

Enablement for the Service-Oriented Architecture (SOA), refer to 4.3Enterprise SOA.

Assignment of software components to Enterprise Service Bundles,see SAP Note 1224284.

4 Verification and OptimizationWe recommend that you take the following steps in order to verify and optimizeyour plan:

Verify the installation scope for potential Installation constraints.Installation constraints might apply particularly with Add-On solutions.

You might be interested in installing a business function for a businessprocess, which you have not yet implemented in your systemlandscape. In this case, you need to verify that all necessary systeminstances are available prior to installing the technical usages/ softwarecomponents. If a required system instance is not available, you need tore-plan and extend your system landscape first.

If you do not use the full functional scope of a generic businessprocess/role-based Work Center from SAP, it is possible to optimizethe installation scope. This step requires a deeper analysis of yourparticular installation, and the functional capabilities of the businessfunctions selected.

Recommendations and Further InformationIf you have an Add-On installed in your system, refer to the followinginformation:

Add-On solutions from SAP

o SAP enhancement package 3 for SAP ERP 6.0: SAP note1117309

o SAP enhancement package 4 for SAP ERP 6.0: SAP note1226284

o Section 4 Solution-Wide Topics

Other Add-Ons: Verify that the Add-On is compatible with the


83 February, 2009

Step Activityenhancement package

For more information about the availability of all required systeminstances, and possible detail optimizations, see 3.2 SoftwareComponent Matrix, and see 4 Solution-Wide Topics

The documentation of the business function in the help portal help.sap.com,contains the following information

New features delivered by a business function

Technical usages and additional technical product instances requiredfor the respective feature.

The information in the SAP Library helps you to specify the information laid outin the Process and Scenario Component list. It furthermore allows you tonarrow down the set of product instances that you need to update or install inorder to be able to consume the new feature.

5 PrerequisitesThe Solution Manager – Maintenance Optimizer supports you with theinstallation of an enhancement package. Make sure that:

You have a SAP Solution Manager 7.0 system with the highest supportpackage level available in your system landscape

You maintain your system landscape in the Solution Manager system(see in the SAP Library help.sap.com -> SAP Solutions -> SAPSolution Manager)

The installation of enhancement packages requires the availability of thedefined minimum support package stack (or higher) in your SAP ERP systemlandscape. In order to save effort, SAP recommends that you include theinstallation of the required support package stack in the same installationqueue that you will use to install the enhancement package.

Further Information For minimum Support Package requirements, see SAP Note 1165437.

Use the Solution Manager – Maintenance Optimizer to calculate therequired support packages, and to assign them to the import queue. Ifyou do not use this support tool for installing the enhancementpackage make sure, to take care of the required Support Packagewithout further tool support.

For additional documentation of the Solution Manager - MaintenanceOptimizer refer to SAP Note 1155041.

3.4.2 Phase 2: Enhancement PackageInstallationOverview


84 February, 2009

Technical usages group software components, and are assigned to business functions. Afteryou have planned the installation scope, you install the technical usages that enable thosebusiness functions, which you intend to use. The installation consists of the following steps:

In order to download the software components and prepare the installation: Use theMaintenance Optimizer of the SAP Solution Manager to select, download, and installthe required Technical Usages, or software components and the required supportpackages.

Up to and including enhancement package 3 for SAP ERP 6.0,you use theinstallation tools:

Transaction SAINT (SAP Add-On Installation Tool)

Java Support Package Manager (JSPM)

As of enhancement package 4 for SAP ERP 6.0, the following changes apply (seeSection 2.3 Installation and Upgrade):

A new enhancement-package-installation-tool is available, which fulfills thesame role than these previously separate transactions. The installation path(Easy Adoption versus Continuous Innovation), and the operating systemparameters (32 bit/ 64 bit), defines, if you use the new tool or the existingtools (see Section Installation and Upgrade).

Normally you install software components from the current enhancementpackage. Under certain conditions and depending on the target systemlandscape, a two-step approach is required now. It consists of the steps

Installation of enhancement package 3 for SAP ERP 6.0

Installation of enhancement package 4 for SAP ERP 6.0

Installation StepsThe following table shows the resulting sequence when planning the installation of theenhancement package in the Individual System Landscape for SAP ERP.

Table 12: Installation Procedure SAP enhancement package 4 for SAP ERP (Installation Step)

Step Activity

1 Install the ABAP Add-OnsUp to and including enhancement package 3 for SAP ERP you use transactionSAINT (SAP Add-On Installation Tool) to install ABAP Add-Ons. As ofenhancement package 4 for SAP ERP, the tool-choice partly depends on theinstallation path. Normally, you use the new Enhancement Package installertool (SAPehpi) to achieve the following:

Install or update ABAP software components for the currentenhancement package on your system instances

Apply the required Support Packages

Under certain conditions, you cannot use the SAPehpi (see Installation andUpgrade for more information). In these exceptional cases, you continue towork with the former SAINT.

The installation tools are capable of using the XML document as an input,which you have generated by the Solution Manager Maintenance Optimizer.

Further Information


85 February, 2009

Step Activity

For more information, see the following SAP Notes, and documentation:

1150349 ECC-SE 604 Add-On Installation

1150350 Upgrade to SAP ECC 600 with Add-On ECC-SE 604

1143022 Installation Enhancement Package 4 on SAP ECC 600

1165437 Enhancement package 4 for SAP ERP: Required supportpackages

Documentation for transaction SAINT (SAP Add-On Installation Tool),or SAPehpi, as described in Section 2.3 Installation and Upgrade

Minimum Support Package requirements for SAP ERP 6.0 as by SAPNote 849887

2 Install the Java components and Business PackagesThe installation process for Java components differs by enhancement package:

Up to and including enhancement package 3 for SAP ERP, or wheninstalling the enhancement package in system instances with SAPNetWeaver 7.0 usage type AS Java (Easy Adoption approach), youuse the Java Support Package Manager (JSPM).

As of the current enhancement package, you use the newEnhancement Package installer tool, when installing the enhancementpackage 1 for SAP NetWeaver 7.0 in your system instances withusage type AS Java (Continuous Innovation approach).

You can use these tools to update Java software components and to installPortal Content for the current enhancement package in your system instances:

The installation tools are capable of using the XML document, whichyou have generated with the Solution Manager Maintenance Optimizer.

You need to make sure to have the software archives in place beforeyou start the update.

Product Instance Portal Content includes all Business Packages for thespecific enhancement package. SAP recommends that you install thecomplete portal content product instances. Alternatively, and inselected cases, it is possible to concentrate on the required BusinessPackages, and to reduce the system size. This requires from you adeeper knowledge of the assignment between functional areas andbusiness package.

You install business packages in the system instance in any orderwithout removing prior versions from this instance.

Further InformationFor more information, refer to:

For the installation procedure, see SAP Note 1160106 , 1165442, or1057498 (depending on the enhancement package), and see theinstallation or upgrade guides on SAP Service Marketplace athttp://service.sap.com/erp-inst

For the Java Support Package Manager (JSPM), and the newEnhancement Package installer tool, see Section Installation and



86 February, 2009

Step ActivityUpgrade

For the installation of individual business packages, see SectionContent Instances

Section 2.3 Installation and Upgrade for recommendations aboutfurther applicable installation tools

3 Install the XI Content packagesNormally, you install the XI Content packages of the current enhancementpackage on the system instance with SAP NW – Process Integration.

Product Instance ESR Content includes XI content for the SOA enablement ofSAP ERP 6.0. In order to install packages from product instance ESR Content,you first need to install a system with usage type Process Integration based onSAP NetWeaver 7.10.

In addition, you need to configure the SAP NetWeaver integration directory,and you need to configure the connectivity between the back-end system andthe system with product instance SAP NW – Process Integration.

Further InformationFor more information refer to the following documentation:

For information on the installation procedure for XI Content, see SAPNote 836200 - SAP NetWeaver 7.0: Importing process integrationcontent

For information about steps to install SAP NetWeaver 7.10, see thecorresponding Master Guide for SAP NetWeaver, on SAP ServiceMarketplace at http://service.sap.com/instguides

The configuration of the SAP NetWeaver integration directory isdescribed in the SAP Library help.sap.com SAP NetWeaver 7.0—> SAP NetWeaver 7.0 (2004s) —> SAP NetWeaver Library —>Technology Consultant’s Guide —> Enabling Application-to-ApplicationProcesses —> Application-to-Application Integration —> Configurationof Usage Type Process Integration —> Configuration of BusinessSystems with an Integration Engine.

The configuration of the connectivity between back-end system and thesystem with SAP NW Process Integration is found in the SAP Libraryhelp.sap.com —> SAP NetWeaver 7.0 —> SAP NetWeaver 7.0(2004s) —> SAP NetWeaver Library —> Technology Consultant’sGuide —> Enabling Application-to-Application Processes —>Application-to-Application Integration —> Configuration of Usage TypeProcess Integration —> Configuration of Business Systems with anIntegration Engine.

4 SAP LibraryThe SAP Library includes the documentation for the enhancement packages.In particular, the SAP Library includes information about the new and changedbusiness functions.

You need to install the extended version of the SAP Library in eachsystem instance where you plan to use the business functions.

It is possible to update your SAP Library in specific relation to the



87 February, 2009

Step Activitybusiness functions you have activated.

By means of the new Help Center, it is possible to choose an alternativemethod to present SAP Library information to the user.

Further Information SAP Note 1066110 includes the instructions to install the SAP Library.

More information about the Help Center is found in the releaseinformation SAP enhancement package 1 for SAP NetWeaver 7.0 inhelp.sap.com SAP NetWeaver SAP enhancement package 1for SAP NetWeaver What's New - Release Notes.

5 Installation Step 5 (optional): SAP Industry ScenariosSAP industry solutions function widely with SAP ERP 6.0 and theenhancements available from the different enhancement packages.

Certain SAP Industry Scenarios require functions from both, SAP ERP andother SAP Business Suite Applications. In such cases, it might be necessary toinstall further system instances in your system landscape.

Further InformationFor more information about:

SAP industry solution scenarios, see Section Generic BusinessProcesses, Scenarios and Role-Based Work Centers

Installing additional components for the SAP industry solutions, see theMaster Guide for the corresponding solution or application, on SAPService Marketplace at http://service.sap.com/instguides

6 Front-End Component Installation (optional)If you are enhancing the scope of your system landscape by means of theenhancement package, you need to make sure that you install all requiredFront-End components, such as the SAP GUI, as well.

Several functions, such as the PLM Web User Interface run with alternativeclient system instances. This includes systems with product instances SAP NW– EP Core, or with the SAP NetWeaver Business Client, and they third partyviewers might be required.

Further InformationFor more information refer to:

The different Front-End components available with SAP ERP 6.0, seethe Master Guide SAP ERP 6.0 on SAP Service Marketplace athttp://service.sap.com/erp-inst

For the SAP NetWeaver Business Client, see Product Instance: SAPFrontend Business Client

For the third party viewers see Additional and Third-Party Products

3.4.3 Phase 3: Enhancement Package Testingand Activation




88 February, 2009

OverviewAfter you have installed the enhancement package, you need to activate the deliveries and toconfigure them for productive use. SAP recommends that you test a business function,before you activate a business function. Test Case Templates are available to support youwith that task.

Note, that you can reverse neither the installation of technical usages for a businessfunction, nor the activation of business functions.

Testing and Activation ActivitiesThe following activities are required to test and activate the new functions.

Table 13: Testing and Activation enhancement packages

Step Activity

1 TestingSAP makes test case templates available for the business functions deliveredwith the enhancement packages. These test case templates provide examplesof how you can test the new functions before activation. You can add furthertest cases.

The test case templates help you to reduce the implementation time andefforts. The use of test case templates gives you the following advantages:

Using the test case description, you can find out how to test the newfunctions and what you have to consider.

You can plan your tests using the test case templates and calculate theefforts accordingly.

You can prepare the content of the tests, for example, by creating thetest data required.

You can access the test case templates in transaction SFW5. From there youcan navigate to the related SAP test case catalog for each business function.

ActivitiesProceed as follows to get information about the individual business functionsusing the SAP test catalog:

Call transaction SFW5. You access the transaction from theImplementation Guide under Activate Business Functions.

In the Test Catalog column, select the test catalog that you wantinformation about (The application Display Test Catalog <topic>appears).

Open the descriptions for the respective test cases.

Documentation References For general information about the use of test cases, see the SAP

NetWeaver Library help.sap.com by using the search term TestWorkbench.

For information about using the test case templates for the businessfunctions, see the introductory documentation for the enhancementpackages. You can access this information in transaction SFW5 bycalling up the documentation of a business function and expanding the


89 February, 2009

Step Activityintroductory section.

2 ActivationYou need to activate the deliveries and configure them for productive use.

Note, that you cannot reverse the activation of business functions.

Documentation ReferenceFor more information about activation see:

Section New Enhancement Package Delivery Architecture

Review the corresponding Installation or Upgrade Guides on SAPService Marketplace at http://service.sap.com/erp-inst, orhttp://service.sap.com/instguides



4 Solution-Wide Topics

90 February, 2009

4 Solution-Wide TopicsThe installation of an enhancement package is highly automated. In the current section youcan find information, which is relevant to your Installation project on a case to case basis or,which helps you to understand the software architecture. This information is helpful in specialcases including:

Planning and Optimizing System Landscapes

Generic Business Processes, Scenarios and Role-Based Work Centers

Service-Oriented Architecture (SOA)

Add-On Products

Software Architecture

4.1 Planning and Optimizing SystemLandscapes4.1.1 The Enhancement Package in a SAPBusiness Suite System LandscapePurposeSystem landscapes and the optimum system-landscape-layout depend on the customerneeds and enhancement package Installation strategy. With the current enhancementpackage, reference landscapes for the SAP Business Suite are available which focus on asystem setup for SAP ERP together with other applications.

The next section introduces the following reference system landscapes and highlights themain differences between them in terms of the current enhancement package:

Reference Landscape for easy adoption

Reference Landscape for continuous innovation

The enhancement package 4 for SAP ERP 6.0 requires system instances based onenhancement package 1 for SAP NetWeaver 7.0. The System Administrator needs thefollowing information when defining the layout of the complete application, or when identifyingthe most relevant additional documentation.

4.1.1.1 Reference System Landscape for EasyAdoptionOverviewThe following figure shows the reference system landscape for Easy Adoption for the SAPBusiness Suite.


91 February, 2009

Figure 3: Reference System Landscape for Easy Adoption - SAP Business Suite

You see in this figure that you can distribute the SAP Business Suite to several centralsystem instances of the following types:

Separate business oriented system instances, such as for the different SAPapplications, such as SAP ERP, or SAP SRM (based on usage type AS ABAP)

Central supporting SAP NetWeaver system instances, such as system instances withthe SAP NetWeaver usage types EP Core, or Process Integration (based on theusage types AS ABAP or AS Java)

Central Solution Management system instances (SAP Solution Manager)

Presentation clients

In the typical SAP Business Suite system landscape, the different system instances reside ondifferent SAP NetWeaver Versions. The following release levels are possible in this referencesystem landscape:

Systems based on SAP NetWeaver 7.0

SAP NetWeaver 7.0 systems with enhancement package 1 for SAP NetWeaver 7.0

Systems based on SAP NetWeaver 7.10

You can verify that the individual system landscape of SAP ERP is in fact a subset of thesystem landscapes for Easy Adoption, or Continuous Innovation. The installation of theenhancement package alters the following system instances of the SAP Business Suitereference system landscape

SAP ERP

SAP NetWeaver


92 February, 2009

Frontend Clients

Characteristics of the Reference Landscape for Easy AdoptionThe landscape for Easy Adoption keeps most of the SAP NetWeaver system instances stableon SAP NetWeaver 7.0 as delivered with SAP ERP 6.0. You only need to update the differentSAP Business Suite-system-instances on usage type AS-ABAP with the enhancementpackage 1 for SAP NetWeaver 7.0.

You can see this system landscape as the default option for existing SAP ERP customers inupgrade, because the AS Java based system instances are not affected.

Alternatively, customers willing to use SAP NetWeaver innovation based on enhancementpackages for SAP NetWeaver can upgrade their system instances to the correspondingenhancement package for SAP NetWeaver 7.0, or to SAP NetWeaver 7.10.

4.1.1.2 Reference Landscape for ContinuousInnovationOverviewThe Reference Landscape for Continuous Innovation includes the same system instances asthe Reference Landscape for Easy Adoption. However, in contrast to it, the landscape forcontinuous innovation is built on the principle that the complete landscape including all SAPNetWeaver system instances run on the same enhancement package for SAP NetWeaver7.0 release on which all new functionality based on the Business Suite 7.0 core processescan be used.

All system instances will be available in the latest available version after you have installedthe enhancement package. Thus, we see the Continuous Innovation System Landscape asthe default for all customers who upgrade to or install SAP ERP 6.0 and the currentenhancement package the first time.

Figure 4: Reference System Landscape for Continuous Innovation - SAP BusinessSuite


93 February, 2009

4.1.2 General Planning ApproachOverviewAs explained in the Master Guide for SAP ERP 6.0, we have structured SAP ERP for genericbusiness processes and Role-Based Work Centers. Different product versions, productinstances, software components and software component versions are required when youintent to install the SAP ERP completely. A customer-specific system landscape is plannedindividually taking account of the supported scenarios, processes, or Role-Based WorkCenters and the business functions selected.

You need to consider the following inter-relations between existing system landscapes andenhancements from enhancement packages:

In cases where a part of an enhancement package is installed, which would extendthe existing functional reach of SAP ERP installed, it may be necessary to installother parts from SAP ERP 6.0, before it is possible to install the product instancefrom the enhancement package.

In other cases, it might be possible to optimize the installation scope, if you do notuse the full functional scope of a generic business process/role-based Work Center,and so to install less software components than are generally necessary.

These optimizations require information about the planning approach, the softwarearchitecture, and the relation between business functions and generic businessprocesses/Role-Based Work Centers.


94 February, 2009

Planning ApproachEach generic business process and Role-Based Work Center supported by SAP ERPrequires a number of software components and product instances to function. You initiallyneed to plan the overall system landscape around these required objects.

The easiest way would be to install SAP ERP and the enhancement package completely.However, this approach is not recommendable for several reasons. SAP recommendsnarrowing down the system landscape to the necessary parts as follows:

When starting from scratch, the installation of a specific process or a specific Role-Based Work Center of an enhancement package for SAP ERP starts with theidentification of product instances required by this specific process or Role-BasedWork Center. Either these can be product instances taken from product version SAPERP 6.0 or it can be general product instances from the product versions for theenhancement package.

Business functions extend the scope of these processes or role-based Work-Centers. Under certain conditions, it is possible to optimize the installation scope.The steps are as follows:

Identification of the recommended product instances and softwarecomponents

Verification of the release notes of the particular business function, and theSAP Library documentation for the business function in order to identify therequired software components for the business function

With this information you are able to decide, which system instances, youactually need to implement

You then install the product instances from the product version for the currentenhancement package. Note that:

Unchanged product instances of product version SAP ERP 6.0 are not partof delivery for a specific enhancement package. They need to be installedseparately from the SAP ERP 6.0 installation and must be patched to thecorrect Support Package level

Certain SAP Industry Scenarios might require software components that donot belong to product version SAP ERP 6.0 or a specific product version foran enhancement package for SAP ERP. These components must be madeavailable as described in separate documentation

The same but in the opposite direction might hold for other applications thatrequire specific software components from SAP ERP to function

Documentation ReferencesFor more information related to the optional planning and optimization step, see the followinginformation sources:

Release notes in SAP Service Marketplace athttp://service.sap.com/releasenotes

Documentation of the business functions in Business Function Sets and BusinessFunctions in the SAP Library for the enhancement package for SAP ERP available athelp.sap.com, under ERP SAP ERP Central Component

The recommendations in 3 Software Units, Systems and Installation with regards tothe required portal content

Scenario Description and Configuration Documentation in the documentation of theSAP Solution Manager

http://service.sap.com/releasenotes


95 February, 2009

Documentation of software component/product instance for a process or scenario inSAP Service Marketplace at http://service.sap.com/scl

Information about dependencies between component lists (SAP Note 824757)

The Master Guide for SAP ERP 6.0 on SAP Service Marketplace athttp://service.sap.com/erp-inst describes the installation of SAP ERP 6.0and it provides examples of the different system landscape alternatives

Master Guide for the corresponding SAP Industry solution for the various scenariosavailable for each industry on SAP Service Marketplace athttp://service.sap.com/instguides (scenarios and their Installation)

For more information about the installation of other SAP Applications, see SAPService Marketplace at http://service.sap.com/instguides

Technology Consultant’s Guide in the SAP Library help.sap.com Help Portal:help.sap.com —> SAP NetWeaver 7.0 —> SAP NetWeaver 7.0 (2004s) —> SAPNetWeaver Library —> Technology Consultant’s Guide

Information Center for enhancement packages for SAP ERP on SAP ServiceMarketplace at http://service.sap.com/erp-ehp

4.2 Generic Business Processes,Scenarios and Role-Based Work Centers4.2.1 Processes and Role-Based Work Centerswith EnhancementsOverviewThe use of a particular business function in an enhancement package either alters an existinggeneric SAP ERP process/role-based Work Center or it leads to the installation of a new one.As enhancement packages are cumulative, all focus topics from prior enhancementpackages are part of the current enhancement package.

In order to plan the system landscape, information about the new, changed or enhancedgeneric business processes, or role-based work centers is required. Some of these role-based work centers have specific requirements.

Technical PrerequisitesDepending on the processes involved, different product instances of SAP ERP 6.0 and of thecurrent enhancement package need to be available. The Process and Scenario ComponentLists, includes a documentation guide for each SAP ERP generic business process/role-based Work Center.

The following special requirements exist:

HR Administrator

Web Dynpro is a client-independent programming model of the SAP NetWeavertechnology platform for developing user interfaces for professional businessapplications. It relates on the model-view controller-paradigm. This paradigmseparates the business logic from the presentation logic. This architecture is visible inthe Web Dynpro perspective of the SAP NetWeaver Developer Studio (NWDS)

SAP has changed the user interface technology for the role-based Work Center HRAdministrator as of enhancement package 1 for SAP ERP 6.0. More specifically,







96 February, 2009

SAP changed the Web Dynpro Java technology to the Web Dynpro for ABAPtechnology. Since developments for these technologies are part of different productinstances of the product versions SAP ERP 6.0 or SAP Enhance Package 2005.2(Java Web Dynpro is part of SAP XSS (Self Services), and ABAP Dynpro is part ofSAP ECC), this change affects the system landscape and the Installation or upgradeof systems, where the role-based Work Center HR Administrator is used

Globalization and UnicodeYou can implement generic business processes/Role-Based Works Center globally. Certaingeneric business processes and Role-Based Work Centers include country specificadoptions, so that exceptions to this rule may exist. When you plan to use such an entityglobally, you need to clarify the following questions first:

Is the business process/Role-Based Work Center available to each country that yousuppose to support with the corresponding business function?

Is the generic business process/Role-Based Work Center available in the relevantlanguage?

The use of multiple languages for internal or external systems often leads to problems ofcharacter recognition. If you employ truly global business processes, you will need to supportlocal language characters. SAP applications support the Unicode standard to aid yourglobalization and localization efforts and SAP highly recommends you to install only Unicode-based systems. Non-Unicode systems can only run one code page, limiting the languageusage to English and the additional language(s) available for the given code page. Thesolution does not support code page combinations.

Documentation ReferencesFor more information about the following documentation, see the reference given:

The generic business processes or the Role-Based Work Centers of SAP ERP thatare created, changed or enhanced with the different enhancement packages can befound in the following path in SAP Service Marketplacehttp://service.sap.com/erp-ehp - > Media Library - SAP enhancementpackages -> Category Enhancement Packages - General.

For information about software components, which are required for specificprocesses or role-based Work Centers see

Section Software Component Matrix

SAP Service Marketplace at http://service.sap.com/scl Processand Scenario Component List.

The Master Guide for SAP ERP 6.0 on SAP Service Marketplacehttp://service.sap.com/erp-inst explains the overall globalization conceptfor SAP ERP. For more information about the country and language availability ofindividual generic business processes/Role-Based Work Centers, see SAP Note883072.

The documentation about the assignment between generic business processes/Role-Based Work Centers and business functions is located in the SAP ServiceMarketplace at http://service.sap.com/erp-ehp.

The HR Administrator, see SAP Service Marketplace athttp://service.sap.com/notes SAP Note 1024326 (New Applications forrole HR Administrator).







97 February, 2009

For more information about the Unicode advantages, see SAP Service Marketplaceat http://service.sap.com/Unicode, andhttp://service.sap.com/Unicode@SAP.

For more information about the upgrade of Unicode systems, see the UpgradeMaster Guide SAP ERP 6.0 from SAP Service Marketplace athttp://service.sap.com/erp-inst, and see SAP Note 928729Combined Upgrade & Unicode Conversion FAQ

4.2.2 Role-Based Work Centers and AutomaticRolesOverviewEmployees typically have one or more roles in the enterprise. SAP ERP supports the role-based work approach by means of portal roles. A role in the portal enables you to access theapplications and transactions that are required to carry out the tasks of a particular role in theenterprise. You can access the applications and transactions as services in the portalregardless of which back-end system they are located in.

Roles provide simple, direct access to the services they use,regardless of the system, used to run the services.

A role can comprise of several work centers, which bundle theservices for a particular task within a role. Therefore, a work center isthe starting point for an employee’s work in a particular task area.From a technical point of view, a Role-Based Work Center is aWorkset, which is included in the Business Package.

Beginning with enhancement package 1 for SAP ERP 6.0, SAP has as follows enhanced andsimplified the role-based access to functions of product version SAP ERP 6.0:

Introduction of Automatic Roles

New Role-Based Work Centers

Simplification of the system landscape requirements for the use of Role-Based WorkCenters

Automatic RolesRole-based access offers the following features:

Upload roles (BC-SEC-USR) into the SAP NW - EP Core System/SAP NW -Enterprise Portal System and display them using the Service Map.

An enhanced tool allows you to upload the roles maintained in transaction PFCG ofproduct instance SAP ECC into the SAP NW - EP Core System/SAP NW - EnterprisePortal System. This enables customers to re-use any investments in role definitionsmade in SAP ECC. If these roles comply with certain rules, such as using hierarchieswith no more than five levels, it is possible to display the uploaded roles as ServiceMaps in the SAP NW - EP Core System/SAP NW - Enterprise Portal System. ServiceMaps can contain icons and explanatory texts for (groups of) applications.

Set standard Automatic Roles ready for upload out-of-the-box.

A predefined set of new standard roles is available that can be displayed andmaintained in transaction PFCG. You can directly upload PFCG roles to the SAP NW- EP Core System/SAP NW - Enterprise Portal System. There you can display themas Service Maps. These Automatic Roles already contain icons and explanatory texts

http://service.sap.com/Unicode

http://service.sap.com/Unicode@SAP



98 February, 2009

and they can act as the perfect starting point for providing role-based access for endusers.

SAP ships a set of standard work centers ready for use out-of-the-box.

In product versions for enhancement package 1 for SAP ERP 6.0, SAP ships anumber of Role-Based Work Centers. Role-Based Work Centers complement amenu-based approach, where users pick their applications from a hierarchical list. Inaddition, they actively present information to users. The users use this information inorder organize their work. For example, there are work lists that inform the user ofbusiness objects that need to be processed or key performance indicators requiringtheir attention.

You can use the roles and work centers shipped with product version SAP ERP 6.0together with usage type Enterprise Portal (EP) Core.

As of Support Package 08 of the product version SAP ERP 6.0, you can run all Role-Based Work Centers using the new lean SAP NetWeaver usage type EP Core. Thisusage type is part of the new SAP NW – EP Core product instance. If you choosethis usage type, you do not need to run the richer SAP NetWeaver usage typeEnterprise Portal. Keep in mind, that you can also run the uploaded authorizationroles mentioned above with SAP NW - EP Core.

You can change Standard Automatic Roles before you upload them.

You can copy and change all standard Automatic Roles before you upload them tothe SAP NW - EP Core System/SAP NW - Enterprise Portal System. This allows youto create own company-specific roles starting from the rich set of predefined rolesand is thus a valuable starting point for providing role-based access for many endusers.

Customers can change or enhance the standard work centers.

You can copy and change all SAP standard work centers to meet company-specificneeds. SAP provides Generic Work Center building blocks, such as the PersonalObject Work List or the Generic Key Figure Monitor, which you can use to change oradd more information actively presented to the user.

Customers can evolve their uploaded authorization roles into full work centers.

After uploading their company-specific roles from SAP ECC to the SAP NW - EPCore System/SAP NW - Enterprise Portal System, customers can use the genericwork center building blocks mentioned above to develop menu-centered roles into fullwork centers that help users to organize their work.

SAP NetWeaver Business ClientAs of enhancement package 2 for SAP ERP 6.0, the SAP NetWeaver Business Client isavailable. You can use the newest SAP NetWeaver Business Client as an alternative to theSAP NetWeaver portal client to access business applications.

The SAP NetWeaver Business Client offers role-based access to the SAP ERP applicationand other SAP and Web-applications and can render Automatic Roles and Role-Based WorkCenters.The current enhancement package includes the business function ‘SAP All-in-One Roles’,which adds further roles and user interfaces for users in small and midsize companies in theareas of accounting, controlling, materials management, production planning, or sales anddistribution. These enhancements require the SAP NetWeaver Business Client.

Technical PrerequisitesYou must create and assign roles to user master records before you can use the SAPSystem. You can only log on to the system if you have a user master record. Both, a user


99 February, 2009

menu and authorizations are assigned to the user master record by means of one or morecomposite roles, or single roles.

Documentation ReferencesFor more information about Automatic Roles, see the following:

SAP Library, at help.sap.com, under mySAP ERP SAP ERP CentralComponent SAP ERP Central Component Roles in the Backend-System

SAP Service Marketplace at http://service.sap.com/notes SAP Note1000291

For more information regarding:

Overall role concept, see the SAP Library, at help.sap.com, under SAP ERPCentral Component Business Packages (Portal Content) Role and Work CenterConcept

SAP system authorization concept, see the SAP Library, at help.sap.com, underBasis Components Computing Center Management System BC Users andRoles

4.2.3 Industry Solution Scenarios in SAPenhancement package 4 for SAP ERP 6.0OverviewSAP uses scenarios in order to structure SAP Industry Solutions. These scenarios caninclude and extend processes of SAP ERP. The following section helps you as the systemadministrator to identify the SAP Industry Solutions with deliverables in the enhancementpackage. Separate documentation is available, which describes the SAP Industry Solutionsand their specific installation-needs.

Table 14: SAP Industry Solutions

SAP IndustrySolution

Development in the area of the Scenario As of SAPenhancementpackage <n>for SAP ERP

Asset Life-Cycle Management, MaintenanceProgram Management, Heavy Maintenance, LineMaintenance, Service Parts Management

2SAP for Aerospace& Defense

Contract & Order Management, ProjectManufacturing, Program Management

3, 4

Enterprise Asset Management, Make-to-Order/Make-to-stock, Supply-to-line, OutboundLogistics, Sales Order Management, Sales andMarketing Handover/takeover A&D, LeanMaintenance, Web-Based Supplier Kanban, DetailedDesign with Collaboration

2, 4SAP for Automotive

Service Parts Planning (BU SAM) with ERP2005 3SAP for ConsumerProducts

DSD Paper-Based 3



100 February, 2009



SAP for Defense &Security

Basic Organization, Controlling and Analysis,Deployment, Equipment Management, LocalityManagement, Management of System Landscape,Personnel Management, Replenishment, UnitMaintenance, Vehicle Fleet Management

3

SAP for HigherEducation

Recruitment & Admission 4

SAP for Insurance Claims Handling and Fulfillment, Claims Recovery,Customer Billing and Payment, Portfolio Accounting,Portfolio Controlling, Portfolio Management, SalesForce Management, Statutory Reporting, PortfolioManagement; Portfolio Accounting PortfolioControlling, Sales Quantity Planning

3, 4

SAP for Media Press Distribution Various new processes, SalesQuantity Planning

2, 4

SAP for MillProducts

Change to billing documents handling 2

SAP for PublicSector

Public Services - Expenditure Certification; GrantsManagement, US–Federal: Financial SystemsIntegration Office, Collections Management (requiresSAP CRM), Budget Execution, Grants Managementfor Grantor, Fund Accounting, Receivables andPayables Management

1,2

SAP forProfessionalServices

Invoice Management 3

Inventory Management, Multilevel Replenishment,Commodity Trading, Purchase Order Management,Retail Master Data Management, Store & POSAnalytics, Trading Contract Management with FastData Entry, Trade Promotion Management

1,2

Allocation, Merchandise & Assortment Planning 1,2,4In-Store Merchandise and Inventory Management,Store Connectivity,

1,2,3,4

Cross Channel Customer Order Management, ItemManagement

3

SAP for Retail

Chain Wide Inventory Management, Fresh ItemProcurement, Item Management, OperationalBuying, Trade&Commodity Management,Merchandise Distribution in WarehouseManagement, Pooled Payment

4

Billing, Invoicing and Presentment, Operations andMaintenance

2SAP forTelecommunications

Receivables Management and Payment Handling,Bill Calculation, Creating and Posting Invoice

4


101 February, 2009



Grid Maintenance and Operations (CompatibleUnits), Plant Maintenance and Operations (dependsin resource situation and allocation), Energy DataManagement, Energy Settlement, ElectronicCustomer Services, Receivables Management andPayment Handling, Credit Risk & CollectionsManagement, Change of Supplier

SAP ERP with SAP CRMExtended Customer Services and Sales in theInteraction Center, Sales Management forCommercial & Industrial Customers, CustomerService in the Interaction Center

2

Receivables Management and Payment Handling 2,4

SAP for Utilities

Billing-Relevant Device and Measurement DataManagement, Registration for Grid Usage, Selling ofEnergy Supply Products, Grid Usage InvoiceVerification and Payment

4

SAP for Waste &Recycling

Weighing, Container Services 2

Chargeback and Rebate Management, Demand andSupply Planning, Rebate Management

2SAP for WholesaleDistribution

Trade & Commodity Management, Purchasing,Warehouse Management

2,3

Technical PrerequisitesNormally, you install SAP Industry Solutions in system landscapes capable ofaccommodating SAP ERP 6.0. Certain scenarios might require the installation of softwarecomponents from other SAP Business Suite Applications and thus a SAP Business SuiteSystem Landscape.

The following are examples of special requirements that may exist:

The enhancement package 1 for SAP ERP 6.0 has introduced the product instanceSAP FinServ Claims Mgmt (software component IS-FS-CM). This product instance isnot available in Enhancement Package 2005.2 or in subsequent product versions.For the functional perspective and the corresponding SAP Industry scenarios refer tothe deliveries with product version SAP ERP 6.0.

Further Information For more information about the SAP industry solutions, see SAP Service

Marketplace at http://service.sap.com/industries.

The Master Guides for SAP ERP 6.0 include generic information about industrysolutions, mainly to do with activation or upgrade.

The SAP Industry Master Guides available for the specific enhancement packagesconcentrate on industry-specific information. For more information, see SAP Service



102 February, 2009

Marketplace at http://service.sap.com/erp-inst andhttp://service.sap.com/instguides.

For more information about non-SAP ERP system landscape elements, review theapplication-specific Master Guides on SAP Service Marketplace athttp://service.sap.com/instguides.

For detailed information about the assignment of Business Functions and forinformation about the Industry Scenarios see the SAP Service Marketplace athttp://service.sap.com/erp-ehp.

4.3 Service-Oriented Architecture (SOA)OverviewSAP’s delivery on SOA (service-oriented architecture) differs from the pure architecturalconcept of SOA in the delivery of ready-to use enterprise services. Briefly, enterprise servicescan technically be web services, but SAP has created them in such a way as to ensuresemantic harmonization and business relevance.

Different software components of the enhancement packages for SAP ERP includeenterprise services available for SAP ERP 6.0. The service enablement of SAP ERP has twokey ingredients:

The service-enabled SAP ERP functions:

Many software components or product instances of SAP ERP include service-enablinginterfaces. You enable a system for enterprise services by installing those softwarecomponent versions in the system landscape that contain the required enterpriseservices interfaces.

The service interfaces installed within the backend system, prepare SAP ERP for serviceenablement according to their documentation. If you want to consume services directly,the enablement in the backend system is sufficient.

The interface description in the repository:

In addition to service enablement carried out directly in the backend system, a repositoryis available based on the SAP NetWeaver usage type Process Integration. Therepository, also known as the Enterprise Services Repository (ESR), includes adescription of interfaces used for enterprise service enablement. You can access it duringthe design phase, when you require the repository-based description of the interface. Youcan also use it during run time, for example, when you want to modify it in order toconfigure the system to allow for asynchronous access.

You can base the repository either on the release SAP NetWeaver 7.0 or on the releaseSAP NetWeaver 7.10. Enhancement package 4 for SAP ERP requires SAP ERP 6.0 andthus requires SAP enhancement package 1 for SAP NetWeaver 7.0. To support its usewith different releases, the current enhancement package includes the following content:

Usage Type Conventional Service Enablement

The usage type Conventional Service Enablement (Product Instance XI Content)includes the enterprise service related content, which you need to install with SAPNetWeaver 7.0 usage type Process Integration.

You use the conventional service enablement in system landscapes based on SAPNetWeaver 7.0 with enhancement package 1 for SAP NetWeaver 7.0. You use it aswell in system landscapes, which do not make systems available with the separateproduct versions ESR FOR SAP NETWEAVER CE 7.1 (Enterprise ServicesRepository for SAP NetWeaver CE 7.1) and SAP NETWEAVER CE 7.1 (SAPNetWeaver Composition Environment 7.1).






103 February, 2009

SAP NetWeaver usage type Service Enablement with ESR

The SAP NetWeaver usage type Service Enablement with ESR (Product instanceESR Content) includes the enterprise service related content for the SAP NetWeaver7.10 usage type Process Integration.

This product instance is relevant only if you are leveraging a solution based on SAPNetWeaver 7.10, such as SAP NetWeaver CE 7.1, with an underlying enterpriseservices repository on release SAP NetWeaver 7.10.

Specific Software Components for the Service-Oriented Architecture(SOA)The table below lists the Service-Oriented Architecture (SOA) enabling add-ons thatspecifically provide service interfaces. You need these interfaces to service-enable SAPERP.

Table 15: Product Instances in SAP Enhancement Package 4 for SAP ERP 6.0 for Service-Oriented Architecture (SOA)

SAP ERP EnhancementPackage Product Instance

Included SoftwareComponents

Corresponding ProductInstance of Product Version

SAP ERP 6.0

ESA ECC-SE 604

SAP WEB UIF 7.0

SAP_BS_FOUNDATION701

SAP ESA ECC-SE

SAP enhancementpackage 1 for SAPNetWeaver 7.0 - ASABAP

ABAP Server, such as SAPECC Server

XI Content XI CONTENT ESA ECC-SE 604 (XI Content forsoftware component ESAECC-SE 604)

SAP NetWeaver 7.0 - usagetype XI/PI (Product InstanceSAP ERP 6.0 – SAP NWProcess Integration)

ESR Content XI CONTENT ESA ECC-SE 604 (XI Content forsoftware component ESAECC-SE 604)

SAP NetWeaver 7.10 – usagetype XI/PI (to be installedseparately)

Technical Usage XI ContentESR 710

Product Instances XIContent, and ESRContent

SAP NetWeaver 7.10 – usagetype XI/PI (to be installedseparately)

InstallationThe installation of service interfaces and therefore the service enablement of SAP ERP 6.0consists of the following phases:

Identification of software components, Technical Usages or business functions

Service interfaces are assigned to software components. Depending on the specificservice interface, you need to install different software components. For some ofthese service interfaces, technical usages are available, or you need to activatebusiness functions.


104 February, 2009

The required software components, technical usages, or business functions areclarified with the descriptive documentation about the Enterprise Services,

Selection and installation together with the other parts of the enhancement package

Software components for service enablement, not assigned to a business function,might already be available in the system landscape. Most often, this is a result ofinstallation activities for other business functions. After you have verified theavailability of these software components, you install the software components withbusiness function/technical usage assignment together with other business functionsand technical usages of the enhancement package. This Master Guide describesthese activities.

SAP enhancement package 1 for SAP NetWeaver 7.0 is the basis for SAP ERP 6.0 and theavailable enhancement packages for SAP ERP. After you have installed the enhancementpackage for SAP ERP, the enhancement package 1 for SAP NetWeaver 7.0 is automaticallyavailable in the corresponding system instances.

Documentation ReferencesFor more information about the Service-Oriented Architecture (SOA), see the followinginformation sources:

SAP Network at https://www.sdn.sap.com/irj/sdn/enterprisesoa(registration required) - in particular the ES Workplace

SAP Network at https://wiki.sdn.sap.com/wiki/x/LQ0

SAP Library http://help.sap.com SOA

SAP Service Marketplace at http://service.sap.com/pam

SAP Service Marketplace at http://service.sap.com/swdc

SAP Service Marketplace at http://service.sap.com/esa

You find the descriptions for the software components for the Enterprise Services as follows

In the Enterprise Service Workplace

In SAP Note 1224284 - Enterprise Services Bundles - required Technical Usagesand Business Functions

The SAP Network, mentioned above, comes with more information about this tool.

For more information about installing SAP NetWeaver 7.10 related content and systems, seethe corresponding SAP NetWeaver 7.10 based Master Guide.

You find these guides on SAP Service Marketplace athttp://service.sap.com/instguides.

4.4 Add-On ProductsOverviewIf you have installed SAP Add-Ons or Add-Ons from other vendors, you must verify, prior toinstalling a particular enhancement package that these Add-Ons are available for thatenhancement package:

For non-SAP Add-Ons, you need to verify that it is compatible with the enhancementpackage.

For SAP Add-Ons, consult the individual Release Planning Information Note of theAdd-On.

https://www.sdn.sap.com/irj/sdn/enterprisesoa

https://wiki.sdn.sap.com/wiki/x/LQ0

http://help.sap.com/



http://service.sap.com/esa



105 February, 2009

Documentation References You find release-planning-information-notes for SAP Add-Ons on SAP Service

Marketplace at http://service.sap.com/notes.

For more information about the country availability of SAP ERP, or the solution typesfor country versions, see SAP Service Marketplace athttp://service.sap.com/globalization and athttp://service.sap.com/notes SAP Note 883072.

For an overview of different solution types for the individual SAP Industry Solutions,see the Master Guide for SAP ERP 6.0 on SAP Service Marketplace athttp://service.sap.com/erp-inst.

For general information about Add-On products, see the following SAP Notes

o SAP enhancement package 3 for SAP ERP 6.0: SAP Note 1117309

o SAP enhancement package 4 for SAP ERP 6.0: SAP Note 1226284

4.5 Software ArchitectureOverviewThe Solution Manager Maintenance Optimizer supports the installation of enhancementpackages in an existing system landscape. It uses the software architecture, which we willintroduce in this section. This conceptual overview of the software architecture helps thesystem administrator to adapt the enhancement package installation to specific requirements.

Software Structure and Grouping EntitiesSAP ERP supports a wide range of cross-industry business needs. SAP delivers thecomplete software as a package (product version). Each part of the package includessoftware and preconfigurations for different specific business needs.

Unlike the first enhancement package, where deliveries took place withinAdd-On software components, all deliveries as of enhancement package 2 forSAP ERP 6.0 take place within existing software components. As seen in theversion number of each software component, SAP delivers different versionswith the current enhancement package:

Unchanged software components from earlier enhancementpackages (For example, BP ERP DISPUTE MANAGER 1.20, or BPERP EXPENDITURE CERT 1.31)

Software components newly created for the current enhancementpackage (For example, BP ERP 05 COMMON PARTS 1.41)

The following table shows the main structuring entities for the SAP ERP product version. Thefollowing entities group the different software components according to their specific task (theinstallation tools are using corresponding entities):

Technical Usages

ABAP Product Instance

General Product Instances

Enterprise Service Bundles group software components, which are required for the serviceenablement of SAP ERP. Consider that the entity relationship model does not show thesegrouping entities.


http://service.sap.com/globalization




106 February, 2009

Figure: Entity Relationship Model

Business FunctionsThe business functions in an enhancement package define the functional scope, which youcan install and use in the supported business process.

To use particular parts of the enhancement package, you must install the relevantsoftware components and activate the business function assigned to the specificfunctional area.

During installation and activation, you need to bear in mind, that

o Some business functions require different business functions to be active inaddition

o Industry functions delivered in this enhancement package will only be activeif both the industry business function/enterprise business function and thecurrent enhancement package have been activated

General Product InstancesYou use the different product instances to build system landscapes and the individual systeminstances. Which system instances you need to make available in your system landscapedepends on the functional scope and therefore the generic business processes or Role-Based Work Centers that you intend to support.

The SAP ERP process Group Close requires systems with the productinstances SAP NW – EP Core, SAP NW - Business Intelligence, and SAPSEM.


107 February, 2009

The enhancement packages include several new software component versions. Thesesoftware components are running in different general product instances.

A business function is available related to the generic business processGroup Close. For this business function, you need to make a higher version ofSAP SEM available. Alternatively, you can install the technical usageStrategic Enterprise Mgmt in a SAP ECC System.

In some cases, product instances from product version SAP ERP 6.0 are required to enablethe complete functional scope of a specific generic business process or enhancementpackage feature.

A given productive system landscape consists of a system with productinstance SAP ECC Server, but not any system where product instance SAPNW EP – Core is available. A new business function is available with theenhancement package that includes Portal Content. Portal Content requires asystem with SAP NW EP – Core.

Before you can install the enhancement package, you need to make a systemwith product instance SAP ERP 6.0 – SAP NW EP Core available.

Special Product InstancesEnhancement packages allow for the selective upgrade of the existing SAP ERP 6.0 systemlandscape. ABAP Product Instances define all the software components of an enhancementpackage, which you install on a general product instance such as SAP ECC Server.

The following other Product Instances have a comparable function to these ABAP ProductInstances:

Java Product Instances, which coup all software components, which are installed inJava systems (usage type AS Java)

Content Instances, which group content for particular systems based on the usagetypes AS Java and AS ABAP

Technical UsagesOften business functions run in different system instances, so that you might need to changevarious system instances with a specific enhancement package. In order to allow you theidentification of the system instances affected by a particular business function, you requirespecific groupings.

Technical Usages group different ABAP Product Instances, Java Product Instances,or Content Instances.

Technical Usages relate to a particular Business Function.

Documentation ReferencesBusiness functions and generic business processes or Role-Based Work Centers representdifferent views of the same concept. The appropriate view depends on the particularsituation.

For detailed documentation of the business functions and their activation, see sectionBusiness Function Sets and Business Functions in the SAP Library for enhancementpackage for SAP ERP available at help.sap.com, under ERP SAP ERP CentralComponent.


108 February, 2009

The assignment of business functions, software components, and the groupingTechnical Usages is documented in the following SAP Notes:

Enhancement package 4 for SAP ERP 6.0: 1165438



You find information about the assignment of business functions and the genericbusiness in the SAP Service Marketplace at http://service.sap.com/erp-ehp.

You can see the relationship between product instances and processes/Role-BasedWork Centers in the Scenario and Process Component List on SAP ServiceMarketplace at http://service.sap.com/scl.

4.6 Additional Products and Third-PartyProductsOverview

Closing Cockpit

You can use the Closing Cockpit to schedule and monitor tasks relating tothe generic business process Local Close in a single SAP ERP 6.0 systeminstance with no additional effort. However, if you wish to schedule closingtasks in multiple SAP systems from the Closing Cockpit, you will need theSAP NetWeaver 7.0 (2004s) usage Job Scheduler [Software componentSAP CPS BASIC (SCHEDULER)] to schedule these closing tasks in theattached systems and to manage any inter-system dependencies. For eachexternal task, you need to create a job definition in the system with usageJob Scheduler then include this job as a remote task in the Closing Cockpit

This feature requires separate product instances and software componentsin order to function. These are neither considered part of the currentenhancement package for SAP ERP nor of SAP ERP 6.0

You obtain the SAP CPS Scheduler in the SAP Software Distribution Centeron SAP Service Marketplace at http://service.sap.com/swdc

For additional information regarding pricing and availability for SAP CPS,contact your SAP Account Executive

SAP Learning Solution

A separate and additional premium learning solution with additional featuresand functions is also available under the name SAP Enterprise Learning(Environment). This solution is part of the separate HCM, EnterpriseLearning business function and requires separate product instances andsoftware components in order to function. It is not considered part of thecurrent enhancement package for SAP ERP or of SAP ERP

It allows customers to leverage the use of the SAP Learning Solution andSAP Enterprise Learning by integrating external Learning Services ofvarious kinds such as virtual classroom, collaboration tools, externally orinternally hosted content or tests. From the learning portal, learners canbook, launch, and cancel courses hosted by a third party provider orinternally. Learning progress achieved on the Learning Service Providersystem can be seamlessly transferred back to and stored in the employeerecord in the SAP Learning Solution and SAP Enterprise Learning





109 February, 2009

The license to use the SAP Learning Solution (business process ManageEnterprise Learning Strategies) does not include the license for the SAPEnterprise Learning (Environment). For additional information regardingpricing and availability for the latter solution contact your SAP AccountExecutive

The separate product SAP Enterprise Learning (environment) requires theadditional software component Integrated Virtual Learning Room (ELEADOBE CONNECT), which is not part of the product versions for thedifferent enhancement packages for SAP ERP or the related licenses

The Learning Portal and the Instructor Portal include the Virtual LearningRoom. Learners can enter the Virtual Learning Room from the LearnerPortal to attend learning events conducted there

Instructors can create, manage, and enter Virtual Learning Rooms from theInstructor Portal. Information on user participation in learning eventsconducted in the Virtual Learning Room is automatically stored in the SAPEnterprise Learning (environment)

Users need the Adobe Flash Plug-In installed in their browser to use theVirtual Learning Room

The integration scenario External Learning Services is part of the processManaging Enterprise Learning Strategies, and is shipped with softwarecomponent XI CONTENT EA-HR

PLM Web User Interface

To display 2D and 3D graphics in PLM Web User Interface you can usedifferent viewers that you must install locally on each user’s client

If you work with viewers, it might also be necessary to install a conversionserver, on which the system converts CAD files into a format that yourviewer can display

Generic Business Process Managing Succession and Talent Development

If you plan to implement talent management, we strongly advise you toimplement the new functionality of Talent Management and TalentDevelopment delivered with the enhancement package 4 for SAP ERP 6.0.

In addition, SAP strongly recommends you to implement the new TalentVisualization by Nakisa 2.0, which is available with the current enhancementpackage 4 for SAP ERP 6.0.

Documentation ReferencesFor more information about the usage type Job Scheduler, refer to the followingdocumentation on SAP Service Marketplace:

Overview is available atsap.com/solutions/solutionextensions/centralprocessscheduling

Installation information can be found athttp://service.sap.com/instguidesNW70 Installation Installation StandAlone Engines

Adobe Acrobat Reader and its installation, see the Adobe Website atwww.adobe.com

Conversion servers, see the SAP ERP documentation on SAP Help Portal athelp.sap.com SAP ERP Central Component SAP ERP Enhancement

http://service.sap.com/instguidesNW70

http://www.adobe.com/


110 February, 2009

Packages SAP enhancement package 04 SAP ERP Central ComponentDocument Management Conversion

For more information about the PLM Web User Interface, see the Master Guide for SAP PLMWeb User Interface in SAP Service Marketplace athttp://service.sap.com/instguides SAP Business Suite Applications SAPPLM, and refer to section Product Instance: SAP Product Visualization.

You find information about Talent Visualization by Nakisa 2.0, and about migration supportfor earlier data models for succession planning in SAP note 1223936, and related notes.Upgrade and installation information about this and other SAP Solution Extensions fromindependent partners are available in the SAP Service Marketplace athttp://service.sap.com/instguides -> SAP Solution Extensions.




111 February, 2009

5 Media ListGeneralYou install the current enhancement package from one of the following product versions:

EHP 4 for SAP ERP 6.0 [Easy Adoption]

EHP 4 for SAP ERP 6.0/ NW 7.01 [Continuous Innovation]

SAP delivers several data carriers for the product version EHP 4 for SAP ERP 6.0/ NW 7.01[Continuous Innovation]. These data carriers include the software components, which youneed in order to install SAP ERP 6.0 together with enhancements from the enhancementpackage.

With the data carriers for EHP 4 for SAP ERP 6.0/ NW 7.01, you cannot install a SAP ERP6.0 system without installing the enhancement package in the same step. If you intend toinstall a system landscape, which consists of SAP ERP 6.0 without enhancement package,use the DVD set for SAP ERP 6.0 Support Release 3.

PrerequisitesBefore installing any software component of the enhancement package, ensure that you areusing the current version of the installation documentation.

For installation documentation for SAP NetWeaver 7.0 and the SAP enhancementpackage 1 for SAP NetWeaver 7.0, see SAP Service Marketplace athttp://service.sap.com/instguidesnw70.

For installation documentation for SAP ERP, see the SAP Service Marketplace athttp://service.sap.com/erp-inst.

For additional installation documentation for enhancement packages for SAP ERP,see the enhancement packages information center athttp://service.sap.com/erp-ehp.

Documentation ReferencesFor more information about tools and related Media information, see the following:

SAP Software Distribution Center on SAP Service Marketplace athttp://service.sap.com/swdc

The Media information is documented as follows

The Media information for SAP NetWeaver 7.0 and the enhancementpackages for SAP NetWeaver 7.0 are described in the document Media List– SAP NetWeaver <Release> on SAP Service Marketplace athttp://service.sap.com/instguidesnw (SAP NetWeaver) -><Release> -> Installation.

The Media information of SAP Solution Manager is part of the documentMedia List – SAP Solution Manager <Release>. For more information, seeSAP Service Marketplace at http://service.sap.com/instguides -> SAP Components -> SAP Solution Manager -> Release <x>

The Media information for SAP ERP 6.0 is part of the SAP ERP 6.0 MasterGuide, on SAP Service Marketplace at http://service.sap.com/erp-inst (SAP ERP)



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





5 Media List

112 February, 2009

5.1 EHP 4 for SAP ERP 6.0 [Easy Adoption]GeneralTo obtain the required SAP software components to which your enterprise is entitled to, youneed to use the Maintenance Optimizer of the SAP Solution Manager. The system generatesthe corresponding authorizations automatically from the licenses.

Software Components and DVD / CD StructureFor product version EHP 4 for SAP ERP 6.0 [Easy Adoption], SAP does not deliver any DVD.You download the software components electronically in addition to SAP ERP 6.0. You findthe latest version of the SAP enhancement package installer for ABAP (SAPehpi) in theSoftware Distribution center (http://service.sap.com/swdc)

For software components based on AS Java, you use the Java Support Package Manager(JSPM).

Documentation ReferencesFor more information about tools and release information, see the following:

You find the download path for the SAP enhancement package installer for ABAP,and related information in SAP note 1245473.

Information about the SAP Solution Manager

SAP Library, at help.sap.com, under SAP Solution Manager ChangeManagement Maintenance Optimizer and the document version on SAP ServiceMarketplace at http://service.sap.com/solutionmanager Media LibraryDocumentation

SAP bases the shipment of a particular enhancement package on defined SupportPackage Stacks. For more information on Support Package stacks, see the following:

SAP Service Marketplace at http://service.sap.com/sp-stacks

SAP Note 849887 – Release and Information (which lists all Release andInformation notes that have been released for SAP ERP)

SAP Note 1064635 - SAP ERP Enhancement Packages: SP StacksRelease Info Note.

5.2 EHP 4 for SAP ERP 6.0/ NW 7.01[Continuous Innovation]Software Components and DVD / CD StructureThis section summarizes the exact location of the required software components on thecorresponding DVD(s) and CD(s) shipped with the EHP 4 for SAP ERP 6.0/ NW 7.01[Continuous Innovation] package. If appropriate, references to other sources are alsoincluded.

Product version EHP 4 for SAP ERP 6.0/ NW 7.01 requires the minimum support packagestack 13, or higher of SAP ERP 6.0. You find more information about Support Packagestacks in the SAP Service Marketplace at http://service.sap.com/sp-stacks. Also,review the corresponding Release and Information Notes (RIN). SAP Note 849887 includesinformation about all RINs issued for SAP ERP.


http://service.sap.com/solutionmanager




113 February, 2009

Table 16: DVD/CD for Installation of EHP4 FOR SAP ERP 6.0/ NW 7.01 (Start-Release:operating system only)

DVD / CD Label Description / Additional Information

Installation Master for:

SAP EHP1 FOR SAPNetWeaver 7.0EHP 4 FOR SAP ERP 6.0/NW 7.01SAP CRM 7.0/ NW 7.01SAP SRM 7.0/ NW 7.01SAP SCM 7.0

The Installation Master is the starting point for installingEHP 4 FOR SAP ERP 6.0/ NW 7.01 and SAP SRM 7.0/ NW7.01. You also use it to install new dialog instances and runa system copy. The installation process for product versionEHP 4 FOR SAP ERP 6.0/ NW 7.01 installs the technicalusage ABAP Technology for ERP EHP4 and the selectedJava instances. In order to install further technical usagesyou need to continue the installation with the SolutionManager and with the SAP enhancement package Installerfor software components in usage type AS ABAPrespectively JSPM for Java.

It is furthermore the starting point for installing SAP ERPJava components and most Business Packages.

SAP ERP 6.0/ NW 7.01

EHP4 READY

Installation Export

Contains required installation files for EHP 4 FOR SAP ERP6.0/ NW 7.01 with technical usage ABAP Technology forERP EHP4. If you intend to install further ABAPcomponents for the enhancement package, you need toperform a second installation step using the SAPenhancement package Installer.


EHP4 READY

Languages

Contains language files for installation and upgrade of EHP4 FOR SAP ERP 6.0/ NW 7.01 in several folders. Thedelivered languages are DE, EN, FR, IT, PT, DA, ES, FI,NL, NO; SV, CS, EL, HR, HU, PL, SK; AR, BG, RO, SU,SH, SL, TR, UK; JA, KO, TH, ZF, ZH.

SAP EHP1 FOR SAPNetWeaver 7.0,

Kernel 7.01, <OperatingSystem>

Contains SAP Kernel files for SAP NetWeaver 7.0 EHP 1,EHP 4 FOR SAP ERP 6.0/ NW 7.01 and SAP SRM 7.0/ NW7.01 (for installation and upgrade).

RDBMS <Database>,<Database Version>

Media for database software

<Database>, <DatabaseDocumentation>

Database documentation (available for Oracle only)

EHP 4 FOR SAP ERP 6.0/NW 7.01,

ERP Components

The ERP Components DVD contains the ABAP Add-Oninstallations and upgrades for Learning, CPRXRPM(cProject Suite) 4.0 (folder CPROJECTS), WorkforceDeployment 1.0 (WFMCore 200 and LCAPPS_2005_700 infolder WORKFORCE_DEPLOYMENT), SAP SRM ServerAdd-On 7.0 (folder SRM_SERVER_ADDON), SAP OpenPSfor MS Project (folder OPENPS_FOR_MS_ PROJECT),SAP Easy Document Management (folderEASY_DOCUMENT_MGMT)

The ERP Components DVD contains the installation files forthe Java components SAP Learning Solution AuthorsEnvironment 6.0 (folder LSO LSOAE), SAP LearningSolution Offline Player 6.0 (folder LSO LSOOP), SAPElster 2.0 (folder PI_ADAPTER ELSTER_2.0), SAP

5 Media List

114 February, 2009


BCONS 604 (folder PI_ADAPTER SAP_BCONS_604)and SWIFT 602 (folder PI_ADAPTER SWIFT_602)

It contains

The EHP 4 FOR SAP ERP 6.0/ NW 7.01 XI Contentin folder XI_CONTENT

The EHP 4 FOR SAP ERP 6.0/ NW 7.01 ESRContent in folder ESR_CONTENT

SAP EHP1 FOR SAPNetWeaver 7.0

Java based SoftwareComponents

Contains the Java Load and the SAP NetWeaver AS Javausage types.

Java Components for:EHP 4 FOR SAP ERP 6.0/NW 7.01SAP CRM 7.0/ NW 7.01SAP SRM 7.0/ NW 7.01SAP SCM 7.0

Contains the installation files for SAP XSS (Self Services)603, SAP FSCM Biller Direct 604, SAP Learning SolutionContent Player (LSOCP) 604, SAP XECO 7.0, SAP IS-SRS602, SAP Utility Customer E-Services 604 and PortalContent 604 (all in folder J2EE_OSINDEP UT_ERP).

Some Business Packages (BP_ERP5_HIGHER_EDU_RES1.0, BP_COMPENSATION_SPECIAL_60.2,BP_SALES_ANALYSIS_60.1,BP_ENV.HEALTH_&_SAFETY_50, and BP PRODUCTS50.3, etc) are neither included into the shipment, nor in theinstallation. You need to install these packages manually.

SAP SRM 7.0/ NW 7.01

Installation Export

Contains required installation files for SAP SRM 7.0/ NW7.01.


Languages

Contains language files for installation and upgrade of SAPSRM 7.0/ NW 7.01.

BI CONT 7.04

Business Intelligence Content

Add-On Vers. 4

Contains Business Intelligence Content Add-On Version 4

Table 2: DVD/CD for Upgrades to EHP4 FOR SAP ERP 6.0/ NW 7.01 (Start-Release ERP2004 or lower)

DVD/ CD Label Description/ Additional Information

Upgrade Master for:SAP EHP1 FOR SAPNetWeaver 7.0EHP 4 FOR SAP ERP 6.0/NW 7.01SAP CRM 7.0/ NW 7.01SAP SRM 7.0/ NW 7.01SAP SCM 7.0

The Upgrade Master is the starting point for upgrading toEHP 4 for SAP ERP 6.0/ NW 7.01 and SRM 7.0/ NW 7.01.


115 February, 2009



EHP4 READY

Upgrade Export

Contains required upgrade files for EHP 4 for SAP ERP 6.0/NW 7.01 with technical usage ABAP Technology for ERPEHP4. You bind further EHP 4 technical usages into theupgrade and download further selected technical usages bymeans of the Solution Manager.


EHP4 READY

Languages

Contains language files for installation and upgrade of EHP4 FOR SAP ERP 6.0/ NW 7.01 in several folders. Thedelivered languages are DE, EN, FR, IT, PT, DA, ES, FI,NL, NO; SV, CS, EL, HR, HU, PL, SK; AR, BG, RO, SU,SH, SL, TR, UK; JA, KO, TH, ZF, ZH.


Kernel 7.01, <OperatingSystem>

Contains SAP Kernel files for SAP NetWeaver 7.0 EHP 1,EHP 4 FOR SAP ERP 6.0/ NW 7.01 and SAP SRM 7.0/ NW7.01 (for installation and upgrade).

RDBMS <Database>,<Database Version>

Media for database software

<Database>, <DatabaseDocumentation>

Database documentation (available for Oracle only)

EHP4 FOR SAP ERP 6.0/NW7.01 enhancementpackages for all EHP4components

Contains SAP enhancement package 4 for SAP ERP 6.0support package 0. You can use the files on this DVD tosubstitute the same files from your download basket during,which you obtain with the Solution Manager (see SectionInstallation and Upgrade). With this step, you reduce theamount of download traffic.

EHP 4 FOR SAP ERP 6.0/NW 7.01

ERP Components

The ERP Components DVD contains the ABAP Add-Oninstallations and upgrades for Learning, CPRXRPM(cProject Suite) 4.0 (folder CPROJECTS), WorkforceDeployment 1.0 (WFMCore 200 and LCAPPS_2005_700 infolder WORKFORCE_DEPLOYMENT), SAP SRM ServerAdd-On 7.0 (folder SRM_SERVER_ADDON), SAP OpenPSfor MS Project (folder OPENPS_FOR_MS_ PROJECT),SAP Easy Document Management (folderEASY_DOCUMENT_MGMT)

The ERP Components DVD contains the installation files forthe Java components SAP Learning Solution AuthorsEnvironment 6.0 (folder LSO LSOAE), SAP LearningSolution Offline Player 6.0 (folder LSO LSOOP), SAPElster 2.0 (folder PI_ADAPTER ELSTER_2.0), SAPBCONS 604 (folder PI_ADAPTER SAP_BCONS_604)and SWIFT 602 (folder PI_ADAPTER SWIFT_602)

It contains

The EHP 4 FOR SAP ERP 6.0/ NW 7.01 XI Contentin folder XI_CONTENT

The EHP 4 FOR SAP ERP 6.0/ NW 7.01 ESRContent in folder ESR_CONTENT.


Contains the Java Load and the SAP NetWeaver AS Javausage types.

5 Media List

116 February, 2009


Java based SoftwareComponentsJava Components for:EHP 4 FOR SAP ERP 6.0/NW 7.01SAP CRM 7.0/ NW 7.01SAP SRM 7.0/ NW 7.01SAP SCM 7.0

Contains the installation files for SAP XSS (Self Services)603, SAP FSCM Biller Direct 604, SAP Learning SolutionContent Player (LSOCP) 604, SAP XECO 7.0, SAP IS-SRS602, SAP Utility Customer E-Services 604 and PortalContent 604 (all in folder J2EE_OSINDEP UT_ERP).

Some Business Packages (BP_ERP5_HIGHER_EDU_RES1.0, BP_COMPENSATION_SPECIAL_60.2,BP_SALES_ANALYSIS_60.1,BP_ENV.HEALTH_&_SAFETY_50, and BP PRODUCTS50.3, etc) are neither included into the shipment, nor in theinstallation. You need to install these business packagesmanually.


Upgrade Export

Contains required upgrade files for SAP SRM 7.0/ NW 7.01.


Languages

Contains language files for installation and upgrade of SAPSRM 7.0/ NW 7.01.

BI CONT 7.04

Business Intelligence Content

Add-On Vers. 4

Contains Business Intelligence Content Add-On Version 4

Table 3: DVDs for updating with Enhancement Package Installer* to EHP4 FOR SAPERP 6.0/ NW 7.01 (Start-Release SAP ERP 6.0, SAP ERP 6.0 with enhancementpackages 2, 3 or 4)


EHP4 FOR SAP ERP 6.0/NW7.01 enhancementpackages for all EHP4components

Contains SAP enhancement package 4 for SAP ERP 6.0Support Package SP00. You use the files on this DVD tosubstitute the same files, which you obtain from yourdownload basket, when using the Solution Manager (Section2.3 Installation and Upgrade). You do this to reduce theamount of download traffic.


Add-On Upgrade

Contains SAP enhancement package 1 for SAP NetWeaver7.0 Support Package SP00. You use the files on this DVD tosubstitute the same files, which you obtain from yourdownload basket, when using the Solution Manager (Section2.3 Installation and Upgrade). You do this to reduce theamount of download traffic.

BI CONT 7.04

Business IntelligenceContent

Add-On Vers. 4

Contains Business Intelligence Content Add-On Version 4.You use the files on this DVD to substitute the same files,which you obtain from your download basket, when using theSolution Manager (Section 2.3 Installation and Upgrade). Youdo this to reduce the amount of download traffic.


117 February, 2009

* SAP delivers the SAP enhancement package installer tool (SAPehpi) electronically. Youfind the download path and additional information in the Software Distribution Center(http://service.sap.com/swdc) described in SAP note 1245473.


6 References

118 February, 2009

6 References6.1 List of DocumentsThe following table lists all documents mentioned in this Master Guide.

Title Where to Find

HR Administrator role-based WorkCenter

SAP Library, at help.sap.com, under SAP ERPCentral Component Business Packages (PortalContent) Business Package for HR Administrator(SAP ERP)

Information Center SAPenhancement packages for SAPERP

SAP Service Marketplace athttp://service.sap.com/erp-ehp

Employee Interaction Center –Customizing

The Implementation Guide (IMG) for PersonnelManagement under Employee Interaction Center(EIC)

Employee Interaction Center - Help SAP Library, at help.sap.com, under SAP ERPCentral Component Human ResourcesPersonnel Management PersonnelAdministration (PA-PA) Employee InteractionCenter

Enabling Enterprise Services(Service-Oriented Architecture(SOA))

SAP Library, at help.sap.com, under SAPNetWeaver 7.0 Administrator’s GuideTechnical Operations Manual for SAP NetWeaver

Enabling Enterprise Services

Grants Management SAP Library, at help.sap.com, under SAPBusiness Suite SAP Customer RelationshipManagement

Group Close SAP Library, at help.sap.com, under SEM -Strategic Enterprise Management BusinessConsolidation (SEM-BCS)

Information Center SOA SAP Service Marketplace athttp://service.sap.com/esa

Management of Internal Controls SAP Library, at help.sap.com, under SAP ERPCentral Component Financials Managementof Internal Controls (FIN-CGV-MIC)

Master Guide for product versionSAP ERP 6.0

SAP Service Marketplace athttp://service.sap.com/erp-inst

Master Guide for SAP for Banking SAP Service Marketplace athttp://service.sap.com/instguidesIndustry Solutions Industry Solution MasterGuides SAP for Banking

Master Guide for SAP NetWeaver7.0

SAP Service Marketplace athttp://service.sap.com/instguidesnw,andhttp://service.sap.com/instguidesnw70


http://service.sap.com/esa






119 February, 2009

Master Guides for SAP IndustrySolutions

SAP Service Marketplace athttp://service.sap.com/instguides

SAP CRM Master Guides SAP Service Marketplace athttp://service.sap.com/instguides

SAP ERP Common role-based WorkCenter

SAP Library, at help.sap.com, under SAP ERPCentral Component Business Packages (PortalContent) Business Package for Common Parts

Product Availability Matrix SAP Service Marketplace athttp://service.sap.com/pam

SAP Credit Management SAP Library, at help.sap.com, under SAP ERPCentral Component Financials SAP FinancialSupply Chain Management SAP CreditManagement

SAP Developer Network sdn.sap.com/irj/sdn/developerareas/esa(registration required)

SAP Industry Solutions SAP Service Marketplace athttp://service.sap.com/industries

Scenario and Process ComponentList

SAP Service Marketplace athttp://service.sap.com/scl

Security Guide for Management ofInternal Controls

SAP Service Marketplace athttp://service.sap.com/securityguide

Software Distribution Center SAP Service Marketplace athttp://service.sap.com/swdc

Support Package Stacks SAP Service Marketplace athttp://service.sap.com/sp-stacks

Talent Management SAP Library, at help.sap.com, under SAP ERPCentral Component Business Packages (PortalContent) Business Package for TalentDevelopment Specialist

Technology Consultant's Guide SAP Service Marketplace athttp://service.sap.com/instguidesnw70

Installation Technology Consultant's Guide

6.2 List of SAP NotesThe following table lists all SAP Notes mentioned in this Master Guide.

SAP NoteNumber

Title Content

503907 Release strategy for the LSOFEadd-on

Planning of installation and upgrades ofR/3 add-on LSOFE

529063 Overview: Notes for theLearning Solution add-on

SAP Learning Solution Overview

568853 Supported TREX versions inSAP E-Recruiting

You want to install the SAP E-Recruitingapplication and you require informationabout the version of the necessary searchengine, TREX. The search engine TREXis part of SAP NetWeaver










6 References

120 February, 2009

SAP NoteNumber

Title Content

824757 Dependencies between SAPERP component lists

Dependencies of Role-Based WorkCenters with Generic SAP ERP Processes

836200 SAP NetWeaver 2004s:Importing process integration

Migration and import of XI Content basedon SAP NetWeaver 7.0

849887 SAP ERP 6.0: Support PackageStacks Release and Info Note

List of all SAP ERP 6.0 Release andInformation Notes (RIN) issued for SAPERP 6.0

883072 Globalization information onSAP ERP

Detailed information about translation andcountry availability of SAP ERP

928729 Combined Upgrade & UnicodeConversion FAQ

Information, which you need in a upgradeproject, which combines the upgrade witha Unicode conversion

927530 BI Java sizing Hardware sizing for BI Java component inNetWeaver 2004s

956074 Using the update function forforms

Information about SAP Interactive Formsby Adobe. Certain functions are onlyavailable when you update your forms. Anexample is the processing and display ofinteractive forms in the Adobe reader onthe Basis of ZCI (Zero Client Installation)

998833 Release Restrictions SAP ERP6.0 - Enhancement Packages

Information about the limitations for SAPenhancement packages for SAP ERP 6.0

1000291 Automatic Roles This SAP note describes automatic roles.With these roles, SAP ERP 6.0 enhancesand simplifies roll-based activities in theSAP Enterprise Portal.

1024326 Corrected UI for role HRadministrator available

As of SAP ERP Enhancement Package2005.1 (EhP1), the user interfaces used inthe function HCM Processes and Forms ofthe portal role HR Administrator. Bothwere migrated from the Web Dynprotechnology for Java to the Web Dynprotechnology for ABAP

In future, SAP will continue to support theWeb Dynpro for ABAP technology for therole-based Work Center HR Administrator.


Using transaction SAINT to install an add-on for Enhancement Package 2 on SAPERP Central Component ECC 600(referred to here as SAP ECC 600)

1052470 SAP ERP 6.0 EhP 2 - Businessfunctions and SW components

Installing functions of enhancementpackage 2 for SAP ERP 6.0.

1052522 Enhancement Package 2 forSAP ERP 6.0: required SupportPack

Information on installation prerequisites forenhancement package 2 for SAP ERP6.0: Required Support Package Stacks

1057498 Installing JAVA SAP Importing components of enhancement


121 February, 2009

SAP NoteNumber

Title Content

Enhancement Package 2 forSAP ERP 6.0

package 2 for SAP ERP 6.0 that werecreated in Java to a central J2EE server


Information about the add-on upgrade toRelease SAP ERP Central ComponentECC 600 (referred to in this note as SAPECC 600) with ECC-SE 602

1064419 SAP Integration Package forSWIFT: Info about installation

Additional information about the installationof the SAP Integration Package for SWIFT

1064635 SAP ERP EnhancementPackages: SP Stacks ReleaseInfo Note

List of all Release Information Notes for:SAP ERP Enhancement PackageReleases, SAP ERP EnhancementPackage Support Package (SP) Stacks,Corresponding or equivalent SAP ERP 6.0Support Package Stacks

1065209 SAP Enhancement Package 2for SAP ERP 6.0

Enhancement Package 2 for SAP ERP 6.0complements the ERP 6.0 release in anumber of focus areas. It is easy to installand immediately adds incremental valueto your business processes withoutdisruption

1066110 ERP Enhancement Package:Installing the SAP Library

Using enhancement package 2 for SAPERP 6.0 or enhancement package 3 forSAP ERP 6.0 and you want to install theSAP Library on your customer server

1081630 ECC-SE 603 Add-OnInstallation

Installing/upgrading to ECC-SE 603 onSAP ERP Central Component ECC 600using transaction SAINT



1082916 Upgrade AIO 1.2 toEnhancement Package 3

This note relates to the upgrade of AIO 1.2to Enhancement Package 3 (EhP3) usingtransaction SAINT

1083533 Installation EnhancementPackage 3 on SAP ERP 6.0

Using transaction SAINT to update andenhance existing software componentsusing enhancement package 3 on SAPERP Central Component ECC 600(referred to here as SAP ECC 600)

1083576 SAP enhancement package 3for SAP ERP 6.0 - requiredSWC

Installing dedicated parts of enhancementpackage 3 for SAP ERP 6.0

1093628 SAP ERP 6.0 SR3 - ReleaseInformation Note

SAP ERP 6.0 SR3 Installation or Upgrade

1095233 Enhancement Package 3 forSAP ERP 6.0: required SupportPack

Installation prerequisites for enhancementpackage 3 for SAP ERP 6.0: RequiredSupport Package Stacks

6 References

122 February, 2009

SAP NoteNumber

Title Content

1100230 Installing JAVA SAPEnhancement Package 3 forSAP ERP 6.0

Importing components of enhancementpackage 3 for SAP ERP 6.0 that werecreated in Java to a central J2EE server

1105694 Installing & upgrading info forPortal Content EnhancementPackage 3

New portal roles and functions deliveredwith the SAP ERP Enhancement Package2005.3

1111660 Release Info SAPEnhancement Package 3 forSAP ERP

Enhancement package 3 for SAP ERP 6.0complements the SAP ERP 6.0 release ina number of focus areas. It is easy toinstall and immediately adds incrementalvalue to your business processes withoutdisruption

1117309 Compatibility of Add-Ons vsenhancement packages forERP 6.0

Special issues to consider when applyingan enhancement package for SAP ERP6.0 to your ERP 6.0 system when youalready have an Add-On installed (SAPenhancement package 3 for SAP ERP6.0)

1122966 Maintenance Optimizer: Notesfor Enhancement Packages

You want to import ERP 6.0 EnhancementPackages using the MaintenanceOptimizer. The import is possible as ofSolution Manager 4.0 Support Package 13.

1141296 Solution Manager: ERP productdata missing

Information required by the MaintenanceOptimizer when current SAP ERP 2005product data is missing in the SAPSolution Manager


Enhancing existing software componentsusing enhancement package 4 on SAPERP Central Component ECC 600(referred to here as SAP ECC 600)

1150349 ECC-SE 604 Add-OnInstallation/Delta upgrade

Install/upgrading to ECC-SE 604 on SAPERP Central Component ECC 600 usingtransaction SAINT



1155041 ERP upgrade usingMaintenance Optimizer

The note contains important additionalinformation for the documentation. Readthis note before you perform the upgradeto SAP ERP 6.0.

1156407 SAP ERP Enhan. Pk. 4 SPStacks - Release & InformationNote

This Release Information Note (RIN)contains information and references tonotes for applying Support Package (SP)Stacks of SAP Enhancement Package 4for SAP ERP 6.0 (Initial shipment). Keepin mind, that SAP Note 1064635 serves asa container for all SAP Notes with release


123 February, 2009

SAP NoteNumber

Title Content

information.

1160106 Enhancement package 4 forSAP ERP: Installing JAVA

Importing components of enhancementpackage 4 for SAP ERP 6.0 that werecreated in Java to a central J2EE server

1161294 Name chg, SAP SolutionManager 4.0 to SolutionManager 7.0

SAP Solution Manager 4.0 renamed toSAP Solution Manager 7.0.

1164532 Release restrictions of SAPEHP 1 for SAP NetWeaver 7.0

This note provides customer informationon possible restrictions.

1164979 NetWeaver 7.0 EmbeddedSearch: Central Note

You are using Embedded Search of SAPenhancement package 1 for SAPNetWeaver 7.0.

The central release note includes allrequired information and informationreferences

1165067 Release Info SAPEnhancement Package 4 forSAP ERP 6.0

Enhancement package 4 for SAP ERP 6.0complements the SAP ERP 6.0 release ina number of focus areas. It is easy toinstall and immediately adds incrementalvalue to your business processes withoutdisruption

1165437 Enhancement package 4 forSAP ERP: Required supportpackages

Installation prerequisites for enhancementpackage 4 for SAP ERP 6.0

1165438 Enhancement package 4 forSAP ERP: Required SWCV

Installing dedicated parts of enhancementpackage 4 for SAP ERP 6.0

1165442 Enhancement package 4 forSAP ERP: Info for portalcontent

New portal roles and functions deliveredwith enhancement package 4 for SAPERP 6.0

1170324 Java Components SAP LSOand Enhancement Packages

Information about the Java softwarecomponent version and about theactivation of business functions.

If you have installed the enhancementpackage, but do not activate the businessfunctions of the SAP Learning Solution,you need to verify that you are using thecorrect software component versions

1172899 BI_CONT 7.04: Informationabout Installation and Upgrade

Installing BI Content packages andadditional information about performing adelta upgrade

1172901 SAP SRM Add-On 6.0 for ERP6.0 EhP4: Installation/Upgrade

Installing SAP SRM Add-On 6.0 for SAPERP 6.0 with transaction SAINT

1175205 New Support Pack Strategy forIS-Oil-PRA from EHP4

Beginning with enhancement package 4for SAP ERP 6.0, SAP has decoupled thesoftware components IS-OIL-PRA and IS-OIL. It has included IS-OIL into the new

6 References

124 February, 2009

SAP NoteNumber

Title Content

Software Component IS-PRA. While youstill need to install IS-Oil and IS-PRA withthe new enhancement package, the IS-PRA and IS-OIL (Downstream) correctionsare available in separate supportpackages from enhancement package 4for SAP ERP onwards.

1175848 Additional Information - SAPEnhancement Package Installer

This SAP Note (or successor notesmentioned) describes errors in theinstallation procedure; preparations for theinstallation; and additional information tothe guides

SAP updates this note regularly, andrecommends, that you read it immediatelybefore starting the installation.

1179524 Installation Note for SAPProduct Visualization

Product instance SAP ProductVisualization includes a third party viewer

1223936 Talent Management and TalentDevelopment with EHP4

With enhancement package 4 for SAPERP 6.0 SAP introduces new functionsand process support with the genericbusiness process Managing Successionand Talent Development

1224097 Installation of Applets for PLMWeb User Interface

Necessary installation for PLM Web UserInterface (Security)

1224284 ES Bundles - RequiredTechnical Usages and BFs

You want to use enterprise services andneed an overview which sets of servicesare available, and which product versions,software components, Technical Usagesand Business Functions they require.

1226284 Add-on compatibility toEnhancement Package 4 forSAP ERP 6.0

You plan to apply the SAP enhancementpackage 4 for SAP ERP 6.0 to your ERP6.0 system where you already have anAdd-On installed. This note provides youwith information about special issues youneed to consider.

1224543 Release Note ESR/PI Contentfor SAP NetWeaver PI 7.1

Process Integration Content, and ESR-Content, released for SAP NetWeaver 7.0usage type Process Integration isavailable for SAP NetWeaver 7.1 usagetype Process Integration 7.1.

1245473 Additional Information – SAPEnhancement Package installer

Information about errors in the installationprocedure, preparations for theinstallation, and information in addition tothe guides.

1258912 PLM Core 7.00 Release Notesand Information

Information and references to SAP notes,which include information about installingPLM Core 7.00 and importing PLM Core7.00 Support Packages. Will be updatedwhenever new information is available.


125 February, 2009

SAP NoteNumber

Title Content

Information specific to a support packagewill be added upon availability.

1273780 Talent Management and TalentDevelopment - TREX 7.10

Enterprise Search used in TalentManagement and Talent Develpment in theSAP enhancement package 4 for SAP ERP6.0 requires TREX 7.10.

1275873 Memory bottleneck during DDICactivation during EHP import

During the installation of an EnhancementPackage queue, the DDIC activationterminates with runtime errorsSYSTEM_NO_TASK_STORAGE,TSV_TNEW_PAGE_ALLOC_FAILED,SYSTEM_NO_ROLL

1280819 SAP BCONS Adapter for BillingConsolidation EDX

Additional information about the installationof the SAP BCONS Adapter (ProductInstance: SAP Integration for BCONS)

6.3 Terminology ConceptThe following naming conventions are important in the context of SAP ERP Master Guides.

Old Terminology New Terminology Remark

mySAP ERP 2005 SAP ERP 6.0 A SAP application, such as SAP ERPis associated to one or moreinstallable product versions

SAP ERP 2005 SAP ERP 6.0 Product Version

SAP ERPEnhancementPackage 2005.<n>

SAP enhancement package<n> for SAP ERP 6.0

<n> depicts the enhancementpackage number

SAP ERPEnhancementPackage 2005.<n>.

SAP ENH PACK <n> FORSAP ERP 6.0

Product Version/ <n> depicts theenhancement package number

SAP ENH PACK<n> FOR SAP ERP6.0

EHP4 FOR SAP ERP 6.0

EHP4 FOR SAP ERP 6.0/NW 7.01

Product Versions for Easy Adoptionor Continuous Improvement

SAP NetWeaver2004s

SAP NetWeaver 7.0

Solution Manager4.0

Solution Manager 7.0 Renaming as described in SAP Note1161294.

Product Instance(Conventional) XIContent

Product Instance XI Content XI content groups the XI contentpackages, which the software usesfor the conventional serviceenablement with SAP NetWeaver7.0. In enhancement package 3 forSAP ERP 6.0, this product instanceis named Conventional XI Content

Product Instance Product Instance ESR In addition, SAP ships the new

6 References

126 February, 2009

ESR 7.10 content product instance ESR Content. Thisincludes comparable XI Contentsoftware components, used forService Enablement with ESR basedon SAP NetWeaver 7.10. Thetechnical usage XI Content ESR 710groups ESR Content and XI Content.

Product Instance ESR Content isnamed Product Instance ESR 7.10 inenhancement package 3 for SAPERP 6.0

6.4 GlossaryThe following table shows terminology, which the current document frequently uses.

Item Meaning

SAPenhancementpackage for SAPERP (shortEnhancementPackage)

Mechanism to ship innovations in a non-disruptive way based on astable core release. Enhancement packages follow a set of rules toensure that you can install the functions smoothly and quickly withoutaffecting the customers’ business processes. New functionality inenhancement packages must be explicitly switched on by the customerin order to become effective

Stable CoreRelease

The stable core release of SAP ERP is SAP ERP 6.0. For otherApplications in the SAP Business Suite, a different stable core releaselevel could exist. SAP ships innovations to the stable core release bymeans of enhancement packages. Separate support packages areavailable for the stable core, which contain only bug fixes but no newfunctionality

EnterpriseService

A SAP or SAP Partner defined web service. Enterprise Servicesprovide business processes or business process steps that can beused to compose business scenarios while ensuring business integrityand ease of reuse

Product Instance A group of technically dependent software component versions whichhave to be installed and operated on a single logical system/serverwhich:

Show the maximum possible distribution of a product version

Smallest elements for designing system landscapes

Example:

Version 6.0 of software component SAP ECC is part of theproduct instance SAP ERP 6.0 – SAP ECC SERVER, whereSAP ERP 6.0 depicts the product version.

Specializations:

In the enhancement package framework the following specializationsare possible:

General product instances, such as SAP ECC Server, or SAP


127 February, 2009

Item MeaningNW – EP Core, which you need to install ass a completepackage.

You install the product instances of type content together withother product instances, where they provide necessary contentand preconfigurations. Examples for similar content are theBusiness Packages (Portal Content), which you install inaddition to product instance SAP NW – EP Core.

Product instances of type ABAP product instances, or Javaproduct instances, which bundle different software componentsfrom general product instances, as they are required toimplement a desired business function

Product External/delivery view on SAP‘s software:

Examples: SAP R/3, SAP ERP, enhancement package forSAP

Product version Versioned technical representation of an SAP Product, carrying, amongother things, properties such as Add-On product version or stand-aloneproduct version, comprised software components, and productinstances.

Collection of software component versions, which defines the systemlandscape required to perform defined business function.

The following types of product versions are available:

Stand-alone product version: Product version than can be used onits own

Add-On product version: You have to install the product instancesof the Add-On Product Versions on the corresponding instances ofthe stand-alone product version

Example:

Product version SAP ENH PACK 3 for SAP ERP 6.0represents enhancement package 3 for SAP ERP 6.0 from thetechnical perspective. SAP ENH PACK 3 for SAP ERP 6.0includes all product instances and software components thatyou require in order to install the enhancements shipped withenhancement package 3 for SAP ERP 6.0. SAP ENH PACK 3for SAP ERP 6.0 requires product version SAP ERP 6.0 inorder to function.

SoftwareComponent

Software components represent the technical view on SAP softwareand are a building block of a product instance. They might be used inseveral product versions.

It describes the smallest unit that is delivered, maintained or deployed,and is installed and patched as a whole.

Example:

SAP ECC 6.0 is part of product instance SAP ECC Server, andincludes software component SAP APPL


Version or release of a software component.

Properties include, for example, availability information, maintenanceinformation, technical dependencies on other software component

6 References

128 February, 2009

Item Meaningversions, release information.

Examples:

SAP BASIS 4.5B, SAP APPL 4.6B

BusinessFunction

Business meaning assigned to a specific functional enhancementshipped with an enhancement package for SAP ERP 6.0. Businessfunctions describe a set of functions and processes that belongtogether logically.

One or more switches control one Business Function. These switchesare assigned to each business function in a predefined state.

Example:

Business function Local Close is assigned to the ClosingCockpit, which is used to schedule and monitor tasks relatingto the generic business process Local Close

ABAP ProductInstance

Grouping used to bundle all software components of an enhancementpackage for SAP ERP, which are installed on a defined general productinstance

Example:

ABAP Product Instance Central Applications includes thesoftware component versions EA-APPL 604 and SAP APPL6.04. You install Central Applications on the general productinstance SAP ECC Server. SAP ECC Server consists of othersoftware components as well.

In the enhancement package framework: when installing anABAP product instance within a general product instance, theincluded software components exchange existing but lowerversions of the same software component

Technical Usage Technical Usages are assigned to business functions and bundle allproduct Instances and software components that meet the followingcriteria

They are required to install the enhancements for that businessfunction,

They are part of the enhancement package for SAP ERP.

Example:

Technical Usage HCM - Travel Management includes ABAPProduct instance - Human Capital Management (based onSAP ECC Server) and Portal Content (based on PortalContent, requires SAP NW - EP Core), and XI Content (basedon XI Content, requires SAP NW - Process Integration)

Industry BusinessFunction Sets

Industry extensions are grouped by industry business function sets andare activated using the SAP Switch Framework

EnterpriseBusinessFunctions

Generic business functions used with SAP Industry Solutions.

Industry functions delivered in this enhancement package for SAP ERPwill only be active if both the industry business function/enterprisebusiness function and the enhancement package for SAP ERP havebeen activated


129 February, 2009

Item Meaning

Business Process A business process is a set of activities transforming a definedbusiness input into a defined business outcome

BusinessScenario

A sequence of business processes designed to achieve key businessobjectives. A business scenario is either specific to one industry(industry-specific scenario) or applicable to multiple industries (cross-industry scenario)

Generic BusinessProcess

Grouping used to structure SAP ERP from the process point of viewYou find the grouping by business processes in several deliveries, suchas the SAP Solution Manager, and Solution Map.

Example:

SAP ERP 6.0 includes, among other things, the key functionalarea Financials. Generic business process Local Closebelongs to that key functional area

DeploymentScenario

A Deployment Scenario is the representation of a business scenario ina concrete system landscape. It consists of a list of technicalcomponents and of a configuration bill of material. It describes thephysical shipment of a scenario and considers the various releaselevels

ProcessComponent List

List of software components and product instances required to install ageneric business process or Role-Based Work Center.

Example:

In order to implement process Local Close, you require systems withthe following product instances (versions):

SAP ECC Server

SAP NW – EP Core, including SAP XSS (Self Services) andportal content

Component wiseupgrade

SAP has designed enhancement packages for SAP ERP as Add-Onproduct versions to SAP ERP 6.0.

Where applicable, the software components they include are installedin an SAP ERP 6.0 system landscape in such a way that theyexchange the older versions of the same software component alteredwith that enhancement package for SAP ERP

SOA Service-Oriented Architecture

ReferenceLandscape forEasy Adoption

The landscape for easy adoption keeps the SAP NetWeaver systeminstances stable on SAP NetWeaver 7.00 as delivered with SAPBusiness Suite 2005. Only the SAP NetWeaver usage type AS ABAPneeds to be on the release level 7.01 in order to use developments ofthe SAP Business Suite 7.0

ReferenceLandscape forContinuousInnovation

The landscape for continuous innovation is built on the principle thatthe complete landscape including all system instances run on the sameenhancement package 1 for SAP NetWeaver 7.0 on which all newfunctionality based on the Business Suite 7.0 core processes can beexecuted

7 The Main SAP Documentation Types

130 February, 2009

7 The Main SAP Documentation TypesThe following is an overview of the most important documentation types that you need inthe various phases in the life cycle of an SAP solution.

Documentation types in the software life cycle

ImplementationImplementation

Master Guide

ConfigurationDocumentation Release Notes

ComponentInstallation Guide

ComponentUpgrade Guide

Upgrade Master Guide

OperationOperation UpgradeUpgrade

Solution ManagementGuide

Implementation Guide (IMG) Delta and Upgrade IMG

Security Guide

SAP Library

SAPterm

Cross-Phase DocumentationSAPterm

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30languages, as well as many definitions and glossary entries in English and German.

Target group:

Relevant for all target groups

Current version:

Located in the SAP Help Portal at help.sap.com Additional Information Glossary(direct Access) or Terminology (available as terminology CD)

In the SAP-System in transaction STERM

SAP Library

The SAP Library is a collection of function and process-oriented documentation for SAPcomponents. The SAP Library also contains the Business Scenario Descriptions.

Target group:

o Consultants

o System administrators


131 February, 2009

o Project teams for implementations or upgrades

Current version:

o Located in the SAP Help Portal at help.sap.com

o Also located in the SAP Service Marketplace at http://service.sap.com/ibc (only theBusiness Scenario Descriptions)

Implementation Guide (IMG)

The Implementation Guide is a tool for configuring the SAP system to meet customerrequirements. Its structure and documentation are component-oriented.

Target group:

o Solution consultants


Current version:

o In the SAP menu of the SAP system under Tools Customizing IMG

Security Guide

The Security Guide describes the settings for a medium security level and offers suggestionsfor raising security levels. A collective security guide is available for the SAP NetWeavertechnologies like SAP Web Application Server (SAP Web AS). This document containsgeneral guidelines and suggestions about system security. Other technologies and individualapplications have a Security Guide of their own.

Target group:

o Technology consultants



Current version:

o Located in the SAP Service Marketplace athttp://service.sap.com/securityguide

InstallationMaster Guide

The Master Guide is the starting point for installing an SAP solution. It lists the required SAPcomponents and third party applications that are required for each Business Scenario. Itprovides scenario-specific descriptions of preparation, execution, and follow-up of anInstallation. It also offers references to other documents, such as Component InstallationGuides and SAP Notes.

Target group:



o Project teams for implementations

Current version:

o Located in the SAP Service Marketplace athttp://service.sap.com/instguides

http://service.sap.com/ibc



7 The Main SAP Documentation Types

132 February, 2009

Component Installation Guide

The Component Installation Guide describes the technical Installation of an SAP component,taking into account the combinations of operating systems and databases. It does notdescribe any business-related configuration.

Target group:


o Project teams for implementations

Current version:


Configuration Documentation in SAP Solution Manager

SAP Solution Manager is a tool with various functions, one of its main functions being theconfiguration of SAP solutions and Business Scenarios. It contains IMG activities,transactions, and so on, as well as documentation. Instead of the configurationdocumentation in SAP Solution Manager, there may be separate Business ScenarioConfiguration Guides in the SAP Service Marketplace for earlier shipments of the BusinessScenarios.

Target group:


o Project teams for implementation

Current version:

o In SAP Solution Manager

o Located in the SAP Service Marketplace athttp://service.sap.com/ibc

Production OperationSolution Operation Guide

The Solution Operation Guide is the starting point for operating an SAP solution. The guiderefers users to the tools and documentation that are required to carry out various tasks, suchas monitoring, backup/restore, master data maintenance, transports, and tests. It also refersusers to other documents, for example the SAP Library, the Master Guide, and theComponent Management Guides.

Target group:





Current version:


Upgrade


http://service.sap.com/ibc



133 February, 2009

Upgrade Master Guide

The Upgrade Master Guide is the starting point for upgrading the Business Scenarios of anSAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of an upgrade. It also refers to other documents, such as the Component Upgrade Guidesand SAP Notes.

Target group:


o Project teams for upgrades

Current version:


Component Upgrade Guide

The Component Upgrade Guide describes the technical upgrade of an SAP component,taking into account the combinations of operating systems and databases. It does notdescribe any business-related configuration.

Target group:



Current version:


Release Notes

Release notes are documents that contain short descriptions of new features or changes inan SAP component since the previous release. Release notes about ABAP developmentsenable the SAP system to generate delta and upgrade IMGs.

Target group:

o Consultants


Current version:

o Located in the SAP Service Marketplace athttp://service.sap.com/releasenotes

o In the SAP menu of the SAP system under Help Release information

SAP Solution Browser Tool

o The SAP Solution Browser Tool supports you with comparable informationabout functional enhancements, which took place in the SAP Productbetween different releases.

o Access this tool at internet addresssolutionbrowser.erp.sap.fmpmedia.com/.



http://service.sap.com/releasenotes

Master Guide

Documents

Transcript of Master Guide