Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 5

SAP's cadences: the clocks you plan around

9 min

After Contoso Motor Co. goes live on SAP S/4HANA, the project calendar ends and the run calendar begins. Luis, the release manager, now has to fit Contoso's own releases between events that SAP schedules: support and feature packages, security notes, cloud upgrades, maintenance end dates. Priya, the test lead, needs to know which of those events require testing and how much. Grace, the PMO lead, wants one calendar the steering committee can read. This course builds that calendar, starting with the clocks SAP runs on.

MonthlySAP Security Patch Day, the second Tuesday of each month: new and updated security notes
About every two weeksPublic edition hotfix collections, applied by SAP
QuarterlySAP BTP ABAP environment release upgrades, with an optional pre-upgrade of a test system
Twice a yearPublic edition major releases (February, August); private edition and on-premise feature or support package stacks (about every six months)
Every two yearsPrivate edition and on-premise base releases since SAP S/4HANA 2023, each with seven years of mainstream maintenance
ContinuouslyMost SAP BTP services and SAP Cloud ALM, updated by SAP without a customer upgrade project
SAP's clocks from fastest to slowest. Each one creates a testing obligation of a different size.
The Sign-Off Table · thesignofftable.com/academy/sap-rel-204

Private edition and on-premise

Contoso runs SAP S/4HANA Cloud Private Edition, which follows the same release cycle as on-premise because it is the same software. After the 2023 release, SAP moved to a two-year base release cycle and extended mainstream maintenance from five to seven years per release. After a base release, SAP ships feature pack stacks (FPS) about every six months, with corrections and new, non-disruptive features, until the next base release. The previous release then receives support package stacks (SPS) about every six months, with corrections only, until its mainstream maintenance ends. SAP Learning adds that customers must install at least one upgrade every seven years to stay in mainstream maintenance, and that under RISE with SAP the customer can request an upgrade once a year; SAP performs the technical upgrade, while planning, preparation and testing stay with the customer.

Public edition

SAP S/4HANA Cloud Public Edition has two major releases a year, in February and August, with feature deliveries between them and hotfix collections that SAP has described as arriving in roughly two-week blocks. SAP sets the upgrade dates: the test system first, then development and production about three weeks later, after an email notification about six weeks ahead. The customer controls none of the timing, only how ready the regression pack is.

SAP BTP and SAP Cloud ALM

Most BTP services are updated continuously; changes are published in the What's New Viewer for SAP BTP rather than as customer upgrade projects. The SAP BTP ABAP environment is the exception that looks like the public edition: SAP has described four major release upgrades a year on a predefined schedule, with an option to have a nominated test system upgraded about two weeks early for regression testing. SAP Cloud ALM, which Contoso uses for test and change management, is also delivered continuously.

Security notes

SAP publishes security fixes as SAP Security Notes on its monthly Security Patch Day, the second Tuesday of each month, a day SAP aligned with the patch days of other major vendors. Some notes are Patch Day notes that need attention; others are support package notes that arrive automatically with the next support package. Security notes are small but frequent, and some need prompt action, so the calendar needs a monthly slot for assessment and targeted testing.

ProductCadenceWho sets the timingTypical test response
S/4HANA private edition / on-premiseBase release every two years; FPS or SPS about every six monthsCustomer (SAP executes under RISE)Planned regression per stack; project-scale testing per upgrade
S/4HANA public editionReleases in February and August; hotfixes in betweenSAPRegression in a fixed window after the test system upgrade
SAP BTP servicesContinuousSAPSmoke tests of key apps and integrations; watch What's New
SAP BTP ABAP environmentFour upgrades a yearSAP, with optional pre-upgradeRegression on the pre-upgraded test system
Security notesMonthly Patch DaySAP publishes; customer appliesAssess monthly; targeted test of affected areas
SAP cadences and what each one asks of a test team. Confirm current details in SAP's published information.
The Sign-Off Table · thesignofftable.com/academy/sap-rel-204

What would you do?

Grace asks whether Contoso should apply every feature pack stack the moment SAP releases it, "to stay current". What should Luis recommend?

Key points
  • Private edition and on-premise: base release every two years since 2023, seven years of mainstream maintenance, FPS/SPS about every six months.
  • Public edition: February and August releases on SAP's schedule, test system first.
  • BTP services change continuously; the BTP ABAP environment upgrades quarterly with a pre-upgrade option.
  • Security Patch Day is the second Tuesday of every month.
  • Each clock creates a different testing obligation; the calendar must show all of them.

Check your understanding · not graded

Lesson check

  1. 1. Since SAP S/4HANA 2023, how often does SAP deliver a new base release for private edition and on-premise?

  2. 2. How long is mainstream maintenance for each new base release?

  3. 3. When is SAP Security Patch Day?

  4. 4. Who controls the timing of public edition upgrades?