Lesson 2 of 5
Stacks and versions
10 min
Listen to this lesson
Notes fix individual problems. Larger maintenance arrives as packages, and the vocabulary matters because each kind has a different scope, risk and test effort. SAP training separates four levels: SAP Notes, support packages, feature packages and release upgrades.
Support packages and stacks
A support package is a group of corrected or new objects for one software component, such as SAP_BASIS or the SAP S/4HANA application component. Each component has its own sequence. Because components depend on each other, SAP bundles tested combinations into a support package stack for a product version, and recommends applying whole stacks rather than arbitrary combinations. SAP training says stacks are typically assembled every three to six months for most product versions.
Feature packages
A feature package can also contain innovations and new functions. Technically, feature packages are imported like support packages, as a stack with their own prerequisites. For SAP S/4HANA, a release is followed by a series of feature package stacks; the last one before the next release (SAP calls it the "go-to" feature package) usually begins a maintenance-only phase with corrections but no innovations. Since the 2023 release, SAP ships an SAP S/4HANA base release every two years with seven years of mainstream maintenance, and feature package stacks roughly every six months until the next base release; after that, the older release receives support package stacks with corrections only. SAP S/4HANA 2025 shipped in October 2025, so under that rule its mainstream maintenance runs to the end of 2032 and the next base release is due in 2027. Private cloud customers under RISE must upgrade at least once within the seven-year window. Confirm the exact dates in SAP's release and maintenance strategy and the Product Availability Matrix before you plan around them.
| Support package stack | Feature package stack | Release upgrade | |
|---|---|---|---|
| Content | Corrections, legal changes, security fixes | Corrections plus new features | New product version |
| Tool | SPAM or SUM | SPAM or SUM | SUM |
| Modification adjustment | SPDD/SPAU for affected objects | SPDD/SPAU, usually more objects | SPDD/SPAU at full scale |
| Typical test scope | Risk-based regression | Regression plus new-feature checks | Full regression and many new-feature checks |
| Planning horizon | Weeks | Weeks to a few months | Months, often a project |
The other layers: kernel and database
Two more layers have their own patches. The SAP kernel (the executables that run the system at operating-system level) is patched by replacing files; SAP training recommends backing up the kernel directory first, and a rolling kernel switch can update application servers one at a time while the system keeps running. The SAP HANA database has its own revisions and support packages. A maintenance plan names all three layers: ABAP stack, kernel and database.
- ReleaseSAP S/4HANA 2025 initial shipmentContoso's conversion target; the go-live stack is fixed by the project
- Feature package stacksNew features plus correctionsApplied after go-live when the business case and test capacity justify it
- Support package stacksCorrections and legal changesPlanned regularly to stay within supported levels
- Go-to feature packageLast feature package of the releaseStart of the maintenance-only phase
- Next releaseUpgrade projectPlanned months ahead with full regression
Who does what under RISE
In a RISE with SAP private cloud like Contoso's, SAP operates the technical layer, and technical maintenance such as applying stacks, kernel patches and SAP HANA revisions is typically performed by SAP as part of the service. The customer still decides which target stack and when, performs the modification adjustment for its own changes, and tests. The exact split is defined in the service description and the roles-and-responsibilities documents of the contract, so check them before assuming who does what. Either way, the vocabulary in this lesson is what Contoso's release manager and SAP's team use to agree a plan.
What would you do?
Grace asks Sam whether the next maintenance event for CMP, a feature package stack, can be tested "like a note", with a few spot checks. What is the best answer?
- SAP Notes fix single issues; support packages bundle corrections per component; stacks combine components.
- Feature packages add features and are applied like support packages, as a stack.
- Release upgrades move to a new product version and are projects.
- Plan kernel and SAP HANA patches alongside the ABAP stack.
Check your understanding · not graded
Lesson check
1. What is a support package stack?
2. What can a feature package contain that a support package normally does not?
3. What does a rolling kernel switch allow?
4. Where should Contoso check the cadence and maintenance period of SAP S/4HANA 2025?