SAP Solutions
Clean core, explained plainly, and done properly.
Every custom object in your SAP core either helps you or slows down your next upgrade. In August 2025 SAP replaced its old three-tier extensibility model with four clean core levels. We assess where your code sits and move it to where it won't hold you back.
The four levels
The four levels, in plain English.
| Level | What it means | Upgrade risk |
|---|---|---|
| A | Released APIs, ABAP Cloud, CAP, SAP Build | Clean: SAP's strategic direction |
| B | Classic APIs such as BAPIs and IDocs | Clean and upgrade-stable |
| C | Internal or unreleased SAP objects | Some risk: manage with wrappers |
| D | Modifications, direct table writes, implicit enhancements | Not clean: remediate |
Source: SAP Note 3578329. Last verified 1 November 2026.
The challenge
What gets in the way.
- Thousands of custom objects with unknown upgrade risk.
- Uncertainty about whether the system is ready for SAP Cloud ERP Private.
- Developers trained only in classic ABAP.
What we do
Clean core services.
Clean Core Assessment
An ATC-based scan that classifies your custom code into Levels A–D, with a remediation roadmap.
Custom code remediation and retirement
Remove unused code; move Level C/D logic to released APIs or wrappers.
ABAP Cloud / RAP development
New on-stack extensions built at Level A.
Side-by-side extensions on BTP (CAP)
Move non-core logic off the ERP.
BTP →Integration clean-up
Replace custom point-to-point RFC/BAPI links with APIs or events through Integration Suite.
Integration Suite →Find out where your custom code sits.
A Clean Core Assessment classifies every custom object and tells you what to fix first.