At the same time, the ERP landscape is changing rapidly. More organisations are moving their systems to cloud-based platforms, where innovation and updates are delivered continuously. In this reality, an ERP foundation that can keep up is essential. This is where Clean Core becomes critical.
What is Clean Core?
Clean Core is a principle focused on keeping the ERP core as close to standard as possible. This means limiting changes within the core system and instead placing customisations and innovations outside the core – through extensions, integrations, or dedicated platforms.
The goal is not to eliminate customisation, but to ensure it is implemented in a way that does not compromise stability or future development. When the core remains clean, it becomes easier to adopt updates, leverage new functionality, and integrate new solutions.
More on SAPs Clean Core Levels: A Stepwise Approach to ERP Extensibility
Clean Core Levels is SAP’s updated approach to assessing and governing custom extensions. It replaces the previous three-tier model by moving away from a binary classification of “clean” vs. “not clean” core, and instead introduces a more gradual, level-based framework.
This makes the journey toward a clean ERP core more flexible and practical – especially for organisations with a significant amount of existing classic ABAP custom code.
Level A – Clean core: Extensions built using the ABAP Cloud development model, either on-stack or side-by-side on SAP BTP. These are designed to have minimal impact on the SAP standard.
Level B – Classic but controlled: Classic ABAP extensions that follow SAP’s recommended development practices and use released APIs.
Level C – Conditionally clean: Classic ABAP extensions that rely on internal SAP objects. With dedicated upgrade checks, these can be considered conditionally clean.
Level D – Not clean core: Extensions that deviate from Clean Core principles, such as modifications of non-recommended objects and technologies.
With Clean Core Level, organisations can take incremental steps toward a cleaner core at their own pace. This provides greater upgrade stability while still allowing room for innovation – without requiring a complete rebuild of existing systems.
As ERP Moves to the Cloud
Clean Core is not a new concept in the ERP world, but it has become significantly more relevant as more organisations move to the cloud.
In cloud environments, innovation is typically delivered through continuous updates. New features, improvements, and security enhancements become a natural part of the system lifecycle. This allows organisations to continuously evolve their systems, but it also requires systems to be flexible enough to keep up. If an ERP system is heavily customised within the core, upgrades can become both time-consuming and risky. A clean core, on the other hand, makes it much easier to keep up with change and take advantage of new opportunities.
Start with Visibility
For many organisations with existing ERP systems, the path to Clean Core can seem overwhelming. However, the first step is rarely about technology – it’s about making the right decisions.
First and foremost, organisations need to understand why it is important to adapt processes and standardise the core: Which processes truly differentiate the business, and where can standard functionality be adopted without risk?
Once there is clarity around the purpose, organisations can create visibility into existing customisations and extensions to understand the value they deliver. Often, this reveals that some functionality is no longer in use, or that newer standard features can meet needs that previously required custom development.
This insight makes it possible to decide what to retain, improve, or retire.
Gaining Visibility in Clean Core: Using Custom Code Analysis and ATC
A clear understanding of existing customisations is essential for making informed decisions in a Clean Core journey. This is where Custom Code Analysis and the ABAP Test Cockpit (ATC) come into play.
Custom Code Analysis provides an objective view of how much classic ABAP customisation exists, which objects are in use, and where potential upgrade risks may arise. It effectively acts as a “health check” for the system, identifying deviations from standard, legacy modifications, and potential upgrade issues.
The ABAP Test Cockpit (ATC) supports governance by ensuring that both existing and new developments comply with SAP-recommended practices – for example, in relation to Clean Core Levels. ATC can be configured to run regular checks, giving development teams a solid basis for deciding which customisations to retain, optimise, or phase out.
Together, Custom Code Analysis and ATC provide more than just technical visibility. They create a data-driven foundation for decision-making. This enables organisations to plan a safe and incremental transition to Clean Core without compromising flexibility or the ability to innovate.
A Stronger Foundation for the Future
Ultimately, Clean Core is about balance: between standard and innovation, stability and flexibility.
A clean ERP core creates a robust foundation that makes it easier to evolve the system landscape over time. It enables organisations to adapt to new technologies, respond quickly to change, and continuously improve their processes.
In short, Clean Core is not about doing less – it’s about building an ERP landscape that is ready for the future: flexible, stable, and built for innovation.
Is your ERP ready for the future? Talk to our experts about building a future-ready ERP foundation.
Fill in the form or give us a call on
+45 3555 5575