What Is Clean Core in SAP? Definition and the A-D Extensibility Model
Clean core means keeping S/4HANA free of custom modifications. Here's SAP's A-D extensibility model, and why it determines whether Joule agents work reliably.
Clean Core
Clean core is the SAP practice of keeping the S/4HANA core system free of custom code modifications, using SAP's released APIs and key-user extensibility instead, so upgrades stay non-disruptive and AI agents like Joule can read standard business objects rather than tripping over custom logic they were never designed to interpret.
SAP grades how clean a system actually is on an A-to-D extensibility scale. Level A is classic ABAP modifications and user exits: the highest technical debt and the highest risk to agent reliability. Level B mixes classic modifications with newer key-user extensions. Level C, SAP's recommended baseline, uses key-user tools like Custom Fields and Custom Logic along with UI adaptation instead of touching core code. Level D, the target state, restricts everything to ABAP Cloud and released APIs only.
Most enterprise SAP estates sit somewhere between A and C after years of accumulated customization, not at D. ABAP Test Cockpit (ATC) checks and the RISE Methodology dashboard are the standard tools for measuring exactly how much custom-code debt a given system carries, and that number is one of the first things an AI readiness review should surface.
Related terms
Read more
AI Readiness: clean core and AI, the connection SAP isn't fully explaining.
Want to know your system's actual extensibility level? Check Your SAP AI Readiness Now.