M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Clean core

Concept

An SAP extension approach that avoids modifying SAP standard code and instead extends the system through released APIs and side-by-side apps so upgrades stay predictable.

✦ CONCEPTClean coreM365.FM
Title graphic: Clean core (Concept)

Also discussed

The episode about Clean core also covers SAP ECC, SAP Fiori, SAP S/4HANA and SAP.

Description

Clean core is an SAP extension approach in which the standard SAP code is left unmodified. Custom requirements are instead met through released interfaces and through apps that run beside the core system. The aim is that upgrades stay predictable, because extensions are kept separate from SAP code and therefore do not interfere with it. In SAP Learning material on clean core extensibility, this is summed up as keeping extensions clean so that they stay separate from SAP code, upgrades run smoothly and the system remains maintainable.

The approach covers several practical rules. According to the SAP Learning unit "Decouple Extensions from Standard", extensions should be avoided where standard features or configuration already meet the need. Where an extension is justified, approvals should be governed with documented reasons and value. The guiding principle is two-sided: extensions must never break upgrades, and upgrades must never break extensions. An organization that follows this principle treats every request for custom code as a decision to be assessed, not as a default.

Two families of extension are described. On-stack extensions are created inside S/4HANA Cloud and include key user extensions and developer extensions. Side-by-side extensions are built on SAP Business Technology Platform and run outside the core system. In both cases, extensions may use only released objects, such as released public APIs, BAdIs and RAP business object extension points. Unreleased objects must not be used. The ABAP Cloud model enforces this restriction through syntax checks, which means that the boundary between permitted and non-permitted objects is checked by tooling and does not depend on developer discipline alone.

A three-tier model ranks the available approaches. Tier 1 uses only ABAP Cloud and the cloud extensibility model, and it is mandatory for the Public Edition. Tier 2 wraps unreleased objects in released ones and applies to Private Edition and on-premise systems. Tier 3 covers classical extensions, which are discouraged because they are likely to disrupt upgrades. For assessing use cases and choosing a target solution, the SAP Application Extension Methodology is named as a supporting aid. Typical decisions around clean core therefore concern which tier an existing or planned extension falls into, whether a standard feature could replace it, and whether it belongs on-stack or side-by-side.

Clean core also appears outside pure SAP development topics. The M365.FM episode "Build an Enterprise AI Operating Model for Scale" (2026-01-19) lists building a clean core architecture as one of the steps for incorporating AI into an operating model. The episode names it alongside redesigning workflows to integrate machine participation, defining accountability before automation, and treating data governance as infrastructure. In that framing, clean core is presented as part of the architectural foundation that lets AI initiatives scale, and the episode describes the wider goal as turning AI from a novelty into a competitive advantage.

In summary, clean core is a discipline for how SAP systems are extended. It restricts extensions to released, supported mechanisms, prefers standard capabilities over custom code, and uses a tiered model to classify how far a given extension departs from that ideal. The result described in the sources is a system whose extensions remain separate from SAP code, so that upgrades can proceed without the extensions causing disruption.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept

Episodes about Clean core

Episodes in which Clean core is discussed:

SAP S-4HANA - Simply Explained

2026-10-31

SAP S/4HANA sounds intimidating, yet most companies running SAP ECC have to decide where it lives and how to migrate before the 2027 deadline. This plain-language episode is for IT and business people who need to understand what S/4HANA is, how it connects to…

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What does clean core mean in SAP? (AI)

Clean core is an extension approach that avoids modifying SAP standard code. Extensions use released APIs and side-by-side apps instead, so that upgrades stay predictable.

Which objects may clean core extensions use? (AI)

Only released objects, such as released public APIs, BAdIs and RAP business object extension points. Unreleased objects are not allowed, and the ABAP Cloud model enforces this through syntax checks.

What are the three tiers of the clean core model? (AI)

Tier 1 uses only ABAP Cloud and the cloud extensibility model and is mandatory for Public Edition. Tier 2 wraps unreleased objects in released ones for Private Edition and on-premise systems. Tier 3 covers classical extensions, which are discouraged because they are likely to disrupt upgrades.

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: