SAP R/3 Upgrade

SAP Upgrade Concepts

What

Upgradation of the R/3 System to a higher release

using Upgrade kit supplied by SAP.
Why
The decision to upgrade should be based on Business
Need.
Reasons to upgrade.
Significant & Relevant additional functionality in new
releases Problem Fixes and Resolutions Requirement to
be on a supported release .
SAPs end of Maintenance & Support .

Upgrade
Reasons not to Upgrade.
Cost of upgrading the hardware / database / OS (if required).
Time required to Test the newer release and fix the problems
with the upgrade.
Cost of implementing the newer functionality / reviewing the
workarounds and enhancements in the previous release etc.
Cost of upgrading the SAPGUI on the users computers.
Manpower and Effort associated with the above.

When to Upgrade.
The additional functionality in the new release meets your
requirements.

Technical Upgrade
Methodology
Planning an Upgrade
OS,DB Upgrade
Pre-requisites for Upgrade
Detailed Upgrade Activities
Escalation Procedures

Planning
Readiness for Upgrade ?
Is there any other project going on ?
Are there enough resources ?
What are the time estimate ?
Budget restrictions ?
What are the show stoppers ?
Hardware architecture change ?
Functional problems ?
Training ?
Performance problems ?

Budget Planning
Budgeting for Upgrades
Front-end, Backend, Network, E-commerce
Check - What are the free services provided by SAP ?
Plan - What are the risks to be managed ?

Upgrade Schedule
Define overall upgrade schedule
Define database backup times
Method
OS upgrade

Upgrade sequence
Development system
Quality assurance
Production system

DB upgrade

R/3 upgrade

Major Factors Influencing Upgrade

Hardware
Tools

Preparation
& Planning

Teamwork and
Management

Considerations for enhancement

Hardware Upgrades
Upgrades to Application and Database server
Storage requirements determination
High-end Backup Requirements
Backup and Archiving Solution
Network Infrastructure requirements
Front-end Upgrade
Software Upgrades
Version Upgrades to OS
Version Upgrades to DB
Version Upgrades to mySAP.com products

Upgrade Steps
Pre-Upgrade Check.
Is there a performance problem ?
Is the hardware adequately sized ?
Sizing as an exercise
Perform Stress test / Load test
Downtime
Estimate the downtime properly.
Parallelise activity.
Educate the end user.

Activities during Upgrade

Detailed Steps
Database Backup
Pre - Upgrade - Hot packs application
Kernel Upgrade
Database Upgrade
OS Upgrade
Database Reorganization
Run Prepare
Perform the Upgrade
SPAU and SPDD

Factors of Runtime and Downtime

Runtime and downtime depend on:
Hardware / Operating system.
Hard disk configuration.
Database.
Modifications (SPDD).
Productive applications.
Number of clients.
Installed languages.
Upgrade strategy.
Use test upgrade to get estimations of runtime and downtime

R/3 Roadmap

Upgrade Roadmap is a generic project plan, require to

develop by the BASIS Consultant based on the source
and target system. For example.

4.6(X)

4.0(X)

During preparation
of Upgrade Roadmap
you must have to
consider the O.S and
Database support for
3.1(X)each R/3 Release.
3.0(X) R/3 Release

Upgrade Roadmap
R/3 Upgrades - Core
Product availability roadmap
Note No :156548(4.x), 23875(3.x)
Maintenance of R/3 Release :303751
Addon Products upgrade
Addon upgrade roadmap
Note No :78432
Complimentary Software Products
SAPNET
http://service.sap.com/platforms
http://service.sap.com /osdbmigration

R/3 Upgrade Assistant

New frontend with graphical user interface
Remote control of upgrades (saprouter)
Multiple user interfaces for each upgrade process
Improved analysis of errors
-Tools for analyzing upgrade log files
-Improved error tolerance (severity P)
Support functions - Internet Integration
-Direct access to OSS notes using SAPNet (4.5A)New
documentation media (HTML, ...)
-Sap router support, direct OSS access
-Alert Service and Input Wizard

R/3 Upgrade Assistant

R/3 Upgrade Assistant: Architecture

Administrator

R3up

Upgrade
Assistant
Server

Observer 1

Firewall

Observer 2

Benefits:
Upgrade process runs independently of frontend
More than one connection
Remote connection possible

R/3 Upgrade Assistant: R3up control

Escalation Procedure
Check with SAP Support for help during upgrade
Have access to OSS
Have a backup person work from office if no OSS
Check with your experienced colleagues in case of
problem.
Ensure you have enough resources to perform the
upgrade
Plan the upgrade time properly

Optimizing the Upgrade Process

Goals
Downtime Reduction for productive systems
Predictability and Planning of Upgrade ASAP
Support for Upgrade Project Management ASAP
Unattended upgrade via PREPARE phase to reduce
Upgrade support time R/3 Upgrade Assistant
Usability improvements UA
Technical downtime reduction ICNV
Enhanced Modification Adjustment Modif.Assistant

Upgrade Strategies

Strate Advantages
Disadvanta
gy
ges
Disk capacity for a
A_switc Short downtime
Medium amount of space possible database
h
required if you need to recover recovery is monitored.
the database.

A_on

Shortest downtime
No offline backup required after
upgrade

Greatest
additional
space requirements to
ensure database
recovery.
Disk capacity for a
possible database
recovery is monitored

A_of

No additional space required if

you need to recover the
database
Offline
backup
necessary after the upgrade.

Longest downtime
Disk capacity for a
possible
database
recovery
is
not
monitored.

R/3 Upgrade: Using the right strategy

A_SWITCH: Productive First Steps (DEV System)

Productive
Operation

Repository
Data Import

Copy
Cust.
Rep.

Downtime

Switch
+
Table
Adjust

Dev. Sync
Locked Point

Import
Control

Import
Lang.
Cleanup

Database
Backup

time
10

14

16

~20

R/3 Upgrade: Using the right strategy

A_ON: Shortest Downtime (Production System)

Productive
Operation

Repository
Data Import

Copy
Cust.
Rep.

Import
Lang.
Cleanup

Downtime

Switch
+
Table
Adjust

Stop
Production

Database
Backup

Import
Control

time
10

14

Restart
Production

16

~20

R/3 Upgrade: Using the right strategy

A_OFF: Upgrade with full downtime (Quality System)
Productive
Operation

Downtime

Repository
Data Import

Copy
Switch
Cust.
+
Reposit. Table Adjust

5
Sync
Point

10

Import
Control
Data

Import
Lang.
Cleanup

14

Database
Backup

16 h

time