SAP System Upgrade Overview

1

SAP System Upgrade

2

Outlook

Overview

SAP Upgrade Techniques and Tools

3

© SAP AG 2007, SAP System Upgrade / SAP NetWeaver Product Management / 3

SAP Web Application Server 6.20

SAP Basis

SAP R/3up to 4.6C

SAP R/3 Enterprise

Application

SAP ERP 6.0

SAP NetWeaver™ 7.0

Com

posi

te A

pplic

atio

n Fr

amew

ork

APPLICATION PLATFORM (7.00)

Life Cycle M

gmt

Composite Applications

PEOPLE INTEGRATIONMulti Channel Access

Portal Collaboration

INFORMATION INTEGRATION

Master Data Mgmt

Bus. Intelligence Knowledge Mgmt

PROCESS INTEGRATIONBusinessProcess Mgmt

ABAP

DB and OS Abstraction

Strategic Enterprise Management

Self-ServicesInternet Sales… and more

Release Upgrade: From R/3 To Enterprise SOA

Industry Solutions

SwitchSwitch FrameworkFramework

Supplier Relationship Management

Enterprise Extensions Industry Extensions

Industry Sol.

SAP ECC Core (6.0)SAP R/3 Enterprise Core (4.70)

SAP Enterprise Extension Set

EhP 1 EhP 2

ITSJava

4


6.00

SAP ECC

Target

Upgrade to SAP ECC 6.0 from..

472471464402

SAP IS-M

47X20047X110

SAP R/3 ENTERPRISE

4.6C4.6B4.5B4.0B3.1I

SAP R/3

3.0B

SAP IS-EC

2.0SAP IS-CWM

471463461

SAP IS-U/FERC

4.6C4.6B4.5B4.1B

SAP JVA

4.624.614.52

SAP HR-PS

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

SAP EH&S

2.00

SAP LEARNING SOLUTION

4.6C

SAP PH-ELR

4.6C

SAP PLM ADDON

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.0B1.0B

SAP IS-MP

3.0B2.0B

SAP IS-AD

4.61

SAP IS-HT

5.0

SAP ECC DIMP

4.71

SAP DIMP4.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

472471464461

SAP IS-U/CCS

4.72

SAP WASTE AND RECYCLING

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)

5.0

SAP ECC

5

Outlook

Overview


6

ABAP UpgradeJava UpgradeDouble-Stack Upgrade

7


Upgrade at a Glance

What is going to be upgraded?

Repository objects providing new or extended functionalities, i.e. ABAP coding, DDIC, Dynpro etc.

But not application dataMaster dataCustomer dataThey will be migrated if necessary

Data volume of repository objects is much smaller than application data’s volume

8


System Switch Upgrade

DB: SIDDB: SID, sapr3 SID~, sapr3shdProduction

Kernel 46C

ABAP 46C

dbsl

Production Instance 4.6 <NR>

TABLE, 46C

Tool

s

View46C

View700

Shadow

Kernel 700

ABAP 700

dbsl

Shadow Instance 7.00 <NR~>

Tool

s

TABLE, 700

Aliases,...

TABLE~, 700

System Switch Upgrade exists since SAP NetWeaver Application Server ABAP 6.10:

A shadow system of the target release is installed.

DB objects and some required (used during the upgrade) technicaltransactions of the new release are imported to the DB with aliases (distinctive extension pattern, e.g. ~ at the end of the original table name).

The shadow system access the DB objects using their aliases, so that the shadow system always works on the new object version.

Modification adjustment and other necessary steps are performed in the shadow system while the original system is functional for business transactions.

Data conversion/migration using the Incremental Table Conversion (ICNV) method, see next slides.

9


System Switch Upgrade: Timing Diagram

Upt

ime

Dow

ntim

e

PREPARE Upgrade

Inst.

Shad

ow In

stan

ce

(on

targ

et re

leas

e)

NewRel.

Upgradepost

Imp.

Bac

kup

downtime-minimizeddowntime-minimized

Bac

kup

Act

ivat

ion

Dis

trib

utio

n

Supp

ort P

ack‘

sA

dd-O

ns

Mod

ifica

tion

Adj

ustm

ent

Impo

rt o

f Con

trol

Dat

a in

Cop

y Ta

bles

ICN

V

Impo

rt o

f Su

bstit

utio

n Se

tUpgrade

Production Downtime

With the System Switch Upgrade, the system is unavailable for production use only for a small percentage of the time.

10


Incremental Table Conversion (ICNV)

T1_old

View T1

Shadow Table

T1_new

Status fields

Migrating (uptime)

update X

X

insertX

X

XX

delete Completing Migration

(downtime)

T1_old T1_new

The ICNV technique can be used in combination with the System Switch Upgrade to minimize the downtime required for the migration of database tables with high volumes.

The vast majority of data can be migrated during uptime.

Only very few data records, which have been changed recently, must be migrated when the system has been stopped for production use.

11


Inclusion of Support Packages and Add-On Upgrades

Newer Support Packages of the start release can contain enhancements/corrections that are not included in the installation/upgrade DVDs

SP equivalences between lower releases and the target releases are defined and checked by the upgrade

Add-OnsVast majority of SAP Industry Solutions are integrated to ECC 6.00 (except for the Apparel and Footwear solution)Partner products

12


Units of the Upgrade

PREPARECan be performed any time prior to the actual upgradeCan take virtually as much time as neededCan be repeated as often as neededChecks requirements to be fulfilledPrepare for the upgrade: Determining software modules to be upgraded, extracting DVDs, including SPs and Add-Ons …Preparation for modification adjustmentsPreparation for ICNV…

UPGRADEActual upgrade (from the technical point of view)Partly during downtimeShould be scheduled with deliberation

13


Customer-Based Upgrade: Process

P31

CustomerUpgrade

C31

copycopy

ECC

SAPUpgrade

upgradeupgrade

CBUCBUReRe--packagepackage

P31 ECC

upgradeupgrade

testtestupgradeupgrade

P31

C31 ECC

copycopy

ProductionProduction

Support PackagesAdd-on Installation/Upgrade

Customer developmentModification adjustment

Support PackagesAdd-on Installation/Upgrade

Customer developmentModification adjustment

Customer-based upgrade built on top of the standard System Switch Upgrade technology, intended for customers who cannot tolerate a downtime longer than approximately 1 hour.

A more costly solution! Trade-off: high resource and skill demands vs. shorter downtime

The standard System Switch Upgrade is conducted with a system clone of the actual system to be upgraded.

When the upgrade of the cloned system is entirely completed, a system-individual DB export will be done.

This individual DB export is then used for the upgrade of the actual productive system. In this way, much of downtime caused by repository operations can be saved.

14


Customer-Based Upgrade: Summary

DDIC ACT PCON TABIM XPRA rest

Uptime

Imports afterUpgrade

cros

s-cl

ient

clie

nt-

spec

ific

Inclusion of additional packages

Add-on installations (SAINT)

Add-on upgrades (SAINT)

Support Packages

Add-on patches, CRT‘s

No modification adjustments

No transports after upgrade except forcustomizing

Reductions in application adjustment

Accurate timing on production upgrade

Upgrade to target release including customer defined number of Support Packages, modification adjustments, pre-generated loads, ...

Repackaging large number of post-upgrade transport requests and include them as single change request into shadow import phase of upgrade (uptime!)

Upgrade to target release including customer defined number of Support Packages, modification adjustments, pre-generated loads, ...

Repackaging large number of post-upgrade transport requests and include them as single change request into shadow import phase of upgrade (uptime!)

15


Generic Factors of Runtime and Downtime

Hardware (CPU performance) / operating system (32 vs. 64 bit)

Hard disk configuration (I/O throughput)

Backup and restore times of database

Number of modifications (SPDD)

Number of productive applications (# of used tables)

Number of clients

Scatter Plot Downtime vs. DB-Size

0

1020

30

40

5060

70

8090

100

0 100 200 300 400 500 600 700 800 900 1000

DB-Size/GB

Dow

ntim

e/h

Source: Analysis of RSUPGSUM reports

No direct impact of DB-Size on upgrade runtime/downtime !

As each system is highly individual regarding its configuration and application data, a forecast of runtime and downtime is only possible when analyzing results of a test upgrade with a representative set of data !

SAP‘s Downtime Assessment Service is recommended !

16


Recommendations for SAP R/3 Enterprise Upgrades

Functional upgrades should be preferred

SAP Going-Live Functional Upgrade Check should be requested

Distribution of new SAPGUI version should be started as soon as possible

“Downtime-minimized” method should be used

Returning of modifications to SAP standard should be one of the main targets

Some recommendations based on experiences from previous upgrade projects…

17


18


Deployment-Based Upgrade To SAP NetWeaver 7.0 Java

NW04Applications

Binaries

Profiles & scripts

J2EE Engine Components

NW 7.0Applications

Binaries

Profiles & scripts

J2EE Engine ComponentsSAPJup Configure

Adapt

Adapt

Migrate

Migrate

Deploy

Deploy

19


Features

Inclusion of latest Support Package Stack

Preservation of customer dataMigrates J2EE Engine configurationsPreserves application data and configurations

Support for modification adjustment

Affinity with ABAP upgrade: PREPARE and UPGRADE

20


Preparation

Preparation steps are performed during the system uptime

The PREPARE phases include following major tasks:Investigating the source systemPerforming various parameter and profile checksDetermining usages types to be upgradedExtracting upgrade DVDsIncluding Support PackagesIncluding custom development componentsCalculating the deployment lists and order

21


Upgrade

The UPGRADE phases mainly run during the downtime.

It includes following major steps:Stopping the systemDisabling the current user store of the UME to ensure that SAP* is the only user who can access the system during the downtimeUpdating the kernel, SAP MMC (Windows only), IGS and SDMUndeploying and deploying SLOT1 (file system deployment)Undeploying and deploying SLOT2 (database deployment)Updating the engine bootstrap and adapting profilesUndeploying and deploying SLOT3 (offline deployment)Migrating engine core data (Java Migration Toolkit)Starting the system in Safe modeUndeploying and deploying SLOT4 (online deployment)Running application migration (application migration container)Stopping the systemRe-enabling the original user store of the UMEStarting the system

SAP* is the only active user during the upgrade

SAP* is only active during the upgrade

22


23


Synchronized Upgrade of ABAP 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

Upgrade of ABAP and Java stack (PREPARE and UPGRADE) must be performed in parallel with following sync points:

At the beginning of the downtimeWhen the profiles are going to be modifiedAt the end of the downtime

Except for the sync points, the upgrade processes of both stacksare performed independently

24


Java Add-in Installation

Java-based systems mostly required by functional upgrades from R/3

Java engine can be hosted in the same SAP System along with an ABAP engine

The installation option Java Add-in Installation supports the installation of an Java engine to an existing ABAP engine (here:upgraded from R/3)

Add-in or standalone? Depends on many factors:Functionalities to be implementedLicenseMaintenance…

25

Outlook

Overview


26


Unified Upgrade Procedures For ABAP and Java

One GUI for both ABAP-based and Java-based systems

Simultaneous execution

Automatic synchronization

Consolidated user interactions

27


System Switch Upgrade for Java-based Systems

Same technology as for ABAP

Standard technology for future releases

Downtime reduction to an absolute minimum with standard tools

Synchronized downtime period with ABAP

28


Copyright 2007 SAP AG. All Rights Reserved

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

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

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

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

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

29


Copyright 2007 SAP AG. Alle Rechte vorbehalten

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® und SQL Server® sind eingetragene Marken der Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower und PowerPCsind Marken oder eingetragene Marken der IBM Corporation.

Adobe, das Adobe Logo, Acrobat, PostScript und Reader sind Marken oder eingetragene Marken von Adobe Systems Inc. in den USA und/oder anderen Ländern.

ORACLE® ist eine eingetragene Marke der ORACLE Corporation.

UNIX®, X/Open®, OSF/1® und Motif® sind eingetragene Marken der Open Group.

Citrix®, das Citrix-Logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® und andere hier erwähnte Namen von Citrix-Produkten sind Marken von Citrix Systems, Inc.

HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA® ist eine eingetragene Marke der Sun Microsystems, Inc.

JAVASCRIPT® ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie.

MaxDB ist eine Marke von MySQL AB, Schweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, und weitere im Text erwähnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet.

Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherige Ankündigung geändert werden.

SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte, Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialien entstehen können. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.

Documents

SAP System Upgrade Overview