Lesson 5 of 5
Testing implications: release cadence and ownership
7 min
The biggest testing change in a cloud ERP contract is not during the project. It is after go-live. On ECC, Contoso decided when to apply support packages, and it often waited years. Under RISE and GROW, updates arrive on a rhythm, and every update needs evidence that Contoso's processes still work. Testing becomes a recurring business activity, and its ownership stays with the customer.
Private edition rhythm
SAP S/4HANA Cloud Private Edition follows the on-premise S/4HANA release cycle because it is the same software. Since the 2023 release, SAP ships a new base release every two years, with seven years of mainstream maintenance. Between base releases, Feature Package Stacks deliver non-disruptive new features about every six months; older releases receive Support Package Stacks with corrections. Under RISE, SAP's learning content says customers can request one upgrade per year from SAP, and must upgrade at least once within the seven-year window to stay in mainstream maintenance.
- Go-liveSAP S/4HANA 2025Contoso goes live on the 2025 release in Q3
- About 6 monthsFeature Package StackNew non-disruptive features; Contoso requests the update and runs regression
- About 12 monthsNext Feature Package StackSame pattern; the regression suite grows with each change
- About 2 yearsNext base release availableContoso decides when to plan a full upgrade project
- Within 7 yearsUpgrade requiredAt least one upgrade to stay in mainstream maintenance
Public edition rhythm
The public edition is different: SAP upgrades every tenant on a published calendar, with two major releases a year, named by year and month (for example, 2508 for August 2025). Smaller features arrive in between. The test system is upgraded first; development and production follow a few weeks later. That gap is the customer's regression window. SAP provides the Test Automation Tool for the public edition and a release assessment tool to focus testing on what changed. Exact gaps vary by release, so check the upgrade calendar for your tenant.
| Topic | Private Edition (RISE) | Public Edition (GROW) |
|---|---|---|
| Who chooses update timing | Contoso, within SAP's maintenance rules | SAP, on a published calendar |
| Frequency | Feature Package Stacks about twice a year; upgrades when planned | Two major releases a year plus smaller updates |
| Regression window | Set by Contoso's plan, before production | Fixed gap between test and production upgrades |
| SAP test tooling | SAP Cloud ALM for test management | SAP Cloud ALM plus the Test Automation Tool |
| Who tests business processes | Contoso, or SAP if a packaged service is bought | The customer, usually with its partner |
What the program must leave behind
Because regression never stops, the program's test assets are part of the deliverable, not by-products. Priya plans for three things to be handed to the support organization at hypercare exit: a regression suite of process-based test cases in SAP Cloud ALM, prioritized by business risk; test data that can be refreshed or recreated in QAS; and a named owner for each process's regression evidence. Whether to automate part of that suite is a decision for Explore or Realize, based on how often it will run.
- Update announcedSAP or Contoso schedules a Feature Package Stack or release
- Impact assessmentRelease notes and assessment tools identify changed areas
- Regression scopeRisk-based selection from the Cloud ALM regression suite
- Execute in QASManual and automated tests with evidence attached
- DecideProcess owners accept; production update proceeds or is held
What would you do?
Six months after go-live, SAP makes a Feature Package Stack available. Contoso's support manager wants to apply it "since SAP has already tested it". What should Priya recommend?
- Under RISE and GROW, regression testing is recurring and stays the customer's responsibility unless a service is bought.
- Private edition: base release every two years, Feature Package Stacks about every six months, seven years of mainstream maintenance.
- Public edition: two major releases a year on SAP's calendar, with the test system upgraded before production.
- Hand over a risk-based regression suite, test data and named owners at the end of the project.
Check your understanding · not graded
Lesson check
1. How often does SAP ship a new private edition base release since 2023?
2. In the public edition, which system is upgraded first?
3. Which SAP tool supports automated testing in the public edition?
4. What should the program hand to support for future regression?