SAP Note 3832186: what happens to ECC on Oracle, DB2 or SQL Server from 2031

The full timeline

What SAP stops providing from 2031

The note details the limitations for any Business Suite 7 or NetWeaver system on a third-party database that enters CSM. In summary:

• Kernel and security. No kernel patches, functional or security.
• Database. SAP will not certify new versions or support performance or functional issues, even on already validated versions.
• Lifecycle tooling. No support for SUM, SWPM, R3load, R3trans or tp on these systems, and the third-party database versions will be removed from the SAP marketplace.
• Upgrades and system copies. SAP will not support upgrades or system copies.
• Migration. No supported migration paths from the third-party database to another database or to S/4HANA.
• Infrastructure changes. No support for database updates or operating system or hardware changes.
• Monitoring and backups. No support for database-specific parts of DBA Cockpit or Host Agent, or for tools such as BR Tools.

One point is easy to miss. According to the note, secondary database connections from an SAP ABAP server to a third-party database are no longer supported either, even when the system's primary database is already an SAP database. It is worth checking whether any interface relies on a connection like that.

Why it is a security issue

Without kernel or database patches, a system in this situation has no SAP-supported way to fix new vulnerabilities, and the note makes clear that the exposure falls on the customer. To put it in perspective, think of OVERPASS, the CVSS 10 kernel flaw SAP fixed in September 2026. From 2031, a system on a third-party database would not receive a patch like that.

The options SAP lays out

The note recommends starting to plan immediately, while systems are still under mainstream or extended maintenance, and lays out three paths:

• SAP Cloud ERP. The route SAP proposes for those who want to keep innovating, with the transformation finished before the end of 2030. For most mid-sized and large companies, that means S/4HANA within RISE with SAP.
• Transition option for SAP ERP. A time-bound subscription for the largest and most complex customers already in transformation who need more time. It is detailed in note 3591251.
• Switch to SAP HANA. Those who want to stay on Business Suite 7 on-premise can remove the third-party database dependency by moving to HANA before the end of 2030. This does not extend mainstream or extended maintenance.

What to do now

Take a full inventory. The review goes beyond ECC, because the note applies to any NetWeaver ABAP or Java system on a third-party database, so it is worth checking BW, PI/PO, Portal, Solution Manager and any other satellite system too.

Check secondary connections. Identify the interfaces that connect from an ABAP system to Oracle, DB2 or SQL Server as a secondary database, even if the main system already runs on HANA.

Do not leave the migration for 2030. The tools that make migration possible, such as SUM, SWPM and R3load, are only supported while the system is under mainstream or extended maintenance. Planning early lets you rehearse the migration several times before cutover, something that is no longer possible if it is left for the end.

If your company already runs S/4HANA on RISE with SAP, your main system runs on HANA and the core of this note does not affect you. Even so, it is worth reviewing secondary connections and any satellite systems that have not moved yet.

Sources

• SAP Note 3832186, Third-Party Database Maintenance: limitations in Customer Specific Maintenance after 2030. Requires an SAP for Me user.
• SAP Community, Planning Beyond 2030: What Customers Using Third-Party Databases Need to Know.
• SAP Note 3591251, Transition Option for SAP ERP.
• SAP Note 2881788, end of SAP Business Suite 7 mainstream maintenance.
• SAP Note 1648480, maintenance for SAP Business Suite 7 and SAP NetWeaver.