sap r3 upgrade
DESCRIPTION
SAP R3 UpgradeTRANSCRIPT
SAP Upgrade Concepts
WhatUpgradation of the R/3 System to a higher release using Upgrade kit supplied by SAP.WhyThe 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 .SAP’s end of Maintenance & Support .
UpgradeReasons not to Upgrade.Cost of upgrading the hardware / database / OS (if required).Time required to Test the newer release and fix the problemswith the upgrade.
Cost of implementing the newer functionality / reviewing theworkarounds 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 yourrequirements.
Technical UpgradeMethodology
Planning an UpgradeOS,DB UpgradePre-requisites for UpgradeDetailed Upgrade ActivitiesEscalation Procedures
PlanningReadiness 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 ScheduleDefine overall upgrade schedule
Define database backup times
Method
OS upgrade DB upgrade R/3 upgrade
Upgrade sequence
Development system
Quality assurance
Production system
Considerations for enhancementHardware Upgrades
Upgrades to Application and Database serverStorage requirements determinationHigh-end Backup RequirementsBackup and Archiving SolutionNetwork Infrastructure requirementsFront-end Upgrade
Software UpgradesVersion Upgrades to OSVersion Upgrades to DBVersion Upgrades to mySAP.com products
Upgrade Steps Pre-Upgrade Check.Is there a performance problem ?Is the hardware adequately sized ? Sizing as an exercisePerform Stress test / Load test Downtime
Estimate the downtime properly.Parallelise activity.Educate the end user.
Activities during Upgrade Detailed Steps
Database BackupPre - Upgrade - Hot packs applicationKernel UpgradeDatabase UpgradeOS UpgradeDatabase ReorganizationRun PreparePerform the UpgradeSPAU 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
3.0(X) R/3 Release
3.1(X)
4.0(X)
4.6(X)
Upgrade Roadmap is a generic project plan, require to develop by the BASIS Consultant based on the source and target system. For example.
During preparation of Upgrade Roadmap you must have to consider the O.S and Database support for each R/3 Release.
Upgrade RoadmapR/3 Upgrades - Core
Product availability roadmapNote No :156548(4.x), 23875(3.x)Maintenance of R/3 Release :303751
Addon Products upgradeAddon upgrade roadmapNote No :78432
Complimentary Software ProductsSAPNEThttp://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
Administrator
Observer 1
Firewall Observer 2
R3upUpgradeAssistant
Server
R/3 Upgrade Assistant: Architecture
Benefits: Upgrade process runs independently of frontend More than one connection Remote connection possible
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 ProcessGoals
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 StrategiesStrategy
Advantages Disadvantages
A_switch
Short downtimeMedium amount of space required if you need to recover the database.
Disk capacity for a possible databaserecovery is monitored.
A_on Shortest downtimeNo offline backup required after upgrade
Greatest additional space requirements to ensure databaserecovery.Disk capacity for a possible databaserecovery is monitored
A_off No additional space required if you need to recover the database Offline backup necessary after the upgrade.
Longest downtimeDisk capacity for a possible database recovery is not monitored.
A_SWITCH: Productive First Steps (DEV System)
ProductiveOperation
Downtime
5 7 10 16
time
h
RepositoryData Import
Copy Cust.Rep.
Switch+
TableAdjust
ImportControl
Import Lang.
Cleanup
~20
DatabaseBackup
14SyncPoint
Dev.Locked
R/3 Upgrade: Using the right strategy
A_ON: Shortest Downtime (Production System)
ProductiveOperation
Downtime
time
h
RepositoryData Import
Copy Cust.Rep.
Switch+
Table Adjust
ImportControl
DatabaseBackup
StopProduction
RestartProduction
5 7 10 16 ~20 14
Import Lang.
Cleanup
R/3 Upgrade: Using the right strategy
A_OFF: Upgrade with full downtime (Quality System)
ProductiveOperation
Downtime
5 7 10 14 16 timeh
RepositoryData Import
Copy Cust.
Reposit.
Switch+
Table Adjust
ImportControl
Data
Import Lang.
Cleanup
SyncPoint
DatabaseBackup
R/3 Upgrade: Using the right strategy