Lesson 1 of 6
What 'end of maintenance' really means: mainstream, extended, customer-specific
10 min
Listen to this lesson
Every SAP deadline headline compresses a contract term into a single year. "ECC ends in 2027" is the classic example, and it is wrong in two ways: the software does not stop working, and 2027 is only the end of one kind of support. Before a steering committee builds a plan on a date, someone has to say precisely what ends on that date. This lesson gives you the vocabulary. The rest of the course applies it product by product.
Three maintenance phases
SAP describes the support for an on-premise release in phases. Mainstream maintenance is the standard service included in your maintenance contract: support packages, corrections, legal changes such as tax and reporting updates, and security notes. Extended maintenance is an optional, paid extension for selected releases. SAP Note 52505 describes it as the same scope of service as mainstream maintenance, bought through a supplementary agreement for a fixed period. Customer-specific maintenance is what a release falls into automatically when mainstream (or extended) maintenance ends and nothing else is contracted. SAP still helps solve problems, but it no longer ships new support packages or legal changes for that release.
| Phase | What you get | What you pay | Typical misquote |
|---|---|---|---|
| Mainstream maintenance | Support packages, corrections, legal changes, security notes | Included in the standard maintenance fee | "After this date the system stops." |
| Extended maintenance | Same scope as mainstream, for selected releases and a fixed period | Optional; for SAP Business Suite 7 a premium of two percentage points on the maintenance base | "Everyone is covered to 2030." |
| Customer-specific maintenance | Problem solving on the existing code; no new legal changes or support packages | Standard fee; the risk moves to you | "It is the same support, just older." |
| Use right (Compatibility Scope) | Permission to use a legacy function inside SAP S/4HANA at all | Part of the license or subscription | "It is only maintenance, we can keep using it." |
Maintenance phases and the separate idea of a use right.
Maintenance versus use rights
Maintenance is about support. A use right is about whether you may run the function at all. Most deadlines in this course are maintenance deadlines: after them you may keep running the software at growing risk. Compatibility Scope is different. SAP's own February 2026 user-group deck on compatibility packs states that after the defined end date the use right expires, not only the maintenance. That means a function you are not allowed to use, not a function that simply gets no more patches. Confusing the two is the most expensive mistake on the map.
| Question | Maintenance deadline | Use-right deadline |
|---|---|---|
| Does the software keep running? | Yes | Technically yes, but you are no longer licensed to use it |
| Can you buy more time? | Often: extended maintenance | Only where SAP grants an extension |
| Typical examples | ECC 6.0, PI/PO 7.5, Solution Manager 7.2, BW 7.5 | Compatibility Scope items in SAP S/4HANA |
| Risk if ignored | Missing legal changes and security fixes | License non-compliance found in an audit |
Why legal changes matter most
Teams often think of maintenance as bug fixes, and a mature ECC system has few new bugs. The real loss is legal changes. US sales and use tax changes, 1099 reporting, payroll rules in other countries, e-invoicing mandates: these arrive as SAP notes and support packages during mainstream and extended maintenance. A system in customer-specific maintenance gets none of them. For Contoso, Dan's finance team relies on year-end legal updates; Nadia relies on security notes. Neither can wait for a contract negotiation.
- Security: SAP Security Notes keep coming for releases in maintenance; a release outside maintenance becomes an audit finding.
- Legal and regulatory: tax, reporting and e-document changes stop for releases in customer-specific maintenance.
- Interoperability: new operating system, database and browser versions are certified only for maintained releases.
- People: skills for retired products become scarce and expensive, which is a test-staffing risk as well as a support risk.
- Is the date a use-right date?Yes → the function must be replaced or relicensed by then · No → next question
- Will the product still run live business after the date?No → plan decommissioning and archive access · Yes → next question
- Is extended maintenance offered and affordable?Yes → budget it and record a dated exit · No → next question
- Can the business accept no legal changes or new patches?Yes → record it as an accepted risk with an owner · No → bring the migration forward
What would you do?
In a steering meeting, the CFO says: "Our auditor read that ECC ends in 2027. If we slip to Q1 the following year, do we have to switch the system off?" Grace turns to you. What is the most accurate answer?
- Mainstream maintenance is included; extended maintenance is optional, paid and time-boxed; customer-specific maintenance is the automatic fallback.
- Customer-specific maintenance keeps problem solving but stops legal changes and new support packages.
- Compatibility Scope dates are use-right dates: after them you may not use the function.
- Legal changes and security notes are the real loss when maintenance ends.
- Always label a date with its type, scope and source.
Check your understanding · not graded
Lesson check
1. What happens to a release when mainstream maintenance ends and no extension is contracted?
2. What does customer-specific maintenance no longer include?
3. Why is a Compatibility Scope date different from the ECC 2027 date?
4. Which loss usually hurts most when a release leaves maintenance?