SAP Clean Core Licensing: What SAP's Extension Strategy Means for Your BTP Costs and Compliance Position

What SAP Clean Core Actually Means

SAP Clean Core is SAP's strategic mandate that customer-specific code and customisations should not modify the standard S/4HANA or SAP application code directly. Instead, all custom logic must be built using SAP's approved extension points: ABAP Cloud APIs, released BAdIs, and side-by-side extensions running on SAP BTP (Business Technology Platform).

The business rationale SAP presents is compelling: Clean Core enables faster upgrades, reduces testing burden, and maintains upgrade compatibility. These benefits are genuine. But the commercial rationale for SAP is equally clear and rarely stated openly — Clean Core systematically redirects customer extensibility spending from classical ABAP development (which requires no incremental SAP licence) to SAP BTP (which requires significant incremental SAP licences). Understanding this dynamic is essential before you commit to a Clean Core strategy.

Clean Core is not optional for S/4HANA Cloud customers — it is architecturally enforced. For on-premise and RISE with SAP private cloud customers, it is technically possible to maintain some classical ABAP customisation, but SAP increasingly positions any deviation from Clean Core as a compliance and upgrade risk. The pressure to conform is commercial as much as technical.

The Four Licensing Cost Implications of Clean Core

Understanding where Clean Core creates new or expanded licence costs requires examining four distinct areas. Each has different commercial characteristics and negotiation dynamics.

BTP Entitlements in RISE vs What Clean Core Actually Requires

RISE with SAP includes a bundle of BTP entitlements as part of the base subscription. SAP presents these entitlements as sufficient for a standard Clean Core implementation. They are not — for any enterprise with a material SAP customisation footprint. Understanding the gap between included BTP entitlements and actual Clean Core BTP requirements is one of the most important pre-signature due diligence activities an enterprise can perform.

The BTP entitlements bundled in RISE are designed around a typical small-to-medium deployment. Large enterprises with complex process landscapes, dozens of integrations, and significant custom development typically exhaust the included BTP entitlements within 12–18 months of go-live and must purchase additional consumption. This expansion cost is rarely modelled in the initial RISE business case, making the total cost of ownership significantly higher than projected. See our detailed guide to SAP BTP licensing for a full breakdown of what is and is not included.

Our RISE with SAP advisory service specifically includes BTP entitlement gap analysis as a standard deliverable — because this is consistently one of the most significant sources of cost overrun we see in RISE implementations.

What Custom Code Migration to Clean Core Costs

The technical effort to migrate existing ABAP customisations to Clean Core is substantial and is often underestimated at programme initiation. SAP provides a Clean Core Readiness Assessment tool (ABAP Test Cockpit / ATC) that identifies custom code violations, but the tool identifies problems — it does not solve them.

The typical outcome of an ABAP custom code scan for an enterprise running a large ECC or S/4HANA instance is thousands of violations, ranging from trivial (deprecated function module calls) to architecturally significant (direct database access bypassing the SAP data model, use of SAP internal APIs with no public equivalent). Each violation requires developer effort to remediate — either by refactoring the code to use Clean Core APIs, rebuilding the functionality as a BTP extension, or making a business decision to retire the custom logic entirely.

From a licensing perspective, the remediation work itself generates licence cost implications: ABAP Cloud developer licences for developers working on the migration, BTP capacity for hosting the new extensions, and Integration Suite consumption for the new integration patterns. These are in addition to the programme delivery costs, which for a large enterprise typically run to several million euros for a comprehensive Clean Core migration.

Our guide on SAP custom code migration licensing covers the full cost model for this migration in detail.

Indirect Access Risk in the Clean Core Model

Clean Core introduces a less obvious but significant indirect access and compliance risk. When custom logic is moved from inside the SAP core to BTP extensions, and those extensions interact with SAP data — reading, writing, or triggering SAP business processes — the interaction patterns may create SAP indirect access exposure depending on how the integration is architected.

SAP's official position is that extensions built using released BTP services and SAP-approved APIs do not create indirect access exposure. In practice, the boundary is less clear when extensions use third-party services or custom API calls that are not part of SAP's released API catalogue. This is an area where architecture decisions made during programme delivery have direct licence compliance implications — and where early involvement of SAP indirect access advisory expertise can prevent expensive compliance problems post-go-live.

What to Negotiate Before Committing to Clean Core

Clean Core is increasingly non-negotiable from a technical architecture standpoint for S/4HANA Cloud customers. But the commercial terms around the BTP consumption required to implement Clean Core are highly negotiable. The following are the key areas to address before signing.

• BTP consumption entitlements in RISE: Negotiate specific BTP service entitlements (not just generic credits) that match your extension landscape. Get volume commitments for Integration Suite message volumes, BTP application environments, and ABAP Cloud system sizes — sized to your actual requirements, not SAP's standard bundles.
• ABAP Cloud developer licence pricing: The list price for ABAP Cloud developer access is significantly higher than classical ABAP workbench access. This difference is negotiable, particularly as part of a broader S/4HANA or RISE deal. Establish the developer licence cost in the main negotiation, not as a subsequent add-on.
• BTP growth protections: Any BTP consumption agreement should include usage monitoring provisions, overage caps, and conversion rights to ensure that BTP cost overruns during the Clean Core migration period do not result in unbudgeted spend. SAP should share the risk of consumption forecasting inaccuracy in the early years of a RISE implementation.
• Contract provisions for API stability: Clean Core extensions built on SAP's released API catalogue are only as stable as SAP's API release commitments. Contractual provisions protecting you from SAP deprecating APIs your extensions depend on — without adequate notice and backward compatibility — are a legitimate and important negotiation point.

Clean Core and SAP Audit Risk

Organisations that are in transition to Clean Core — where some custom code has been migrated but legacy ABAP customisations still remain active — face a complex compliance position. SAP's measurement tools will detect classical ABAP usage patterns, and depending on how your SAP licence agreement defines compliant usage in the context of S/4HANA, legacy customisations may create audit exposure.

This is a nuanced area where the contractual definition of "standard use" in your specific SAP licence agreement matters more than general guidance. Our SAP audit defence team regularly advises on the compliance position of transitional Clean Core environments. For a full treatment of the audit risk dimensions, see our companion guide on SAP Clean Core audit risk.

Related Clean Core and BTP Topics

Clean Core licensing is closely connected to several adjacent topics that enterprise buyers need to understand to build a complete picture. Our guides on SAP ABAP Cloud developer licensing, SAP BTP side-by-side extension licensing, and SAP BTP credits and consumption cover the specific licence mechanics in depth.

For enterprises in the process of selecting between RISE and on-premise S/4HANA, the Clean Core licensing cost differential between deployment models is a material factor in the total cost of ownership comparison. Our S/4HANA cloud vs on-premise licensing comparison addresses this directly.

If you are already in negotiation with SAP on RISE or S/4HANA, contact our team for an independent review of the BTP and Clean Core licensing terms in your current draft agreement. This is one of the highest-value interventions we provide, and it is consistently the area where we find the largest gaps between what SAP offers and what a well-informed buyer should achieve.