SAP S/4HANA Cloud Public Edition follows a semi-annual release schedule, with major updates occurring every February (02) and August (08). These releases deliver new business processes, enhancements to existing functionality, and technical features.
Release Naming Convention
The release code identifies the timing and version. For example, 2708.2 represents:
- 27: The year (2027)
- 08: The major release month (August)
- 2: The second subsequent feature delivery since that major release
Feature Activation and Delivery
- Automatic Enhancements: SAP automatically pushes updates to customer systems based on the defined Upgrade & Maintenance schedule. Enhancements to existing processes only apply if those processes are already active in the customer's system.
- Continuous Innovation: Between major releases, smaller, non-disruptive features are delivered. Customers can choose to adopt these early. If not manually activated, these features are automatically enabled during the next major release (provided they are relevant to the customer's active scope).
- New Business Processes: Activation of entirely new business processes remains at the customer's discretion and is managed through SAP Central Business Configuration.
Software Upgrade Process Flow
- Preparation (6 Weeks Prior): Customers receive an email notification six weeks before an upgrade.
- Test System Upgrade: SAP upgrades the Test System first.
- Regression Testing: Partners and customers perform regression testing to ensure existing and customized processes work correctly. The Test Automation Tool is recommended to accelerate this phase.
- Transports: Customizing and development transports can be released and imported into the Test system during this window.
- Development and Production Upgrade: Three weeks after the Test system upgrade, SAP upgrades the Development and Production systems to the latest software release.
Note
Importing key user extensions created in a previous release version into an upgraded system may not be possible.
Content Upgrade Process Flow
The content upgrade (updates to business process logic and configuration) follows the software upgrade to ensure alignment across the landscape.
- SAP Central Business Configuration & Development System: Content changes are released in SAP Central Business Configuration on the release schedule. These are recorded in a transport request, and automatically exported to the Development System tenants.
Note
The transport from SAP Central Business Configuration to the Development System is automatic, however the implementation team/customer have control over deciding when they want to transport the upgrade content to the Test and Production Systems. - Test System: The content can be transported to the Test system manually or via an automation schedule in the Import Collection app. Regression testing should be completed here before proceeding.
- Production System: Once validated in Test, the content upgrade can be transported to the Production system manually or via an automation schedule in the Import Collection app.
Importance of Content Alignment
It's critical to move new business process content to the Production system quickly. Many software features have a content dependency, meaning they only function if the corresponding content version is present.
- What’s New Viewer: Use the "Latest Reference Content Version Required" filter to identify features with specific content dependencies in the What's New Viewer.
- Automation: While transporting is manual by default, it is highly recommended to use the Import Collection app to set up an automation schedule, ensuring software and content versions remain synchronized across all systems.
