Moving SAP Targets
SAP modifications for legacy systems
Many SAP customers have adapted the ERP systems R/3 and ERP/ECC 6.0 with Abap modifications. In some instances, these ERP enhancements were implemented not only in the designated area, but also in the ERP core.
SAP has always been an open system, and the company places great importance on constructive cooperation with users and innovative further developments. From the outset, SAP had the requisite IT tools to design the ERP system according to user requirements. On occasion, the modifications gained a momentum of their own, ultimately rendering the ERP system unfit for release.
SAP clean core or frozen core
Under the direction of SAP Chief Technology Officer Jürgen Müller, who is departing from the company, the idea was born: return to the standard! The objective is to develop an ERP system that is as close to the standard as possible, allowing for quick and easy implementation of future release upgrades and system extensions.
However, the concept of a standardized ERP system has yet to be formally defined from a scientific perspective. At times, it was referred to as "ERP Frozen Core," then "S/4 Clean Core," and there were even suggestions that specific functions could be modified in close proximity to the ERP core.
SAP has a clear vision for the future of its S4 Hana system. The goal is to have a clean core that will remain stable and maintainable until 2040. Additionally, a Business Technology Platform will be introduced, providing an IT ERP platform for modifications including Steampunk, CAP, and RAP.
A binding definition of what the clean core is and a roadmap for future S/4 modifications, including a corresponding PKL (price and conditions list), are currently lacking. Jürgen Müller's successor will have to address numerous legacy issues, including the Abap modifications from the R/3 era and the "frozen and clean core" vision, which lacks a scientific definition and roadmap.
SAP BTP lifeline
Going forward, SAP customers will still be required to adapt the ERP system S/4. The Abap modification tool will remain in use, and new development tools and methods will be added, including CAP (Cloud Application Programming) and RAP (RESTful Application Programming).
This year, E3 magazine held a successful summit on the subject of Steampunk and BTP. The event will be held again in 2025 on March 5 and 6, in Heidelberg, Germany. The summit will address the full range of possibilities and options for (embedded) Abap, CAP, RAP, and SAP BTP, the new ERP platform. Analysts, experts, and SAP partners will present numerous insights into the world of SAP modifications.
The Steampunk and BTP Summit 2025 should provide further clarity about SAP's goals, as the BTP platform is still undergoing a metamorphosis. Many good ideas do not yet make an IT ERP platform. Together with the clean core, BTP is still a moving target at SAP.
DE
EN
ES
2 comments
Werner Dähn
Sehe ich nicht so.
Clean Core heißt nicht zurück zum Standard, sondern “man verwendet nur public APIs”, also nur SAP ABAP Funktionsbausteine, die freigegeben sind.
Anfänglich wollte man nur sehr wenig Erweiterungen im ABAP eines ERP erlauben und stattdessen ein Sidecar haben, also CAP in BTP. Aber weder ist das sinnvoll noch bietet es die gewünschten Funktionalitäten wie z.B. etwas in der gleichen LUW zu machen.
Erst sehr viel später kam die Developer Extensibility hinzu, mit der man eigene Erweiterungen im ABAP Stack und Upgrade-Sicher hinzufügen konnte.
https://help.sap.com/docs/SAP_S4HANA_CLOUD/6aa39f1ac05441e5a23f484f31e477e7/e1059ff581854a699f15734049f14293.html
Und natürlich die Key User Extensibility geht noch immer.
https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/3ccb50e724b045508fea8b2cf1774b2b.html
Zusammengefasst:
– Es ist sehr genau definiert, was clean core bedeutet
– Erweiterungen in ABAP sind (inzwischen wieder) möglich
– CAP ist nutzlos
– BTP Steampunk ist eine nette Sache, wenn man keinen eigenen ABAP server laufen lassen möchte. Also nur bei S/4 Cloud
E3-Magazin
Vielen Dank für die ergänzende Aufklärung und Präzision. Die Sache mit den „Public APIs“ war mir in dieser Weise nicht klar. Wieder etwas gelernt – und ich werde wahrscheinlich auch in Zukunft daneben greifen: Bitte weiterhin genau lesen und korrigieren. DANKE!