I am pleased to announce the availability of the SAP Application Extension Methodology version 2.4. In this blog post, I would like to provide a quick overview and highlight the changes in this newest release.
For a quick introduction to the methodology, please take a look here: SAP Application Extension Methodology.
This blog post is part of the series SAP BTP Guidance Framework: A Compass for Architects, Developers, and Administrators.
The SAP BTP Guidance Framework is a practical framework tailored to anyone using the SAP Business Technology Platform. SAP BTP acts as the technological backbone for building, integrating, extending, and innovating with SAP solutions. Whether you're an enterprise architect, software developer, or administrator, SAP BTP offers significant opportunities for productivity and development.
What’s New for SAP Application Extension Methodology
With the SAP Application Extension Methodology version 2.4, we have made some changes to the Extension Technology Mapping. We now include the Clean Core Level concept directly in the Mapping, allowing you to easily follow the latest guidance. Next to each Technical Extension Building Block, you can find the corresponding Clean Core Level (A-D).
Please be aware that the single source of truth for the Clean Core Levels is the official SAP Note 3578329.
If you are still using an older version of the Technology Mapping, I highly recommend checking out our new version and to learn about the latest innovations and technologies on SAP S/4HANA and SAP Business Technology Platform.
Clean Core Level Concept in a Nutshell
TL;DR
- Always develop your extension with the highest clean core level.
- Leverage released APIs and best practice classic APIs of Level A and B to be clean core compliant.
- Avoid not recommended SAP objects of Level D as they are not clean core compliant.
Level A
Level A is considered clean core and your strategic direction. You develop extension with SAP Build either on-stack on SAP S/4HANA and/or Side-by-Side on SAP BTP. Usually, you use a combination of both. You will use ABAP Cloud, CAP and our low-code/no-code tools in SAP Build. You can find the released APIs and extensions points on the SAP Business Accelerator Hub.
Level B
Level B is considered clean core. You use upgrade stable classic APIs, which you can find in the cloudification repository viewer with filter state = classic API.
Level C
Level C is considered conditionally clean. Use the internal SAP objects only if needed. There is no guarantee on long-term stability. Apply the changelog for SAP objects to mitigate upgrade risks.
Level D
Level D is considered NOT clean core. Those objects are unfit for customer use. You can find them in the cloudification repository viewer with filter state = noAPI.
Next Steps:
Learn more about the SAP Application Extension Methodology on the SAP Help Portal.
Learn more about the SAP BTP Guidance Framework on the SAP Discovery Center and look out for the continuation of the blog post series. The next one will be about Data&Analytics.
Learn more about Clean Core by reading our detailed whitepaper, or tune into our latest Unlocking SAP BTP podcast episode focusing on clean core.
Feel free to like, comment and ask your questions!
Talk to you soon,
Marco
Product Manager SAP Business Technology Platform
Join me online: https://www.linkedin.com/in/marcomatha/
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.