SAP ECC end of maintenance 2027: what it means for SAP Product Compliance
Mainstream maintenance for SAP ECC ends in 2027. We explain what this means for your Product Compliance solution — and why the Classic Scenario on S/4HANA has an end date too.
For most SAP customers, 2027 is the year their S/4HANA planning is working towards. For Product Compliance — formerly SAP EH&S — there is a second date that is often overlooked: the classic solution now has a planned end on S/4HANA as well. Here is the context.
The dates at a glance
| Date | What happens |
|---|---|
| 31 Dec 2027 | End of mainstream maintenance for SAP ECC (EHP 6–8) |
| S/4HANA 2029 | Last release in which Classic can be used without restriction |
| 31 Dec 2030 | End of optional extended maintenance for SAP ECC |
| S/4HANA 2031 | Classic functionality planned to be decommissioned |
| 31 Dec 2036 | End for phrase management and dangerous-goods master data (Classic) |
The dates for SAP ECC
SAP has staggered maintenance for SAP ECC 6.0 (SAP Business Suite 7):
- Mainstream maintenance until 31 Dec 2027 — applies to enhancement packages EHP 6 to 8.
- Optional extended maintenance until 31 Dec 2030 — for a premium of two percentage points on the maintenance base.
- Customer-specific maintenance thereafter — without new support packages and without adjustments to new legal requirements.
For older releases (EHP 0 to 5), mainstream maintenance already ended at the end of 2025.
In addition, SAP offers the “SAP ERP, private edition, transition option”: a cloud subscription that lets you run ECC systems until the end of 2033. It requires a move to SAP ERP, private edition — and it is explicitly not an extension of on-premise maintenance.
Important: end of maintenance does not mean end of use. Your ECC system keeps running after 2027. What stops is the ongoing supply of corrections — and for Product Compliance that weighs particularly heavily, because regulations, safety data sheet requirements and dangerous-goods rules change constantly.
Classic on S/4HANA: still usable, but with an end date
The classic solution — specification database, safety data sheets with WWI and SDS distribution, dangerous goods, Substance Volume Tracking, Global Label Management — also runs on S/4HANA and can be carried over in a conversion.
Since S/4HANA 2025, however, there is a clear roadmap (SAP Note 3656482):
- SAP has marked all Classic functionality for Product Compliance as “deprecated” with S/4HANA 2025.
- In releases 2025, 2027 and 2029 it remains usable without restriction.
- With S/4HANA 2031, the Classic functions are planned to be decommissioned.
- Exception: phrase management and maintenance of dangerous-goods master data remain available until 31 Dec 2036 — regardless of release.
SAP recommends switching to the new functionality at the latest before upgrading to S/4HANA 2031. If you convert from ECC to S/4HANA today and carry the Classic Scenario over, you are choosing a path with a foreseeable end — but one that still holds for several years.
A second point to clarify early: licensing. Using the Classic functions in S/4HANA is not automatically covered by your S/4HANA licence. Check with SAP or your licensing advisor on what basis you will run the solution after the conversion.
What the conversion actually involves
Product Compliance is rarely the largest work package in an S/4HANA conversion — but it is one with many dependencies. Typical points:
- Check simplification items — which entries in the Simplification List affect your Product Compliance processes? The SAP Readiness Check gives you a first overview.
- Review custom development — user exits, BAdIs and custom programs need to be checked against S/4HANA and adjusted where necessary.
- WWI templates and servers — test report generation, Expert and WWI servers, and the generation of safety data sheets and labels end to end.
- SDS distribution — check that shipping orders, recipients and output channels work as usual after the conversion.
- Logistics integration — if the conversion also changes processes in SD, EWM or TM, the integration point for the dangerous-goods check changes with them.
- Regulatory content — secure content packages (e.g. from Verisk 3E) and their update cycle in the new system.
Classic or New Scenario?
With the roadmap for Classic, the question of the New Scenario — positioned by SAP as “SAP S/4HANA for product compliance” with new functionality — becomes more pressing. The new solution is Fiori-based, has its own data model and has been expanded step by step since S/4HANA 1809.
There is no one-size-fits-all answer. What matters is whether the new functionality already covers your requirements today, how much custom development is in your Classic solution — and when a switch fits into your release planning. You can find more on the differences in our comparison of the scenarios and in the glossary.
Our core territory is the Classic Scenario on ECC and S/4HANA. For the New Scenario, we help you assess whether and when a switch pays off for you.
Five questions before you switch
- Which enhancement package is your ECC on — and which maintenance applies to you as a result?
- Which Classic functions do you use in production: safety data sheets, dangerous goods, SVT, labels?
- How much custom development is in your solution — user exits, BAdIs, WWI templates?
- On what licence basis will you run Classic after the conversion — and up to which S/4HANA release are you planning with it?
- Does the new functionality already cover your requirements — and when would be the right time to switch?
If you would like to go through these questions for your landscape: in a free 30-minute initial conversation with a senior consultant, we give you a first assessment.
As of October 2026. This article provides a general overview and does not replace licensing or contract advice. The current SAP notes (including SAP Notes 3656482 and 3015382), SAP’s maintenance strategy and your individual contracts are authoritative.