2 minute read
Meet the Authors
Key Takeaways
What you need to know
SAP's reselling and support agreements for third-party databases and Java are scheduled to end when extended maintenance for SAP Business Suite 7 closes on December 31, 2030.
Customers running SAP Process Integration and SAP Process Orchestration face the same Java cutoff because those products run on SAP NetWeaver Application Server Java 7.5.
Conversion tooling for SAP Business Suite 7 systems on third-party databases ends with those agreements, leaving new implementations as the supported route to SAP Cloud ERP.
SAP’s reselling and support agreements with major third-party database providers for legacy environments, and its support arrangements for Java, are scheduled to end when extended maintenance for SAP Business Suite 7 closes on December 31, 2030.
The expiry affects systems that run on third-party databases and systems that use SAP NetWeaver Application Server Java 7.5 (SAP NetWeaver AS Java 7.5), including SAP Process Integration (PI) and SAP Process Orchestration (PO).
What Ends When Extended Maintenance Closes
SAP CTO Philipp Herzig confirmed October 7 that the maintenance dates announced in 2020 have not changed: mainstream maintenance for SAP Business Suite 7 runs through December 31, 2027, followed by optional extended maintenance through December 31, 2030.
Explore related questions
Ask SAPi
Today, SAP handles a customer’s third-party database ticket end to end, routing it directly to the database vendor’s team. That path ends with the agreements. SAP will no longer provide database-specific support for these databases in the affected legacy environments, including for customers that originally licensed their database through SAP and enrolled in SAP Maintenance and Support.
At the end of 2030, SAP’s support arrangements for Java used with SAP NetWeaver AS Java 7.5 conclude, and the server with its add-ons enters customer-specific maintenance in 2031 without a follow-on release.
PI and PO run on that server, SAP’s guidance for those customers notes, so the Java limit applies even to companies that have already left SAP Business Suite 7. Maintenance for SAP Process Orchestration, Private Cloud Edition, ends December 31, 2030.
Customer-Specific Maintenance and Conversion After 2030
On-premises SAP Business Suite 7 systems run under customer-specific maintenance after extended maintenance, which SAP restricts further for third-party database and Java environments.
SAP will not provide comprehensive support for issues involving those technologies, including kernel patches and kernel security patches for third-party databases, and may stop offering downloads of database administration, backup, upgrade, and migration tooling. Customer-specific maintenance is not a sustainable long-term model for business-critical systems on these technologies, SAP advises.
Tooling to convert SAP Business Suite 7 on a third-party database to SAP S/4HANA or SAP Cloud ERP is available only before the agreements end. Afterward, SAP supports only greenfield transitions, meaning new implementations.
SAP Points Customers Toward SAP Cloud ERP
SAP recommends that customers plan to complete their transformation to SAP Cloud ERP by the end of 2030. The Transition Option for SAP ERP is a time-bound subscription intended for the largest and most complex SAP Business Suite 7 customers.
Herzig’s post describes the option as supporting business continuity from 2031 through 2033. SAP’s transition option page, updated October 13, says subscriptions may run until December 31, 2035, with further prerequisites. Systems must move to SAP ERP, private edition on SAP HANA before extended maintenance ends, and Java-dependent capabilities are not supported.
Customers that stay on premises can remove the third-party database dependency by moving a system to SAP HANA before the agreements end. The move does not extend maintenance, and SAP does not recommend it as a long-term path.
Michael Bloch, a board member at the German-speaking SAP User Group, said in SAP’s post that any decision should rest on “a comprehensive assessment of all available alternatives and their respective long-term consequences.”
What This Means for SAPinsiders
The database becomes a support decision. The expiring agreements end SAP’s end-to-end handling of third-party database tickets, so the database beneath a system now sets how much support SAP can give. Moving to SAP HANA removes that dependency without extending maintenance.
Integration middleware carries its own clock. PI and PO run on SAP NetWeaver AS Java 7.5, so the Java limit follows integration landscapes even after the ERP core has moved. Those layers can remain on a platform SAP describes as having no follow-on release.
SAP treats cloud ERP as the supported destination. SAP calls customer-specific maintenance unsustainable for these business-critical systems and does not recommend staying on premises with SAP HANA as a long-term path. It describes SAP Cloud ERP as the route to a fully supported environment.
More Resources
See All Related Content
Accelerate and De-Risk SAP Migrations to the Cloud with Splunk and Amazon Web ServicesSplunk and AWS help organizations accelerate SAP cloud migrations while reducing operational, security, and performance risks through enhanced visibility and observability. The brief highlights how unified monitoring, predictive analytics, and SAP-certified cloud services support successful SAP S/4HANA transformations and long-term cloud optimization.
1 minute read
CyberTech’s Microsoft Solutions Partner Designation: Expertise For SAP And ArcGIS On AzureCyberTech, recognized as a Microsoft Solutions Partner, specializes in Azure modernization for SAP and ArcGIS Enterprise, emphasizing the importance of assessing application dependencies and implementing a structured migration approach to ensure minimal disruption and continuity of business-critical operations.
3 minute read