Product Information
Maintenance Timelines for SAP ERP 6.0
This blog is meant to refresh your memory on the SAP ERP 6.0 maintenance timelines that SAP communicated back in 2020, explain how to find out your release and enhancement package level, and highlight your options to stay in maintenance.
When will maintenance end?
As described in the SAP Release and Maintenance Strategy (login required) and more detailed in SAP Note 2881788 (login required) and the Product Availability Matrix (PAM) mainstream maintenance for the latest three enhancement packages for SAP ERP 6.0 – namely enhancement packages 6, 7 and 8 – runs until December 31, 2027, followed by an optional extended maintenance phase until December 31, 2030.
However, mainstream maintenance for SAP ERP 6.0 without enhancement package, as well as SAP ERP 6.0 with enhancement packages 1 to 5, will end on December 31, 2025.
How can you find your release and enhancement package level?
The easiest way to find out is to log on to your system and open the system status:
Open the product version details:
Look for the entry SAP_APPL and the release number next to it:
For any SAP ERP 6.0 system the first digit will be 6. The second digit is not relevant here, and the third digit corresponds to your enhancement package level. For example, 616 means that the system is on SAP ERP 6.0 with enhancement package 6.
What are your options to stay in maintenance?
Keep in mind that any transition project can take months or even years, so now is the perfect time to plan your path forward, in particular if you are running a system with end of mainstream maintenance in 2025.
With SAP’s maintenance commitment until 2040 and by now more than 20,000 customers, SAP S/4HANA is the natural destination for your technical transition. Many organizations combine this transition with a move to the cloud, hence opting for RISE with SAP. Please reach out to your SAP account executive or SAP partner to discuss your options.
Regardless of the commercial dimension, we strongly recommend that you start off with the SAP Readiness Check. Included at no extra cost with your maintenance agreement, it provides a comprehensive overview of the most important aspects for a transition to SAP S/4HANA. While primarily targeted for customers considering a system conversion, i.e. a technical transition of an entire SAP ERP system to SAP S/4HANA, it also gives good insights for customers planning a new implementation.
Please let me know your thoughts and feedback in a comment. Also check out other SAP S/4HANA blogs for further information.
Good insight. Your blog was very helpful. What kind of support can we expect as part of extended support? Does SAP help with bugfixes to standard code? Can we enable new functionalities when we are on extended support?
Hi Sami,
Thanks for your feedback. The scope of support for the extended maintenance period is similar to the scope of support provided during mainstream maintenance. Further details can be found here.
Regards
Arne
Thanks Arne.
These dates apply also to Industry Solutions as part of SAP ERP 6.0? If not, where can I find the end of support info for ERP IS-Retail?
These dates also apply to IS-Retail as this is part of SAP ERP. Generally, you can check maintenance timelines in the Product Availability Matrix (PAM).
Thank you very much, Arne.
Thank you for the informative post, Arne.
The general feeling from some ECC customers is SAP is forcing them to move to RISE even though SAP S/4HANA (On-Premise) has still been an option. While some customers are hesitant to move to the cloud, they are eager to upgrade their ECC systems to S/4HANA and work with hyperscalers (bring your own license model).
It would be great if you write a blog addressed to these customers to give them the tranquility that is also an option, and they can move to RISE or the Public Cloud at a later moment.