Lesson 1 of 6
The SAP-managed cadence
10 min
Listen to this lesson
In SAP S/4HANA Cloud Public Edition you do not decide when to upgrade. SAP does. The software in your systems moves forward on a published schedule, and your job as a test lead is to prove, every time, that your configured processes, extensions and integrations still work before the new release reaches production. This course is about doing that well and on time. Contoso's examples here are a what-if, explained below: its real program runs on Private Edition.
Major releases and feature deliveries
SAP's learning material for Public Edition describes two major releases a year, in February and August. Release names follow a year-month pattern: a release such as 2708 is the August 2027 release, and a suffix such as 2708.2 marks the second feature delivery since that major release. Between major releases, smaller and non-disruptive features ship continuously; customers can activate many of them early, and if they don't, relevant features are enabled with the next major release.
On top of that, SAP applies regular corrections (hotfix collections) during scheduled maintenance windows between major releases. Treat the exact frequency and timing as something you read from SAP's current Upgrade & Maintenance Schedule for your landscape rather than from memory: it is the document SAP points customers to, and it changes from year to year.
- About 6 weeks beforeNotificationSAP emails the customer that an upgrade is coming
- Week 0Test system upgradedThe regression window opens
- Weeks 0–3Customer regressionAutomated and manual tests, fixes, transports into Test
- About 3 weeks after the test upgradeDevelopment and production upgradedThe new release is live for the business
Test first, then production
For a major release, SAP's learning material describes this order: customers get an email notification about six weeks ahead, the test system is upgraded first, and the development and production systems follow about three weeks later. That three-week gap is your regression window. During it, customizing and development transports can still be released and imported into the test system, so fixes found during regression can be moved and retested before production is upgraded.
Content follows software. After the software upgrade, new reference content is released in SAP Central Business Configuration and recorded in a transport that reaches the development tenant automatically. The customer decides when to move it to Test and Production with the Import Collection app. SAP's guidance is to finish regression in Test before moving content to Production, and to watch the What's New Viewer filter for features that need the latest reference content version.
| Change type | Who triggers it | What the test lead does |
|---|---|---|
| Major release (February, August) | SAP, on the published schedule | Full regression cycle in the test system during the window |
| Continuous feature delivery | SAP ships; customer may activate early | Test features you activate; plan for those enabled at the next major release |
| Hotfix collections | SAP, in maintenance windows | Smoke tests on critical processes; watch for incidents |
| Reference content upgrade | Customer, via Import Collection | Regression in Test before importing to Production |
| Your own configuration and extensions | Customer, via transports | Functional tests plus regression of neighbors |
Where to read what is coming
- Upgrade & Maintenance Schedule: the dates for your landscape. Put them in the test calendar for the year.
- What's New Viewer on the SAP Help Portal: new and changed features per release, filterable and exportable.
- Release Navigator: a central entry point to release resources, also reachable from SAP Cloud ALM.
- Release Assessment and Scope Dependency (RASD): a free tool that compares release information with your actual system usage to give a "day 1 impact" view. Someone with the right permission (such as an IT contact) must log in to see real systems; others see demo data.
What would you do?
In the what-if, Grace asks Priya in January when the regression team for the next major release must be booked. What should Priya do first?
- Public Edition has two major releases a year (February and August) plus continuous feature deliveries and regular corrections.
- The test system is upgraded first; development and production follow about three weeks later. That gap is your regression window.
- Transports can still move into Test during the window, so fixes can be retested before production is upgraded.
- Read dates from SAP's Upgrade & Maintenance Schedule and impact from the What's New Viewer and RASD.
Check your understanding · not graded
Lesson check
1. In which months does SAP ship the major Public Edition releases?
2. Which system does SAP upgrade first in a three-system landscape?
3. What does the suffix in a release name such as 2708.2 indicate?
4. Which tool gives a "day 1 impact" view by comparing release information with your system usage?