---
title: The Clean Core for SAP BTP
description: Discover how SAP's clean core approach enhances cloud adoption by standardizing processes, ensuring extensibility, and improving operational efficiency for businesses.
image: https://blog.sap-press.com/hubfs/The%20Clean%20Core%20for%20SAP%20BTP.jpg
---

[![rheinwerk-sappress-logo-header-1](https://blog.sap-press.com/hubfs/rheinwerk-sappress-logo-header-1.svg)](https://blog.sap-press.com/) [Blog](https://blog.sap-press.com)

- Books 
    - Get an overview of our books and courses on every relevant SAP topic. 
          - [Programming](https://sap-press.com/programming/)
          - [Administration](https://sap-press.com/administration/)
          - [BI](https://sap-press.com/business-intelligence/)
          - [Finance](https://sap-press.com/finance-controlling/)
          - [Logistics](https://sap-press.com/logistics/)
          - [HR](https://sap-press.com/human-resources/)
          - [CRM & Sales](https://sap-press.com/marketing-sales/)
          - [HANA](https://sap-press.com/hana/)
          - [Introductions](https://sap-press.com/introductions/)
          - [E-Bites](https://sap-press.com/e-bites/)
          - [Certification Guides](https://www.sap-press.com/certification-guides/)
          - [Rheinwerk Courses](https://www.sap-press.com/online-courses/)
- Book Subscription 
    - Get unlimited access to all SAP PRESS books! 
          - [SAP PRESS Subscription](https://sap-press.com/subscriptions/)

[Programming](https://blog.sap-press.com/tag/programming)

# The Clean Core for SAP BTP

![SAP PRESS](https://blog.sap-press.com/hubfs/Twitter_profile_pic.svg)  by [SAP PRESS](https://blog.sap-press.com/author/sap-press) on November 20, 2026

While multiple technologies help achieve the promise of the cloud, enterprises need to adopt a cloud mindset to realize the full benefits.

 

While focusing on developing innovative cloud-native applications to differentiate themselves, they should adopt the concept of fit-to-standard as much as possible for their non-differentiating capabilities. Most enterprises' ERP landscapes are burdened by a huge amount of custom development, which restricts flexibility, hinders upgrades, and increases costs.

 

The clean core approach helps overcome these challenges through increased use of standards and the rapid adoption of industry best practices at minimal cost. It allows faster upgrades and faster innovation powered by high-quality data and AI. Loosely coupled to the standard core should be the cloud-native differentiating layer, both of which can evolve as required without impacting each other. Hence, the core can be upgraded faster, and the differentiating layer can be innovated and scaled up more quickly. SAP’s clean core principles ensure that all extensions made to the standard SAP solution are both upgrade proof and cloud ready.

 

This post covers the core concept of SAP’s clean core strategy for [SAP Business Technology Platform](https://learning.sap-press.com/sap-btp) (SAP BTP), the mechanism for implementing the strategy, and the benefits of adopting it.

 

## Concept

SAP’s clean core focus is underpinned by the following five guiding principles:

- **Business process**: Standardize processes to leverage industry best practices quickly and cost effectively
- **Extensibility**: Achieve differentiation by extending standard solutions in a loosely coupled way
- **Data**: Govern data and ensure compliance with the latest data standards
- **Integration**: Ensure flexibility by using reliable, modern integration techniques
- **Operations**: Improve operational efficiency through automation

All the principles are interlinked. Extensions to standard processes are made by enterprises to differentiate themselves from their competitors. These differentiations are expected to help enterprises achieve measurable goals. In order to reach these goals, extensions should work with high-quality data, be powered by automation, and supported by flexible integration capabilities. The extensibility principle is based on three fundamental rules, as follows:

1. Customer extensions should only use *released* SAP APIs, whether local or remote. SAP commits to keeping these APIs stable; thus the extension will not get adversely impacted by upgrades to the core.
2. *No modifications* to SAP standard objects should be made. Any extension to SAP objects can only be done through predefined extension points. SAP also commits to keeping the extension points stable.
3. Extensions should be done using *cloud-enabled* technologies and SAP’s cloud syntax.

By following these rules, as shown in the figure below, enterprises can ensure that their extensions are loosely coupled and future-proof (i.e., they will continue to work even if the core SAP solution gets upgraded) and that these extensions benefit from cloud-native characteristics.

 

*![Clean Core Concept and Rules](https://blog.sap-press.com/hs-fs/hubfs/image-png-Nov-09-2026-02-03-00-2751-PM.png?width=1233&height=376&name=image-png-Nov-09-2026-02-03-00-2751-PM.png)*

 

## Mechanism

Based on the concepts discussed in the previous section, every enterprise should try to build all their new extensions following clean core rules and convert their old extensions which don’t follow the rules. [SAP S/4HANA](https://learning.sap-press.com/sap-s4hana-overview-benefits) Cloud Private Edition, SAP S/4HANA Cloud Public Edition, and on-premise SAP S/4HANA offer two extensibility options:

- **On-stack**: This is used when tight coupling with the standard solution and the need to run in the same environment are required. This is used, for example, for extending the UI, data models, etc.
- **Side-by-side**: This is used when loosely coupled extensions running on a separate environment (SAP BTP) is feasible; for example, custom full stack applications, mobile applications, etc.

While side-by-side extensions on SAP BTP is the preferred option, as it provides maximum flexibility, in terms of upgrade impact and cloud-native capabilities, there are reasons why certain types of extensions are best done on-stack. This is why the clean core framework covers both types of extensions.

 

SAP has provided a number of tools, technologies, and frameworks to assess the clean core readiness of an enterprise’s custom extensions and to plan for the adoption of the clean core rules. SAP’s clean core extensibility framework (see figure below) allows you to assess your current extensions across four categories based on the impact of upgrades and the extent of cloud nativeness.

 

*![SAP’s Clean Core Extensibility Framework](https://blog.sap-press.com/hs-fs/hubfs/image-png-Nov-09-2026-02-03-30-2239-PM.png?width=1145&height=721&name=image-png-Nov-09-2026-02-03-30-2239-PM.png)*

 

Let’s look at each level in more detail:

### Level A

This is the highest level of extension and the most preferred. These extensions interact with SAP’s standard solutions through publicly released APIs and extension points. SAP ensures the stability of these APIs and extension points across versions. Hence these extensions are not impacted by upgrades. These extensions can either be:

- **Side-by-side**: Developed on SAP BTP [ABAP](https://learning.sap-press.com/abap) environment using SAP Build Code’s low-code environment or using the pro-code environment of [SAP Business Application Studio](https://blog.sap-press.com/what-is-sap-business-application-studio) with [SAP Cloud Application Programming Model](https://blog.sap-press.com/introducing-the-sap-cloud-application-programming-model-cap).
- **On-stack**: Developed in the core ERP on SAP S/4HANA Cloud ABAP environment using SAP Build tools using locally released APIs and extension points. While private cloud and on-premise customers can choose either ABAP Cloud or classic ABAP (also called standard ABAP) extensibility options, SAP S/4HANA Cloud Public Edition customers must choose ABAP Cloud extensibility.

Level A extensions are both upgrade safe and cloud native.

### Level B

These extensions leverage classic APIs published in the [Cloudification Repository](https://sap.github.io/abap-atc-cr-cv-s4hc/?states=classicAPI). SAP ensures that these APIs remain stable across versions so Level B extensions aren’t impacted by upgrades.

### Level C

These extensions use internal objects of SAP and, as such, are not guaranteed by SAP to be stable across versions and might even be withdrawn. These extensions are neither upgrade safe nor cloud ready. Given that a large number of enterprises have this type of extension, SAP has provided a change log for SAP objects to help organizations understand the changes that may have occurred to these objects, allowing them to update their extensions accordingly. These change logs are delivered through simplification database accessible through SAP Support Portal.

### Level D

These types of extensions are *not* recommended as they include modifications to standard SAP objects, the use of SAP objects SAP has called “unfit” (marked as “noAPI” in the Cloudification Repository), direct table writes, the use of implicit enhancement, etc.

 

These categories allow organizations to monitor and manage their enhancements, with the goal of having as many enhancements as possible at Level A or Level B. Check out SAP Note 3578329 for more information.

 

SAP provides RISE with SAP customers with dashboards (available in [SAP Cloud ALM](https://blog.sap-press.com/what-are-the-differences-between-sap-cloud-alm-and-sap-solution-manager)) that measure the following KPIs related to the clean core, enabling customers to monitor and govern their progress toward an improved clean core state:

- **Clean core share**: How many of their custom developments fall in which clean core level
- **Technical debt score**: Identifies objects using obsolete or soon to be obsolete technologies
- **Unused code share**: How many custom developments are not used
- **Business modifications**: Number of this type of modification which has upgrade risk

In the [RISE with SAP](https://blog.sap-press.com/what-is-rise-with-sap) methodology, SAP has recommended the “get clean” and “stay clean” approaches so that enterprises can convert their existing classical development to the clean core way and ensure that they do not introduce new non-clean core developments over time.

 

## Benefits

While the benefits of moving to clean core extensibility are clear in terms of upgrade readiness and cloud readiness, the fact that many organizations have not attained the perfect clean core state yet points to the trade-offs they face.

 

While IT teams want to move to clean core for the “technical” benefits, enterprises often struggle to find a business justification for the change. The effort, cost, potential disruption, and required change management often do not clearly justify the transition. Hence, enterprises most often follow this path:

1. Ensuring that anything new that they develop is built in a clean core way so as not to increase the technical debt.
2. If they touch an existing classical development due to a business need, they will apply clean core principles and make the new version clean core compliant
3. Migrate those classical developments which, if migrated, provide business benefits such as enabling adoption of AI, automation, scale, usability transformation, process transformation, or improved data.

A combination of these paths ensures slow but steady progress toward a clean core. However, enterprises also need a clear vision of the benefits they aim to achieve by adopting a clean core. While clean core drives the dual benefits of upgrade readiness and cloud-native capabilities, some enterprises may have an upgrade event approaching. Hence, they may want to accelerate the transition to a clean core, as otherwise their upgrade event will be effort, time, and cost intensive. Given the nature of business processes, some enterprises may benefit more from cloud-native properties than others, as needs such as scaling, seasonality, the nature and intensity of customer interaction, transitioning to mobility platforms, and adopting off-the-shelf AI capabilities may vary. Accordingly, enterprises can define the speed and drivers of clean core migrations.

 

Editor’s note: This post has been adapted from a section of the book [*Application Development with SAP Business Technology Platform*](https://www.sap-press.com/application-development-with-sap-business-technology-platform_6322/?utm_source=sappressblog&utm_medium=referral&utm_campaign=Blogs&utm_term=2855_chapter3&utm_content=2855) by [Govind Bajaj](http://www.linkedin.com/in/govind-bajaj-a5a7589.), [Arup Bhattacharya](https://www.linkedin.com/in/arup-bhattacharya-22000442/), [Laboni Bhowmik](https://www.linkedin.com/in/laboni-bhowmik-4a14387/), [Avijit Dhar](https://www.linkedin.com/in/avijit-dhar-8444859/), [Anup Ghosh](http://www.linkedin.com/in/anupkghosh), [Gairik Acharya](https://www.linkedin.com/in/gairik-acharya/), and [Asidhara Lahiri](http://linkedin.com/in/asidharalahiri). These authors bring more than 120 years of combined IT experience, most of it with SAP solutions, in roles ranging from senior technical architect and distinguished engineer at IBM to managing director of an SAP practice at Accenture. Their expertise covers SAP BTP, SAP S/4HANA, ABAP, SAP Fiori and SAPUI5, integration, data and analytics, IoT, and machine learning, built through large-scale global implementations in manufacturing, consumer products, oil and gas, airlines, and utilities. Among them are patent holders, frequent SAP TechEd and SAP Sapphire speakers, and several returning SAP PRESS authors.

## Recommendation

[![Application Development with SAP Business Technology Platform](https://blog.sap-press.com/hs-fs/hubfs/2855.jpg?width=170&name=2855.jpg)](https://www.sap-press.com/application-development-with-sap-business-technology-platform_6322/?utm_source=sappressblog&utm_medium=referral&utm_campaign=Blogs&utm_term=2855_chapter3&utm_content=2855)

**Application Development with SAP Business Technology Platform**

Create customized cloud applications! Master the basics of SAP Business Technology Platform (SAP BTP) and its development environments. Then get step-by-step instructions for developing your frontend and backend using Java, Node.js, Python, or ABAP and tools like SAP Business Application Studio, SAP Joule for Developers, and more. With detailed code examples throughout, this book is your complete guide to building cloud applications on SAP BTP!

[Learn More](https://www.sap-press.com/application-development-with-sap-business-technology-platform_6322/?utm_source=sappressblog&utm_medium=referral&utm_campaign=Blogs&utm_term=2855_chapter3&utm_content=2855)

![SAP PRESS](https://blog.sap-press.com/hubfs/Twitter_profile_pic.svg)

**by [SAP PRESS](https://blog.sap-press.com/author/sap-press)**

SAP PRESS is the world's leading SAP publisher, with books on ABAP, SAP S/4HANA, SAP IBP, intelligent technologies, SAP Business Technology Platform, and more!

[Programming](https://blog.sap-press.com/tag/programming) [Administration](https://blog.sap-press.com/tag/administration) [Featured](https://blog.sap-press.com/tag/featured)

[![Share on facebook](https://7528309.fs1.hubspotusercontent-na1.net/hub/7528309/hubfs/raw_assets/public/mV0_d-web-default-modules_hubspot/img/facebook-color.png?width=24&name=facebook-color.png)](https://www.facebook.com/share.php?u=https%3A%2F%2Fblog.sap-press.com%2Fthe-clean-core-for-sap-btp%3Futm_medium%3Dsocial%26utm_source%3Dfacebook) [![Share on linkedin](https://7528302.fs1.hubspotusercontent-na1.net/hub/7528302/hubfs/raw_assets/public/mV0_d-web-default-modules_hubspot/img/linkedin-color.png?width=24&name=linkedin-color.png)](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fblog.sap-press.com%2Fthe-clean-core-for-sap-btp%3Futm_medium%3Dsocial%26utm_source%3Dlinkedin) [![Share on twitter](https://7528304.fs1.hubspotusercontent-na1.net/hub/7528304/hubfs/raw_assets/public/mV0_d-web-default-modules_hubspot/img/twitter-color.png?width=24&name=twitter-color.png)](https://twitter.com/intent/tweet?original_referer=https%3A%2F%2Fblog.sap-press.com%2Fthe-clean-core-for-sap-btp%3Futm_medium%3Dsocial%26utm_source%3Dtwitter&url=https%3A%2F%2Fblog.sap-press.com%2Fthe-clean-core-for-sap-btp%3Futm_medium%3Dsocial%26utm_source%3Dtwitter&source=tweetbutton&text=) [![Share on email](https://7528311.fs1.hubspotusercontent-na1.net/hub/7528311/hubfs/raw_assets/public/mV0_d-web-default-modules_hubspot/img/email-color.png?width=24&name=email-color.png)](mailto:?subject=Check+out+https%3A%2F%2Fblog.sap-press.com%2Fthe-clean-core-for-sap-btp%3Futm_medium%3Dsocial%26utm_source%3Demail&body=Check+out+https%3A%2F%2Fblog.sap-press.com%2Fthe-clean-core-for-sap-btp%3Futm_medium%3Dsocial%26utm_source%3Demail)

### Comments

### Latest Blog Posts

[![SAP’s DevOps Portfolio](https://blog.sap-press.com/hs-fs/hubfs/SAP%E2%80%99s%20DevOps%20Portfolio.png?height=600&name=SAP%E2%80%99s%20DevOps%20Portfolio.png)](https://blog.sap-press.com/saps-devops-portfolio)

[Programming](https://blog.sap-press.com/tag/programming)

## [SAP’s DevOps Portfolio](https://blog.sap-press.com/saps-devops-portfolio)

[Read More](https://blog.sap-press.com/saps-devops-portfolio)

[![How Does VS Code Compare to Traditional SAP Development Environments?](https://blog.sap-press.com/hs-fs/hubfs/How%20Does%20VS%20Code%20Compare%20to%20Traditional%20SAP%20Development%20Environments.png?height=600&name=How%20Does%20VS%20Code%20Compare%20to%20Traditional%20SAP%20Development%20Environments.png)](https://blog.sap-press.com/how-does-vs-code-compare-to-traditional-sap-development-environments)

[Programming](https://blog.sap-press.com/tag/programming)

## [How Does VS Code Compare to Traditional SAP Development Environments?](https://blog.sap-press.com/how-does-vs-code-compare-to-traditional-sap-development-environments)

[Read More](https://blog.sap-press.com/how-does-vs-code-compare-to-traditional-sap-development-environments)

**Subscribe to our blog!**Get notified about future blog updates.

- <https://www.facebook.com/sappress>
- <https://twitter.com/sappress>
- <https://linkedin.com/company/sap-press>
- <https://www.instagram.com/sap_press/>
- <https://blog.sap-press.com/rss.xml>

### The official SAP PRESS Blog

As the world’s leading SAP publisher, SAP PRESS’ goal is to create resources that will help you accelerate your SAP journey. The SAP PRESS Blog is designed to provide helpful, actionable information on a variety of SAP topics, from SAP ERP to SAP S/4HANA. Explore ABAP, FICO, SAP HANA, and more!

### SAP Blog Topics

- [All Topics](https://blog.sap-press.com)
- [Logistics](https://blog.sap-press.com/tag/logistics)
- [Programming](https://blog.sap-press.com/tag/programming)
- [FICO](https://blog.sap-press.com/tag/fico)
- [Administration](https://blog.sap-press.com/tag/administration)
- [Featured](https://blog.sap-press.com/tag/featured)
- [Business Intelligence](https://blog.sap-press.com/tag/business-intelligence)
- [What Is?](https://blog.sap-press.com/tag/what-is)
- [CRM & Sales](https://blog.sap-press.com/tag/crm-sales)
- [Human Resources](https://blog.sap-press.com/tag/human-resources)
- [Video](https://blog.sap-press.com/tag/video)

### Blog curated by

[![Rheinwerk Publishing & SAP PRESS Logo](https://blog.sap-press.com/hubfs/rheinwerk-sappress-logo-header-1.svg)](https://sap-press.com) [Visit the SAP PRESS Store](https://sap-press.com)

### About

- [Home](https://sap-press.com/)
- [About Us](https://sap-press.com/the-publisher/)
- [Contact](mailto:info@rheinwerk-publishing.com)
- [Legal Notes](https://sap-press.com/legal-notes/)
- [Privacy Policy](https://sap-press.com/privacy/)
- [Terms of Use](https://sap-press.com/terms/)
- [Guest Posting](https://blog.sap-press.com/guest-posting)

© 2026 Rheinwerk Publishing, Inc. | Change Privacy Options

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "SAP PRESS",
    "url" : "https://blog.sap-press.com/author/sap-press"
  },
  "dateModified" : "2026-11-20T14:00:01.492Z",
  "datePublished" : "2026-11-20T14:00:01.000Z",
  "headline" : "The Clean Core for SAP BTP",
  "image" : [ "https://blog.sap-press.com/hubfs/The%20Clean%20Core%20for%20SAP%20BTP.jpg" ],
  "mainEntityOfPage" : {
    "@id" : "https://blog.sap-press.com/the-clean-core-for-sap-btp",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://blog.sap-press.com/hubfs/Logo-1.jpg"
    },
    "name" : "Rheinwerk Publishing, Inc."
  }
}
```