Upgrade cadence and test windows

Every SAP S/4HANA system changes over time. The editions differ in who decides when and how often. That decides how much time the business has to test, and how often it has to do it.

Public Edition: SAP's calendar

Public Edition receives two major releases a year, in February and August, named by year and month (for example 2602 and 2608). Between them, SAP delivers hotfix collections and, increasingly, smaller feature deliveries. Every customer is upgraded; the customer does not choose whether, only how well prepared it is. SAP notifies customers in advance and upgrades the test system before production, which gives a regression test window of a few weeks between them. The exact dates and window length are published for each release in SAP's upgrade schedule, so check them for your tenant rather than relying on a rule of thumb.

Private Edition and on-premise: your calendar

For Private Edition and on-premise, SAP moved to a two-year release cycle from SAP S/4HANA 2023: 2023, 2025 and so on, with feature pack stacks in between and seven years of mainstream maintenance per release. The customer decides when to apply a feature pack or move to a new release. In Private Edition, SAP performs much of the technical work under the RISE contract, but the timing is planned with the customer and the business testing is the customer's. On-premise customers run the whole upgrade themselves. In both, the upgrade moves through the landscape (sandbox, development, quality, production), and the regression test happens in quality before production, for as long as the project plan allows.

The trade-off

Private Edition and on-premise give control, and with it the temptation to postpone. Skipping releases makes each upgrade larger: more changes, more extensions to check, more retraining. Public Edition removes the choice but makes upgrades smaller and regular. Neither is easier; they demand different habits. Public Edition customers need a regression set that can run in days, twice a year, every year. Private Edition customers need the discipline to keep their system current and a regression set that does not decay between upgrades.

Decay is the quiet problem. Between upgrades, processes change, new extensions arrive and test cases are not updated. When the next upgrade comes, half the regression set no longer matches how the business works. Contoso counters this with a simple rule: any change that goes to production must update or add the regression test case for the process it touches, so the set is current whenever an upgrade or feature pack is announced.