Clean Core with SAP CAP: Extend SAP CX Without the Upgrade Pain

You customise SAP. A year later, the upgrade breaks your changes. Your team spends weeks fixing it. Sound familiar?

We hear this story at least once a month. That’s the cost of custom code inside the SAP core. It adds up fast. After a few rounds, every quarterly update turns into a mini-project of its own. Your team dreads release notes instead of reading them.

Clean Core stops this cycle. The idea is simple: keep the SAP core standard. Build your custom logic next to it, not inside it. SAP gave you a proper extension framework. Use it.

TL;DR: Seventy-five per cent of ERP implementation projects get derailed (Gartner, 2024). Custom code inside the core is a key contributor. Clean Core architecture with SAP CAP on Cloud Foundry keeps your extensions separate, so SAP upgrades stay simple. Extensions talk to SAP through stable APIs. The core stays standard. Upgrades that used to take months now take days.

What Does Clean Core Actually Mean?

Forty-eight per cent of DSAG respondents already use or plan to use RISE with SAP, up from just 16% in 2024 (DSAG/The Register, 2025). Cloud migration is accelerating, and Clean Core is the de facto prerequisite.

The principle: no custom code inside SAP. Your business logic lives in separate extensions that talk to SAP through stable APIs.

SAP Sales Cloud V2 and SAP Service Cloud V2 are built for exactly this. They expose clean REST APIs and an event system designed for side-by-side extensions. SAP updates the core on their schedule. Your extensions keep working.

This isn’t a workaround. SAP designed it this way on purpose. The V2 products were specifically architected to enforce separation. That’s a proper engineering decision, not an afterthought.

How Do We Build Extensions with SAP CAP?

Average ERP implementation timelines have dropped from 15.5 months to 9 months, driven by SaaS adoption and side-by-side extension patterns (Panorama Consulting, 2025). CAP accelerates this even further.

We use the SAP Cloud Application Programming model (CAP): SAP’s open-source framework for building services on SAP BTP. CAP runs on Cloud Foundry inside SAP BTP.

We’ve used it across every V2 project we’ve delivered. Here’s why it’s a solid choice:

• No infrastructure headaches. Cloud Foundry handles scaling, routing, and deployment. Your team writes business logic, not ops scripts.
• SAP connections built in. CAP plugs directly into XSUAA (auth), SAP Event Mesh (events), the Destination Service, and the Sales/Service Cloud V2 APIs. No glue code needed.
• Standard tech stack. Node.js or Java. OData and REST. CDS for data modelling. No exotic lock-in. Your developers already know the tools.

The result: extensions you can deploy, test, and update independently of SAP’s release calendar. Neat separation of concerns.

What Does This Look Like in Practice?

SAP’s total cloud revenue reached EUR 17.14 billion in FY 2024, up 25% year-over-year (SAP News, 2025). The move to cloud makes Clean Core the only sensible approach. Jamming custom code into the core just doesn’t work anymore.

Sales Cloud V2 example: A customer needs custom validation on the opportunity object, plus a few extra fields for their workflow. We deploy a CAP service on Cloud Foundry. It adds the validation logic and custom fields. It listens to opportunity events via SAP Event Mesh: no polling, no scheduled jobs. A custom Fiori UI sits inside the Sales Cloud shell. Sales reps see one clean interface.

The Sales Cloud V2 core? Untouched. SAP pushes an update next quarter? No regression testing needed.

Service Cloud V2 example: Custom escalation rules, enriched case data, connections to external ticketing tools. All CAP extensions, all on Cloud Foundry, all outside the core. Spot on for keeping maintenance costs down.

Why Does Clean Core Matter for Your Budget?

Fifty per cent of ERP implementations fail on their first attempt (Panorama Consulting, 2025). Custom code that breaks during upgrades is one of the most common failure modes. I reckon most IT leaders have lived through at least one upgrade that went sideways because someone hacked something into the core three years ago and nobody documented it.

Without Clean Core, every SAP release costs you. Your team tests custom code, adapts it, fixes what broke. Every single time.

With Clean Core, an SAP release is just a deployment. You test your extensions against the API contract, which SAP keeps backwards-compatible. Upgrades that used to take months now take days. That’s not an exaggeration.

Over three to five years, the savings compound properly. Less time on maintenance means more time building features that actually grow your business.

FAQ

What if my extension needs data from the SAP core?

CAP extensions call SAP’s REST APIs to read and write data. For real-time events (e.g., “new opportunity created”), SAP Event Mesh delivers notifications to your extension. You never access the core database directly.

Can existing customisations be migrated to Clean Core?

Yes, but it’s a refactoring effort, not a lift-and-shift. Custom ABAP or in-core modifications need to be rebuilt as CAP services. The business logic stays the same. The architecture changes.

Does Clean Core work for Commerce Cloud too?

Commerce Cloud uses a different extension model (extensions and AddOns in the type system) but the principle is identical: keep customisations in well-defined extension points rather than modifying core code. For frontend extensions, the Composable Storefront’s Angular dependency injection pattern enforces separation.

Is CAP the only option for Clean Core extensions?

No. You can build extensions with any technology that calls SAP’s APIs: Node.js, Java, Python, or even low-code on SAP Build. CAP is SAP’s recommended framework because it handles auth, data modelling, and SAP connectivity out of the box. We use it because it’s the fastest path to production-grade extensions. But it’s not the only path.

How does Clean Core affect my SAP support?

SAP supports the core product. Custom code inside the core can void parts of that support. Clean Core extensions sit outside the core, so SAP support applies fully to the standard product. You support your own extensions separately. Fair enough: that’s a cleaner arrangement for everyone.