Database Reference
In-Depth Information
• Release the system for productive business use.
Summary
• The SAP upgrade is performed using the Upgrade GUI program.
• Technical downtime includes time required for performing the technical upgrade.
• Business downtime includes the technical downtime plus the additional downtime
needed for performing post technical upgrade steps. It is also the time the application
is not available to the end business user.
• The goal of effective upgrade projects should be to reduce business downtime.
• A system-switch upgrade creates a parallel shadow instance in the same database.
• The shadow instance is for the target SAP release.
• The resource-minimized strategy consumes fewer system resources but has a longer
downtime.
• The downtime-minimized strategy consumes more system resources but has a shorter
downtime.
• SAP provides a number of upgrade tools to help the customer plan and execute the up-
grades.
• The upgrade program executes the upgrade in eight roadmap steps.
• The upgrade master guide, technical upgrade guide, and upgrade OSS Notes must be
downloaded before starting the upgrade.
• Upgrade software must be downloaded before starting the upgrade.
• Upgrade software logistics must be planned ahead of the time for the upgrade project.
• Successful execution of SAP upgrades involves a lot of planning and practice runs be-
fore the final production upgrade is executed.
Additional Resources
•
Upgrade technology
www.sdn.sap.com/irj/sdn/upgradetech
•
Upgrade to ERP 6.0
www.sdn.sap.com/irj/bpx/index?rid=/webcontent/uuid/
70a24e6f-de25-2b10-bdba-cd1affa226e3
•
Business rationale and perspective for SAP upgrades
www.sap.com/services/more/
erpupgrade/index.epx
