To define a strategy for upgrading your SAP environment to the next SAP release
This strategy should include both CA release and GA release upgrades.
Controlled Availability (CA) releases
· Provide new SAP functionality
· Receive only limited maintenance from SAP
· Are only shipped to customers on request
General Availability (GA) releases
· Provide only corrections with no new functionality
· Are automatically delivered to all SAP customers
· Receive full maintenance from SAP
· Are recommended by SAP for production use
During the implementation project, do not apply any CA release upgrades to the environment unless you need the new functions.
Analyze minor release upgrades carefully and do not load GA releases less than three months before the going live date.
1. Define a detailed strategy that includes:
- Upgrading the development, quality assurance, and production systems
- Estimating the projected technical downtime
- Understanding the upgrade and post-upgrade activities
- Defining the skill sets required for an upgrade and for Support Packages
- Using the SAP Upgrade Manual and SAP Notes for additional information
- Appreciating the technical and functional differences between major upgrades and maintenance releases
2. Document the projected timeline for the upgrade.
Upgrade strategy with minimal disruption of the project or production operation
For more detailed information, see the ASAP Upgrade Roadmap.
To decide whether to implement a new CA release, check whether the new functionality is relevant to your company. For more information, read the SAP Development News published a few weeks before the release is shipped.
To decide whether to implement a new GA release, check whether the corrections are relevant for the functions you use. For more information, read the SAP Release Notes published when the release is shipped.