ADM327 Enhancement Package Implementation

© SAP 2010© SAP 2009

ADM327 Enhancement Package Implementation

Enhancement PackageImplementation

ADM327

SAP ECC 6.05 (as part of SAP enhancement package 5 for SAP ERP 6.0)AS ABAP 7.02 (as part of SAP enhancement package 2 for SAP NetWeaver 7.0)BS 7i2010 (Business Suite 7 Innovations 2010)

SAP NetWeaver

Version 72

Material number: 50101087

© SAP 2010

Copyright 2011 SAP AG. All rights reserved.

Neither this training manual nor any part thereof maybe copied or reproduced in any form or by any means,or translated into another language, without the priorconsent of SAP AG. The information contained in thisdocument is subject to change and supplement without prior notice.

All rights reserved.

Copyright

Trademarks: Microsoft ®, Windows ®, NT ®, PowerPoint ®, WinWord ®, Excel ®, Project ®, SQL-Server ®, Multimedia Viewer ®, Video for Windows ®, Internet Explorer ®, NetShow ®, and HTML Help ® are registered trademarks of Microsoft Corporation.

Lotus ScreenCam ® is a registered trademark of Lotus Development Corporation. Vivo ® and VivoActive ® are registered trademarks of RealNetworks, Inc. ARIS Toolset ® is a registered Trademark of IDS Prof. Scheer GmbH, Saarbrücken Adobe ® and Acrobat ® are registered trademarks of Adobe Systems Inc. TouchSend Index ® is a registered trademark of TouchSend Corporation. Visio ® is a registered trademark of Visio Corporation. IBM ®, OS/2 ®, DB2/6000 ® and AIX ® are a registered trademark of IBM Corporation. Indeo ® is a registered trademark of Intel Corporation. Netscape Navigator ®, and Netscape Communicator ® are registered trademarks of Netscape Communications, Inc.

OSF/Motif ® is a registered trademark of Open Software Foundation. ORACLE ® is a registered trademark of ORACLE Corporation, California, USA. INFORMIX ®-OnLine for SAP is a registered trademark of Informix Software Incorporated. UNIX ® and X/Open ® are registered trademarks of SCO Santa Cruz Operation. ADABAS ® is a registered trademark of Software AG The following are trademarks or registered trademarks of SAP AG; ABAP/4, InterSAP, RIVA, R/2, R/3, R/3 Retail, SAP (Word), SAPaccess, SAPfile, SAPfind, SAPmail, SAPoffice, SAPscript, SAPtime, SAPtronic, SAP-EDI, SAP EarlyWatch, SAP ArchiveLink, SAP Business Workflow, and ALE/WEB. The SAP logo and all other SAP products, services, logos, or brand names included herein are also trademarks or registered trademarks of SAP AG.

Other products, services, logos, or brand names included herein are trademarks or registered trademarks of their respective owners.

© SAP 2009

Course Prerequisites

Required KnowledgeADM100 Administration AS ABAP IADM326 SAP ECC Upgrade

Recommended KnowledgeADM325 Software Logistics AS ABAP

© SAP 2009

Target Audience

This course is intended for the following audiences:SAP system administrators

Technology consultants

Project team leads

Duration: 2 days

User notes

These training materials are not a teach-yourself program. They complement the explanations provided by your course instructor. Space is provided on each page for you to note down additional information.

There may not be sufficient time during the course to complete all the exercises. The exercises provide additional examples that are covered during the course. You can also work through these examples in your own time to increase your understanding of the topics.

© SAP 2009

Course Goals

This course will prepare you to:plan and implement enhancement packages installations for SAP systems

© SAP 2009

Course Objectives

After completing this course, you will be able to:plan and implement enhancement packages installations for SAP systems

© SAP 2009

Agenda

1. Concept and Architecture2. Solution Manager: Selection of Technical Usages

Exercise 1: Solution Manager: Selection of Technical Usages3. SAPehpi: Enhancement Package Installation

Exercise 2: SAPehpi: Enhancement Package Installation4. SAPehpi: Technical Phases5. Downtime6. Planning and Preparation

© SAP AG ADM327 1-1

Concept and Architecture




© SAP 2009

Agenda


Contents:Release strategyArchitecture of SAP ERP systemsIdea of SAP enhancement packages

Concept and Architecture

© SAP 2009


SAP Business Suite

SAP NetWeaverIntegration EH

P

EHP

SAP ERP SAP CRM SAP SCM SAP PLMSAP SRM

Industry Applications

Supplementary Applications

The SAP Business Suite: Process Excellence to Reduce Cost and to Capture Opportunities

For increased end user

productivity

Harmonized UI across applications and

processes

Value Scenarios

For process integrity and

increased business and IT efficiency

SAP enhancement

packages: ‘Non-disruptive’

innovation for the SAP

Business SuiteFor faster

innovation with lower TCO

SOA enablement

For process flexibility and business agility

Embedded analytics

Industry Best Practices

For improved business performance in core

processes

Continuous innovation for every line of

business in all industries

For improved performance

For business insight and control

Best-Run NowPackages

Fast deployment and quick ROI to address

priorities in current economy

SAP NetWeaverComposition

The SAP Business Suite consists out of SAP ERP, SAP CRM, SAP SCM, SAP SRM and SAP PLM

SAP ERP consists out of ECC, XSS, XECO, BW, Portal, PI and many more. These are upgradeable units.

You can not upgrade (to) SAP ERP in general. You can upgrade (to) ECC or XSS and so on.


© SAP 2008

Apples and PearsTe

chno

logy

Appl

icat

ion

Here you can see a brief overview about the evolution of the SAP ERP architecture.

With SAP R/3 4.6 and SAP R/3 Enterprise 4.7 the SAP Web Application Server (former 'Basis') based on ABAP was the foundation of the ERP applications. There was no SAP NetWeaver (as a name), the SAP industry solutions were add-ons on top of the core applications. SAP started to support Unicode with SAP R/3 Enterprise 4.7.

Since SAP R/3 Enterprise 4.7 SAP developed new applications and shipped them as Enterprise Extensions. A concept which was based on smaller software packages to deliver new functionality to customers.

With SAP ERP 6.0 SAP provides a solution which is built on top of SAP NetWeaver, e.g the SAP NetWeaver Portal can be leveraged as a unified User Interface (UI) for all applications, also the SAP Business Warehouse (SAP BW) and SAP Process Integration are integral parts of SAP’s ERP solution. The application was also enhanced tremendously, with SAP ERP most industry solutions became part of the application plus new functionality is ready to use. Due to the new Enhancement Framework introduced with SAP NetWeaver Application Server ABAP 7.0 it was possible to ship new functionality in a more granular way. These new functions are now included in the SAP enhancement packages.


SAP ERP 6.0 – Components

Overview of SAP ERP 6.0 Components

ERP 6.0 MG Chapter 3

ABAP Components - The ABAP components of SAP ERP 6.0 consist of the:

SAP ERP Central component (SAP ECC), the SRM Server, as well as different ABAP-based add-on components. Technical component BI Content. This includes the content required to install the usage type Business Intelligence and is always installed in addition.

Java Components - Java components include:

General Java web applications; content packages for the usage type Portal or usage type PI (XI)

These components are always installed in addition to an instance of the usage type Portal or a deployment of PI (Exchange infrastructure). The components included in Java web applications are independent J2EE components, combined into a single installation tool as a product instance SAP XECO. Therefore, if you want to install one or more of these components, you will require Java components for an ERP installation, which is done by the SAPinst tool.

Additional Components - Additional components include the mobile functions of SAP ERP, for example, mobile time and travel components and mobile asset management. Furthermore, the relevant front-end components are considered as additional components.

Depending on the key capabilities or business processes you intend to deploy, you install the add-ons shown explicitly within the frame Additional Components.

Industry Add-Ons - most former industry solution add-ons are integrated into SAP ECC.


© SAP 2010

At-a-Glance SAP Enhancement Package 5 for SAP ERP 6.0

Improvements for configurable sales UI

SALES

Enhanced reporting and master data maintenanceLegal compliance for product safety and occupational healthEnhanced incident management (delivered as add-on for SAP ERP EHP 5 in September 2010)

SUSTAINABILITY: EH&S COMPLIANCE MANAGEMENT

Procurement: Integration with SAP Supplier Relationship Management service procurement functionalityFurther procure-to-pay improvements

New stock type for inventory managementSAP Auto-ID infrastructure offeringImprovements for outsourced manufacturing scenarios

PROCUREMENT AND LOGISTICS EXECUTION

Work-in-process batch tracking and valuation Engineering and manufacturing product structure synchronizationProduction order integration with ME applicationsPower lists for process ordersManufacturing analytics:

Overall equipment efficiency (OEE) analytics via Xcelsius softwareManufacturing analytics via Xcelsius

Shift report and shift note enhancementsExtensions in Lean Manufacturing (Kanban)XSteps and PI sheet enhancements

PRODUCTION PLANNING AND EXECUTION

SAP Treasury and Risk Management application:Streamlined hedge management processEnhancements in in-house cash

SAP Master Data Governance application for financials:

Managing and distributing organizational units (profit center, cost center)

Enhancements in SAP Financial Supply Chain Management set of applicationsNew features in financial accounting and new general ledger – reorganization of profit centerImproved formats of financial reportsLocalizations for India, Japan, Chile, and RussiaEnhancements in SAP Strategic Enterprise Management business consolidation functionality for legal compliance

FINANCIALS

New FMEA (failure mode and effects analysis) featuresIntegration with SAP EHS Management

QUALITY MANAGEMENT

New role: simplified and improved maintenance planning and execution processes New functionality for modeling of linear assetsMore granular cost collectionImprovements in rotable managementSAP Real Estate Management application:

Enhanced processes in commercial real estate management

ENTERPRISE ASSET MANAGEMENT

New shared service framework (SSF) as a platform for multifunctional shared service organizationsEnhancements in financials, HCM, travel management, and supplier relationship management to integrate processes with the SSF

SHARED SERVICE CENTER

Talent management: Enhanced UI and functionalities of compensation management and talent managementImproved insights into learning activities

Workforce process management: Automated performance assessment processUI flexibility and organization management analyticsExtended integration of e-recruiting and HR core system in the hiring processEnhancements for organization chart visualization

Next-generation employee self-servicesAdditional HCM – localizationsImprovements in SAP Travel Management application

HUMAN CAPITAL MANAGEMENT

Highlights


SAP Enhancement Packages & SAP ERP 6.0

What Are SAP Enhancement Packages?Optionally installed and activated software innovations for SAP ERP 6.0Software innovations include UI simplifications, functional enhancements and Enterprise servicesSAP enhancement packages are built on top of each otherSAP enhancement packages are not SAP Support Packages: SAP Support Packages contain corrections and legal changes

Quick Facts About SAP ERP 6.0Preamble: SAP enhancement packages are shipped as a delta shipment to SAP ERP 6.01. Selective Installation: Each SAP enhancement package contains new versions of existing software components. You only update software components, which are related to the functionality you want to use. After installation: No UI or process change until a Business Function is activated (ABAP). One common regression test for both, SAP Support Packages and SAP enhancement package2. Selective Activation: New functionality must be explicitly switched on to become active in the system (EHP5: ~600 Business Functions).If activated: Changes are predictable, only well described changes in the activated areas.Testing is simplified with templates, provided for every Business Function

SAP Business Suite - Stable Core

SAP NetWeaver

SAP ERP 6.0

Enhancement Packages

2006 2008 2010 2012+

SAP enhancement packages for SAP ERP include functional enhancements, industry-specific enhancements and simplifications. To discover and evaluate which innovations are shipped in which SAP enhancement package, visit the SAP Service Marketplace.

In addition, enterprise service (ES) bundles are delivered with SAP enhancement packages. Each ES bundle comprises a set of enterprise services to support an end-to-end business process (for example Order to Cash) across the SAP Business Suite. To learn which ES bundles are available and to understand the details of the services, please refer to the Enterprise Service Wiki Pages in SDN.

From a functional perspective SAP enhancement packages are built on top of each other: By installing the current SAP enhancement package the entire content of earlier packages is incorporated.

SAP enhancement packages have the same maintenance duration as the underlying core application, SAP ERP 6.0. As before, all legal changes and corrections will be available via SAP Support Packages. SAP provides SAP Support Packages for SAP ERP 6.0 on a regular basis during the defined maintenance period and, in parallel, in the equivalent SAP Support Packages for SAP enhancement packages for SAP ERP. Since Business Suite 7i2010 SAP deliver SAP enhancement packages for other SAP applications (e.g. SAP CRM or SAP SCM) as well.

The first three generations of SAP enhancement packages for SAP ERP 6.0 have been delivered and adopted in the market. This is proven by high number of live customers.


R/3/R/3 Enterprise/ECC Releases

Basis functionality(SAP Basis/SAP Web AS/

SAP NetWeaver AS)

Main business functions(-/Core)

Additional business functions(-/Extension Set)

4.6C4.6D6.106.206.306.407.007.007.007.007.107.017.027.117.30

4.6C--4.74.75.06.0(6.01)(6.02)(6.03)-(6.04)(6.05)--

---1.102.005.006.00(6.01)(6.02)(6.03)-(6.04)(6.05)--

2003200320046.0 (2005)6.0 EHP16.0 EHP26.0 EHP3-6.0 EHP46.0 EHP5--

2004 ('04)7.0 (2004s)7.07.07.0-7.0 EHP17.0 EHP2-7.3

Part ofSAP NetWeaver

Part ofSAP ERP

Releases 4.0A, 4.5A and 4.6A are missing. These were only versions for controlled availability (CA).

No SAP R/3 release exists for SAP Basis/SAP Web AS/SAP NetWeaver AS 4.6D, 6.10 and 7.10.

Concerning the ABAP part, SAP Web AS 6.30 is the same as SAP Web AS 6.20.

Several renaming took place in the past; here are a few of them:

SAP R/3 was renamed to SAP R/3 Enterprise beginning with 6.20/4.7/1.10

SAP R/3 Enterprise was renamed to SAP Enterprise Resource Planning Central Component (SAP ECC) beginning with 6.40/5.0/5.00

SAP Basis was renamed to SAP Web Application Server ABAP (SAP Web AS ABAP) beginning with 6.10

SAP Web Application Server was renamed to SAP NetWeaver Application Server ABAP beginning with 7.00

Starting from ECC 6.01 the new releases are called SAP enhancement packages.

The brackets starting from 6.01 indicate, that not all software components have to be on this release level.


© SAP 2010

SAP R/3 4.6C

Basis, including TMS,performance tools,development tools, user administration,and many more

Core applications

Modifyingadd-on,IS-U, IS-Oil, and many others

Modification free add-on,Plug In, Y2K check, and many others SAP R/3 4.6C

ABAP

SAP_APPL 4.6CAdd-On

Add-On

SAP_ABA 4.6C

SAP_BASIS 4.6C

SAP_HR 4.6C

The software components of an SAP R/3 4.6C remain more or less as they are up to the latest release ECC 6.05. But during the releases these software components were updated and new software components were added.

The figures do not show a complete list of all software components.


© SAP 2010

SAP R/3 Enterprise 4.7x2.00

Basis is now calledSAP Web AS ABAP

Enterprise ExtensionsEA-APPL,EA-HR,and others

SAP R/3 4.7

ABAP

SAP_APPL 4.7Add-On

Add-On

SAP_ABA 6.20

EE2.05

EE2.00

SAP_BASIS 6.20

SAP_HR 4.7

EE2.05

EE2.00

The Enterprise Extensions were introduced with R/3 Enterprise 4.7. They should help to change the core software components SAP_APPL and SAP_HR as less as possible, in order to keep them stable and to simplify upgrades for customers.

The Basis was renamed.


© SAP 2010

SAP ECC 6.0

Industry ExtensionsIS-UT,IS-Oil,and others

SAP ECC 6.0

ABAP

SAP_APPL 6.00Add-On

Add-On

SAP_ABA 7.00

EE6.00

EE6.00

IE6.00

IE6.00

IE6.00

IE6.00

SAP_BASIS 7.00

SAP_HR 6.0

EE6.05

EE6.00

Basis is now calledSAP NetWeaver AS ABAP

Former SAP for Industry Add-Ons were integrated into SAP ECC 6.0 as Industry Extensions.

Industry Extensions are grouped by industry business function sets and consist of one or more business functions (BF) which can be activated separately.

It is not possible to activate business functions from different industry business function sets at the same time.

The Switch Framework (SFW) allows you to externally control the visibility of Repository objects or their components by means of switches. The main purposes of the Switch Framework are to:

Simplify an ABAP-based system landscape by adopting one or more industry solutions in a standard system

By using the Switch Framework, most industry solutions and a restricted list of repository objects are delivered in an inactive state in the system. You no longer need to install an industry solution – you can activate it when required.

Introduce a new, modification-free enhancement concept

The Switch Framework is integrated in the ABAP Workbench and works closely together with the Enhancement Framework.

The Enhancement Framework enables the implementation of the best-practice solutions defined within an industry, while the Switch Framework controls which enhancement implementations are to be performed.

The Switch on industry solutions and Enterprise Add-Ons

Develop new functions without affecting the existing ones

Enhance delivered partner and customer systems by adding functions in the context of the Enhancement Framework

The Basis was renamed again.


© SAP 2010

SAP ECC 6.05 (Example)

SAP ECC 6.05

ABAP

SAP_APPL 6.05Add-On

Add-On

SAP_ABA 7.02

EE6.05

EE6.00

IE6.05

IE6.00

IE6.00

IE6.00

SAP_BASIS 7.02

SAP_HR 6.0

EE6.05

EE6.00

Some software components are on 6.0, some are on 6.05

With SAP enhancement packages new Enterprise Business Functions and Industry Business Functions are delivered.

Customers can install Business Functions via the implementation of a technical usage, which can contain ABAP and non-ABAP component versions and PI/Portal/BW-content .

Selective Installation: With SAP enhancement package installation, not all software component versions will be changed, but only those selected.

Selective Activation: You can select the required business function within an SAP ECC system


Industry ExtensionsIndustry Extension consist of

Business Functions Sets (BFS) (one or more) consists ofBusiness Functions (BF) (one or more)activated per Switch FrameworkOnly ONE Industry Extension can be activated per instanceAn industry extension cannot be deactivated once it has been activated (no switch to another industry solution possible!!)Activation of one or more Business Functions (BFS and BF) per instance possibleSee note 838003 for further information

Enterprise ExtensionsParts of former industry solutions were integrated in Enterprise ExtensionsEnterprise Extensions consists of

Generic Business Functions (one or more)Activation of all Enterprise Extensions by the SAP Switch FrameworkThe Enterprise Extensions are available in addition to the Industry ExtensionsActivation of one or more Enterprise Extension per instance possibleActivation of more than one generic business function of the Enterprise Extension at the same time possibleSee note 838002 for further information

SAP ECC 6.0 and above: Industry and Enterprise Extensions

Examples for Industry Extensions (see note 838003 and ERP 6.0 master guide for detail information):

ECC-DIMP, DIMP, DI, IS-SW, IS-HT, IS-MP, IS-AD, IS-A is now included in Software component ECC-DIMP = 'Discrete Industries & Mill Products'

INSURANCE is now included in Software component INSURANCE = 'Insurance'

IS-U/CCS, ISUCEN and IS-U/I is now included in Software component IS-UT

Examples for Enterprise Extensions (see note 838002 and ERP 6.0 master guide for detail information):

BANKING, BANK/CFM, TR-TM-PO are now included in Extension EA-FINSERV

EHS is now included in Extension EA-APPL

PI and PI-A are now included in Extension SAP_APPL and SAP_HR

General information about available industry solutions and how they are deployed within ERP 6.0

ERP 6.0 Master Guide

Note 838002 for Enterprise Extension overview

Note 838003 for Industry Extension overview


Switch Framework:Transaction SFW5

Activation of Industry and Enterprise Extensions

Via the Switch Framework (transaction SFW5) Business Functions Sets can be activated.


"Switchable" Industry Solutions in SAP ECC 6.0

Single Activation

Multiple Usage

Exclusive Activation Multiple ActivationSAP ECC Industry Extension Healthcare 6.0 SAP ECC Enterprise Extension Consumer Products 6.0

SAP ECC Industry Extension Chemicals 6.0 SAP ECC Enterprise Extension Defense Forces & Public Security 6.0

SAP ECC Industry Extension Contract Accounting 6.0 SAP ECC Enterprise Extension Financials 6.0

SAP ECC Industry Extension Discrete Industries & Mill Products 6.0 SAP ECC Enterprise Extension FERC: Regulatory Reporting 6.0

SAP ECC Industry Extension Insurance 6.0 SAP ECC Enterprise Extension Financial Services 6.0

SAP ECC Industry Extension Media 6.0 SAP ECC Enterprise Extension Global Trade 6.0

SAP ECC Industry Extension Mining 6.0 SAP ECC Enterprise Extension Human Capital Management 6.0

SAP ECC Industry Extension Oil & Gas 6.0 SAP ECC Enterprise Extension Incentive & Commission Management 6.0

SAP ECC Industry Extension Public Services 6.0 SAP ECC Enterprise Extension Industry-specific Sales Enhancements 6.0

SAP ECC Industry Extension Retail 6.0 SAP ECC Enterprise Extension Joint Venture Accounting 6.0

SAP ECC Industry Extension Telecommunications 6.0 SAP ECC Enterprise Extension PLM 6.0

SAP ECC Industry Extension Utilities, Waste & Recycling 6.0 SAP ECC Enterprise Extension Public Sector Management 6.0

SAP ECC Enterprise Extension Retail 6.0

SAP ECC Enterprise Extension SCM 6.0

SAP ECC Enterprise Extension Travel Management 6.0

You can activate multiple Enterprise Extensions but only one Industry Extension at the most.


Traditional SAP application innovation lifecycle

Cos

t

EHPEHP

Maintenance: SAPSupport Package Stack • Legal/tax changes,

corrections, mandatory

• Technically a set of SAP Support Packages and patches

Release Upgrade

Upgrade

Support PackageSAP

system

New SAP application innovation lifecycle

Time

SAP enhancement packages for SAP ERP

SAP Support Packages, SAP Enhancement Package and Upgrade

Support Package

Support Package

Support Package

Support Package

Support Package

Upgrade

• New & improved functionality

• Optional, new software components

• Activate new functionality in Switch Framework via Business Function

Install SAP enhancement packages for SAP ERP combined with SAP Support Package Stack as a maintenance activity with only minor additional effort.

SAP ERP (ECC 6.0)

Since the installation process is decoupled from activation, you can now continuously provide the newest functionality to the system along with your regular maintenance activities. In order to use synergy effects and to minimize effort (especially regarding potentially needed modification adjustments – see above), the ECC components of the SAP ERP enhancement packages should be applied within one queue, together with the required SAP Support Packages. Using this strategy, SAP enhancement packages can be installed without causing disruption as a normal maintenance activity together with SAP Support Packages. Please note that once an SAP enhancement package is installed, you cannot reverse the installation. If you are not sure if you want to leverage dedicated functionality, use a sandbox system to explore the new functionality.


7-2 maintenance strategy for new releases of the core applications* of SAP Business Suite: 7 years of mainstream maintenance, 2 years of extended maintenance

Solution Changes - New 7-2 Maintenance Strategy

Before

New

* 7-2 strategy applies to new releases of the core applications of SAP Business Suite, starting with SAP CRM 7.0, SAP SRM 7.0, SAP SCM 7.0, SAP PLM 7.0; plus SAP ERP 6.0 (EHP4) and SAP NetWeaver 7.0. Industry-specific add-on applications and SAP enhancement packages based on these core application releases will offer mainstream and extended maintenance in line with these releases.

** Enhancement packages: Illustrative only; does not reflect exact shipment times and frequency.

Dec

Mainstream Maintenance Extended Maint. (+ 2%)*

SAP ERP 6.0, SAP NetWeaver 7.0


SAP CRM 7.0, SAP SCM 7.0, SAP SRM 7.0

Ramp-Up

Dec

Cust.-Spec.Maintenance


Ramp-Up

2011 20122009 2010 20142013 2015 2016 2017200820072006

7 2

EHP** EHP** EHP** EHP** EHP** EHP**

EHP** EHP** EHP** EHP**

Nov Dec




SAP CRM 7.0, SAP SCM 7.0, SAP SRM 7.0

Ramp-Up

Dec



Ramp-Up

2011 20122009 2010 20142013 2015 2016 2017200820072006

7 2

EHP** EHP** EHP** EHP** EHP** EHP**

EHP** EHP** EHP** EHP**

Nov

Mar

Mar

Mar

Mainstream Maintenance Ext. Maint. (+ 2%)*


Ramp-Up

EHP** EHP** EHP** EHP**Ext. Maintenance

(+ 4%)*

2011 20122009 2010 20142013 2015 2016 2017200820072006


Mar

Mar

Mar

Mar

Mar

Mar

Mainstream Maintenance Ext. Maint. (+ 2%)*


Ramp-Up

EHP** EHP** EHP** EHP**Ext. Maintenance

(+ 4%)*

2011 20122009 2010 20142013 2015 2016 2017200820072006


In November 2008 SAP introduced the 7-2 maintenance strategy for new core application releases introduced and shipped to customers after this point in time. In particular, for SAP CRM 7.0, SAP SCM 7.0, SAP SRM 7.0, and SAP PLM 7.0, SAP will offer mainstream maintenance to December 2015, and extended maintenance for two additional years to December 2017. In parallel, maintenance for SAP ERP 6.0 and SAP NetWeaver 7.0 will also be adapted to this new strategy, meaning that mainstream maintenance for these releases is extended from March 2013 to December 2015; extended maintenance will be offered to December 2017.

Main advantages of this new strategy:

Long-term planning security and higher return on investment – nine years’ maintenance horizon

Additional time to deploy and benefit from innovation delivered via SAP enhancement packages

Less additional cost for extended maintenance


Improved Software Lifecycle

In previous days: Upgrades … … and now: SAP enhancement packages

Time

Business Requirements

= innovation gap = R/3 4.6C standard

R/3 4.6C Implementation Time

Busi

ness

Req

uire

men

ts /

Sys

tem

Fun

ctio

nalit

y

Business Requirements

= innovation gap

ECC 6.0

= ECC 6.0 standard

EHP 2 EHP 4

Upgrade as a major business activity every 5-6 years to fulfill business requirements.

New functionality implemented in digestible portions via SAP enhancement packages.

Bus

ines

s R

equi

rem

ents

/ S

yste

m F

unct

iona

lity

= ECC 6.0 standard = EHP functionality

ECC Upgrade

Permanently decrease functional gapWith SAP enhancement packages for SAP ERP continuous provisioning of new functionality is possible.

EHP 5EHP 3

The key difference between SAP enhancement packages for SAP ERP and other, older technologies is the improved software lifecycle. This is given through the selective character and the capability that no UI or process changes take place after the installation as new functionality must be explicitly switched on to become active in the system.

As a result the continuous provisioning of new functionality is possible with SAP enhancement packages for SAP ERP.

Thereby companies can permanently decrease the functional gap.


© SAP 2010

1. Always install parts of SAP enhancement packages combined with SAP Support Pack Stack as a maintenance activity with minor additional effort and facilitated by the new installation tool (SAPehpi).

Support Package

Support Package

EHPEHPInactive Business

Functions

Time

Business Function Activation

active active

2. Select and activate the functionality needed by your business using the Switch Framework. Functionality your business does not need will remain dormant.

Support Package

Support Package

How is this Possible?

SAP System


Example: SAP Enhancement Package 5 for SAP ERP 6.0 - Focus: Installation

FactsSelective, component-wise installation: With SAP enhancement packages you can selectively update software components. Matching combinations of software components, as well as PI/Portal/BW-content and Java software components are grouped by Technical Usages. As the number of software components are limited, e.g. a separated installation of logistics and financials (both are located in the core software component SAP_APPL/EA-APPL) is not possible.Strict separation of technical installation and the implementation of the new functionality: Explicit activation separately for each Business Function (with SAP Enhancement Package 5 for SAP ERP 6.0: ~600 Business Functions). However only backend functionality (ABAP) is switchable.

SAP ECC Core (6.00)

Switch FrameworkEnterpriseExtensions

IndustryExtensions

Architecture

EHP 4 ..

SAP NetWeaver Application Server 7.0

EHP 5

1

1. Installation of EHP components with regular maintenance

SAP_APPL (600)

EA-APPL(600)

IS-OIL(600)

EA-HR(605)

SAP_HR(605)

SAP_ABA (702)SAP_BASIS (702)

1Technical Usage:

“Human Capital Management”

Step 1:

A selective exchange of one component is possible: With SAP enhancement packages you can selectively update software components. Please note that matching combinations of software components, as well as PI/Portal/BW-content and Java software components are grouped by Technical Usages. As the number of software components are limited, e.g. a separate installation of logistics and financials (both are located in the core software component SAP_APPL/EA-APPL) is not possible.

Step 2:

Strict separation of technical installation and the implementation of the new functionality: Explicit activation separately for each Business Function (with EHP3 we have approximately 150 Business Functions). However only backend functionality (ABAP) can be switched.


Equivalent SAP Support PackagesExample

time

Equivalent SAP Support Packages (see also SAP note 1064635)Are time-synchronized SAP Support Packages for different versions ofone software component (SWC)Contain identical corrections for capabilities that both versionshave in commonDiffer only with respect to corrections for new capabilities(which are only provided by the higher SWC version)SAP Support Package Stacks for SAP ERP include SAP Support Packagesfor SAP NetWeaver.

SAP ERP 6.0(SWC version 6.00) SPS 20

SPS 1

SPS 23SPS 21

SAP ERP 6.0 Enhancement Package 5 for SAP ERP 6.0 (605)

SPS 22 SPS 24

SPS 2

Equivalent (same correction level), time-synchronized Support-Packages

SPS 25

SPS 3

SAP enhancement packages contain also a certain level of corrections therefore require an equivalent SAP Support Package Level for the software components which remain on version 6.00.

Therefore SAP enhancement packages should always be installed together with the required SAP Support Package Stack. As a consequence customers have to adjust possible modifications and test the application, however this was the same with the pure SAP Support Package Stack installation. Efforts should be expected to be comparable or slightly higher.


Example: SAP Enhancement Package 5 for SAP ERP 6.0 - Focus: Activation

FactsSelective, component-wise installation: With SAP enhancement packages you can selectively update software components. Matching combinations of software components, as well as PI/Portal/BW-content and Java software components are grouped by Technical Usages. As the number of software components are limited, e.g. a separated installation of logistics and financials (both are located in the core software component SAP_APPL/EA-APPL) is not possible.Strict separation of technical installation and the implementation of the new functionality: Explicit activation separately for each Business Function (with SAP Enhancement Package 5 for SAP ERP 6.0: ~600 Business Functions). However only backend functionality (ABAP) is switchable.

SAP ECC Core (6.00)

Switch FrameworkEnterpriseExtensions

IndustryExtensions

Architecture

EHP 4 ..

SAP NetWeaver Application Server 7.0

EHP 5

1

1. Installation of EHP Components with regular maintenance

SAP_APPL (600)

EA-APPL(600)

IS-OIL(600)

EA-HR(605)

SAP_HR(605)


1

2

SAP_APPL (600)

EA-APPL(600)

IS-OIL(600)

SAP_HR(605)


EA-HR(605)

2. Activation ofBusiness Functions

2 Business Function:“Employee Interaction Center”

Step 1:

A selective exchange of one component is possible: With SAP enhancement packages you can selectively update software components. Please note that matching combinations of software components, as well as SAP NetWeaver PI/SAP NetWeaver Portal/SAP NetWeaver BW-content and AS Java software components are grouped by Technical Usages. As the number of software components are limited, e.g. a separate installation of logistics and financials (both are located in the core software component SAP_APPL/EA-APPL) is not possible.

Step 2:

Strict separation of technical installation and the implementation of the new functionality: Explicit activation separately for each Business Function (with EHP3 we have approximately 150 Business Functions). However only backend functionality (ABAP) can be switched.


Switch Framework Enables Optional Activation of Business Functions

With the Switch Framework it is possible to control the activation of SAP ERP objects.

Activating a Business Function triggers switches.

The switch controls whether the switch-controlled code is executed or not at runtime.

The Switch Framework is a proven concept (already used to retrofit Industry Solutions in ERP 6.0).

Switch Framework

SAP ECC

Fundament: Enhancement Framework is the solution of SAP NetWeaver 7.0 to allow adaptations of development objects without touching them.

All enhancements offered by Enhancement Framework can be switched by the Switch Framework.

All reports, includes, classes, function modules, and Web Dynpro ABAP UIs can be changed and enhanced using the Enhancement Framework.

The new BAdI is also integrated in the Enhancement Framework.

Every change is hidden behind a switch

About 50 Business Functions delivered with SAP Enhancement Package 2 for SAP ERP 6.0 that can be activated separately.

In the background happens a lot, activation of code an DDIC objects.

Switch and Enhancement Framework is not totally new and already used for IS retrofit since SAP ECC 6.0.


ArchitecturalView: techn. Switch

Repository View:“Enhancement Framework”

Switch 1

Business Function Set

Bus Fct F1 Bus Fct F2

Bus Fct F4

Business Function Set

Bus Fct F1 Bus Fct F2

Bus Fct F4

Industry Business Function Set “Media“

Advertising Mgmt.

Press Distribution …

Enhancements

IMG-nodes

EnhancementsSwitch BC Set

Screen

Element 1

Element 2

Enterprise Business Function

HCM, Administration Real Estate

Switch 2

Switch 3

Switch 4

Switch 5

Switch n

Business View:Business Function

…

Switch Framework - How Does It Work?

A switch controls the vis ibility of other repos itory objects .

The Switch Framework Enables Optional Activation Of Business Functions:

With the Switch Framework, it is possible to control the activation of SAP ERP objects. Activating a business function triggers switches, which then “influence” the execution of the code enhancements. These switches ensure that you only see the new functions if you have activated them. All functional changes and the impact of an activated business function are made transparent in advance by the documentation. Bear in mind that once a business function is activated you cannot reverse it. Please note: The activation process starts a job in your SAP system which automatically performs all changes in the system.

The Switch Framework is a proven concept as it was already used to retrofit Industry Solutions in ERP 6.0.


Activities before the activation …View the list of business functions now selectableAccess documentation, release notes, test catalogue and possible dependencies from hereInstall the relevant documentation, refer to SAP note 1066110

BenefitsTransparency of all system and UI changes that will take placeStability for all other parts of the solution

Activities after the activation …Activate the chosen business functionConfigure the chosen business function

BenefitsNew coding becomes active only where activatedFaster implementation because only activated parts are configured

Transaction: SFW5

Activate And Configure

The switch transaction shows all the business functions that can now be activated after the installation of the new software components.

In the switch framework transaction you can:

View the list of business functions available with the latest system setup

Access documentation, release notes, test catalogue, and possible dependencies

Install the relevant documentation, refer to SAP note 1066110

Before the activation you get transparency of all system and UI changes that will take place.

Afterwards you can activate the chosen business functions and perform the configuration tasks.

By that the new coding becomes effective. All other parts of the system remain stable.


Switch Framework: Transaction SFW5Transport of Switch Settings

Sandbox DEV QAS PRDtransport transport

Activate Business Functions manually

Activate Business Functions manually

Generate transport with switch settings

Import transport with switch settings

Import transport with switch settings

Transaction: SFW5


Things You Should Know Before Installing SAP Enhancement Packages

Only one SAP enhancement package level per systemOne application system can only consist of one SAP enhancement package level (e.g. SAP Enhancement Package 4 for SAP ERP 6.0 xor SAP Enhancement Package 5 for SAP ERP 6.0). Hence installed SAP enhancement package components have to be updated with every future SAP enhancement package implementation.

Industry SolutionsCustomers who have activated an industry business function set have to include the corresponding SAP enhancement package industry software component during installation.

EHP Installation and functional activation is partially non-reversible

EHP Facts

SAP enhancement packages are “cumulative”When installing the latest SAP enhancement package you will automatically get all functionality delivered with previous ones.Technically the SAP enhancement package installation delivers only changed objects to your system (delta shipment):- In case you have already installed SAP Enhancement Package 4 for SAP ERP 6.0 you will only install the new objects of SAP Enhancement Package 5 for SAP ERP 6.0.- In case you have installed SAP Enhancement Package 3 for SAP ERP 6.0 you will install SAP Enhancement Package 4 for SAP ERP 6.0 and SAP Enhancement Package 5 for SAP ERP 6.0 objects in one step

SAP Enhancement Package 2 for SAP NetWeaver 7.0 available

Technical Delivery

Modification AdjustmentDuring installation of SAP enhancement packages modifications must be adjusted – even if no business function has been activated.

Regression Test requiredThe installation of an SAP enhancement package requires a full regression test – even if no business function has been activated.

Effort Estimation Most customers say that the installation effort is a bit higher with SAP enhancement packages (without activating business functions) compared to pure SAP Support Package updates.

Project Perspective


Comparing SAP Enhancement Packages for SAP ERP and SAP NetWeaver

SAP ERP

SAPNetWeaver

Installation procedure

Impact of installation

Selective activation

New functions are switched on selectively (ABAP switch framework)

SAP provides an impact analyzer tool and test case templates

Both: Efficient and fast installation with SAP enhancement package installer based on proven SAP software lifecycle management tools

Both: No UI or process change for end users after installation of SAP enhancement package.

Switching procedure between old and new UI screens is providedNetWeaver

enhancement package adds new functionality, but does not replace existing functionality

SAP Enhancement Package 2 for SAP NetWeaver supports SAP Enhancement Package 5 for SAP ERP 6.0

SAP enhancement packages for

So where is the difference between SAP enhancement packages for SAP ERP and for SAP NetWeaver?

There are a lot of similarities. The installation procedure is in both cases efficient and fast. The installation is performed with the SAP enhancement package installer based on proven SAP software lifecycle management tools.

In both cases there is no UI or process change for end users after installation of an SAP enhancement package and by that the impact of installation is limited. Furthermore new functions are switched on selectively, either with the switch framework or other, alternative procedure.


SAP NetWeaver 7.0(foundation for the SAP Business Suite)

EHP EHP EHP

SAP BS 7i2010

Continuous Innovation

ERPCRM SCM

PLMSRM

EHP EHP EHP

SAP Business Suite 7i2010 core applications:

SAP Enhancement Package 5 for SAP ERP 6.0SAP Enhancement Package 1 for SAP CRM 7.0SAP Enhancement Package 1 for SAP SRM 7.0SAP Enhancement Package 1 for SAP SCM 7.0

SAP enhancement packages across the SAP Business Suite 7 Innovations 2010

Non

-SAP

SAP Business Suite 7 Innovations 2010

EHP EHP

Composite Applications

SAP NetWeaver

Accelerated innovation

PI 7.1 …CE 7.1

Increasing flexibility through composition

SAP Business Suite core applications

SAP Enhancement Package 5 for SAP ERP 6.0

SAP Enhancement Package 1 for SAP Customer Relationship Management (SAP CRM) 7.0

SAP Enhancement Package 1 for SAP Supplier Relationship Management (SAP SRM) 7.0

SAP Enhancement Package 1 for SAP Supply Chain Management (SAP SCM) 7.0

SAP Product Lifecycle Management (SAP PLM) as part of SAP ERP


SAP Enhancement Package InstallerStandard Installation Tool

SAP enhancement package installer (SAPehpi)

Installation tool

Reliable &intuitive

Mature, stable and optimized system switch procedureImproved user experience due to intuitive guided procedureStreamlined installation process

Minimizeddowntime

Risk mitigation due to isolated shadow systemPlan for some additional technical preparation and execution runtime


Summary

Gain stability and access to innovation

Reduce risk and downtime

Upgrade only the enhancements applicableto your business

Speed implementation and test less

Reduce training effort

Benefits of the new SAP enhancement package approach:


Upgrade only the enhancements applicable to your business



Reduce training effort



Solution Manager: Selection of Technical Usages




Agenda


Contents:Create XML/TXT files for the installation with the Maintenance Optimizer

Solution Manager:Selection of Technical Usages


Overview: Main Steps of SAP Enhancement Package Installation Procedure

SAP ERP 6.0

ABAP

ECC Server

SAP NetWeaver Portal

Java

Portal

ABAP

BW

SAP NetWeaverBW

SAP NetWeaverPI

ABAP + JAVA

Sample SAP system landscape

SAPehpiSAINT/JSPM

SAPehpiSAINT/JSPM

XML Document

SAPehpiSAINT/JSPM

SAPehpiSAINT/JSPM

SAPehpiJSPM

SAPehpiJSPM

SAPehpiSAINT

SAPehpiSAINT

Package Configuration File

(„Stack XML“)

If SLD and SMSY are configured correctly,

Maintenance Optimizer will calculate the

packages for every system that is part of the

SAP ERP solution

SAP Solution Manager

Maintenance Optimizer

SMSYSLD

Prepare SAPSolution Managersystem

1

Calculate software packages and generate configuration file with Maintenance Optimizer

2

Install the software packages on every system that is part of your SAP ERP solution

3

The SAP Solution Manager creates a customer specific stack XML which contains the information about the queue of selected support and SAP enhancement packages.

Now the installation tools use this information to bring the specific system to a well-defined and consistent system state. The tool to use for installation depends on the type of software component:

ABAP and Java software components are installed using the SAP enhancement packages installer with minimal downtime.

Portal Content is installed using the JSPM tool

XI Content is usually uploaded from within the Integration Repository, which is part of usage type Process Integration (PI) of SAP NetWeaver.

BW Content is applied as common SAP Support Packages.

Alternatively ABAP components can be installed using the SAINT tool and Java software components can be are installed using the JSPM tool.

Please note that there might be limitations.


SAP NetWeaver Support Package equivalentEach SAP ERP 6.0 SAP Enhancement Package 5 SAP Support Package Stack contains the definition of an equivalent SAP NetWeaver Support Package Stack

SAP NetWeaver SP Stack contentSAP NetWeaver Support Package Stacks contain SAP Support Packages for SAP_BASIS, SAP_ABA, SAP_BW and PI_BASIS

Other software componentsSAP NetWeaver Support Package Stacks do not contain SAP Support Packages for SAP ERP application software component

SAP Enhancement Package 5 for SAP ERP 6.0 Support Package Stack selectionYou must select an SAP Enhancement Package 5 for SAP ERP 6.0 SAP Support Package Stack to calculate SAP Support Packages for an SAP Enhancement Package 5 for SAP ERP 6.0 system .

SAP Enhancement Package 5 for SAP ERP 6.0 Support Package Stack contentSAP Enhancement Package 5 for SAP ERP 6.0 SAP Support Package Stacks contain SAP Support Packages for every available SAP Enhancement Package 5 for SAP ERP 6.0 software component version

Other software componentsSAP Enhancement Package 5 for SAP ERP 6.0 SAP Support Package Stacks do not contain SAP Support Packages for SAP ERP software component version 6.00 and SAP NetWeaver software components.

Maintenance of SAP Enhancement Package 5 for SAP ERP 6.0 System: SAP Support Packages

SAP ERP 6.0 Support Package equivalenceEach SAP ERP 6.0 Enhancement Package 5 Support Package Stack contains the definition of an equivalent SAP ERP 6.0 Support Package Stack

SAP ERP 6.0 Support Package Stack contentSAP ERP 6.0 Support Package Stacks contain SAP Support Packages for every SAP ERP 6.0 software component version

Other software componentsSAP ERP 6.0 Support Package Stacks do not contain SAP Support Packages for SAP Enhancement Package 5 for SAP ERP 6.0 software component versions and SAP NetWeaver software component

Determine equiv. SAP Support Packages for SAP

NetWeaver 7.0 EHP 2

Select SAP ERP 6.0 EHP5SAP Support Package Stack

Determine equiv. SAP Support Packages for SAP

ERP 6.0 components

The SAP Solution Manager Maintenance Optimizer will perform the following steps automatically …


Request for Stack Configuration File

Needed components ofSAP Enhancement Package 5 for SAP ERP 6.0 are defined withinSAP Solution Manager system

How is this stack file created?

A properly installed Solution Manager system is required to generate the xml and txt file to install an individual selection off SAP Enhancement Package 5 for SAP ERP 6.0.

This step is mandatory for the SAP ECC 6.05 update!


© SAP 2010

SAP Solution Manager 7.01

latest SP level

MOpzMOpz

Maintenance Optimizer (MOPZ)

PPMS

Download Basket

SMSY

E2E SAP Enhancement Package Installation Process

Java Schema

ABAP Schema

SCSInsta nce

ENQ Server(Java)

MSG Server(Java)

Add -I n Cen tral Ins ta nce

Java Server Pr ocess

Java Server Process

Server Process

Java Dispa tcher

SDM

Java

ABAP

ABAPDispatcher

WorkProcessWork

ProcessWorkProcess

Gateway

ICM

IGS

ENQ WP(ABAP)

MSG Server(ABAP)

Globa l FS

StackConfiguration

File.xml

SAP ERP 6.0Based on SAP NW 7.0

SAP ERP 6.0 EHP 5based on SAP NW 7.0 EHP 2

Technical Usagesbased on

SAP EHP 5*

a

c

Select required Technical Usages and SP levela

SAPehpi4

MOpz generate Stack Configuration fileand calculates dependent software components and SAP Support Packages

b

5

Download SW components and SAP Support Packagesvia Download Manager

c

2 Maintain System landscape via SLD/SMSY

2

3

3 Run Maintenance Optimizer

Provide your download to SAPehpi4

Perform the SAP enhancement package installation 5*Example for SAP ERP 6.0. CRM 7.0, SRM 7.0 und SCM 7.0 you choose the SAP enhancement package

1 Run Landscape Verification Wizard

Landscape Verification

Wizard1

SLD

bSPsEHPSW

Comp.

SPsEHP SWComp.

E2E SAP Enhancement Package installation process – example

Customer plans to update a SAP ERP 6.0 system to SAP Enhancement Package 5 for SAP ERP 6.0.

Therefore the customer needs to have installed a SAP Solution Manager 7.0 on the latest available SAP Support Package level (SPS 23). In addition SAP Solution Manager Maintenance Optimizer needs to be configured.

Before the customer starts a new maintenance transaction the Landscape Verification Wizard need to run to check the system data in SMSY for inconsistencies and if needed provides hints to update the system data.

As soon as the system data in SMSY is maintained a new maintenance transaction can be started.

During the maintenance transaction the customer has to select the required Technical Usages as well as the target SAP Support Package level. This selection is used by the Maintenance Optimizer to generate a Stack Configuration File, the SAP enhancement package software components as well as the dependent SAP Support Packages.

These files can be downloaded via Download Manager. After the download the files have to be provided to the SAP enhancement package installer. The SAP enhancement package installer uses the files to update the SAP ERP 6.0 system to an SAP ERP 6.0 system including SAP Enhancement Package 5 for SAP ERP 6.0.


Generation of Stack Configuration File:Initial Setup (Extract)

AISUSER:user assignment

SM59:RFC destinations

A prerequisite for generating the xml and txt file is a properly installed and configured Solution Manager system.

The Solution Manager system must connect to the system being upgraded and to the SAP Service Market Place.

This also includes a mapping of the Solution Manager system user to an SAP Service Market Place user

and properly configures RFC destinations to the SAP Service Market Place.


Solution Manager Preparation (1)

1. In transaction SMSY, check the server:Before you can check the set up of your SAP system, it is essential to review, if an entry for your server was created or to create it.

1) in “SMSY”, navigate in the left frame to “Landscape Components Server” Check if the Server name is in place

2) To create a new entry, click with right mouse button on server, choose “Create New Server” and fill in the dialog with your server’s data (hostname).

2. After having checked your server, proceed to check the SAP system in transaction SMSY.

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

Open SAP ERP and check if the SID is in place

2) To create a new entry, click with right mouse button on “Systems” and fill in your system’s data (even if you are already on ERP EHP, register as regular ERP!)



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

4. Then click on the RFC wizard and create an RFC connection to that SAP system and client 000 (or any other client).5. Now you can automatically

read the SAP system data via the button „Read System Data Remote“.

This should remotely read the SAP system data and update the information about this SAP system. Check the tab “Clients” and/or “Software Components” and verify that the information there has been updated. It is important to have the exact versions of the Software Components maintained. Only then a valid stack of SAP Support Packages and SAP enhancement packages can be calculated!



6. Create a new logical component. Also in “SMSY”, click on “System Groups and Logical Components”.

With the right mouse button click on “Logical Components” and create a new logical component.

Fill in your system data, let the name for your logical component start with “Z...”.

7. In the “Current System Assignments” of the newly created logical component, add your system with the appropriate role (e.g. as “Production System”).



8. Check transaction “SOLUTION_MANAGER”for an existing solution. If you do not have a solution yet, create one.

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

SOLUTION_MANAGER:create solution

In the Solution Manager system in transaction SOLUTION_MANAGER: create a solution (application) and assign the logical component assigned to the SAP system entry from transaction SMSY.

The logical component is the link between the solution and the SAP system.



Change into edit modeSelect line (new line in field logical component, F4 help)Select your system from list (SAP ERP, logical component)Save selectionClick on button “complete system data replication”before saving

10. Then add your SAP ERP system (e.g. SAP ECC, SAP XSS, SAP NetWeaver BW, SAP NetWeaver Portal) to the solution as follows:

Further help:Note 1134872 (FAQ for Stack Delta Files in EPS) Note 1122966 (Maintenance Optimizer for EHP)

SOLUTION_MANAGER:assign system via

logical component



If you have a dual stack SAP system, then make sure that the Java part is correctly maintained in SMSY.

The correct way is to register both the Java system and the ABAP system in a central SLD (via Visual Administrator) and to schedule SLD update jobs from within SMSY_SETUP.

On the right side you can see how a properly maintained Java system looks like.

11. Java systems


Download Packages and Generate Stack XML via Maintenance Optimizer

Generation of the XML stack fileSolution Manager generates a XML file. This is a requirement for the installation!

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

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


Generation of Stack Configuration File:Create Maintenance Transaction

1. Enter description2. Choose product version3. Choose system(s)

Select the solution (application) and create a maintenance transaction.


Generation of Stack Configuration File:Scenario ‘Enhancement Package Installation'

1. Calculate Files Automatically2. Enhancement Package Installation


Generation of Stack Configuration File:Select Technical Usages

• Select desired technical usages

Select the technical usages, that are required from a business point of view. This selection should not be done by the administrator but is part of the upgrade project planning.


Generation of Stack Configuration File:Select Operating System

1. select operating system and database2. …3. Select Download Basket

• Now the files can be downloaded with the Download Manager

Select operating system.

Maybe there are stack independent files. Select these also.


Generation of Stack Configuration File:Copy xml File for SAPehpi

Copy the xml file, so it can be accessed by SAPehpi

The xml and txt files are generated in the transport directory of the Solution Manager system, subdirectory EPS\in.

Copy the XML file so it is accessible by the SAPehpi.


Getting started with SAP Enhancement Package Installation: Important Prep. Steps

1. Solution Manager preparation

In general: review the set up of your Solution Manager System and System landscape (Transaction SMSY), SAP note 1022072 gives for further information (e.g. product version of your system has to be SAP ERP 6.0 NOT SAP ECC 6.0)

Download of SAP enhancement packages and SAP Support Package Stacks only with use of Maintenance Optimizer when using SAPehpi

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

Up-to-date Solution Manager System (Patches), more information: SAP note 1165438

XML file is generated and stored in <transport directory>/EPS/in of Solution Manager system (configuration required!)

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

Note 1134872 (FAQ for Stack Delta Files in EPS)

Note 1122966 (Maintenance Optimizer for EHP)

Note 1090202 (MOPZ: adjust stack delta XML)

Note 1165587 (MOPZ: EHP stack selection)

Note 1277035 (EHP4 product data missing)

2. Download SAP enhancement package

Download the SAP enhancement packages components via selection of “Technical Usage”, for more information see SAP note 1165438

3. Get familiar with the SAPehpi

Download & Study EHP Installer Guide provided on SAP Service Marketplace: http://service.sap.com/erp-instGo to SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP enhancement package 5 for SAP ERP 6.0

Download your EHP Installer tool provided on SAP Service Marketplace: http://service.sap.com Go to Support Packages and Patches Additional Components Upgrade Tools SAP EHP INSTALLER 7.00

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

“Download” directory for SAP enhancement packages and SAP Support Packages of app. 10-30 GB *Shadow instance of app. 100 GB *Additional space for existing tablespaces (depends on available free space in each tablespace)

Auto extend setting for tablespaces recommended

* temporary space

1. Solution Manager Preparation

Make sure you have an Up-to-date Solution Manager system (patches), more information: SAP note 1165438 (SAP Enhancement Package 4 for SAP ERP 6.0), SAP note 1324838 (SAP Enhancement Package 5 for SAP ERP 6.0)

In general: review the set up of your SAP Solution Manager system and system landscape (transaction SMSY), SAP note 1022072 gives for further information (e.g. product version of your system has to be = SAP ERP 6.0 NOT SAP ECC 6.0)

Get familiar with the Maintenance Optimizer

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

Further help: Implement SAP note 1233954 (No XML in EPS Inbox), SAP note 1134872 (FAQ for Stack Delta Files in EPS), SAP note 1122966 (Maintenance Optimizer for EHP), SAP note 1090202 (MOPZ: adjust stack delta XML), SAP note 1165587 (MOPZ: EHP stack selection)

2. Get familiar with SAPehpi

Download & study SAPehpi guide provided on SAP Service Marketplace: http://service.sap.com/ehp-inst Go to EHP5 --> "Enhancement Package Installation on Existing SAP Systems”

Download your SAPehpi provided on SAP Service Marketplace: http://service.sap.com Go to Support Packages and Patches Additional Components Upgrade Tools SAP EHP INSTALLER

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

http://service.sap.com/


© SAP 2010

Correctness of landscape data is the key for a successful EHP installation:A correct landscape configuration is a major prerequisite for error-free execution of MOpzErroneous or incomplete landscape information can result in failure of the update procedureGuidance towards correctly entering all information needed in the update process is required

New: Landscape Verification 1.0 for SAP Solution Manager

Using landscape verification 1.0 for SAP Solution Manager helps to improve landscape data quality as a major prerequisite for smooth installation of SAP enhancement packages for SAP Business Suite.

New Solution: landscape verification 1.0 for SAP Solution Manager

Helps to analyze system landscape data in SAP Solution Manager System Landscape (SMSY) in order to identify issues in landscape description Add-on installation - details can be found hereLandscape verification promotes the “landscape pattern” concept: Hub and sidecar - details can be found here


Relation between Technical Usages, Business Functions and SWCVs: SAP Note 1324838

Business functionsTechnical usageProduct instancesBusiness packages (content)

BF-TU_mapping_EHP_2-5_f_ERP_6_V5.pdf

Technical usagesBusiness functionsProduct instancesBusiness Packages

TU-BF_mapping_EHP_2-5_f_ERP_6_V5.pdf

ABAP-based product instancesABAP-based EHP5 software component versions

Java-based product instancesJava-based EHP5 software component versions

EHP5_instance_swcv_mapping_v5.pdf

SAP Note 1324838 – SAP Enhancement Package 5 for SAP ERP 6.0: Required SWCcontains the following attachments:

The corresponding SAP note for SAP Enhancement Package 4 for SAP ERP 6.0 is: 1165438


Two Alternative Installation Approaches (For SAP ECC Server)

Selective InstallationCustomer’s IT Strategy for SAP enhancement package installations:

• Change (install) only what is needed for activating a business function that the business decided to use. • Use synergy effects with your maintenance cycles to avoid a separate regression test.

Proceeding: Install exactly those technical usages that are needed to activate the business functions that are in scope for your project.

Advantages: Minimize risk for this implementation project

• Less potential adjustment efforts as less software components are touched

Default approach

Customer’s IT Strategy for SAP enhancement package installations:• Proactively add relvant scope of new functions to be in best shape to activate

further business functions as soon as these are requested by the business.• Use synergy effects with your maintenance cycles to avoid a separate regression test.

Proceeding for SAP ECC: Flat installation approach Look at the technical usages offered and exclude the ones that you do not use on this system. For the remaining technical usages, check if the enhancements inside potentially add value for youIf yes, install these technical usages.

Advantages: Minimize initial effort for analyzing new functions

• In best shape for new implementations.

‘Broad’ Installation

TechnicalInstallation

Which T echnical Usages should I include for the S AP E C C S erver? T he business experts can‘t tell which

B usiness F unction(s) they want to use later on..

Evaluate content of SAP enhancement packages in advance (service.sap.com/erp-ehp) and select required functionality

Apply required SAP Support Package Stack and include all required parts (technical usages) of the SAP enhancement package

This is the recommended approach by SAP as it minimizes the implementation effort

Ongoing innovation as part of maintenance strategy: Install all relevant software components together with SAP Support Packages

Demand driven Innovation: Activate Business Function when required

Main disadvantage: All Installed SAP enhancement package components have to be updated with every future SAP enhancement package installation. Potentially additional adjustment effort and downtime must be considered.

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


© SAP 2010

Installation Procedure At A Glance

Selective InstallationBroad Installation

1. Choose business functions, e.g.: ‘Retail Buying’

Queue of installablepackages + stack xml

6. Regression Test

1+2. Choose relevant Technical Usage(s) with potential business value for your company.

EHP5 SAP Note: 1324838

2. Map business function(s) to Technical Usage(s)

Now defined: technical usage(s)

Business

Build &TestD

esign

5. Modification Adjustment

4. Install installation packages using SAPehpi

3. Select technical usage(s) using Solution Manager Maintenance Optimizer. Automated calculation and download of required installation files


1. S elec t the required C ore F unc tionality:T ec hnic al Us ag e(s ) C entral Applications Human C apital Management

3. P lus optionally s elec t one indus try related Tec hnic al Us ag e(s ):T ec hnic al Us ag e(s ) Discrete Ind. & Mill P roducts O il&G as Hospital P ublic S ector Accounting

C atch Weight Management Insurance Media Utilities/Waste&R ecycl./T elco

O il&G as with Utilities R etail Defense Defense F orces & P ublic S ec.

F inancials - C ontr. Acc. & L easing

2. P lus optionally s elec t the extended func tionality:T ec hnic al Us ag e(s ) E -R ecruiting on E C C S erver HC M - L earning S olution G lobal T rade F inancial S upply C hain Mgmt

E S A E C C -S E P L M C ore F inancial S ervices

Broad Approach: Choose Technical Usage(s)

Remember: What you see here are not software components, but ‘Technical Usages’ (=valid subsets of compatible software component versions). You cannot decide per software components which ones you update to the next EHP level.

Proceeding using the ‘broad installation approach’: 1. Exclude all technical usages that reflect topics that you do not use in your system.2. For the remaining technical usages, briefly verify if these include interesting capabilities for your end-users. To find out which

Business Functions are part of a Technical Usage read SAP note 1324838 – there you will find the respective mapping.3. Check if any add-on’s are installed and if these are released for the respective SAP enhancement package.4. For those technical usages that fulfill this prerequisite, install them along with SAP Support Package stack. 5. For customers with an activate industry business function set: The corresponding industry component must be included into

the SAP enhancement package installation.


© SAP 2010

Build and Test

Further ServicesExpert Guided Implementation

- Update to Solution Manager EHP1 including basic configuration

Result:Getting the solution ready and tested

System Administrator

Software Installation And Activation

Installation of SAP enhancement package with SAP enhancement package installer (SAPehpi)

Activation of Business Functions using the Switch Framework

Regression and Acceptance Testing

SAP delivers SAP enhancement package test case templates

SAP Solution Manager enables risk based testing (BPCA)

First of all the business expert has to select the required business functions.

The Enhancement Package Information Center is the single point of access to all information related to a business function for the business expert.

Here you can find presentations, documentation, release notes, test catalogues and learning maps. The Business Function documentation allows the user to get to know the capabilities behind a business function and how to use them; learn about options the business function provides; and notes which software components are needed. Please note that each Business Function has a technical name. This identifier is important to determine which parts of the system needs to be updated.


SAPehpi: Enhancement Package Installation




Agenda


Contents:Installation of parts of an SAP enhancement package with SAPehpi

SAPehpi: Enhancement Package Installation


© SAP 2010

How to install SAP Enhancement Package 5 for

SAP ERP 6.0

SAP Enhancement Package 5 for SAP


SAP Enhancement Package Installation

Guide

1

2

3

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


Reading Sequence Of Documentation about EHP Implementation Procedure


Overview about main Steps of SAP Enhancement Package Installation Procedure


SAPehpiSAPehpi

SAPehpiSAPehpi

Sample system landscape

ECCServer

SAP ERP 6.0

ABAP

SAP ERP 6.0

Java

Portal

ABAP + JAVA

MOpz


SLD

Stack.XML


Using the SAP Enhancement Package Installer (SAPehpi)

Get familiar with SAPehpiDownload & study SAP enhancement package installation guide provided on SAP Service Marketplace:http://service.sap.com/erp-instGo to SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP enhancement package 5 for SAP ERP 6.0

Download SAPehpi provided on SAP Service Marketplace: http://service.sap.com Go to Support Packages and Patches Additional Components Upgrade Tools SAP EHP INSTALLER 7.00

Prepare free space for…Installation directory “EHPI” of approx. 10-15 GB *Download directory for packages of approx. 10-30 GB *Shadow instance of approx. 100 GB (depends on customer situation)*Additional space for existing tablespaces (depends on available free space in each tablespace)

Auto extend setting for tablespaces recommended

* temporary space


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

Installation on an existing SAP ERP 6.0 system:ABAP: SAPehpiJava: SAPehpi*

Including into an upgrade to an SAP ERP 6.0 release:ABAP: SAPupJava: SAPJup

Installation of additional software component:ABAP: SAPehpi or SAINTJava: SAPehpi or JSPM

Installation of SAP Enhancement Package 4 or 5 for SAP ERP 6.0: Tool Matrix

SAP Enhancement Package 5 for SAP ERP 6.0 comes with SAP Enhancement Package 2 for SAP NetWeaver 7.0

SAP Enhancement Package 4 for SAP ERP 6.0 comes with SAP Enhancement Package 1 for SAP NetWeaver 7.0

Some SAP systems based on SAP Enhancement Package 4 or 5 for SAP ERP 6.0 can also be combined with other versions of SAP NetWeaver


The web page now offers you to:

Starting the SAPehpi Front End

Read the manual on the Service Marketplace

Start the SAPehpi GUI

Read the SAPehpi documentation

Java EE SAP Enhancement Package installation evaluation

To start SAPehpi:Download the SAPehpi package from SAP Service Marketplace and extract it

Start STARTUP.BAT from the EHPI directory

Via browser connect to the SAPehpi port 4239

Note that SAPehpi installation directory path must not be longer than 45 characters.

SAPehpi has to be executed by user <SID>adm

Before you start, please remove any old and outdated profile files from the profile directory (even if they are renamed).


PreparationAll objects, parameters and passwords are providedShadow system (ABAP) is createdSystem prerequisites are checked and can be adjusted if necessaryHint: Therefore its recommended to run this block as soon as possible. All steps can be repeated if necessary.

UptimePoint of no-return is reached

DowntimeSAP system is switched (ABAP)Deployment is executed with JSPM (JAVA)SAPehpi finalizesManual steps

SAP Enhancement Package Installation Using SAPehpi – the Main Blocks

Uptime DowntimePreparation (no ‘real’ changes)


System analysis:Step completedAS ABAP identified

SAPehpi: Monitor

Note, that in systems based on AS ABAP and AS Java, both stacks will be updated synchronously – you will see tabs “ABAP” and “J2EE” next to the “Monitor”.


Performance parameters:

In the configuration phase you are prompted to select one of four performance models.

Your choice influences the number of parallel processes that will work during the installation.

It is always recommended to go for the “Manual selection of parameters”since that way you can best adapt the number of processes to your specific system.

SAPehpi: Configuration

For additional information, please refer to Troubleshooting and Administration Guide


SAPehpi: Add-Ons

How to deal with Add-OnsDuring the installation of SAP Enhancement Package 5 for SAP ERP 6.0 you will be asked how to deal with Add-ons. You have several possibilities, depending on the specific Add-on.

Not all Add-Ons are released for SAP Enhancement Package 5 for SAP ERP 6.0, check SAP note 1318299 for details.


SAPehpi: Stack XML File

Retrieving the stack from SAP Solution Manager by RFC

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

SAPehpi can get that file automatically by an RFC call.

If you cannot get this to work, then log in to the target system and check table BCOS_CUST via transaction SM30 and make sure that you see the name of the RFC connection to SAP Solution Manager.


SAPehpi: SAP Support Packages

Including the latest SAP Support Packages into the installation

Especially SAP_HR and EA-HR Support Packages are released more often than a complete SAP enhancement package Support Package stack.

You can manually download and then include those SAP Support Packages. In phase BIND_PATCH you are prompted if you want to add further SAP Support Packages to the target release.

Provide those SAP Support Packages in the download directory right from the beginning of SAPehpi or extract the SAP Support Packages to the EPS/in directory.


SAPehpi: Troubleshooting Guide

SAPehpi Troubleshooting Guide

You can find more information about SAPehpi troubleshooting in the SAPehpi Troubleshooting Guide.

See http://service.sap.com/instguides SAP Business Suite Applications SAP ERP SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP enhancement package 5 for SAP ERP 6.0 SAP enhancement package installer (SAPehpi) guide

You can find the Troubleshooting Guide at the bottom of the page.


© SAP 2010

Get Started - Enhancement Package Infocenter: http://service.sap.com/erp-ehp

Master Guide&

How to Install SAP Enhancement Package 5 for

SAP ERP 6.0: A Practical Guide

SAP Enhancement Packages -Frequently Asked Questions

Lifecycle of SAP Enhancement Packages

SAP enhancement packages Technology Facts

SAP Enhancement Package strategy for SAP ERP

ERP@BPX: EHP Forum & Wiki

SAP EHP Info CenterEnhancement Package

Info Center



SAPehpi: Technical Phases




Agenda


Contents:Overview of the major steps of the SAP enhancement package installationMost important phases of the SAP enhancement package installation

Technical Phases


The five major Technical Steps

SAP Notes: post Installation stepsInstallation Guide: post Installation stepsASU Toolbox: post Installation steps

1

2

3

4

5

Needed Technical Usages of SAP Enhancement Package 5 for SAP ERP 6.0 and corresponding SAP Support Packages

See Installation Guide

SAP Note 1000009

Roadmap steps 1 - 4

Roadmap steps 5 - 8

See Installation Guide

SAP Note 1000009

Solution Manager: select target ‘release’

SAP Notes: pre Installation stepsInstallation Guide: pre Installation stepsASU Toolbox: pre Installation steps

SAPehpi: preparational stepsSAPehpi: resolving negative checks

SAPehpi: Installation

The technical installation procedure can be described with these five major steps.


Installation Tools with SAP NetWeaver AS 7.02

SAP Software Delivery Tool (SDL)

InstallationMonitor

Main Upgrade tool, that helps preparing the Upgrade by checking for problems and configuring the software components for the upgrade and performs the actual upgrade

Tool, that simplifies handling of the installation by providing a multi-functional user interface

Tool from Installation Front-end, that shows the progress of the currentroadmap step

3

4

SAPehpi Installation Controller

SAPehpi front end

The SAPehpi is the main Installation tool.

The SAPehpi front end is a graphic-based tool.

The installation monitor is a feature of the SAPehpi front end.


Central instance host

Installation Tools: SAPehpi Front-end

Remote client hostSAPehpi SAPehpi controller

Port 4240

Port 4239HTTP

Port 4241


SAPehpi Controller and SAPehpi Front-end

directly starts

connect

Start the UA server

Only on the central instance host

Command from the Upgrade Master DVD: <DVD drive>:\ STARTUP.BAT "upgdir=<upgrade directory>" "jce_policy_zip=<path to JCE policy archive>"

If you would like the upgrade GUI to start automatically, use the following parameter: STARTUP.BAT "guistart=on"

Choose a password when starting for the first time

Start the SAPehpi front end on a client host with network access to the central instance host

In the Web Browser call the URL: http://<central-instance-host>:4239

The client GUI starts after the download of the client application code is complete.


SAPehpi Front-end

You can log on to the Upgrade Front-end with different roles.

Administrator:

Power user gets full functionality of Upgrade Assistant

Use the password you have chosen

This user can be logged in once

If the administrator logs on, another active administrator will be switched to user observer

Observer:

This user can only monitor the upgrade

Use the password you have chosen

This user can be logged on several times

An observer can take over the administrator role when applying the administrator password


SAPehpi Front-end: Input Window

Download directory

It is possible to provide a central download directory for all patches and files that should be bound to the installation


SAPehpi Front-end: Monitor

Informs the administrator about

Progress of current roadmap step

Status of current phase


SAPehpi Front-end: Handling


Resource Consumption of the Installation Process

Downtime minimized

Resource minimized

Not available with SAPehpi: 'Low recourse use' triggers 'Resource minimized’


Installation Process Overview

DB and SAPehpi directorymust be restorable to state at end of production!

ECC

6.0

ECC

6.0

5

Shadow system running

Standard resource use, archiving off

High resource use, archiving off

High resource use, archiving on

Downtime

Downtime

Downtime

Bac

kup

Downtime behavior with standard, high and low resource use.

'Standard and High Resource Use' refers to the 'Downtime minimized' strategy

Not available for SAPehpi: 'Low Resource Use' refers to the 'Resource minimized' strategy


Shadow system running

Standard resource use, archiving off

High resource use, archiving off

High resource use, archiving on

Downtime

Downtime

Downtime

Bac

kup

Important Phases of the Installation

RU

N_R

SD

BSC

PY

Tran

sact

ion

SPD

D

AC

T_U

PG

PAR

DIS

T_S

HD

MO

DP

RO

F_TR

AN

S

EU

_SW

ITC

H

PAR

CO

NV

_UP

G

PM

VN

TAB

_UP

G

TABI

M*

XPR

AS

*

SH

AD

OW

_IM

PO

RT*

Man

ual a

ctio

ns

App

ly S

AP

note

s

Tran

sact

ion

ICN

V

PR

D: d

elta

tran

spor

ts

RUN_RSDBSCPY* Clones tables from original to the shadow system

ACT_UPG Activates all ABAP dictionary objects, that are not delivered activated

PARDIST_SHD Starts distributor

SHADOW_IMPORT* Imports SAP enhancement package objects, also imports upgrade and language data into the new tables, imports included Add-on and SAP Support Packages into the shadow tables and the new tables

MODPROF_TRANS Stops SAP system and changes profiles

EU_SWITCH Switches to new Repository

PARCONV_UPG Converts application tables and activates their nametab entries

PMVNTAB_UPG Converts application views and activates remaining nametab entries

TABIM_UPG Import of additional transport requests

XPRAS* Executes XPRAs


Status at Phase ACT_UPG / SPDD

Application datacustomizing datauser master data

Application datacustomizing datauser master data

Add. application dataadd customizing data(imported after ACT)

Add. application dataadd customizing data(imported after ACT)

SAP

R3

SAP

R3S

HD

Repository

7.00/6.00

Repository

7.00/6.00Shadow repository

7.02/6.05

Shadow repository

7.02/6.05

Repository

7.02

Repository

7.02

Productive instance7.00

Shadow instance7.02

Productive instance7.00

Productive system 7.00/6.00

Shadow repository 7.02/6.05

Shadow system7.02

Accesses

...

DB

(Application data)customizing datauser master data

(Application data)customizing datauser master data


Phase START_SHDI_FIRSTStart shadow instance for the first time

Batch jobs on shadow instanceVersioning preparations

SPDDModification adjustments on shadow instance

Activation: Phase ACT_UPGParallel activation on shadow instance

Distribution: Phase PARDIST_SHDParallel distribution on shadow instance

Phase STOP_SHDI_LASTStop shadow instance finally

Steps Performed on Shadow System

production

shadow

The shadow instance is used for SPDD, batch monitoring, troubleshooting during shadow phases

DDIC user

Password copied from productive instance

Create additional users with transaction SU01

No access to application tables

Only basis tables accessible

No customizing

No production operation

No tp import to shadow instance

No tp mvntabs, no DDL statements

No online activation and conversion

Only “inactive“ activation in SE11

No operations in SE14

Access to target release repository during production operation on source release


Connect to shadow system:

Danger

R3load, R3trans and tp need additional environment settings

to connect to shadow system correctly.

Manual calls of R3load or tp with wrong environment

will damage the system! Calling SAPehpi with this setting could damage the system!

D A N G E R !


Update of Components 7.02

Industry Extensions

Enterprise Extensions

In this example enterprise extension EA-HR is updated to 6.05, industry extension IS-UT is not updated, so it is not displayed on this screen.


BIND_PATCH: Selection

Selected in ADM327

Minimum SAP Support Package Level (min)

Required for the given Add-On selection

Available only after successful Add-On queue calculation (phase ADDON_QCALC)

Set to <unknown> if Add-On queue calculation not successful

A Support Package selection that does not meet the minimum package levels leads to an error.

Equivalent SAP Support Package Level (equi)

Package level that is equivalent to the level for the source release

<unknown> if equivalent level could not be determined

To avoid loss of data we strongly recommend that you include enough SAP Support Packages to reach the equivalent level.

An SAP Support Package selection that does not meet the equivalent package levels leads to a warning.

Current Package Level (current) is the maximum package level that

Is delivered with the installation (service release level, for example ECC 5.0 SR1)

Has already been selected (and confirmed) by the customer

Is already installed in the customer system, if the release of the component does not change with the installation (only relevant for component upgrades)


Changing the SAP Standard

DevelopmentOwn applications

Customizing

Development Enhancements

SAP Standard

Mod.Adv. Corr.

CustomizingSetting of business parameters(obligatory or optional)

Adv. CorrectionsSW changes in regard to a later upgrade

ModificationsChanges to the SAP software

EnhancementsUse of existing user exits or BAdIs for software enhancements

There are five types of SAP system changes:

Customizing: Involves setting system business parameters using special Customizing transactions. Changes are scheduled and organized in advance. Customizing is mandatory before using the SAP system in a live environment. Do not confuse with technical parameters from transaction RZ10!

Customer developments: Creation of customer-specific objects according to naming conventions.

Enhancements: Customer changes to SAP Repository objects without the need for modifications.

Modification: Customer-specific changes to SAP Repository objects. When SAP objects are changed, the customer version has to be modified to match the new SAP version.

Advanced correction: Apply bug fixes from SAP directly to the SAP system.


Modification: Yes or No?

Modifications that need adjustmentManually implemented advanced correction in accordance with a SAP NoteAdjustments of customer beyond Customizing (Repair)Customer transports (<SID>K9*)

No modifications Advanced correction with SAP transport (<SID>K0*)will probably be part of the new releaseSAP Support Packageswill be part of the new release or an SAP Support Packages of the new releaseAdd-onswill be part of the new release (Extension Set) or need an upgrade DVD


Update System Landscape

system active

system active

system down

Switch

Production

SPDD

SPAUSPAU_ENH

Import

bin/umodauto.lstdata/R...cofiles/K..buffer/SAP

Integration of thecreated transportrequests intothe installation

Switch

Production

SPDD

SPAUSPAU_ENH

Import

TransportDirectory

DEV QAS, PRD

The start of the upgrade process involves the transfer of new data to the system from the shipped DVDs. SAP Repository objects are imported into the system and the customer objects are compared. All ABAP Dictionary objects that have been modified by customers must be compared to the new SAP standard during this upgrade process.

To avoid loss of data and table fields that customers may have created, conflicting structures must be merged before the mass activation of ABAP Dictionary objects in the upgrade process.

If objects need to be adjusted, use the transactions SPDD and SPAU/SPAU_ENH. All modifications made by customers are then merged with the new SAP object versions to retain data; otherwise, the new SAP version will be activated and data may be lost.

Upgrades to >= 6.10: The system is available during the activation phase. The activation takes place on the shadow instance.

When the upgrade is completed, the SAP system is successfully running at the new release level. Customer-developed objects and modifications have been preserved.


Preparation Aspects

Withoutadjustment,

modificationsare lost

Preliminarycorrections

are lost

SPAU/SPAU_ENH objects:

Adjusted at theend of

installation

SPAU/SPAU_ENH14 Dayswithout

key check

SPDD: No transportinto system

manuallySPDD:Do notactivateobjects

SPDDmodification

adjustment onshadowinstance

SPDD/SPAU

Do not attempt to import adjustment transport requests into the system manually during SPDD. This can leads to a loss of data in customer fields.

Do not activate any objects. Activation is carried out automatically after the adjustment.

If errors are reported when you activate your own developments after executing this phase, you can correct these here, since SAPup stops when errors occur. However, you also have the option of choosing Ignore to temporarily ignore these errors. You do not need a password to do this. If you chose Ignore here, you must activate these objects after the upgrade.

After you have completed the upgrade, you have a maximum of 14 days to execute transaction SPAU/SPAU_ENH without a key check (SAP Software Change Registration) for the objects that you changed.

For further information, see the Component Upgrade Guide and online application help for SPDD and SPAU/SPAU_ENH.


Transaction SPDD

Domains

Data elements

Tables

Transaction SPAU

Different modifiedobjects requiredifferent transactionsfor modificationadjustment

For most ABAP Dictionary objects

For all other Repository objects

Modification Adjustment Transactions

Reports

Menus

Screens

Views

Lock objects

If you do not use SPDD where necessary, you risk data loss

Transaction SPDD is used to perform modification adjustments to certain ABAP Dictionary objects such as domains, data elements, table structures, transparent tables, pooled tables, cluster tables, and table technical settings. Not performing modification adjustment for these objects would cause data loss.

After activating the new Repository, transaction SPAU/SPAU_ENH is used to perform modification adjustment for objects for which not performing modification adjustment would NOT directly lead to data loss. These objects include:

Some ABAP Dictionary objects (lock objects, views, and so on)

All other Repository objects (such as module pools, ABAP programs, function modules, menus, and screens)

After running transactions SPDD and SPAU/SPAU_ENH, all modifications are incorporated into the new SAP release

The preparation phases check which modified objects need adjustment to enable you to better plan the time required for modification adjustment.


Takes place after modificationadjustment with SPDDFully integratedinto installation process

Easy handling

Incremental Table Conversion (ICNV)

Large tables are nowconverted during uptime During downtime only switchto new structure necessaryCan handle modified tables

Exclusion timesProgress prediction

Configurableconversion process

ICNV

Reduction ofinstallation downtime

With each new release, the structure of the tables in your database changes. These table conversions used previously only occurred during the installation downtime (for example, phase PARCONV). By using incremental conversion, you can convert many of these data records before the installation downtime.

Advantages of ICNV:

Reduced downtime during the installation, because a large number of tables will be converted during uptime.

You can return to the SAP standard more easily for modified tables.

You can use incremental conversion especially for large tables.

Incremental table conversion is performed using transaction ICNV. You can use the following functions:

Display the tables determined by SAPehpi (tables for conversion with ICNV)

Choose which tables you want to convert incrementally.

Start the conversion.

Monitor the conversion.

Estimate the runtime of the conversion.

You can define the time during which ICNV should not be executed (for performance reasons).

ICNV gives you information about the progress prediction


Transaction ICNV: Selection of Candidates

Selection of conversion candidates:

Modified tables that will be converted are includedTables can be excluded from ICNV even at this point (for example: a hot spot with frequent updates / deletes)

RU

N_R

SD

BSC

PY

Tran

sact

ion

SPD

D

AC

T_U

PG

PAR

DIS

T_S

HD

MO

DP

RO

F_TR

AN

S

EU

_SW

ITC

H

PAR

CO

NV

_UP

G

PM

VN

TAB

_UP

G

TABI

M*

XPR

AS

*

SH

AD

OW

_IM

PO

RT*

Tran

sact

ion

ICN

V

Man

ual a

ctio

ns

PR

D: d

elta

tran

spor

ts

App

ly S

AP

note

s

By calling transaction ICNV, all potential candidates are displayed with their current selection status. You can decide which of the pre-selected tables should be processed by ICNV.

Tables can be excluded from being processed by ICNV with 'Do not perform ICNV'. This should be used for tables with a high number of updates and / or deletes, because in this case the ICNV can be inefficient. The delete operations are especially critical. The load on the database is doubled by performing a delete on a table processed by ICNV.

This efficiency check must be done manually. There is no tool that excludes “hot spot tables” automatically!


Transaction ICNV: ICNV Assistant

ICNV configuration:Number of background jobsSelection of background hostsExclusion times

ICNV assistant:InitializationStart of data conversion

Monitor progress:Computation ofconversion statisticsEstimation of time to finishStatus display

Transition to new repository structure is done by SAPehpi

ICNV offers several features to configure the incremental conversion process

Batch hosts can be specified

The number of running batch processes is adjustable

Exclusion times for processing can be specified for each table (This enables you to run conversion job at times with relatively low table I/0).

The log files of the conversion processes for each table can be accessed

See online documentation in ICNV

After deciding about all tables, the user can choose to be guided through the necessary steps by an ICNV Assistant. For the installation scenario, there are two steps needed to be started manually:

Initialization

- Extension by flag field

- Build of an index on the flag field

- Creation of update and delete triggers

- Replacement of table by a view and renaming table

Start of the data transfer

The remaining steps (switch and delete entry in ICNV) are then performed by SAPehpi!


ASU Toolbox – Management Tool for Manual Pre-Installation and Follow-up Activities

Guidance for manual steps

Benefit: Reduction of runtime and downtime

Delivered with ST-PI

Must be started manually

Preparation phase: REQ_PRE_ASU_RUN

Downtime phase: REQ_POST_ASU_RUN

See SAP Note 1000009


Transaction SGEN

Can now be started by SAPehpi during the installation phases

Works in parallelstarting with upgrades to AS ABAP 6.20,improvements with ECC 6.0 SR3 upgrade

Generates programs, business server page applications,function groups

Load Generation (SGEN)

With SAP R/3 4.6, report RDDGENLD is replaced by transaction SGEN.

With AS ABAP 6.20, SGEN generates loads in parallel. In addition to programs, SGEN can now generate business server page applications, function groups, and so on.

The most important ABAP loads for the Basis system are upgraded with the new release. However, there are not yet any generated ABAP loads for all of the transactions from the different SAP application areas. When you call a program, a load is automatically generated if it does not already exist. This may, however, reduce production system performance. To avoid this, you can use transaction SGEN to generate the missing loads.

Recommendation: If possible, generate the loads directly after the upgrade. New with basis 7.01 upgrades: SGEN can be started by the upgrade during the upgrade downtime phases.

For a detailed description of the features, see the online documentation in transaction SGEN by choosing Information on the SAP Load Generator, or in the Job Monitor by choosing Job Monitor.

For more information on the free space requirements in the load tables, see SAP Note 186066.


Downtime




© SAP 2009

Agenda


Contents:What is downtime?What causes the downtime during an SAP enhancement package installation?How can downtime be reduced?Outlook: Near Zero Downtime Upgrade

Downtime

© SAP 2009


What is Business Downtime?

Productionoperation

DowntimeSAP system is not available for end users

High availability is the requirement to maximize system availability from an end-users point of view.

“

Uptime: end users can use the system’s applications in production

Business downtime is the duration, in which an end user cannot use the systems applications in production.

Why downtime?

The big advantage of SAP‘s installation technology is, that we allow our customers to adapt, extend and modify SAP software, and these extensions will be kept and adjusted to the new release during the installation process. Most of the required processing steps can be performed during system uptime.

Downtime is necessary, whenever live running transactions have to be replaced by new functionality, and a potential risk of data inconsistency is given, i.e. changing the processing logic, or changing the data model/structure.


Causes for Downtimes and Measures

Having a highly available technical infrastructure in place is crucial in order to reduce 'unplanned downtimes'From a technical infrastructure point of view, the architectural and technical single point of failures (SPOF) need to be identified and secured in an appropriate manner.

“Human errors” (= 80% of downtime causes) to be addressed by ease of system management and with improved change and problem management processes

not solvable by automatic switchover!!

Unplanned downtime Planned downtime System/system landscape & infrastructure maintenance

Patches, release upgrades, Deployment / transportsConfiguration changes...

Improved/optimized Upgrade and patch processesProven software lifecycle management and propagation engines (i.e. enhanced CTS)To be avoided with scalable components which enable rolling maintenance

Hardware/OS failuresOther disasters Application failuresOperating / handling errorsUnintentional data deletion…

Application failures

40%

Operator errors40%

HW, OS failures, disasters

20%

Source: Gartner Group

Main causes for unplanned downtime


Planned Downtime - Availability Impact

High frequency

Long duration

Minutes

Lowfrequency

Short duration

0,5 … 2 hours 10…15 hours

Weekly

Monthly

Quarterly

Yearly

Offline backups with split-mirror

Kernelpatches

Profile parameter changes

Offline backups

without split-mirror

Transports

SAP Support

Packages

End of daylight

saving time

Release upgrades

Database reorganizations

OS/DB migration / Unicode

conversions

20…48 hours

SingleEvent

SAP enhancement

package

Overall guideline:

Avoid frequent downtime with long downtime period.

Frequent events need to be minimized regarding the downtime

Offline backups need to be avoided

Database reorganizations should be a rare occurrence


Downtime Costs versus Availability Costs

C

ost

95% 98% 99,5% 99,9%

Availability

Availability cost curve (Source: Gartner Group)

Costs

downtime

co

sts

Downtime costs are usually not linear over the time of system outageThey depend on the business impactFor longer downtimes costs can increase progressivelyExample: when SCM processes are stuck longer than 3 hours the whole production will be stuck and cause even higher costs

Redundant components Disaster recovery siteSystem management toolsIT staffCapacity planningGuaranteed SLAProactive services


© SAP 2010

cv

SAPehpi – Timing Diagram

Extraction Configuration Checks Preprocessing DowntimePost-

processingFinali-zation

Uptime UptimeBusiness downtime

Initialization

!

Shadow build - up

Overall installation runtime (median: 44 hours)

Majority of user interactions (~1 day)

Installation Preparation Steps

Dep

loy

(AS

Java

)

Rep

osito

ry

switc

h (A

S A

BA

P)

Prep

are

dow

ntim

eB

acku

p

‘Pos

t‘ac

tiviti

es

Verif

y &

test

sys

te,

Bac

kup

Point of no return

7 81 2 3 4 5

Development close

6

The SAP enhancement package Installer uses a system cloning and switch procedure. This procedure installs a copy of the SAP system, the shadow system, in parallel to the original SAP system. The shadow system is used to

update the affected software components and to install the additional components, while the original SAP system is still in production operation.

For further information please read the SAPehpi documentation.


What are the elements of production downtime?Installation technical runtime (SAPehpi) – most of this is not production downtime!Post-installation transports & manual adjustmentsBusiness validation & acceptance testingPossibly pre- and post-installation system backupsBusiness ramp-down & ramp-up

Production Downtime During Installation

up

down

up

down

SAPehpi:prepare & repository

import

ramp-down

SAPehpi: conversion, XPRAS, etc.

Basis

ramp-up

backup?

Functional/ business Operations

go/no-go decisionbackup?

transports & manual tasks

Business validation

tests

Begin and end of downtime is not only a 'click' but could be a complex process: for example stopping the production line with all its implications.

Both could take hours of time. So this should be called 'ramp down' and 'ramp up' instead of just 'stop' and 'start'.


Potential to Reduce Downtime

down

ramp-down

up

down

upSAPehpi:prepare & repository

import


ramp-up

backup?

go/no-go decision

backup?

up

down

upSAPehpi:Prepare & repository

import


ramp-up

backup?go/no-go decision

down

before

after

Basis

Functional/ business

Operations

Transports & manual tasks

Business validation

tests

1 2

The highest potential lays in:

Speeding up the delta transports and manual tasks

Speeding up business validation test (for example using tools like eCATT)


Influencing Factors for Runtime & DowntimeD

ownt

ime Type & performance of

the storage(I/O throughput)Number and type of CPU´s for the application & DB server

Start & target ReleaseVersion of SAPehpiProductive applications/ Add-Ons or industry solutions

SAPehpi parameterization (e.g. number of processes)Number of clients

Usage of Incremental Conversion (ICNV)

Run

time

Type & performance of the storageNumber and type of CPU´s for the application & DB server

Start & target releaseNumber of included SAP Support PackagesNumber of modifications on standard SAP objectsVersion of SAPehpiProductive applications/ Add-Ons or industry solutions

SAPehpi parameterization (e.g. number of processes)Number of installed languages

Usage of Incremental Conversion (ICNV)

Hardware Software Configuration Strategy1 2 3 4

Each system is highly individual regarding it‘s configuration and application data runtime/downtime forecasts are only possible when analyzing results of a test installation with production data !

“

Installation runtime: Total duration of the installation controlled by SAPehpi including preparation and uptime activities.

Runtime and downtime depend on:

Hardware and operating system: The whole installation runtime depends on the hardware and operating system you use.

Hard disk configuration: Input/output throughput, backup speed

Database: Size of tables, database configuration, parameter tuning

Number of modifications: SPDD and activation time

Number of data structure conversions: Phase PARCONV; depends on start/target releases; bigger leaps mean more data conversions

Productive applications: More productive applications mean more data conversions

Number of clients: Client cascade in phase TABIMP

Number of installed languages: More data import

A test installation on a production system mirror (sandbox system installation) and thorough analysis of the installation log files can highlight many possibilities for effective manual tuning activities early in the project.


© SAP 2008

Transaction ICNV: Reduction of Installation Downtime

Reduction of installation downtimeLarge tables are now converted during uptime Only switch to new structure during downtime(in PARCONV)

Easy handlingFully integrated into upgrade process

Configurable conversion processExclusion timesProgress prediction

Because most data is converted before the beginning of downtime, downtime can be reduced by several hours. The actual reduction depends on the table size. The dependence of downtime on the database size is also strongly reduced. The downtime can be predicted more accurately.

Conversion of large tables during system uptime

Conversion process can be stopped and restarted

Possible error situations during uptime

ICNV especially suited for WORM tables

ICNV is fully integrated into the installation

Tables to be processed by ICNV can be selected

Conversion process is configurable

Additional resource usage of DBMS

Sufficient number of background work processes

Execute ICNV as early as possible


© SAP 2008

Description

Example Management tool for application specific manual preparation and follow-up task such as

Restoring of certain user specific settings Manual transactions or correction reports to be started after upgradeReports needing manual input by usersSpecial data migrations

Integrated with SAPehpi and Solution ManagerDelivered via support tool plug-in ST-PIRefer to SAP Note 1000009

Benefits

More efficient preparation and execution of upgrade relevant application tasksLess manual efforts during upgradeHigher business stability after upgrade

Application-Specific Upgrade (ASU) Toolbox


Hardware I/O throughput of the storage / more and faster CPU‘s

Use new backup tools & strategy

Tools Use latest versionof SAPehpi

Use Incremental Conversion (ICNV) if possible

Service Downtime Optimization Service

Cutover Planning

Parallelize tasks

Improve backup strategy

Automate testing for GO decision

Downtime Tuning (in Addition to Standard)

1 Service is part of SAP's Premium Support (AGS)2 Gives guidance to reduce downtime

With these tuning methods the downtime can be reduced.


Scatter plot downtime vs. DB-Size

0

1020

30

40

5060

70

8090

100

0 100 200 300 400 500 600 700 800 900 1000

DB-Size/GBD

ownt

ime/

h

Source: Analysis of RSUPGSUM reports of SAP R/3 4.6C Upgrades

Database Size and Downtime

No direct relation between DB size and installation downtimeSome tables that undergo structural changes may have to be converted and therefore affect the downtime

Q: Does the total database size affect the installation downtime? A: No, only in special cases the size of single tables may have an effect on installation downtime.

Q: Why may some tables affect installation downtime? A: The following situations require downtime:

Structural changes of the table or index such as changed field length and altered index will lock the table and can only take place during downtime. The fewer records are contained in that table, the faster the operation can be performed.

Functional and design changes require an update of the table content.

Note: Besides reducing the table content, other technical tuning options such as parallelization of the index creation should be investigated because they may be easier to implement than archiving or deletion.

Q: Will new fields added to an existing table cause downtime? A: No, only in the case of these exceptions:

iSeries (AS/400): To change the table structure all records of the previous table have to be copied and transferred to the new table structure.

All DB systems: In some cases the new fields are initialized with a default value. This value has to be updated in every record of the table and will therefore require downtime.

Q: How to determine which tables may increase installation downtime? A: The most precise way is to do a test installation and evaluate the installation log, especially the parts: DDLs, conversions and XPRAs.


The requirements of the customersBusiness Downtime for a release upgrade is 2 - 4 hoursIn case of problems the procedure is completely resettableUpgrade procedure should be reusable for all SAP systems, initially R/3The procedures should also be applicable for SAP Support Packages

Near Zero Downtime Upgrade (NZDT)Summarized customers’ requirements

The method can be used for numerous downtime eventsUpgrade / SAP enhancement package installationUpgrade and Unicode ConversionUpgrade and OS/DB Migrations

… and alsoOS patchHW replacementDB reorg


Consistent system copy (clone) with the logging of database changesNormal Upgrade / Unicode conversionSynchronization of the changes between the main system and the copy – delta replayTransports, Pre-Validation while Uptime

Technologies for Near Zero Downtime

Delta replay

Recordingclone

downtime

Prepare + Upgrade Uptime

SAP Enhancement Package 5 for SAP ERP 6.0

+ Transports + Add Ons

+ Pre-Testing

Last Delta replay

Final-Validation

Infrastructure adjust. -interfaces

EHP installation downtime Post ProcessingDelta

TransferInfra

structure

hostA

Validation

PRDECC 6.02

hostB

PRDECC 6.02

hostA

PRDECC 6.05

hostB


Downtime

Delta replay

Recording

PRDERP 6.02

hostAclone

downtime

Prepare + Upgrade Uptime

Implement EhP 5

+ Transports + Add Ons+ Pre-Testing

Last Delta replay

Final-Validation

Infrastructure

adjust. -interfaces

EhP installation downtime Post Processing DeltaTransfer

Infrastructure

PRDERP 6.02

hostB

PRDERP 6.05

hostB

hostA

Validation

10 Steps to a Minimized Downtime

2

3

45

6

7 8

9

10

21

1. Users are working on PRD system2. Copy of PRD system & start recording of transaction data3. Data from production live transactions are recorded4. Implementation of the SAP enhancement package on the copy to 6.055. Finish SAP enhancement package implementation and replay transactions from PRD6. Users shutdown on production system and finish replaying transactions7. Start reconciliation source to target system8. Get signoff that both systems are reconciled9. GO decision10. Start up users on copy (new PRD)


Near Zero DowntimeArchitecture

Application dataApplication data

Z-Application data

Z-Application data

CustomizingCustomizing Z-Cust.Z-Cust.

System tablesSystem tables

RepositoryRepository

Application dataApplication data

Z-Application data

Z-Application data

CustomizingCustomizing Z-Cust.Z-Cust.

System tablesSystem tables

RepositoryRepository

Delta

freeze

Delta

ignore

ignore

freeze

Allo

w c

hang

es

Hot clone + SA

P enhancement package

Including Upgrade logic


Comparison of Business DowntimesStandard Method versus NZDT

up

down

SAPehpi:PREPARE &

repository import

ramp-down


Basis

backup?

transports & manual

tasks

business validation

tests

Functional/ business Operations

go/no-go decision

backup?

up

down

SAPehpi:PREPARE &

repository import SAPehpi: conversion, XPRAS, etc.

ramp-up

transports & manual

tasks

FinalDelta sync

Replicate Data

Standard EHP implementation with SAPehpi

NZDT Upgrade

freeze


© SAP 2010

Applicable forRelease upgradeSAP Support Package updatesCustomizing wavesDB maintenance – table reorganizationOS or DB patch

Near Zero Downtime for SAP ECC Minimizing Planned Downtimes

Near Zero Downtime method as a tool for minimizing downtimes

Number of executions

Effo

rt pe

r exe

cutio

n

Upgrade

DB reorg

SAP enhancement

package Support Packages DB reorg


Example: Installation of SAP ERP 6.0 EHP 3 SP1 (32 Packages) - Downtime Reduction in %

-18%

Restricted uptime downtime

SAINT: Standard SAP Support Package deployment:

SAINT: “Downtime Minimized” mode:

Restricted uptime downtime

SAPehpi:

-77%

uptime

SAPehpi starts

SAPehpi ends

Point of no- return

t

Point of no- return

Point of no- return

uptime

uptime -45 %

-55%

downtime

SAP Enhancement Package 2 for SAP ERP 6.0 was implementated with transaction SAINT. During the delivery of SAP Enhancement Package 3 for SAP ERP 6.0 the tool was switched from trasaction SAINT to the SAPehpi. The reason was: SAPehpi is able to implement an SAP enhancement package in much shorter downtime.

The installation of an SAP enhancement packages with SAPehpi is performed with minimized downtime. The point of no-return is reached significantly later in the installation process and not before checks have been run successfully by the tool. This means you get a smooth and safe implementation.

As you can see in the graphic the expected downtime is reduced by 77 %, further information will be published soon via the SAP enhancement package experience database.


Overview of Factors affecting SAPehpi Runtime & Downtime

As each system is highly individual regarding it‘s configuration and application data. A forecast of runtime and downtime is only possible when analyzing results of an SAP enhancement package installation test run with representative set of data!

Key take aways

SAPehpi uptime SAPehpi uptime Follow-up activities

Business uptime Business uptime Business downtime

Customer specificSystem

configuration

Number of selected

technical usages & SPs

Database utilization &

configuration

Number of modifications

Number of clients

Productive applications/

Add-Ons or industry solutions

Number of installed

languages

SAPehpi configuration

mode

Hardware / hard disc

configuration

Reaction time on dialog steps

Runtime / Downtime

depending on


Current StatisticsSAP Enhancement Package Installer

SAPehpi runtime

SAPehpi downtime

Median runtime: 44h Median downtime: 7,5h

* This statistic is based on the current evaluation forms referring to test and productive systems where an SAP Enhancement Package 4 for SAP ERP 6.0 installation was performed.

SAPehpi statistics for SAP Enhancement Package 4 for SAP ERP 6.0


© SAP 2010

1 Upgrades to SAP ECC 6.0 with source release SAP R/3 4.6C ; Source: Upgrade Experience Database2 SAP enhancement packages for SAP ERP 6.0; this number represents an extract only out of more than 5,900 enhancement package installations globally

(as of February 2010); Source: SAP Enhancement Package Experience Database;

0 12 24 36 48

Hours

Max: 48Min: 8 Median: 24

SAP enhancement

package2

installation(hours/overall)

n = 87

0 12 24 36 48 60 72 84 96 108

Hours

Max: 86,2Min: 22,9 Median: 48,0Upgrade1

(hours/overall)n = 140

Upgrade versus SAP Enhancement Packages Installation: Business Downtime


Planning and Preparation




Agenda


Contents:SAP enhancement package implementation as a projectImplementation in a three system landscapeUpgrade Dependency Analyser (UDA)Technical aspectsExperiences with SAP enhancement package implementations

Planning and Preparation


Unit 6: Overview Diagram

Lesson 3: Upgrade Dependency Analyzer

Lesson 4: Technical Aspects

Lesson 5: SAP Enhancement Package Implementations: Experiences

Lesson 6: Further Information

Unit 6 – Implementation Planning and Preparation

Lesson 1: SAP Enhancement Package Implementation as a Project

Lesson 2: Implementation in a Three System Landscape


Implementation Project: Key Questions

Key Questions

Will the implementation go live on time?

Will the solution still do what we designed it to?

How do we minimize thedisruption to business?

Have we identified allthe potential risks?

Will the system performat optimal levels?


Key Success Factors for any Implementation Project

Ensure a smooth system landscape transition

Plan your IT infrastructure

Manage parallel changes

Adapt applications

Ensure business continuity

Perform data operations

Minimize business downtime

Managing these focus topics is the key for a successful implementation project“

Based on SAP experiences in consulting, support and development seven key challenges have been identified that are relevant for any implementation project. If you manage to control them the project will succeed, if not serious issue will arise.



SAP CustomerSAP

End-to-endsolution operations

SAP Experts

Upgrade Roadmap

Test Workbench

E-learning mgmt. Change Management

SAP Service Marketplace


Maintenance Optimizer

Central tool for planning, executing, and managing the installation of enhancement packages, SAP Support Packages and patches across the entire SAP landscape

Monitors the complete maintenance procedure for your entire SAP solution.

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

SAP Solution Manager 7.01 SPS 23 or higher

Data maintenance with Solution Manager System Landscape (SMSY)


Upgrade only the enhancements applicableto your business



DESCRIPTION

ACCESS

BENEFITS


StrategyTechnical implementation vs. implementation with newfunctionality

New features and functionsNew features in existing transactionsNumber of new functionalities to implement

ModificationsNumber of modifications, which could be returned to SAP standard Number and complexity of modifications needed in the new release

DocumentationLevel and quality of documentation of business processes, custom programs, and modificationsDocumentation for testing

Planning a backup strategyDuring the technical installation After installation

Project Duration – Influencing Factors (1/2)


Executing of installationDevelopment, quality assurance, and productive systemsTraining systems

Activities after installationPerformance analysis, re-organizational actions

Determine software requirementsSAP Industry Solutions (most of them absorbed into SAPERP Central Component as of SAP ERP 6.0)SAP country-specific versionsThird-party products or add-onsInterfaces between SAP ERP and non-SAP software Operating system and database

Last but not least …Hardware requirementsRange of testing and trainingCustomer or partner skills in implementation projectsManagement commitment and available resources

Project Duration – Influencing Factors (2/2)


© SAP 2010

Legend

= ERP + EHP5

= old release (6.0)= actual project work

= Transport route

How to Evaluate a Business Function in Your System Landscape

Productive landscape

SAP enhancement package evaluation system

For evaluation („Does the Business Function add value?“) you should not use the DEV system

Recommendation: Use a sandbox system (SBX)Keep in mind: Activation of a business function can in most cases not be revoked (exception: some newly available reversible business functions)

You can only transport the complete BF system switch settings across the system landscape

System copy

System landscape

EHP 4

SBXECC

EHP 5

Build & TestDesign DeployRequirements

DEVECC

QASECC

PRDECC


© SAP 2010

Build & Test DeployDesignRequirements

Prepare Technical Installation

Check PrerequisitesWhat are the prerequisites to check before installing?

Choose Installation ApproachSelective or Broad

Map Business Functions and Technical UsageWhich are ‘Technical Usages’ are relevant?

Design

Result:Business blueprint and technical preparation activities

Define Business AspectsCreate business blueprint for InnovationExecute implementation project with ASAP methodology

Business



© SAP 2010

Build & Test DeployDesignRequirements

Prerequisites for SAP Enhancement Package 5 for SAP ERP 6.0 Installation

1. Up-to-date SAP Solution Manager SAP Enhancement Package 1 for SAP Solution Manager 7.0 (SPS 23 is mandatory)

2. Latest installation or upgrade toolsFor systems on SAP ECC 6.0 use SAP Enhancement Package Installer (SAPehpi)For systems from SAP R/3 4.6C to SAP ECC 5.0 use upgrade tools (SAPup) & bind in SAP Enhancement Package 5 for SAP ERP 6.0 parts

3. Compatibility of Add-onsAsk your add-on provider whether your add-ons are compatible with the SAP enhancement package for SAP ERP 6.0

4. SAP Support PackagesIn general there is no minimal SAP Support Pack level required in the source system where the SAP enhancement package will be installed – refer to the guides and relevant notes for more details.


First you have to bring your SAP Solution Manager up-to-date.

In order to use the Maintenance Optimizer application, you need SAP Solution Manager 4.0 with the highest SAP Support Package level in your system landscape. Your system landscape has to be maintained in the Solution Manager system. You can find more information about the SAP Solution Manager at help.sap.com > SAP Solutions > SAP Solution Manager.

Please make also sure that you have installed the latest SPAM/SAINT update in your system.

Secondly, as you need a certain SAP Support Package level in your system let the SAP Solution Manager Maintenance Optimizer calculate the needed (and equivalent) SAP Support Packages for you. They can be included in the installation queue - the details are explained in the next step.

Thirdly please note that if you have an add-on installed in your system, ask your add-on provider whether it is compatible with the SAP enhancement package for SAP ERP 6.0. See SAP note 1117309 for details of add-ons delivered by SAP.

Fourthly read the documentation and the referenced notes to check that all other prerequisites are met.

https://service.sap.com/sap/support/notes/1117309


© SAP 2010

Mapping Process (Example)

Business Function Technical Usage Main Instances & Software Components

SAP ECC Server

A “Technical Usage”groups software components which must be installed together.

A “Business Function” is the activatable unit within the SAP ECC Server

EA-HR 605

SAP_HR 605

ERECRUIT 600

EA_GLTRADE 600

…….

SAP_APPL 605

EA-APPL 605

SAP NetWeaver 702

Central ApplicationsABAP Product Instance: Central Application

HCM Self ServicesABAP Product Instance: Human Capital Management JAVA Product Instance: SAP XSS (Self Services)

BF

BF

Central Application

MediaABAP Product Instance: Media

FinancialsABAP Product Instance: Leasing/Contract A/R & A/PBusiness Function 3

Lean ManufacturingTechnical Name:LOG_PP_LMAN

Business Function 1Real Estate ManagementTechnical Name:RE_GEN_CI_1

Business Function 2New General Ledger Accounting Technical Name:FIN_GL_CI_1

. . .

BF

Mapping via O

SS Note 1324838


© SAP 2010

How to install SAP Enhancement Package 5 for

SAP ERP 6.0

SAP Enhancement Package 5 for SAP


SAP Enhancement Package Installation

Guide

1

2

3

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

Reading Sequence Of Documentation about EHP Implementation Procedure

Build & Test DeployDesignRequirementsSystem

Administrator


© SAP 2010

Software Installation And Activation

Installation of SAP enhancement package with EHP-installer

Activation of Business Functions using the Switch Framework

Regression and Acceptance Testing

SAP delivers EHP test case templates

SAP Solution Manager enables risk based testing (BPCA)

Build and Test

Result:Getting the solution ready and tested

Further Services

Expert Guided Implementation- Update to SAP Enhancement Package 1 for SAP Solution Manager 7.0 including basic configuration

System AdministratorDeployBuild & Test Requirements Design



Here you can find presentations, documentation, release notes, test catalogues and learning maps. The Business Function Documentation allows the user to get to know the capabilities behind a business function and how to use them; learn about options the business function provides; and notes which software components are needed. Please note that each Business Function has a technical name. This identifier is important to determine which parts of the system needs to be updated.


© SAP 2010© SAP 2007 / Page 1

SAP Enhancement Packages for SAP ERP 6.0Business Function Prediction

Wondering which SAP enhancement package functionality

is potentially relevant for you?

SAP now offers a solution:Prediction of relevant SAP enhancement package functionality based on your existing system usage

Including direct access to:Overview presentationRelease NotesDocumentationTest case catalogsMapping to Technical Usage

Register for a free Business Function Prediction today! http://service.sap.com/BFP

A new version of SAP Enhancement Package Must Know Guide available


© SAP 2010

Activities before the activation …View the list of Business Functions now selectableAccess documentation, release notes, test catalogue and possible dependencies from hereInstall the relevant documentation, refer to SAP note 1066110

BenefitsTransparency of all system and UI changes that will take placeStability for all other parts of the solution

Activities after the activation …Activate the chosen Business FunctionConfigure the chosen Business Function

BenefitsNew coding becomes active only where activatedFaster implementation because only activated parts are configured

Activate and Configure:Transaction SFW5Activate and Configure:Transaction SFW5

Business

The switch transaction shows all the Business Functions that can now be activated after the installation of the new software components.

In the switch framework transaction you can:

View the list of Business Functions available with the latest system setup

Access documentation, release notes, test catalogue, and possible dependencies

Install the relevant documentation, refer to SAP note 1066110

Before the activation you get transparency of all system and UI changes that will take place.

Afterwards you can activate the chosen business functions and perform the configuration tasks.

By that the new coding becomes effective. All other parts of the system remain stable.


New: reversible Business Functions:A reversible Business Function can be tested / evaluated in DEV/QAS systems but only in separate clientsDuring the test of reversible Business Functions no other tests must take place in the whole system as Business Functions are active in all clientsTo completely ‘undo’ a Business Function the whole client has to be deleted Currently there are 37 reversible Business Functions

New With SAP Enhancement Package 5 for SAP ERP 6.0: Reversible Business Functions


© SAP 2010

Switch Framework: Transaction SFW5Transport of Switch Settings

Sandbox DEV QAS PRDtransport transport

activate Business Functions manually

activate Business Functions manually

generate transport with switch settings

import transport with switch settings

import transport with switch settings

Business


SAP Business Suite 7 generally available since May 2009SAP enhancement package concept is proven by high number of live customers

SAP ERP 6.0

SAP CRM 7.0

SAP PLM 7.0

SAP SCM 7.0

SAP SRM 7.0

SAP Business Suite 7

SAP Business Suite 7

Innovations2010

EHP5

EHP1

EHP1

EHP1

EHP3 EHP4

SAP Enhancement PackagesRoadmap











© SAP 2010

How to Evaluate a Business Function in your System Landscape (1/2)

For evaluation purposes („Does the Business Function add value?“) you should not use the development system until you are sure about later realization

Recommendation: Use a sandbox system Keep in mind: Activation of a business function cannot be revoked


SBXECC

SBXECC


DEVECC

QASECC

EHP evaluation system

System copy

System landscape

EHP installation

EHP 4EHP 5EHP 4EHP 5 Activate BF

PRDECC

Legend= ECC + EHP 5= Old release (6.0)= Actual project work= Transport route


SBXECC


© SAP 2010

How to Evaluate a Business Function in your System Landscape (2/2)


For evaluation purposes („Does the Business Function add value?“) you should not use the development system until you are sure about later realization

Recommendation: Use a sandbox system Keep in mind: Activation of a business function cannot be revoked


SBXECC


DEVECC

QASECC

EHP evaluation system

System landscape

EHP 4EHP 5

PRDECC

Legend= ECC + EHP 5= Old release (6.0)= Actual project work= Transport route


© SAP 2010

QASECC

DEVECC

PRDECC

DEVECC

EHP 4EHP 5EHP 4EHP 5

Transport changes

Emergency Corrections

Dual Maintenance

System Landscape Aspects

During and after SAP enhancement package or SAP Support Package installation your development system may not be able to support your production line with emergency corrections and/or phased development go-lives unless you add temporarily a copy of the development system

Based on your risk profile you should consider appropriate measures

Ensure dual maintenance


System landscape Legend= ECC + EHP 5= Old release (6.0)= Actual project work= Transport route

TemporaryDevelopmentSystem

DeployBuild & Test Requirements Design


Application data

(orders, invoices, and

so on)

Use

r(a

utho

rizat

ions

, mas

ter,

reco

rds,

and

so

on)

Client-Specific Customizing

(company codes, plants, storage locations, and so on)

Client-Specific Customizing

(company codes, plants, storage locations, and so on)

Application data

(orders, invoices, and

so on)

Use

r(a

utho

rizat

ions

, mas

ter,

reco

rds,

and

so

on)

Client 100

Adjustments of modifications, custom developments, customizing and interfaces are one of the key cost driver of any implementation project!How to plan efforts and resources for adjustment processHow to identify adjustment needs in custom programs using SAP standard objects

Adjust Applications

Cross-Client Customizing

Repository Objects(such as table definitions, programs, transactions, function modules)

Technology FI CO HR PP MM SD …

Customer developments in the customer

namespace

…

Grouping to form packages

Client 200

Modifications Customer Development

Extension

Challenge: Organize application adjustment process efficiently


© SAP 2010

??? High avail-ability

e.g. iterative testing

Testing all processes in

use

Goodeffort-risk balance

Testing only core business

processes

No testingUnsufficient test

managemente.g. sampling

Ensure Business Continuity

Define business requirements and KPIs for a successful go-live Define suitable test scope: Find right balance between level of risk mitigation and testing effortSet-up efficient test procedures and test KPIsIdentify appropriate training scope and efficient training methods

Make sure that no big surprises occur after upgrade weekend

Testingeffort

Risk

Evaluatetest automation

Rethink yourtest management

Final prep. for cutover


Test Stages –Overview

Realization

Realization

Productionpreparation

tests

Operation

Functionaltests

e.g. SAP Support Packages

Phase

Source: Testing SAP Solutions, ISBN 978-1-59229-127-4

Developer tests

Functional tests

Scenario tests

Integration tests

Technical system tests

User acceptance tests

Regression tests

Final prep. for cutover

Tremendous resource effort, thousands of person-hours

Reducing testing costs while enhancing current testing processes and coverage

A scalable approach that can extend into multiple business groups / lines and applications

Lack of resources and/or loss of productivity due to using business users and/or analyst throughout all testing cycles

Managing quality throughout the life cycle that includes new implementations, upgrades and maintenance through the development and use of a reusable regression suite

Little or no test automation

Testing not enough and/or too late to reduce the cost of fixing defects

Lack of SAP accelerators to reduce automation test development cycle time

No component approach to test design to lower maintenance effort and Total Cost of Ownership (TCO)

Planning for adequate testing procedures and infrastructure to insure application quality and performance

Supporting global deployments that support multiple languages and localization


© SAP 2009 /

Using the Impact Analyzer, you can analyze which user interfaces are affected for which roles and users if you activate a business functionThis enables you to answer the following questions at a very early stage, that is, before you activate a business function:

Which training material is affected?To what extent does the training material have to be adjusted?Which users have to be informed and may need delta training courses?

To use the impact analyzer, start transaction SFW5, select a business function, and choose Impact Analyzer Planned BFs

Impact Analyzer:Transaction SFW5

It evaluates the following user interfaces:

Transactions

Portal i-Views and portal roles

Reports/programs of the ABAP-based system

ABAP WebDynpro applications


© SAP 2010

ActivitiesAcceptance test for selected Business FunctionsUse standard test case templates Train end-usersGo live, transport switch activities to production system

BenefitsFaster test preparation due to test case templatesSmaller test scope because changes are documented for each business functionSmaller training effort due to limited and documented effect on user interfaces

Test & Go Live:SAP Delivers Test Case Templates

Business

All test cases are available as documents in the Enhancement Package Information Center(http://service.sap.com/erp-ehp)Documents (texts) can be downloaded

Access TCTs before installing an SAP enhancement package

Test cases are shipped with the SAP enhancement package and arepart of the installation (SAP ECC)Access the test case from the switch transaction (SFW5)From there, you will (by drilldown) enter the test workbenchTest cases can be transported to SAP Solution Manager via workbench request.

...or after installing an SAP enhancement package

DeployBuild & Test Requirements Design

Test case templates will be available for each business function that is new to an SAP enhancement package.

These templates can be called directly from the switch transaction. The link to the corresponding test case is located right next to each Business Functions.

The SAP test case templates help you to plan and perform your acceptance test and train your end users for the selected business functions.

By that you are also able to narrow down the test scope because functional changes are documented for each business function.

So - where to find Test Case Templates?

Firstly before installing an SAP enhancement package in SAP Service Marketplace. All test cases are available as documents in the SAP enhancement package information center and can be downloaded.

Secondly after installing an SAP enhancement package via the switch framework. Test cases are shipped with the SAP enhancement package and are part of the installation (SAP ECC). From there, you will (by drilldown) enter the test workbench. Test cases can be transported to SAP Solution Manager via workbench request.


Test cases are shipped with the SAP enhancement package and are part of the installation (SAP ECC)Access the test case from the switch transaction (SFW5)From there, you will (by drilldown) enter the test workbenchTest cases can be transported to SAP Solution Manager via workbench request

All test cases are available as documents in the Enhancement Package Information Center(http://service.sap.com/erp-ehp)Documents (texts) can be downloaded

Two Options

Before Installing anSAP Enhancement Package

After Installing anSAP Enhancement Package

Where to Find Test Case Templates

You can either access the Test Case Templates via the Service Marketplace or transaction SFW5 after the installation.











Big Bang versus Phased Upgrades

QuestionWhat is the best roll-out approach for a series of upgrades?Examples:

Different ERP systems are part of a common transport landscape, e.g. in a global template landscape, and need to be upgraded together.Several SAP products of a common solution shall be upgraded, e.g. because of business process dependencies.

Options1.Big Bang: All systems are upgraded in parallel in one common project and go-live at the

same date.

2.One project, phased go-live: All systems are upgraded in parallel in one common project, but go-lives are distributed over several dates (e.g. subsequent weekends)

3.Phased projects: Projects are scheduled and executed independently with go-lives at different dates.

Upgrade ECC + SCMBig BangECC

SCM

Upgrade ECC + SCMPhased Go-Live ECC SCM

Upgrade SCM

Upgrade ECCPhased Projects ECC

SCM


Risks

Costs& Efforts

Option 1Big Bang

Option 2One project, phased go-live

Option 3Two separate projects

– Issues of one project can impact the other

– problem analysis can be harder

+ Go-lives do not depend on each other

+ Projects do not depend on each other

+ one test phase+ one project less overhead– more hardware resources required

for project– more external project resources

+ One test phase+ one project less overhead– Min. test of intermediate state

required– More hardware resources required

for project– more external project resources

+ Less hardware resources requirement for project

+ projects better handled with internal resources

– Two test phases

Benefits + Earlier realization of process enhancements in new releases

+ Earlier realization of process enhancements in new releases

– Later realization of process enhancement in new releases

+ one business downtime+ one code freeze period+ key business users needed only one

time– problem resolution may need longer– higher work load on key users

+ Root cause of problems can be better separated

+ one code freeze period+ key business users needed only one

time– Two Business Downtimes– higher work load on key users

+ Root cause of problems can be better separated

+ less work load for key users– Two Business Downtimes– two code freeze periods– key business users needed two

times for projects

Business Impact

Crit

eria

Evaluation of Big Bang versus Phased Upgrade

Note: The pros and cons arguments above represent general considerations that are valid for most situations in which a roll-out approach has to be defined. Nevertheless, they shall be regarded as model only. Content, importance and judgment of the pro and con arguments will definitely differ in a specific customer situation.


Implementation in Complex Landscapes:Upgrade Dependency Analyzer

Upgrade ECC

Potential release dependenciesbetween Upgradeable Units

Identify release dependenciesWhich Upgradeable Units to upgrade at the same time

CRM

Self Services

Learning Solution

...

SRMSEM

R/3

CRM

Self Services

Learning Solution

...

SRMSEM

?

ECC


Upgrade Dependency Analyzer Customer View (1)

Planning an Upgrade?

Find out dependencies within your SAP system landscape!

Example:

http://service.sap.com/uda





Example:

Upgrade one system to SAP ECC 6.05





Example:


Searching for dependencies to second system SAP SCM 7.0



Accessible via SAP Service MarketplaceAlso integrated in SAP Solution Manager



Example:


Searching for dependencies to second system SAP SCM 7.0

Result: no known upgrade dependencies!

Possible Results of a Dependency Analysis:

No known upgrade dependencies, independent upgrade possible: When upgrading to the target component, all standard cross-system functions that worked prior to the upgrade will be retained. New cross-system functions may require an upgrade of the existing component you have specified.

Independent upgrade possible, but with known restrictions: When upgrading to the target component, all standard cross-system functions that worked prior to the upgrade will be retained. If there are restrictions, you will find them in the attached SAP Note.

Independent upgrade not possible: After the upgrade to the target component, some or all standard cross-system functions will no longer work. It is required to also upgrade the existing component you have specified, or you may have to manually implement those cross-system functions in a different way.

Loss of cross-system functions: After the upgrade to the target component, some or all standard cross-system functions will no longer work. You need to manually re-implement those cross-system functions in a different way. It is not possible or sufficient to upgrade the existing component.

No interaction: The two components you have specified have no standard cross-system functions in common. No direct interaction exists. You can upgrade the components independently.

No interaction in existing release combination: The releases specified are indicating an existing release combination with no standard cross-system functions in common. No direct interaction exists before the upgrade. You can upgrade the components independently.


Check the existence of upgrade dependencies between two separately installed SAP systems in your system landscape

Landscape analysis capabilities (planned fornext SAP Solution Manager release)

Description

Access

Benefits

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

Planned: SAP Solution Manager ‘Implement./ Upgrade: Upgrade Analysis’ work center

Simplification of upgrade planning

Fast and easy access to needed dependency information for all SAP solutions

Reduction of risks, costs and effort

Reuse of customer specific system landscape definition (planned for next release)

Upgrade Dependency Analyzer


High level technical planningShows known dependencies on technical level according to categories:

Dependency existsConditional dependency existsCurrently no dependencies

Focus of Upgrade Dependency Analyzer vs. Scenario & Process Component List

Answers the question:Will a given combination of two systems still work (still be supported by SAP) after the upgrade of one of these systems?

Upgrade Dependency Analyzer

Answers the question:Which scenarios/processes will continue to work (or will not work any more) after the upgrade of a component in a defined system landscape?

Scenario & Process Component ListDetailed analysis on process levelShows predefined scenarios/processes before and after an upgrade according to categories:

Already availableAdditionally available after upgradeNot available after upgrade











1

New Installation

2 Upgrade of anExisting System

3EnhancementPackageInstallation

Implementation ScenariosDifferent Use Cases


NW 7.0

NW EHP2

NW 7.1

ERP 6.0

ERP6.0

NW EHP1

NW EHP2

* SAP ERP 6.0 EHP5 Ready Installation

ERP6.0

ERP 6.0

ERPEHP5

NW EHP2

SAPehpi

ERP 6.0

ERPEHP4

SAPehpi

ERPEHP5

NW EHP2

Implementation Scenarios Different Use Cases

New Installation1

SAPInstNW

EHP1SAPehpi

ERP*EHP5

The SAP ERP 6.0 EHP5 Ready installation of an SAP ECC system contains only technical usage ‘Central Applications’ (SAP_APPL and EA_APPL) on 6.05 level. All others are on 6.00 level only.



Upgrade of an Existing SystemNW 7.0

NW EHP2

NW 7.1

ERP 6.0

ERP6.0

ERPEHP4

2

NW 2004 SAPup/ SAPJup

NW EHP1

ERPEHP5

NW EHP2

R/34.6C SAPup/ SAPJup

NW EHP1


ERP6.0


Enhancement Package Installation3

NW 7.0

NW EHP2

NW 7.0

ERPEHP5

NW 7.1

SAPehpi

NW 7.1

ERP6.0

SAPehpi NW EHP1

NW EHP2

SAPehpi

ERP 6.0

ERPEHP4

ERP6.0

NW EHP1

SAPehpi


SAP Enhancement Package 5 for SAP ERP 6.0 requires SAP Enhancement Package 1 for SAP Solution Manager 7.0

Maintenance Optimizer must be set up and running (check Note 1122966)

Maintenance Optimizer analyzes the ERP’s software components and calculates a list of packages

SAP Enhancement Package 5 for SAP ERP 6.0 is installed with a new tool

SAINT is not supported anymore (SAP note 1256600).

SAPehpi reads the list of packages from Solution Manager

The SAPehpi tool reduces the downtime dramatically compared with SAINT


Always combine the installation of SAP enhancement packages with the installation of the latest SAP Support Package stack

Key Take Aways


SAP Enhancement Package 4 for SAP ERP 6.0: Equivalent Target SAP Support Packages

Requirements Build & Test DeployDesign

Attention: Do not install new SAP Support Packages before an SAP enhancement package installation unless you are sure that the equivalent SAP enhancement package Support Packages have already been released

During an SAP enhancement package installation, the target SAP Support Packages that are equivalent to the current SAP Support Package levels must be included in the installation queue.If the equivalent target SAP Support Packages are not yet released, you must postpone the SAP enhancement package installation until the release date.

SAP ERP 6.0 Support Package

Equivalent EHP4 Support PackageExample

Software Component SAP_BASIS SAP_BASIS

Version 700 701

SAP Support Package SP 19 SP 05

Release Date CW 25 (June) CW 41 (October)

In this example, the SAP Enhancement Package 4 for SAP ERP 6.0 installation would have to be postponed for more than three months if SAP_BASIS 700 Support Package 19 was installed directly after its release in June

Summary: In general, SAP recommends to implement the latest SAP Support Packages, but if you are planning an SAP enhancement package installation, careful scheduling is necessary


Consider additional temporary system resources: (free space on file systems, DB & log archives)

SAPehpi installation directory: ~ 25GB EHP4 & SPS Download directory: ~ 10GB depending on # of packagesFree space in /usr/sap/trans : ~ 4GBShadow system ~ 60-80 GBAdditional free space in table spaces: ~ 20-50 GB 150- 170 GB should be sufficientArchive Logs

Start early enough with the SAPehpi process! Until end of preprocessing phase SAPehpi can run during system uptime, i.e. start at beginning of the week Consider executing the preprocessing phase during low DB utilization times (i.e. a weekend earlier) After uptime preprocessing you can stop SAPehpi and continue later with the downtime phases at beginning of maintenance windowConsider time for postprocessing

Manual clean-up steps and load generationAdjustment transports and BackupTesting & validation

SAPehpi – Best Practices



Here you can find Presentations, Documentation, Release notes, test catalogues and Learning Maps. The Business Function Documentation allows the user to get to know the capabilities behind a business function and how to use them; learn about options the business function provides; and notes which software components are needed. Please note that each Business Function has a technical name. This identifier is important to determine which parts of the system needs to be updated.


Upgrade Downtime

up up

down

SAPup:PREPARE

& repository

import

SAPup: conversion, XPRAS, etc.

backup?go/no-go decisionbackup?

transports & manual tasks

Business validation

tests

Recording

PRDR/3 4.6C

(reduced) uptime

cloned PRD

PRDECC 6.05

Validation,sign-off

downtime

clone

Delta replay

ICNV Near Zero Downtime Upgrade

Upgrade and Unicode Conversion


Application-Specific (ASU) Toolbox

Before/after a technical upgrade often additional application-specific steps need to be performed

ASU collects and summarizes these activities

Enables you to recognize the necessary steps and perform them in a controlled manner

ASU toolbox is integrated with the upgrade GUI through the ASU phase in the upgrade process

One tool for all kinds of predefined tasks (reducing the upgrade time)

Making the upgrade more transparent (avoid mistakes)

Avoiding problems after the upgrade(message reduction)

DESCRIPTION

ACCESS

BENEFITS











Adoption SAP Enhancement Packages for SAP ERP 6.0 – January 2011

LA

798

6%

44%(350)

51%(404)

NA

1.534

5%

30%(456)

64%(986)

APJ

1.542

6%

31%(474)

63%(974)

EMEA

6.136

6%

27%(1.642)

67%(4.110)

Regional View of current month

Customer is counted only once with its latest release

Source: Early Watch Alert. EWA counts technical installations in productive systems and represents ~50% of installed based customers. Number of reported productive customers multiplied to reflect EWA coverage.

Productive Customers

Jan 11

10.010

6%

29%

65%

Dec 10

9.642

6%

41%

7.915

May 10

42%

8.822

7.430

44%

44%

Jun 10

47%

Jul 10

41%

15% 11%

8.540

13%

32%

17%

51%

Mar 10

15%

Feb 10

49%

35%5.972

6.954

47%

38%

Apr 10

6.528

16%18%

61%

Oct 10

9.420

30%

63%

7%

34%

58%

Nov 10

9.544

Sep 10

9.122

9% 7%

32%40%

50%

Aug 10

5.348

Jan 10

5.660

20%

56%

23%

19%

55%

28%26%

Dec 09

53%

Months growthof all SAP enhancement packages for SAP ERP 6.0 and SAP Enhancement Package 4 for SAP ERP 6.0

EMEA APJ NA LA

EHP all +248 +64 +24 +32

EHP 4 +240 +58 +38 +22

The different colors on the slide reflect SAP Enhancement Package 2, 3 and 4 for SAP ERP 6.0.


3.500

7.000

10.500

14.000

17.500

Jan 11Dec 10Nov 10Oct 10Sep 10Aug 10Jul 10Jun 10May 10Apr 10Mar 10Feb 10Jan 10Dec 09Nov 09Oct 09Sep 09

= 16.566

= 6.474

= 10.010

KEY MESSAGE- Already more than 6.470 productive SAP Enhancement Package 4 for SAP ERP 6.0 customers after 20 months of general

availability- Based on the numbers, customers are switching on new functionality roughly after 6 months*

Customers is counted once with its latest release

Source: Early Watch Alert. EWA counts technical installations in productive systems and represents ~50% of installed based customers. Number of reported productive customers multiplied to reflect EWA coverage.

SAP EHP 4 total # of prod. customers SAP EHP total # of prod. customersSAP ERP 6.0 total # of prod. customers

Adoption of SAP Enhancement Packages for SAP ERP 6.0


0

3.000

6.000

9.000

12.000

Dec 10Nov 10Oct 10Sep 10Aug 10Jul 10Jun 10May 10Apr 10Mar 10Feb 10Jan 10Dec 09Nov 09Oct 09Sep 10Aug 09Jul 09Jun 09May 09 Jan 11

10.010 EHP customers

General Availability (GA) of SAP Enhancement Package 4 for SAP ERP 6.0

Productive Customers

Growth of productive SAP Enhancement Package for SAP ERP 6.0 Customers


© SAP 2010

SAP ERP – Top 10 Business FunctionsAugust 2010

S A P E nhanc ement P ac kag e 2 for S AP E R P 6.0 S A P E nhanc ement P ac kag e 3 for S AP E R P 6.0

S A P E nhanc ement P ac kag e 4 for S AP E R P 6.0

B us ines s F unc tion Name B us ines s F unc tion Des c ription

F IN_T R AVE L_1 S AP T ravel Management E nhancements

S D_01 O rder-to-C ash S implification

HC M_AS R _C I_1 HC M P rocesses and F orms

F IN_F S C M_INT E G R ATIO N F S C M, Integration

L O G _MM_C I_1 B usiness F unction Materials Management

HC M_L S O _C I_1 S AP L earning S olution

F IN_AC C _G R O UP _C LO S E G roup C lose

IS U_UTIL _1 R eal E state Management

R E _G E N_C I_1 Utilites, G eneral E nhancements

F IN_F S C M_C C D F S C M, F unctions


F IN_G L _C I_1 New G eneral Ledger Accounting

F IN_R E P _S IMP L _1 R eporting F inancials

/K Y K /G E N_AIO _S IMP LIF IC AT IO N R oles in S AP All-In-O ne

HC M_E S S _C I_1 HC M, E S S for P ersonal Information

O P S _P S _C I_1 P roject S ystem

HC M_E R C _C I_1 HC M, S AP E -R ecruiting 1

L O G _E S O A_OP S _2T R M: Hedge Management, New Instruments, New K ey F igures

F IN_T R M_L R _F I_AN O perations, E nterprise S ervices 2

L O G _P P _MIS Manufacturing Information S ystem

L O G _S D_C I_01 S ales and Distribution


E R P _E NTE R P R IS E S E AR C H E nterprise S earch in S AP E R P

HC M_AS R _C I_2 HC M, Administrative S ervices 02

HC M_O S A_C I_1 HC M, P erformance Management 01

E R P _AL L _P DF _F O R MS All C ommon F orms Available in P DF

L O G _MMF I_P 2P MM, Integration of MM and F I

E R P _AL L _LIS T S E R P , New User Interface for AB AP L ists

F IN_R E P _S IMP L _2 R eporting F inancials 2

F IN_G L _C I_2 G eneral L edger Accounting 2

HC M_L S O _C I_2 HC M, L earning S olution 02

HC M_T MC _C I_1 HC M, C ore P rocesses in T alent Management


SAP Upgrade Experience Databaseprovides orientation on

Project duration Business downtimeSatisfaction with the upgradeEtc.

A frequent request from SAP customers to SAP:'We would like to see benchmarking data from other

completed customer upgrade projects'

Strong Customer Demand for Upgrade Experiences Gathered in Upgrade Projects

The anonymous results are available in SAP Service Marketplace.

Note: The SAP Upgrade Experience Database currently provides only information on ERP upgrades.


Provide YOUR Feedback! Benefit from Others Feedback!

Provides benchmarking data and project statistics from completed SAP enhancement package implementation projects, for example, on project duration, downtime, satisfactionUp-to-date results and the online questionnaire are published at http://service.sap.com/ehp-db.

SAP Enhancement Package Experience Database

Please send Evaluation Form (Statistics plus your individual feedback comment) via email!

The statistics of your SAP enhancement package implementation help us improving the SAPehpi!Your individual comments are reviewed within our tool development!

SAPehpistatistics


© SAP 2010

Current StatisticsSAP Enhancement Package Installer

SAPehpi statistics for SAP Enhancement Package 4 for SAP ERP 6.0

*This statistic is based on the current evaluation forms referring to test and productive systems where an SAP Enhancement Package 4 for SAP ERP 6.0 implementation was performed.

SAPehpi downtime

SAPehpi runtime

Median runtime: 44h Median downtime: 7,5h

Build & TestDesignRequirements Deploy


1 Upgrades to SAP ECC 6.0 with source release SAP R/3 4.6C and SAP R/3 Enterprise, no Unicode Conversion; Source: Upgrade Experience Database2 Enhancement packages for SAP ERP 6.0; this number represents an extract only out of more than 5,900 enhancement package installations globally

(as of February 2010); Source: Enhancement Package Experience Database

Project duration

(weeks)

Weeks

Project person days

Project effort

(person days)

Upgrade versus SAP Enhancement Packages Installation: Project Duration and Effort


© SAP 2010

SAP ERP – Top 10 Business Functions*



F IN_T R AVE L_1 S AP T ravel Management E nhancements

S D_01 O rder-to-C ash S implification

HC M_AS R _C I_1 HC M P rocesses and F orms

F IN_F S C M_INT E G R ATIO N F S C M, Integration

HC M_L S O _C I_1 S AP L earning S olution

F IN_AC C _G R O UP _C LO S E G roup C lose

L O G _MM_C I_1 B usiness F unction Materials Management

IS U_UTIL _1 Utilites, G eneral E nhancements

R E _G E N_C I_1 R eal E state Management

F IN_F S C M_C C D F S C M, F unctions


F IN_G L _C I_1 New G eneral Ledger Accounting

F IN_R E P _S IMP L _1 R eporting F inancials

/K Y K /G E N_AIO _S IMP LIF IC AT IO N

R oles in S AP All-In-O ne

HC M_E S S _C I_1 HC M, E S S for P ersonal Information

O P S _P S _C I_1 P roject S ystem

HC M_E R C _C I_1 HC M, S AP E -R ecruiting 1

F IN_T R M_L R _F I_AN T R M: Hedge Management, New Instruments, New K ey F igures

L O G _E S O A_OP S _2 O perations, E nterprise S ervices 2

HC M_E R C _S E S _1 HC M, S AP E -R ecruiting - S earch 1

L O G _S D_C I_01 S ales and Distribution


E R P _E NTE R P R IS E S E AR C H E nterprise S earch in S AP E R P

HC M_O S A_C I_1 HC M, P erformance Management 01

HC M_AS R _C I_2 HC M, Administrative S ervices 02

F IN_R E P _S IMP L _2 R eporting F inancials 2

F IN_G L _C I_2 G eneral L edger Accounting 2

E R P _AL L _P DF _F O R MS All C ommon F orms Available in P DF

L O G _MMF I_P 2P MM, Integration of MM and F I

E R P _AL L _LIS T S E R P , New User Interface for AB AP L ists

HC M_L S O _C I_2 HC M, L earning S olution 02

HC M_T MC _C I_1 HC M, C ore P rocesses in T alent Management

*1st July 2010



HC M, C ore P rocesses in T alent ManagementHC M_T MC _C I_1

HC M, L earning S olution 02HC M_L S O _C I_2

E R P , New User Interface for AB AP L istsE R P _AL L _LIS T S

MM, Integration of MM and F IL O G _MMF I_P 2P

All C ommon F orms Available in P DFE R P _AL L _P DF _F O R MS

G eneral L edger Accounting 2F IN_G L _C I_2

R eporting F inancials 2F IN_R E P _S IMP L _2

HC M, Administrative S ervices 02HC M_AS R _C I_2

HC M, P erformance Management 01HC M_O S A_C I_1

E nterprise S earch in S AP E R PE R P _E NTE R P R IS E S E AR C H

B us ines s F unc tion Des c riptionB us ines s F unc tion Name


© SAP 2010

Service offering: SAP Enhancement Package Planning for SAP ERP 6.0

Overview….Intensive 2 days onsite workshopWe plan your SAP enhancement package installation project & strategyLearn from experienced SAP consultantsFeel well prepared to start your implementation project!

Project Milestone Plan• We define a customer specific implementation

approach & EHP strategy

• We create an SAP enhancement package project roadmap based SAP’s best practices & proved methodology

Landscape Dependencies• Identify technical dependencies of your system

landscape

• Outlines critical issues for a smooth Implementation project

• Getting behind the new technology

• Understand the concept of switchable Business Functions & Technical Usages

• Learn how to use “EHP Installer” Tool

Knowledge Transfer

Order & Contact Details…Direct contact: [email protected]

Service Market Place link: /ufg

Your Benefit:* New SAP Consulting

Service Offering


Criteria Upgrades¹ SAP Enhancement Packages²Customer satisfaction

Reasons for upgrading / installing enhancement packages

1%4%

18%

41%

36%

Not satisfiedLess satisfiedSatisfiedMore satisfiedVery satisfied 8% 5%

2%

32%53% Not satisfied

Less satisfiedSatisfiedMore satisfiedVery satisfied

0 20 40 60 80 100

MaintenanceBusiness innovation

Use latest technologyImprove usability

Functional requirementsManage modifications

System landscape cons.Legal compliance

0 20 40 60 80 100

Others

Functional requirementsManage modifications

Business innovationUse latest technology

Improve usability

System landscape cons.Legal compliance

1 Upgrades from SAP R/3 4.6C to SAP ECC 6.0; Source: Upgrade Experience Database² Based on n = 91 enhancement package installations (EHP 2 to 4); this number represents an extract only out of more than 5,900 enhancement package installations globally (as of February 2010); Source: Enhancement Package Experience Database

n = 165

n = 168

Upgrade versus SAP Enhancement Package Installation: Overall Satisfaction And Reasons


Criteria Upgrades¹ Reduction SAP Enhancement Packages²

Business downtime (technical installation)

Ø 48 hours Ø 24 hours

Total project duration Ø 21 weeks Ø 8 weeks

Duration of project phases in weeks

Preparation: 3 wBlueprint: 3 wRealization: 8 wPrep for cutover: 3 wProd. cutover & support: 2 w

Preparation: 1 wBlueprint: 1 wRealization: 2,5 wPrep for cutover: 2 wProd. cutover & support: 1 w

- 50%

- 62%

up to 70%

1 Based on n = 168 upgrades from SAP R/3 4.6C to SAP ECC 6.0; Source: Upgrade Experience Database² Total number of enhancement package installations (EHP 2 to 4): n = 91; only those considered which provided details on these questions; this number

represents an extract only out of more than 5,900 enhancement package installations globally (as of February 2010); Source: Enhancement Package Experience Database

According to current statistics the installation of SAP enhancement packages for SAP ERP 6.0 greatly increases the speed of innovation while reducing its cost.

n = 87

n = 88

n = 67

Upgrade versus SAP Enhancement PackagesInstallation: Customer Experience (Overview)











© SAP 2010

Service offering: SAP Enhancement Package Planning for SAP ERP 6.0

* New SAP Consulting

Service Offering

Overview….Intensive 2 days onsite workshopEHP installation project & strategy planningLearn from experienced SAP ConsultantsFeel well prepared to start your Implementation project !

Project Milestone PlanWe define a customer specific implementation approach & EHP strategy

We create an SAP enhancement package project roadmap based SAP’s best practices & proved methodology

Landscape DependenciesIdentify technical dependencies of your system landscape

Outlines critical issues for a smooth Implementation project

Getting behind the new technology

Understand the concept of switchable Business Functions & Technical Usages

Learn how to use SAPehpi

Knowledge Transfer

Order & Contact Details…Direct contact: [email protected]

Service Market Place Link: /UFG

Your Benefit:


The ConceptPurpose of the SAP ERP enhancement package strategy Concept and methodology of enhancement packagesWhat you need to know beforeHow to implement them What to test at what point in time

Functional OverviewWhich enhancements are included in each enhancement package? Which areas of the solution were touched by new developments?

Level 1 => ‘Short overview presentation’:

Get an idea of each business function(short description and target group)

Level 3 => ‘Detailed presentation’:

Understand each feature ofa business function(~ 1 slide per feature)

Level 4 => ‘Online information’:

Assess each business function, using all related information. This is presented in a table-like list with links to documentation, test cases, release notes, detail presentations, etc.

Business

Level 2 => ‘Detailed overview presentation’:

Understand each business function with features included, benefits, target users and their and technical name.(~ 1 slide per business function)

How To Use The Enhancement Package Information Center


Business Function Documentation

First, select the appropriate link from section (1), then search for the required business function and click on link (2).

The SAP enhancement package information center contains documentation for each enhancement package business function

Technical Usages and Business Packages that are required to use the business function

Additional business functions that must be activated as well

Prerequisites that must be satisfied before the activation

Features that become available when the business function is activated

Business


© SAP 2007 / Page 1

What IT professionals must know about

New version of SAP Enhancement Package Must Know Guide available

A new version of SAP Enhancement Package Must Know Guide available


© SAP 2010

Get Started – Enhancement Package Infocenter: http://service.sap.com/erp-ehp

Master Guide&

How to Install EHP5: A Practical Guide

SAP enhancement packages -Frequently Asked Questions

Lifecycle of SAP enhancement packages

SAP enhancement packages Technology Facts

SAP enhancement package strategy for SAP ERP

ERP@BPX: SAP enhancementpackage Forum & Wiki

SAP EHP Info CenterEnhancement Package

Info Center


Exercises

Unit 2: Solution Manager: Selection of Technical Usages Topic: Configure SAP enhancement package stack

1.) Create entry for your system in SAP Solution Manager, transaction SMSY. The name of your SAP system in the SMSY should be D## (whereby ## stands for your group number). Use the Assistant to assign a logical component and create the needed RFC destinations to your SAP system.

2.) Create a solution via transaction SOLUTION_MANAGER or SOLMAN_WORKCENTER. Assign the logical component of your SAP system to the solution. Create a maintenance transaction for installing SAP enhancement package parts for your SAP system, using the Maintenance Optimizer.

3.) Configure the needed parts of SAP Enhancement Packahe 5 for SAP ERP 6.0 and the XML and TXT files by selecting the relevant Technical Usages. Assume that the Technical Usages Central Applications and Human Capital Management are desired.

Hint: It is not necessary to really download the files from the SAP Enhancement Package 5 for SAP ERP 6.0 and to copy the XML and TXT files, because they are available on your host already. Note: in the XML file (located in directory ADM327_col72\SMS) the host name twdf0000 has to be replaced by your actual host name. You can perform a replace all using Wordpad.


Exercises

Unit 3: SAPehpi: Enhancement Package Installation Topic: Run SAPehpi up to roadmap step Preprocessing

1.) Download the installation guide Installation Guide SAP Enhancement Package Installation Using SAP Enhancement Package Installer (SAPehpi) 7.00 for operating system Windows and database Oracle from SAP Service Marketplace

It can be found at: → service.sap.com/instguides → SAP Business Suite Applications → SAP ERP → SAP ERP 6.0 → SAP enhancement packages for SAP ERP 6.0 → SAP enhancement package 5 for SAP ERP 6.0 → SAP enhancement package installer (SAPehpi) guide → (ABAP systems, Windows) Oracle

or at ADM327_col72\Guides ;-)

2.) Check and follow Chapter 1, 1.3.3: SAP Notes for the Installation

Especially consider SAP notes 1302772 and 1161052.

For this class ADM327 only the following steps have to be performed::

- note the keyword for the installation

- use the ASU Toolbox, as described in SAP note 1000009

3.) Check and follow Chapter 4: Preparation

For this course ADM327 especially consider the following steps:

- 4.12 Filling the Download Directory: create the download directory any copy there the content of the ADM327_col72 subdirectories Kernel_Patch_702, MOpz_Download, SAPehpi, SMS and Support_Packages_605.

- 4.4 Making Preparations at the Database Level

4.) Start SAPehpi as described in Chapter 5: Installation Process Run SAPehpi up to roadmap step Preprocessing

Start the installation program (5.2) and the installation GUI (5.3). Provide all necessary input.
