Clean core approach for SAP ABAP S4HANA developers. Let's understand the meaning of clean core with example.
In S4HANA cloud, sap recommends clean core approach. What is actually meant by clean core? How clean core is achieved? How clean core is connected with SAP BTP?
Let's understand the meaning of clean core
We as a consultant usually map customer business requirement in SAP by using enhancement options or hooks given by SAP like user exit, customer exit and enhancement (Implicit/explicit) and BADIs. Earlier these options were used to meet business custom requirements.
In latest SAP S4HANA cloud version, SAP has provided extensibility (enhancement) approaches which are useful to meet customer needs. This extensibility approach revolves around clean core strategy. Let me explain how clean core strategy works.
Custom developments are performed on a separate layer (BTP – Business Technology Platform) which is connected with core sap system via. APIs. This ensures sap core software is not disturbed while also meeting customer requirements. If anything goes wrong with custom development, then simply detach the custom development by removing API connection between sap core and BTP.
SAP recommended Level Based Clean Core Approach where one achieves extensibility based on certain levels.
SAP has categorized clean core into below four levels: Level A: Clean Extension based on Released APIs Level B: Use of Classic APIs Level C: Use of Internal Objects Level D: Not Clean Core
Below example will help you understand sap clean core approach
Imagine you rented a house for one year. You are living in the house but you can not drill into walls, can not change floor layout of house, can not remove any wall and can not create any new wall. You are user of the house but can not temper the house as per your need. You will have to meet your requirements by using some arrangements without tempering the house. You are keeping the house clean core.
Similarly in sap, no tempering core of software. Any customization needed can be achieved through development in BTP layer. Customization will connect with core via. API (Application Programming Interface) provided by sap. If any any point of time, there is need to remove customization then simple switch of the API.
SAP released APIs and Public extension points
SAP recommends using only Released APIs and Public Extension Points to meet business requirements.
Do not change SAP standard code
Use only the options that SAP officially allows
This keeps the system safe during upgrades and reduces errors
Build custom solutions outside the core SAP system
Use SAP BTP (Business Technology Platform) for development
Connect SAP BTP with SAP S/4HANA using standard APIs
Conclusion
Be it technical consultant or a functional consultant, understanding clean core strategy is important. In any sap transformation project or fresh sap implementation project, clean core strategy is very important. SAP reviews the approach for custom developments and if clean core strategy is not followed then sap put strong remarks in project review meeting. This reflects bad on sap implementation team.
Clean Core Approach completely comes under Level A where without touching core system we are achieving the High Degree of cleanness in our development which are upgrade safe and future ready.
