End of 2022 we launched ABAP Cloud and published the new ABAP extensibility guide. This guide is the best starting point for overview of ABAP Cloud development model and ABAP-based extensibility options for SAP S/4HANA in the cloud and on-premise. The last update of the extensibility guide took place in May 2023 where we incorporated the feedback of early adaptors of ABAP Cloud in real SAP S/4HANA systems.
A key concept for extensibility in S/4HANA Cloud Private Edition and on-premise outlined in the ABAP extensibility guide was the 3-tier extensibility model. This model described how ABAP Cloud and classic ABAP can co-exist within a single system: tier 1 contained ABAP Cloud on-stack extensions, as well as any developments with SAP Build on SAP BTP for side-by-side extensions. Tier 2 served to address gaps, providing mechanisms to mitigate necessary publicly released SAP APIs not yet available in tier 1. Finally, tier 3 encompassed classic ABAP extensions. Only tier 1 (and tier 2, when using recommended SAP objects) was considered as clean core. In contrast, tier 3 was classified as “not clean.” The ABAP test cockpit checks for ABAP Cloud readiness controlled the usage of classic ABAP in custom extensions.
The main objective of the clean core dimension Extensibility for SAP S/4HANA Cloud Private Edition and SAP S/4HANA on-premise deployments is decoupling of custom extensions from SAP standard via use of ABAP Cloud and reliable development and extension technologies to reach upgrade stability. On the way to clean core, dealing with the classic ABAP custom code represents a challenge for SAP customers and partners. Multiple customer and partner interactions showed that the binary classification of custom code in the 3-tier extensibility model in “clean core” and “not clean core” and governance based on ABAP test cockpit checks for ABAP Cloud readiness were too restrictive and not applicable for systems with a lot of existing custom code developed with classic ABAP. Besides this there are also new custom extensions which need to be implemented with classic ABAP because for example the related SAP application area is not sufficiently covered by publicly released SAP APIs or is implemented with SAP GUI based technologies and frameworks. On the other hand, many of underlying SAP classic ABAP technologies, like ABAP List Viewer for example, incorporate an implementation stability which most likely will bring minimum upgrade risks and can be still utilized in classic ABAP developments.
The new Clean core extensibility white paper introduced by SAP incorporates evolution of the current 3-tier extensibility model with binary decisions on clean core to more detailed assessment of classic ABAP extensions based on the clean core level concept, allowing you as SAP customers and partners stepwise transformation to clean core at your own pace.
In a nutshell:
Level A are the cleanest custom extensions built either on-stack with ABAP Cloud development model or side-by-side using any option of SAP Build on SAP BTP – ABAP Cloud, CAP or low-code/no-code tools
Levels B-D relate to all classic ABAP developments and can be reached as follows:
Level B can be achieved by custom extensions that comply with SAP recommendations for the use of classic ABAP development technologies and the frameworks offered as classic SAP APIsLevel C contains custom extensions which cannot be qualified for Level B because of usage of arbitrary SAP internal objects. Under the condition that dedicated checks are performed before the release upgrade (following the changelog for SAP objects approach), these custom extensions can be considered conditionally clean.Level D is not clean core and includes custom extensions with severe violations of SAP development recommendations like modifications, usage of not recommended SAP objects or extension technologies (e.g. implicit enhancements).
Following the new clean core extensibility guidance we have updated the ABAP extensibility guide with technical guidelines which are in line and support the clean core level concept for the classification of custom extensions.
Summary of technical ABAP extensibility guidelines for clean core
How the ABAP test cockpit (ATC) supports clean core level concept
Main updates for transformation of 3-tier extensibility model to clean core extensibility based on clean core level concept (see the activity log on page 1 of the ABAP extensibility guide for details):
Change technical guidelines for extensibility from 3-tier model to ABAP Cloud development and classic ABAP developmentExplain classic SAP APIs and their matching to clean core levelsProvide ABAP test cockpit (ATC) recommendations for governance of classic ABAP development for clean coreExplain relation of custom code use cases to clean core levelsDescribe changelog for SAP objects approach for assessment of upgrade stability of custom code using SAP internal objectsChange transformation options for existing custom code from 3-tier extensibility model to ABAP Cloud and classic ABAP developments
Supporting the clean core extensibility and clean core level concept with these technical guidelines for ABAP extensibility is a next significant step forward to support your clean core transformation at your own speed.
If you have already set up the 3-tier extensibility model and are following clean core development practices, you might be wondering if the new guidance changes everything. Good news — you are already on the right track! The new clean core level concept simply provides enhanced guidance for everything you developed in tier 3 with classic ABAP.
If you now want to learn more about the refined clean core extensibility guidance and clean core levels, read the Clean core extensibility whitepaper.
For more information about ABAP Cloud and recommendations for classic ABAP developments, classic APIs, ABAP test cockpit setup and behavior for governance of clean core development supporting the clean core levels switch directly to the updated ABAP extensibility guide.
In addition, you can also use the updated ABAP Cloud – Extensibility slide deck . To get your questions answered use the ABAP Cloud FAQ and the ABAP Development community.
We will continue our ABAP Cloud and clean core collaboration with customers and partners and will share the new learnings and provide new updates. After this update related to the adaption of the new clean core extensibility model the next major update of the ABAP extensibility guide planned for Q4/2025 will focus on enhancements in ABAP custom code management tools and ABAP AI capabilities. Stay tuned!
End of 2022 we launched ABAP Cloud and published the new ABAP extensibility guide. This guide is the best starting point for overview of ABAP Cloud development model and ABAP-based extensibility options for SAP S/4HANA in the cloud and on-premise. The last update of the extensibility guide took place in May 2023 where we incorporated the feedback of early adaptors of ABAP Cloud in real SAP S/4HANA systems.A key concept for extensibility in S/4HANA Cloud Private Edition and on-premise outlined in the ABAP extensibility guide was the 3-tier extensibility model. This model described how ABAP Cloud and classic ABAP can co-exist within a single system: tier 1 contained ABAP Cloud on-stack extensions, as well as any developments with SAP Build on SAP BTP for side-by-side extensions. Tier 2 served to address gaps, providing mechanisms to mitigate necessary publicly released SAP APIs not yet available in tier 1. Finally, tier 3 encompassed classic ABAP extensions. Only tier 1 (and tier 2, when using recommended SAP objects) was considered as clean core. In contrast, tier 3 was classified as “not clean.” The ABAP test cockpit checks for ABAP Cloud readiness controlled the usage of classic ABAP in custom extensions.The main objective of the clean core dimension Extensibility for SAP S/4HANA Cloud Private Edition and SAP S/4HANA on-premise deployments is decoupling of custom extensions from SAP standard via use of ABAP Cloud and reliable development and extension technologies to reach upgrade stability. On the way to clean core, dealing with the classic ABAP custom code represents a challenge for SAP customers and partners. Multiple customer and partner interactions showed that the binary classification of custom code in the 3-tier extensibility model in “clean core” and “not clean core” and governance based on ABAP test cockpit checks for ABAP Cloud readiness were too restrictive and not applicable for systems with a lot of existing custom code developed with classic ABAP. Besides this there are also new custom extensions which need to be implemented with classic ABAP because for example the related SAP application area is not sufficiently covered by publicly released SAP APIs or is implemented with SAP GUI based technologies and frameworks. On the other hand, many of underlying SAP classic ABAP technologies, like ABAP List Viewer for example, incorporate an implementation stability which most likely will bring minimum upgrade risks and can be still utilized in classic ABAP developments.The new Clean core extensibility white paper introduced by SAP incorporates evolution of the current 3-tier extensibility model with binary decisions on clean core to more detailed assessment of classic ABAP extensions based on the clean core level concept, allowing you as SAP customers and partners stepwise transformation to clean core at your own pace.In a nutshell:Level A are the cleanest custom extensions built either on-stack with ABAP Cloud development model or side-by-side using any option of SAP Build on SAP BTP – ABAP Cloud, CAP or low-code/no-code tools Levels B-D relate to all classic ABAP developments and can be reached as follows:Level B can be achieved by custom extensions that comply with SAP recommendations for the use of classic ABAP development technologies and the frameworks offered as classic SAP APIsLevel C contains custom extensions which cannot be qualified for Level B because of usage of arbitrary SAP internal objects. Under the condition that dedicated checks are performed before the release upgrade (following the changelog for SAP objects approach), these custom extensions can be considered conditionally clean.Level D is not clean core and includes custom extensions with severe violations of SAP development recommendations like modifications, usage of not recommended SAP objects or extension technologies (e.g. implicit enhancements).Following the new clean core extensibility guidance we have updated the ABAP extensibility guide with technical guidelines which are in line and support the clean core level concept for the classification of custom extensions.Summary of technical ABAP extensibility guidelines for clean coreHow the ABAP test cockpit (ATC) supports clean core level conceptMain updates for transformation of 3-tier extensibility model to clean core extensibility based on clean core level concept (see the activity log on page 1 of the ABAP extensibility guide for details):Change technical guidelines for extensibility from 3-tier model to ABAP Cloud development and classic ABAP developmentExplain classic SAP APIs and their matching to clean core levelsProvide ABAP test cockpit (ATC) recommendations for governance of classic ABAP development for clean coreExplain relation of custom code use cases to clean core levelsDescribe changelog for SAP objects approach for assessment of upgrade stability of custom code using SAP internal objectsChange transformation options for existing custom code from 3-tier extensibility model to ABAP Cloud and classic ABAP developmentsSupporting the clean core extensibility and clean core level concept with these technical guidelines for ABAP extensibility is a next significant step forward to support your clean core transformation at your own speed.If you have already set up the 3-tier extensibility model and are following clean core development practices, you might be wondering if the new guidance changes everything. Good news — you are already on the right track! The new clean core level concept simply provides enhanced guidance for everything you developed in tier 3 with classic ABAP.If you now want to learn more about the refined clean core extensibility guidance and clean core levels, read the Clean core extensibility whitepaper.For more information about ABAP Cloud and recommendations for classic ABAP developments, classic APIs, ABAP test cockpit setup and behavior for governance of clean core development supporting the clean core levels switch directly to the updated ABAP extensibility guide.In addition, you can also use the updated ABAP Cloud – Extensibility slide deck . To get your questions answered use the ABAP Cloud FAQ and the ABAP Development community.We will continue our ABAP Cloud and clean core collaboration with customers and partners and will share the new learnings and provide new updates. After this update related to the adaption of the new clean core extensibility model the next major update of the ABAP extensibility guide planned for Q4/2025 will focus on enhancements in ABAP custom code management tools and ABAP AI capabilities. Stay tuned! Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
