Clean Core explains: Why SAP cleans up—and what it means for customers, SAP, and partners

Clean Core means: the SAP standard remains untouched. Custom customizations and add-ons now only connect via approved, stable interfaces, either directly in the system with ABAP Cloud or alongside on the SAP Business Technology Platform. The goal is upgrades without rework, faster access to innovations like AI, and significantly less technical debt.

Everyone talks about clean core. Hardly anyone can explain it.

Since 2005, we at munich enterprise software have been developing add-ons for SAP, including MailCenter and our e-invoicing solutions. During this time, I have seen many buzzwords come and go. Clean Core is not one of them. Clean Core remains.

Still, I keep seeing the same scene in customer conversations: At the word “Clean Core,” everyone nods, and two sentences later it becomes clear that everyone thinks differently. IT management thinks about cleaning up, purchasing about licenses, developers thinking about bans. Everyone is somewhat right.

That’s why I’m trying here without foil jargon: with a rental apartment, a few candid words about SAP’s motives, and a look at what that means for customers and manufacturers like us.

What Clean Core Means: The Rental Apartment Declaration

Let’s take a rental apartment. The landlord is SAP, the apartment is the SAP standard, the core of your ERP system. As a tenant, you want to make it feel comfortable. Completely understandable.

In many SAP systems, the following has happened over the years: Here, a wall was moved because sales needed special logic. There, a water pipe was tapped because you wanted to write directly to an SAP table. And somewhere there is a cable from 2009 that no one remembers what it is for. In SAP language, these conversions are called modifications, implicit extensions, or direct table accesses.

That’s fine as long as no one renovates. When the landlord announces new windows, i.e., a release upgrade, the big shaking begins: Will the renovation still hold? Who checks it? How many weeks does the test take?

Clean Core means: you can continue furnishing as much as you want. Furniture, pictures, shelves. But load-bearing walls, pipes, and fuse boxes remain exactly as the landlord built them. Those who need more space add additions, for example a garden house on the SAP Business Technology Platform (BTP).

Technically translated: Extensions only use interfaces that SAP has officially released and keeps stable across releases. Within the system itself, this is done with ABAP Cloud, outside with BTP applications connected via APIs and events. SAP even broadens the concept: business processes, data, integrations, and operations should remain as close to the standard as possible. In practice, however, the discussion almost always revolves around in-house developments and add-ons.

Clean core before and after: makeshift apartment with torn-out wall and cable mess, next to it the tidy apartment with garden house as SAP BTP

Why SAP places so much value on this

It is not selfless, and it does not have to be. SAP has three solid reasons.

First: the cloud. SAP wants to bring its customers to the cloud with RISE with SAP and GROW with SAP. There, SAP installs updates for thousands of customers on the same platform. That only works if no one has moved walls.

Second: the deadlines. Mainstream maintenance for SAP ECC 6.0 ends at the end of 2027, and paid extended maintenance runs until 2030 (SAP News). Anyone switching to S/4HANA now shouldn’t have to carry around 20 years of legacy issues. Clean Core is the method to ensure the migration doesn’t become a move with all the boxes from the attic.

Third: AI. SAP integrates Joule and AI agents directly into the processes. They work best on standard processes and clean data. An AI agent that encounters heavily modified order processing is like a navigation device in a city where someone has secretly swapped the street signs.

A fourth reason is spoken out loud less often: Less uncontrolled customer growth means less support effort for SAP. That is also legitimate. Anyone who has ever accompanied an upgrade in a patched-up system understands it immediately.

SAP Add-On
MailCenter
Digital Communication for SAP ECC and S/4HANA
Schedule a Live Demo
SAP Add-on MailCenter

What Clean Core Means for SAP Customers

The good news first: No one has to delete all in-house developments tomorrow. Clean Core is a goal, not a demolition command.

The benefit is concrete. Upgrades become predictable because less testing and improvements are needed. New SAP functions and AI scenarios can be used earlier. And the knowledge no longer depends on the one developer who built the special logic in 2011 and now rents sailboats in Croatia.

The price for that is discipline. Existing original developments need to be reviewed, and the first question is the simplest: Does anyone still use it? In many established systems, there is code that no one has called for years. It can be deactivated without anyone noticing. For the rest, the ABAP Test Cockpit (ATC) checks at which clean-core level an object is located.

However, the most difficult transition is not a technical one. Clean Core requires departments to say “The standard is enough” more often. Those who manage that have been halfway through.

And when buying add-ons, it’s worth asking every provider from now on: At what clean-core level is your solution, and how do you prove it?

What Clean Core means for add-on developers like us

Now it gets personal. Classic ABAP was for decades the toolbox of the SAP partner world, including ours. Anyone who intervenes deeply in SAP processes, such as document output or invoice intake, used to get involved where it was technically easiest. Those were not always the places SAP had intended for this.

That is fundamentally changing right now. SAP is discontinuing certification for classic ABAP add-ons and instead offering Clean Core-compatible certifications (SAP). Since the third quarter of 2026, there have been two levels: the Integration Certification for solutions that rely on BTP and Clean Core, and an Interoperability Review for technically sound solutions that do not fully meet these strategic criteria (SAPinsider). The seal on the packaging will therefore mean much more to customers in the future than before.

For us as a manufacturer, this means:

  • New features are created on shared APIs and with ABAP Cloud, wherever SAP offers the necessary interfaces.
  • We check existing products object by object with the ATC and gradually move access to internal SAP objects to shared interfaces.
  • Where there is no approved interface yet, we say so openly.

The truth is: Not every process already has approved APIs today. Especially with older functions, there is a gap. That’s exactly why there are levels B and C. A provider who claims their product is consistently level A should be able to prove this.

In the end, we benefit too. An add-on on stable interfaces survives an upgrade without an emergency patch. This saves our customers testing effort and us the Monday morning call that starts with “Since the upgrade over the weekend …” starts.

The clean-core levels A to D at a glance

Since August 2025, SAP has classified extensions into four tiers. The model replaced the previous three-tier (“3-tier”) model (SAP News).

Level What is allowed Typical Technique Evaluation by SAP In the rental apartment
A Only publicly released, stable SAP interfaces ABAP Cloud, side-by-side extensions on BTP Fully compliant Furniture and Paintings
B Additionally, classic, documented SAP APIs e.g. BAPIs and other classic APIs Compliant Shelf and the designated wall rails
C Access to internal SAP objects Non-shared tables, function modules, classes Partially compliant Cable routed through existing empty conduits
D Techniques not recommended Modifications, write access to SAP tables, implicit extensions Not clean Wall torn out

Level A and B are the target. Level C is tolerated for legacy scenarios; SAP wants to help with upgrade planning with a change protocol for internal objects. According to SAP, level D causes the highest risk and the greatest technical debt.

Clean-core levels A to D from SAP: furniture and pictures, shelf on the wall rail, cables in empty conduit, torn-out wall

Three misunderstandings I keep hearing

“Clean Core means: no more in-house developments.” Wrong. Clean Core regulates how you expand, not whether. Custom logic is explicitly desired as long as it is connected via approved channels. A company that distinguishes itself from the competition through its processes should also be able to reflect this in SAP.

“That only applies to cloud customers.” Also wrong. The levels apply equally to S/4HANA on-premise and the Private Cloud. Those who expand cleanly on-premise today keep their path to the cloud open and make every future upgrade cheaper.

“Clean Core is a project, and then we’re done.” Unfortunately not. Clean Core is more like brushing teeth: once thoroughly helps, regular helps more. Every new requirement is again a decision between piece of furniture and wall breakthrough.

FAQ: Frequently Asked Questions about Clean Core

What is Clean Core in a sentence?

Clean Core is SAP’s strategy to keep the standard of an ERP system unchanged and to connect all extensions only via approved, upgrade-stable interfaces.

Does Clean Core also apply to SAP ECC?

Levels A to D have been defined for S/4HANA. For ECC customers, Clean Core is still relevant: mainstream maintenance for ECC 6.0 ends at the end of 2027, and those who clean up before migration carry fewer legacy issues.

What is the difference between ABAP Cloud and classic ABAP?

ABAP Cloud is a limited language and development model. It only allows shared SAP objects and checks this already during syntax checking. Classic ABAP, on the other hand, allows access to practically everything, including internal SAP objects.

How do I find out how “clean” my system is?

The ABAP Test Cockpit (ATC) checks in-house developments against the Clean-Core rules and assigns them to the stages. A usage analysis is also useful so that you only evaluate the code that is actually still running.

What should I pay attention to with SAP add-ons?

Ask the vendor about the clean-core level of their solution and about SAP certification. A reputable manufacturer can show which parts run on approved interfaces and where gaps still exist.

My conclusion: Tidying up is worth it, with good judgment

Clean Core is not a harassment of SAP, but the condition for SAP systems to keep pace with cloud, AI, and short release cycles in the future. For customers, this means: honestly evaluating in-house developments and building new ones cleanly. For manufacturers like us, it means: switching products to approved interfaces and openly stating where that is not yet possible.

Or in the language of the rental apartment: Furnish it however you like. Just please leave the walls standing.

Do you want to know how Clean Core fits with your document outbound or e-invoice processing in SAP? Contact me, I’ll be happy to show you how we approach this in MailCenter and our e-invoicing solutions. Get in touch

Thilo Kiefer

Thilo Kiefer

CEO and Product Manager SAP Add-Ons

For me, real innovation arises where technology serves people and not the other way around.