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

Lesson 1 of 5

Upgrade types and cadence

11 min

Listen to this lesson

0:00 / 7:18

A conversion is a once-in-a-decade event. Upgrades are not. Once Contoso Motor Co. is live on SAP S/4HANA Private Edition, SAP will deliver feature pack stacks and support pack stacks every few months and a new release every two years, and Contoso has to test each one it applies. This course is about testing those updates efficiently: knowing what kind of update you face, which test streams it needs, how to scope them with SAP's own tools, how to plan iterations, and how to decide go or no-go.

Throughout, we follow Contoso after go-live. Priya leads testing, Sam leads Basis, Kenji leads ABAP development, Luis runs the update cutover, Grace chairs the decision, and Dan (finance process owner) and the sales process owner sign off for finance and order to cash, with Maria, the order-to-cash key user, running the order-to-cash checks. Under RISE with SAP, SAP Enterprise Cloud Services (ECS) performs the technical update; Contoso plans, prepares, tests and decides.

Three kinds of update

UpdateWhat changesExampleTypical test effort
Release upgradeNew product version with new and changed functions and simplification itemsSAP S/4HANA 2023 to 2025Project: technical, custom code, full regression, performance, UAT
Feature pack stack (FPS)Non-disruptive new features plus corrections within the current release2025 FPS01 to FPS02Targeted: technical checks, regression of changed areas, new features opted into
Support pack stack (SPS)Corrections only, for releases in their later lifeLater stacks of an older releaseLight: technical checks, regression of critical processes
Kinds of SAP S/4HANA updates and how test effort scales.
The Sign-Off Table · thesignofftable.com/academy/sap-tst-304

SAP's learning material for Private Edition describes the cadence: base releases every two years following the on-premise cycle, feature pack stacks every six months between base releases, and support pack stacks every six months with corrections only for the prior release. Mainstream maintenance was extended from five to seven years. Under RISE, SAP's learning material also notes that customers can request one upgrade a year. Check your own contract and the current release strategy for exact entitlements and dates.

  1. Year 0New releaseBase release available; initial shipment followed by feature pack stacks.
  2. Every ~6 monthsFeature pack stacksNew non-disruptive features and corrections for the current release.
  3. Year 2Next releaseThe previous release moves to support pack stacks: corrections only.
  4. Up to 7 yearsMainstream maintenancePlan a release upgrade well before maintenance for your release ends.
The SAP S/4HANA Private Edition update cadence, simplified.
The Sign-Off Table · thesignofftable.com/academy/sap-tst-304

Why test effort differs

Test effort follows risk, and risk follows what changes. A release upgrade brings simplification items, which document functional differences between start and target release: functions changed, replaced or removed. It updates the technical stack (for 2025, the upgrade guide notes that software component SAP BASIS moves to 8.16) and usually requires custom code adaptation. A feature pack stack stays within the release, so simplification impact is smaller, but it still delivers new code into every area and can change user interfaces. A support pack stack carries corrections, which can still change behavior you rely on.

Test depth starts from what SAP changes in the update, then grows with how much custom code, modification and interface exposure Contoso has.
The Sign-Off Table · thesignofftable.com/academy/sap-tst-304
RoutineSPS on a clean system: technical checks and critical-process regression.
Watch the standardRelease upgrade on a clean, standard system: simplification-driven regression.
Watch the customFPS on a heavily customized system: custom code, modifications and interfaces dominate.
Full projectRelease upgrade on a heavily customized system: every stream at full depth.
Test effort depends on both SAP's change and your own exposure.
The Sign-Off Table · thesignofftable.com/academy/sap-tst-304

The update path through the landscape

  1. PlanChoose the target and path; SAP's Release Upgrade Management application in SAP for Me helps plan timelines and service requests.
  2. SandboxOptional but recommended: a copy of production for the first technical run and discovery.
  3. Development (CMD)Update first; adjust modifications and custom code; development is locked for part of the update.
  4. Quality (CMQ) and pre-production (CMR)Update with the adjustment transports; run full test streams in CMQ, then the release regression and sign-off in CMR.
  5. Production (CMP)Update in the agreed downtime; smoke tests, validation and hypercare.
An update moves through the landscape in transport order.
The Sign-Off Table · thesignofftable.com/academy/sap-tst-304

The upgrade guide is explicit about order: update systems in the same sequence in which you transport custom objects, with each system on the same software level, and transport only between systems at the same release and stack. That rule shapes the test plan in lesson 4.

Systems are updated in transport order, and transports only move between systems on the same release and stack, so the test plan follows the same sequence.
The Sign-Off Table · thesignofftable.com/academy/sap-tst-304

What would you do?

Contoso's Basis lead proposes treating the next feature pack stack exactly like the last release upgrade: full regression of all 600 test cases, two UAT weeks and a performance test. Priya thinks that is too much. What is the best approach?

Key points
  • Release upgrades, feature pack stacks and support pack stacks differ in scope and test effort.
  • Private Edition: new release every two years, FPS every six months, SPS corrections for older releases; seven years of mainstream maintenance.
  • Effort depends on SAP's change and your exposure: custom code, modifications, integrations.
  • Updates move through the landscape in transport order, each system on the same level.
  • Under RISE, SAP ECS performs the technical update; the customer plans, tests and decides.

Check your understanding · not graded

Lesson check

  1. 1. Which kind of update brings new simplification items and usually requires custom code adaptation?

  2. 2. How often do feature pack stacks arrive for SAP S/4HANA Private Edition, per SAP learning material?

  3. 3. In which order should Contoso update its systems?