SAP Clean Core Strategy: What It Means for Your Licensing Bill

What SAP's Clean Core Strategy Actually Means

SAP's Clean Core architecture is simple to describe but transformative in its implications: keep all standard SAP processes untouched in the core ERP system, and move every business customization—every bespoke ABAP transaction, every interface, every modified process—out of the core and onto SAP Business Technology Platform (BTP) using SAP's extension frameworks.

The official framework is this: Use ABAP Cloud (a subset of ABAP with restrictions on direct database access) for custom logic. Use Rapid Application Programming (RAP) for OData-first development. Use Cloud Application Programming (CAP) for cloud-native extensions. Keep the core system untouched, versioned, and "clean" so that every SAP upgrade is a simple, predictable patch operation rather than a multi-year, multi-million-dollar migration project.

It sounds rational. It is rational—from SAP's perspective.

Why SAP Is Pushing This (And Why You Should Be Skeptical)

Clean Core isn't a technology mandate issued out of goodwill. It's a revenue strategy. Here's why SAP wants you to adopt it:

• Cloud upgrade velocity: SAP wants to move every enterprise customer to the cloud. Every customization in the core makes cloud migration harder, slower, and more expensive. Clean Core removes that friction.
• RISE with SAP subscription lock-in: RISE is SAP's flagship cloud subscription (€1M+/year for mid-market enterprises). But RISE margins are lower than traditional license-plus-maintenance stacks. BTP add-ons have higher margins. Clean Core expansion into BTP = higher RISE total contract value.
• Support reduction for legacy systems: SAP's investment in ECC 6.0 and even S/4HANA on-premise is shrinking. ECC is in extended maintenance; S/4HANA on-premise customers are being quietly nudged toward RISE or out the door. Clean Core is the technical justification for that retreat.

This is not conspiracy. This is standard vendor economics. SAP benefits when your customization portfolio migrates from "expensive on-premise ABAP development" to "expensive BTP platform fees." The customer risk is that BTP pricing is less transparent and more complex than traditional licensing—and that the initial BTP allocation you receive in a RISE bundle is deliberately undersized.

The Licensing Trap Inside Clean Core

This is where most enterprises get blindsided. When you commit to Clean Core, here's what actually happens:

Every Extension Requires BTP Licensing

BTP is not free for extensibility. BTP is sold as a separate product with its own pricing model, its own deployment options, and its own licensing complexity:

Each is sold separately. Each has capacity-based pricing. Each scales with your complexity. And here's the trap: in RISE bundles, you receive a minimum allocation for each component. It's always undersized. SAP knows it. Your SAP account team knows it. By month 6 of your RISE deployment, you'll be adding capacity.

BTP Capacity Pricing Is Deliberately Opaque

SAP doesn't advertise BTP pricing. There's no public price list. Instead, enterprises negotiate based on "capacity units," "blocks," or "subscriptions"—all of which are defined differently by component. ABAP Cloud is measured in CPU. Cloud Foundry is measured in GB-hours. Integration Suite is measured by API calls and message volume. Analytics Cloud is measured by active users and data volume.

This opacity is intentional. It prevents price comparison. It makes vendor lock-in defensible because "BTP is the only way to extend S/4HANA cleanly." And it means that when you need to add capacity (and you will), there's no public market rate to reference.

Real-World Cost Impact

Here's a realistic scenario: A manufacturing enterprise with 50 custom ABAP transactions in their ECC system decides to migrate to S/4HANA with Clean Core. Those 50 transactions must move to ABAP Cloud on BTP.

Per SAP's recommendation, they're modeled as 8-10 dedicated instances of ABAP Cloud. At current capacity pricing (€18K–€28K per instance, annually), that's €144K–€280K per year in ABAP Cloud alone. That's on top of their S/4HANA license fees, their RISE subscription, and any Integration Suite costs for middleware.

Compare that to their legacy ECC environment, where those same 50 transactions were built and maintained by 2-3 in-house developers (cost: their salary, ~€150K–€200K combined). The Clean Core path costs more and forces centralization of development onto a platform you don't control.

Most enterprises encounter this reality after they've signed the RISE contract.

RISE with SAP and Clean Core—The Bundle Pressure

RISE is SAP's cloud subscription for S/4HANA. It bundles cloud infrastructure, SAP licensing, managed services, and "basic" BTP allocations into a single contract. Typical RISE pricing for a mid-market enterprise: €2M–€5M over 3 years.

But "basic" BTP allocations are systematically undersized. Here's how SAP structures the negotiation:

1. The Clean Core Assessment workshop: SAP conducts a "Clean Core assessment" where they audit your current ECC customizations and recommend which ones migrate to BTP, which stay in the core, and which are retired. This assessment is framed as discovery; it's actually a sales tool.
2. The gap identification: The assessment invariably finds that 60-80% of your customizations require BTP migration. This number is not accidental—it's designed to create a "gap" between your initial BTP allocation and what you actually need.
3. The capacity add-on pitch: SAP sales then positions BTP capacity add-ons as a negotiation point: "We can include more ABAP Cloud instances in RISE, but we'll need to adjust the overall contract value." This frames BTP expansion as expensive to the enterprise.
4. The implementation reality: You sign RISE with undersized BTP. During hypercare (the post-go-live period), you discover you need more capacity. You're now in a weak negotiating position: your go-live is in jeopardy, and adding capacity through SAP's channel is faster than building in-house alternatives.

The result: RISE contracts that appear cheaper than traditional licensing, but are actually more expensive once BTP capacity is properly sized.

What Happens at S/4HANA Migration: The Licensing Exposure Crystallizes

The S/4HANA migration project is where Clean Core licensing costs become concrete. Here are the specific licensing exposures that appear in migration contracts:

Shadow User Licenses During Parallel Running

During parallel run (typically 4-8 weeks), you're running both ECC and S/4HANA simultaneously. SAP licensing for parallel run requires that every user accessing either system is licensed for both systems. You'll negotiate a "transition period" where shadow user licenses are included, but after a set date (often 90-120 days post-go-live), you're responsible for the full named-user count on S/4HANA. The gap between your ECC user count and S/4HANA user count is a negotiation point.

Indirect Access Exposure Through RFC and APIs

In Clean Core architectures, BTP extensions frequently call back into S/4HANA via RFC (Remote Function Call) or OData APIs. SAP interprets these API calls as "access" to the S/4HANA system, which means BTP instances that call S/4HANA may trigger SAP Digital Access licenses. This is usually not discovered until the integration is live.

Digital Access Add-Ons Triggered by Clean Core APIs

Digital Access licenses are additional fees for non-human usage of SAP systems (APIs, integrations, middleware). Clean Core's reliance on APIs as the primary integration pattern dramatically increases your Digital Access exposure. An enterprise with 10-15 API integrations might find themselves needing 50-100 Digital Access licenses after Clean Core implementation.

BTP Integration Suite Replacing Enterprise Middleware

Many enterprises use third-party middleware (Mule, Dell Boomi, Informatica, etc.) to manage integration with their SAP systems. Clean Core is designed to eliminate that need: SAP positions their Integration Suite as the "native" integration for Clean Core extensions. The migration path is clear: retire your third-party middleware contract (savings), adopt Integration Suite on BTP (new costs). The net result is often cost-neutral or cost-negative from the enterprise's perspective.

All of these exposures are contractually addressable during the migration negotiation. Most enterprises don't negotiate them.

The Four Cost Pools Enterprises Always Miss

When we audit SAP RISE and S/4HANA migration contracts with enterprises, we consistently find cost underestimates in four areas:

For a typical mid-market enterprise, that's a €310K–€770K annual cost gap, discovered after contract signature. Most of that gap is contractually "non-negotiable" at that point because you've already migrated.

The SAP Clean Core Negotiation Playbook: Six Levers

These are the six specific levers that experienced enterprises use to reclaim control of their SAP Clean Core and RISE costs:

1. Demand a Clean Core Cost Modelling Exercise Before Contract Signature

Before you sign RISE, require SAP to deliver a detailed cost model for each BTP component based on your actual customization audit. Don't accept "basic allocation" language. Make SAP commit to specific ABAP Cloud instance counts, Integration Suite message volumes, and Analytics Cloud user counts. Document these in the commercial schedule. Any capacity overages after 12 months are SAP's responsibility.

2. Negotiate BTP Capacity Into the RISE Bundle, Not as Add-Ons

BTP add-ons purchased separately are more expensive than BTP capacity included in the RISE base contract. Negotiate your primary BTP components (ABAP Cloud, Integration Suite, Work Zone) as part of the RISE base contract value, not as optional add-ons. This gives you price stability and removes the gap-based sales dynamic.

3. Include "SAP Preferred Success" in RISE, Not as a Separate Service

SAP Preferred Success is their "success management" service for RISE customers. It's typically sold as an add-on. Negotiate it as part of RISE base. This service includes quarterly business reviews, roadmap planning, and performance optimization—all of which reduce your risk of underestimating Clean Core complexity.

4. Lock Per-Unit BTP Pricing for the Full 3-Year Term

SAP's standard language allows them to increase BTP pricing annually. Negotiate fixed pricing for all BTP components for the entire RISE term (typically 3 years). This removes price escalation risk and prevents mid-term surprises.

5. Preserve ABAP Modification Rights During the Migration Window

SAP's guidance is that post-migration, all new ABAP development goes to BTP. But during the first 12 months of S/4HANA operation, you should retain the right to make direct ABAP changes in the core if migration to BTP delays your go-live or impacts business outcomes. Negotiate this explicitly. It's your escape hatch if BTP complexity becomes a blocker.

6. Demand Digital Access Audit Indemnification During Hypercare

SAP audits Digital Access compliance aggressively during the first 2 years post-migration, when your integration patterns are still unstable. Negotiate indemnification: SAP covers the cost of Digital Access licenses for any API calls or indirect access triggered by their recommended Clean Core architecture during the first 18 months of production operation. This shifts audit risk back to SAP, where it belongs.

The Red Lines: What NOT to Accept in SAP Contracts

There are specific contract clauses that are deal-breakers for Clean Core-based RISE agreements. Here's what to push back on:

Real Numbers: What This Looks Like in Practice

Here's how this plays out in a real enterprise scenario:

The company: A €200M revenue manufacturing company with 1,200 SAP users. They're running ECC 6.0 with 60 custom ABAP modifications. They've been advised by SAP that Clean Core + RISE is the "strategic" path.

The initial SAP proposal:

• RISE with SAP (3-year): €7.5M
• BTP "standard allocation": included (vague definition)
• Professional services (migration): €1.2M
• Total: €8.7M

The reality after the Clean Core assessment:

• RISE with SAP (3-year): €7.5M (unchanged)
• ABAP Cloud (for 60 custom modifications): €280K/year × 3 = €840K
• Integration Suite (replacing PI/PO): €180K/year × 3 = €540K
• Work Zone (replacing Portal): €120K/year × 3 = €360K
• Digital Access licenses (discovered during hypercare): €80K/year × 2.5 = €200K
• Professional services: €1.2M (unchanged)
• Total: €10.84M (up 24% from initial estimate)

That €2.14M gap emerges post-contract-signature and is baked into the business case by then. Most enterprises absorb it as "migration complexity." It's not complexity; it's contract design.

What does renegotiation look like with the six levers applied?

• Lever 1: Pre-contract Clean Core cost modelling identifies the €840K ABAP Cloud, €540K Integration Suite, and €360K Work Zone costs up-front. They're negotiated into the base RISE contract or explicitly excluded with a defined alternative (keep ABAP modifications, outsource integration to third-party middleware, defer Work Zone).
• Lever 2: BTP capacity is priced into RISE base, reducing per-unit costs by 15-25%.
• Lever 3: SAP Preferred Success (€80K–€120K/year) is negotiated into RISE, reducing external advisory costs.
• Lever 4: Fixed pricing on all BTP components removes price escalation risk.
• Lever 5: Preservation of ABAP modification rights for 12 months post-migration allows the enterprise to make tactical decisions about which customizations stay in-core vs. migrate to BTP, based on actual operational complexity rather than SAP recommendations.
• Lever 6: Digital Access indemnification during hypercare (18 months) protects against audit exposure during the integration stabilization period.

The renegotiated deal:

• RISE with SAP base (ABAP Cloud, Integration Suite, Work Zone included): €8.1M
• Professional services: €1.2M
• Total: €9.3M (down €1.54M from the "reality" estimate, 15% reduction)

That's a savings of €1.54M over 3 years on a €10.84M commitment. For a gainshare engagement with a 25% split, that's €385K in advisory fees—and the client gets a better contract.

Key Takeaways