Clean Core
Keeping the SAP S/4HANA core free of modifications so that extensions rely only on released, stable interfaces and upgrades stay predictable.
A clean core means that SAP standard code is not modified and that extensions use only stable, documented interfaces: released APIs, released CDS views and extension points such as BAdIs. When an extension depends only on released objects, a new release is far less likely to break it.
Existing custom code usually departs from the principle in a few recurring ways: direct writes to SAP standard tables, use of objects without a release contract, modifications and implicit enhancements of standard code, and dependencies on objects that are deprecated in the target release.
SAP describes how far an extension follows the principle with a tier model and, more recently, with more granular clean core levels. Which classification applies depends on your release, so check the current SAP documentation for it.
In ERP Preflight
Clean Core Object Guard classifies custom ABAP code and the SAP objects it references, with file, line and SHA-256 as evidence. The free Clean Core Object Lookup answers the question for a single object from the SAP Cloudification Repository.
Problems that involve Clean Core
- MajorLegacy object needs a cloud extension
- MajorCustom Z/Y transaction needs Clean Core review
- CriticalRequirement implies a Clean Core violation (tier 11)
- BlockerDirect write to an SAP standard table
- CriticalDirect read of an SAP standard table
- CriticalObsolete or cloud-forbidden ABAP statement
- CriticalCall to a function module not released for cloud development
- CriticalUse of a class not released for cloud development
Related terms
Free tools
- Clean Core Object Lookup
Is a table, CDS view, class or function module released for ABAP Cloud?
Background articles
- Clean core extensibility explained: tiers, released APIs and classic modificationsA practical overview of how SAP classifies extensions by their upgrade stability, from ABAP Cloud on released APIs to classic modifications, and how to assess existing custom code.
Written for ERP Preflight · reviewed September 27, 2026
All glossary termsERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.