ADM326 SAP ECC Upgrade - hservers.org

© SAP 2010

ADM326 SAP ECC Upgrade

SAP ECC Upgrade

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)

ADM326

� Material number: 50101086

© SAP 2010

Copyright 2011 SAP AG. All rights reserved.

Neither this training manual nor any part thereof may

be copied or reproduced in any form or by any means,

or translated into another language, without the prior

consent of SAP AG. The information contained in this

document 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.

Course Prerequisites

Required Knowledge� Knowledge of SAP system administration

� Basic knowledge of database and operating system administration

Recommended Knowledge� ADM100 Administration AS ABAP I

� ADM325 Software Logistics AS ABAP

Target Audience

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

� Technology consultants

� Project team leads

Duration: 5 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.

Course Goals

This course will prepare you to:� plan and implement upgrades for SAP systems

Course Objectives

After completing this course, you will be able to:� plan and implement upgrades for SAP systems

Agenda

1. Concept and Architecture2. Sequence and Major Steps3. Selecting the Target Release 4. Modification Adjustment5. Technical Phases6. Troubleshooting7. Incremental Conversion

8. Support Packages and Add-Ons9. Downtime

10. Planning and Preparation 11. Enhancement Packages12. Unicode Conversion13. Tools and Services14. SAP Notes for this Course

© SAP 2010

Agenda: Concept and Architecture

1. Concept and Architecture

2. Sequence and Major Steps3. Selecting the Target Release 4. Modification Adjustment5. Technical Phases6. Troubleshooting7. Incremental Conversion



© SAP AG ADM326 1-1

Concept and Architecture

Contents:� Why and when should a customer upgrade a productive system?

� Overview of different releases

� Products and terms used in the context of an upgrade

Old Release

New Release

Upgr

ade


SAP Business Suite

SAP NetWeaverIntegration E

HP

EH

P

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

Enhancement

packages: ‘Non-

disruptive’

innovation for

the SAP

Business Suite

For 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 Now

Packages

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 Pears

Tec

hn

olo

gy

Ap

pli

cati

on

� 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 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 Enhancement Packages & SAP ERP 6.0

Quick Facts About SAP ERP 6.0

� Launched in June 2006

� Platform upon SAP will deliver future software innovations via ‘SAP enhancement packages’

� SAP enhancement package 5 for SAP ERP 6.0 generally available in 2011

SAP Business Suite - Stable Core

SAP NetWeaver

SAP ERP 6.0

Enhancement Packages

2006 2008 2010 2012+

What are enhancement packages?

� Optionally installed and activated software innovations for SAP ERP 6.0

� Software innovations include

� UI simplifications

� Functional enhancements

� Enterprise services

� Cumulative: current enhancement package contains all functionalities of previous packages

� Enhancement packages are not Support Packages: Support Packages contain corrections and legal changes, SAP enhancement packages new functionality

� 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 services (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.

� From a functional perspective SAP enhancement packages are cumulative: each current SAP

enhancement packages contain the entire content of earlier packages. So each SAP enhancement

package is based on the previous one. 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 Support Packages. SAP provides Support Packages for SAP ERP

6.0 on a regular basis during the defined maintenance period and, in parallel, in the equivalent

Support Packages for SAP enhancement packages for SAP ERP.

� Since Business Suite 7 Innovation 2010 (BS 7i2010) SAP enhancement packages also exist for SAP

CRM, SAP SCM, and SAP SRM.


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

4.6D

6.10

6.20

6.30

6.40

7.00

7.00

7.00

7.00

7.10

7.01

7.02

7.11

7.30

4.6C

-

-

4.7

4.7

5.0

6.0

(6.01)

(6.02)

(6.03)

-

(6.04)

(6.05)

-

-

-

-

-

1.10

2.00

5.00

6.00

(6.01)

(6.02)

(6.03)

-

(6.04)

(6.05)

-

-

2003

2003

2004

6.0 (2005)

6.0 EHP1

6.0 EHP2

6.0 EHP3

-

6.0 EHP4

6.0 EHP5

-

-

2004 ('04)

7.0 (2004s)

7.0

7.0

7.0

-

7.0 EHP1

7.0 EHP2

-

7.3

Part of

SAP NetWeaver

Part of

SAP 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 enhancement packages.

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

level.


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 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

EE

2.05

EE

2.00

SAP_BASIS 6.20

SAP_HR 4.7

EE

2.05

EE

2.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 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

EE

6.00

EE

6.00

IE

6.00

IE

6.00

IE

6.00

IE

6.00

SAP_BASIS 7.00

SAP_HR 6.0

EE

6.05

EE

6.00

Basis is now calledSAP NetWeaverAS 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 ECC 6.05 (Example)

SAP ECC 6.05

ABAP

SAP_APPL 6.05Add-On

Add-On

SAP_ABA 7.02

EE

6.05

EE

6.00

IE

6.05

IE

6.00

IE

6.00

IE

6.00

SAP_BASIS 7.02

SAP_HR 6.0

EE

6.05

EE

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


SAP ECC 6.0 and above: Industry and Enterprise Extensions

Industry Extensions � Consist of Business Functions Sets (BFS) and Business Functions (BF)

� Activated per Switch Framework

� Only ONE Industry Extension can be activated per SAP system

� Cannot be deactivated once it has been activated (no switch to another industry extension possible)

� Activation of one or more Business Functions (BFS and BF) per SAP system possible

� See note 838003 for further information

Enterprise Extensions� Parts of former industry solutions were integrated in Enterprise Extensions

� Consist of Generic Business Functions

� Activation of all Enterprise Extensions by the SAP Switch Framework

� The Enterprise Extensions are available in addition to the Industry Extensions

� Activation of one or more Enterprise Extension per SAP system possible

� Activation of more than one generic business function of the Enterprise Extension at the same time possible

� See note 838002 for further information

� 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


Activation of Industry and Enterprise Extensions

Switch Framework:Transaction SFW5

� 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.


Plan Build Run

Upgrade

DiscoveryUpgrade Implementation

Upgrade

Evaluation

Operations &

Continuous

Improvement

Upgrade Project

completedUpgrade Project

started

Define Business and IT requirements

Definestrategy

Minimize costs and risks of Upgrade Project

Upgrade Roadmap

Project

PreparationRealization

Final Preparation

for Cutover

Production

Cutover &

Support

Blueprint

Document current solution and set-up

project

Specify implementation

scope and solution adjustment needs

Implement and adjust solution

Perform integration and system tests and plan cutover

Execute production system Upgrade &

Support

Upgrade as a Project –Discover, Evaluate & Implement

� An upgrade of a productive ECC system is not done at one weekend. But it is a whole project, that

lasts for months.


472471464402

SAP IS-M4.6C

SAP R/3

3.0B

SAP IS-EC

471463461

SAP IS-U/FERC

4.6C4.6B4.5B4.1B

SAP JVA

2.2B/2.7B/4.6C2.2B/2.7B/4.6B2.2B/2.7B/4.5B

SAP EH&S

2.00

SAP LEARNING SOLUTION

4.724.714.644.614.51

FS-CD

SAP INSURANCE

4.724.714.64

FS-CM

4.724.714.64

FS-CS

4.724.63B

SAP PATIENT MANAGEMENT

4.6C12.0B

1.0B

SAP IS-MP

3.0B2.0B

SAP IS-AD

4.61

SAP IS-HT

5.0

SAP ECC DIMP

4.71

SAP DIMP

4.6C2

SAP DI

4.724.6C4.6B4.0B

SAP IS-OIL

4.6C4.6B

SAP IS-MINE

4.724.714.64

SAP FI-CA472471464461

SAP IS-T

2.11.0

SAP PLM RECIPE MANAGEMENT

4.634.614.03

SAP BANKING

2.0

SAP CFM

4.624.614.02

SAP IS-PS-FM3.002.05

SAP VADM

4.724.714.64

SAP PUBLIC SECTOR PSCD

4.724.714.64

SAP IS-HER-CM

Industry add-ons integrated into SAP ECC 6.0 (see SAP Note 838003)

Non industry add-ons integrated into

SAP ECC 6.0 (see SAP Note 838002)

472471464461

SAP IS-U/CCS

4.72

SAP WASTE AND RECYCLING

4.624.614.52

SAP HR-PS

SAP ERP 6.0 + EHP 5SAP XECO

SAP XSSSAP SEM

EHP 5

SAP ECC 6.0

Target

2.0

SAP IS-CWM

47X20047X110

SAP R/3 ENTERPRISE

4.6C

SAP PLM ADDON

4.6C

SAP PH-ELR

SAP ERP 2004

5.0

SAP ECC

Upgrade to SAP ECC 6.0 including SAP Enhancement Package 5 possible from…

Upgrade to SAP ECC 6.05 (part of SAP enhancement package 5 for SAP ERP 6.0)

� This overview shows all possible start releases for the upgrade to SAP ECC 6.05 (SAP enhancement

package 5 for SAP ERP 6.0, Business Suite 7 Innovations 2010).

� SAP offers for all industry solutions an upgrade path to SAP ECC 6.0.

� The smallest start release for the upgrade to SAP ECC 6.0 without an enhancement package is SAP

R/3 3.1I

� Beginning of Service Release 3 for SAP ECC 6.0 the smallest start release is SAP R/3 4.0B.

� Since SAP enhancement package 3 for SAP ERP 6.0 together with Service Release 3 for SAP ERP

6.0, it is possible to include parts of the enhancement package into the upgrade procedure.

� Beginning with ECC 6.05 the smallest start release is SAP R/3 4.6C.


Possible Upgrade Approaches: Think Big And Start Small

…are large projects…

� Affecting the whole

enterprise

� Demanding in-depth knowledge of

� Business models

� Processes

� Application landscapes

� Application modification

� Requiring strict planning and precise timing

Discover,

prepare

and

get even

more

value

Take your time

Generate value

as you go

Think BIG and start SMALL!

…but with progressive scope !

Fast

Low costs

and manageable

impact

Protect investment

Service-

oriented

architecture

New

FunctionalityTechnical Upgrade

� Technical Upgrade: Reduction of Modifications

� Eliminate modification not used: Up to 80% of all modification

� Replace modification with standard functionality: Up to 50% of all modifications

� Technical and functional optimization: Archiving, master date clean-up, interface optimization

� Functional: Focus

� Modernization of the Core SAP ERP, Stabilization of the basis

� Individualization of the user interface

� Strategic: Focus

� Standardization

� Harmonization

� Consolidation


Why Upgrade

Customer Feedback - Main Reasons to Upgrade / not to Upgrade to SAP ECC 6.0

Why not

17%Consolidation of system

landscape

13%Legal compliance

11%Replacement of modifications

6%Others

62%End of standard/

Extended maintenance

42%Use of latest technology

enhancement packages

41%End of old hardware servers

24%Empowering new business

(SOA)

20%Achieve enhance user

experience

Replacing customdevelopment

21%

20%Thorough implementation

of function enhancements

40%Conflicting business

priorities

38%Time and effort to upgrade

27%No business case

25%Lack of project resources

23%Too costly

22%Still receiving maintenance

for current release

17%Do not understand value of

SAP ERP 6.0

13%Higher number of

modifications

9%Other

8%Too much downtime involved

to upgrade

N=1484 N=994The report include answers from the following 360 Upgrade adoption programs: North America (Jan 2008), Brazil (March 2008), Germany (March 2008), Japan (March 2008), UK & Ireland (March 2008), Australia (April 2008), Sweden (April 2008),China (May 2008), India (May 2008) and France (Sept 2008)

� Results of the worldwide customer surveys in 2008 on Upgrade adoption programs


Upgrades to SAP ERP 6.0: Satisfaction with Upgrade Approach

based on 152 upgrades

SAP R/3

Enterprise

SAP R/3

4.6C


� Almost all customers were satisfied or more than satisfied with the upgrade to SAP ECC 6.0

� Source: Customer Experience Database


SAP R/3

Enterprise

SAP R/3

4.6C


Upgrades to SAP ERP 6.0: Approach in Upgrades by Source Release


Definitions:

Technical upgrade

� Limited impact in business processes

� May include the elimination of unused modifications

New functionality

� Technical upgradewith subsequent functional enhancements

Service Oriented Architecture (SOA)

� Technical upgrade with functional enhancements and subsequent SOA adoption

1

2

3

� In most landscapes the upgrade to SAP ERP 6.0 represents the first step to create a stable and

modern core before.

� Most customers follow the recommended tree-step-approach by executing a technical upgrade first

before implementing new functionality delivered with SAP ERP 6.0 and preparing a service-oriented

architecture.


Solution Changes - New 7-2 Maintenance Strategy

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

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.

De

c

Mainstream MaintenanceExtended Maint.

(+ 2%)*

SAP ERP 6.0, SAP

NetWeaver 7.0


(+ 2%)*

SAP CRM 7.0, SAP SCM 7.0, SAP SRM 7.0

Ramp-Up

De

c

Cust.-Spec.Maintenance


Ramp-Up

2011 20122009 2010 20142013 2015 2016 2017200820072006

7 2

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

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

No

v

De

c


(+ 2%)*

SAP ERP 6.0, SAP

NetWeaver 7.0


(+ 2%)*

SAP CRM 7.0, SAP SCM 7.0, SAP SRM 7.0

Ramp-Up

De

c



Ramp-Up

2011 20122009 2010 20142013 2015 2016 2017200820072006

7 2



No

v

Ma

r

Ma

r

Ma

r

Mainstream MaintenanceExt. Maint.

(+ 2%)*

Cust.-Spec.

Maintenance

Ramp-Up


Ext. Maintenance (+ 4%)*

2011 20122009 2010 20142013 2015 2016 2017200820072006

SAP ERP 6.0, SAP NetWeaver 7.0

Ma

r

Ma

r

Ma

r

Ma

r

Ma

r

Ma

r


(+ 2%)*

Cust.-Spec.

Maintenance

Ramp-Up



2011 20122009 2010 20142013 2015 2016 2017200820072006

SAP ERP 6.0, SAP NetWeaver 7.0

� 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 enhancement packages

� Less additional cost for extended maintenance


2011 2012

Solution Changes – SAP Release Strategy

2006 2007 2008 2009 2010

mySAP ERP 2004

SAP R/3 4.6C

SAP ERP 6.0**

Dec

Mar

Dec

Mar

Mar

Mar

2013

Dec

Mar

Ext. Maint. (+ 2%)*


Customer-SpecificMaintenance

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



SAP R/3

Enterprise 47x110, 47x200

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



Ju

n

Dec

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

2014 2015 2016

Cust.-Spec.Maint.

* Overall payment is SAP support fee plus additional fee of 2% or 4% of the maintenance base per year.** SAP ERP 6.0 is the application release formerly known as mySAP ERP 2005.


Dec

Mainstream Maint. Customer-SpecificMaintenance

As of January 01, 2009, extended

maintenance for SAP R/3 4.6C and SAP R/3 Enterprise 4.7 is included

in SAP Enterprise Support and extended by one year

Extended maintenance (no add. fee,included in SAP Enterprise Support contract)

SAP R/3

3.1I – 4.6BExt. M.(+ 4%)*


This strategy is also valid for all industry-specific add-on applications and SAP enhancement packages for SAP ERP based on the releases above.

Extended maintenance (no add. fee,included in SAP Enterprise Support contract)

2017

Dec

Release and maintenance strategy SAP ERP

New 7-2 maintenancestrategy for SAP ERP 6.0:

� According to SAP customer surveys, the SAP release and maintenance strategy is an important

driver for upgrades, particularly, for older releases (see SAP Upgrade Experience Database).

� The above picture shows the current maintenance strategy for SAP ERP. Information for other SAP

products is provided in the SAP Service Marketplace under alias /maintenance.


Summary

Business is the driver for change

� Early involvement and commitment of business

stakeholders is key success factor for every IT change

projects

“

Benefit from SAP enhancement package concept

� improve your TCO and get faster access to innovation“

Every solution is different

� Take the time to analyze your situation and to create your

own solution transition roadmap

“


SAP ERP 6.0 Solution Information –Resources (1/2)

Ac

ce

ss

to

Up

gra

de

in

form

ati

on

Access to upgrade specific informationSAP Upgrade Info Centerhttp://service.sap.com/upgrade

Access to all information/assets concerning the enhancement packages for SAP ERP 6.0

SAP Enhancement

Package Info Centerhttp://service.sap.com/erp-ehp

Access to technical (SDN) and business process information

(BPX), weblogs, forums, and Wiki (login required)SAP Community Network www.sdn.sap.com/irj/sdn

Access to all information/assets regarding SAP ERP 6.0SAP ERP Info Centerhttp://service.sap.com/erp

ERP solution browser tool for SAP ERP 6.0Solution browser toolhttp://erp.fmpmedia.com/

Public websites containing marketing content and high-level

information: http://www.sap.com/solutions/index.epx,

http://www.sap.com/services/programs/erpupgrade/index.epx

www.sap.com: Solutions

www.sap.com: Services


Ac

ce

ss

to

Up

gra

de

In

form

ati

on

Access realization alternatives for SAP Solutions, business

scenarios, and processes

Scenario & Process

Component List

http://service.sap.com/scl

Access to library with complete documentation and

description of the solutions (technical and functional for each

release)

SAP Helphttp://help.sap.com/

Fairy detailed information on news/changes within ECC 6.0

up to EHP3

Release Noteshttp://service.sap.com/releasenotes

High level evaluation of functionalities running best with SAP

ERP 6.0 in terms of ease/speed of implementation and

possible innovation potential

ERP Learning Maps

http://service.sap.com/rkt

Blueprints visualizing how various processes are covered.

Offer drill down from Solution Area/Key Capabilities to

Business processes also providing configuration variants

and partly Business Scenario Maps showing possible value

potential

Solution Mapshttp://service.sap.com/bmet

Access to upgrade related trainings by SAP Education:

http://www.sap.com/services/education/catalog/erp/coursefinder.epxUpgrade Course Finder

SAP ERP 6.0 Solution Information –Resources (2/2)


© SAP 2010

Agenda: Sequence and Major Steps

1. Concept and Architecture2. Sequence and Major Steps

3. Selecting the Target Release 4. Modification Adjustment5. Technical Phases6. Troubleshooting7. Incremental Conversion




Sequence and Major Steps

Contents:� Identify the different types of documentation

� Describe the structure and content of the Upgrade Guide

� Use the Upgrade Guide more effectively


The Main SAP Documentation Types

Implementation

Master Guide

Configuration

DocumentationRelease Notes

Component

Installation Guide

Component

Upgrade Guide

Upgrade Master Guide

Operation Upgrade

Solution Management Guide

Implementation Guide (IMG) Delta and Upgrade IMG

Security Guide

SAP Library

SAPterm� Describes the

upgrade

� Provides you with additional information

� Intended for system administrator with knowledge of:

� Operating system

� Database

� SAP Basis/SAP Web AS/SAP NetWeaver AS

� SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages.

� The SAP Library is a collection of function- and process-oriented docu for SAP components.

� The Implementation Guide (IMG) is a tool for configuring the SAP system to meet customer

requirements. Its structure and documentation are component-oriented.

� The Security Guide describes the settings for a medium security level.

� The Master Guide is the starting point for implementing an SAP solution. It lists the required SAP

components, and third-party applications that are required for each Business Scenario.

� The Component Installation Guide describes the technical implementation of an SAP component.

� The Configuration Documentation in SAP Solution Manager is a tool with various functions, one of

its main functions being the configuration of SAP solutions and Business Scenarios.

� The Solution Management Guide is the starting point for operating an SAP solution. The guide refers

users to the tools and documentation that are needed to carry out various tasks, such as monitoring,

backup / restore, master data maintenance, transports, and tests.

� Upgrade Master Guide is the starting point for upgrading the Business Scenarios of an SAP solution.

It provides scenario-specific descriptions of preparation, execution, and follow-up.

� The Component Upgrade Guide describes the technical upgrade of an SAP component.

� Release Notes are documents that contain short descriptions of new features or changes in an SAP

component since the previous release.


The Upgrade Documentation:Upgrade Guide + Troubleshooting and Admin.


© SAP 2010

The five major Technical Steps

SAP Notes: post Upgrade steps

Upgrade Guide: post Upgrade steps

ASU Toolbox: post upgrade 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 Upgrade Guide

SAP Note 1000009

Roadmap steps 1 - 4

Roadmap steps 5 - 8

See Upgrade Guide

SAP Note 1000009

Solution Manager: select target release

SAP Notes: pre Upgrade steps

Upgrade Guide: pre Upgrade steps

ASU Toolbox: pre Upgrade steps

SAPup: preparational steps

SAPup: resolving negative checks

SAPup: Upgrade

� The technical upgrade procedure can be described with these five major steps. The slides of this

chapter refer to these steps.


Upgrade Guide + Troubleshooting and Administration

Upgrade Guide 1.3.3 SAP Notes for the Upgrade

Troubleshooting and

Administration

2 Quick Guide

3 Planning

4 Preparation

5 Upgrade Process

6 Follow-Up Activities

2 Troubleshooting

3 Administration

2

3

4

5(part of)

(part of)

1(part of)


Upgrade: Quick Guide

Step by step list to perform the Upgrade

(Extract)

2

3

4

5(part of)

(part of)

1(part of)


Upgrade Tools with SAP NetWeaver AS 7.02

SAP Software Delivery Tool (SDL)

UpgradeMonitor

� 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 upgrade by providing a multi-functional user interface

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

SAPupUpgrade

ControllerUpgrade

Front-end

3

4

� The SAPup is the main Upgrade tool. Starting with Upgrades to SAP ECC 6.04 it includes the

functionality of the former PREPARE and the steps of the actual Upgrade process.

Starting with Upgrades to SAP ECC 6.04 also a new design is introduced.

� The Upgrade Assistant is a graphic-based tool which has been available since upgrades to SAP R/3

4.6.

� The Upgrade Monitor is a feature of the Upgrade Assistant.

� With upgrades to AS ABAP 7.01 the Upgrade Assistant has a new look and feel.

� The Upgrade Monitor has a new design and no more progress bar for the running phase starting with

upgrades to AS ABAP 7.01.


SAPup / SAPJup

� Standard SAP upgrade tool for ABAP and Java

� Execution of main upgrade activities

� For an ABAP system you require SAPup; for a

Java system you require SAPJup.

� The tools share a similar architecture � consist

of an upgrade program (SAPup or SAPJup) and

a control program (Upgrade GUI or SDT GUI).

� New upgrade GUI layout and simplified upgrade

procedure for AS ABAP 7.01, AS Java 7.1 and

AS ABAP+Java 7.1 ('dual stack') upgrades

� Established system switch upgrade technology

is also available for AS Java 7.1 and AS

ABAP+Java 7.1 ('dual stack') upgrades

� Synchronized upgrade procedure for

ABAP+Java 7.0 ('dual stack') upgrades

DESCRIPTION

BENEFITS

� SAPup and SAPJup are part of the upgrade

software kit shipped by SAP

� More Information is available on SDN:

http://sdn.sap.com/irj/sdn/upgradetech

ACCESS

3

4


Central Instance host

Upgrade Tools: Upgrade Front-end

Remote client hostUpgrade Upgrade Controller

Port 4240

Port 4239HTTP

Port 4241

3

4


Upgrade Controller

directly starts

3

4

� 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


Upgrade Front-end (1)

� New setup

with upgrade

to AS ABAP/AS

Java 7.01

3

4

� Start the Upgrade 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 UA client GUI starts after the download of the client application code is complete.


Upgrade Front-end (2)

� New design with

upgrade to AS

ABAP/AS Java 7.01

3

4

� 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


Upgrade Front-end: Input Window

� New look and feel

with upgrade to AS

ABAP/AS Java 7.01

� New feature:

download directory

3

4

� The Upgrade Front-end input window has a new look and feel with upgrades to AS ABAP/AS Java

7.01

� It is now possible to provide a central download directory for all patches and files that should be

bound to the upgrade


Upgrade Front-end: Upgrade Monitor

Informs the administrator about

� Progress of current roadmap step

� Status of current phase

� New look and feel

with upgrade to AS

ABAP/AS Java 7.01

3

4

� The Upgrade Monitor has a new look and feel with upgrades to AS ABAP/AS Java 7.01


Upgrade Front-end: Upgrade Documentation

� New access to information

with upgrade to AS ABAP 7.01

3

4

� There is a new access to information with upgrades to AS ABAP 7.01


Upgrade Front-end: Upgrade Phase List

� New phase list design with

upgrade to AS ABAP 7.01

3

4

� There is a new Phase List design with upgrades to AS APAB 7.01.

� Besides others this new phase list takes into account, that there is no separation between PREPARE

and Upgrade anymore.


ASU Toolbox – Management Tool for Manual Follow-up Activities

� Guidance for manual steps

� Benefit: Reduction of runtime and downtime

(part of) 5

� Delivered with ST-PI

� Must be started manually /ASU/UPGRADE

� Preparation phase: REQ_PRE_ASU_RUN

� Downtime phase: REQ_POST_ASU_RUN

� See SAP Note 1000009


© SAP 2010

Agenda: Selecting the Target Release

1. Concept and Architecture2. Sequence and Major Steps3. Selecting the Target Release

4. Modification Adjustment5. Technical Phases6. Troubleshooting7. Incremental Conversion




Selecting the Target Release

Contents:� Create Solution Manager key with the SAP Solution Manager

� Create XML/TXT files for the upgrade with the Maintenance Optimizer


Select the Target Release of the Upgrade with SAP Solution Manager

How is this stack file created?

� A properly installed Solution Manager system is required to generate the xml and txt file to bind an

individual selection on SAP Enhancement Package 5 for SAP ERP 6.0 components to the upgrade.

� This step is mandatory for the 6.04 upgrade!


Generation of Stack Configuration File:Initial Setup

SOLUTION_MANAGER:

assign system via

logical component

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.


Generation of Stack Configuration File:Create Maintenance Transaction

1. Enter description

2. Choose product version

3. Choose system(s)

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


Generation of Stack Configuration File:Choose Scenario 'Upgrade'

1. Calculate files automatically

2. Upgrade

� Choose 'upgrade' (this feature only exists if the Solution Manager system has the required SAP

Support Package level - for details see upgrade guide)

� Find download files.


Generation of Stack Configuration File:Select Technical Usages

1. 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.

� Find download files for the stack version (minimum for the upgrade: SAP Support Package stack 2 -

recommendation: use the latest!)


Generation of Stack Configuration File:Select Operating System

1. select operating system and database

2. …

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 and txt File to Upgrade

Copy the txt file,

so it can be accessed by the Upgrade

� The xml and txt files are generated in the transport directory of the Solution Manager system,

subdirectory EPS\in.

� Copy them so they are accessible by the upgrade.


© SAP 2010

Agenda: Modification Adjustment

1. Concept and Architecture2. Sequence and Major Steps3. Selecting the Target Release 4. Modification Adjustment

5. Technical Phases6. Troubleshooting7. Incremental Conversion




Modification Adjustment

Contents:� Basic ideas of SPDD and SPAU/SPAU_ENH

� Changing the SAP standard

� Preparing the modification adjustment

� Adjusting follow up systems in the landscape

� Handling transport requests for modifications


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 adjustment� Manually implemented advanced correction in accordance with a SAP Note

� Adjustments 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 release

� SAP Support Packageswill be part of the new release or an SAP Support Packages of the new release

� Add-onswill be part of the new release (Extension Set) or need an upgrade DVD


E070C11K900001

SAPK01384COMMFILEC11K900004

E071C11K900001

C11K900004C11K900001C11K900001

LIMU REPS RSPUTPRT

R3TR PROG RDDFINFOR3TR TABL GODIRLIMU DOMD RESULT

C11K900001

C11K900004

...

List of customer

requests and tasks

{{... ...

resolve

single

objects

LIMU REPS RSPUTPRTLIMU REPS RDDFINFOLIMU DYNP RDDFINFO1000

LIMU DOMD RESULT...

List of modified part objects‘Back to SAP standard’

X

Object key

LIMU TABD GODIR XObjects

modified by

customer

TODIR SPDD

SPAU/SPAU_ENH

UMODOBJ UMODHDR

Objects modified

by SAP

that come with

new release

Calculation of Modified Objects to be Adjusted

� Without modification adjustment, you would lose all modifications you made to objects that conflict

with SAP modifications when you upgrade the system. The modification adjustment lets you make

your modifications to the appropriate new objects in the upgrade.

� You can identify modifications as repairs to the SAP standard or as imports of SAP objects. Requests

in the customer namespace (number range 900000 to 9ZZZZZ) “modify” the SAP objects included

in them. All other requests are dealt with as preliminary corrections.

� The ABAP Dictionary objects (tables, data elements, domains, and so on) can be adjusted during

productive operation before the activation of the ABAP Dictionary. The adjusted objects are

collected in a repair that is released to a transport request. You should not release this transport

request; instead it must be flagged for export in transaction SPDD. Towards the end of the upgrade,

SAPup exports this transport request into the transport directory /usr/sap/trans and then registers it

for transport in the file umodauto.lst.

� Repository objects (reports, screens, and so on) are adjusted toward the end of the upgrade, during

downtime. At this stage, the import of SAP objects has already been completed. However, the old,

modified version is still available in the versions database. As with ABAP Dictionary objects, all

adjustments are released to a transport request that is noted and then exported and registered by

SAPup.


Upgrade System Landscape

system active

system active

system down

Switch

Production

SPDD

SPAU

SPAU_ENH

Import

bin/umodauto.lst

data/R...

cofiles/K..

buffer/SAP

Integration of the

created transport

requests into

the upgrade

Switch

Production

SPDD

SPAU

SPAU_ENH

Import

Transport

Directory

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

upgrade

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.


SPDD

SPDD provides the following functions:

Display

Comparing old and new versions

Maintenance

Reset to original

Marking objects as processed

Refresh

Marking for transport

� Display: Within individual packages or corrections, the objects are displayed according to type. To

view a changed object, select it with a double-click. You are automatically shown an overview of all

existing versions of the selected object.

� Comparing old and new versions: Selecting an individual object lets you view all existing versions of

the object stored in version management. The display is the same as the one with which you are

presented when you compare two objects in version management. The information reflects the status

of the objects after their activation. For example, a comment in a table field indicating deletion

means that the field will be deleted after activation, provided no maintenance is carried out

beforehand.

� Maintenance: Transaction SPDD lets you compare the most important attributes of old (modified)

and new (SAP standard) versions of domains and data elements. This helps you to decide how to

proceed. Perform the adjustments required in transaction SE11, preferably in a second window.

� Reset to original: If, after comparing the results of the analysis, you conclude that you do not wish to

retain previous modifications, choose Reset to original for the object in question. For example, you

may need this function if you have patched an object by hand. When SAP delivers the same patch

together with other corrections in the next upgrade, you can return to the SAP standard because you

no longer need your own modification.

� Marking objects as processed: To facilitate work with the generated object list, you can assign the

status Completed to each object. Selecting the function changes the status of the object and indicates

this by highlighting it with a different color. The completed flag is meant only to assist you in

organizing your work and has no other internal function.

� Marking for Transport: The Select for transport function helps you to adjust other SAP systems.


SPAU

� Automatic adjustment

� Semi-automatic adjustment

� Manual adjustment

� Unknown adjustment mode

� Reset to original

� Automatic adjustment: Customer modification can be automatically adopted. Clicking on the icon

causes the system to automatically adjust the object (only With Modification Assistant category).

� Semi-automatic adjustment: Semi-automatic means that each tool will individually offer you support

during the adjustment process. When adjusting programs, the split-screen editor is called, whereas in

the other tools any entries made in the collision dialog box lead to the necessary adjustments being

made automatically. As with the green traffic light, the semi-automatic adjustment icon only appears

in the With Modification Assistant category.

� Manual adjustment: Objects in the Without Modification Assistant sub-tree can only be post-

processed manually after the adjustment process. Manual adjustment means that you must make

modifications without any special support from the system. Use the log as a help. Using Version

Management, you can retrieve old versions or use your recordings to process the newly imported

objects. In rare cases, the red traffic light may also appear in the With Modification Assistant

category.

� Unknown adjustment mode: The adjustment mode (manual, semi-automatic, automatic) for at least

one of the objects in question could not be determined for modification adjustment with the

Modification Assistant. If this is the case and you start transaction SPAU, a dialog box informs you

that you can start a background process by choosing the appropriate button, which determines the

adjustment modes for all objects.

� Reset to original: If you choose Reset to original for an object displayed in the overview, no

modifications are adopted for this object. The original is the version that was last imported into the

SAP R/3/ECC system during the upgrade or an SAP Support Package.


SPAU_ENH

� Automatic adjustment

� Tool-supported adjustment

� Manual adjustment

� Semantic change

NavigationArea

ToolArea

Object List Selector

� All enhancements that you have to adjust are shown in transaction SPAU_ENH. In contrast to

modifications of source code units, you only have to adjust enhancements if the underlying SAP

development objects were deleted or changed in an incompatible way.

� For the quality assurance and production system, we recommend that instead of adjusting

modifications and enhancements manually, you automatically transfer the transport requests

exported from the first system: one for the ABAP Dictionary objects adjusted using transaction

SPDD and one for the Repository objects adjusted using transactions SPAU and SPAU_ENH.

� If you have implemented enhancement framework options of the new Enhancement Framework or

implemented a new kernel-based BAdI (also part of the new Enhancement Framework), and the

underlying development objects have changed in an incompatible way, you must adjust these objects

in transaction SPAU_ENH.

� The enhancement framework does not support modifying enhancement definitions or enhancement

implementations. In some cases you can, however, replace enhancement implementations of a higher

layer with your own enhancement implementations.


� Create one new transportrequest for SPDD and one for SPAU/SPAU_ENH

� Transport routes:Local or transportable transport request

� Only release tasks after modificationadjustment, do not release the transport request now

� Select for transport function in SPDD and SPAU

Handling Transport Requests During Adjustment

� The configuration of the transport routes in the SAP system determines whether changes to objects

during modification adjustment are recorded in a local or transportable transport request. You cannot

and must not change these settings during the upgrade. In all cases, the transport request can still be

used for automatically transferring modifications to a subsequent system. For this procedure, the

transport requests are not released in the normal way, but handled specially.

� Do not change the configuration of the transport routes in your system group during the upgrade.

� When modification adjustment has been completed, release your tasks. The tasks are the repairs

and/or corrections that were automatically assigned to you when the transport request was created.

Do not release the transport request at this point if you want to use it to automatically transfer the

modification adjustments to subsequent systems.

� During the adjustment of the ABAP Dictionary objects, releasing requests is locked until the edited

objects have been activated. Do not release these requests until after the upgrade.

� To automatically transfer modifications to a subsequent system when you have completed

modification adjustment, use the Select for transport function in SPDD or SPAU.

� If your modifications are recorded in several transport requests, you first have to place all entries in a

single request. Several requests cannot be marked for transport.


Transport Requests: Notes

Use the Modification Browser (SE95) for analysison modified objects (if available)

Analysis report Search for objects in requests/tasksin transaction SE03 can be used to check whetherthe objects modified are recorded in repairs

Objects that have been modified and differ from theSAP standard must be included in a repair

Be

fore

th

e U

pg

rad

e:

Du

rin

g t

he

Ad

jus

tmen

t:

The Reset to Original function should be used for objects with no differences.

Also for objects where last and second to lastversions were created by user SAP (R3trans)

� Before the upgrade:

� Check whether the objects you modified are recorded in repairs. To do this, you can use

transaction SE95 and search for objects in requests/tasks in transaction SE03.

� No repairs or customer transports are displayed by the Transport Organizer (SE01) and the

Workbench Organizer (SE09), although you know that objects have been modified in the SAP

system. Indicate the objects that have been modified and differ from the SAP standard by

including them in a repair and subsequently releasing it.

� During the adjustment:

� No differences are found when you compare the second-to-last and third-to-last versions:

During the last upgrade you did not perform adjustments to retain changes you had made to

objects. Indicate that modifications to these objects are no longer needed with the Reset to

original function.

� The last and second-to-last versions were created by user SAP (R3trans):

During the last upgrade you did not perform adjustments to retain changes you had made to

objects. Indicate that modifications to these objects are no longer needed with the Reset to

original function.


Transaction SPDD

� Domains

� Data elements

� Tables

Transaction SPAU

Different modified

objects require

different

transactions

for modification

adjustment

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.


© SAP 2010

Agenda: Technical Phases

1. Concept and Architecture2. Sequence and Major Steps3. Selecting the Target Release 4. Modification Adjustment5. Technical Phases

6. Troubleshooting7. Incremental Conversion




Technical Phases

Contents:� Overview of the major steps of the upgrade

� Most important phases of the upgrade


New Upgrade Interface


Resource Consumption of the Upgrade

Downtime minimized

Resource minimized

� New with upgrade to AS ABAP 7.01

� 'Low recourse use' triggers 'Resource minimized'

� 'Standard' and 'High resource use' trigger 'Downtime minimized'


Overview

DB and upgrade directory

must be restorable to state at end of production!


SAPGUI

� Be sure to have a suitable SAPGUI in place when needed:

� The end users need a suitable SAPGUI when productive operations is started in the upgraded

productive system.

� The users from the departments involved in the upgrade project need a suitable SAPGUI at the end

of the upgrade of the sandbox system.

� Developers involved in the upgrade project need a suitable SAPGUI starting from SPDD

modification adjustment in the sandbox system.

� The administrators involved in the upgrade project need a suitable SAPGUI starting from the begin

of the upgrade project.


Important Phases of the Upgrade

EU

_IM

PO

RT

*

DIF

FE

XP

*

Tra

nsac

tion

SP

DD

AC

T_U

PG

PA

RD

IST

_SH

D

MO

DP

RO

F_T

RA

NS

EU

_SW

ITC

H

PA

RC

ON

V_U

PG

PM

VN

TA

B_U

PG

TA

BIM

*

XP

RA

S*

SH

AD

OW

_IM

PO

RT

*

RU

N_R

DD

IT00

6

DIF

FE

XP

*I

Tra

nsac

tion

ICN

V

Man

ual a

ctio

ns

PR

D: d

elta

tran

spor

ts

App

ly S

AP

not

es

� EU_IMPORT* Copies substitution set from Upgrade CD to the shadow tables

� RDDIT006 Determines deviations of the current system from the future standard SAP system

(objects and modifications that need to be copied)

� DIFFEXP* Exports objects not stored in shadow tables: Add-on objects, SAP Support Package

objects, generated objects, unsent modified objects, customer developments, customer extensions to

SAP object documentation, documentation for customer objects, local private objects and test objects

in the SAP name range

� ACT_UPG Activates all ABAP dictionary objects, that are not part of the standard upgrade DVDs

� PARDIST_SHD Starts distributor

� DIFFEXP*I Import of objects into shadow repository exported by DIFFEXP*

� SHADOW_IMPORT* 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(Example: 4.6C Start Release)

Application data

customizing data

user master data

(Application data)customizing datauser master data

Add. application data

add customizing data

(imported after ACT)

SA

PR

3

SA

PR

3SH

D

Repository

4.6C/4.6C

Shadow repository

7.02/6.05

Repository

7.02

Productive instance

4.6D

Shadow instance

7.02

Productive instance

4.6D

Productive system 4.6C/4.6C

Shadow repository 7.02/6.05

Shadow system7.02

Accesses

...

DB

� At the most, there are three repositories active at the same time:

� the old repository

� the shadow repository (which will be the new productive repository at the end of the upgrade)

� the repository of the shadow system.


Operation of Shadow System

Phase START_SHDI_FIRST

� Start shadow instance for the first time

Batch jobs on shadow instance

� Versioning preparations

SPDD

� Modification adjustments on shadow instance

Activation: Phase ACT_UPG

� Parallel activation on shadow instance

Distribution: Phase PARDIST_SHD

� Parallel distribution on shadow instance

Phase STOP_SHDI_LAST

� Stop shadow instance finally

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


Danger

Connect to shadow system:

�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 SAPup with this setting could damage the system!

D A N G E R !


Upgrade of AS Java based SAP System: Prerequisites

� Source system prepared for the deployment of Adobe Document Service (ADS) if ADS not installed yet. Refer to Java Upgrade Guide

� JDK version, refer to SAP Note 709140

� JCE requirement, refer to SAP Note 865166: Only required if the source system uses stronger encryption and a new JDK version is installed

� SAP Support Package level of the source system

� Web AS: 6.40 SP09

� SDM version > 6.40 SP13

� The application components must be:

� EP: 6.0_640 SP09

� XI: 3.0 SP09

� BI-Java: 3.5 SP09

� ADS: 1.0 SP09

� KW IKS: 1.0 SP09

� ADS becomes an integral part of the NW 7.0 Application Server. It will be deployed in the target

system regardless whether it is installed in the start release.

� Including the latest SAP Support Package Stack

� Preserve Customer Data

� Migrate J2EE Engine configurations

� Preserve application data and configurations

� Upgrade Modified Components

� Archives containing new releases of modified and third-party components can be selected and

deployed by SAPJup


Deployment-Based Upgrade

2004

Applications

Binaries

Profiles & scripts

J2EE Engine Components

7.02

Applications

Binaries

Profiles & scripts

J2EE Engine Components

SAPJup

Configure

Adapt

Adapt

Migrate

Migrate

Deploy

Deploy

� Preparation steps are performed during the system uptime

� The PREPARE phases include following major tasks:

� Investigating the source system

� Performing various parameter and profile checks

� Determining Usages Types to be upgraded

� Extracting upgrade DVDs

� Including SAP Support Packages

� Including custom development components

� Calculating the deployment lists and order

� Additional instances (non-central instances) have to be re-installed using SAPinst.


Uptime and Downtime

Upgrade Uptime

� Uptime is the time when the J2EE Engine is up and running. It’s still productive, in use and untouched by the upgrade procedure

� Whole Prepare unit runs in Uptime

� Reconfiguring J2EE Engine is not allowed during the Uptime

� Upgrade can be stopped and cancelled during the Uptime

Upgrade downtime

� Downtime is the time when the J2EE Engine is being modified and controlled by the upgrade procedure

� The system is not productive

� Even when system is up – it can’t be used. Upgrade starts the J2EE Engine in SAFE mode during DEPLOY_ONLINE and RUN_APPLICATION_MIGRATION phases.

� The only active user is SAP* and it should not be changed during the downtime

� The UPGRAGE phases are mainly performed during the downtime.

� It includes following major steps:

� Stopping the system

� Disabling the current user store of the UME to ensure that SAP* is the only user who can access

the system during the downtime

� Updating the kernel, SAP MMC (Windows only), IGS and SDM

� Undeploying and deploying SLOT1 (file system deployment)

� Undeploying and deploying SLOT2 (database deployment)

� Updating the engine bootstrap and adapting profiles

� Undeploying and deploying SLOT3 (offline deployment)

� Migrating engine core data (Java Migration Toolkit)

� Starting the system in Safe mode

� Undeploying and deploying SLOT4 (online deployment)

� Running application migration (application migration container)

� Stopping the system

� Re-enabling the original user store of the UME

� Starting the system


Upgrade of AS ABAP+Java System(Dual Stack)

Synchronization points at

� Begin of downtime

� End of downtime

Synchronized upgrade of

� ABAP stack and

� Java stack

� Reduce the overall downtime: Both stacks start and end the downtime phases at same time

� Handle common resources correctly: for instance, system profiles and profile entries are shared by

ABAP and Java stack

� Upgrading (PREPARE and UPGRADE) ABAP and Java stack must be performed in parallel with

following sync points:

� At the beginning of the downtime

� When the profiles are going to be modified

� At the end of the downtime

� Except for the sync points, the upgrade processes of both stacks are performed independently

� The vast majority of the Java upgrade takes place during the downtime


© SAP 2010

Agenda: Troubleshooting

1. Concept and Architecture2. Sequence and Major Steps3. Selecting the Target Release 4. Modification Adjustment5. Technical Phases6. Troubleshooting

7. Incremental Conversion




Troubleshooting

Contents:� Monitoring upgrade activity

� Troubleshooting within job phases, transport phases, bulk import phases

� Log file analysis


tp

R3load

SAP system

Start

User Interface

User interaction &

SAPup output

DB

Main Programs Tools Used During Upgrade

SAPup

Overview: Upgrade Executables

� The user interface is described in the Upgrade Manual.

� The version of most SAP executables can be determined with the option -V.

For those tools which connect to the database, a value in the DB library line indicates that the

corresponding DB library can be loaded.

� The Upgrade Assistant GUI does not require a permanent connection to the server.


Overview: Monitoring Upgrade Activity

Upgrade Assistant Monitor

� Current phase, estimated runtime

Operating System

� CPU activity (UNIX: top, Win: Task Manager)

� Active processes (UNIX: ps, Win: pstat)

� Current log files in DIR_PUT/tmp

SAP System

� SM50 Work process overview

� SM37 Active background jobs

� You can use the above tools to see the upgrade activity.

� If input is required, the upgrade will stop. A file, upalert.log, is then written to <upgrade

directory>\abap\tmp.


Overview: When the Upgrade Stops

Upgrade

Stop

In the SAP System (if it runs):

� SM21 system log

� SM37 job logs of finished

or canceled jobs

� ST11 trace files

� ST22 short dumps

Determine the current phase,

check the log file mentioned

in the phase list for this phase.

Check the most recently writtenlog files in <upgrade directory>\abap\logand <upgrade directory>\abap\tmp.

Read message from SAPup

For the database,

check the database alert file.

� These steps should be processed to find what caused the upgrade to stop.

The current phase is the last in SAPup.log.

� Additional logs can be created in transactions SM21 and SM37 for activities inside the SAP system.

� The database alert file can contain special DB-related errors such as archiver stuck.


Overview: Phases

JOB_ or RUN_ phases: SAPup starts a background

job or a function module

in the SAP System

Bulk import phases: SAPup starts R3load to import

new data (full)

SAPup starts tp to do one of the following:

� tp connects to the database and

executes an SQL script

� tp starts R3trans. R3trans connects

to the DB and imports/changes data

� tp starts sapevt. sapevt sends an event. RDDIMDP

runs once, transport steps are processed in the background

Transport phases:

� An upgrade to SAP ECC 6.0 contains several hundred different phases. Most of the phases fit into

one of three described classes.

� SAPup itself cannot connect to the database. To read or change information in a database table,

SAPup needs a tool that can access the database. In each of the three classes, SAPup chooses

different tools. Details of these classes are described on the following pages.

� During upgrade phases with names like JOB_ or RUN_ , SAPup starts a function module in the

system using RFC to schedule and start a background job. After the job had finished, the result is

evaluated from the log file.

� Phases with names such as TABIM, TABUIMP, VIEWIMP, PORT_IMP, TOOLIMP and so on are

classical import phases. tp starts R3trans, R3trans imports data.

Phases like DIFFEXP or SHADOW_IMPORT are similar phases, except that R3trans imports into

the shadow tables.

� The EU_IMPORT phases are the bulk import phases during which the new Repository is imported

into the shadow tables invisible to the production SAP System.

Most of the data in the Repository is not unique to the system, therefore an exchange is more

efficient than a import of the delta. In contrast, customizing is unique to each system, and therefore

only the delta is imported.


Function module

Database

Schedules

Within SAP system

Job

External programs

Job Phases: Control Flow

Read & Write

Write

SAPup

Log Files in

<upgrade directory>\abap\log

RFC

� SAPup starts a function module in the SAP system as user DDIC in client 000

(SUBST_START_BATCHJOB).

� This function schedules a background job for the phase.

� SAPup regularly checks the status of this job with a new RFC call (SUBST_CHECK_BATCHJOB),

until the job has finished.

� The log file written by the job in <upgrade directory>\abap\tmp is analyzed and evaluated by SAPup.


Job Phases: Log Files

Example for phase RUN_RDDIT006:

� DIFFCALC.LOG RFC logon

� CUSTEXP.<SID> Log file of background Job RDDIT006

� DIFFCALC.ELG Condensed errors from CUSTEXP.<SID>

� (DIFFCALC.SAV) .LOG and .ELG from previous runs.

During a JOB phase, the following kind of log files are written:

<name>.LOG RFC login, start and check a

background job <name>

<name>.<SID> Where <name> is not a transport log file,

it can be the log file of a background job

<name>.ELG Errors collected from the previous log

<name>.SAV .LOG and .ELG from previous runs

� The first RFC phase is RFCCHK_INI in PREPARE. Only the RFC logon is performed during this

phase, and no background jobs are started (RFCCHK_INI.LOG).

� The check of the background job functionality is made during BATCHCHK phases (for example,

BATCHCHK_IMP.LOG).


Write R3trans

Data file

DatabaseLog Files


Start

Import

Read

Transport Phases: Control Flow (TABIM)

Start

Write

Read & Write

tpSAPup

� This is also valid for TOOLIMP, DIFFEXP*, and other import phases.

� During the DIFFEXP* phases, R3trans reads from the source release tables and writes into the target

release tables (copy to shadow).

� SAPup evaluates a direct return code from the tools (finished) and evaluates an indirect return code

from the written log files.


sapevt

Schedules

Jobs within

SAP systemExternal programs

Transport Phases: Control Flow (ACT, XPRA)

Read & Write

Write

Log Files in


Start

Write

StartSAPup tp

RDDIMPDP

Database

RDD*

Trigger

� Instead of R3trans, a transport background job might also be started for actions such as activation.

� The start of RDDIMPDP works differently from the start of a job during a JOB phase.

� PARCONV (parallel conversion) is similar to this, but SAPup starts the transport background jobs

(distribution, conversion) itself, and in parallel. After distribution, an additional check is made for

lost fields (FDSAVPROT). SAPup then starts tp only for movenametab (PMVNTAB, execution of

DDLs).


Transport Phases: Log Files

SAPup calls tp with a special transport profile (TPPARAM/TP<Domain>.PFL)

SAPup log files

� TP.ECO or R3up.ECO stdout of tp� *.ELG Collected error lines from transport logs

tp log files

� ULOG... tp call inclusive used transport profile� ALOG<rel> Finished steps (request, return code)� SLOG<rel> Details of tp call

R3trans log files

� SAPI* (Main) Import logs� SAPH* Dictionary import logs

Transport background jobs log files

� SAPA* Activation logs� DS<nnnnnn> Distribution� N<nnnnnn> or Conversion

NCONV<nn>

� The special upgrade log files are .ECOs for standard output and .ELGs, where errors from other log

files are collected. A line in a transport log is transferred if it contains an E in the second column.

� The log files for tp differ only in the naming from the usual transport log files.

� Additional PCON log files are:

� FDSAVPRT.<SID> Check for lost fields

� PA<date>.<SID> Only nametab activated

� PD<date>.<SID> Activate and alter table (add field or similar)

� PL<date>.<SID> Delete table and remove nametab


Transport Phases: Strategy for Problems

Did a tool

write an error

message into its log file?

(Check the

.ELG File)

No (that is, ELG of transport phase does not contain error lines):

Check if tp finished correctly (ECO File).

Check log files written by tp for errors (especially SLOG)

� R3trans import:

In most cases during import phases,

errors are related to DB problems and a DB

error message is found in the import log.

� Activation error:Check the object in transaction SE11.

� XPRA error or short dump:

Check the report documentation of the XPRA

Yes (that is, an error line appears in ELG):

check the corresponding original log file

mentioned in the ELG.

Yes

No

� Activation errors should be resolved or classified as non-critical. Otherwise, there is a chance that

data in PARCONV will be lost.

� In ACT, TABIM and XPRA, a return code of 8 means that individual objects were not processed

successfully. You could repeat the phase at your own risk with repair severe errors. If you do this,

then only return codes larger than 8 will stop the phase.

� Check for lost fields fails in PARCONV :

Verify that this is correct (SAP Note). Data might be lost if the phase is repeated with Do not repeat

checks.


Database

SAPup

R3loadData file from DVD

Bulk Import Phases: Control Flow

Start

Read & Write

WriteImport

Read

Log Files in


SAPup starts R3load for each data package EX<nnnnn>.

� EX<nnnnn>.DPR is the import log file,

� EX<nnnnn>.DST is the statistics log file.

� Depending on your upgrade strategy (downtime minimized, resource minimized and sub-strategies):

� If the system is productive during EU_IMPORT phases, you can slow down the R3load process

so that the performance of the SAP system is not affected.

� If the system is not productive during EU_IMPORT, the SAP system is shut down during

EU_IMPORT and several parallel R3load processes are started.

� The statistics log file contains only the number of imported bytes and the total number of bytes in

this data package.

� The restart of an EU_IMPORT phase with init first removes all previously imported tables and then

starts R3load to import all tables again.

� The restart of an EU_IMPORT phase with repeat just starts R3load to restart from the point where

the error occurred.

� Duplicate keys during the creation of a index are caused by CD read problems. The recommended

solution is init of the phase with the DVD copied to disk.


Transaction SE91 can be used to display the long texts of error messages. (>long text >document >screen)

Example

A line in a log file starting, for example, with

2EETG779 ....means:

Severity 2 (Level of log file display in SE09),Error,

English,

Message class TG,

Message 779.

SAPup checks the log file for errors (E in the second column) and copies these lines into an .ELG file. The number of errors in one phase is equal to the number of lines copied into the .ELG.

Log File Analysis

� SE91 can also be used to identify the development class of the message. The development class has a

component assigned. Especially for XPRAs, the customer message can be opened directly on this

component.


Access to Troubleshooting Guide


SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R/3 System BC-UPG

R/3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Management:� Communication Station and Mobile Development Workstation� CRM Server� Internet Pricing and Configurator (IPC)� Mobile Client Component� SAP R/3, SAP R/3 Enterprise, SAP ECC

� CRM-MW� BC-MID-INT-SRV� CRM-MT-IU-SPE� CRM-WBT-IU� BC-UPG

SAP TREX Search Engine (SAP DrFuzzy Search Engine) BC-SRV-TRX

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

Providing SAP Support with Information

� If you encounter problems that are specific to the upgrade, create an error message in SAP Support

Portal (http://service.sap.com/support) and assign it to component BC-UPG. Answer the following

questions and put these answers in your customer message:

� For which SAP component do you want to perform the upgrade?

� Which release are you upgrading from? Which release are you upgrading to?

� Which operating system version are you using?

� What was the original release of your SAP system?

� In which upgrade program phase does the error occur?

� This information is listed at the end of the SAPup.log file located in the upgrade directory.

� Did you have problems with the SAP system before upgrading?

� In any case you should send the troubleshooting ticket file created by SAPup to SAP!


Recommendations

� Test upgrade: Problems can be localized and analyzed to avoid them during the production upgrade.

� Ignore a phase: The upgrade was tested at SAP and should work without ignoring any phases with a password. In general this leads to more problems in later phases.Distinguish between an ‘Ignore’ that requires a password and an ‘Ignore’ without a password!

� Backup: In case the upgrade cannot be finished, ensure that you have made matching backups of the database and of the upgrade directory!

� During a test upgrade, problems can be localized and analyzed, so that they can be avoided during

the production upgrade.

� The upgrade was tested at SAP and should work without ignoring any phases. To ignore a phase

with a password will, in general, lead to more problems in later phases, Therefore passwords are

given only by SAP support.

� In the very rare case that the upgrade cannot be finished, ensure that you have made a backup of the

database and of DIR_PUT as described in the Component Upgrade Guide. The database and the

upgrade directory must have a matching state.


© SAP 2010

Agenda: Incremental Conversion





Incremental Conversion

Contents:� Early incremental table conversion (ICNV) during an upgrade to a system

based on AS ABAP 6.x/7.x

� Description of the conversion procedure


Goals of Early ICNV

Reduction of upgrade downtime

� Large tables are now converted during uptime

� Only switch to new structure during downtime(in PARCONV)

Easy handling

� Fully integrated into upgrade process

Configurable conversion process

� Exclusion times

� Progress prediction

Early ICNV is not available when using low resource use!

� The main goal of the ICNV is to reduce the downtime during an upgrade.

� The procedure should not be too complicated and it should be fully integrated into the upgrade

process.

� The conversion process is executed during uptime. The database load is expected to be higher during

this process; therefore, it is possible to define exclusion times during which no ICNV processes are

running.

� The administrator should be informed about the estimated end of the process to be able to plan the

upgrade accurately.


Table T1

Table QCMT1

(New structure)

Rename (2)

View T1

Create (4)

Create (1)

Create

(5)

Update

trigger

Delete

triggerCreate (6)

Add

Field

(3)

Overview

Table QCM1T1

� Here is the sequence of steps during an incremental table conversion:

� The conversion table candidates are selected.

� (1) A QCM table with a new structure is created.

� (2) The table T1 is renamed to QCM1T1.

� (3) An additional status field is added to QCM1T1.

� (4) A view on the old table structure is created. The applications access the view from now on.

To log these changes the update (5) and the delete (6) trigger is needed

� The table content is copied (low priority copy) to the shadow table QCMT1.

� QCMT1 is filled by periodic runs

� At beginning of downtime, only a few conversions should remain. The downtime due to table

conversion is significantly reduced.


Active table (QCM1T1) Shadow table (QCMT1)

Needs update

Out of use

Missing

Copy

Missing

Production

operation

Need for Logging Mechanism

Update

Delete

Insert

� A shadow table named QCMT1 with is created the new structure.

� The data from the original table QCM1T1 is copied using a background process during uptime to the

shadow table QCMT1.

� QCM1T1 is still accessible by the applications. Therefore the changes during the data transfer must

be logged and also be executed on the shadow table.

� QCM1T1 is modified by creating a flag field. This field indicates if this entry was already copied to

the corresponding fields in QCMT1.

� Programs can perform updates, deletes and inserts on QCM1T1.

� Update of already converted entry: The “x” in the flag field is erased by the update trigger.

� Deletion of already converted entry: The corresponding entry in the new table is directly deleted

by the delete trigger.

� Insert: The flag field for this entry is left empty.

� Every entry in table QCM1T1 with an empty flag field is copied to QCMT1

� Periodically, the copy is repeated for all new rows since the last copy


Logging Mechanism

QCM1T1 QCMT1

x

x

x

x

x

x

x

x

Needs update

out of use

Still missing

x

Update trigger

x

Copy

Delete

trigger

Update

Delete

Insert

� This could be the situation right after beginning of downtime:

� Some rows are updated or inserted but not copied yet (empty flag field).

� There can be a part of the old table which has not been transferred to QCMT1 (empty flag field).

� The latest insert/update operations and the remaining conversion will be processed during downtime.

� Inserting rows is possible without an additional load at that point in time, because no insert trigger is

used.

� The update trigger is very efficient, because the additional load just consists of filling the flag field.

� Delete operations must be executed in both tables and are therefore inefficient.

� After the incremental conversion starts, dictionary definitions for the relevant tables cannot be

changed until the upgrade ends. This affects changing, deleting or adding field definitions.

Transaction SE11 is locked for these tables.

� If you use incremental table conversion, do not start an SAP archiving program for these tables in

parallel, since this can lead to performance bottlenecks. Therefore, archive as much as possible

before starting the conversion.

� Incremental conversion requires sufficient background work processes. Ideally, there should be one

process for each table to be converted. If you cannot have one process for each table due to a large

number of tables, you can still convert the tables since transaction ICNV distributes the tables by

itself to the available background processes. However, completing the incremental conversion takes

longer, and therefore more time is needed before beginning the upgrade downtime.


Transaction ICNV: Selection of Candidates

Selection of conversion candidates:

� Modified tables that will be converted are included

� Tables can be excluded from ICNV even at this point (for example: a hot spot with frequent updates / deletes)EU_IMPORT

DIFFEXP

START_SHDI

ACT

SHD_IMP

SWITCH

PCON

TABIM

XPRA

ICNV

� 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 jobs

� Selection of background hosts

� Exclusion times

ICNV assistant:

� Initialization

� Start of data conversion

Monitor progress:

� Computation ofconversion statistics

� Estimation of time to finish

� Status display

� Transition to new repository structure is done by the upgrade!

� 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 upgrade 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 SAPup !


Transaction ICNV: UI Elements

Control Elements

� Assistant� Control menu� Menu Edit � Add table

Monitoring elements

� Performance analysis� Error log� Standard log� Job overview

Configuration elements

� Menu Edit � Options used for background processing configuration

� Menu Control � Exclusion times used to limit execution� When starting an activity, starting date / time can be set

Other elements

� Compute progress (usually not needed, recalculates the estimated runtime of data transfer)� Menu Edit � Detailed information (same as double-klick on table)

� Don't trust SE11 and SE14, consistency checks and so on. Objects are mostly not what they appear to

be

� Don't use the reset option in case of trouble. Only error free ICNV cases can be reset and even then

this has an impact on the customer system.

� After a reset, fix the DDIC definition and convert again.

� In the standard upgrade scenario, you cannot make changes to the target definition, as you are

working in the standard instance and the shadow instance is gone.

� Don‘t enter Upgrade downtime with an ICNV conversion in error. If you do so, you have to reset to

the MODPROF_TRANS and finish ICNV first.


Transaction ICNV: Initialization and Steps

Initialization is downtime for the table. Choose a suitable time for that action.

Do not start steps 3 and 4. They are started within the

upgrade downtime automatically.

� There are useful tools for analysis and trouble shooting

� FuBa DD_ICNV_REPAIR lets you execute individual transition steps

� Report RADIMOVE lets you start the data transfer

� Report RADINCNV lets you move along the transition graph

� Report RUTNTCHECK (rutntchk in older releases) lets you display (true) runtime objects

- Option S for DDIC source, Option N for nametab, Option I for internal ICNV description

- A for Active, N for inactive variants

� There is a step count in table ICNV

� If you want to change execution plans, debug to the statement table


Aspects of ICNV

� 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 upgrade

� 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

� 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.

� The conversion process can be stopped and restarted at any time without loss of converted data.

� Error situations like table space overflow or reaching of maxextends due to the incremental

conversion occur during uptime.

� ICNV is especially suited for large Write Once Read Many (WORM) tables

� Pay special attention to the resource usage of your database management system to detect

bottlenecks early.

� Incremental conversion requires double the space in the relevant database container (tablespace,

dbspace, and so on) for each affected table during the conversion.

� Due to the continuous data transfer, there are more transactions. Therefore, you should also

monitor the space for the rollback information.

� Incremental conversion eventually requires more background work processes.

� Make sure, that at beginning of downtime most data is converted.


© SAP 2010

Agenda: Support Packages and Add-Ons


8. Support Packages and Add-Ons

9. Downtime10. Planning and Preparation 11. Enhancement Packages12. Unicode Conversion13. Tools and Services14. SAP Notes for this Course


Support Packages and Add-Ons

Contents:� Why bind SAP Support Packages and Add-Ons to the upgrade?

� Handling of objects from Add-Ons and SAP Support Packages during the upgrade


Binding Add-Ons and SAP Support Packages

� Integrating Add-Ons and SAP Support Packages into the upgrade prevents you from losing data

� PREPARE gives warnings about different patch levels between source and target release

� The upgrade runtime is extended but

� The upgrade downtime is almost the same when using a ‘downtime minimized’ strategy ('high resource usage' or 'medium recourse usage')

� Loading of the included packages into the shadow repository during uptime


SAP Support Packages (1)

t

Begin of availability

End of maintenance

SAP Support Package

SAP R/3 4.6C

SAP_APPL 46C

SAP ECC 6.0

SAP_APPL 600

SAP ECC 6.05

SAP_APPL 605

Bind SAP Support Packages of the

destination release to the upgrade!

60

20

2

� SAP Support Packages on the start release are produced also after a potential destination release has

been shipped.

� SAP R/3 4.6C SAP_APPL Support Package 60 for example has been shipped after the shipment of

SAP ECC 6.0.

� On each potential destination release, SAP Support Packages are available, too.

� There is some relation between the SAP Support Packages: usually fixes have been mad at the same

time for different releases.

� An upgrade from SAP R/3 4.6C SAP_APPL Support Package 60 to SAP ECC 6.0 SAP_APPL

Support Package 0 would partially downgrade the system.

� But: it is possible to bind SAP Support Packages to the upgrade: you can go directly to ECC 6.0

SAP_APPL Support Package 20 or higher (in this example).

� Advantages:

� No need to supply the SAP Support Package on the destination release after the upgrade

� No (temporary) downgrade



A B C D

A B C A B C E

A B C D E

SAP

R/3 4.6C

SAP

ECC 6.05

SPAM

SPAM

new field ‘E‘

SAP_HR SP 140

new field ‘E‘

SAP_HR SP 4

OK OK

Example: Field ‘E‘ was delivered

in SAP_HR SP 140 of SAP R/3 4.6C and SAP_HR SP 4 of SAP ECC 6.05

If 4.6C SP 140 is the start configuration: bind at least SP 4 to the upgrade!

TABLE X TABLE X

TABLE X TABLE X

� An example of why binding SAP Support Packages is necessary:

� Imagine, the field E has been shipped in SAP R/3 4.6C SAP_HR Support Package 140 and SAP

ECC 6.05 SAP_HR SP 4.

� If the start release is 4.6C with SAP_HR Support Package 140 or higher an upgrade to SAP

ECC 6.05 SAP_HR Support Package lower than 4 would drop the field! The data would be lost.

Even if the SAP_HR Support Package 4 was applied after the upgrade, the data of field E still is

lost.

� An upgrade of SAP R/3 4.6C SAP_HR Support Package level 140 should got to SAP ECC 6.0

SAP_HR Support Package 4 or higher.

� PREPARE calculates the so called Equivalence Level (not available with start release 3.1I).


New Features in AS ABAP 6.x/7.x:Queue Calculation (Example)

ABA

APPL

IS-B

BASIS

HR

IS-A

4.6C

4.6C

3.0

2.0

4.6C

4.6C

4

3

140

56

56

56

ABA

APPL

IS-B

BASIS

HR

IS-A

6.05

6.05

5.0

3.0

7.02

7.02

1

2

4

3

2

2

+ IS-A IS-B

Condition for IS-A

Condition for IS-B

only one step

to the system you like

Upgrade DVD Queue of EHP5-parts, Add-Ons, SPs…

� The queue calculation is necessary to determine, in which sequence the SAP Enhancement Package

5 for SAP ERP 6.0 software components, Add-Ons and SAP Support Packages have to be applied to

the new repository (to the shadow repository).

� This is, because SAP Support Packages can be based on each other and Add-Ons may require a

certain Support Package level.


Handling of Add-ons/Software Components

Depending on the situation in the old and the new release, during

an upgrade the following is possible:

� Additional software component is newly installed as

standard component

� Existing Add-on becomes part of standard delivery

� Existing Add-on becomes part of other standard

components

� Existing Add-on is upgraded

� Existing Add-on is kept as it is (keep)

� Existing Add-on is deleted (active/passive)

� Add-on is newly installed

� Depending on the situation in the old and the new release, during an upgrade the following is

possible:

� A additional software component is newly installed as standard component: for example the

software components from the Extension Set

� Existing Add-on becomes part of standard delivery: for example in SAP R/3 4.6C IS-U is an

Add-on, in SAP ECC 6.0 it is in standard delivery (Enterprise Extension IS-UT)

� Existing Add-on becomes part of other standard components: for example the Plug-in (PI) is an

Add-on in SAP R/3 4.6C, but part of standard components in SAP ECC 6.0

� Existing Add-on is upgraded: for example from a release fitting the old SAP R/3 4.6C to a

release fitting the new SAP ECC 6.0

� Existing Add-on is kept as it is: for example because it fits just as well the old SAP R/3 4.6C as

the new SAP ECC 6.0 (option 'keep')

� Existing Add-on is deleted: because it is not needed any longer (active or passive deletion)

� Add-on is newly installed: it is possible to install a new Add-on during the upgrade


Upgrade of Components 7.02

Enterprise

Extensions

Industry

Extensions(none selected here)


IS_SELECT: Selection


Decision about Add-On

� Upgrade with Add-On CD: Add-On upgrade with supplement CD (must be mounted). If the

supplement CD contains a SAINT attribute package (AOS), it is handled by the Add-On queue

calculation (phase ADDON_QCALC)

� Upgrade with SAINT package: Add-On upgrade with SAINT package (AOU). Package must be

available in <EPS>/in directory and is automatically uploaded. Add-On upgrade is handled by the

Add-On queue calculation (phase ADDON_QCALC)

� Upgrade to version on std. upgrade CDs: Only possible for Add-Ons that are delivered with the

Upgrade. This is the default selection for these Add-Ons. Must be changed only if a newer version is

available and you want to include it (usually for PI and PI_BASIS Add-Ons)

� Keep (with vendor key): Component upgrade only. Only possible for Add-Ons that refer to

components that remain unchanged in the upgrade. This is the default selection for these Add-Ons.

Add-On is transferred unchanged to new release

� Delete: Passive deletion. Only possible if the Add-On is not protected (that is, listed in file

<putdir>/bin/IS_PROTECT.LST)

� Delete with CD: Active deletion with a deletion CD (must be mounted).

� no decision yet: Decision is needed. Default selection for all optional Add-Ons. Phase can be

finished successfully only when all Add-Ons have been determined


BIND_PATCH: Selection

� 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

� An SAP Support Package selection that does not meet the minimum package levels leads to an

error.

� Equivalent SAP Support Package Level (equi)

� SAP Support Package level that is equivalent to the level for the source release

� <unknown> if equivalent level could not be determined (for source release 3.1I, for example)

� To avoid loss of data we strongly recommend that you include enough 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 SAP Support Package Level (current) is the maximum package level that

� Is delivered with the upgrade

� 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 upgrade (only relevant for component upgrades)


Availability of SAP R/3, SAP R/3 Enterprise, and SAP ECC Add-Ons (1)

integrated into

SAP Discrete Industries

Add-On (4.5B)SAP

Engineering & Construction

Engineering,

Construction & Operations

Industry Extension*

Add-OnSAP Catch

Weight Management

Consumer Products

Industry Extension* (limited)

Industry Extension (limited)

Industry Extension (limited)

Add-OnSAP BeverageConsumer Products

Industry Extension*

Industry Extension

Industry Extension

Industry Extension

Add-OnAdd-On (4.0B, 4.6B)

SAP BankingBanking

Industry Extension*

Add-OnAdd-OnAdd-OnSAP Discrete Industries

Automotive

Add-OnAdd-OnAdd-On (3.1I, 4.5B)

SAP Apparel & Footwear

Apparel & Footwear

Industry Extension*


Aerospace & Defense

integrated into

SAP Discrete Industries

Add-On (4.0B, 4.5B)

SAP Aerospace & Defense

Aerospace & Defense

SAP ECC 6.0*SAP ECC 5.0

SAP ERP 6.0*SAP ERP 2004SAP R/3

Enterprise 47x200

SAP R/3

Enterprise 47x110SAP R/3 4.6C

SAP R/3 3.1I-4.6B

Availability of SAP R/3, SAP R/3 Enterprise and SAP ECC Add-Ons

Industry-

Specific Component

Industry Solution

� This and the next slide show the impact of Add-Ons when choosing a target release.

� If an Add-On is not offered for a release, it is not possible to perform an upgrade to this release!


Industry Extension*

Add-OnAdd-OnAdd-OnSAP Insurance FS-CS

Insurance

Industry Extension*

Add-OnAdd-OnAdd-OnSAP Insurance FS-CM

Insurance

Industry Extension*

Add-OnAdd-OnAdd-OnAdd-On (4.5B, 4.6B)

SAP Insurance FS-CD

Insurance

Industry Extension*

Add-OnAdd-OnAdd-OnSAP Campus Management

Higher Education & Research

Industry Extension*


High Tech

integrated into SAP Discrete Industries

Add-On (4.5B, 4.6B)

SAP High TechHigh Tech

Industry Extension*

Add-OnAdd-OnAdd-OnAdd-On (4.0B)SAP Patient Management

Healthcare

Industry Extension*

Industry Extension

Industry Extension

Industry Extension

Add-OnSAP Corp.

Finance Management

Financial

Service Providers



Enterprise

47x200

SAP R/3 Enterprise

47x110SAP R/3 4.6C

SAP R/3 3.1I-

4.6B


Industry-Specific

Component

Industry

Solution


* Information on availability with SAP ERP 6.0 / SAP ECC 6.0 reflects current planning status and is subject to change.


Industry Extension*

Add-OnAdd-OnAdd-On (4.0B, 4.6B)

SAP Oil & Gas -IS-Oil

Oil & Gas

Industry Extension*

Industry Extension

Industry Extension

Industry Extension


SAP Environment, Health & Safety

mySAP PLM

Industry Extension*

Add-OnAdd-OnAdd-On (4.6B)SAP MiningMining

Industry Extension*

Add-OnAdd-OnSAP Discrete Industries

Mill Products

integrated into SAP

Discrete Industries


SAP Mill Products

Mill Products

integrated into SAP Discrete Industries

Add-OnAdd-On (3.1I, 4.5B)

SAP Cable Solution

Mill Products

Industry Extension*

Add-OnAdd-OnAdd-OnAdd-On (4.0B)SAP IS-MMedia

Add-OnAdd-OnAdd-OnSAP Insurance FS-RI

Insurance



Enterprise

47x200

SAP R/3 Enterprise

47x110SAP R/3 4.6C

SAP R/3 3.1I-

4.6B


Industry-Specific

Component

Industry

Solution





Industry Extension*

Add-OnAdd-OnAdd-OnSAP IS-WASTEUtilities

Industry Extension*

Industry Extension

Industry Extension

Add-OnAdd-OnAdd-On (4.6B)SAP IS-U/FERCUtilities

Industry Extension*

Add-OnAdd-OnAdd-OnAdd-On (4.6B)SAP IS-U/CCSUtilities

Industry Extension*

Add-OnAdd-OnAdd-OnAdd-On (4.6B)SAP RM-CATelecommunication

Industry Extension*

Add-OnAdd-OnAdd-OnSAP Public Sector PSCD

Public Sector

Industry Extension*

Industry Extension

Industry Extension

Industry Extension

Add-OnAdd-On (4.0B, 4.5B, 4.6B)

SAP HR Public Sector

Public Sector

Industry Extension*

Industry Extension

Industry Extension

Industry Extension


SAP Funds Management

Public Sector

Industry Extension*

Industry Extension

Industry Extension

Industry Extension

Add-OnAdd-On (4.0B, 4.5B, 4.6B)

SAP Oil & Gas -JVA

Oil & Gas


SAP ERP 6.0*SAP ERP 2004

SAP R/3 Enterprise

47x200

SAP R/3 Enterprise

47x110SAP R/3 4.6C

SAP R/3 3.1I-

4.6B


Industry-Specific

Component

Industry

Solution



Availability of Other Add-Ons

Add-OnSAP IS-U/UCESUtilities

Add-On (SAP SCM 5.0)*

Add-On (SAP SCM 4.1)

SAP Forecasting & Replenishment

Retail

Add-OnSAP IS-M/AMCMedia

Add-On*Add-OnAdd-OnSAP Account Management

Banking

Add-On*Add-OnSAP CYT Management

Banking

Add-OnAdd-On (SAP

Web AS 6.20, SAP BW 3.1 Content)

Add-OnSAP Bank AnalyzerBanking

SAP NetWeaverAS 7.0

SAP NetWeaverAS 2004

SAP Web AS 6.20

SAP Web AS 6.10SAP Basis 4.6C

Availability of Other Add-Ons

Industry-Specific ComponentIndustry Solution

* Information on availability with SAP NetWeaver 7.0 reflects current planning status and is subject to change.


© SAP 2010

Agenda: Downtime





Downtime

Contents:� What is downtime?

� What causes the downtime during an upgrade?

� How can downtime be reduced?

� Outlook: Near Zero Downtime Upgrade


What is Business Downtime?

Production

operation

Downtime

SAP 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 Upgrade 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 Upgrade 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 / transports

� Configuration changes

� ...

� Improved/optimized Upgrade and

patch processes

� Proven software lifecycle

management and propagation

engines (i.e. enhanced CTS)

� To be avoided with scalable components

which enable rolling maintenance

� Hardware/OS failures

� Other disasters

� Application failures

� Operating / handling errors

� Unintentional data deletion

� …

�Application

failures

40%

�Operator

errors

40%

�HW, OS failures,

disasters

20%

Source: Gartner Group

Main causes for unplanned downtime


© SAP 2010

Planned Downtime - Availability Impact

High

frequency

Long duration

Minutes

Low

frequency

Short duration

0,5 … 2 hours 10…15 hours

Weekly

Monthly

Quarterly

Yearly

Offline

backups with split-mirror

Kernel

patches

Profile

parameter

changes

Offline

backups

without split-mirror

Transports

SAP Support Packages

End of

daylight saving time

Release upgrades

Databasereorganizations

OS/DB migration /

Unicode

conversions

20…48 hours

Single

Event

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


The High Availability Scale

Availability Downtime per week

Weekly downtime usable for (examples)

Downtime per year

Yearly downtime usable for ….

99,9999% 0,6 sec ?? 30 sec ??

99,999% 6 sec Weekly fast switchover 5 min 1 yearly restart (?)

99,99% 1 min Daily fast switchover 52 min One short offline software maintenance per year

99,9% 10 min 1 Weekly restart8 hours 45 min

One offline software maintenance per year

99% 1h 40 min Offline software maintenance

87,5 hours

90% 16h 48 min 1 Offline backup per week 36 days

�ACHIEVABLE TODAY�ACHIEVABLE TODAY


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 outage

� They depend on the business impact

� For longer downtimes costs can increase progressively

� Example: when SCM processes are stuck longer than 3 hours the whole production will be stuck and cause even higher costs

� Redundant components � Disaster recovery site� System management tools� IT staff� Capacity planning� Guaranteed SLA� Proactive services


UpgradeStrategy

Planning the Upgrade Strategy: Purpose

Archive

mod

e

of

data

base

Database backup

Maximum

permitted

downtime

Sizeof

certa

in

datab

ase

tables

Import of

substitutionset in

production

operation


Decoupling of OS, DB and SAP Upgrade

SAP

DB

OS

SAP

DB

OS

Start release

configuration

Destination

release

configuration

New SAP version may require

� new database version

� new operating system version

The start release of SAP software

runs on

� target release DB and

� target release OS

System downtime

Recommendation: Split into different maintenance slots!

� SAP usually also releases 'older' SAP releases on DB and OS versions higher than those used

initially

� This enables customers to run an SAP release on the latest DB and OS versions if required. Thus the

maintenance periods of SAP releases can be enlarged.

� During the upgrade of an SAP / DB / OS combination this feature may be used to split up the system

downtime (e.g. into two different weekends):

� First, do the upgrade of DB and OS to the version required by the target release of SAP system.

� Second, upgrade SAP system to target release.


Production Downtime During Upgrade

� Downtime behavior with standard, high and low resource use.

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

� 'Low Resource Use' refers to the 'Resource minimized' strategy


Production Downtime During Upgrade

� Upgrade technical runtime (SAPup) – most of this is not production downtime!

� Post-upgrade transports & manual adjustments

� Business validation & acceptance testing

� Possibly pre- and post-upgrade system backups

� Business ramp-down & ramp-up

What are the elements of production downtime?

up

down

up

down

SAPup:PREPARE

&repository

import

ramp-down

SAPup: 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

upSAPup:

PREPARE &

repository import


ramp-up

backup?

go/no-go decision

backup?

up

down

upSAPup:

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 (for example using a Customer Based

Upgrade)

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


Influencing Factors for Runtime & Downtime

Do

wn

tim

e � Type & performance of the storage(I/O throughput)

� Number and type of CPU s for the app. & DB server

� Start & target Release

� Version of the Upgrade tools

� Productive applications/ Add-Ons or industry solutions

� Upgrade parameterization (e.g. number of processes)

� Number of clients

� Upgrade strategy (downtime or resource minimized)

� Usage of Incremental Conversion (ICNV)

Ru

nti

me

� Type & performance of the Storage

� Number and type of CPU s for the app. & DB server

� Start & target release

� Number of included SAP Support Packages

� Number of modifications on standard SAP objects

� Version of the Upgrade tools

� Productive applications/ Add-Ons or industry solutions

� Upgrade parameterization (e.g. number of processes)

� Number of installed languages

� Import destination time

� Usage of Incremental Conversion (ICNV)

Hardware Software Configuration Strategy

1 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 upgrade with production data !

“

� Upgrade runtime: Total duration of the upgrade controlled by SAPup including preparation and

uptime activities.

� Runtime and downtime depend on:

� Hardware and operating system: The whole upgrade 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

� Upgrade strategy: More or less down- and runtime

� A test upgrade on a production system mirror (sandbox system upgrade) and thorough analysis of the

upgrade log files can highlight many possibilities for effective manual tuning activities early in the

project.


Ac

tio

ns t

o r

ed

uce d

ow

nti

me

Ph

ases

Upgrade Tuning Within SAP StandardActions to Reduce Runtime & Downtime

Usage of ICNV

Create well thought out cutover plan

Including all required SAP Support Packages into the upgrade

Backup strategy

Use transports created for automatic mod. Adjustment (SPDD/SPAU)

Hardware

Software & tools

Configuration

Strategy

Set import destination time

Usage of new hardware

Usage of the latest Upgrade software/tools (SAP ECC 6.05 / SAPup / Fixbuffer)

Usage of 'Downtime minimized' upgrade strategy

Use as many parallel upgrade processes as possible

Usage of ASU ToolboxUsage of

Upgrade Accelerator / ASU

Test automation for

business validation


Follow-up

activities

Upgrade

downtimePrepare Upgrade uptime

SAP R/3

4.7

SAP R/3

4.6C

1 based on Upgrade Experience DB

Upgrades to SAP ECC 6.0:Business Downtime by Source Release1

Business downtime in hours

0 12 24 36 48 60 72 84 96 108

Hours

Max: 86,0Min: 24,0

Median: 48,0


Business downtime in hours

0 12 24 36 48 60 72 84 96 108

Hours

Max: 71,0


Median: 33,0

Min: 15,5

� Business downtime: Total time that the system is not available for end users, including the technical

downtime plus the time necessary for data backup, final tests, etc.


SAP R/3

4.7

SAP R/3

4.6C

Project duration in weeks

0 4 8 12 16 20 24 28 32 36 40 44 48 52

Weeks

Max: 30,9

Median: 15,8

Min: 7,0


Distribution of values


0 4 8 12 16 20 24 28 32 36 40 44 48 52

Weeks

Max: 35,0

Median: 21,0

Min: 12,0


Upgrades to SAP ECC 6.0 –Project Duration in Weeks

� On an average an upgrade project takes around 21 weeks (with an SAP R/3 4.6C start release). But

the range is quite large. This is because an upgrade project is highly individual and depends on the

special circumstances and environment of the landscape.


Upgrades to SAP ECC 6.0:Technical Downtime

250

200

150

100

50

0

0 3 5 7 9

11

31

15

17

< 1

8

Downtime# U

pg

rad

es

Hours (average 8.3)

Technical downtime: Total time during which the system cannot be used productively. This does not include time for data backup, testing etc.

Average technical downtime:8.3 h

Upgrade strategies: Downtime-minimized, resource-minimized Number of Systems Analyzed: 755


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

Use new backup tools & strategy

ToolsUse latest Support Release for Upgrade

Use Incremental Conversion (ICNV) if possible

ServiceDowntime Optimization Service1

Upgrade Coach2

Cutover

PlanningParallelize tasks

Improve backup strategy

Automate testing for GO decision

Customer Based Upgrade (CBU)

Upgrade 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.


Transaction ICNV: Reduction of Upgrade Downtime

Reduction of upgrade downtime

� Large tables are now converted during uptime

� Only switch to new structure during downtime(in PARCONV)

Easy handling

� Fully integrated into upgrade process

Configurable conversion process

� Exclusion times

� Progress 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 upgrade

� 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


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 upgrade� Reports needing manual input by users� Special data migrations

� Integrated with SAPup and Solution Manager

� Delivered via support tool plug-in ST-PI� Refer to SAP Note 1000009

Benefits

� More efficient preparation and execution of upgrade relevant application tasks

� Less manual efforts during upgrade� Higher business stability after upgrade

Application-Specific Upgrade (ASU) Toolbox


Upgrade Accelerator

� The Upgrade Accelerator executes known and automatically executable additional preparation and follow-up activities.

� This reduces significantly the number and efforts spent with additional

manual upgrade steps!

� The Upgrade Accelerator is being executed automatically during the preparationalphases and at the end of the downtime:� Preparational phase: RUN_UACC_PREP� End of downtime: RUN_UACC_POST

� The add-on ST-PI delivers the Upgrade Accelerator Framework. It is being checked as an upgrade requirement by SAPup in phase ASU_CHK.

� The newest content is available via the SAPup Fix Buffer as download from SAP Service Marketplace.


Scatter plot downtime vs. DB-Size

0

10

20

30

40

50

60

70

80

90

100

0 100 200 300 400 500 600 700 800 900 1000

DB-Size/GB

Do

wn

tim

e/h

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

Database Size and Upgrade

Upgrade without Unicode conversion: Archive and delete only selectively“Unicode conversion: Archive and delete as much as possible“

� No direct relation between DB size and upgrade downtime

� Some tables that undergo structural changes may have to be converted and therefore affect the downtime

� Q: Does the total database size affect the upgrade downtime? A: No, only in special cases the size of

single tables may have an effect on upgrade downtime.

� Q: Why may some tables affect upgrade 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 upgrade downtime? A: The most precise way is to

do a test upgrade and evaluate the upgrade log, especially the parts: DDLs, conversions and XPRAs.


Near Zero Downtime Upgrade (NZDT)Summarized customers’ requirements

The requirements of the customers

� Business Downtime for a release upgrade is 2 - 4 hours

� In case of problems the procedure is completely resettable

� Upgrade procedure should be reusable for all SAP systems, initially R/3

� The procedures should also be applicable for SAP Support Packages

The method can be used for numerous downtime eventsUpgradeUpgrade and Unicode ConversionUpgrade and OS/DB Migrations

… and alsoOS patchHW replacementDB reorg


Technologies for Near Zero Downtime

� Consistent system copy (clone) with the logging of database changes� Normal Upgrade / Unicode conversion� Synchronization of the changes between the main system and the copy – delta replay� Transports, Pre-Validation while Uptime

De

lta re

pla

y

Recording

PRD

R/3 4.6C nUC

hostA

clo

ne

downtime

Prepare + Upgrade Uptime

Upgrade

and Unicode conversion

+ Transports

+ Add Ons+ Pre-Testing

Last D

elta

rep

lay

Fin

al-V

alid

atio

n

Infra

stru

ctu

re

ad

just. -

inte

rfaces

Upgrade + UC Downtime Post ProcessingDelta

TransferInfra

structure

hostA

Validation

PRD

ECC 6.0 UC

hostB

PRD

R/3 4.6C nUC

hostB


Technologies for Near Zero Downtime

� Consistent system copy (clone) with the logging of database changes� Normal Upgrade / Unicode conversion� Synchronization of the changes between the main system and the copy – delta replay� Transports, Pre-Validation while Uptime

De

lta re

pla

y

Recording

clo

ne

downtime

Prepare + Upgrade Uptime

SAP Enhancement Package 5 for SAP ERP 6.0

+ Transports

+ Add Ons+ Pre-Testing

Last D

elta

rep

lay

Fin

al-V

alid

atio

n

Infra

stru

ctu

re

ad

just. -

inte

rfaces

EHP installation downtime Post ProcessingDelta

TransferInfra

structure

hostA

Validation

PRD

ECC 6.02

hostB

PRD

ECC 6.02

hostA

PRD

ECC 6.05

hostB


Near Zero DowntimeArchitecture

Application data

Z-A

pplication data

Customizing Z-Cust.

System tables

Repository

Application data

Z-A

pplication data

Customizing Z-Cust.

System tables

Repository

Delta

freeze

Delta

ignore

ignore

freeze

Allo

w c

hang

es

Hot clone + enhancem

ent package

Including Upgrade logic


Comparison of Business DowntimesStandard Method versus NZDT

up

down

SAPehpi:

PREPARE &

repository import

ramp-down

SAPehpi: conversion, XPRAS, etc.

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

Final

Deltasync

Replicate Data

Standard EHP implementation with SAPehpi

NZDT Upgrade

freeze


© SAP 2010

Near Zero Downtime for SAP ECC Minimizing Planned Downtimes

Applicable for� Release upgrade� SAP Support Package updates� Customizing waves� DB maintenance – table reorganization� OS or DB patch

Near Zero Downtime method as a tool for minimizing downtimes

Number of executions

Effo

rt p

er e

xecu

tion

Upgrade

DB reorg

SAP enhancement package

SAP Support PackagesDB reorg



© SAP 2010

Agenda: Planning and Preparation





Planning and Preparation

Contents:� Upgrade as a project� Upgrading a three system landscape� Upgrade Dependency Analyser (UDA)� Technical aspects� Upgrade experiences� Further information


© SAP 2010

Unit 10: Overview Diagram

Lesson 3: Upgrade Dependency Analyzer

Lesson 4: Technical Aspects

Lesson 5: Upgrade Experiences

Lesson 6: Further Information

Unit 10 – Upgrade Planning and Preparation

Lesson 1: Upgrade as a Project

Lesson 2: Upgrade of a Three System Landscape


Upgrade Project: Key Questions

Key Questions

Will the upgrade go liveon 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 Upgrade 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 upgrade project“

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


Plan

Main Challenges when Planning and Executing an Upgrade – Worldwide Results

Build

69%Estimate cost & effort

46%Define business case

46%Define and allocate project team/resources

46%Downtime minimization

43%Assess impact onexisting solution

29%Find information onupgrade methods & tools

28%Interoperability

14%

4%

Complianceconsiderations

Others

0% 80% 100%20% 40% 60%N=1484 N=1484

64%Efficient testing


48%Modification adjustment

47%Project management

39%End user training

39%IT infrastructure/sizing

5%Others

0% 80% 100%20% 40% 60%

The report includes answers from the following 360 Upgrade adoption programs: North America (Jan 2008), Brazil (March 2008), Germany (March 2008), Japan (March 2008), UK & Ireland (March 2008), Australia (April 2008), Sweden (April 2008),China (May 2008), India (May 2008) and France (Sept 2008)


Possible Upgrade Approaches: Think Big and Start Small


� Affecting the whole enterprise

� Demanding in-depth knowledge of� Business models� Processes� Application landscapes� Application modification


Discover,prepare

andget even

morevalue

Take your time

Generate value

as you go



Fast

Low costsand manageable

impact

Protect investment

Service-oriented

architectureNew


� Technical Upgrade: Reduction of modifications

� Eliminate modification not used: Up to 80% of all modification

� Replace modification with standard functionality: Up to 50% of all modifications

� Technical and functional optimization: Archiving, master date clean-up, interface optimization

� Functional: Focus

� Modernization of the Core SAP ECC, stabilization of the basis

� Individualization of the user interface

� Strategic: Focus

� Standardization

� Harmonization

� Consolidation


You can directly upgrade:

* AS/400: Start release must be >= 4.6C

SAP R/3 3.1I

SAP R/3 4.6C

SAP R/3 4.0B

SAP ECC 6.0

from(and above)

to(and below)

SAP ECC 6.0 EHP 3 or 4

SAP ECC 6.0 EHP >= 5

Upgrade to ECC 6.0:Start and Target Release

� Note: it is not possible to upgrade from SAP R/3 3.1I to ECC 6.03 and above anymore!

� Starting from upgrades to ECC 6.05 only upgrades from start release 4.6C and above are supported!


Complexity Drivers

Upgrade project

complexity drivers

Business related leversImpact: medium to high

IT related leversImpact: medium to high

Number of modifiedobjects

Source release

Number of codepages

Number & type of ext.interfaces

OS / DB migration requirements

Type of Upgrade (Technical/functional)

Number of Add-ons / Industry Solutions

Required downtime

Testing requirements

Code freeze strategy

� An upgrade project is more or less complex, depending on several drivers.

© SAP AG ADM326 10-10

SAP Solution Manager

SAP CustomerSAP

End-to-endsolution operations

SAP Experts

Upgrade Roadmap

Test Workbench

E-learning mgmt. Change Management

SAP Service Marketplace

© SAP AG ADM326 10-11

SAP Upgrade Road Map – Overview

DESCRIPTION

BENEFITS� Repeatable approach that helps to mitigate risks,

attack key time consumers and reduce costs and effort

� Central point of access to upgrade project information and integrated use with SAP Solution Manager

EXAMPLE

� SAP's standard methodology to plan and execute the upgrade of an SAP solution

� Content: Best practices and templates for project management, functional and technical aspects facilitating key tasks of the entire project team

� Formats: � SAP Solution Manager � HTML version on SAP Upgrade Info Center

at: http://service.sap.com/upgraderoadmap� Availability:

� Since 06/2004� Languages: English, German

� The SAP Upgrade Roadmap: On one side, this is a methodology, as the Upgrade Roadmap represents SAP’s standard project methodology (it is a flavour of the ASAP methodology). On the other side, it is a tool, as it is really a tangible application. It covers:

� Organizational/basic project management aspects

� Application-specific aspects

- Application and modification adjustments

- Test planning and execution

- End-user training and documentation

� Technology aspects

- IT infrastructure planning and re-sizing

- Administration and security concept

- Technical upgrade procedure

� Target group:

� Project lead as well as

� Project team members

© SAP AG ADM326 10-12

Plan Build Run

Upgrade Discovery Upgrade ImplementationUpgrade

Evaluation

Operations &Continuous Improveme

nt

Upgrade project completed

Upgrade project started

Define business and IT requirements

Definestrategy

Minimize costs and risks of Upgrade Project

Upgrade Roadmap

ProjectPreparation Realization Final Preparation

for Cutover

Production Cutover &Support

Blueprint

Document current solution and set-up

project

Specify implementation scope and solution adjustment needs

Implement and adjust solution

Perform integration and system tests and plan cutover

Execute production system Upgrade &

support

Upgrade as a Project – Plan, Build, Run

� The Upgrade project does not start with the kick-off. Before an upgrade project some tasks has to be done for defining business and IT requirements, define an upgrade strategy and create a business case for the upgrade project during discovery and evaluation phase before the project starts itself.

� Three different phases of an upgrade project:

� Plan

� Build

� Run

� Use SAP Upgrade Roadmap to handle the complete 'Build' phase

© SAP AG ADM326 10-13

Key Activities in the Discovery Phase

Define Business Requirements

Define IT Requirements

� Document current status of business solution� Identify impact of corporate business strategy on current

business solution� Identify existing gaps and issues� Define future business needs� Understand new functions and features of SAP target

solution� Map requirements to possible target solutions

� Document current solution landscape� Identify impact of corporate IT strategy on current solution,

for example. including provider model and data center, hardware and platform strategies

� Define maintenance strategy for solution� Understand new technology features of possible SAP

target solutions

Update Corporate Business and IT strategies

Build

Upgrade Discovery Realization Final Preparation

for Cutover

Production Cutover

& SupportBlueprintProject

Preparation

Plan

Upgrade Evaluation

� Identify TCO of the as-is solution and costs for adaptation to business requirements in existing landscape

� Estimate TCO of planned target landscape� Estimate upgrade project costs and general change costs� Formulate business value proposition� Create business case

Create business case

Create Upgrade Master Plan

� Identify and design possible target solution landscapes (releases and software components) that meet business and IT requirements

� Perform high-level analysis of how changes affect the complete solution landscape (including technical platform, SAP and non-SAP software)

� Evaluate migration paths to possible target landscape and determine best option

� Considerations that help to define the IT requirements are as follows:

� Which changes are intended in the foreseeable future, either driven by the corporate IT program management or by local system owners?

� Is a change of the provider model planned? May systems get moved into a hosting scenario?

� Will geographical re-locations take place, for example, centralization or de-centralization?

� Is it possible to merge servers into one data center?

� Will global agreements with hardware vendors about new architectures be negotiated regarding new CPU type, blade server, adaptive computing and so on?

� Does the global policy regarding operating system or database product change?

� Regarding an SAP maintenance contract, what type of contract situation do you have: standard maintenance, extended maintenance, or customer-specific maintenance?

© SAP AG ADM326 10-14

Key Project Activities of a Technical Upgrade at a Glance

Build


for Cutover

Production Cutover


Preparation

Plan

Upgrade Evaluation

Project Management

Business Aspects

Technical Aspects

� Time planning: Dependencies to other implementation or roll-out activities, project runtime� Budgeting: IT costs; project costs (internal and external) � Resource planning: number of project members; skills; roles & responsibilities; external resources involved

� Application Adjustments:� Release Customizing: Upgrade Customizing / Delta Customizing� Redesign of missing SAP functionality: redesign; application and technology migration (if required)� Modifications/Custom Developments: Identification and elimination of unused code� Other adjustments: interfaces, forms, authorizations

� Testing of key business processes� End-User Training: only if significant user interface changes and redesign / application adjustments were required

� IT Infrastructure Adjustments / Sizing of new release: Server, Frontend; Network� Planning – Technical Upgrade Process: SAP application but also operating system and database� Planning - Backup Strategy: during and after the technical upgrade � Execution - Technical Upgrade: DEV, QAS and PRD system as well as additional project & training systems� Post Upgrade Activities: Performance analysis, reorganizational actions

© SAP AG ADM326 10-15

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.0 SP15 or higher

� Data maintenance with Solution Manager System Landscape (SMSY)

� Gain stability and access to innovation

� Upgrade only the enhancements applicableto your business

� Reduce risk and downtime

� Speed implementation and test less

DESCRIPTION

ACCESS

BENEFITS

© SAP AG ADM326 10-16

Strategy� Technical upgrade vs. upgrade with new functionality

New features and functions� New features in existing transactions� Number of new functionalities to implement

Modifications� Number of modifications, which could be returned to SAP

standard � Number and complexity of modifications needed in the

new release

Documentation� Level and quality of documentation of business processes,

custom programs, and modifications� Documentation for testing

Last but not least …� Hardware requirements� Range of testing and training� Customer or partner skills in upgrade projects� Management commitment and available resources

Project Duration – Influencing Factors (1/3)

© SAP AG ADM326 10-17

Hardware requirements of the new release� Server� Frontend� Network

Sizing and system configuration for the new release� Going Live – Functional upgrade check

Planning of technical upgrade process� Operating system, database, and SAP ERP

Planning a backup strategy� During the technical upgrade � After release upgrade

Executing of technical upgrade� Development, quality assurance, and productive systems� Training systems

Activities after upgrade� Performance analysis, re-organizational actions


© SAP AG ADM326 10-18

Determine software requirements� SAP Industry Solutions (most of them absorbed into SAP

ERP Central Component as of SAP ERP 6.0)� SAP country-specific versions� Third-party products or add-ons� Interfaces between SAP ERP and non-SAP software � Operating system and database� Communication protocols


© SAP AG ADM326 10-19

Key Upgrade Considerations Impact Software license requirements � Any needed? … Allow for approval cycles, if required

Operating system/database upgrade � Does the operating system & database need to be upgraded?

Hardware upgrades � Add time & dependencies

Set-up of upgrade project system infrastructure

� Usually takes two weeks, unless hardware is needed

Unicode conversion � Will add more time to the project

Dependencies on other SAP software components, e.g., Employee Self-Service or SAP CRM

� Additional time & effort if other components will be upgraded

Dependencies on non-SAP software � Early inquiries with vendors on SAP compliance

Installation of SAP enhancement packages

� Upgrade + plus install latest SAP enhancement package; allow time for installation & regression testing. Activating functionality will have a greater impact on the project scope

Functional enhancements � Usually require additional effort; requires separate scoping effort to assess impact

Business constraints � Timing & availability of resources for testing; amount of time production system will be taken down during cut-over time.

Scheduling Factors (1/2)

© SAP AG ADM326 10-20

Key Upgrade Considerations ImpactParallel projects � Planned projects that may affect the upgrade, change control/code freeze plans,

Landscape analysis � Upgrade of other SAP applications; analysis of source SAP system (volume & complexity of custom modifications & developments; number of modules in use; number of interfaces, number of end user)

Fiscal year end � Generally drives the go-live date

IFRS compliance � New G/L involves a GL migration project; upgrade typically before a new GL migration project

Scheduling Factors (2/2)

© SAP AG ADM326 10-22

Project work

Key Project Activities –Project Preparation

BuildPlan


for Cutover

Production Cutover

& SupportBlueprint

ProjectPreparation

Upgrade Evaluation

UPS

Old

System landscape

Upgrade project system

Productive landscape

System copy

DEV

Old

QAS

Old

PRD

Old

Legend= new release= old release= actual project work

= Transport route= System copy

Project Management Team:� Create project plan� Nominate project team� Plan and facilitate project team training� Order temporary hardware� Define test conceptTechnical Team:� Prepare upgrade project system UPS� Update SAP GUIs (if required)Business Team:� Study material on new release

(Development news, Service Marketplace material, documentation and so on)

Developers:� Review customer programs and

modificationsMilestones: Project prepared (Start of Project)

� Deliverables at milestone 'project prepared' (Solution Manager project milestone 'Start of Project'):

� Project plan exists describing the project organization with roles, tasks and responsibilities as well as exact timelines, milestones and deadlines

� Project resources (internal/external) are nominated and trained

� Test focus and framework have been defined

� Upgrade project (sandbox) system is prepared for first test upgrade

© SAP AG ADM326 10-23

Project work

Key Project Activities –Upgrade Blueprint

BuildPlan


for Cutover

Production Cutover


PreparationUpgrade

Evaluation

System landscape



QAS PRDDEV

Old Old Old

UPS

New

Project Management Team:� Kick-off project� Refine project plan� Plan end-user trainings� Review solution operation conceptTechnical Team:� Upgrade project system UPS� Define future IT infrastructure� Prepare DEV system upgradeBusiness Team:� Perform initial business processes

tests� Design business processes changesDevelopers:� Start application adjustment on UPSMilestones:Blueprint completed (Scope to Build)



� Deliverables at milestones 'blueprint completed' (Solution Manager project milestone 'Scope to Build'):

� New business processes, process enhancements and replacements of custom developments with the SAP standard are fully specified

� Adjustment requirements are specified and all performed adjustment activities (SPDD, SPAU, custom developments, customizing, etc) are documented

� Existing core business processes run in sandbox system without errors, at least for standard regression test scenarios

� Full documentation of upgrade procedure, issues and problem resolutions exists in central upgrade script

� Documentation and first analysis of technical downtime performed during sandbox upgrade

© SAP AG ADM326 10-24

Project work

Key Project Activities –Upgrade Realization I

BuildPlan


for Cutover

Production Cutover


PreparationUpgrade

Evaluation

System landscape


Temporarymaintenance

landscape


QAS

Old

PRD

Old

UPS

New

Doublemaintenance

DEV'

OldTransfer changes

DEV

New

Project Management Team:� Prepare integration tests� Prepare end-user trainings� Update solution operation conceptTechnical Team:� Set-up temporary DEV' system for

maintenance� Upgrade DEV system� Prepare QAS system upgrade � Start optimizing technical downtimeBusiness Team:� Complete customizing adjustmentsDevelopers:� Redo manually adjustments in DEV� Complete application adjustments� Perform unit tests in DEVMilestones:Solution built (Build to Test)



� Deliverables at milestones 'solution built' (Solution Manager project milestone 'Build to Test'):

� Development system is upgraded to new release

� Double Maintenance and code freeze phase for current production environment is in place.

� All changes or enhancements to business processes, customizing or custom developments are completed and unit tested in the development system

© SAP AG ADM326 10-25

Project work

Key Project Activities –Upgrade Realization II

BuildPlan


for Cutover

Production Cutover


PreparationUpgrade

Evaluation

System landscape



landscape


Double maintenance

PRD

Old

UPS

New

DEV'

Old

Transfer changes

Transfer changes

Transfer changes

QAS'

Old

QAS

New

Project Management Team:� Prepare integration tests� Prepare end-user trainings� Update solution operation conceptTechnical Team:� Set-up temporary QAS' system for

maintenance� Upgrade QAS system� Transport project work to QAS system� Optimize technical downtimeBusiness Team:� Perform main integration and

acceptance tests in QASDevelopers:� Correct errorsMilestones:Integration, performance and system

tests complete (Test to Deploy)



DEV

New

� Deliverables at milestones 'Integration, performance and system tests complete' (Solution Manager project milestone 'Test to Deploy'):

� Development system is upgraded to new release

� Double Maintenance and code freeze phase for current production environment is in place

� All changes or enhancements to business processes, customizing or custom developments are completed and unit tested in the development system

© SAP AG ADM326 10-26

Project work

Key Project Activities –Final Preparation for Cutover

BuildPlan

Upgrade Discovery Realization

Final Preparationfor Cutover

Production Cutover


PreparationUpgrade

Evaluation

System landscape



landscape


Double maintenance

PRD

Old

UPS

New

DEV

New

DEV'

Old

QAS'

Old

Project Management Team:� Create detailed cutover scheduleTechnical Team:� Perform final system tests� Deploy new production infrastructure� Prepare PRD system upgradeBusiness Team:� Perform final integration tests� Sign off solution in the new releaseProject Steering Committee:� Sign off production system upgradeMilestones:Cutover prepared



QAS

New

� Deliverables at milestones 'Cutover prepared':

� Cutover schedule and upgrade script are compiled

� Final integration and system tests are completed without issues

� Infrastructure is ready for production system upgrade

© SAP AG ADM326 10-27

Project work

Key Project Activities –Final Preparation for Cutover

BuildPlan


for Cutover

Production Cutover


PreparationUpgrade

Evaluation

System landscape


DEV

New

QAS

New

PRD

New

Technical Team:� Upgrade production system PRD� Perform post processing activitiesBusiness Team:� Finally sign off business solution� Support go-liveDevelopers:� Support go-liveProject Management Team:� Handover solution to production� Close projectMilestones:Start of productionHandover to production (End of Project)



� Deliverables at milestones 'Start of production':

� Production system is upgraded to new release and released for production operation

� Deliverables at milestones 'Handover to production' (Solution Manager project milestone 'End of Project'):

� Standard operating organization resumes responsibility for solution

� Temporary project enhancements of system landscape are removed

� Project is finally signed off and closed

© SAP AG ADM326 10-28

Recommended Upgrade Project Landscape –Upgrade Project System

Reasons for an upgrade project system:� Test technical upgrade procedure

� learn about specifics of your system� Test of customer developments in new release

� understand and plan custom development changes in detail� Start modification and custom development adjustment

� limit efforts by focusing on objects in production� reduce double maintenance/code freeze period

� Perform first tests of core business processes in new release� understand and plan integration tests requirements

� Perform first checks of new functions� obtain insight in new release and plan future functional roll-outs

� Obtain first test results of technical upgrade downtime� understand and plan downtime optimization requirements

Making early upgrade experiences helps� mitigating risks � better planning project efforts

“

� The upgrade project system is frequently also called 'upgrade sandbox system'.

� SAP recommends creating the upgrade project system as copy from the production system with full data. Otherwise all benefits listed above cannot be achieved.

© SAP AG ADM326 10-29

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 upgrade project!

� How to plan efforts and resources for adjustment process� How 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 AG ADM326 10-30

Recommended Upgrade Project Landscape

Legend

= new release

= old release


UPS

New

3-system landscape

Double maintenance

Transfer changes


Temporarymaintenance landscape


Transfer changes

Transfer changes

System copy

DEV QAS PRD

DEV'

New New Old

Old

QAS'

Old

� The upgrade project landscape consists of the following system groups:

� Productive Landscape This is the landscape that shall be upgraded to the new release. The standard landscape is assumed to consist of a development system (DEV), a quality assurance system (QAS) used for testing, and the production system (PRD). If more systems exists in the actual landscape, more upgrades might be necessary. However, depending on the system role and creation process, some of these additional system could also be created as copies of the three main systems above after the upgrade has been completed. For example, a training system could be created as copy of the upgraded QAS or PRD systems.

� Temporary Maintenance Landscape This landscape is set up during the project to ensure the maintenance of the production system on the old release until it is upgraded. The systems will be removed after the completion of upgrade project.

� Upgrade Project System This system – sometimes also called upgrade sandbox system – is created in the preparation or upgrade blueprint phase to conduct the first upgrade tests. This system should be available throughout the project. Even after the DEV and QAS system upgrades, it can serve as additional test system, for example, for optimizing the technical downtime. The upgrade project system can also be removed after the completion of the upgrade project.

© SAP AG ADM326 10-31

Productionsupport

Production Landscape

Upgrade Project LandscapeUpgradeproject

� Code freeze: yes or no? - avoid possible system and testing inconsistencies versus fulfilling ongoing business requirements

� Plan efforts required for implementing and testing changes in both landscapes, particularly with ongoing developments in production landscape

� Manage emergency repairs in production landscape during code freeze period and align with upgrade landscape

Manage Parallel Changes

DEV

New

QAS

New

PRD

Old

DEV'

Old

QAS'

Old

Challenge: Coordinating the parallel change streams

© SAP AG ADM326 10-32

Recommended Upgrade Project Landscape –Special Cases

Legend

= new release

= old release


UPS

New

2-system landscape

Transfer changes



landscape


Transfer changes

System copy

DEV

New

PRD

Old

DEV'

Old

Recommended upgrade project landscape for two system maintenance landscapes

Recommended upgrade project landscape for three system maintenance landscapes including a temporary development system for new projects after the upgrade

UPS

New

3-system landscape

Transfer changes



landscape


Transfer changes

Transfer changes

System copy

DEV

New

QAS

New

PRD

Old

DEV'

Old

QAS'

Old

Temporarydevelopment

landscape

DET

New

Transfer changes

Doublemaintenance

Doublemaintenance

� For certain SAP products (SAP BW, SAP NetWeaver PI) or systems with a small business scope, two system maintenance landscapes might be used. In these cases, development and quality assurance are done on one system (here: DEV). Nevertheless, an upgrade projects system should be installed as well.

� In case, you do a pure technical upgrade first, but nevertheless plan a functional upgrade or roll-out soon after the upgrade, you could set up an additional temporary development system on the new release. This step avoids conflicts with the project or code freeze and saves time for the preparation of the roll-out. The temporary development system should be created as copy from the upgraded development system after completion of the initial application adjustments. During the project the temporary development system receives change transports and corrections from the project development system.

© SAP AG ADM326 10-33

Source Release Landscape

Change Management During the Upgrade Project

Manually re-applyTarget Release Landscape

TR

DEV'

ABAP

QAS'

ABAP

TR PRD

ABAP

TRTR

DEV

ABAP

QAS

ABAP

Export

TRTR

TR Transport Requests

Import after Upgrade

Corrections

TRExport

TR

TransportBuffer

ExportTR

Export

TransportBuffer

TransportBuffer

TransportBuffer

� In the standard three-system landscape, each system is updated in the standard transport sequence. Tasks such as Customizing, applying patches, and custom developments are performed in the development system and transported to the quality assurance and production systems.

� During the upgrade of the development and test systems no development roll-outs or other changes in the production landscape should be done ('code freeze'). Otherwise SPDD and SPAU transports have to adjusted as well leading to higher efforts ('double maintenance').

� Emergency situations may arise during the upgrade project requiring a change to be made to the production system. If such situations arise, handle them on an individual basis and always use SAP Change Management tools to make any corrections.

� Note: All changes to the production environment should be manually reproduce in the upgraded development system. Customizing transports between different releases are not supported, repository transports are critical (e.g. SAP note 1090842).

� Consequences of inconsistent transport management during upgrade projects:

� SPDD and SPAU transports created during the upgrade of development system may be not valid for test and production system.

� Results of the upgrade of one system in the landscape can not be used as reference for upgrade of another system.

� Identification of modifications and creation of test cases can take much longer without appropriate documentation.

© SAP AG ADM326 10-34

Upgrade Project Landscape

� Make early experiences in the upgrade project system:

� Technical upgrade procedure� Modification adjustment� Test of customer developments in new release� Upgrade customizing� Check functionality of processes in new release� Test of core business processes

� Reduce dual maintenance period:� Do high effort work in upgrade project system before

upgrade of system landscape� Reduce time window between upgrade of DEV

and PRD system

� Always 3-system-landscape for maintenance (only emergency corrections allowed)

� Plan and communicate code freeze time!

© SAP AG ADM326 10-35

Adjustments in an Upgrade Project

ModificationDefinition: any change to an SAP-owned

workbench object

Types of modifications� Modifications made due to SAP notes� Customer modifications

� Who “owns” the modification?� What is the business justification for retaining

the modification?

� Enhancements� E.g.: user exits - these are generally not issues

in upgrades (Unicode – SAP note 553110)

What objects must be adjusted?� Objects that have been modified by customer

AND changed by SAP

What must be decided?� Keep new SAP-standard or modify again

Custom ObjectsDefinition: any development in the

customer namespace

Custom reports & transactions� Generate programs (SGEN) post-upgrade to

identify syntax errors (or use UCCHECK)� Key issue: degree of reliance on SAP

standard objects� Pure custom development should require

little/no work

Custom ABAP Dictionary objects� Generally require little re-work – any errors

are identified immediately during activation of new repository

“Cloned” objects� SAP-standard objects copied into the

customer namespace� Cloned objects present unique challenges –

possible approach: re-clone them on the new release.

CustomizingStudy release notes; generate Upgrade IMG (SPRO_ADMIN)

Blueprint

� 367676 4.6 to 6.10

� 452229 6.10 to 6.20

� 689951 6.20 to 6.40

� 857904 6.40 to 7.0

� e.g. ABAP and Unicode, ABAP objects, Internal tables, Open SQL, ABAP Compiler, ABAP runtime

� Integration (R/3 Plug-In): http://service.sap.com/R3-Plug-In

� Queries Please read SAP note: 672784

� Batch Input Please read SAP note: 311440

� Authorizations: SAP_NEW profile contains authorizations for new checks in functions .

� After the upgrade:

� To copy the latest SAP default values while retaining your own modifications, call transaction SU25 (steps 2 and 3)

� Delete all the individual profiles from SAP_NEW that refer to releases that are lower than the source release for the upgrade.

� Go through the profile SAP_NEW and decide for each authorization object, into which customer profile the authorizations need to be copied.

© SAP AG ADM326 10-36

??? Testing all processes in

use

� Goodeffort-risk balance

High avail-ability

e.g. iterative testing

Testing only core business

processes

Unsufficienttest

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 effort� Set-up efficient test procedures and test KPIs� Identify appropriate training scope and efficient training methods

Make sure that no big surprises occur after upgrade weekend

Testingeffort

Risk

No testing

Evaluatetest automation

Rethink yourtest management

Final prep. for cutover

© SAP AG ADM326 10-37

Test Stages –Overview

Realization

Realization

Productionpreparation

tests

Operation

Functionaltests

e.g. SAP Support Packages

Phase

Developer tests

Functional tests

Scenario tests

Integration tests

Technical system tests

User acceptance tests

Regression tests

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

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 AG ADM326 10-38

� Hope for the best

Evol

utio

nof

test

ing

� Accelerated Testing Solution for SAP

� Automated record and replay

� eCATT unit testing plus manual integrated testing

� Manual testing

]

]

]

Business Process Test

Script

Test Strategies

� Automated Testing:

� Human intervention only for triggering the test process, BUT not running it

� Dramatically reduced test period; time available for “value added/random manual tests

� Immediate detection of errors

� Clear test case results (OK or not OK)

� Greater degree of reliability; repeatability

� Detailed test logs; troubleshooting

� Manual Testing

� Potentially greater flexibility in design, creation & execution of test cases. Manual testers can use expert knowledge to fill in gaps about test requirements

� Identification of “real” issues; is functionality not working or temporary condition due to network connectivity issues?

� Testers can perform random tests that meaningfully extend the scope of the test plan

© SAP AG ADM326 10-39

© SAP 2009 /

�Using the Impact Analyzer, you can analyze which user interfaces are affected for which roles and users if you activate a business function

�This 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

Via Transaction SFW5

Impact Analyzer

� It evaluates the following user interfaces:

� Transactions

� Portal i-Views and portal roles

� Reports/programs of the ABAP-based system

� ABAP WebDynpro applications

© SAP AG ADM326 10-40

�Test cases are shipped with the 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 workbench

�Test 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 an EHP After Installing an EHP

Where to Find Test Case Templates

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

© SAP AG ADM326 10-42

Big Bang versus Phased Upgrades

Question� What 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

© SAP AG ADM326 10-43

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.

© SAP AG ADM326 10-44

Upgrade in Complex Landscapes:Upgrade Dependency Analyzer

Upgrade ECC

Potential release dependenciesbetween Upgradeable Units

� Identify release dependencies� Which Upgradeable Units to

upgrade at the same time

CRM

Self Services

Learning Solution

...

SRMSEM

R/3�CRM

Self Services

Learning Solution

...

SRMSEM

?

ECC

� Prerequisites and assumptions:

� Upgrade Dependency Analyzer always compares two systems, one system that is being upgraded vs. one other system in the system landscape

� The result of a dependency analysis is a predefined dependency statement and optionally an SAP note

� Dependency statements refer to separately installed systems/upgradeable units

� Only functionality/processes are considered that are currently used, e.g. an analysis result of 'no upgrade dependencies' means, that functionality/processes that worked before the upgrade, will still work properly after the upgrade

� No information about new functionality/processes, because they often require the upgrade of both components

� Only information about standard SAP functionality/processes, not about custom developments or self-defined customer processes

� Restricted to the ‘top 80%' of upgradeable units, no individual software components considered

� All software components that are part of one system will be upgraded at the same time. Upgrade Dependency Analyzer delivers no information about possible combinations of software component versions within one system.

© SAP AG ADM326 10-45

Upgrade Dependency Analyzer Customer View (1)

� Planning an Upgrade?

� Find out dependencies within your SAP system landscape!

� Example:

http://service.sap.com/uda

© SAP AG ADM326 10-46




� Example:

� Upgrade one system to SAP ECC 6.05

© SAP AG ADM326 10-47




� Example:


� Searching for dependencies to second system SAP SCM 7.0

© SAP AG ADM326 10-48


�Accessible via SAP Service Marketplace�Also 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.

© SAP AG ADM326 10-49

� 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

© SAP AG ADM326 10-50

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

� High level technical planning� Shows known dependencies on technical

level according to categories:� Dependency exists� Conditional dependency exists� Currently no dependencies

� 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?


� 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 List� Detailed analysis on process level� Shows predefined scenarios/processes before

and after an upgrade according to categories:� Already available� Additionally available after upgrade� Not available after upgrade

© SAP AG ADM326 10-52

Technology Aspects

� Hardware requirement on new release: server, front end, network

� Sizing forecast and system configuration for new release

� Planning of OS, DB and SAP system upgrades

� Testing and validating of backup strategy for upgrade and on the new release

� Performing technical upgrade on the whole system landscape

� Post-upgrade activities including performance monitoring

� Since the requirements of the new release are changing, we need a sizing forecast which in turn requires changes to the configuration. Finally the whole environment is concerned, for example the server hardware, the client hardware, the network, the operating system and the database. Especially when changing the operating system, other software on this computer has to be tested. For example the backup software has to be tested.

� Because of the new requirements, performance monitoring gets more important after the upgrade.

© SAP AG ADM326 10-53

SAPup / SAPJup

� Standard SAP upgrade tool for ABAP and Java� Execution of main upgrade activities� For an ABAP system you require SAPup; for a

Java system you require SAPjup.� The tools share a similar architecture � consist

of an upgrade program (SAPUp or SAPJup) and a control program (Upgrade GUI or SDT GUI).

� New upgrade GUI layout and simplified upgrade procedure for ABAP (SAP NW 7.01), Java (SAP NW 7.1) and dual stack (SAP NW 7.1) upgrades

� Established system switch upgrade technology is also available for Java (SAP NW 7.1) and dual stack (SAP NW 7.1) upgrades

� Synchronized upgrade procedure for dual stack SAP NW 7.0 upgrades

DESCRIPTION

BENEFITS

� SAPup and SAPJup are part of the upgrade software kit shipped by SAP

� More Information is available on SDN:http://sdn.sap.com/irj/sdn/upgradetech

ACCESS

© SAP AG ADM326 10-54

Bind parts of SAP Enhancement Package 5 forSAP ERP 6.0 to the SAP ECC 6.0 Upgrade

With the upgrade to SAP ECC 6.0 SR3 it is possible for the first time to bind the relevant parts of an SAP Enhancement Package for SAP ERP 6.0 to the upgrade. This includes also the necessary SAP Support Packages.

� The SAP Enhancement Package 5 for SAP ERP 6.0 can be bound to the upgrade by providing a text and XML file to the Upgrade. This text and XML files contain the stack configuration, calculated and created by the Maintenance Optimizer.

© SAP AG ADM326 10-55


t

Begin of availability

End of maintenance

SAP Support Package

SAP R/3 4.6CSAP_APPL 46C

SAP ECC 6.0SAP_APPL 600

SAP ECC 6.05SAP_APPL 605

Bind SAP Support Packages of thedestination release to the upgrade!

60

20

2

� SAP Support Packages on the start release are produced also after a potential destination release has been shipped.

� SAP R/3 4.6C SAP_APPL Support Package 60 for example has been shipped after the shipment of SAP ECC 6.0.

� On each potential destination release, Support Packages are available, too.

� There is some relation between the Support Packages: usually fixes have been mad at the same time for different releases.

� An upgrade from SAP R/3 4.6C SAP_APPL Support Package 60 to SAP ECC 6.0 SAP_APPL Support Package 0 would partially downgrade the system.

� But: it is possible to bind Support Packages to the upgrade: you can go directly to ECC 6.0 SAP_APPL Support Package 20 or higher (in this example).

� Advantages:

� No need to supply the SAP Support Package on the destination release after the upgrade

� No (temporary) downgrade

© SAP AG ADM326 10-56

Handling of Add-ons / Software Components

Depending on the situation in the old and the new release, during an upgrade the following is possible:

� Additional software component is been newly installed as standard component

� Existing Add-on becomes part of standard delivery� Existing Add-on becomes part of other

standard components� Existing Add-on is upgraded� Existing Add-on is kept as it is� Existing Add-on is been deleted � Add-on is been newly installed

� Depending on the situation in the old and the new release, during an upgrade the following is possible:

� Additional software component is been newly installed as standard component: for example the software components from the Extension Set

� Existing Add-on becomes part of standard delivery: for example in SAP R/3 4.6C IS-U is an Add-on, in SAP ECC 6.0 it is in standard delivery

� Existing Add-on becomes part of other standard components: for example the Plug-in (PI) is an Add-on in SAP R/3 4.6C, but part of standard components in SAP ECC 6.0

� Existing Add-on is upgraded: for example from a release fitting the old SAP R/3 4.6C to a release fitting the new SAP ECC 6.0

� Existing Add-on is kept as it is: for example because it fits just as well the old SAP R/3 4.6C as the new SAP ECC 6.0 (option 'keep')

� Existing Add-on is been deleted: because it is not needed any longer (active and passive deletion)

� Add-on is been newly installed: it is possible to install a new Add-on during the upgrade

© SAP AG ADM326 10-57

Upgrade Downtime

up up

down

SAPup:PREPARE

&repository

import


backup?go/no-go decisionbackup?

transports & manual tasks

Businessvalidation

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

© SAP AG ADM326 10-58

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

© SAP AG ADM326 10-59

Check Technical PrerequisitesOS/DB Dependencies

Check impact and dependencies early!!!

� Perform your OS/DB upgrade in advance of the SAP upgrade

Key Take Aways

� Check the Product Availability Matrix (PAM) to determine if any upgrade are required to the OS/DB via Service Marketplace quick link: /pam

� Oracle customers: SAP NetWeaver 7.0 (and thus ECC 6.0) only run on Oracle 10� For new installations 64bit OS-/DB releases are mandatory since SAP NetWeaver 7.0� For upgrades to SAP NetWeaver 7.0 64bit OS-/DB releases are recommended

OS/DB Upgrades

© SAP AG ADM326 10-60

Check Technical PrerequisitesSAP GUI Options

For existing functionality SAP GUI is still the default UI� SAP Enterprise Portal is not required unless portal-specific

applications are used (e.g. Employee Self-Service)

Key Take Aways

� SAPGUI 7.10 is the recommended GUI for use with SAP ECC 6.0� SAPGUI 6.40 also supports SAP ECC 6.0, check dependencies during planning

of SAPGUI rollout� SAP GUI for Java still offered for Macintosh, Linux, etc.� SAP GUI for HTML still supported via ICM (Integrated ITS)

� Check the Product Availability Matrix (PAM) for technical prerequisites about your SAP GUI via Service Marketplace quick link: /pam

SAP GUI

© SAP AG ADM326 10-61

SAP Business Connector

SAP BC and SAP XI/PI are based on different technologies� SAP BC 4.6 and 4.7 based on webMethods‘

Integration Server 4.6� SAP XI/PI based on open standards (e. g.

BPEL4WS for business processes)

Only parts of an SAP BC implementation can be migrated to an SAP XI/PI implementation� XSLT mappings (offered since SAP BC 4.6)

Any custom programming done on the basis of SAP BC will likely not be reusable in the SAP XI/PI context� Example: SAP BC flow language

Customers still starting new projects with SAP BC should consider XSLT for mappings

� SAP BC to SAP XI/PI Migration Guide

SAP note 309834 – SAP BC support and release strategy� Supported SAP BC releases 4.6 and 4.7� Supported JDK versions 1.3 and 1.2 (with

limitations) only� Supported operating systems

• Windows NT and 2000• Linux• Sun Solaris 8 and higher (32-bit only)• IBM AIX 4.3 and higher (32-bit only)• HP-UX 11.0 and higher (32-bit only)

OSS Support (SAP note 571530)� The end-of-maintenance dates for the two BC

versions are defined as follows:- BC 4.6: December 31, 2008.

� - BC 4.7: December 31, 2009.� Customers that want to keep a BC running that is

not out of maintenance should read the announcement of BC 4.8 in SAP note 1094412.

© SAP AG ADM326 10-62

Internet Transaction Server (ITS)

� ITS 6.20 is long term supported for SAP products based on SAP Netweaver 2004 (6.40) and below as long as these products are supported

� ITS 6.20 standalone cannot be used with SAP Netweaver 7.0 (SAP Kernel 7.00). ITS services which use Flowlogic and WebRFC are no longer supported in system based on SAP Netweaver 7.0Note 709038

� Because SAP ICM (integrated ITS) is part of the SAP kernel, the maintenance is as long as the maintenance for the SAP kernel

For detailed information please check Platform Availability Matrix (PAM) to get up to date information (http://service.sap.com/pam)

© SAP AG ADM326 10-63

� SAP will no longer maintain the most ESS standard services based on Standalone ITS Technology as of SAP ERP 6.0. Note 870126.

� The functional scope of ESS will be ensured by SAP. SAP recommends using ESS based on Web Dynpro (Java).

� For the implemented ESS scenarios several SAP components have towork together (Business Package, XSS, Portal, backend). The combination and dependencies of them is dependent on the implemented scenarios and could be different in the individual releases.

Example: Employee Self Service (ESS)

© SAP AG ADM326 10-64

Planning

Get Support from SAP!

Source: DSAG-360 -Customer Feedback Program: Upgrade (March 2008 – 138 participants – 138 companies)

Execution

64 %Estimate thecosts and efforts

38 %Define & assignproject resources

17 %Define Business Case

Upgrade-Services:

QUA, QUE (TUP),

UVA

75 %Efficient testing

43 %Downtimeminimization

21 %Project-management

62 %Modificationadjustments

21 %Enduser trainings

31 %IT-infrastructure/

sizing

21 %Others

SA

P U

pgrade Factory, Upgrade C

oaching, S

afeguardingforU

pgrades

Interoperability

39 %Impact on thesystem landscape

25 %Search & find upgraderelated information

17 %

KnowledgePlatform

and Upgrade Depen-dency

Analyzer

More information available at http://service.sap.com/upgradeservices

© SAP AG ADM326 10-66

Customers’ Perceived Challenges –Worldwide Results Survey

Plan Build


Efficient testing

55%

69%

Downtime minimization

47%

Justify budget

5%

Project management

Cost/Effort Estimation

17%


Others


19%

Participants: North America (Jan 2008), Brazil (March 2008), Germany (March 2008), Japan (March 2008), Australia (April 2008), Sweden (April 2008), China (May 2008) and India (May 2008), UK & Ireland (March 2008).


Define and allocateproject team/resources

46%

28%

Downtimeminimization strategy

44%

Interoperability/Dependencies

15%

Assess impact onexisting solution

29%


4%Others


48%

N = 1,362 N = 1,362

Find information on upgrade methods & tools

© SAP AG ADM326 10-67

Average Durations of ERP Upgrade Projects

Start ReleaseTarget Release

n/a4 25 2n/aCombined Upgrade & Unicode Conversion- Single CP

n/a

6 3

< R/3 4.6C

7 2

5 3

R/3 4.6C

4 24 2Upgrade only

n/a4 3Combined Upgrade & Unicode Conversion- MDMP

R/3 4.7 ECC 5.0ERP 6.0

duration in months; results derived from SAP Upgrade Experience database 11/2008

© SAP AG ADM326 10-68

Additional Hardware Requirementsfor an Upgrade to ECC 6.0 non-UNICODE

Start-Release:

SAP Note:

4.0B

113795

4.6B

323263

4.5B

178616

4.6C

517085

4.7/1.10

752532

4.7/2.00

778774

5.0

901070

100,0%

80,0%

60,0%

40,0%

20,0%

0,0%

� Memory Application Server � CPU Application Server

Absolute additional hardware consumption for an upgrade from a source Release to SAP ECC 6.0

The notes contain only DELTA sizing information from a source release to the next release.

� This chart above shows absolute additional hardware consumption for an upgrade from different source releases to SAP ECC 6.0

� This chart is only valid for a pure technical upgrade.

� Absolute additional hardware requirements are shown in the figure.

� The SAP notes mentioned contain only delta information between one release and another, for example, SAP Note 901070 contains delta hardware requirements between SAP ECC 5.0 and SAP ECC 6.0.

� To check sizing plausibility and proactively optimize configuration use:

� Continuous Quality Check for Upgrade (service is part of Enterprise Support)

- Analysis session Load-based analysis Parameterization of future landscape

- Verification session provides corrective measures for avoiding potential bottlenecks

© SAP AG ADM326 10-69

� UTF-8* : up to +10%ORACLE, DB/2 (AIX)

� UTF-16 : + 20 to 60%SQL Server, DB/2 (AS400), MAX DB (7.0)

Database size

� UTF-8� Almost no change

due to efficientcompression

Network Load

Additional Hardware Requirements for Unicode

� +30%� Depending on

existing scenario(MDMP, double byte)

CPU

� +50%� Application servers

are based on UTF-16internally

RAM

Based on parallel benchmarking of Unicode and non-Unicode test systems. The CPU and RAM figures are measured average numbers and will be different for different transactions

*35% is the observed maximum in growth for small systems (db size < 200 GB).* 10% is the observed maximum for bigger systems (db size > 200 GB).

1. Priority

� All of the values are average values. Also refer to SAP note 1139642. Based on the real scenario that is used in the system to be upgraded those values may be very different from the ones displayed here. For example, measurements in customer system using UTF-8 based databases showed that more than 90% of the databases actually have shrunk about 10%. The main reason for this decrease is that with the Unicode conversion also an implicit database re-organization is performed freeing unused space. Particularly, with large databases such re-organizations are carried out seldom because it impacts the availability and performance of the system.

© SAP AG ADM326 10-70

Average Cost Structure of ERP Upgrade Projects

2-5%

0-5%

10-20%

25-60%

10-30%

0-20%

0-10%

15-25%

Software license

Hardware / infrastructure

SAP technical upgrade

Custom code andmodification adjustmentTesting

Project management

Change management /trainingSupport

© SAP AG ADM326 10-71

How to Keep Upgrade Costs Down

� Reduce DB size and growth

� Optimize system configuration

� Optimize operation

� Outsource temporary hardware requirements

IT Infrastructure

Set-up

� Analyze downtime drivers

� Choose downtime optimization tools and procedures that meet best your requirements

� Define emergency procedures during cut-over

Business Downtime

� Eliminate unused custom code

� Assess if you can return to standard with new release or enhancement package

� Avoid modifications and encapsulate custom developments

Custom Code

� Assess efficiency of test organization

� Define standard regression test cases

� Use test administration and automation tools

� Focus on critical areas

Testing

� Identify training requirements early

� Improve learning material creation and effectiveness

� Use state-of-the-art learning material distribution and training methods

Training

Reduce Upgrade Costs by

Implement technical risk management / quality assurance

© SAP AG ADM326 10-72

�> BW 7.0: Web Reporting deployment

�> CRM 2007: UI Migration

�> CRM 2005:VMC deployment

Release DependendTopics

� Business downtime: Ramp down/ ramp up of interfaces

� Business downtime: Higher requirements

� Downtime: LiveCache

� Compatibility:LC Build, com routines, SPs

� Transition: Mobile Scenarios

� Infrastructure: Java Deployment

� Upgrade: Industry Solutions

� Compatibility:Add-ons

� Conversion: MDMP

Product Specific Challenges

1-3 mths1-3 mths2-3 mths3-4mths3-4 mths4-5 mths4-6 mthsProject Duration

1-6h1-6h2-8h2-6h5-12h*3-10h3-10hTechnical Downtime

500-1500 mods

2500-10000 cust obj

Adjustment Requirements

NW EPNW PINW BWSRMSCMCRMReference:ECCTopic

Comparison of Upgrade Experiences in Business Suite and NetWeaver

Legend: effort/duration is lower than comparable to higher than ECC reference

� SAP Business Suite and SAP NetWeaver products are compared with average SAP ECC Upgrade project.

� The average SAP ECC upgrade project is defined based on figures from SAP Upgrade Experience Database from Nov 2008 (~290 entries) for upgrades to SAP ECC 6.0.

� Comments:

� * SCM downtime: 2-6h SCM Server + 3-6h Live Cache export/import

© SAP AG ADM326 10-73

SAP Upgrade Experience Databaseprovides orientation on� Project duration � Business downtime� Satisfaction with the upgrade� Etc.

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.

© SAP AG ADM326 10-74

�

Questionnaire Used for the SAP Upgrade Experience Database

Only upgrades of production systems are measured

A standardized questionnaire (online) is used for data collection (available in English and German versions)

The questionnaire is tailored to tracking upgrade experiences

Many questions can be answered by simple mouse clicks

At present, the database holds data for upgrades to SAP ECC 6.0 and for upgrades to SAP ECC 5.0

© SAP AG ADM326 10-75

Feedback from Customers who have Completed the Upgrade

95 % of our customers

who upgraded to ECC 6.0

were satisfied or even gave a better rating

Very satisified

More than satisfied

Satisfied

Less satisified

Not satisfied

Based on 212 upgrades

Proven approach andtools

Very few highly criticalproblems Qualified support

Excellent documentation

© SAP AG ADM326 10-76

Upgrades to SAP ECC 6.0: Number of Datasets in Database by Source Release

168

30 32

103Total: 333upgrades

SAP ECC 5.0

SAP R/3 Enterprise

SAP R/3 4.6C

SAP R/3 <4.6CThe following slides provide the results for the source releases SAP R/3 Enterprise and SAP R/3 4.6C.

� Results for the other source releases will be provided as the number of datasets in the SAP Upgrade Experience Database increases.

© SAP AG ADM326 10-77

Upgrades to SAP ECC 6.0: Approach in Upgrades by Source Release

Approach in upgrade project

20%

4%

12%

64%Technical upgrade only

Total: 103upgrades

Functional upgrade

Strategic upgrade

Technical upgrade + subs.functional enhancements

Approach in upgrade project

14%79%

5%2%

Technical upgrade only

Total: 167upgradesFunctional upgrade

Strategic upgrade

Technical upgrade + subs. functional enhancements

SAP

R/3

Ent

erpr

ise

SAP

R/3

4.6

C

� Annotation:

� Technical upgrade + subs. functional enhancements = technical upgrade with subsequent implementation of additional functional or strategic enhancements

� Functional upgrade = technical upgrade with additional functional enhancements

� Strategic upgrade = technical upgrade with strategic enhancements

� Findings:

� Most upgrade projects to SAP ECC 6.0 were performed using the upgrade approach “Technical upgrade only.”

� On the other hand, the diagrams on the next page indicate that the new functionality provided with SAP ECC 6.0 is one of the main reasons to upgrade. This is in accordance with the experiences of other SAP upgrade projects.

© SAP AG ADM326 10-78

Upgrades to SAP ECC 6.0: Reasons for Upgrades by Source Release

Reasons for upgrade

0% 25% 50% 75% 100%

Replacement / elimination of modifications and / orcustomer specific development by SAP standard

System landscape consolidation / Integration ofindustry solutions

Business Innovation

Leverage latest technology

Legal compliance

End of mainstream or extended maintenance

Improve usability of existing solution

Functional requirements


Reasons for upgrade

0% 25% 50% 75% 100%

Replacement / elimination of modifications and / orcustomer specific development by SAP standard

System landscape consolidation / Integration ofindustry solutions

Business Innovation

Leverage latest technology

Legal compliance

End of mainstream or extended maintenance

Improve usability of existing solution



SAP

R/3

Ent

erpr

ise

SAP

R/3

4.6

C

� How to read the charts:

� More than one reason per upgrade could be selected. The results for each reason category are standardized to the number of upgrades of the given sample.

© SAP AG ADM326 10-79

Upgrade strategy

23% 77%Total: 166upgrades

Downtime minimized

Resource minimized

Upgrade strategy

81%19% Total: 102upgrades

Downtime minimized

Resource minimized

Upgrades to SAP ECC 6.0: Upgrade Strategy by Source Release (System Switch Upgrade)

SAP

R/3

Ent

erpr

ise

SAP

R/3

4.6

C

© SAP AG ADM326 10-80

Upgrades to SAP ECC 6.0: Overall Satisfaction with Upgrade Approach by Source Release

Overall satisfaction with upgrade

33%

46%

15%6%

Total: 102upgrades

Very satisfied

More than satisfied

Satisfied

Less than satisfied

Overall satisfaction with upgrade

4%

18%

41%

36%

1%

Total: 165upgrades

Very satisfied

More than satisfied

Satisfied

Less than satisfied Not satisfied at all

SAP

R/3

Ent

erpr

ise

SAP

R/3

4.6

C

� Annotation:

� The following satisfaction levels could be selected:

� ++ Very satisfied

� + More than satisfied

� O Satisfied

� - Less than satisfied

� -- Not satisfied at all

© SAP AG ADM326 10-81

Upgrades to SAP ECC 6.0: Customers’Perceived Challenges by Source Release

Customers' perceived challenges

0% 25% 50% 75% 100%

End-user training

Minimize downtime

Efficient testing

Modification adjustment

IT infrastructure / sizing

Project Management

Justify budget for project / value proposition

Cost / effort estimation


Planning phase

Building Phase

SAP

R/3

Ent

erpr

ise

SAP

R/3

4.6

C

Customers' perceived challenges

0% 25% 50% 75% 100%

End-user training

Minimize downtime

Efficient testing

Modification adjustment

IT infrastructure / sizing

Project Management

Justify budget for project / value proposition

Cost / effort estimation


Planning phase

Building Phase


� More than one category per upgrade could be selected.

© SAP AG ADM326 10-82

Upgrades to SAP ECC 6.0: Project Duration in Weeks by Source Release


0 4 8 12 16 20 24 28 32 36 40 44 48 52Weeks

Max: 36,6

Median: 21,0

Min: 12,0


Range of values(w/o outlier values)


0 4 8 12 16 20 24 28 32 36 40 44 48 52Weeks

Max: 31,9

Median: 18,0

Min: 8,1





SAP

R/3

Ent

erpr

ise

SAP

R/3

4.6

C

� Question asked:

� “Please specify the duration of your upgrade project up to the initial go-live (in weeks).”


� Distribution of values: shows the frequency distribution of all measured values (in weeks, without cutting at the edges).

� Range of values: by cutting 10% of the number of values at each end of the frequency distribution outlier values are excluded. The length of each bar indicates the variance of the measured values.

© SAP AG ADM326 10-83

Upgrades to SAP ECC 6.0: Duration of Project Phases in Weeks by Source Release

Duration of single project phases in weeks

2,0

3,0

6,0

2,0

2,0

18,0

0 5 10 15 20 25

Production cutover & support phase

Final preparation for cutover phase

Upgrade realization phase

Upgrade blueprint phase

Project preparation phase

Weeks

Project duration (total)

SAP

R/3

Ent

erpr

ise

SAP

R/3

4.6

C

Duration of single project phases in weeks

2,0

3,0

8,0

3,0

3,0

21

0 5 10 15 20 25

Production cutover & support phase

Final preparation for cutover phase

Upgrade realization phase

Upgrade blueprint phase

Project preparation phase

Weeks

Project duration (total)

� Question asked:

� “Duration of project phases according to the SAP Upgrade Roadmap (in weeks).”


� For each project phase, the median value of all answers is shown. In a project, overlaps or gaps between the project phases are possible.

© SAP AG ADM326 10-84

Business Downtime* in Hours by Source Release, without Unicode Conversion

Business downtime* in hours

0 12 24 36 48 60 72 84 96 108Hours

Max: 65,0


Median: 34,0Range of values

Min: 15,0



0 12 24 36 48 60 72 84 96 108Hours

Max: 86,2Min: 22,9

Median: 48,0 Range of values


* Business downtime = total time (planned and unplanned) that the system / solution is not available for end users. This includes the technical downtime plus the time necessary for the data backup, final tests, etc., before the productive environment is released for end users.

SAP

R/3

Ent

erpr

ise

SAP

R/3

4.6

C Distribution of values

� Question asked:

� “Assuming a 24x7 hours operation of the production system, how many hours was the production system unavailable for the end users?”


� Distribution of values: shows the frequency distribution of all measured values (in hours, without cutting at the edges).


� Only upgrades that followed the “Downtime minimized“ upgrade strategy were taken into account. No Unicode conversion was performed.

� Findings:

� The business downtime was <= 48 hours (2 days)

� SAP R/3 Enterprise: for 74% of all measured upgrade projects (for 88% <= 60 hours)

� SAP R/3 4.6C: for 53% of all measured upgrade projects (for 65% <= 60 hours)

© SAP AG ADM326 10-85

Upgrades to SAP ECC 6.0: Modules* (Business Scope) Used in the Upgraded ECC System

Modules* used in ERP component

0%

25%

50%

75%

100%

CO FI HR LE MM PM PP PS QM SD


* Despite the fact that SAP R/3 modules are no longer applicable in SAP ECC 6.0, customers were asked to describe the business functionality of the upgraded SAP software in terms of the classic SAP R/3 modules (e.g., “FI”) in order to provide a comparison with the business scope of the upgraded SAP software.

Modules* used in ERP component

0%

25%

50%

75%

100%

CO FI HR LE MM PM PP PS QM SD


SAP

R/3

Ent

erpr

ise

SAP

R/3

4.6

C


� More than one SAP R/3 module could be selected:

� the results for each module are standardized to the number of upgrades of the given sample.

� Conclusion / findings:

� A broad coverage of components, and therefore a wide scope of business functionality, can be observed in the upgraded systems.

© SAP AG ADM326 10-86

Upgrades to SAP ECC 6.0: Database Size in GB by Source Release

Database size in GB

0 1000 2000 3000 4000 5000 6000GB

Max: 1870Min: 122

Median: 375



Database size in GB

0 1000 2000 3000 4000 5000 6000GB

Max: 1340Min: 78

Median: 340 Range of values(w/o outlier values)




SAP

R/3

Ent

erpr

ise

SAP

R/3

4.6

C

� Questions asked:

� “What was the used database size in your productive environment (in GB)?


� Distribution of values: shows the frequency distribution of all measured values (in GB, without cutting at the edges).


� Findings:

� SAP R/3 Enterprise: 80% of the upgrades � DB size <1000 GB

56% of the upgrades � DB size < 500 GB

� SAP R/3 4.6C: 86% of the upgrades � DB size <1000 GB

62% of the upgrades � DB size < 500 GB

© SAP AG ADM326 10-87

Upgrades to SAP ECC 6.0: Number of Projects by Number of Users and Source Release

Number of users

9%

17%

17%31%

15%5%5%

1%

Total: 99upgrades

1 - 99

100 - 249

250 - 499

500 - 999

1000 - 1999

2000 - 4999

5000 - 9999=10000

Number of users

3%1%

15%

18%

19%20%

16%

9%

Total: 166upgrades

1- 99

100 - 249

250 - 499

500 - 999

1000 - 1999

2000 - 49995000 - 9999 =10000

SAP

R/3

Ent

erpr

ise

SAP

R/3

4.6

C

© SAP AG ADM326 10-88

Lessons Learned:Project Management

Make early experiences in the upgrade project system• Technical upgrade procedure• Modification adjustment• Test of customer developments in new release• Upgrade customizing• Check functionality of processes in new release• Test of core business processes

Reduce dual maintenance period• Do add. effort work in upgrade project system before upgrade of system landscape• Reduce time window between upgrade of DEV and PRD system

Test output programs• Most companies focus on the business process testing and forget about print

programs and forms

Involvement and commitment• Early Involvement of key users and management commitment are key success

factors

PM

� Plan and communicate code freeze time!

© SAP AG ADM326 10-89

Lessons Learned:Functional Aspects

Good housekeeping drives efficiency of upgrade• Archiving, Cleansing of un-used custom code and SAP modifications• Document table changes thoroughly and their usage in custom programs

The older release the more money spent on training• Significant for customers starting with SAP R/3 4.5B and below (Enjoy

transactions, tree structures…)• Utilize computer based training: Easy to distribute and review at the

convenience of the user

Industry Add-on• Customers with Industry Add-ons should review the specific upgrade guides

Tackle custom developments as early as possible• The faster the development team can have access the faster business process

issues can get resolved

Modification adjustments and testing are key cost drivers• The better the documentation and existing test procedures, the easier and less

time consuming those project tasks will be)

© SAP AG ADM326 10-90

Lessons Learned:Technical Aspects

Upgrade Strategy• „Downtime minimized“ method should be used• In order to get a realistic forecast about the expected downtime, a Sandbox

upgrade with representative configuration and data set is highly recommended

Distribution of new SAP GUI version should be started early

Check impact and dependencies early• With the help of the Product Availability Matrix and PCL e.g. On OS/DB compliance,

availability of country versions and 3rd party products, ITS and dependencies to other SAP products

Perform test upgrades over and over until you get it right• A key for success mentioned by many customers

Verify sizing - leverage SAP GoingLive Functional Upgrade Check • Consider the additional hardware requirements

Install and use SAP Solution Manager

© SAP AG ADM326 10-92

Documentation

New with SAP NetWeaver 7.0 :Master Guides reflect new concept:�General information provided (mapping to

new building blocks – systems with usage types, standalone engines, clients) and planning information (landscape-related topics– SAP NetWeaver Administrator, SAP Solution Manager, SLD, SLM, …)

�One section for every IT scenario providing information of its system landscape and implementation/upgrade sequence

For the installation of a system with usage types, only one Installation Guide – SAP NetWeaver required�Comprises the information for your

platform/database and all usage types�No longer separate guides required for BI,

EP, etc.�OS Dependencies included/no longer

required due to Prerequisite Checker

Description:� Documentation provides information required to

understand and perform software life-cycle tasks• Planning Guides ([Upgrade] Master Guide, …)• Installation Guides• Upgrade Guides• SAP Support Package Stack Guide• SAP Library documentation• Tool documentation (F1 help, …)

� Profiling prepared: in the future, it is planned that more specific guides can be created on demand that only contain information for required usage types and operating systems

© SAP AG ADM326 10-93

Information Sources

ERP Upgrade specific information

Statisticsor

screen shot

SAP ERP Solution Browser

SAP Upgrade Newsletter

Enhancement Package info center

SAP Upgrade Info Center(www.service.sap.com/upgrade)

© SAP AG ADM326 10-94

Information at SAP Service Marketplace

Upgrade� Homepage: http://service.sap.com/upgrade� Upgrade services: http://service.sap.com/upgradeservices� Upgrade Dependency Analyser: http://service.sap.com/uda

SAP ERP� Homepage: http://service.sap.com/erp� Development News: http://service.sap.com/developmentnews� Release Notes: http://service.sap.com/releasenotes� Release Strategy: http://service.sap.com/releasestrategy� Maintenance Strategy: http://service.sap.com/maintenance� Scenario & Process Component List: http://service.sap.com/scl

SAP Enhancement Packages� SAP ERP enhancement package Installation: http://service.sap.com/ehp-inst� SAP ERP enhancement package Homepage: http://service.sap.com/erp-ehp� EHP Installation Guides for existing products

SAP NetWeaver:� Homepage: http://www.sdn.sap.com/irj/sdn/netweaver� SAP NetWeaver Administrator: SDN Netweaver Administration� System Landscape Directory: https://www.sdn.sap.com/irj/sdn/nw-sld� Software Lifecycle Manager: https://www.sdn.sap.com/irj/sdn/softwarelogistics

© SAP AG ADM326 10-95

� Regional and local SAP upgrade news is proactively distributed on a quarterly basis to customers

� No. of recipients today: more than 10,000� Available language/country versions:

� English� German� Japanese� Russia

� Upgrade News - Content:� Focus topic� Solution-specific information, for example, mySAP ERP� SAP upgrade tools, services and content� …

SAP Upgrade Newsletter – Register NOW!

For continuous upgrade news right to your desk, subscribe to the SAP Upgrade Newsletter: SAP Upgrade Newsletter

© SAP 2010

Agenda: Enhancement Packages



10. Planning and Preparation 11. Enhancement Packages

12. Unicode Conversion13. Tools and Services14. SAP Notes for this Course


© SAP 2010


Contents:� The idea of the enhancement packages

� Binding enhancement packages to the upgrade


Since the upgrade to ECC 6.0 SR3 it is possible for the first time to bind the

relevant parts of an enhancement package to the upgrade. This includes also the necessary SAP Support Packages.

Bind SAP ERP Enhancement Package 5 for SAP ERP 6.0 to the ECC 6.0 Upgrade


© SAP 2010

1. SAP Enhancement Package Concept & Strategy

2. Architecture and Technology3. Implementation Procedure4. Customer Experiences and Summary

Agenda: SAP EnhancementPackage Concept & Strategy


© SAP 2010

Support Package

Support Package

EHPEHP

Inactive Business Functions

TimeSAP

System

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

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?


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

� Improvements for configurable sales UI

SALES

� Enhanced reporting and master data maintenance� Legal compliance for product safety and

occupational health� Enhanced 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 functionality� Further procure-to-pay improvements

� New stock type for inventory management� SAP Auto-ID infrastructure offering� Improvements for outsourced manufacturing

scenarios

PROCUREMENT AND LOGISTICS EXECUTION

� Work-in-process batch tracking and valuation � Engineering and manufacturing product structure

synchronization� Production order integration with ME applications� Power lists for process orders� Manufacturing analytics:

� Overall equipment efficiency (OEE) analytics via Xcelsius software

� Manufacturing analytics via Xcelsius� Shift report and shift note enhancements� Extensions in Lean Manufacturing (Kanban)� XSteps and PI sheet enhancements

PRODUCTION PLANNING AND EXECUTION

� SAP Treasury and Risk Management application:� Streamlined hedge management process� Enhancements 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 applications� New features in financial accounting and new

general ledger – reorganization of profit center� Improved formats of financial reports� Localizations for India, Japan, Chile, and Russia� Enhancements in SAP Strategic Enterprise

Management business consolidation functionality for legal compliance

FINANCIALS

� New FMEA (failure mode and effects analysis) features

� Integration with SAP EHS Management

QUALITY MANAGEMENT

� New role: simplified and improved maintenance planning and execution processes

� New functionality for modeling of linear assets� More granular cost collection� Improvements in rotable management� SAP 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 organizations

� Enhancements 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 management

� Improved insights into learning activities� Workforce process management:

� Automated performance assessment process� UI flexibility and organization management

analytics� Extended integration of e-recruiting and HR

core system in the hiring process� Enhancements for organization chart

visualization� Next-generation employee self-services� Additional HCM – localizations� Improvements in SAP Travel Management

application

HUMAN CAPITAL MANAGEMENT

Highlights


Productive SAP Enhancement Package Customers (June 2010)

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

7,915 EHP

customers

General availability of

SAP Enhancement Package 4

for SAP ERP 6.0


SAP Enhancement Packages & SAP ERP 6.0

What Are Enhancement Packages?

� Optionally installed and activated software innovations for SAP ERP 6.0

� Software innovations include UI simplifications, functional enhancements and Enterprise services

� SAP enhancement packages are built on top of each other

� Enhancement packages are not SAP Support Packages: SAP Support Packages contain corrections and legal changes

Quick Facts About SAP ERP 6.0

� Preamble: SAP enhancement packages are shipped as a delta shipment to SAP ERP 6.0

� 1. Selective Installation: Each 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 package

� 2. 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


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.


New 7-2 Maintenance Strategy

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

� Long-term planning security and higher return on investment – nine year maintenance horizon� Additional time to deploy and benefit from innovation delivered via enhancement packages� Less additional cost for extended maintenance

Before

New

* Core applications of SAP Business Suite 7: 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.

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

De

c


(+ 2%)*

SAP ERP 6.0,

SAP NW 7.0


(+ 2%)*

SAP CRM,

SCM, SRM 7.0Ramp-

Up

De

c

Cust.-Spec.

Maintenance

Cust.-Spec.

Maintenance

Ramp-Up

2011 20122009 2010 20142013 2015 2016 2017200820072006

7 2



No

v

De

c


(+ 2%)*

SAP ERP 6.0,

SAP NW 7.0


(+ 2%)*

SAP CRM,

SCM, SRM 7.0Ramp-

Up

De

c

Cust.-Spec.

Maintenance

Cust.-Spec.

Maintenance

Ramp-Up

2011 20122009 2010 20142013 2015 2016 2017200820072006

7 2



No

v

Ma

r

Mar

Mar


(+ 2%)*

SAP ERP 6.0,

SAP NW 7.0Cust.-Spec.

Maintenance

Ramp-Up



2011 20122009 2010 20142013 2015 2016 2017200820072006

Ma

r

Mar

Mar

Ma

r

Mar

Mar


(+ 2%)*

SAP ERP 6.0,

SAP NW 7.0Cust.-Spec.

Maintenance

Ramp-Up



2011 20122009 2010 20142013 2015 2016 2017200820072006

� Beginning with Business Suite 7 core applications, the mainstream maintenance phase is 7 years.

� The extended maintenance phase is 2 years, for an additional fee.


© SAP 2010

1. SAP Enhancement Package Concept & Strategy2. Architecture and Technology

3. Implementation Procedure4. Customer Experiences and Summary

Agenda: Architecture and Technology

© SAP AG ADM326 11-10

Example: SAP Enhancement Package 5Focus: 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 NetWeaverApplication 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.

© SAP AG ADM326 11-11

© SAP 2010

New Features• Manageability and usability

• Observer mode

• Alerting functionality

• GUI reconnect

• Stability & Robustness

• Check consistency of stack.xml

• Redesign of the add-on handling

Quick facts

SAPehpi: Standard tool to implement SAP enhancement packages

Technology: System Switch Procedure

Available for:� All 32-bit and 64-bit platform for ABAP, Java and Dual-Stack� SAP Business Suite 7 and SAP Business Suite 7 Innovations 2010*� SAP Enhancement Package 1 and 2 for SAP NetWeaver 7.0 � SAP Enhancement Package 1 for SAP Process Integration 7.1� SAP Support Packages for ABAP – only systems

* SAP Enhancement Package 4 and 5 for SAP ERP 6.0; SAP Enhancement Package 1 for SAP CRM, SAP SRM, SAP SCM 7.0

SAP Enhancement Package Installation Tool: SAP Enhancement Package Installer

© SAP AG ADM326 11-12

Example: SAP Enhancement Package 5Focus: Activation

Facts

Selective, 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 NetWeaverApplication 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

2Business 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 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.

© SAP AG ADM326 11-13

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 enhancement package 2 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 ECC

6.0.

© SAP AG ADM326 11-14

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.

© SAP AG ADM326 11-15

Things You Should Know Before Installing SAP Enhancement Packages

� Only one EHP Level per systemOne application system can only consist of one EHP level (e.g. EHP4 or EHP5). Hence installed EHP components have to be updated with every future EHP implementation.

� Industry SolutionsCustomers who have activated an industry business function set have to include the corresponding EHP industry software component during installation.

� EHP Installation and functional activation is partially non-reversible

EHP Facts

� EHPs are “cumulative”When installing the latest EHP you will automatically get all functionality delivered with previous SAP enhancement packages.

� Technically the EHP installation delivers only changed objects to your system (delta Shipment):- In case you have already installed EHP4 you will only install the new objects of EHP 5.- In case you have installed EHP 3 you will install EHP 4 and EHP 5 objects in one step

� Enhancement Package 2 for SAP NetWeaver 7.0 available

Technical Delivery

� Modification AdjustmentAfter installing 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 EHP’s (without activating business functions) compared to pure SAP Support Package updates.

Project Perspective

© SAP AG ADM326 11-16

© SAP 2010

1. SAP Enhancement Package Concept & Strategy2. Architecture and Technology3. Implementation Procedure

4. Customer Experiences and Summary

Agenda: ImplementationProcedure

© SAP AG ADM326 11-17

© SAP 2010

1

New Installation

2Upgrade of an

Existing System

3

Enhancement

Package

Installation

Implementation ScenariosDifferent Use Cases

© SAP AG ADM326 11-18

NW

7.0 NW

EHP2

NW

7.1

ERP

6.0

ERP

6.0

NW EHP1

NW EHP2

* SAP ERP 6.0 EHP5 Ready Installation

ERP

6.0

ERP

6.0

ERPEHP5

NW EHP2

SAPehpi

ERP

6.0

ERPEHP4

SAPehpi

ERPEHP5

NW EHP2

Implementation Scenarios Different Use Cases

New Installation1

SAPInst

NW EHP1

SAPehpi

ERP*EHP5

© SAP AG ADM326 11-19


Upgrade of an Existing System

NW

7.0 NW

EHP2

NW

7.1

ERP

6.0

ERP

6.0

ERPEHP4

2

NW

2004 SAPup/ SAPJup

NW EHP1

ERPEHP5

NW EHP2

R/3

4.6C SAPup/ SAPJup

NW EHP1

© SAP AG ADM326 11-20

ERP

6.0


Enhancement Package Installation

3

NW

7.0 NW

EHP2

NW 7.0

ERPEHP5

NW

7.1

SAPehpi

NW

7.1

ERP

6.0

SAPehpi NW EHP1

NW EHP2

SAPehpi

ERP

6.0

ERPEHP4

ERP

6.0

NW EHP1

SAPehpi

© SAP AG ADM326 11-21

Identification: Enhancement Package Info Center

� Single point of access to all information related to EHP’s:

• Presentations, documentation and release notes

• Test catalogue and learning maps

� Documentation at deep level of granularity

� Great ability to analyze new software functionality

� Easily identify needed Business Function(s)http://service.sap.com/erp-ehp

Phase 1:Select Required Business Functions

Result:High-level business requirements and selection of Business Functions

Further Services and Tools� Accelerated Innovation Enablement (AIE)

- Five days of SAP enablement helping to evaluate

the innovation capabilities of the latest SAP EHP

� Solution Browser and Business Function Prediction

AIE Experts

Requirements Design Build & Test Deploy

Business

� 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.

© SAP AG ADM326 11-22

© SAP 2010

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

Including direct access to:� Overview presentation� Release Notes� Documentation� Test case catalogs� Mapping to Technical Usage

SAP Enhancement Packages for SAP ERP 6.0Business Function Prediction

Register for a free Business Function Prediction today!

http://service.sap.com/BFP

Wondering which enhancement package

functionality is potentially relevant for you?

Freeserviceoffering

� A new version of SAP Enhancement Package Must Know Guide available

© SAP AG ADM326 11-23

© SAP 2010

The Concept� Purpose of the SAP ERP

enhancement package strategy

� Concept and methodology of enhancement packages

� What you need to know before

� How to implement them

� What to test at what point in time

Functional Overview� Which 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.

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)


Business

How To Use The Enhancement Package Information Center

© SAP AG ADM326 11-24

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 AG ADM326 11-25

Productive landscape DEVECC

PRDECC

QASECC

SBXECC

Enhancement package evaluation system

EHP 5

System copy

Legend

= ERP + EHP5

= old release (6.0)

= actual project work

= Transport route

How to Evaluate a Business Function in Your System Landscape

� 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: somenewly available reversible business functions)

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

System landscape


© SAP AG ADM326 11-26

Prepare Technical Installation

� Check Prerequisites� What are the prerequisites to check before installing?

� Choose Installation Approach� Selective or Broad

� Map Business Functions and Technical Usage� Which are ‘Technical Usages’ are relevant?

Phase 2:Design

Result:Business blueprint and technical preparation activities

Define Business Aspects� Create business blueprint for Innovation

� Execute implementation project with ASAP methodology

System Administrator

Business

DesignRequirements Build & Test Deploy

© SAP AG ADM326 11-27

Prerequisites For SAP ERP 6.0 – SAP Enhancement Package 5 Installation

1. Up-to-date SAP Solution Manager � SAP Enhancement package 1 for SAP Solution Manager 7.0 (SP 23 is mandatory)

2. Latest installation or upgrade tools� For systems on ECC 6.0 use 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-ons� Ask your add-on provider whether your add-ons are compatible with the SAP Enhancement

Package for SAP ERP 6.0

4. SAP Support Packages� In general there is no minimal 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 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.

© SAP AG ADM326 11-28

Mapping Process (Example)

Business Function Technical Usage Main Instances &

Software Components

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)

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 LedgerAccountingTechnical Name:FIN_GL_CI_1

. . .

Mapping

via OS

S N

ote 1324838

BFBF

BF

A “Technical Usage”groups software

components which must be installed together.

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

Server

© SAP AG ADM326 11-29

Installation Procedure At A Glance

Selective InstallationBroad Installation

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

Queue of installablepackages + stack xml

5. Modification Adjustment

6. Regression Test

4. Install installation packages using SAPehpi

1+2. Choose relevant Technical Usage(s) with potential business value for your company.More information about this approach can be found here.

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

EHP5 SAP Note: 1324838

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

Now defined: technical usage(s)

Business

Build

& T

estD

esign

© SAP AG ADM326 11-30

© SAP 2010

How to install SAP Enhancement Package 5

SAP Enhancement Package 5 Master

Guide

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

© SAP AG ADM326 11-31

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)

Phase 3:Build and Test

Result:Getting the solution ready and tested

Further Services

� Expert Guided Implementation

- Update to SAP Solution Manager Enhancement

Package 1 including basic configuration


Test & BuildRequirements Design Deploy





The Business Function Documentation allows the user to get to know the capabilities behind a




© SAP AG ADM326 11-32

SAP

Solution Manager 7.0

latest SP level

MOPZMOPZ


(MOPZ)

PPMSDownload Basket

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

ABAP

Dispatcher

WorkProcess

Work

ProcessWork

Process

Gateway

ICM

IGS

ENQ WP(ABAP)

MSG Server

(ABAP)

Globa l FS

StackConfiguration

File.xml

SAP ERP 6.0

Based on SAP NW 7.0SAP ERP 6.0 EHP 5

based on SAP NW 7.0 EHP 2

Technical Usagesbased on

SAP EHP 5*

b

StackConfiguration

File.xml

Select required Technical Usages and SP levela

SAPehpi

4

MOPZ generate Stack Configuration file

and calculates dependent software components and SPs

b

5

Download SW components and SPs via Download Basketc

2 Maintain System landscape via SLD/SMSY

3

3 Run Maintenance Optimizer

Provide your download to SAPehpi4

Perform the SAP enhancement package implementation 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

2 SMSY

c

a

SP‘sEHP SWComp.

SP‘sEHP 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

SP level (SP23). 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 of SAP ERP 6.0

© SAP AG ADM326 11-33

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 here

� Landscape verification promotes the “landscape pattern” concept: Hub and sidecar - details can be found here

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 MOpz

� Erroneous or incomplete landscape information can result in failure of the update procedure

� Guidance towards correctly entering all information needed in the update process is required

© SAP AG ADM326 11-34

Guided Download Procedure: Maintenance Optimizer

� Technical usage: predefined, installable subsets of an SAP enhancement package for SAP ERP

� SAP Note 1324838 (EHP5) maps identified business functions to a technical usage

� You enter the technical usage in the Maintenance Optimizer and it automatically calculates the relevant download files

� Prerequisites: - Solution Manager 7.0 EHP1 (SPS 23), Accuracy of system data- Data maintenance with Solution Manager System Landscape (SMSY)

* This is an example of installed software components in SAP ECC. For Java components and BI-, PI- and Portal content, a different installation procedure would be used.


� If you use the SAP Solution Manager Maintenance Optimizer - as strongly recommended and

already required for downloading SAP Support Packages in general - you only need the name of the

Technical Usage to install all needed software components. Based on that information, the SAP

Solution Manager Maintenance Optimizer calculates the needed software components and SAP

Support Packages automatically. Create a new maintenance transaction for updating your system

with SAP enhancement packages for SAP ERP 6.0. A guided procedure leads you through the

preparation process for updating your systems. Select all systems that are affected by the application

of the SAP enhancement package. In the next step of the guided procedure, you select the Technical

Usages you want to apply to your systems. The Solution Manager Maintenance Optimizer

automatically calculates all needed SAP Support Packages and new software component versions

needed for installing the previously selected Technical Usages. As a result, the Solution Manager

Maintenance Optimizer creates the Stack-XML file that can be read by the installation tools to create

a valid import queue. You can find further information about the Solution Manager Maintenance

Optimizer at service.sap.com/solman-mopz, detailed documentation at help.sap.com > SAP Solution

Manager > (select your preferred language) in the "Change Management" section.

Please remember: The software components of SAP enhancement packages for SAP ERP 6.0

contain new developments (as we partially replace existing software components). Therefore, if you

take a look at your system after applying the SAP enhancement package software components, you

will find software components in version 600 (e.g. with SAP Support Package stack 10) as well as

software components in version 602 (e.g. SAP enhancement package 2 with SAP Support Package

stack 0 which contains equivalent corrections to SP level 10 of the same component in version 600).

© SAP AG ADM326 11-35

EHP 5 EHP 5

Productive landscape DEVERP

PRDERP

QASERP

Transport changes

DEVERP

Temporarydevelopmentsystem Emergency

CorrectionsDual

Maintenance

System Landscape Aspects during Build & Test Phase

Legend

= ERP + EHP5

= old release (6.0)

= actual project work

= Transport route

System landscape

� During and after 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


© SAP AG ADM326 11-36

Installation of Additional Technical Usages

Both installation options require modification adjustment and regression tests for the

affected software components!

� Prerequisites:

� The enhancement package 5 Technical Usage “Central Applications” must be already installed

� Disadvantages:

� Longer downtime compared with EHP Installer

� Limited possibilities to reset installation

� Advantage:

� Shorter total runtime for small installation queues (few packages and/or small packages)

SAPehpi Transaction SAINT

� Mandatory for the initial enhancement package 5 installation

� Advantages:

� Shorter downtime compared with transaction SAINT

� Productive work is possible before downtime

� Reset is possible until beginning of downtime

� Large installation queues can be processed

� Disadvantage:

� Total runtime is longer compared with SAINT

If you want to activate a business function that does not belong to the technical usages that have been installed initially, you must install the missing technical usage later.

There are two different options to install additional technical usages:

© SAP AG ADM326 11-37

© SAP 2010

Activities before the activation …

� View the list of Business Functions now selectable

� Access documentation, release notes, test catalogue and possible dependencies from here

� Install the relevant documentation, refer to SAP note 1066110

Benefits

� Transparency of all system and UI changes that will take place

� Stability for all other parts of the solution

Activities after the activation …

� Activate the chosen Business Function

� Configure the chosen Business Function

Benefits

� New coding becomes active only where activated

� Faster implementation because only activated parts are configured

Transaction: SFW5

Business

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.

© SAP AG ADM326 11-38

New With Enhancement Package 5:First Set of Reversible Business Functions

New: reversible Business Functions:

� A reversible Business Function can be tested / evaluated in DEV/QAS systems but only in separate clients

� During the test of reversible Business Functions no other tests must take place in the whole system as Business Functions are active in all clients

� To completely ‘undo’ a Business Function the whole client has to be deleted

� Currently there are 37 reversible Business Functions

© SAP AG ADM326 11-39

Switch Framework: Transaction SFW5Transport of Switch Settings

Transaction: SFW5

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 AG ADM326 11-40

Test & Go Live:SAP Delivers Test Case Templates

Activities

� Acceptance test for selected Business Functions

� Use standard test case templates

� Train end-users

� Go live, transport switch activities to production system

Benefits

� Faster test preparation due to test case templates

� Smaller test scope because changes are documented for each business function

� Smaller training effort due to limited and documented effect on user interfaces

� All test cases are available as documents in the enhancement package information center(http://service.sap.com/erp-ehp)

� Documents (texts) can be downloaded

You can access the TCTs before Installing an EHP..

� Test cases are shipped with the 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 workbench

� Test cases can be transported to SAP Solution Manager via workbench request.

..or after installing an EHP

Business


� Test case templates will be available for each business function that is new to an 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 enhancement package in SAP Service Marketplace. All test cases are

available as documents in the enhancement package information center and can be downloaded.

� Secondly after installing an enhancement package via the switch framework. Test cases are

shipped with the 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.

© SAP AG ADM326 11-41

Phase 4:Deploy

Go-Live and Support

� Update of production system:EHP Installer is specialized to minimize downtime

� Release of the EHP System for Production Operation

� Support after Go-Live

� Project Closure

Services

� SAP delivers continuous quality checks

� Transport Management synchronizes deployment to production

Result:Innovation is available for business


DeployRequirements Design Build & Test





The Business Function documentation allows the user to get to know the capabilities behind a




© SAP AG ADM326 11-42

Current StatisticsSAP Enhancement Package Installer

EHP Installer Statistics forSAP 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 enhancement package 4 implementation was performed.

SAPehpi downtime

SAPehpi runtime

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


DeployRequirements Design Build & Test

© SAP AG ADM326 11-43

Service offering: Enhancement Package Planning for SAP ERP 6.0 * New SAP consulting

service offeringOverview….� Intensive 2 days onsite workshop

� We plan your enhancement package installation project & strategy

� Learn from experienced SAP consultants

� Feel well prepared to start your implementation project!

Project Milestone Plan� We define a customer specific implementation

approach & EHP strategy

� We create an 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

© SAP AG ADM326 11-44

© SAP 2010

1. SAP Enhancement Package Concept & Strategy2. Architecture and Technology3. Implementation Procedure4. Customer Experiences and Summary

Agenda: CustomerExperiences and Summary

© SAP AG ADM326 11-45

© SAP 2010

‘The implementation of SAP enhancement package 2 for SAP ERP 6.0 was much easier than upgrading a full release. We installed all the software components that we could get in order to be open toimplement further innovations at minimized cost at any time.’

Thomas Muhler, Technology Consultant, cormeta ag

Innovate -Just in Time

• Stability and Access to Innovation – activate new functionality on demand.

Cost reduction• Lower effort to install

functional enhancements, ideally silent as part of system maintenance

• Easier testing with standard test case templates

‘Within an extremely short timeframe, we managed to implement functional enhancements around Real Estate Management. We went live after only a few weeks.’

Martin Kling, Head of Group Financials,TreuHandStelle GmbH

‘We were delighted that no side effects occurred at all outside the activated new functional capability. The EHP conceptallowed us to fulfill requirements years before we will start our next release upgrade. The end-user reactions were very positive and no critical issues occurred.’

Stephan Polster, Project Manager, ThyssenKrupp Steel

‘We implemented enhancement package 2 in order to use the new capabilities for Bank Relationship Management. No critical issues occurred. The implementation was very easy.’

Joerg Engel, System Engineer, Wuerth-Group

Benefits of SAP Enhancement PackagesFurther Customer Proof Points

© SAP AG ADM326 11-46

Comparing SAP Enhancement Packages for SAP ERP and SAP NetWeaver

SAP ERP (SAP ECC)

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

SAPNetWeaver

SAP Enhancement Packages for

Both: Efficient and fast installation with SAPehpibased 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 provided

SAP Enhancement Package 2 for SAP NetWeaversupports SAP Enhancement Package 5 for SAP ERP

NW EHP adds new functionality, but does not replace existing functionality

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

NetWeaver?

� All in all there are a lot of similarities. The installation procedure is in both cases efficient and fast.

The installation is performed with SAPehpi 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 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 AG ADM326 11-47

© SAP 2010

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 w� Blueprint: 3 w� Realization: 8 w� Prep for cutover: 3 w� Prod. cutover & support: 2 w

� Preparation: 1 w� Blueprint: 1 w� Realization: 2,5 w� Prep for cutover: 2 w� Prod. 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 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 Packages Installation: Customer Experience (Overview)

© SAP AG ADM326 11-48

© SAP 2010

Criteria Upgrades¹ SAP Enhancement Packages²

Customer

satisfaction

Reasons for

upgrading /

installing

enhancement

packages

1%4%

18%

41%

36%

Not satisfied

Less satisfied

Satisfied

More satisfied

Very satisfied 8% 5%

2%

32%

53% Not satisfied

Less satisfied

Satisfied

More satisfied

Very satisfied

0 20 40 60 80 100

Maintenance

Business innovation

Use latest technology

Improve usability

Functional requirementsManage modifications

System landscape cons.

Legal compliance

0 20 40 60 80 100

Others


Manage modifications

Business innovation

Use 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

© SAP AG ADM326 11-49

© SAP 2010

1 Upgrades to SAP ECC 6.0 with source release SAP R/3 4.6C ; 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;

0 12 24 36 48

Hours

Max: 48Min: 8 Median: 24

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

© SAP AG ADM326 11-50

© SAP 2010

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 AG ADM326 11-51

© SAP 2010

SAP ERP – Top 10 Business Functions*

S AP �E nhancement�Pac kage�2�for�S AP �E RP �6.0

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

F IN_TRAVE L_1 S AP �T ravel�Management�E nhancements

S D_01 Order�to�C ash�S implification

HCM_AS R _C I_1 HCM�P rocesses�and�F orms

F IN_FS CM_INTEGRATION F S CM,�Integration

HCM_LS O_C I_1 S AP �Learning�S olution

F IN_AC C _GROUP_C LOS E G roup�C lose

LOG_MM_C I_1 Business�F unction�Materials�Management

IS U_UTIL_1 Utilites,�G eneral�E nhancements

R E _GE N_C I_1 R eal�E state�Management

F IN_FS CM_C C D F S CM,�F unctions


F IN_G L_C I_1 New�General�Ledger�Accounting

F IN_R E P_S IMPL_1 R eporting�F inancials/K Y K /G E N_AIO_S IMP LIF IC AT ION R oles�in�S AP �All�In�One

HCM_E S S _C I_1 HCM,�E S S �for�P ersonal�Information

OP S _P S _C I_1 P roject�S ystem

HCM_E R C _C I_1 HCM,�S AP �E �R ecruiting�1

F IN_TRM_LR _F I_ANTRM:�Hedge�Management,�New�Instruments,�New�Key�F igures

LOG_E S OA_OP S _2 Operations,�E nterprise�S ervices�2

HCM_E R C _S E S _1 HCM,�S AP �E �R ecruiting�� S earch�1

LOG_S D_C I_01 S ales�and�Distribution


E R P_E NTE R PR IS E S E AR C H E nterprise�S earch�in�S AP �E R P

HCM_OS A_C I_1 HCM,�P erformance�Management�01

HCM_AS R _C I_2 HCM,�Administrative�S ervices�02

F IN_R E P_S IMPL_2 R eporting�F inancials�2

F IN_G L_C I_2 General�Ledger�Accounting�2

E R P_ALL_PDF _FORMS All�C ommon�Forms�Available�in�PDF

LOG_MMF I_P 2P MM,�Integration�of�MM�and�F I

E R P_ALL_LIS TS E R P ,�New�User�Interface�for�ABAP �L ists

HCM_LS O_C I_2 HCM,�Learning�S olution�02

HCM_TMC _C I_1 HCM,�C ore�P rocesses�in�T alent�Management

*1st July 2010

S AP �E nhanc ement�Pac kage�3�for�S AP �E R P �6.0

S AP �E nhancement�Pac kage�4�for�S AP �E RP �6.0

© SAP AG ADM326 11-52

© SAP 2010

What IT professionals must know about

SAP enhancement packages for SAP ERP

New version of SAP Enhancement Package Must Know Guide available

service.sap.com/erp-ehp

� A new version of SAP Enhancement Package Must Know Guide available

© SAP AG ADM326 11-53

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 EHP Technology Facts

SAP enhancement package strategy for SAP ERP

ERP@BPX: EHP Forum & Wiki

SAP EHP Info Center

© SAP AG ADM326 11-54

© SAP 2010

Agenda: Unicode Conversion



10. Planning and Preparation 11. Enhancement Packages12. Unicode Conversion

13. Tools and Services14. SAP Notes for this Course


Unicode Conversion

Contents:� What is Unicode?

� Major steps in an Unicode conversion project

� What has a Unicode conversion to do with an upgrade?

� Combined Upgrade and Unicode Conversion (CU&UC)

� Twin Upgrade and Unicode Conversion (TU&UC)


Single Code Pages (Non-Unicode) in SAP Systems

Turkish

Croatian

Czech

Hungarian

Polish

Rumanian

Slovakian

Slovene

English

German

Danish

Dutch,Finnish

French, Italian

Norwegian

Portuguese

Spanish

Swedish

Russian

Ukrainian

Greek

Hebrew

Thai

Korean

Japanese Chinese

Taiwanese

� Every ellipse represents

one code page

� Single Code Page system

means that only

languages within ONE ellipse can be used

Icela

nd

ic

� Without Unicode a SAP system makes use of one or more 'small' codepages.


Unicode: Example Languages Supported with Unicode

Turkish

Croatian

Czech

Hungarian

Polish

Rumanian

Slovakian

Slovene

English

German

Danish

Dutch

Finnish,

French, Italian Norwegian

Portuguese

Spanish,

Swedish

RussianUkrainian

Greek

Hebrew

Thai

Korean

Japanese Chinese

TaiwaneseIc

ela

nd

ic

Farsi

Hindi

Bashkir

PanjabiSanskrit

Arabic

Azerbaijani

Belarusian

Bengali

Urdu

Vietnamese

Unicode

ellipse

� With Unicode a SAP system makes use of only one 'big' codepage.


Unicode is the 'master-codepage' Greek

HebrewKorean

Japanese Chinese

Taiwanese

Turkish

CroatianCzechHungarianPolish

RumanianSlovakian

Slovene

Thai

Ukrainian

MDMP

Single

codepage

SAP ECC 6.0 and Unicode:

ONLY mandatory for MDMP customers

Globalization Requirements

Acting in global business requires support of a global character set!

� Companies running global business processes like global HR systems

� Companies offering web services to their customers: global master data containing multiple local language characters!

� Companies using open standards: J2EE and .NET integration

AfarAbkhazian

AvestanAfrikaansAmharic

ArabicAssamese

AymaraAzerbaijaniBashkir

BelarusianBulgarian

UzbekVietnameseVolapük

WolofXhosaYiddishYorubaReserved- cust.

ZhuangChinese trad.Chinese

Zulu

BihariBislamaBengali

TibetanBreton

BosnianCatalanChechen

ChamorroCorsicanCzechChurch SlavicChuvash

WelshDanishGerman

TeluguTajikThaiTigrinya

TurkmenTagalogTswanaTonga

TurkishTsongaTatarTwiTahitian

UighurUkrainianUrdu

DzongkhaGreekEnglish

EsperantoSpanishEstonian

BasquePersianFinnishFijianFaroese

FrenchFrisianIrishGaelic

GalleganGuaraniGujarati

Manx

HausaHebrew

HindiHiri Motu

CroatianHungarianArmenian

HereroInterlinguaIndonesianInterlingueInupiak

IcelandicItalianInuktitutJapanese

Javanese GeorgianKikuyu

Kuanyama

KazakhGreenlandic

KhmerKannadaKorean

KashmiriKurdish

KomiCornishKirghiz

LatinLetzeburgeschLingalaLao

LithuanianLatvianMalagasyMarshalleseMaori

MacedonianMalayalamMongolianMoldavian

Marathi

MalayMaltese

BurmeseNauru

Norwegian BokmålNdebeleNepali

NdongaDutchNorweg. NynorskNorwegianNdebele

NavajoNyanjaOccitanOromo

OriyaOssetianPanjabi

PaliPolishPushtoPortugueseQuechua

Raeto-RomanceRundiRomanian

RussianKinyarwanda

SanskritSardinianSindhi

Northern SamiSango

Serbo-CroatianSinhaleseSlovak

AfarAbkhazian


ArabicAssamese


BelarusianBulgarian




Zulu


TibetanBreton



WelshDanishGerman




UighurUkrainianUrdu






Manx

HausaHebrew

HindiHiri Motu





Kuanyama

KazakhGreenlandic

KhmerKannadaKorean

KashmiriKurdish

KomiCornishKirghiz




Marathi

MalayMaltese

BurmeseNauru







RussianKinyarwanda


Northern SamiSango


AfarAbkhazian


ArabicAssamese


BelarusianBulgarian




Zulu


TibetanBreton



WelshDanishGerman




UighurUkrainianUrdu






Manx

HausaHebrew

HindiHiri Motu





Kuanyama

KazakhGreenlandic

KhmerKannadaKorean

KashmiriKurdish

KomiCornishKirghiz




Marathi

MalayMaltese

BurmeseNauru







RussianKinyarwanda


Northern SamiSango


German

DanishDutch,FinnishFrench, ItalianNorwegian

SpanishSwedish

EnglishRussian

Portuguese


Communication: The Ideal Picture

The ideal picture:

Unicode components only

� Conversions are done algorithmically (1:1 relation)

� No data misinterpretation

� No data loss

� All business relevant characters available at the same time

SAP R/3 4.7

3rd party

SAP BW

R/3 4.7

FilesInternet

� The Unicode logo is used here as an placeholder for any of the Unicode encoding formats UTF16LE,

UTF-16BE or UTF-8.

� In case of an Unicode � Unicode combination RFC passes all character data without code page

conversion or merely with adaption of the endianness.

� UTF-16 big endian = SAP code page 4102

� UTF-16 little endian = SAP code page 4103

� Information about the destination is maintained in SM59�� special options � character width in target system

� 1 Byte = non-Unicode

� 2 Byte = Unicode


Communication: Reality

Reality: Unicode and

non-Unicode component

� Conversions between incompatible code pages everywhere

� Only common subset exchangeable

� Special rules have to be followed to make communication possible

3rd party EBCDIC

SAP BWISO8859-1

R/3 4.7Files

...charset=iso-8859-1" >...charset=windows-1257" >

...charset=Shift_JIS" >...charset=utf-8" >

Internet

SAP R/3 4.6CISO8859-1

SJIS

IS0-2

BIG-5

IS0-1

12511251697/0277

IS0-7

IS0-8

SJIS

1251697/0500

1252

� In an MDMP (Multi Display Multi Processing Code Page) system character data is encoded in

different code pages. Only that part of the data that belongs to the current system code page will be

handled correctly during string processing or code page conversions. In an MDMP system you have

to ensure that you use language keys to mark your data. Use SET LOCALE LANGUAGE to switch

between different system code pages.


Unicode: Communication Rules RFC

MDMP

Receiv

er

Unicode

Single Code

Page (SCP)

Unicode Single Code Page (SCP) MDMP

no issues no issues as Unicode is superset of all code pages �understands all characters

special measure required to ensure communication

receiver understands only characters that are part of the SCP in use

No issues in case of identical SCP; otherwise only ASCII 7 subset can be exchanged without errors

No issues in case SCP is part of MDMP and language info is correct; otherwise only ASCII 7 subset can be exchanged without errors

receiver understands only characters that are part of its MDMP code pages

No issues in case SCP is part of MDMP; otherwise only ASCII 7 subset can be exchanged without errors

receiver understands only characters that are part of its MDMP code pages

Sender

Complex communication landscapes that worked before will

work also after Unicode conversion if communication rules and

user discipline is preserved!

“

� Examples for issues of Unicode <> MDMP communication:

� Language key must be provided correctly, otherwise inconsistencies and short dumps may occur

on receiver side;

� The connection of an Unicode SAP BW system to an MDMP SAP ECC system requires special

interface adoptions to work correctly.

� Special attention should be paid to SAP to non-SAP interfaces. Unicode compliance of non-SAP

software must be ensured. Especially, links to printer or fax machines should be tested as well.


Database

UTF-8

CESU-8

UCS-2

UCS-2

UTF-16

UTF-16

~10%

~10%

40 … 60%

40 … 60%

10 … 20%*

20 … 60%**

DB2 (Universal Database for Unix / NT)

Oracle

MaxDB

MS SQL

DB2 for AS/400

DB2 for z/OS**

Encoding Add. Storage Req‘s

Expected Hardware Requirements -Database

Average database growth at customers (sum of all sizes):

� UTF-8 and CESU-8: -14% (for more than 90% of the installations the database shrunk - due to the reorganization)

� UTF-16: +30% - +40%

* small growth as biggest part of the Ascii based database is already UC** white range as it depends on compression usage


�UTF-8* : up to +10%

ORACLE, DB/2 (AIX)

�UTF-16 : + 20 ... 60%

SQL Server, DB/2 (AS400),

MAX DB (7.0)

Database size�UTF-8

�almost no change

due to efficient

compression

Network Load

Additional Hardware Requirements for Unicode

� +30%

� depending on

existing scenario

(MDMP, double byte)

CPU� +50%

� Application Servers

are based on UTF-16

internally

RAM

Based on parallel benchmarking of Unicode / non-Unicode test systems

Note: The CPU/RAM figures are measured average numbers and will be different for different transactions

* 35% is the observed maximum in growth for small systems (db size < 200 GB).

* 10% is the observed maximum for bigger systems (db size > 200 GB).

1. Priority

� When using Unicode, characters use up more space in database and main memory.

� This causes the need of much more hardware to keep the system performance the same as without

Unicode.

© SAP AG ADM326 12-10

Conversion (Without Upgrade)

SPUMG

R3load

Control

Table

Voca-

bulary

EXPORT

IMPORT

non

Unicode

+ Conversion

Re-process

Log

UnicodeData R3load

� Import and export during downtime

� Unicode conversion during export

� The default conversion method is to export the entire database using R3Load, create a new Unicode

database, and then import the database using R3Load again.

� Conversion from Unicode to non-Unicode is not possible

� MCOD (more than one SAP system in one database):

� a Unicode SAP system is not compatible with a non-Unicode SAP system

� Unicode SAP systems are not released for Informix.

� If the source system is a MDMP system perform additional steps that are described SAP Note

551344.

� If you are using HR functionality within SAP R/3/SAP ECC, additional steps are mandatory, which

are described in SAP Note 573044.

� Currently SAP does not support an upgrade with simultaneous Unicode conversion. Therefore you

must first upgrade a non-Unicode system with a basis release less than AS ABAP 6.20 to AS ABAP

6.20 (or higher). Once the non-Unicode system uses AS ABAP 6.20 or later you can convert to

Unicode.

� Perform the following steps on the source system:

� Preparation step in the transaction SPUMG

� Initialize the worklist (see SAP Note 548016)

© SAP AG ADM326 12-11

Downtime: Dependencies

Single Code Page or MDMP conversion?

� MDMP requires more reconversion tasks and post conversion handling in the Unicode system

Biggest tables – optimize parallelization of export/import processes (splitting of R3load packages)

Processing of cluster tables

� Sizes of cluster tables (compared to transparent tables)

Hardware

� Number and speed of CPUs

� Performance of disks

� Separate server available for Unicode system?

Time spent on optimization (problems not related to runtime)

SAP Note

784118

857081

� Production time:

� Unicode enabling of customer programs and conversion of customer code pages

� Transport for import of customer programs

� Unicode preparation with tool SPUMG

� Downtime:

� Unicode Conversion (system copy with SAPinst)

� Manual completion steps

© SAP AG ADM326 12-12

Runtimes – Customer Experiences

� Net runtimes on PRD systems: time needed from begin of export until end of import (without e.g. prepare jobs, back-up, tests after the conversion etc.)

� Most of the shown examples used two servers(export on server 1 and import on server 2 in parallel).

� Experiences show that the reduction can be significantly high when using the two servers scenario (e.g. from 50 h � 28 h for the runtimes).

Examples for Export / Import Runtimes(Database Size > 1000GB)

05

101520253035404550

800 1800 2800 3800 4800 5800 6800 7800 8800

DB size in GB

Net

Run

times

in h

ours

� The pure export and import of the database should be possible within a two days downtime window.

© SAP AG ADM326 12-13

Steps to Minimize Unicode Downtime

� 1. Use old system for export and new machine for import

� 2. Create database statistics

� 3. Parallelize export/import processes (2 proc. for each CPU core)

� 4. Split packages (separate TOP 50 tables)

� 5. Split TOP 10 biggest tables (R3ta)

� 6. Use FAST LOAD option (DB feature)

� 7. Use unsorted UNLOAD

� 8. Parallelize index creation

� 9. Increase your I/O throughput

� 10. Create reusable scripts

� Minimized Downtime Service (MDS) is offered by SAP Consulting (but not possible in combination with an upgrade)

� If necessary, the IMIG (incremental migration) technology is used

� Please have a look at SAP Note 693168 - Email: [email protected]

Optimization

enhancements do not

result in an

acceptable downtime:

� Hardware Tuning (e.g. additional CPUs)

� Use additional (new) server for the Unicode system

� Database tuning (see note 936441)

� R3Load package split (see System Copy Guide)

� Table split (see note 952514)

� Migration monitor (See note 784118)

� Distribution monitor (See note 855772)

� Export: unsorted export of transparent tables (see note 954268)

� Import: R3Load option 'Fastload' (See note 864861)

© SAP AG ADM326 12-14

Who Needs Unicode?

� Companies running global business processes like global HR systems or global master data management

� Companies offering web services to their customers: global master data containing multiple local language characters!

� Companies using open standards: J2EE and .NET integration (JAVA speaks Unicode!)

� Collaborative business: integration of third party products that run on different code pages

Acting in global business requires support of a global character set!

� First upgrade, then conversion to Unicode.

� Customers upgrade their SAP systems to the required non-Unicode target release (at least AS ABAP

6.20).

� Afterwards they perform the Unicode Conversion - as a separate project.

© SAP AG ADM326 12-15

Unicode Conversion

Questions

� Which Unicode Conversion approaches exist in combination with upgrades or other activities?

� What are SAP recommendations?� What are prerequistes and side effects?

Options ECC

� UC without upgrade� standard method (SAPInst/R3load)� Minimized Downtime Service (MDS) with IMIG

� UC with upgrade� Twin Upgrade & Unicode Conversion (TUUC)� Combined Upgrade & Unicode Conversion (CUUC)� Near Zero Downtime Method (NZD)

Options other products

� UC without upgrade� standard method

� UC with upgrade� Combined Upgrade & Unicode Conversion (CUUC)

� Note: For non-ECC products, the method CUUC is only available as pilot projects for sources with

AS ABAP 6.20 or later. Please contact SAP for more information.

© SAP AG ADM326 12-16

ABAP Unicodeenabling

Interfaceadaptation

Technicalconversion

MDMPhandling

Building Blocks of Unicode Conversion Projects

Project management

© SAP AG ADM326 12-17

High level description

The Conversion Roadmap takes you step-by-step through the process of converting a non-Unicode system to a Unicode system.

� Prerequisites: You must first ensure that you employ Unicode-based SAP components and a Unicode-enabled database, as detailed in the following SAP Notes 379940 and 79991

During preparation, topics such as additional hardware requirements, downtime issues, Unicode-enabling of customer developments, and the special treatment of MDMP systems have to be taken into consideration.

Phases

The Unicode conversion process is based on a system copy, and during this process, the database conversion and system shutdown/restart are as automated as possible. For small to mid-size databases (< 1 TB), this is based on an SAP unload/reload of the complete database; minimum downtime tools will be used for larger databases.

Post-conversion

Preparation

Conversion

Once the Unicode system is up and running, you need to verify data consistency on a scenario basis, as well as carry out general integration testing. For systems that support multiple languages, special emphasis needs to be placed on cross-language handling during the test phase. Correction tools are provided by SAP, which can be used in the case that conversion did not run properly.

Note: For details and conversion guides see SAP Service Marketplace http://sercive.sap.com/unicode

Unicode Conversion Roadmap

© SAP AG ADM326 12-18

Interfaces to

Non-SAP systems

Conversion methods

System properties:Database sizeDowntime

Hardware performance

Used language

support technology

easy medium difficult

Single

codepage

Asian

codepage

Multiple

codepages (MDMP)

Type of system SAP ECC SAP CRM

with Mobile Sales

SAP NetWeaver AS

standalone

Small database size

Long Downtime windowGood performing Hardware

Large database size

Small Downtime window

Bad performing Hardware

ABAP enabling Small amount of

objects

Easy objects

(CS, …)

Large amount of

objects

Difficult objects

(Offset)

Standard Table

splitting

Combined Upgrade

& Unicode Conversion

Unicode based

systems

Single codepage

Asian

Single codepage

Latin-1

Interfaces to

SAP systems

SAP singlecodepage Latin-1

SAP MDMP+ ALE (container)

SAP MDMP+ TABLES

SAP Unicode systems

Which Factors Influence the UC Conversion Project?

© SAP AG ADM326 12-19

Recommended Upgrade Paths for Unicode Conversion

Do you currently

useMDMP?

SAP R/3 4.7

and above

SAP R/3

4.6C

SAP R/3 4.6B

or lower

SAP R/3 4.7

and above

MDMP

SAP R/3 4.7

and above

Unicode

SAP ECC 6.0

UNICODE

SAP R/3 4.6C

and above

MDMP

SAP ECC 6.0

Unicode

All releases

MDMP

SAP ECC 6.0

Unicode

All releases

SCP

SAP ECC 6.0

SCP

SAP ECC 6.0

Unicode

Unicode Conversionbefore Upgrade

Combined Upgrade & Unicode Conversion (CUUC)*

Upgrade before Unicodeconversion

Twin Upgrade & Unicode Conversion (TUUC)*

Convert Upgrade

No

Yes

Upgrade Convert

Upgrade, directly followed byUnicode Conversion

Upgrade, directly followed byUnicode Conversion

*CUUC/TUUC: it is also possible to upgrade with CUUC or TUUC, if the start release is an SCP system

SAP R/3 4.7

and above

SCP

SAP R/3 4.7

and above

Unicode

SAP ECC 6.0

Unicode

Unicode Conversionbefore Upgrade

Convert Upgrade>90%

of customers

SAP R/3 4.6C

or lower

SAP R/3 4.7

and above

� Prior to building the SAP ECC 6.0 upgrade business case, it should be determined if Unicode is a

relevant topic for your company and how to handle Unicode

� Depending if you are currently handling multi-code pages through MDMP, your options might look

different:

� The most typical – and our recommendation for more than 90% of customers who are not using

MDMP – is for customers who are on SAP R/3 4.7 to do the Unicode conversion and then the

upgrade.

� Alternatively for customers who are on a release lower than SAP R/3 4.7, we recommend first

to upgrade and then leverage conversion tools to do the conversion on SAP ECC 6.0.

� If you are using MDMP which is true for multi-national customers, and depending on your current

release, you can either do the upgrade, immediately followed by the unicode conversion. If the gap is

very small, the conversion can be done in a very short time. If you are on a lower release than 4.6C,

you will need to upgrade first, but we would recommend to keep the time as short as possible

between upgrade and conversion since SAP doesn‘t support MDMP anymore as of SAP ECC 6.0

and thus we require a special disclaimer from you.

© SAP AG ADM326 12-20

Ways to Your Unicode SAP System

Unicode Conversion without Upgrade

Combined Upgrade & Unicode Conversion

Twin Upgrade & Unicode Conversion

source release >= R/3 4.6C

for target release >= ECC 6.0 only

especially source release < R/3 4.6C MDMP

Supported Unicode Conversion Paths:

standard path for >= R/3 4.7

� Advantages of CU&UC

� Upgrade and Unicode Conversion in one Downtime

� MDMP scan (SPUM4) can be performed on the SAP R/3 4.6C source system

� Possible for SAP R/3 4.6C / SAP R/3 4.7 / SAP ECC 5.0 (MDMP and Single Codepages)

� Prerequisites and Restrictions of CU&UC

� Information and restrictions according to note 928729 / CU&UC Conversion Guide

� Complexity of the project is high - two projects are combined into one !

� Downtime needs to be tested and usually enhanced

� Sandbox conversion is highly recommended

- Evaluation of proper downtime is only possible on a sandbox system

� ABAP Unicode Enabling needs to be done e.g. in sandbox system or upgraded development

system for start release SAP R/3 4.6C

� Development freeze during project highly recommended

© SAP AG ADM326 12-21

Combined Upgrade & Unicode Conversion (CU&UC)

� Many customers have SAP R/3 4.6C systems with MDMP configurations. They want to upgrade to a release >= SAP ECC 6.0.

Problem:

� MDMP support is discontinued starting with release SAP ECC 6.0 .

� Customers can not upgrade their MDMP systems to SAP ECC 6.0 first and then convert to Unicode afterwards.

� Customers can not convert to Unicode first and then upgrade to SAP ECC 6.0 because SAP R/3 4.6C is not a Unicode-enabled release.

Solution:

� The 'Combined Upgrade & Unicode Conversion (CU&UC)' enables customers to upgrade to SAP ECC 6.0 and switch to Unicode in one downtime window.

Note:

� CU&UC is globally available for >= SAP R/3 4.6C - for other products pilot only.Please read SAP Note 928729 for details.

� Every customer who runs on SAP ECC 6.0 with MDMP productively (it does not matter how

long) has to sign the disclaimer - there are no exceptions.

� The customer specific support during this time has to be clarified within the project.

� There is no longest time frame, this needs to be clarified in the project as well. Recommendation

would be to make it as short as possible and not to exceed 3 month.

� See also

http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000380759&_SCENARIO=01100

035870000000112&_OBJECT=011000358700006895212005E --> last page

� During CU&UC upgrade and Unicode conversion are executed sequentially.

� Time saving: Nametab creation during system uptime

� The cost saving of CU&UC lies in the project time. You need to test only one target (the upgraded

Unicode system) instead of two (the upgraded Non-Unicode system and the final Unicode system).

© SAP AG ADM326 12-22

CU&UC Example:SAP R/3 4.6C MDMP SAP ECC 6.05 Unicode

Unicode

conversion

SAP R/3 4.6C

MDMP

SAP

BASIS

4.6C

SAP ECC 6.05

MDMP(!)

SAP ECC 6.05

UnicodeUnicode

preparationUnicode post

processing

DowntimeProduction time

AS ABAP

7.02

AS ABAP

7.02

*SAP ECC 6.05 = Enterprise Central Component of SAP Enhancement Package 5 for SAP ERP 6.0

Upgrade

� During CU&UC upgrade and Unicode conversion are executed sequentially.

� The cost saving of CU&UC lays in:

� a) the project time. You need to test only one target (the upgraded Unicode system) instead of

two (the upgraded Non-Unicode system and the final Unicode system).

� b) Nametab generation is done automatically during system uptime

© SAP AG ADM326 12-23

Twin Upgrade & Unicode Conversion (TU&UC)

Customers with MDMP <= SAP R/3 4.6B want to upgrade to >= SAP ECC 6.0.

Problem:

� They can not make use of the CU&UC because the Unicode Preconversion tool is not utilizable in their release.

Solution:

� The 'Twin Upgrade & Unicode Conversion (TU&UC)' is a release-independent concept which allows a combination of Upgrade and Unicode conversion.

Note:

� TU&UC enables customers to perform both procedures in one downtime window!

How?Preparation steps (SPUMG) are done in an upgraded copy of the production system (twin system):� The twin system is used for collecting all necessary information required for a fast run in the

production system and for creating the control information needed for the correct conversion of the MDMP data.

� The results are then reused during the conversion of the production system in order to minimize the downtime.

� Every customer who runs on ECC 6.0 with MDMP productively (it does not matter how long) has to

sign the disclaimer - there are no exceptions.

� The customer specific support during this time has to be clarified within the project.

� There is no longest time frame, this needs to be clarified in the project as well. Recommendation

would be to make it as short as possible and not to exceed 3 month.

� See also

http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000380759&_SCENARIO=01100

035870000000112&_OBJECT=011000358700006895212005E --> last page

� Options: Customers can upgrade their MDMP system to a release lower than ECC 6.0, perform the

‚normal‘ Unicode conversion and then upgrade the Unicode system to ECC 6.0 or choose the

CU&UC after the first upgrade.

� = too much downtime – unacceptable!

� Reason for no SPUM4 in SAP R/3 4.6B: for SPUMG and SPUM4 we need ABAP Objects. This

ABAP feature is available as of Basis Release 4.6C

© SAP AG ADM326 12-24

Production run

TU&UC Example:SAP R/3 4.6B MDMP � SAP ECC 6.05 Unicode

Unicode post

processing

SAP R/3 4.6B MDMP

SAP ECC 6.05 Unicode

SAP ECC 6.05

MDMP (!)

SAP R/3 4.6B

MDMP

Twin run

Upgrade

Unicode preparation

SAP ECC 6.05 MDMP (!)

Unicode

conversion

Upgrade

Imp

ort

re

su

lts

Downtime

Sys

tem

co

py

� With the end of support of MDMP systems based on AS ABAP 7.00 (e.g. SAP ECC 6.0; see notes

79991 and 838402) there is a need for MDMP customers to convert their systems before going live

with their targeted upgrade version.

Depending on the software component several MDMP customers now face the problem, that

Unicode is not available in their start release (e.g. SAP R/3 4.6B) and MDMP is not supported in the

target release (e.g. SAP ECC 6.0). As the MDMP Unicode conversion preparations with SPUMG

are only possible on the target release and as they take normally at least one week, customers are

faced with a unacceptable downtime for the combination of upgrade and Unicode conversion.

� In order to close this gap SAP is providing the so called 'Twin Upgrade & Unicode Conversion'

which allows to combine upgrade and Unicode within one downtime window. The twin concept is

doing the MDMP Unicode conversion preparations in an upgraded copy of the production system

(twin system) and the results are later reused for the productive conversion without the need to rerun

the MDMP Unicode preparation steps in the production

© SAP AG ADM326 12-25

Unicode ConversionOverview of methods and tools

Standard UC1 Incremental

Migration1 CUUC TUUCNear Zero Downtime

Tools

SAPinst/R3load � IMIG tool(using DB trigger)

� SAPInst/R3load

� SAPup� SAPInst/R3load� special programs (e.g.

SPUM4)

� SAPup� R3load� special programs

� system copy� DB trigger� SAPup� R3load� SLO Migration

Workbench

Prerequisites

Source: SAP R/3 4.7, SAP SCM 4.0, SAP CRM 4.0, SAP SRM 4.0, SAP SEM 4.0, SAP BW 3.5, SAP KW 7.0

source SAP R/3 4.7 source: SAP R/3 4.6C;target: SAP ECC 6.0pilot possible for other products AS ABAP 6.20

Source: all SAP R/3 releases; only MDMP or blended code page systems

source: SAP R/3 4.6C;Product: ERP/ AS ABAP

Benefits

+ established method+ usable for all products

+ reduced downtime by uptime transfer of large tables

+ one project+ optimized handling and slightly reduced downtime of combination+ preparation w/o upgrade

+ one project+ optimized handling and slightly reduced downtime of combination+ available for all releases

+ one project+ significant reduction of downtime+ improved fallback scenarios

Costs

Standard UC project+10% -100% DB storage

- SAP consulting offer, not delivered by partners - additional project hardware (full DB server)- additional test cycles

� Combination of standard upgrade + UC

+ less test efforts+ no add. hardware forUnicode conversion

� Combination of standard upgrade + UC

+ less test efforts- additional projecthardware required (full DBserver)

- SAP consulting offer, not delivered by partners - additional project hardware (full DB server)- additional test cycles

Downtime2

� 100-200 GB/hour throughput

� 1 TB � 48 h

+ SAP guarantees downtime 24h

� 1 TB � 48 h� ~ 3 TB � ~ 60h� ~ 4 TB � ~ 72h

� 1 TB � 48 h� ~ 3 TB � ~ 60h� ~ 4 TB � ~ 72h

+ goal: downtime 12h for arbitrary system sizes

Business impact

- long downtime- extra code freeze (partly)- extra upgrade project

- performance impact in production by DB triggers- extra code freeze (partly)- extra upgrade project

+ no upgrade required for language scan- performance impact in production by SPUM4- reduced functionality of SPUM4

+ full functionality of SPUMG for language scan

- performance impact in production by DB triggers

1 No upgrade, has to be separate project 2 throughput figures are rough estimates based on SAP experience; depends on customer environment

© SAP AG ADM326 12-26

Convert MDMP systems first� Do not extend or implement MDMP in existing systems – convert these

systems to Unicode � the more code pages the more complicated the conversion gets

� Unicode compatible release and SAP Support Package level need to be met

� Minimize Unicode – MDMP Interfaces � they cause most effort

“

SCP system only sending to Unicode system can be converted later

� no “data loss risk”“

Convert the fast growing systems in the first place� The bigger the system, the more effort needs to be spent on downtime“Minimize Unicode Single Codepage interfaces� Risk of transfer of non-supported characters from Unicode to Single Code Page“

If several PRD systems connect to one DEV system, convert all

PRD systems to Unicode“Check multi language requirements in different systems� Example: SCM system is often operated in EN only – low Unicode priority“

Unicode ConversionRules for complex landscape conversions

© SAP AG ADM326 12-27

� There is no MDMP support in SAP ECC 6.0 and above� Evaluate Unicode usage for single codepage systems � Choose option for Unicode conversion� Enable your customer developments for Unicode� Consider the high effort for preparing Unicode conversion

in MDMP systems (language/codepage assignment)� Test and optimize runtime/downtime of the Unicode

conversion� Plan your Unicode conversion project in close relation to

your upgrade project� Be aware of the importance of the data integrity - interface

check regarding the switch from non-Unicode to Unicode

UNICODE – Summary and Recommendations

© SAP AG ADM326 12-28

Further Information

SAP Notes

� 551344 'Unicode Conversion'� 548016 'Conversion to Unicode'� 79991 'Multi-Language and Unicode support of mySAP solutions'� 928729 'Combined Upgrade & Unicode Conversion FAQ'� 959698 'Twin Upgrade & Unicode Conversion FAQ'

SAP Service Marketplace Quick Links

� www.service.sap.com/unicode@sap� www.service.sap.com/unicode� www.service.sap.com/upgrade-erp

Required documentation

� CU&UC Guide: www.service.sap.com/unicode@sap� Component Upgrade Guide:� www.service.sap.com/upgrade-erp� Homogeneous and Heterogeneous System Copy for SAP Systems

based on SAP NetWeaver 7.0: www.service.sap.com/installnw2004s

© SAP AG ADM326 12-29

Unicode Conversion Downtime Optimization: Costs vs. Benefits

Huge

(> 4000 GB)

Business Downtime

Large

(� 4000 GB)

Medium

(� 1000 GB)

Basic

(� 500 GB)

� Usage of faster CPU s& Storage

� Table Split

� Migration Monitor

� Distribution Monitor

� Unsorted export

� Fastload

� Use latest SAPInsttools (tp, R3Load, etc)

� Database Tuning

� Additional server

� R3Load Package Split

� Standard Unicode Conversion

Costs to reduce downtime

� Minimized Downtime Service using incremental migrations (IMIG)

� Near Zero Downtime approach

© SAP AG ADM326 12-30

Customer Experiences – Throughput and Runtimes

Unicode conversion throughput

0

20

40

60

80

100

120

140

160

180

200

0 500 1000 1500 2000 2500 3000 3500 4000

DB size in GB

Sp

ee

d i

n G

B/h

� Depending on hardware and parallelization effort, the R3load throughput is normally 10 to 200 GB/h.

� Highest reported throughput was ~690 GB/h for standard conversion.

� Actual production runtimes do not increase with size because of tuning measures.

� Technical background for fastest measurement:

� 690 GB/h have been reported for 6.4 TByte (+ indices) MDMP system. Total time of 9h 15 min

for export and import.

� DB was Oracle, OS was IBM AIX.

� Old and new hardware was used for export and import with several powerful application

servers.

� Hardware was dynamically allocated based on export and import progress.

� Tables were split with DB specific measures (ROWID splitter, SAP Note 1043380).

� Customer staff performed several more Unicode conversions for production systems with sizes

between 4 and 9 TByte before this conversion. Performance increased with every execution.

© SAP AG ADM326 12-31

Combined Upgrade and Unicode ConversionProcedure Integration Schematically

What can be gained?

Customer example:

System Size in GB Generation of Unicode Nametabs Cluster Tables Check

880 5 h 12 h

526 1,5 h 20,7 h

Upgrade

Uptime Downtime

Unicode Conversion

time

Uptime Downtime

Downtime of complete procedure

Uptime Downtime

time

Downtime

Downtime of complete procedure speed up

Optimized Preparation:

Sequentially:

Uptime

© SAP AG ADM326 12-32

Example Unicode Conversion with MDS (Minimized Downtime Service)

� Technical downtime for an 8 TB Database comprises:

� 1. MDS completion 1,5hrs

� 2. Export/Import of the rest tables (4 hrs)

� 3. Technical post activities 2,5 hrs

- The total Business Downtime will be less than 24hrs

© SAP AG ADM326 12-33

© SAP 2010

Agenda: Tools and Services



10. Planning and Preparation 11. Enhancement Packages12. Unicode Conversion13. Tools and Services

14. SAP Notes for this Course


© SAP 2010

Tools and Services

Contents:� Understand how SAP upgrade services, tools and accelerators address

customer challenges and needs

� Where to find up-to-date information


© SAP 2010

Agenda

1. Introduction

2. Planning Tools for Upgrades and SAP Enhancement Packages

3. Technical Upgrade and Implementation Tools

4. Change Management Tools

5. Test Tools

6. Summary and Further Information


© SAP 2010

Plan

Main Challenges When Planning And Executing an Upgrade – Worldwide Results

Build



46%Define and allocate

project team/resources


43%Assess impact onexisting solution

29%Find information

on upgrade methods & tools

28%Interoperability

14%

4%


Others

0% 80% 100%20% 40% 60%N=1,484 N=1,484

64%Efficient testing



47%Project management



5%Others

0% 80% 100%20% 40% 60%

The report include answers from the following 360 Upgrade adoption programs: North America (Jan 2008), Brazil (March 2008), Germany (March 2008), Japan (March 2008), UK & Ireland (March 2008), Australia (April 2008), Sweden (April 2008),China (May 2008), India (May 2008) and France (Sept 2008)


© SAP 2010

Technical Innovation – Upgrades…


� Affecting the whole enterprise

� Demanding in-depth knowledge of

Business models

Processes

Application landscapes

Application modification


Discover,

prepare

and

get even

more

value

Take your time

Generate value

as you go



Fast

Low costs

and manageable impact

Protect investment

Enterprise

SOANew



© SAP 2010

How to Find the Right Tool for My Upgrade or Enhancement Package Implementation Project

What I need is a short

overview – with expedient

criteria to find the right tool

for my upgrade and SAP

enhancement package

implementation projects.

„...there are so

many different

tools available.

Which tool can

support me in my

project?“


© SAP 2010


SAP CustomerSAP

End-to-end

solution operations

SAP Experts

SAP Service

Marketplace

Upgrade RoadmapTest Workbench Maintenance Optimizer

Business Process Change Analyzer

eCATT

Test Case Templates for SAP ERP

SAP Custom Development Management Cockpit

Solution Documentation Assistant

++

Customer-specific

maintenance

20112005 2006 2007 2008 2009 2010

SAP Solution Manager 7.0 Mainstream Maintenance

SAP Enhancement Package 1for SAP Solution Manager 7.0


© SAP 2010

Tools Overview

Plan RunBuildSAP Upgrade Road Map


SAP Upgrade Experience Database

Quick Sizer Tool

Product Availability Matrix

Scenario and Process Component List


Solution Browser Tool

Technical

upgrade and

implementation

tools

Testing tools

Change

management

tools


Tools

supporting

upgrades and

enhancement

package

implementationsBusiness Function Prediction for SAP ERP

SAPup / SAPjup

Application-specific Upgrade Toolbox


SAP Enhancement Package Installer

SAINT / JSPM

Custom Development Management Cockpit

Custom Code Library

Enhanced Change and Transport System

Change Request Management

Enhancement and Switch Framework

SAP Landscape Transformation

Near Zero Downtime for ERP

SAP LoadRunner by HP

SAP Quality Center by HP

SAP Test Acceleration and Optimization

SAP Test Workbench

eCATT

SAP Test Data Migration Server

Modification Adjustment Tools: SPDD / SPAU / SPAU_ENH

SAP CloneFinder and Dynamic Usage Detector

Landscape Verification


© SAP 2010

Agenda: Planning Tools for Upgrades and SAP Enhancement Packages

1. Introduction




5. Test Tools


© SAP AG ADM326 13-10

© SAP 2010

SAP Upgrade Road Map

� SAP's standard methodology to plan and

execute the upgrade of an SAP application

� Content: Best practices and templates for

project management, functional and technical

aspects facilitating key tasks of the entire

project team

Description

Further Information / Tool Access

Benefits

� SAP Service Marketplace at:

http://service.sap.com/upgraderoadmap

� Locally in your SAP Solution Manger

� Repeatable approach that helps to mitigate risks, attack key time consumers and reduce costs and effort

� Central point of access to upgrade project information and integrated use with SAP Solution Manager

© SAP AG ADM326 13-11

© SAP 2010

Solution Browser Tool

� Discover new functionality across different SAP ERP releases and SAP enhancement packages for SAP ERP

� Assess the business benefits and the value of upgrading by comparing functional enhancements

Description


Benefits

� Via SAP Upgrade Info Center at:http://service.sap.com/upgrade-erp

� Direct access at:

http://erp.fmpmedia.com

� Tailored access to detailed and structured delta information

� Reduced effort to define a business case or value proposition for an upgrade

� Fast identification of capabilities that respond to user requirements

� Highlights:

� SAP Business Suite content available soon

� New design available soon

� The solution browser tool for SAP ERP is an online tool and is accessible in the SAP Service

Market Place or alternatively on http://erp.fmpmedia.com/

� This tool is a kind of database which contains all information about release delta functionality

� It helps to identify new features that have been added between two releases of SAP ERP or any of

the available enhancement packages and helps to find details of their respective business benefits

� The user logs on directly and freely and will get a selection on release delta functionality filtered by

source release, target release, solution area and module.

� The customers are strongly encourage to use this tool to get an insight into new functionality that the

new ERP release brings and to evaluate relevant new functionality which can then be mapped against

the customer requirements

� Doing so, the solution browser tool for SAP ERP provides the input to build a value proposition for

the upgrade

© SAP AG ADM326 13-12

© SAP 2010

� Check the existence of upgrade dependencies

between two separately installed SAP systems

in your system landscape

� Landscape analysis capabilities (planned for

next SAP Solution Manager release)

Description


Benefits

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

� Planned: SAP Solution Manager

‘Implementation / Upgrade’ work center

� Simplification of upgrade planning

� Fast and easy access to needed dependency

information for SAP products

� Reduction of risks of late problem discovery

� Reuse of customer specific system landscape

definition (planned for next release)

Upgrade Dependency Analyzer (UDA)

© SAP AG ADM326 13-13

© SAP 2010

Scenario & Process Component List (SCL/PCL)

� Allows to flexibly illustrate possible technical realization alternatives for key business scenarios and processes

Description


Benefits


http://service.sap.com/scl

� Easy identification of the components needed

to realize a new business scenario / processes

� Quick access and easy to use

� Central access point across all SAP solutions

� Customers starting an upgrade can find out

which components can - or cannot - be

combined for certain business scenarios /

processes

© SAP AG ADM326 13-14

© SAP 2010

Product Availability Matrix (PAM)

� PAM bundles technical and release planning

information for SAP software product versions

for quick reference

� Provides detailed information for SAP products

on availability and maintenance end dates,

upgrade paths, as well as technical release

information such as supported DB platforms

and operating systems

Description


Benefits


http://service.sap.com/pam

� Central access point across all SAP software product versions

� Quick access and easy to use

� Reduction of risks of late problem discovery

© SAP AG ADM326 13-15

© SAP 2010

Description


Benefits


http://service.sap.com/quicksizing

� Allows verification of hardware resources for SAP systems

� Reduces risk of performance problems

� Supports the budget planning

Delta Sizing / Quick Sizer Tool

� Joint development of SAP and its hardware

partners to support system sizing

� Can be used for delta sizing during upgrade

and SAP enhancement package projects if new

functionality is being implemented

� For pure technical upgrades the additional

resource requirements can be determined by

SAP note 85524 and related notes (per release)

© SAP AG ADM326 13-16

© SAP 2010

SAP Upgrade Experience Database and SAP Enhancement Package Experience Database

Provides statistical data about SAP ERP 6.0

upgrade projects

Additional database for SAP CRM 7.0 upgrades is

currently being build up

Statistical data for SAP enhancement package

implementation projects for SAP ERP is

available in the SAP enhancement package

experience database

Description


Benefits

� SAP Service Marketplace:

� SAP Upgrade Experience Database:

http://service.sap.com/upgradedb� SAP Enhancement Package Experience

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

� Provides consolidated project data for project duration, business downtime, reasons for upgrade, customer satisfaction etc.

� Supports project planning by answering most common questions


0 4 8 12 16 20 24 28 32 36 40 44 48 52

Weeks

Max: 36,6

Median: 21,0

Min: 12,0




SA

P R

/3 4

.6C


0 12 24 36 48 60 72 84 96 1

Hours

Max: 86,2Min: 22,9

Median: 48,0Range of values

based on 140 upgradeS

AP

R/3

4.6

C Distribution of values

© SAP AG ADM326 13-17

© SAP 2010


Description

Benefits

SAP Solution Manager Work Center

SAP Service Marketplace at:

http://service.sap.com/solutionmanager

� Accelerates initial solution documentation

� Enhanced solution and usage transparency

� Bridging the gap between business and IT with

concise solution documentation

� Cost-efficient through automated verification of

solution documentation

� Basis for optimized test planning

Verifies and rates customers’ business process

documentation

Analyzes usage of technical objects like

transactions, reports, BADIs and custom

developments

SQL statement analysis enables live system

analysis from a business perspective


� Solution Documentation Assistant verifies and rates customers’ business process documentation.

Data basis is the usage frequency of technical objects related to the business process structure. The

usage frequency gives transparency about potentially obsolete and clarity about mission-critical

objects and is an excellent starting point for initial documentation as well.

� Scope

� Analysis of template, implementation and maintenance projects

� Analyzes usage of technical objects like transactions, reports, BADIs and custom developments

� SQL statement analysis enables live system analysis from a business perspective

� Uses the existing SAP Solution Manager infrastructure like system connections and technical

statistical data

� Benefits

� Accelerates initial Solution Documentation

� Enhanced solution and usage transparency

� Enables simple and fast system consolidation

� Facilitates business improvements

� Standardization through comparison of business processes at different locations

� Basis for optimized test planning

� Cost-efficient through automated verification of Solution Documentation

© SAP AG ADM326 13-18

© SAP 2010

Business Function Prediction for SAP ERP

SAP now offers a free report: prediction of

relevant SAP enhancement package

functionality based on your existing system

usage, cluding direct access to:

Overview Presentation

Release Notes, Documentation

Test Case Catalogs

Mapping to Technical Usage

Description


Benefits


http://service.sap.com/bfp� Email: [email protected]

� Tailored access to detailed and structured delta

information for your business

� Reduced effort to define a business case or

value proposition for an upgrade

� Fast identification of capabilities that respond

to user requirements

© SAP AG ADM326 13-19

© SAP 2010

Agenda: Technical Upgrade and Implementation Tools

1. Introduction




5. Test Tools


© SAP AG ADM326 13-20

© SAP 2010

Landscape Verification for SAP Solution Manager

Analyze your landscape data in SAP Solution

Manager System Landscape to safely identify

issues in landscape description

Description


Benefits

� Add-on for SAP Solution Manager: Landscape

verification 1.0 for SAP Solution Manager in

Ramp-up since 08/2010

� Transaction LVSM


http://service.sap.com/rampup � Technology

Components

Helps finding a wide range of errors in the SAP

Solution Manager System Landscape

Provides detailed error description and information on required correction procedure

Administration based on a correct description of

the landscape will run with less effort, in

shorter time, and better success

� landscape verification 1.0 for SAP Solution Manager for TechEd session In ALM107 (NOTE that

the add-on is in Ramp-Up still and mark your slides accordingly.)

© SAP AG ADM326 13-21

© SAP 2010


Central tool for planning, executing, and

managing the installation of SAP enhancement

packages, SAP Support Packages and patches

across the entire SAP landscape

Monitors the complete maintenance procedure

for your entire SAP solution

Description


Benefits


http://service.sap.com/solman-mopz� Solution Manager

- Data maintenance: Transaction SMSY

- Maintenance Optimizer: Transaction DSWP

� Gain stability and access to innovation

� Upgrade only the enhancements applicableto your business

� Reduce risk and downtime

� Speed implementation and test less

© SAP AG ADM326 13-22

© SAP 2010

Application-Specific Upgrade (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

Description


Benefits

� 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)

© SAP AG ADM326 13-23

© SAP 2010

Description


Benefits

� Part of the upgrade software kit

� More Information is available on SDN:

http://sdn.sap.com/irj/sdn/upgradetech

� Execution of main upgrade activities

� New upgrade GUI layout and simplified

upgrade procedure for ABAP, Java, and dual

stack system upgrades (SAP NetWeaver 7.1)

� Established system switch upgrade

technology is also available for Java and dual

stack upgrades (SAP NetWeaver 7.1)

� Synchronized upgrade procedure for dual stack upgrades (SAP NetWeaver 7.0)

SAPup / SAPJup

� Standard SAP upgrade tool for ABAP (SAPup)

and Java (SAPJup)

� The tools consist of an upgrade program

(SAPup or SAPJup) and a control program

(Upgrade GUI or SDT GUI).

© SAP AG ADM326 13-24

© SAP 2010

Near Zero Downtime for ERP –Incremental Upgrade & Unicode Conversion

Description


� Available via SAP Minimized Downtime Service

� Email: [email protected]

Significant cost savings due to improved system

availability

� Optimization of system validation and sign-off

Re-usability for implementation of SAP Support

Packages, OS patches, DB patches

Late go/no-go decision and very fast reset of the

system � additional contingency

� Methodology to significantly reduce business

downtime for Upgrades, Unicode conversions

and SAP enhancement package installations

� Consistent system split with the recording of

database changes

� Synchronization of the changes between the

main system and the copy – delta replay

First Customers:

Airbus: Successful project – Go-live in Q2/2009

Further customers are currently executing

projects or investigating opportunities

Benefits

© SAP AG ADM326 13-25

© SAP 2010

SAP Enhancement Package Installer

Description


Benefits

� SAP Software Distribution Center in SAP

Service Marketplace at:

http://service.sap.com/swdc

� Uses proven technology

� New GUI layout and simplified procedure for

ABAP, Java, and dual stack systems

� Synchronized installation procedure for dual

stack systems

� Standard SAP enhancement package

installation tool for ABAP and Java

� Installs SAP enhancement packages for SAP

Business Suite 7 (and above) application and

for SAP NetWeaver 7.0 (and above)

� Execution of main installation activities

� Also able to install SAP Support Packages only

© SAP AG ADM326 13-26

© SAP 2010

SAINT / JSPM

� Tool for installation of additional SAP enhancement package components, SAP Support Packages, and Add-ons

� AS ABAP: SAINT

� AS Java: JSPM

Description


Benefits

� AS ABAP: Transaction SAINT

� AS Java: start JSPM from operating system

level

� Assure consistent deployment of components by checking prerequisites and installed software components and SAP Support Package levels

� Easy to use

� Platform independent

© SAP AG ADM326 13-27

© SAP 2010


Planned software changes

� SAP Support Packages� SAP Enhancement

Packages/ Business Functions

� Custom code changes� Customizing changes

Order to Cash

Sales Order � code changeDeliveryGoods Issue � UI changeBilling

Procure to Pay

Create PO � customizing change

Business Process Change Analyzer1)

(BPCA)

Identification of mission-critical business

processes impacted by software changes

Test scope optimization based on object

coverage and test effort analysis (with next SAP Solution Manager release)

Analysis of planned business function activation

Automatic test plan generation

Description


Benefits

SAP Service Marketplace at:

http://service.sap.com/solutionmanagerand http://service.sap.com/testing

Precise insight of impacted Business Processes

Improved handling of change events

Risk-based test scope recommendation and

automatic test plan generation

1) Available with SAP Solution Manager 7.0 enhancement package1

� Verweis: teched session on BPCA (ALM163)

� which show cases the new SAP Solution Manager functionality

© SAP AG ADM326 13-29

© SAP 2010

Custom Development Management Cockpit1)

(CDMC)

Description


Benefits

� Transaction CNV_CDMC or SAP Solution

Manager Work Center


http://service.sap.com/alm-processes � Upgrade

Management

� Usage transparency of custom developments

� Big saving potential by clearing identified obsolete custom-specific objects

� Accelerated upgrade

1) Available with SAP Solution Manager 7.0 Enhancement Package 1

Central management cockpit for custom developments and respective analysis:

Usage analysis of custom developmentsClearing analysis: Identification of potentially

obsolete objectsChange Impact Analysis: Identification of potential

impacts of an upgrade on custom codeCalculation of the effort necessary for adjusting

custom developments affected by an upgrade

� Verweis: teched session on BPCA (ALM163)

� which show cases the new SAP Solution Manager functionality

© SAP AG ADM326 13-30

© SAP 2010

Custom Code Library

� Central library that provides full transparency of all custom code objects across systems

� Helps to identify candidates for clearing projects to reduce custom code

Description


Benefits

� Planned for next SAP Solution Manager release


http://service.sap.com/alm-processes

� Cost reduction by clearing obsolete/ non-used customer objects

� Monitoring and tracking of changes of key figures for the complete SAP solution

� Provides transparency to derive proactive operations and optimizations projects

SAP StandardEnhancement w/ interfaces

Enhancement w/o interfacesModification assisted

Modification not assisted

Custom with SAP referenceCustom (independent)

© SAP AG ADM326 13-31

© SAP 2010

SAP CloneFinder1) and Dynamic Usage Detector

� Powerful tool to find clones in a system landscape (across systems)

� Determines the similarity degree of clones against SAP originals and also inherited clone versions

� Finds dynamic connections between SAP Code and custom code (Customizing, table entries)

Description


Benefits

� Planned for next SAP Solution Manager release


http://service.sap.com/alm-processes

� Fast and impressive overview in an easy to use UI to manage clones

� Direct split screen editor feature to merge clone differences

� Enhanced attributes to support the clone retirement process

1) Patent pending

© SAP AG ADM326 13-32

© SAP 2010

� Enhancement of CTS to enable the transport of

non-ABAP objects in the system landscape

� Allows to transport non-ABAP objects within

an ABAP transport request

Description


Benefits

� Transport Organizer: Transaction SE09

� Transport Management System: Transaction

STMS

� Solves transport issues by combining and

synchronizing transports in a comprehensive

approach

� Allows to use the standard transport

management transactions to centrally transport

all objects, of ABAP and non-ABAP systems

� Integrated into standard CMS transactions

Enhanced Change and Transport System(CTS)

Run

time

Env

.

Dev

. &

Tra

nspo

rt

Env

ironm

ent

Dev

.T

ools

XIDEV/QA/PRDXI

QAS

NWDI(AS Java)

ABAPDEV/QA/PRD

EPDEV

JavaDEV

JavaTEST/PRD

JavaCONS

JavaPROD

XIPROD

ABAPQAABAPPROD

EPPROD

SAP NetWeaverDeveloper Studio

ABAPWorkbench

(Non-ABAP) (ABAP)

PI Developmentenvironment

EPContent Studio

CTS

� The enhanced CTS functions are available as of Support Package Stack (SP Stack) 12 of SAP

NetWeaver 7.0. As there are further enhancements with SP Stack 14 however, the use of SP stack 14

or higher is recommended for transporting non-ABAP objects with the help of CTS.

© SAP AG ADM326 13-33

© SAP 2010

� Ensures that standard methods and

procedures are used for efficient handling of all

changes

� Manages maintenance and implementations

spanning multiple components

Description


Benefits

� SAP Solution Manager, Change Management

work center


http://service.sap.com/alm-processes � Change

Control Management

� Minimizes impact of change-related incidents

� Improves day-to-day operations

� Changes are administered, tested and

transported within the system landscape

� Workflow driven

� Project definition, control and change tracking

� Access to all involved systems

Change Request Management1) withSAP Solution Manager (ChaRM)

1) Available with SAP Solution Manager 7.0 enhancement package1

© SAP AG ADM326 13-34

© SAP 2010

Description


Benefits

� Switch Framework: Transaction SFW5

Creation of enhancements avoids modifications

and helps to save cost and effort

Enhancements are very flexible and can be

switched via the Switch Framework

Switch Framework

SAP ERP(ECC 6.04)

Enhancement and Switch Framework: Enable Optional Activation of Business Functions

The Enhancement Framework brings all

enhancement techniques under one roof

The Switch Framework controls the activation of

business functions

Activating a business function triggers switches,

which then ‘influence’ the execution of

program code, fields of tables etc.

� Switch Framework is used to:

Retrofit industry solutions in SAP ECC 6.0

Switch the business function sets within SAP

enhancement packages

� Available with SAP NetWeaver 7.0

© SAP AG ADM326 13-35

© SAP 2010

Modification Adjustment ToolsSPDD / SPAU / SPAU_ENH

� Tools for performing modification adjustment

and maintaining enhancements during upgrade

and SAP enhancement package installation

Description


Benefits

� Transaction SPDD for dictionary repository

objects

� Transaction SPAU for other repository objects

� Transaction SAPU_ENH for enhancements

� Automatic or semi-automatic adjustment

possible (depending on modification)

� SPDD adjustments possible during productive operation

� Compare old and new versions

� Reset to original if modification is not needed

any longer

� Resulting transport requests can be integrated

into subsequent SAP enhancement package

installations / upgrades

© SAP AG ADM326 13-36

© SAP 2010

SAP Landscape Transformation1) (SAP LT) Including Client Transfer with Upgrade

Description

Benefits

� Add-on for SAP Solution Manager 7.0 (SP15), available since 07/2010 in Ramp-up

� Transaction LTS (SAP LT Work Center)

� SAP Service Marketplace at:http://service.sap.com/saplt

� Increased agility of SAP solutions

� Cost-efficient and risk-minimized project execution through roadmaps and highly automated transformation solutions

� Client Transfer: Accelerated upgrade in combination with system consolidation leads to lower system complexity and reduced TCO 1) Additional license required


Cost-efficient realization of IT and/or business-driven system landscape transformation

Available transformation solutions:

Client Transfer (may include Upgrade,Unicode conversion, and OS/DB change

Chart of Accounts Conversion

Company Carve-Out

© SAP AG ADM326 13-37

© SAP 2010


Business Blueprint

Test Option 1


Business Process Change Analyzer1


Test Workbench


Test Workbench HP QTP2

MicroFocus2

Worksoft2

IBM Rational2


eCATT

Test Option 2

SAP Quality Center by HP SAP Quality Center by HP + QTP

UI based Tests

eCATT

UI + Backend Tests

SAP TDMS2

SAP TDMS2SAP Solution Manager

Business Blueprint


Business Process Change Analyzer1

SAP TAO2

Automated TestsManual TestsTest PlanningTest Scope Identification

SAP Test Management Options for SAP Customers based on SAP Solution Manager 7.0

1) Available with SAP Solution Manager 7.0 enhancement package1 2) Additional license required

Business Blueprint

Test Planning

Test System SetupTest Execution

Change

Deployment

Change Impact AnalysisSAP Solution

Update

New SAP

Solution

Test Scope IdentificationType of Change

Note: Further test options are currently in planning � see ALM115: Overview Test Management

© SAP AG ADM326 13-39

© SAP 2010

SAP Test Data Migration Server1)

(SAP TDMS)

Description


Benefits


http://service.sap.com/tdms

� Test systems contain up-to-date test data for

more accurate test results

� Improved quality of software developments

� Minimized infrastructure and maintenance

expenses

� Scrambling of sensitive data is possible1) Additional license required

� Create small, easy-to-use test environments

with consistent, relevant extracts of business

data from production systems

� Refresh test data without affecting repository

and administrative data

� Quickly transfer pre-defined business objects

or business process data to test systems

SAP TDMS

© SAP AG ADM326 13-40

© SAP 2010

Extended Computer Aided Test Tool(eCATT)

� Test automation for nearly all transactions and

business process across all SAP solutions that

run in SAP GUI

� Creation of modular tests that can be used as single-function tests and combined with other

modules to represent entire business

processes and document test activities

Description


Benefits

� Transaction SCAT (CATT), SECATT (eCATT)


http://service.sap.com/testing

� Largely reduced costs and efforts by using repeatable, automated tests of individual transactions and whole business processes

� Enables test execution in distributed system landscapes

� Integrated with Test Workbench and partner tools for seamless test management

© SAP AG ADM326 13-41

© SAP 2010

Test Workbench

Description


Benefits



� Comprehensive and mature functionality for E2E Test Management

� 1-click access from test management to test

systems

� Test sign-off including digital signatures

� Integration w/ external tools, e.g. SAP QC by HP

� Management of functional tests from test

planning via test execution to test status

reporting and test sign-off including:

Planning of manual & automated test cases

Links business processes and test cases

Test status reporting for test coordinators and

trend reports through integrated SAP BI

reports

© SAP AG ADM326 13-42

© SAP 2010

Test Case Templates for SAP Enhancement Packages for SAP ERP

Description


Benefits


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

� Via transaction SFW5 after SAP enhancement

package installation

� Can be adjusted to customer specific test

cases

� Time and cost savings due to faster test

planning based on templates

� Simplification of test preparation and execution

� Predefined test case templates are available

for new business functions that are shipped

with SAP enhancement packages for SAP ERP

� Test case templates can be used in test

workbench and are based on the scope of an

acceptance test to verify if the new

functionality

© SAP AG ADM326 13-43

© SAP 2010

SAP Test Accelerator and Optimizer1)

(SAP TAO)

Description


Benefits


http://service.sap.com/saptao

� Accelerated approach to create modularized test cases for SAP business processes

� Optimized way to maintain test cases leading to lower TCO

� Integrated with Quality Center and SAP Solution Manager

1) Additional license required

� Automation of business process testing by

composition of automated test cases

� Automatic generation of test components for

SAPGUI-based SAP business processes

� Fast composition of automated test cases

using standard functionality of SAP TAO and

Quality Center

� Optimized maintenance of automated test

cases via component-based exchange of

damaged test components after SAP updates

© SAP AG ADM326 13-44

© SAP 2010

SAP Quality Center by HP1)

� Requirements moduleDefinition of test requirements for business processes

� Test plan moduleTest planning and definition of test cases

� Test lab and defect moduleTest execution and defect management

� QuickTest ProfessionalTest automation for SAP and non-SAP applications

Description


Benefits



� Manage test strategies and processes based on

business risk

� Enable centralized management of manual and

automated test assets

� Ensure all business critical requirements are

planned for testing

� Significant reduction in post go-live defects


© SAP AG ADM326 13-45

© SAP 2010

SAP LoadRunner by HP1)

and SAP LoadRunner Enterprise Edition by HP1)

� Supports load tests in an SAP context for the

following user interfaces: SAP GUI, Web

Dynpro, http(s), and e-mail protocols

� Replaces real users with thousands of “virtual”

users

� Emulates production workload on SAP

landscapes

Description


Benefits

� SAP Service Marketplace at: http://service.sap.com/testing

� Ease of use reduces the learning curve and

script development time

� Breadth of environment support helps assure

that all enterprise applications are covered

� Reduce support costs, application response

times and time to resolve problems


© SAP AG ADM326 13-46

© SAP 2010

Information: SAP Service Marketplace – Upgrade Information

SAP Upgrade Info Center(http://service.sap.com/upgrade)

SAP Upgrade Newsletter

Upgrade-specific

Information for SAP ERP


Enhancement

Package Info Center

SAP Upgrade Tools Portfolio:http://service.sap.com/upgradetools

© SAP AG ADM326 13-48

© SAP 2010

Upgrade Services – Focus on Customer Decision Making

MaxAttention / Enterprise Support /Safeguarding for Upgrade / Upgrade Value Coaching / Upgrade Coaching

Tech

nic

al

Bu

sin

es

s

Plan

First estimation

for budgeting

Quick Upgrade

Analysis (QUA)

First value

estimation

Solution Browser

Budget planning

Detailed project

plan – Technical

Upgrade

Tech. Upgrade

Planning (QUE)

Detailed value

proposition

Upgrade Value

Assessment

Project planning

On-time,

On-budget

Upgrade

Secure

business

value

Technical

Upgrade

End-to-End

solution

operation

Competitive

differentiati-

on

Build

Project

exec.

Run

Optimization

� Focused

� Global

� Connected

� End-to-end processes

Customer Demand

Related Services

Unicode Conversion / Test Management and Optimization / Test Data Migration Service

Cu

sto

mers

Decis

ion

Po

int

Cu

sto

mers

Decis

ion

Po

int

© SAP AG ADM326 13-49

© SAP 2010

SAP Global Upgrade Services Portfolio Upgrade Services

Plan RunBuild

Quick upgrade analysis for SAP ERP

Technical upgrade implementation for SAP NetWeaver BW

Solution migration for SAP CRM

Technical upgrade for SAP CRM

Technical upgrade planning for SAP Business SuiteTechnical upgrade planning for SAP ERP

Quick upgrade analysis for SAP CRM

Technical upgrade for SAP ERP

Enablement

Provide direction and qualification

Expert Guidance

Provide detailed advice to key questions or challenges

Solution DeliveryProvide solution or knowledge transfer

Quality Management Audit and provide directions

Upgrade and migration assessment for SAP CRM

Technical upgrade planning for SAP NetWeaver BW

Upgrade value assessment

Upgrade training

SAP Safeguarding for Upgrade

Upgrade coaching for SAP ERP

© SAP AG ADM326 13-50

© SAP 2010

SAP Global Upgrade Services Portfolio Upgrade-Related Services

Plan RunBuild

Test data migration services

Test management and optimization

Unicode conversion

Enablement

Provide direction and qualification

Expert Guidance

Provide detailed advice to key questions or challenges

Solution Delivery

Provide solution or knowledge transfer

Test tool strategy workshop

SAP enhancement package planning for SAP ERP

You can find more SAP ERP services in the Global Consulting Service Portfolio for SAP ERP.

© SAP AG ADM326 13-51


SAP Note No. 156387 ________________________________________________________________________

Number 156387

Version 35 from 12.06.2008

Status Released for Customer

Set on 12.06.2008

Language EN

Master language DE

Short text References to upgrade notes regarding HR

Responsible SAP

Component PA

Personnel Management

________________________________________________________________________

Long text

Symptom

***********************************************************************

This note is a composite note concerning the HR upgrade. It contains

references to further notes on the upgrade to Releases 5.0 and 6.0.

***********************************************************************

This note is constantly updated. Therefore, we recommend that you check

the note regularly to see whether any new notes have been added that may

be useful for your system. This note lists the most important notes, but

not all the notes relevant to this subject. Some of the notes specified

may have been archived since this note was created and others may have

been changed. The status of the relevant note applies.

Note the release level for which the notes apply. The notes are listed

under the target release for an upgrade.

In addition, you should also consult notes the subject areas BC-UPG-RDM

and BC-UPG-ADDON, since these contain notes about the upgrade that may

be of interest for HR.

Other terms

Reason and Prerequisites

Solution


Content:

0/ General information/ Points to consider

I/ Upgrade to ERP 2004 (ECC 5.0)

I/ Upgrade to ERP 6.0 (ECC 6.0)


0/ General information/ Points to consider

I/ Upgrade to ERP2004 (ECC 5.0)

310852 PA-PA Performance improvement with upgrade and service packages

317722 PA-BC Upgrade information for table T77S0

353861 PA-BC HR: Upgrade to 4.6C (or higher)

374172 PY-CA Q&A: Master Note for Conversions/Upgrades - Canada

546167 PA-PA Termination in PA10: Infotype 0122 does not exist

549368 PA-PA-KR HR-KR+CN: Retrofitting HR-KR+CN to R/3 standard SAP_HR

Page 2

560272 PA-RC Unicode: Conversion of standard texts

573044 PA Unicode conversion for HR application

679275 PY-XX-BS T52C5: Report for Unicode conversion

728730 PY-XX-DT Short dump in PCP0 after upgrade fr 4.6c to a higher

release

731747 PY-XX-DT HR upgrade to 4.7 Enterprise or higher: user exit

migration

734068 Upgrade to SAP ECC 500 w/ Campus Management deinstallation

737902 PA-PA-FR HCM-FR: Social Security number in infotype 0002

763880 PY-XX-BS Upgrade and customer-specific enhancement of PC2*

structures

775435 PA-BC PM01: Missing TADIR entries of %_Includes

796825 PY-XX-IT PU12: Performance issue for PU12-conversion

829174 PA Contents & applying HRSP ERP5.00/Ext.Set5.00

871937 PA-PA-XX Unicode conversion: Language for object 'CP'

875811 PY-XX-TL RPUOCB00 only displays one personnel number

910573 Container-Migration: Structures with incompatible changes

925390 PY-NL Loonaangifte does not find payroll result after upgrade

950493 PY-AT RPCL16A*, RPCBGNA*, RPCE18A*: Announcement of end of

maintenance

962287 PY-CA CONV: RPC224K0 displays duplicate messages in output log

963753 PY-AU Change in Area Menu for Payment Summary

970556 CA-TS-SV IF_EX_CATSXT_EVENT->ON_MYLIST_SELECTED

980275 PY-CA CONV: RPC224K0 generates one IT0462 record instead of two

982769 PY-FR RPLAASF1: date of payment not shown after upgrade

997275 PY-ES Payroll results of cluster RE inconsistent after upgrade

1001192 PY-DE-PS Operation VARAB: Parameter PSS fehlt nach Upgrade

(German only)

1005516 PY-PCM Upgrade with PYCM 100_*

1013796 PA-PA Table T5ESAIT_SCREEN valid only in ERP04 (ECC500)


1032298 PY-US-TP GEN: HR3PRNA 019 - No payee text found in RPURMR00

report

1034603 PY-XX-TL H99UCDP0: Entries with 0 value created in BALHDR

1106904 HR-IT: Overview of released notes

1113536 PY-BE: Text for processing class 61 option 0 is different

1116583 PA-PA-BE: Overview screen 3000 of infotype 0100 has other

descriptions

1136159 PA-PM Commitment processor: Parameter T77SO/CHKOI is ignored

1169004 PY-BE Payroll function BLIT - Parameter 3 value missing


II/ Upgrade to ERP 6.0 and above (ECC 6.0 and above)

317722 PA-BC Upgrade information for table T77S0

374172 PY-CA Q&A: Master Note for Conversions/Upgrades - Canada

560272 PA-RC Unicode: Conversion of standard texts

573044 PA Unicode conversion for HR application

679275 PY-XX-BS T52C5: Report for Unicode conversion

871937 PA-PA-XX Unicode conversion: Language for object 'CP'

948937 PY-XX ERP2005: Syntax Error in Payroll in ERP2005 after

SAPKH60001

976001 PA-PA-RU 'Payroll Russia' SAP Menu item is missing in ERP2005

________________________________________________________________________

Valid releases

Software Component Release

from to

SAP_HR

R/3 Standard Human Resource

500 - 605 X

Further components

PY

Payroll

BC-UPG

Upgrade - general

PA-PA

Personnel Administration

________________________________________________________________________

Note attributes

Transaction codes HIER

PPOM

Transaction codes PU12

XPRA

________________________________________________________________________

Reference to related Notes

________________________________________________________________________


SAP Note No. 317722 ________________________________________________________________________

Number 317722

Version 7 vom 20.02.2003


Set on 21.02.2003

Language EN

Mastersprache DE

Short text Upgrade information for table T77S0

Responsible SAP

Component PA-BC

Basis

________________________________________________________________________

Long text

Symptom

A number of entries in table T77S0 delivered in the standard system

are incorrect. These include:

PLOGI ORGA

TRSP CORR

PLOGI EVENB

...

After upgrade, it is possible that the system response changed in many

instances in HR. For example, after the upgrade the automatic transport

connection is always active. For example, the automatic transport link is

always active after the upgrade.

Other terms

Upgrade


The error occurs during an upgrade from a release <= 4.6C to a Release

> 4.6C.

Solution

Attached to this note you fin a transport request containing the

required programs RH77S0BU and RH77S0RE.

Start the report RH77S0BU before the upgrade. This report saves the T77SO

entries in all clients in table INDX.

Copy report RH77S0RE to your customer name range so that you still have


the report after the upgrade. It is important that you also copy the

status of the report. After the upgrade you can run the copied report

per client.The report provides a list of entries that are different and

can restore the old status where necessary.The problem only concerns

entries that were changed by the customer in a former release. No new

flags should be deleted.

________________________________________________________________________

Note is not release-specific

________________________________________________________________________

References to related notes

Number Short text

____________________________________________________________

748338 Upgrade LSO (Table LSO_CUSTOMIZE_C)

505820 Backup of Table entries in T77S0 for CM Upgrade

373038 Organizational Management: data missing after upgrade

353861 HR: Upgrade to 4.6C (or higher)

________________________________________________________________________


SAP Note No. 817463 ________________________________________________________________________

Number 817463



Set on 17.11.2010

Language EN

Master language DE

Short text Addtnl info for upgrade to SAP NetWeaver 7.0 ABAP:

MaxDB

Responsible SAP

Component BC-UPG-RDM

README: Upgrade Supplements

________________________________________________________________________

Long text

Symptom

There are problems with the guide or the upgrade procedure.

Other terms


Solution

************************************************************************

This note contains only problems that are specific to MaxDB.

************************************************************************

Topics:

I/ Important general information

II/ Errors in the guide

III/ Activities prior to the upgrade

IV/ Problems during individual phases

V/ Activities after the upgrade

VI/ Documentation

© SAP AG ADM326 14-10

************************************************************************

I/ Important general information

************************************************************************

1. !!! Caution:

Note the following during ERP 2005 upgrades with the following

conditions:

Source system: 46C

Operating system: Linux X86_64 (AMD64)

Under certain circumstances, TADIR entries are incorrectly copied

during the SAP upgrade and the SAP upgrade does not notice this.

This has the following consequences:

1. After the upgrade, customer objects can no longer be edited.

2. Problems occur during the XPRAS_UPG phase because objects without

a TADIR entry were edited.

3. Problems occur during the ACT_UPG phase because objects had no

TADIR entry.

This faulty copy operation appears to be caused by a database error

in MaxDB Version 7.6.

Unfortunately, we have not managed to reproduce the error internally

at SAP using the relevant DB trace, in the same way as it has been

reproduced externally.

If you carry out an ERP 2005 upgrade subject to the conditions

mentioned above, you must implement the workaround described below:

1. After the PREPARE and before you start the actual upgrade, create

a file called R3UPPHAS.BRK in the /usr/sap/put/bin directory with

the following content line:

RUN_RDDCP4TB

2. Then start the actual upgrade, which is then halted _before_ the

RUN_RDDCP4TB phase. This is still in the uptime.

3. You can now execute the RDDCP4TB report, which must be executed

in the phase, online in transaction SE38.

When calling RDDCP4TB, you must specify two parameters:

Enter the TADIR~ value for NEWTADI.

© SAP AG ADM326 14-11

Enter the TADIR value for OLDTADI.

The system then issues 5 lines of numbers in the log. The sum of

these numbers (sum of the lines Saved, Updated, Deleted, Invalid and

Original) must match the number of entries in the original TADIR. If

this is the case, the copy procedure was successful. To display the

number of entries in the original TADIR, choose

transaction SE16 -> TADIR number of entries.

© SAP AG ADM326 14-12

4. If the RDDCP4TB report, which is executed manually, returns the

correct result, you can continue with the upgrade.

If the report returns results that do not match the number of

entries in the original TADIR, proceed as follows:

a) If this is a time-critical upgrade, execute the report manually

again once or several times, if necessary.

After the report has run and returned the correct result, you can

continue with the upgrade.

If you are unable to obtain the correct result when you run the

report, contact SAP Support.

b) If this is a test upgrade or a non-time-critical upgrade, notify

SAP Support and provide them with access to your system (component

BC-DB-DB as specified in Note 826037). They will then investigate

the report directly using the relevant database tracing (SQL trace

ST05 and precompiler trace) in an effort to identify the actual

cause of the error.

2. SAPup patches

You can check the SAPup version using the following command:

SAPup -V

Version Patch Level Remark

700-1 23.059 Correction for phase INDQUE_CHK:

Check inactive when using DCK kernel

!!! You may not use patch level 24.071 - 24.074 since, otherwise, an

error occurs in phase VIEWCHK that can only be corrected by a later

patch level as of 24.075 or higher.

SAPup patches are available on SAP Service Marketplace.

Note 663258 provides the information required for the download.

3. R/3 extended kernel in the source release

Make sure that the minimum Precompiler Runtime version, which is

required for the R/3 Extended Kernel in Note 789086,

is imported in the system. Now use transaction SM50 to check, for

example,

the trace file of a work process:

© SAP AG ADM326 14-13

> Select process > Display Trace.

The trace log names the Precompiler Runtime Version:

> C Precompiler Runtime : C-PreComp 7.3.1 Build 018 ...

4. For the SCM 5.0 upgrade, a maximum three R3trans processes should be

selected, otherwise the phase termination described in section IV

can occur in phase SHADOW_IMPORT_UPG2.

© SAP AG ADM326 14-14

5. For SCM upgrades with database instances of type "liveCache OneDB",

proceed in accordance with Note 1248891.

6. Before you start the PREPARE, check the value of the profile

parameter

dbs/ada/schema, if "sapSID" is in lower case, it must

be changed to upper case ("SAPSID").

7. To avoid the error described in section IV on Windows AMD64 in the

PREPARE phase UVERS, you should replace the tools in the directory

<DIR_PUT>/tools immediately after they were unpacked by the PREPARE

phase with 46D tool versions, for more details see section IV.

8. To avoid the problems in upgrade phase "SCEXEC_ALIAS" listed in

Section IV, select the default password "sap" for the ABAP database

shadow user in the PREPARE phase "Installation".

9. To avoid the problems mentioned in Note 37291, use at least version

7.6.01.12 or higher for SAP upgrades with MaxDB Version 7.6.

Otherwise, database terminations with the following error may occur

during the SAP upgrade:

SYSERROR -9400 AK Cachedirectory full

10. For SCM 5.1 upgrades, you require liveCache Version 7.7.02.15 or

higher for One-DB systems (liveCache and SCM schema in a database).

11. If you have to reset the SAP upgrade during the EU_IMPORT phases,

you must delete the entries of the table "/MAXDB/INDEXSTATEMENTS".

In this case, see Note 1529347.

************************************************************************

II/ Errors in the guide

************************************************************************

© SAP AG ADM326 14-15

************************************************************************

III/ Activities prior to the upgrade

************************************************************************

OS : UNIX/Linux

With SAP Kernel 640_EX2 or higher, the new MaxDB DBSL (dbsdbslib) and,

therefore, disp+work use the SQLDBC interface (libSQLDBC) of the MAXDB

client installation. To ensure that the MaxDB DBSL can find and load the

libSQLDBC, the relevant system variables that are dependent on the

operating system must be set. For all precompiler-based SAP applications

(upgrade of source release) with an SAP kernel lower than Kernel

640_EX2, the .dbenv scripts must therefore be updated in the home

directory of sidadm on all application servers.

Otherwise, terminations will occur when executing tools of the upgrade

SAP kernel under <UPGDIR>/abap/exe. In the developer trace, the problem

will be displayed as follows:

M calling db_connect ...

B create_con (con_name=R/3)

B Loading DB library '<path>/dbsdbslib.so' ...

M *** ERROR => DlLoadLib: dlopen()= libSQLDBC76.so: cannot open shared

object file: No such file or directory -> DLENOACCESS (0,Success)

B *** ERROR => Couldn't load library '<path>/dbsdbslib.so'

As sidadm user, unpack the DBENV.SAR package that is available in Note

1066891 into a temporary directory using the following command:

SAPCAR -xvf DBENV.SAR

Copy the files DBENV.CSH and DBENV.SH into the home directory of the

sidadm user and overwrite the .dbenv files contained in that directory:

cp DBENV.CSH /<homedirectory>/.dbenv_<hostname>.csh

cp DBENV.SH /<homedirectory>/.dbenv_<hostname>.sh

If you perform the upgrade with MaxDB 7.6.00.09, check the database

parameter MAX_SPECIALTASK_STACK before the start of the PREPARE. If

MAX_SPECIALTASK_STACK is lower than 200, set the parameter to 200. As of

MaxDB 7.6.0.10, you do not need to change this database parameter.

If you carry out the upgrade with a MaxDB version lower than 7.6.00.15,

the OPTIMIZE_OPERATOR_JOIN parameter must be set to NO, otherwise the

Signal 11 error (knldiag) can occur during the upgrade:

DBSTATE Caught signal 11(SIGSEGV)

COREHAND ABORTING due to signal 11

(SAP internal information: PTS 1137641)

If you upgrade from Release 4.5B or lower with MaxDB 7.6.00.14 or a

© SAP AG ADM326 14-16

lower build, check the _PACKET_SIZE database parameter before the start

of the PREPARE. If _PACKET_SIZE is larger than 36864, set this parameter

to 36864 before starting the PREPARE. Otherwise, the PREPARE will

terminate because R3trans cannot connect to the database. After the

upgrade, you should set the database parameter to the maximum value

131072.

© SAP AG ADM326 14-17

If you perform the upgrade from Release 4.6D with MaxDB 7.6.00.14 or a

lower build, check the _PACKET_SIZE database parameter before the start

of the PREPARE. If _PACKET_SIZE is larger than 126125, set this

parameter to 126125 before starting the PREPARE. Otherwise, the PREPARE

will terminate because R3trans cannot connect to the database. After the

upgrade, you should set the database parameter to the maximum value

131072.

************************************************************************

IV/ Problems during individual phases

************************************************************************

Phase: UPGRADE general

OS : any

If you use a MaxDB version that is lower than 7.6.01.12, the database

may terminate with the following log entry:

SYSERROR -9400 AK Cachedirectory full

In this case, restart the database and continue the SAP upgrade process.

For this reason, further database terminations may occur during the SAP

upgrade. In this case, proceed in the same way.

For information about how you can solve this problem, see section I.

Phase: PREPARE

OS : LinuxIA64 and LinuxPPC

The database connection closes and the log file

records signal 11 (SIGSEGV). Database parameter USE_COROUTINES

is set to the default value YES. The necessary procedure is described in

Note 851105.

Phase: READDATA_UPGTOOLS (PREPARE)

When the PREPARE is repeated, this phase may be terminated, and the file

<PUT_DIR>/log/CAR.SAV may issue the following error:

dbadashoplib.dll (error 28). The process cannot access the file

because it is being used by another process.

Or:

SAPCAR: could not open for writing

<UPGDIR>/abap/bin/dbadashoplib.<extension> (error 28). Text file busy

Workaround 1:

Choose first "Cancel" and then "Stop Upgrade" from the menu of the

Upgrade Assistant, then restart the Upgrade Assistant and choose

"Repeat" to continue with the upgrade process.

Workaround 2:

© SAP AG ADM326 14-19

Phase: DBCHK_PRE (PREPARE)

OS : Unix

Source release: 31I

A phase termination occurs and a SharedLibrary path is specified in the

<DIR_PUT>/log/DBSDBDLL.LOG file, which references a dependant

directory of the database software: /sapdb/<SID>/db/...

Enhance the SharedLibrary path variable

SUN, DEC, SNI: LD_LIBRARY_PATH

HP : SHLIB_PATH

AIX: LIBPATH

in the environment of the <sid>adm user by adding the correct path to

the libSQLDBC76 library:

/sapdb/programs/lib[/lib64]

AND

the path specified in file DBSDBDLL.LOG.

Then repeat the phase.

Phase: INITPUT_PRE (PREPARE)

DB: 7.3.00

Phase INITPUT_PRE hangs because the "xuser -& c list" command executed

from SAPup does not work on DB Version 7.3.00.

Carry out the DB version change on Version 7.6.00 required for the

PREPARE, and repeat the phase.

Phase: START_SHDI_FIRST

OS : Unix

When you start the shadow instance manually on the remote host, the

connection to the database does not work if the settings for the

<sid>adm user environment are not correct. The problem is that the

program cannot find the library libSQLDBC. Check if the libSQLDBC

library is available in either of the /sapdb/programs/lib or

/sapdb/programs/lib/lib64 directories, and add this directory to the

SHLIB_PATH (HP-UX), LIBPATH (AIX) or LD_LIBRARY_PATH for the <sid>adm

user.

Phase: SHADOW_IMPORT_UPG2

A phase termination may occur with the SQL error "-60".

Repeat the phase in this case.

© SAP AG ADM326 14-20

Phase: SHADOW_IMPORT_UPG2

A phase termination may occur and you see the following SQL error in the

log files of the upgrade:

SQL error "-1000" Too many lock requests

To avoid the problem, you have the following options:

1) Increase the MAXLOCKS database parameter (recommended)

Increase the MAXLOCKS database parameter based on the number of R3trans

selected. To do this, you should apply the following rule of thumb:

R3trans number * 150,000 = MAXLOCKS value

(however, at least 800,000)

Note that parameter changes only become active when you restart the

database.

2) Reduce the R3trans parallelism

To do this, call SAPup as described below:

"SAPup set std"

You can use this call to change the upgrade parameters specified in the

PREPARE In this case, choose an R3trans process number of 3. To activate

the change, you must then repeat the phase using the "Init" option.

Phase RUN_RSPTBFIL_DEST

Failure to comply with point I.6 in this note can lead to the following

error:

R3up> BATCH JOB RSPTBFIL FAILED

Replace all incidences of sap<SID> with SAP<SID> in the entries of the

startsap and stopsap scripts in the

<PUTDIR>/<SID>/homeshd/<SID> directory:

You must restart the shadow instance for the changes to become active:

<PUTDIR>/<SID>/homeshd/<SID>/stopsap r3

<PUTDIR>/<SID>/homeshd/<SID>/startsap r3

Phase SCEXEC_ALIAS

The phase terminates with the following error:

ERROR: no logfile list SQLEXEAL.LOG

The SCEXEC_A.EC0 log file contains the following entry:

TRACE-INFO: 49: [dbsdbsql ,00000]

*** ERROR => Connect to database

rc = -4008 (POS(1) Unknown user name/password combination)

This error is due to the fact that SAPup created the SAP<SID>SHD user

with a default password instead of the password chosen in the PREPARE.

Use the following statement to change the password to the password

chosen in the PREPARE:

1) dbmcli -d <DBSID> -u control,<control password>

-uSQL superdba,<superdba password>

© SAP AG ADM326 14-21

2) sql_execute alter password SAP<SID>SHD <new password>

You can then repeat the SCEXEC_ALIAS phase and continue with the

upgrade.

© SAP AG ADM326 14-22

Phase: KX_SWITCH_2

OS : Windows

System : SCM

For systems with liveCache on the central instance, the phase

KX_SWITCH_2 terminates because the liveCache is using a file of the SAP

kernel, which cannot be used as a consequence:

SEVERE ERROR: Could not delete file '<path>icudt30.dll' in

Reason: 'ErrorMessage: Access is denied.

Shut down the liveCache, continue the SAP upgrade and restart the

liveCache immediately after phase KX_SWITCH_2. (SAP internal

information PTS 1149478)

Phase: START_SHDI_FIRST

This phase terminates and in the dev traces of the shadow system

<DIR_PUT>/<SAPSID>/...

the following entries are displayed:

ERROR => the connected dbid (<DBSID>) is not the right database id

[dbslsdb.cpp 4652]

ERROR => application has to connect to rsdb/dbid=<SAPSID>

(<SAPSID> does not equal <DBSID>)

To the instance profile of the shadow system

<DIR_PUT>/<SAPSID>/SYS/profile/<SAPSID>_DVEBMGS<nr>_<host>

add, the following line:

rsdb/dbid = <DBSID>

Then stop the shadow system.

<DIR_PUT>/bin/SAPup stopshd

Then repeat the upgrade phase.

Phase: INDQUE_CHK

The phase terminates and the following trouble ticket exists:

SAPup broke during phase INDQUE_CHK in module MAIN_SHDCRE

/ Import and Modification Transfer

Error Message : Index creation during database load is inconsistent,

please search section IV of note 817463 for 'INDQUE_CHK'

Check whether the problem described in Note 1428985 exists.

Phase: EU_IMPORT

ERROR: Execute for create index <INDEXNAME> on <TABNAME> failed

(dbrc=103) (SQL error -942)

See Note 1529347.

© SAP AG ADM326 14-23

************************************************************************

V/ Activities after the upgrade

************************************************************************

If you set the OPTIMIZE_OPERATOR_JOIN parameter to NO before the upgrade

for MaxDB Versions lower than 7.6.00.15, you should now reactivate this

parameter.

Schema user SAPR3SHD or SAP<SID>SHD

In the database, the upgrade created the schema user SAPR3SHD or

SAP<SID>SHD for the shadow system. This schema is not deleted at the end

of the upgrade. It can be kept for a follow-up upgrade. Alternatively,

you can delete it using database tools.

As a result of delivery errors, this schema may still contain database

objects

(synonyms). You can also delete these.

************************************************************************

VI/ Documentation

************************************************************************

************************************************************************

________________________________________________________________________

Valid releases


from to

SAP_BASIS

SAP Basis component

700 - 702

© SAP AG ADM326 14-24

________________________________________________________________________


Number Short text

____________________________________________________________

1529347 Upgrade: R3load Error "Unknown Table Name"

1481369 Release of MaxDB Version 7.8 for older SAP versions

1293745 Add. info.: Upgrade to SAP NetWeaver 7.0 EHP 1 SR1 (ABAP)

1293744 Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP1 SR1

1293387 Add. Info. on Upgrading to SAP SRM Server 7.0 SR1 ABAP

1292071 Add. info. on upgrading to SAP SCM 7.0 SR1 ABAP

1292070 Add. info. on upgrading to SAP CRM 7.0 SR1 ABAP

1292069 Add. info. on upgrading to SAP ERP 6.0 EHP4 SR1 ABAP

1289161 Consulting note: Procedure for upgrading SAP F&R 5.0 to 5.1

1276895 Add. info. about Upgrading to SAP Solution Manager 7.0 EHP1

1248891 SAP SCM upgrade to liveCache OneDB

1156970 Add. info. on upgrading to SAP SCM 7.0 ABAP

1156969 Add. info. on upgrading to SAP CRM 7.0 ABAP

1156968 Add. info. on upgrading to EHP 4 for SAP ERP 6.0 ABAP

1156844 Add. Info. on Upgrading to SAP SRM Server 7.0

1146578 Central Note: Upgrade to Systems on SAP NetWeaver 7.0 EHP1

1142632 Enhancements for Enhancement Package installer: MaxDB

1123603 ABAP Dictionary adjustments for MaxDB 7.7

1108510 Add. Info.: Upgrade to SAP SRM Server 5.5 SR3 ABAP

1099841 Add. info.: Upgrade to SAP NW 7.0 Support Rel. 3 ABAP

1071404 Add. info.: Upgrade to SAP CRM 2007 ABAP

1039395 Add. info.: Upgrade to SAP CRM 5.2 ABAP


1002641 SQL error -4004/-942 in DB02 during index consistency check

975861 Add. Info.: Upgrade to SAP SRM Server 6.0 ABAP

961513 Add. Info.: Upgrade to SAP SRM Server 5.5 SR2 ABAP

961512 Add. info. on upgrading to SAP SCM 5.0 SR2 ABAP

961511 Add. info.: Upgrade to SAP CRM 5.0 SR2 ABAP

961410 Add. info. on upgrading to SAP ECC 6.0 SR2 ABAP

960783 Add. info.: Upgrade to SAP NW 7.0 Support Rel. 2 ABAP

947991 Add. info.: Upgrade to SAP CRM 5.1 ABAP

930416 MaxDB precompiler terminates with signal 11

925240 Add. Info. on upgrading to SAP SCM 5.0 SR1 ABAP

916795 Replacement for MaxDB system table SYS.ALL_TAB_COLUMNS

913971 Add. info. on upgrading to SAP ERP Central Component 6.0 SR1

913849 Add. info.: Upgrade to SAP CRM 5.0 ABAP SR1

913848 Add. Info.: Upgrade to SAP SRM Server 5.5 SR1

905029 Add. info.: Upgrade to SAP NW 2004s Support Rel. 1 ABAP

© SAP AG ADM326 14-25

898358 R3load: Entries remain in "/MAXDB/INDEXSTATEMENTS"

890202 Add. info.: Upgrade to SAP Solution Manager 4.0

851105 Deactivating the co-routines for MaxDB on UNIX systems

826488 Enhancements to upgrade on SAP CRM 5.0 ABAP

826487 Add. Info.: Upgrade to SAP SRM Server 5.5 ABAP


826092 Add. info. on upgrading to SAP ERP Central Component 6.0

818322 Add. info.: Upgrade to SAP NW 2004s ABAP

814704 MaxDB Version 7.6 parameter settings for OLTP/BW

789086 Precompiler Runtime to be used for Extended Kernel

415073 Termination or very long runtime in prepare phase DYNSPCADD

________________________________________________________________________

© SAP AG ADM326 14-26

SAP Note No. 1298878 ________________________________________________________________________

Number 1298878



Set on 21.01.2011

Language EN

Master language EN

Short text Installation of SAP Enhancement Package 5 on SAP ERP 6.0

Responsible SAP

Component BC-UPG-ADDON

Upgrade Add-On Components (IS)

________________________________________________________________________

Long text

Symptom

You update and enhance existing software components using Enhancement

Package 5 on SAP ERP Central Component 600 (referred to here as SAP ECC

600).

Other terms

Updating and enhancing existing software components, Enhancement

Package, DVD 51039101, 605, SAPK-605DHINEAAPPL, SAPK-605DHINEADFPS,

SAPK-605DHINEAFINSRV, SAPK-605DHINEAGLTRAD, SAPK-605DHINEAHR,

SAPK-605DHINEAPS, SAPK-605DHINEARETAIL, SAPK-605DHINECCDIMP,

SAPK-605DIINERECRUIT, SAPK-605DHINFICA, SAPK-605DHINFICAX,

SAPK-605DIINFINBASIS, SAPK-605DHININSURANC, SAPK-605DHINISCWM,

SAPK-605DHINISH, SAPK-605DHINISM, SAPK-605DHINISOIL, SAPK-605DHINISPSCA,

SAPK-605DHINISUT, SAPK-605BGINLSOFE, SAPK-605DHINSAPAPPL,

SAPK-605BGINSEMBW, SAPK-605AGINERECRUIT, SAPK-605AGINFINBASIS,

SAPK-605AGINLSOFE, SAPK-605AGINSEMBW, SAPK-605IHINECCSE,

SAPK-605GGINECCSE.

© SAP AG ADM326 14-27


You plan an update and enhancement of existing software components of

SAP ERP 6.0 (this is referred to here as "installation").

Solution

This note provides additional information to the document 'How-to

Install Enhancement Package 5 for SAP ERP 6.0'. This guides is available

in the SAP Software Distribution Center at http://service.sap.com/swdc

-> Installations and Upgrades -> Installations and Upgrades - Entry by

Application Group -> SAP Application Components -> SAP ERP -> SAP ERP

ENHANCE PACKAGE -> EHP5 FOR SAP ERP 6.0 -> Technical Documentation.

This note is updated constantly. Make sure you have the current version

of this note before you start the installation.

Contents

I/....Keywords

II/...Important General Information

III/..Corrections to the Guide

IV/...Preparing the EHP Installation

V/....Problems During the EHP Installation

VI/...Problems After the EHP Installation

VII/...SAINT Passwords

VII/..Chronological Summary

-----------------------------------------------------------------------

I/ Keywords

Roadmap step 'Extraction', phase KEY_CHK: see central SAP Enhancement

Package Installer Note

Roadmap Step Checks, Phase EHPKEY_CHK: 2658825

Phase ADDONKEY_CHK: 2096499

For SAINT passwords, see "VII/ SAINT Passwords"

© SAP AG ADM326 14-28

II/...Important General Information

---------------------< D029128 DEC/23/10 >---------------------------

SEM-BW Add-On

If SEM-BW is installed on your SAP NetWeaver BW Hub system, see SAP Note

1531022 for information about the different landscape options.

---------------------< D053561 MAY/06/10 >-----------------------------

SAP ERP Components on SAP NetWeaver Systems

If additional SAP ERP Components (ERECRUIT, SEM-BW, FINBASIS or LSOFE)

are installed on your SAP NetWeaver system, see SAP Note 1326576 for

information about the update process.

---------------------< D031901 JUL/07/10 >-----------------------------

SRM Add-On

If you want to install the SRM Add-On 7.0 Enhancement Package 1 für ERP

6.0 EHP5 (SRM One-Client Scenario), see SAP Note 1321231 for more

information.

-----------------------------------------------------------------------

III/..Corrections to the Guide

/

-----------------------------------------------------------------------

IV/...Preparing the EHP Installation

---------------------< D033315 JAN/21/11 >----------------------------

Delete View ZVMSEG

At the latest before the start of the Preprocessing Roadmap Step, delete

the view ZVMSEG if it exists in your system.

This prevents and the following activation error in phase ACT_UPG:

Check view ZVMSEG (DDIC/11.01.11/00:16)

Field BWART: Position relative to Basis table cannot be exchanged

Field DMBTR: Position relative to Basis table cannot be exchanged

Field KUNNR: Position relative to Basis table cannot be exchanged

© SAP AG ADM326 14-29

Field LIFNR: Position relative to Basis table cannot be exchanged

View ZVMSEG is not consistent

For more information, see SAP Note 304670.

© SAP AG ADM326 14-30

---------------------< D033315 JAN/21/11 >----------------------------

IS-H only: Use updated Support Package Stacks

If you use IS-H, then do not apply Support Package Stacks 03 - 05 that

you have downloaded before January 14, 2011. Do only apply the updated

versions of these Support Package Stacks that have been provided for

download on January 14. For more information, see SAP Note 1549249.

---------------------< updated AUG/03/10 >----------------------------

---------------------< D037264 JUL/07/10 >----------------------------

Components and Support Package requirements

o Regardless of the initial release, it is essential that you

import EHP5 including EHP5 Support Package Stack 01 (or higher)

to avoid errors.

We always recommend that you include the Support Package stack

that is currently proposed by SAP Solution Manager in the update

process.

o Calculation of Support Packages for Industry Solutions

When the Maintenance Optimizer calculates the required software

packages for the enhancement package installation, the behavior

regarding Support Packages for industry solutions is as follows:

- If you have not activated any industry solution in your

system, then the Maintenance Optimizer calculates Support

Packages for all industry solutions.

- If you have activated one or more industry solutions, the

Maintenance Optimizer only calculates Support Packages for the

activated industry solutions.

o If you have installed the software component ECC-SE, the

following applies: The ECC-SE release must always correspond to

the installed ERP Enhancement Package release. This means that

when you update to ERP Enhancement Package 5, the component

ECC-SE must also be updated to Version 605.

o You can also install the components SEM-BW 605

(SAPK-605AGINSEMBW), FINBASIS 605 (SAPK-605AGINFINBASIS),

ERECRUIT 605 (SAPK-605AGINERECRUIT) and LSOFE 605

(SAPK-605AGINLSOFE) on a pure SAP NetWeaver system (SAP NetWeaver

© SAP AG ADM326 14-31

7.0 with Enhancement Package 2).

o DVDs for Enhancement Package 5 are not automatically sent to

customers. If you cannot use the Maintenance Optimizer for the

download, request the DVD with the material number 51039101 and

also the DVDs of SAP NW 7.02 (if not yet installed) from your

local subsidiary, or download the DVD from SAP Service

Marketplace. Copy the content of the DVDs to the download

directory, which is then accessed by the SAP Enhancement Package

Installer.

© SAP AG ADM326 14-32

V/....Problems During the EHP Installation

-------------------< D035496 DEC/14/10 >-------------------------------

LOAD_SWITCHSTATES_LOST shortdump

If the procedure stops in phase MAIN_SHDRUN/ACT_UPG with a

LOAD_SWITCHSTATES_LOST shortdump, then stop the shadow instance and

start the shadow instance again.

This error can occur if you selected several technical usages and SAP

Kernel 720 with patch level 70 is used for the shadow instance.

--------------------< D032835 NOV/16/10 >------------------------------

Failure of Phase SHADOW_IMPORT_INC

When you update your system from SAP ERP 6.0 or enhancement package 3

for SAP ERP 6.0 to enhancement package 5, the following error can occur:

"Checks after phase MAIN_SHDIMP/SUBMOD_SHIMP/SHADOW_IMPORT_INC were

negativ!

Last error code set Unresolved requests in buffer ...

Check logfiles 'SHDALLIMP.ELG! ...

For a solution, see SAP Note 1525742.

----------------------< D037264 JUL/07/10 >----------------------------

Include Support Packages

To avoid known errors, we recommend that you include all available

Enhancement Package 5 Support Packages and the relevant Support Package

stack directly in the queue. The SAP Solution Manager also proposes

these.

----------------------< D037264 JUL/07/10 >----------------------------

DDIC Activation

The following errors can occur during the DDIC Activation:

o If your system has a lower SP level than SAP_BASIS SP13 in the

start release, the following error for view V_SH_ANKP occurs and

can be ignored:

3 EDO525XActivate dependent view "V_SH_ANKP" 1

EDH202 Check dependent search help "SH_ANKP" 1

EDH103 Search help "SH_ANKP" is consistent

4EEDT721 View "V_SH_ANKP" cannot be buffered

© SAP AG ADM326 14-33

o The search helps H_5ITCN and H_5ITTT cannot be activated:

- "Srch Help" "H_5ITCN" could not be activated

- "Srch Help" "H_5ITTT" could not be activated

If Support Package 35 for SAP_HR 600 is already contained in the

source release, repeat the activation phase. If a lower Support

Package level is contained in the source release SAP_HR 600,

ignore the error and see Note 1243014.

© SAP AG ADM326 14-34

----------------------< D037264 JUL/07/10 >----------------------------

Errors During the Main Import

o If you source release is lower than ERP 6.0 EhP3, the following

error occurs during the main import of ECC-DIMP 603 into

non-Unicode systems: 'duplicate key error during insert into

table SALRTCATCT occured'

Solution: see SAP Note 1083533, unit 5. -> Errors during the

installation

----------------------< D037264 JUL/07/10 >----------------------------

Errors in the method execution

When you update from Enhancement Package 1, the method FDT_AFTER_IMPORT

terminates with return code 0012.

Solution: Implement Note 1053777 and then continue the installation.

----------------------< D037264 JUL/07/10 >----------------------------

Generation errors

o INSURANCE 605:

Program SAPLVKKN, include LVKKNU27: Syntax error in line 000034

INCLUDE report 'ISCDGEN_ACC_OP' not found.

Solution: After you install INSURANCE 605, execute the report

SAPRGEN_CD to generate the includes ISCDGEN_ACC_OP,

ISCDGEN_ACC_OPK and ISCDGEN_COPA.

o IS-H 605:

Screen SAPLNCOOPA003 0100: You can ignore the error (see release

note ISH_461_US_KLASSEN).

VI/...Problems After the EHP Installation

----------------------< D002243 23/DEC/10 >--------------------------

Renamed DIMP Implementations

Some DIMP Implementations have been renamed. If you have created your

own implementations, the references to SAP´s DIMP implementations are

lost because of their new names. You have to redo your implementations.


© SAP AG ADM326 14-35

----------------------- <D029263 15/APR/10 >--------------------------

SAP Master Data Governance Customers Only: Migrating Settings

If you have activated the business function Financial Master Data

Management: Charts of Accounts (FIN_MDM_ACC) in EHP 4 and want to use

the business function Master Data Governance, Generic Functions

(MDG_FOUNDATION) after the update to EHP 5, some of the existing data

needs to be migrated to new tables, further settings have to be made in

new Customizing activities, and the new portal content has to be

adapted. For more information, see SAP Note 1456270.

Delivery Customizing is imported only into client 000. If you want to

copy Customizing into existing clients, read Note 337623.

VII/...SAINT Passwords

These passwords are only required, if you install additional technical

usages with SAINT. This is only possible for systems, which have the

technical usage "Central Applications" already installed.

Component Password

SAPK-605BGINERECRUIT CD11D22C4B

SAPK-605BGINLSOFE C806AE4435

SAPK-605DHINEAAPPL DE13CB5034

SAPK-605DHINEADFPS C813D45031

SAPK-605DHINEAFINSRV C70DD42245

SAPK-605DHINEAGLTRAD C217D53156

SAPK-605DHINEAHR DC63A7503D

SAPK-605DHINEAPS DD63A75025

SAPK-605DHINEARETAIL CB17C6394B

SAPK-605DHINECCDIMP CA0ACA2236

SAPK-605DHINFICA CF63A45836

SAPK-605DHINFICAX CF1BA45836

SAPK-605DHININSURANC DB11CA3145

SAPK-605DHINISH 8E438B621D

SAPK-605DHINISM 8E438B6218

SAPK-605DHINISOIL C70FAB423A

SAPK-605DHINISPRA DC02AB4225

SAPK-605DHINISPSCA DD00CA4225

SAPK-605DHINISUT DA63AB4220

SAPK-605IHINSEMBW CC14B15938

SAPK-605IHINECCSE DD06A75F36

SAPK-605IHINFINBASIS CC02D73C48

SAPK-605IHINISCWM D90EAB4F36

© SAP AG ADM326 14-36

VII/..Chronological Summary

Date.......Topic....Short Description

-----------------------------------------------------------------------

JAN/21/11...IV......IS-H only: Use updated Support Package Stacks

JAN/21/11...IV......Delete View ZVMSEG

DEC/23/10...VI......Renamed DIMP Implementations

DEC/23/10...II......SEM-BW Add-On

DEC/14/10...V.......LOAD_SWITCHSTATES_LOST shortdump

NOV/16/10...V.......Failure of Phase SHADOW_IMPORT_INC

JUL/07/10...II......SRM Add-On

JUL/07/10...IV......Components and Support Package Requirements

JUL/07/10....V......Include Support Packages

JUL/07/10....V......DDIC Activation

JUL/07/10....V......Errors During the Main Import

JUL/07/10....V......Errors in the method execution

JUL/07/10....V......Generation errors

JUL/07/10....V......Postprocessing

MAY/06/10...II......SAP ERP Components on SAP NetWeaver Systems

APR/15/10....VI.....SAP Master Data Governance: Migrating Settings

© SAP AG ADM326 14-37

________________________________________________________________________

Valid releases


from to

SAP_APPL

SAP Application

605 - 605

IS-M

IS Media

605 - 605

IS-OIL

SAP OIL & GAS

605 - 605

ECC-SE

ESA FAST TRACK (ERP)

605 - 605

EA-HR

SAP R/3 Enterprise AddOn Human Resource

605 - 605

EA-RETAIL

SAP R/3 Enterprise AddOn Retail

605 - 605

EA-PS

SAP R/3 Enterprise AddOn Public Sector

605 - 605

EA-FINSERV

SAP R/3 Enterprise AddOn Financial Servi

605 - 605

FINBASIS

FINBASIS

605 - 605

INSURANCE

SAP Insurance

605 - 605

EA-APPL

SAP R/3 Enterprise PLM, SCM, Financials

605 - 605

EA-GLTRADE

SAP R/3 Enterprise Global Trade

605 - 605

FI-CAX

FI-CAX: Extended FI-CA

605 - 605

© SAP AG ADM326 14-38

LSOFE

Learning Solution - Front End

605 - 605

ERECRUIT

E-Recruiting

605 - 605

FI-CA

FI Contract Accounts Receivable and Paya

605 - 605

EA-DFPS

SAP R/3 Enterprise Defense Forces & Publ

605 - 605

SEM-BW

SAP Strategic Enterprise Management

605 - 605

ECC-DIMP

ECC Discrete Industries Mill Products

605 - 605

IS-H

IS-Hospital

605 - 605

IS-PS-CA

IS-Public Sector Contract Accounting

605 - 605

IS-PRA

605 - 605

IS-UT

IS-UT

605 - 605

________________________________________________________________________


Number Short text

____________________________________________________________

1456663 SAINT: Enhancement Package 5 components on NW 7.02

1344564 Maintenance Optimizer: Check system landscape

1302772 Central Note - SAP Enhancement Package Installer 7.00

337623 Customizing after installation or upgrade

________________________________________________________________________

© SAP AG ADM326 14-39

SAP Note No. 1299009 ________________________________________________________________________

Number 1299009



Set on 11.01.2011

Language EN

Master language EN

Short text Central Note: Upgrade Systems on SAP NetWeaver 7.0

EHP 2

Responsible SAP



________________________________________________________________________

Long text

Symptom

Upgrade to SAP Systems based on SAP NetWeaver 7.0 including SAP

enhancement package 2.

Other terms

Upgrade, SAP NetWeaver 7.0 EHP2, central Note


*

Solution

This is the central Note for upgrades to SAP systems based on SAP

NetWeaver 7.0 including enhancement package 2.

----------------------------------------------------------------------

CONTENTS

Part A: Upgrade Notes and Keywords

Part B: New Upgrade Program Release and Version

Part C: Correction Package for the Upgrade Program

Part D: General Problems / Information on all Upgrades

............I/ ...... Upgrade Keyword

© SAP AG ADM326 14-40

............II/ ..... Important General Information

............III/ .... Corrections to the Guide

............IV/ ..... Errors on the CD-ROM

............V/ ...... Preparing the Upgrade

............VI/...... Problems During the Upgrade Phases

............VII/ .... Problems After the Upgrade

............VIII/ ... Chronological Summary

________________________________________________________________

________________________________________________________________

© SAP AG ADM326 14-41

Part A: Upgrades Notes and Keywords

For more information on the upgrade of your specific application and the

current keyword, see one of the following Notes:

SAP NetWeaver 7.0 EhP2.......Note 1299008

SAP CRM .....................Note 1341978

SAP ERP .....................Note 1341975

SAP SCM .....................Note 1341981

SAP SRM .....................Note 1448239

Database................................................ Note number

______________________________________________________________________

SAP MaxDB .................................................. 817463

IBM DB2 for i ..............................................1168235

IBM DB2 for Linux, UNIX, and Windows ....................... 819876

IBM DB2 for z/OS ........................................... 815202

MS SQL Server .............................................. 825146

Oracle ..................................................... 819655

________________________________________________________________

________________________________________________________________

Part B: New Upgrade Program Release and Version

Before you start the upgrade program, check if there is a new release

and version of SAPup.

The current SAPup release is:

SAPup version lmt_001

1. To determine the currently used SAPup release and version,

2. proceed as follows:

- UNIX: Go to <UPGRADE_DIRECTORY>/abap/bin and call './SAPup

-V'.

© SAP AG ADM326 14-42

Under UNIX, you have to enter the ABAP upgrade directory to

allow SAPup to use the correct OS libraries.

- Windows: Go to <UPGRADE_DIRECTORY>\abap\bin and call

'.\SAPup.exe -V'.

- IBM i: ADDLIBLE <SAPuplib>

SAPup UPGDIR(<DIR_PUT>) PARMLIST(' -V')

© SAP AG ADM326 14-43

3. SAPup displays the following message:

This is SAPup version lmt_001, patch level <major>. <minor>

To download SAPup from SAP Service Marketplace go to http://service.sap.

com/patches.

Select Entry by Application Group -> Additional Components -> Upgrade

Tools -> SAPUP UNICODE -> SAPUP 7.02 UNICODE -> <OPERATING SYSTEM> ->

SAPUPLMT001 archive.

Caution: Always use the Unicode SAPup release and version regardless

of your SAP system being Unicode or non-Unicode!

Unpack the archive to a temporary location. In roadmap step

"Extraction", the upgrade program asks you to specify the path to the

new SAPup.

To get a list of all patches contained in a specific SAPup, call

SAPup -V

________________________________________________________________

________________________________________________________________

Part C: Correction Package for the Upgrade Program

Before the upgrade, it is VITAL that you apply the correction package

for the upgrade program, if available.

The correction package is provided as SAR archive that you must

integrate into the upgrade. Each SAR archive is valid for only one

product (= exactly one delivered DVD set).

The upgrade control program displays the correct name of the correction

package you have to apply.

The SAR archives are available at the following SAP Service Marketplace

area:

http://service.sap.com/patches -> Entry by Application Group ->

Additional Components -> Upgrade Tools -> Corrections for Upgrade ->

CORRECTIONS FOR UPGRADE 7.02 -> #OS independent

There are two packages, one for ABAP and one for Java:

ABAP Package Name: FIX_NW702.UPG

Java Package Name: FIX_J_BS7I2010.UPG

© SAP AG ADM326 14-44

Comments:

o Caution: All products (SAP NetWeaver 7.0 EHP2 and all products

based on it) use the same correction package.

o The archive names on SAP Service Marketplace have a slightly

different naming convention:

The prefix "FIX_" ist not displayed. In addition, they have an

extension representing the patchlevel and <number> - an 8 digit

number. Thes extension varies with each patchlevel of the

archive.

o Some products are known under different names and can be used

differently. For example, NW-AS 7.00 which is part of Netweaver

04s is the successor product to WEB-AS as well as to the BW

product family. However, there is only one correction package

regardless of the use of the system.

Integration into the upgrade

4. Download the correction package for your product.

5. Store the SAR archive in the main upgrade directory.

6. Unpack the SAR archive using "SAPCAR -xvf <name>.SAR" You will get

two files, one of them is <Correction package name>.UPG, the other

one contains a history of changes.

7. During the KEY_CHK phase, the upgrade program searches the upgrade

directory for the correct correction package. If it is successful,

the package is automatically integrated into the upgrade. If the

upgrade program does not find a valid package, it displays a user

dialog requesting that you place the correction package in the

upgrade directory. You can use "Retry" to repeat the search.

The UPG archive contains data files and cofiles for the transport

requests and the corresponding buffer files (ABAP upgrade only), and

control files of the upgrade.

The corrections to the ABAP tools of the source release are imported in

the TOOLIMP4_FIX, TOOLIMP6_FIX phases (provided these exist), while the

© SAP AG ADM326 14-45

corrections for the shadow system are imported in the SHD_FIX_IMP phase.

The transport requests are imported automatically.

You must not import requests into the system manually!

The corrections to the J2EE upgrade program and control files are

included automatically and the program is restarted to make the changes

become active.

________________________________________________________________

________________________________________________________________

© SAP AG ADM326 14-46

Part D: General Problems / Information on all Upgrades

I/ Upgrade keyword

----------------------------------------------------------------------

For the upgrade keyword, see the relevant product-specific Note listed

in part A of this Note.

----------------------------------------------------------------------

II/ Important General Information

-----------------------< D034302 DEZ/03/03 >--------------------

Windows only: Execute program R3dllins.exe

The 6.40 kernel is compiled with the new version of MS compiler and

requires additional libraries for operation. To prevent problems during

and after the upgrade, you must execute program R3dllins.exe on your

central host, all application hosts, and on the remote shadow host, if

you are planning to use one.

You can find the program on the Upgrade Master CD in the

NT\I386\NTPATCHfolder. It must be executed before you start the upgrade

program and directly from the NTPATCH folder (it can be shared). Copying

and executing the program will not work!

------------------------< D042621 FEB/02/05 >-------------------------

LSMW now part of SAP_BASIS

As of SAP Web AS 6.20, LSMW is part of SAP_BASIS. If you are using LSMW

and your source release is based on SAP Web AS 6.10 or lower, do not

implement LSMW after the upgrade.


© SAP AG ADM326 14-47

-----------------------< D020904 MAR/15/07 >--------------------------

MSCS Configuration: Split the ABAP Central Instance

In an MSCS configuration, you must split the ABAP central instance into

the ABAP central instance (ASCS) and central instance, as described in

SAP Note 1011190, if one of the following cases apply:

o You have upgraded your SAP NetWeaver '04 ABAP only system to SAP

NetWeaver 7.0 ABAP

o You have upgraded your SAP NetWeaver '04 ABAP only system to SAP

NetWeaver 7.0 ABAP, and now want to install a Java Add-In. The

split must done before the Java Add-In installation.

The split is required for the use of the enqueue replication server. If

you run an MSCS configuration without enqueue replication server, which

is the traditional MSCS configuration (where the clustered central

instance runs the message server and enqueue work process), you will

loose the enqueue lock table during a failover. The enqueue replication

server configuration prevents this loss.

If you want to migrate an ABAP+Java system that is already upgraded to

SAP NetWeaver 7.0 to the new configuration with enqueue replication

server you must perform a homogeneous system copy.

---------------------------------------------------------------------

III/ Corrections to the Guides

-------------------------< D038245 APR/14/10 >--------------------------

Manual Start of ASCS and ERS Instance (Phase REQ_ASCS_START)

When you update the SAP kernel on the host with the ASCS instance, also

run program 'cleanipc'. For more information about this program, see SAP

Note 1195961.

------------------------< updated D050889 JAN/11/11 >------------------

------------------------< C5078662 MAY/11/10 >-------------------------

Starting the Upgrade Program

It is no longer required to specify the jce_policy_zip option when

starting the upgrade program.

---------------------------------------------------------------------

IV/ ..... Errors on the CD-ROM

---------------------------------------------------------------------

© SAP AG ADM326 14-48

V/ Preparing the Upgrade

------------------------< D022989 JUN/11/10 >-------------------------

Avoing Error with the "DB_STORAGE_GET" Module>

When you include SAP NetWeaver 7.0 EHP2 Support Package 4 into the

upgrade, than implement SAP Note 1470501 afterwards to avoid an error

with the "DB_STORAGE_GET" module.

----------------------- < D001330 04/FEB/10 > --------------------------

For Source Releases SAP R/3 4.6C and SAP R/3 4.6D Only: Prevent Lossof

your BSVV objects during the upgrade

If are upgrading your SAP system with the source SAP R/3 4.6C or SAP R/3

4.6D and have created customer-defined objects such as R3TR BSVV Z*

before the upgrade, you might lose parts of your BSVV objects during the

upgrade.

To solve this issue, proceed as described in SAP Note 1432102 prior to

starting the upgrade.

----------------------<changed D001658 10/JUL/07 >-------------------

------------------------< D001330 03/JUL/07 >------------------------

Parameter for the Central Syslog rslg/collect*

There may be conflicts with parameter values for the central syslog

"rslg/collect*" of the default profile.

If the parameters are set with 39<no.> and 40 <no.>, you must change

them to 14<no.> and 15<no.>. Make sure that the ports are not used by

other applications. If so, choose some other number.

For more information, see Note 1069225.

-----------------------< D038006 02/NOV/05 >--------------------------

Source Release on Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64

If you are using the above combination on your source release and have

set environment variable LD_ASSUME_KERNEL 2.4.21 according to SAP Note

797084, proceed as follows:

Before you start the upgrade, you need to delete the environment

variable LD_ASSUME_KERNEL 2.4.21 and deactivate component icman by

setting the following instance profile entry:

rdisp/start_icman=false

Restart the system. After the upgrade, delete the instance profile entry

again.

© SAP AG ADM326 14-49

--------------------------< D003327 15/SEP/05 >------------------------

Back up customer-specific entries in table EDIFCT

If you have maintained customer-specific entries in table EDIFCT, they

may get lost during the upgrade. If you do not want to lose these

entries, export them before the upgrade and reimport them after the

upgrade.


© SAP AG ADM326 14-50

--------------------------< D034302 16/AUG/05 >-----------------------

Windows only: Last profile text line must end with line feedback

Check that the last text line in all profiles ends with a line

feedback.To check this, open a profile file with a text editor, go down

with the cursor and ensure that the last line is empty. Otherwise there

could be problems in the KX_SWITCH phase as some tools will not be able

to handlethe profiles properly.

--------------------------< D034302 07/JUN/05 >-----------------------

Windows only: Stop SAP MMC during the upgrade downtime

Make sure that SAP MMC is not running during the upgrade downtime.

Otherwise, the files in the kernel directory will be in use and the

phase KX_SWITCH is not executed successfully.

--------------------------< D034302 07/JUN/05 >-----------------------

Windows only: Comment out parameter DIR_SERVER_ORAHOME

Check the default profile of your system. If you find the parameter

DIR_SERVER_ORAHOME, comment it out. Otherwise the phase KX_SWITCH is not

executed successfully.

-----------------------------------------------------------------------

VI/ Problems During the Upgrade Phases

---------------------<D037517 25/NOV/10 >------------------------------

SPS06 included in Upgrade: Error in Preprocessing / Phase

RUN_RSDB02CK_END

If you include Support Package SAP_ABA 702 06 into the upgrade, the

following error can occur:

Checks after phase MAIN_POSTP/RUN_RSDB02CK_END were negative! Last error

code set: Batch Job RSDB02CK Failed: Error(s) were found in the log(s),

accumulated in "RSDB02CK.ELG".

In the log file, the following error message exists:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

DB02 consistency check ERRORS and RETURN CODE in RSDB02EN.QO1

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2EETG033 Table "TASYB" does not exist in the database

You can ignore this error.

© SAP AG ADM326 14-52

------------------------< D053561 02/JUN/10 >-----------------------

Phase IS_SELECT

An error in the IS_SELECT phase can erroneously lead to the deletion of

the add-on. In the following situation, the error can occur:

The add-on has the status 'KEEP'. When you choose 'Continue' a message

informs you that 'KEEP' is not valid and the status is set to

'UNDECIDED'. You select another option, for example, 'Keep with vendor

key'. When you then choose 'Back' and run the Configuration roadmap

stepa second time, you no longer get the message that 'KEEP' is not

possible and you cannot choose another option. Although the status of

the add-on is then still 'KEEP', the add-on will be deleted.

To solve the problem, reset the upgrade completely by choosing 'Back'

several times. Then, start the upgrade from scratch.

------------------------<D034302 01/JUN/10 >---------------------------

Phase PARCONV_UPG

During the upgrade, the phase PARCONV_UPG can fail with an error during

the creation of secondary indexes. In the conversion log files of the

form NCONV..<SID> the following error is reported:

Index " " could not be created completely in the database

To solve this problem, repeat the phase. To avoid the error in advance

include the support packages mentioned in SAP Note 1468467 in the

upgrade procedure.

----------------------< D030559 27/APR/10 > ----------------------------

Phase: MAIN_NEWBAS/RUN_RSAIMMERGE_UPG

To avoid a runtime error in your target system, increase parameter

"em/initial_size_MB = 1024" to "em/initial_size_MB = 4096" in the

instance profile.


----------------------< D038245 19/APR/10 > ----------------------------

Phase: MODPROF_PFPAR_UPG

If the following error occurs: "MODPROF_PFPAR_UPG:fails even rc=0", add

the following paramenter to the instance profile: "SAPup_check_level =

5".

----------------------< D037517 17/FEB/10 > ----------------------------

Phase: MAIN_SHADOW/START_SHDI_FIRST

Description: An RFC error occurs (RFC LOGIN FAILED)

Solution:

© SAP AG ADM326 14-53

8. In the SAPup.par file, set the value of the

/UNIX/sleep_after_shdsys_start parameter to 200.

9. Restart the upgrade program and repeat the phase.

© SAP AG ADM326 14-54

----------------------< C5050355 JAN/22/10 >--------------------------

Adjust Hostnames in Shadow Instance Profiles Manually

When you have chosen option "Take profiles from save" to reuse the

profiles for the shadow instance of your previous upgrade, update the

hostnames in the profiles for the shadow instance manually after the

"Configuration" roadmap step. You can find these profiles under

<DIR_PUT>/abap/<SID>/SYS/profiles. This workaround will be fixed for

tools delivered with BS7i2010.

------------------------< D025988 JUN/16/00 >-------------------

Phase: PARDIST_SHD

Description: For Windows NT only

The upgrade is terminated during the PARDIST_SHD phase. The PCONUPG.ELG

log file contains an incomplete error text which was extracted from the

DS<date>. <SID> log file. Repeat the phase.

-------------------------- < D034302 07/OCT/05 >-----------------------

Phase: REQJOBRES

Description: Windows only - SAPup issues the error message

value returned by call sappfpar.exe Start_Program_01 pf=...is incorrect.

Please analyze the content of ...\put\log\NTPARVAL.LOG

You can ignore this error. Repeat the phase to continue.

--------------------------< D034302 16/AUG/05 >-----------------------

Phase: KX_SWITCH (Windows only) Description: Upgrade stops with an error

message which asks you to checkfile NTPARVAL.LOG. In this file, messages

like the following are displayed:

fopen(...): Invalid argument


feedback.To check the profile, open a profile file with a text editor,

go down with the cursor, and ensure that the last line is empty. If it

is not, add an empty line at the end of the file and save it.

--------------------------< D034302 07/JUN/05 >-----------------------

Phase: KX_SWITCH (Windows only)

Description: Because SAP MMC is running, SAPup stopped with the

following error message:

SAPup> SEVERE ERROR: Could not delete file '...\sapstartsrv.exe' ...

Reason: 'ErrorMessage: Access is denied.

In this case, shutdown SAPMMC and SAP service of your system and repeat

the phase.

© SAP AG ADM326 14-55

--------------------------< D034302 07/JUN/05 >-----------------------


Description: If parameter DIR_SERVER_ORAHOME has not been commented out

,SAP up will stop with the following error message:

Error: value returned by call sappfpar.exe Start_Program_01 pf=...is

incorrect. Please analyze the content of ...NTPARVAL.LOG.

The NTPARVAL.LOG states:

immediate ...\sapcpe.exe pf=...Illegal Parameter in Default Profile:

"DIR_CLIENT_ORAHOME". sapparam: Illegal Parameter in Default Profile:

"DIR_SERVER_ORAHOME". (no Default-Value)

In this case, comment the parameter out and repeat the phase.

--------------------------< D021063 OCT/12/06 >----------------------

Phase: XPRAS_UPG

Description: The phase issues the following short dump:

"GEN_BAD_MACRO_SOURCE" for program /1BCDWB/<XXXXXXXXXXXXXXXXXX>

You can ignore this message.

----------------------< D038245 FEB/28/06 >--------------------------

Phase: MODPROFP_UPG

Description: When you are performing a dual-stack upgrade (ABAP and Java

system at the same time), in phase MODPROFP_UPG the ABAP system is

started together with the Java system part for the first time. The phase

may fail if the SAP J2EE Engine does not start fast enough.

Check manually if the SAP J2EE Engine is running and if so, choose

"repeat" to repeat the upgrade phase.

----------------------------------------------------------------------

Phase: CHK_POSTUP

Note: 996953

Description: Log file LONGPOST.LOG prompts you to migrate a CMOD project

although no project exists.

----------------------------------------------------------------------

VII/ Problems After the Upgrade

--------------------< D020815 DEC/23/10 >------------------------------

Reconfiguration of User Reauthentication

If you have performed the upgrade from a source release lower than SAP

NetWeaver 7.0 EHP1, you have to reconfigure the user reauthentication

© SAP AG ADM326 14-56

after the ugprade.

As of SAP NetWeaver 7.0 EHP1, there is a new implementation of the user

reauthentication and it is not active until you have configured it.For

more information, see SAP Note 1532874.

© SAP AG ADM326 14-57

----------------------< D027133 30/NOV/10 >-----------------------------

Missing Table

If you included SAP_ABA 702 SP 06 into the upgrade, the you see the

following in transaction DB02 under 'Missing Tables and Indexes':

Results of Consistency Check

Object missing in the database

Tables

X TASYB

You can either ignore this issue or create the table in the database in

transaction DB02.

If you included a lower or higher Support Package into the upgrade,

thisissue does not occur.

----------------------< D034302 09/JUL/10 >--------------------------

Ignore Short Dump

If the following short dump occured during the enhancement package

installation, you can ignore it:

Category ABAP Programming Error

Runtime Errors CALL_FUNCTION_NOT_FOUND

Except. CX_SY_DYN_CALL_ILLEGAL_FUNC

ABAP Program CL_ENH_TOOL_BADI_IMPL=========CP

Application Component BC-DWB-CEX

Date and Time 12.05.2010 08:59:40

----------------------< D001330 15/JUL/10 >----------------------------

Delete CUA Load after the Upgrade

If after the upgrade you face an issue with the CUA load in your SAP

system, delete the CUA load using report "RSLANG20" as described in SAP

Note 110910.

----------------------<enhanced C5068728 25/MAY/10 >------------------

------------------------< I043868 12/APR/10 >------------------------

Ignore obsolete tables "PATRTVERS2","PATRTCONF", and "PATRTPHASE"

If you run into the table "PATRTVERS2", "PATRTCONF", "PATRTPHASE"

(SPAM-specific), or table "sap_tmp_stmt_stats_tab" (MS SQL

server-specific) after the upgrade, ignore these tables. They have

become obsolete and will be deleted automatically!

------------------------< I043868 12/APR/10 >---------------------------

Windows Only: Ignore obsolete table "sap_tmp_stmt_stats_tab"

If you run into the table "sap_tmp_stmt_stats_tab" (MS SQL

© SAP AG ADM326 14-58

server-specific) after the upgrade, ignore this table. It has become

obsolete and will be deleted automatically.

© SAP AG ADM326 14-59

--------------------------< I803368 21/JUL/09 >-------------------------

Syntax error in TREX ABAP Client after the upgrade

If you perform an upgrade from SAP NetWeaver 7.00 SP17 or higher to

SAP NetWeaver 7.0 including enhancement package 1 SP2 / SP3 / SP4 or

to SAP NetWeaver 7.0 including enhancement package 2 SP1,

you will get a syntax error in class your TREX ABAP client

(CL_TREX_FACADE). To solve this issue, check SAP Note 1355746.

--------------------<enhanced D038245/JUNE/05 >----------------------

-----------------------< D003551 02/MAY/05---------------------------

Check Primary Index of Table MEMGMT_DEPLOYMNT

After the upgrade, check that the primary index of table

MEMGMT_DEPLOYMNT exists. If not, create the index manually.

If you still get the message that MEMGMT_DEPLOYMNT00 is an unknown

object in the dictionary, drop it on the database level.

------------------------< D020815 AUG/23/02 >------------------------

SPAU: Names of interface methods are truncated

Some methods (ABAP objects) that were modified and overwritten by the

upgrade can be displayed in transaction SPAU with their names shortened

to 30 characters.

As a result, the system may also incorrectly sort methods in SPAU under

"Deleted objects".

Caution: Deleted objects are not displayed in the standard selection in

SPAU. It is easily possible to overlook these!

For more information about the correction, see Note 547773.

----------------------------------------------------------------------

© SAP AG ADM326 14-60

Date.....Topic..Short description

-----------------------------------------------------------------------

DEC/23/10..VII..Reconfiguration of User Reauthentication

NOV/30/10..VII..Missing Table

JUL/27/10..VII..Ignore Short Dump

JUL/15/10..VII. Delete CUA Load after the Upgrade<

JUN/11/10..V....Avoiding Error with the "DB_STORAGE_GET" Module

JUN/07/10..V....Preventing long runtime of SUSR_AFTER_IMP_PROFILE

JUN/02/10..VI...Phase IS_SELECT

JUN/01/10..VI...Phase PARCONV_UPG

MAY/11/10..III..Starting the Upgrade Program

APR/28/10...V...Avoiding Loss of Customer Objects During the Upgrade

MAR/10/10...V...Preventing Unrequired Table Conversion

APR/19/10...VI..MODPROF_PFPAR_UPG: Add parameter to the instance profile

APR/14/10..III..Manual Start of ASCS and ERS Instance: cleanipc

APR/12/10...VII.Ignore tables "PATRTVERS2","PATRTCONF", and "PATRTPHASE

APR/12/10...VII.Windows Only:Ignore obsolete table "sap_tmp_stmt_..."

FEB/17/10...VI..Phase MAIN_SHADOW/START_SHDI_FIRST

FEB/04/10...V...Prevent Loss of your BSVV Objects During the Upgrade

JUL/21/09...VII.Syntax error in TREX ABAP Client after the upgrade

JUL/03/07....V..Parameter for the Central Syslog rslg/collect*

MAR/15/07...II..MSCS Configuration

FEB/28/07...VI..Applying Support Packages on the Source Release

FEB/28/07...VI..Phase CHK_POSTUP - CMOD/SMOD migration

OCT/12/06...VI..Phase XPRAS_UPG: short dump GEN_BAD_MACRO_SOURCE

FEB/28/06...VI..Phase MODPROFP_UPG fails - check J2EE Engine

NOV/02/05....V..Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64

OCT/07/05...VI..Phase: REQJOBRES

AUG/16/05...VI..Windows only: KX_SWITCH - Check file NTPARVAL.LOG.

AUG/16/05....V..Windows only: Last profile text line - line feedback

JUN/07/05....V..Windows only: Stop SAP MMC during the upgrade downtime

JUN/07/05....V..Windows only: Comment out parameter DIR_SERVER_ORAHOME

JUN/07/05...VI..Windows only: KX_SWITCH - SAP MMC is running

JUN/07/05...VI..Windows only: KX_SWITCH - parameter DIR_SERVER_ORAHOME

MAY/02/05..VII..Check Primary Index of Table MEMGMT_DEPLOYMNT

FEB/02/05...II..LSMW now part of SAP_BASIS

DEZ/03/03...II..Windows only: Execute program R3dllins.exe

SEP/17/03....I..SAPup keyword

AUG/23/02..VII..SPAU: Names of interface methods are truncated

JUL/19/02...II..Problems with the shadow instance

MAY/24/02...II..Corrections and repairs for the upgrade

________________________________________________________________________

© SAP AG ADM326 14-61

Valid releases


from to

SAP_BASIS

SAP Basis component

701 - 702

________________________________________________________________________


Number Short text

____________________________________________________________

1355746 Syntax error in class cl_trex_test_facade

1341981 Add. info. on upgrading to SAP SCM 7.0 including EHP1 ABAP

1341978 Add. info. on upgrading to SAP CRM 7.0 including EHP1 ABAP

1341975 Add. info. on upgrading to SAP ERP 6.0 including EHP5 ABAP

1338386 Upgrade to SAP NetWeaver 7.0 EHP2 ABAP (IBM DB2 for i)

1293387 Add. Info. on Upgrading to SAP SRM Server 7.0 SR1 ABAP

________________________________________________________________________

© SAP AG ADM326 14-62

SAP Note No. 1341975 ________________________________________________________________________

Number 1341975



Set on 15.12.2010

Language EN

Master language EN

Short text Add. info. on upgrading to SAP ERP 6.0 including

EHP5 ABAP

Responsible SAP



________________________________________________________________________

Long text

Symptom

Errors in the upgrade procedure or in the upgrade guide; preparations

for the upgrade; additional information to the upgrade guide

Other terms

Update, migration, upgrade, release upgrade, SAPup, SAP ERP Central

Component 6.0,


*

Solution

CAUTION:

This note is updated regularly!

Therefore, you should read it again immediately before starting the

upgrade.

What information can I expect from this note?

This note describes problems that may occur during the system upgrade

and provides information on how to solve them. This usually takes the

form of references to other notes.

The main purpose of this note is to prevent data loss, upgrade

shutdowns, and long runtimes.

© SAP AG ADM326 14-63

It deals with database-independent problems only.

Which additional notes do I require in preparation for the upgrade?

You need to refer to the relevant database-specific note below:

Database .................................................. Note number

© SAP AG ADM326 14-64

_______________________________________________________________________

SAP MaxDB .......................................................817463

IBM DB2 for i (NetWeaver-specific)..............................1168235

IBM DB2 for i (Business Suite-specific).........................1179413

IBM DB2 for Linux, UNIX and Windows .............................819876

IBM DB2 for z/OS.................................................815202

MS SQL Server....................................................825146

Oracle...........................................................819655

You also need to refer to the following important SAP Notes:

Short text ................................................ Note number

_______________________________________________________________________

Central Note: Upgrade to Systems on SAP NetWeaver 7.0 EHP2......1299009

OCS: Known problems with Support Packages in SAP NW 7.0 AS ABAP..822379

Contents

I/ ...... SAPup Keyword

II/ ..... Important General Information

III/ .... Corrections to the Guide

IV/ ..... Errors on the CD-ROM

V/ ...... Preparing the Upgrade

VI/...... Problems During the PREPARE and Upgrade Phases

VII/ .... Problems After the Upgrade

VIII/ ... Chronological Summary

I/ SAPup keyword

----------------------------------------------------------------------

The SAPup keyword is: 20077540

This must be entered in phase KEY_CHK.

----------------------------------------------------------------------

© SAP AG ADM326 14-65

II/ Important General Information

-----------------------< D025323 NOV/21/08 >--------------------------

Corrections and Repairs for the Upgrade

Before the upgrade, it is vital that you check whether the following is

available for your specific upgrade:

o A new version of SAPup.

o Repairs to the ABAP upgrade programs.


It is ESSENTIAL that you apply this Note.

-----------------------< D034302 DEC/03/03 >--------------------------

Windows only: Execute program R3dllins.exe

The 6.40 kernel is compiled with the new version of MS compiler and

requires additional libraries for operation. To prevent problems during

and after the upgrade, you must execute program R3dllins.exe on your

central host, all application hosts, and on the remote shadow host, if

you are planning to use one.

You can find the program on the Upgrade Master CD in the NT\I386\NTPATCH

folder. It must be executed before you start PREPARE and directly from

the NTPATCH folder (it can be shared). Copying and executing the program

will not work.

-----------------------< D028310 JUL/19/02 >--------------------------

Problems with the Shadow Instance.

The following Notes contain information about problems with the shadow

instance:

o 525677: Problems when starting the shadow instance

o 430318: Remote shadow instance on a different operating system

------------------------< D042621 FEB/02/05 >-------------------------

LSWM now part of SAP_BASIS

As of SAP Web AS 6.20, LSMW is part of SAP_BASIS. If you are using LSMW

and your source release is based on SAP Web AS 6.10 or lower, do not

implement LSMW after the upgrade.


© SAP AG ADM326 14-66

-----------------------< D020904 MAR/15/07 >---------------------------

MSCS: Upgrade of the ABAP system only, or Upgrade of the ABAP system

with subsequent Java Add-In installation:

In an MSCS configuration, you must split the ABAP central instance into

the ABAP central instance (ASCS) and central instance, as described in

SAP Note 1011190, if one of the following cases apply:

o You have upgraded your SAP NetWeaver '04-based ABAP system to SAP

NetWeaver 7.0-based ABAP system

o You have upgraded your SAP NetWeaver '04-based ABAP system to SAP

NetWeaver 7.0-based ABAP system, and now want to install a Java

Add-In. The split must done before the Java Add-In installation.

The split is required for the use of the enqueue replication server. If

you run an MSCS configuration without enqueue replication server, which

is the traditional MSCS configuration (where the clustered central

instance runs the message server and enqueue work process), you will

loose the enqueue lock table during a failover. The enqueue replication

server configuration prevents this loss.

If you want to migrate an ABAP+Java system that is already upgraded to

SAP NetWeaver 7.0 to the new configuration with enqueue replication

server, you must perform a homogeneous system copy.

---------------------------------------------------------------------

III/ Corrections to the Guides

---------------------------------------------------------------------

IV/ Errors on the CD-ROM

---------------------------------------------------------------------

© SAP AG ADM326 14-67

V/ Preparing the Upgrade

------------------------< D047992 23/APR/09 >------------------------

Check if Matchcodes Exist in Your System

Before starting the upgrade, check if old help views or matchcodes

existin your SAP system. If so, this can lead to an upgrade failure with

a subsequent system restore.

Use report TWTOOL01 as described in SAP Note 1330256 to check if

matchcodes exist in your system.

If you are running a combined upgrade and Unicode conversion, it is

mandatory that you delete or migrate matchcode objects to Search Helps

before you start SAPup.

For more information about Search Helps that have replaced the

matchcodes, see the online documentation for the ABAP Dictionary.

------------------------< D035496 31/MAR/09 >------------------------

Selecting the Target SP Stack Level in Maintenance Optimizer

When selecting an enhancement package release and a target SP Stack

level for the stack XML generation in Maintenance Optimizer, it is

mandatory to select Support Package Stack 02 or higher. If you select a

lower SP Stack level, you will get an error message in phase

EHP_INCLUSION.

------------------------< D038245 09/DEC/08 >------------------------

Downloading Kernel DVDs for the Upgrade

The software of the kernel is split into two files with the following

naming convention:

<product><version>

<product><version>Upgrade

When you download the kernel DVDs for the upgrade, you must download

both files from SAP Service Marketplace.

------------------------< D044675 17/JAN/08 >--------------------------

Upgrade from Source Release 4.6C: Including a minimum SP level

If your source release system includes SAP_HR 46C Support Package level

D1, data loss may occur during the upgrade. To prevent any data loss,

include at least Support Package 26 of the target release into the

upgrade, although the upgrade program does not request it.

Alternatively, update your system to SAP_HR 46C Support Package level D2

before the upgrade.

----------------------<changed D001658 10/JUL/07 >---------------------

© SAP AG ADM326 14-68

------------------------< D001330 03/JUL/07 >--------------------------

Parameter for the Central Syslog rslg/collect*

There may be conflicts with parameter values for the central syslog

"rslg/collect*" of the default profile.

If the parameters are set with 39<no.> and 40<no.>, you must change them

to 14<no.> and 15<no.>. Make sure that the ports are not used by other

applications. If so, choose some other number.


© SAP AG ADM326 14-69

-------------------< D003327 05/FEB/07 >-------------------------------

Back up customer-specific entries in table EDIFCT

If you have maintained customer-specific entries in table EDIFCT, they

may get lost during the upgrade. If you do not want to lose these

entries, export them before the upgrade and reimport them after the

upgrade.


------------------------< D044675 18/DEC/06 >------------------------

New SPAM/SAINT Version on Source Release

Before you include Support Package SAPKH60007 in the upgrade, you must

apply at least the following SPAM/SAINT versions on your source release:

o Source Rel. SAP R/3 4.x: SPAM/SAINT version 0045

o Source Rel. SAP R/3 Enterprise, SAP ECC. 5.0: SPAM/SAINT version

0022

If you use an older version, you will receive conflict messages for

SAP_APPL SP 07 with ECC-DIMP, object list SAPKGES01G, during PREPARE. In

this case, you can repeat the phase after applying the SPAM/SAINT

update.

-----------------------< D028310 28/AUG/06 >--------------------------

Update SAP Kernel on Source Release

If you want to convert logical cluster tables incrementally using

transaction ICNV during the upgrade, you must make sure that the level

of the SAP kernel on the source release is high enough.


-----------------------< D022188 24/APR/06 >--------------------------

Prepare table COEP for the upgrade

If your source release is SAP R/3 4.6C or below and table COEP contains

many data, the conversion of this table during the upgrade can lead to

aprolonged downtime.

For more information about reducing downtime, see Note 937389.

-----------------------< D038006 02/NOV/05 >--------------------------

Source Release on Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64

If you are using the above combination on your source release and have

set environment variable LD_ASSUME_KERNEL 2.4.21 according to SAP Note

797084, proceed as follows:

Before you start the upgrade, you need to delete the environment

© SAP AG ADM326 14-70

variable LD_ASSUME_KERNEL 2.4.21 and deactivate component icman by

setting the following instance profile entry:

rdisp/start_icman=false

Restart the system.

After the upgrade, delete the instance profile entry again.

© SAP AG ADM326 14-71

--------------------------< D034302 16/AUG/05 >-----------------------

Windows only: Last profile text line must end with line feedback


feedback.To check this, open a profile file with a text editor, go down

with the cursor and ensure that the last line is empty. Otherwise there

could be problems in the KX_SWITCH phase as some tools will not be able

to handle the profiles properly.

------------------------< D031149 13/JUL/05 >-------------------------

Source Rel. ECC DIMP 5.0: MPN Conversion Exit

In release ECC DIMP 5.0 - up to and including CRT02 - the MPN conversion

exit is delivered as "active" by default. The conversion exit is set to

active, if the checkbox "Active conversion exit" in the following

customizing transaction is flagged: Logistics - General -->

Interchangeability of Parts --> Set Up Conversion Exit for Material

Numbers.

If the MPN conversion exit should not be used in the system, it is very

important that it is deactivated before the upgrade (in Source release

ECC DIMP 5.0).

For more information on how to proceed, see Note 854523.

The problem is solved with CRT03 of release ECC DIMP 5.0.

-----------------------< D031049 14/OCT/04 >--------------------------

Source Rel. 4.0B: Project-Related Incoming Orders

If you are using the preliminary solution for project-related incoming

orders published with Note 118780, you have to modify data elements

before the upgrade.


----------------------< D038245 09/SEP/04 >---------------------------

Source Release Extension Set 1.10: Exchange containers

If your system was installed with SAP R/3 Enterprise Ext. Set 1.10

(based on SAP Web AS 6.20) and you are using a database that uses

different containers for saving data (Oracle, Informix and DB2 UDB for

UNIX and Windows), refer to note 674070 before the upgrade.

Otherwise, the exchange containers (tablespaces/dbspaces) cannot be

emptied during the upgrade and cannot be deleted after the upgrade.

------------------------< D038245 19/APR/04 >------------------------

Unicode Systems: Downward Compatible Kernel 6.40

If you are using the normal kernel for Release 6.20 with your Unicode

system, PREPARE issues the error message:

Could not open the ICU common library.

© SAP AG ADM326 14-72

Before you start PREPARE, install the Downward Compatible Kernel for

Release 6.40. Until this kernel is available, proceed as described in

Note 716378.

© SAP AG ADM326 14-73

------------------------< D032986 22/SEP/05 >------------------------

Upgrading with reintegrated add-ons (retrofit)

For SAP ERP Core Component 6.0 (ECC 6.0), more add-ons were reintegrated

into the main ECC system or the Extension Sets.

The following Notes contain additional information on processing these

add-ons before, during and after the upgrade.

o Note 838002 Add-ons (non-IS) integrated in SAP ECC 600

o Note 838003 Industry Add-ons integrated in SAP ECC 600

--------------------------< D032986 27/JAN/04 >-----------------------

Upgrading with PI/PI-A

For information on how to upgrade your system with PI/PI-A plug-ins, see

Note 700779.

--------------------------< D025323 24/APR/03 >-----------------------

Upgrade on AIX: saposcol

Refer to Note 526694 before the upgrade.

--------------------------< D019926 DEC/10/02 >-----------------------

Upgrading with AIX 5.1

If you want to upgrade with AIX 5.1, see Note 502532 before starting the

upgrade.

-----------------------< D025323 FEB/20/02 >--------------------------

Source Releases on UNIX 32-bit or AIX 64-bit

In some cases, you may have to upgrade the operating system to 64-bit

before the actual upgrade.

When you upgrade from AIX 4.3 64-bit, you must perform some additional

actions before upgrading.

For more information, see Notes 496963 and 499708.

-----------------------------------------------------------------------

© SAP AG ADM326 14-74

VI/ Problems During the Preparation and Upgrade Phases

This section addresses known problems that cannot be avoided using

preventive measures. These problems will only occur under very specific

circumstances.

Problems During the Preparation Phases

------------------------< D035496 31/MAR/09 >------------------------

Error in the EHP_INCLUSION Phase

If you have selected a target SP stack level lower than SP stack 02 for

the stack XML generation in Maintenance Optimizer, you will get a

similar error message in phase EHP_INCLUSION:

EHP patch level 34 for component SAP_HR is too low, destination level is

already at 37.

Solution:

1. Select SP Stack 02 or higher as the target SPS level for enhancement

package 4 and rerun the package calculation in Maintenance

Optimizer.

2. Download the additional packages calculated by the Maintenance

Optimizer to your EPS inbox directory.

3. Repeat the failed phase with the newly generated stack XML file.

--------------------------< D038245 28/FEB/08 >-----------------------

Windows only: MSSERV_INTERN port numbers

During PREPARE, the upgrade tool requests a port number for the

MSSERV_INTERN port. If your system is running on Windows, you cannot use

port numbers within the following range: 6665 - 6669.

-----------------------< D038245 APR/11/02 >--------------------------

Termination in the TOOLIMPD3 phase

The TOOLIMPD3 phase terminates during the tool import. The following

message appears in the log file:

ABAP runtime error CALL_FUNCTION_NO_RECEIVER

Receiving data for unknown CPIC link XXXXXX.

Repeat the phase and continue with the upgrade.

-----------------------------------------------------------------------

Problems During the Upgrade Phases

© SAP AG ADM326 14-75

--------------------< D030182 05/AUG/10 > ------------------------------

Phase: JOB_RCIFSTKUREN2

Description: Oracle Only: After this phase, on DB platform Oracle you

may encounter an inconsistency with primary DB index of table

"CIFSTKUCOUNT".

Solution: Include the corresponding SP mentioned in SAP Note 1483213

into the upgrade.

If this SP is not yet released, and inconsistency with the DB index

exists, rename index with execution of funtion module DB_RENAME_INDEX

(transaction SE37, only on DB platform Oracle):

Parameters:

TABNAME: CIFSTKUCOUNT

INDNAME_NEW: CIFSTKUCOUNT~0

INDNAME_OLD: CIFSTKUCNT~0

To avoid errors with index information on Oracle systems, apply SAP Not

1483213.

------------------------< I043270 15/JUL/10 >--------------------------

LONGPOST.LOG

- The message: "A1PESEEF_BADI 103 BAdI implementation

FMFG_HELD_PO_NO_UPD must still be migrated" can be ignore

since the implementation is obsolete. See SAP Note 1246090.

- You can ignore the following messages:

'3PETG447 Table and runtime object "/SAPAPO/RESDIM" exist

without DDIC reference ("Transp. table")'

'3PETG447 Table and runtime object "/SAPAPO/RES_HEAD" exist


'3PETG447 Table and runtime object "/SAPAPO/RES_TXT" exist


The tables are deliberately kept on the database when you

upgrade (For more information, see Note 827490).

- Messages with the following pattern can also be ignored:

'4PEDH176 Parameter list of append search help "..." differs

from appending one'.

© SAP AG ADM326 14-76

------------------------< D021548 05/MAY/10 >--------------------------

Phase: MAIN_NEWBAS/XPRAS_AIMMRG

Description: Shortdump OBJECTS_OBJREF_NOT_ASSIGNED_NO

SAP Note: 1465173

------------------------< D026178 15/OCT/09 >--------------------------

Phase CHK_POSTUP

Description: P messages in LONGPOST.LOG file:

o 4PEDH176 Parameter list of append search help "ASH_FICO_TREX"

differs from appending one

o 4PEDH176 Parameter list of append search help "FICO_APPEND"

differs fro appending one

o 4PEDH176 Parameter list of append search help "FICO_SUBSTRINGS"


o 4PEDH176 Parameter list of append search help "ASH_GRANT_TREX"


o 4PEDH176 Parameter list of append search help "GRANTS_APPEND2"


Solution: You can ignore these P messages.

--------------------------< I027631 17/APR/09 >-----------------------

Phase: ACT_UPG

Note: 1321756

Description: During the ACT_UPG phase, you might get the following error

message:

1EEDO519X"Table" "USMDZ1FCRS" could not be activated

Proceed as described in Note 1321756.

--------------------------< D034302 16/AUG/05 >-----------------------


Description: Upgrade stops with an error message which asks you to check

file NTPARVAL.LOG. In this file, messages like the following are

displayed:

fopen(...): Invalid argument

Check that the last text line in all profiles ends with a line feedback.

To check the profile, open a profile file with a text editor, go down

with the cursor, and ensure that the last line is empty. If it is not,

add an empty line at the end of the file and save it.

---------------------<changed D003551 OCT/04/05 >---------------------

© SAP AG ADM326 14-77

--------------------------< D021867 AUG/10/04 >-----------------------

Phase: JOB_RDDNTPUR

Description: In the longpost-log file, you may get the error message:

3PETG447 Table and runtime object "TA22EQU_WAO" exist without DDIC

reference.

or

3PETG447 Table and runtime object "TVERTREE" exist without DDIC

reference

You can ignore this message.

--------------------------< I002675 OCT/07/05 >-----------------------

Phase: SHADOW_IMPORT_INC

Note: 884809

Description: The upgrade fails in phase SHADOW_IMPORT_INC. Check if the

log files display error messages as stated in the above Note. If so,

proceed as described in the Note.

--------------------------< C5003135 MAY/03/09 >-----------------------

Phase: SHDUNINST_DB

Description: The upgrade fails with the following error message:

'Could not drop database shadow user <shadow DB user>'

The log file <upgrade directory>/abap/log/SHDUNINST.LOG contains the

error:

BR0152E Environment variable SAPDATA_HOME is not set

Solution:

4. Stop the SL Controller and SAPup.

5. Set the environment variable SAPDATA_HOME to the directory <upgrade

directory>/abap/tmp (by default /usr/sap/<SAPSID>/upg/abap/tmp) in a

local shell for user <sapsid>adm.

6. Start the SL Controller from this local shell by executing the

startup script from the upgrade directory.

7. Start the upgrade GUI and use the 'repeat' option for this phase.

© SAP AG ADM326 14-78

--------------------------< I027631 MAY/03/09 >-----------------------

Phase: XPRAS_UPG

Description: You may get the following error message in phase XPRAS_UPG:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in SAPR700XP3.O64

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1AETR012X Program terminated (job: "RDDEXECL", no.: "20563602")

Long text:

Cause

Program "<(><<)>(><<(><<)>)>(><(><<)>(><(>&<)><(><<)>)><(><<)>(>

<<(><<)>)>)>V#&", which was started in the background, was terminated

abnormally.

Solution: Download lib_dbsl_<patch level>.sar (patch level must be at

least 38) from SAP Service Marketplace and replace the library

dboraslib.dll, then repeat the phase.

-------------------------< D023536 14/MAR/08 >------------------------

Phase: XPRAS_UPG (sourse release < 4.6C only)

Description: In certain cases, the shortdump

SAPSQL_ARRAY_INSERT_DUPRECmay occur in program "SAPLSBAL_DB_INTERNAL".

If you encounter this error, repeat the phase. If the error persists,

proceed as described in SAP Note 196113.

----------------------------------------------------------------------

Phase: CHK_POSTUP

Note: 996953

Description: Log file LONGPOST.LOG asks you to migrate a CMOD project

although no project exists.

----------------------< D038245 FEB/28/06 >--------------------------

Phase: MODPROFP_UPG

Description: When you are performing a dual-stack upgrade, in phase

MODPROFP_UPG, the ABAP stack is started together with the Java stack for

the first time. The phase may fail if the SAP J2EE Engine does not start

fast enough.

Check manually if the SAP J2EE Engine is running and if so, choose

"repeat" to repeat the upgrade phase.

----------------------------------------------------------------------

© SAP AG ADM326 14-79

VII/ Problems After the Upgrade

This section addresses known problems that cannot be avoided using

preventive measures. These problems will only occur under specific

circumstances.

-----------------------< I036707 26/MAR/10 >--------------------------

Missing instance.box.number in the instance.properties

After the upgrade, you might receive an error message when you try to

display the system details in the SAP NetWeaver Administrator.

To solve this problem, apply SAP Note 927561.

--------------------<enhanced D038245/JUNE/05 >----------------------

-----------------------< D003551 02/MAY/05 >-------------------------

Check Primary Index of Table MEMGMT_DEPLOYMNT

After the upgrade, check that the primary index of table

MEMGMT_DEPLOYMNT exists. If not, create the index manually.

If you still get the message that MEMGMT_DEPLOYMNT00 is an unknown

object in the dictionary, drop it on the database level.

------------------------< D020815 AUG/23/02 >-------------------

SPAU: Names of interface methods are truncated

Some methods (ABAP objects) that were modified and overwritten by the

upgrade can be displayed in transaction SPAU with their names shortened

to 30 characters.

As a result, the system may also incorrectly sort methods in SPAU under

"Deleted objects".

Caution: Deleted objects are not displayed in the standard selection in

SPAU. It is easily possible to overlook these!

For more information about the correction, see Note 547773.

----------------------------------------------------------------------

Linux: Importing the new saposcol version


----------------------------------------------------------------------

ReliantUNIX: saposcol version 32-bit or 64-bit


----------------------------------------------------------------------

Solaris: saposcol version 32-bit or 64- bit

© SAP AG ADM326 14-81

VIII/ Chronological Summary

Date.....Topic..Short description

-----------------------------------------------------------------------

AUG/05/10...VI..Phase: JOB_RCIFSTKUREN2

JUL/15/10...VI..LONGPOST.LOG

MAY/05/10...VI..Phase: MAIN_NEWBAS/XPRAS_AIMMRG

MAR/26/10..VII..Missing instance.box.number in the instance.properties

OCT/15/09...VI..Phase CHK_POSTUP

MAY/03/09...VI..Phase: XPRAS_UPG

MAY/03/09...VI..Phase: SHDUNINST_DB

APR/23/09....V..Check if Matchcodes Exist in Your System

APR/17/09...VI..Phase: ACT_UPG

MAR/31/09...VI..Error in the EHP_INCLUSION Phase

MAR/31/09....V..Selecting the Target SPS Level in Maintenance Optimizer

DEC/09/08....V..Downloading Kernel DVDs for the Upgrade

NOV/21/08...II..Corrections and Repairs for the Upgrade

MAR/14/08...VI..Phase XPRAS_UPG - shortdump SAPSQL_ARRAY_INSERT_DUPREC

FEB/28/08...VI..Windows only: MSSERV_INTERN port numbers

FEB/25/08..VII..Error when Converting Print Parameters

JAN/17/08....V..Source Release SAP R/3 4.6C: Including a min. SP level

JUL/03/07....V..Parameter for the Central Syslog rslg/collect*

MAY/09/07....V..Preparations for FI-CA

MAR/15/07...II..MSCS Configuration

FEB/28/07...VI..Phase CHK_POSTUP - CMOD/SMOD migration

FEB/05/07....V..Back up customer-specific entries in table EDIFCT

DEC/18/06....V..New SPAM/SAINT Version on Source Release

AUG/28/06....V..Update SAP Kernel on Source Release

APR/24/06....V..Prepare table COEP for the upgrade

FEB/28/06...VI..Phase MODPROFP_UPG fails - check J2EE Engine

DEC/12/05....V..SD Texts: Check Text Customizing on Source Release

DEC/12/05..VII..Addition to the Release Notes

NOV/02/05....V..Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64

OCT/07/05...VI..Phase SHADOW_IMPORT_INC

SEP/22/05....V..Upgrading with reintegrated add-ons (retrofit)

SEP/21/05....V..Checking Application Log

AUG/16/05...VI..Windows only: KX_SWITCH - Check file NTPARVAL.LOG.

AUG/16/05....V..Windows only: Last profile text line - line feedback

JUL/13/05....V..Source Rel. ECC DIMP 5.0: MPN Conversion Exit

MAY/02/05..VII..Check Primary Index of Table MEMGMT_DEPLOYMNT

FEB/02/05...II..LSWM now part of SAP_BASIS

OCT/14/04....V..Source Rel. 4.0B: Project-Related Incoming Orders

© SAP AG ADM326 14-82

OCT/14/04....V..Component PS-ST-WBS: Prel. Inclusion of Field KIMSK

OCT/06/04....V..Source Release 4.6C: SMODILOG Entries

© SAP AG ADM326 14-83

SEP/09/04....V..Source Release Extension Set 1.10: Exchange containers

AUG/10/04...VI..Phase JOB_RDDNTPUR: TA22EQU_WAO without reference

APR/19/04....V..Unicode Systems: Downward Compatible Kernel 6.40

JAN/27/04....V..Upgrading with PI/PI-A

DEC/03/03...II..Windows only: Execute program R3dllins.exe

APR/24/03....V..Upgrade on AIX: saposcol

DEC/10/02....V..Upgrading with AIX 5.1

AUG/23/02..VII..SPAU: Names of interface methods are truncated

JUL/19/02...II..Problems with the shadow instance

MAY/23/02...VI..Phase CHK_POSTUP - objects without DDIC reference

APR/11/02...VI..Termination in the TOOLIMPD3 phase

FEB/20/02....V..Source releases on UNIX 32-bit or AIX 64-bit

OCT/19/00..VII..Linux: Importing the new saposcol version

FEB/16/00..VII..saposcol version 32-bit or 64-bit on Reliant UNIX

FEB/16/00..VII..saposcol version 32-bit or 64-bit on Solaris

----------------------------------------------------------------------

________________________________________________________________________

Valid releases


from to

SAP_APPL

SAP Application

600 - 605

SAP_BASIS

SAP Basis component

702 - 702

________________________________________________________________________


Number Short text

____________________________________________________________

1475582 Migration tool for Travel Management for CEE countries

1349967 Upgrade to Business Suite 7 Innovation 2010: IBM DB2 for i

1299009 Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2

________________________________________________________________________

ADM326 SAP ECC Upgrade - hservers.org

Documents

Transcript of ADM326 SAP ECC Upgrade - hservers.org