SAP BTP · Clean Core
Clean Core BTP Extension Strategy
Every Z-program that stays in the core is technical debt that blocks AI. The extension strategy determines where each capability lives — and how it connects back without breaking your upgrade path.
Clean core is DEBCOR's practice area — not a methodology checkbox. We classify your custom code footprint, architect the extension model, and build the BTP extensions and RAP objects that move each Z-program off the core. We also deploy the AI agents that clean core makes possible.
Not sure where your clean core posture stands?
DEBCOR's free AI Readiness Assessment evaluates your landscape immediately — custom code footprint, BTP foundation readiness, data quality, and AI readiness score. 15 minutes. No sales pitch. The clean core analysis is built in.
The extension model
Three Tiers. Every Extension Has a Home.
The extension strategy classifies every custom requirement into one of three tiers. The classification drives the build approach, the governance model, and the timeline.
Side-by-Side Extensions on BTP
Custom applications, AI agents, and integrations built on SAP BTP — outside the S/4HANA core entirely. Technology choice is open: Java, Node.js, Python, LangGraph, n8n. Connects to S/4HANA via APIs and events. Zero impact on the core upgrade path.
- Custom Joule agents and AI automation
- BTP-native applications and UIs
- Integration Suite iFlows and event-driven workflows
- Payment and commerce extensions
DEBCOR's primary BTP engineering practice — where most new capability lives.
RAP/ABAP Extensions on BTP
Clean-core ABAP development using the RESTful Application Programming Model (RAP) on the ABAP Environment on BTP. Custom business logic written in modern ABAP that follows SAP's extension framework — upgrade-safe, natively connected to S/4HANA data, maintainable.
- Custom business logic and validations
- Z-program replacements in clean-core ABAP
- SAP-standard extension points and BADIs
- Side-by-side ABAP services
DEBCOR's founder wrote the first ABAP textbook. 30 years of ABAP depth, now applied to RAP.
Z-Program Remediation
Existing Z-programs classified against three outcomes: retire (standard SAP now covers it), remediate (rewrite to upgrade-safe ABAP without BTP migration), or migrate (rebuild as Tier 1 or Tier 2 extension). This classification is one of the most time-sensitive pre-migration activities.
- Custom code impact analysis
- ABAP cleanup and modernisation
- Z-program retirement where SAP standard applies
- Pre-migration custom code strategy
DEBCOR's Custom Code Remediation practice is a dedicated service — not bundled into migration.
Clean core and AI readiness
Clean Core Is the Prerequisite for SAP's AI Roadmap
Every capability SAP announced at Sapphire 2026 — Joule agents, the Autonomous Enterprise, the Knowledge Graph, AI Agent Hub — runs on BTP and requires a governed, well-architected BTP foundation to deploy against. Organisations with Z-programs still modifying the core cannot adopt SAP's AI roadmap on SAP's own timeline. The extension strategy is not a future-state aspiration — it's the current blocker.
Clean core → AI agents deploy faster
When extensions live on BTP with clean API and event interfaces, deploying a new Joule agent or AI automation is a BTP build — not an S/4HANA modification. The extension framework, data access patterns, and governance architecture are already in place. New AI capabilities slot in without a transport or core change.
AI agents accelerate clean core migration
DEBCOR uses AI to accelerate the clean core migration itself — AI-assisted custom code analysis classifies Z-programs faster, AI data cleansing prepares master data for the extension model, and AI-powered migration cockpit tooling compresses the timeline from classification to go-live. The two programmes reinforce each other.
Where clean core programmes stall
The Z-Program Problem Has to Be Solved Before Cutover
Custom code is the most common reason S/4HANA migrations stall — not because the migration is complex, but because the custom code scope was never properly classified. DEBCOR's clean core approach starts the Z-program analysis before the migration plan is finalised.
~30%
Retire
SAP S/4HANA standard now covers the functionality. The Z-program is retired — no rebuild required. Often the largest category, and the fastest win.
~40%
Remediate
Rewrite to upgrade-safe ABAP without moving to BTP. Clean-core ABAP patterns, extension point adoption, SPAU/SPDD resolution.
~30%
Migrate to BTP
Rebuild as a side-by-side BTP extension or RAP object. These are the Z-programs that represent genuine custom capability worth preserving as a first-class extension.
Percentages are representative ranges from DEBCOR engagements — actual distribution varies by landscape age and customisation depth.
Frequently Asked Questions
What is clean core BTP extension strategy?
Clean core BTP extension strategy is the architectural discipline of extending SAP S/4HANA without modifying the digital core. Every customisation, integration, and custom application lives outside the core — on SAP BTP as a side-by-side extension, as a clean-core RAP/ABAP object, or as a BTP-native AI agent — connected via APIs and events. This preserves the S/4HANA upgrade path and is the prerequisite for SAP's AI roadmap.
How do I know if my SAP landscape is clean-core ready?
DEBCOR's AI Readiness Assessment at catalyst.debcor.com evaluates your landscape's clean core posture immediately — analysing data quality, custom code footprint, BTP foundation readiness, and AI readiness. Results in 15 minutes. It identifies which Z-programs need to move to BTP extensions before S/4HANA cutover or AI agent deployment.
What is the difference between a side-by-side extension and a RAP extension?
A side-by-side extension is a full application or agent built on SAP BTP that connects to S/4HANA via APIs and events — no ABAP required, full technology choice. A RAP extension (RESTful Application Programming Model) is clean-core ABAP inside the ABAP Environment on BTP — custom business logic written in modern ABAP that follows SAP's extension framework, is upgrade-safe, and connects natively to S/4HANA data.
How do AI agents fit into a clean core extension strategy?
AI agents are the most important clean-core extension category in SAP's current roadmap. Joule agents, custom AI agents, and automation workflows all run on BTP — outside the S/4HANA core, connected via APIs and events. A clean core extension strategy that accounts for AI from the start deploys agents significantly faster: the extension framework, data access patterns, and governance architecture are already in place.
What happens to existing Z-programs in a clean core migration?
Z-programs fall into three categories: retire (functionality now standard in S/4HANA), remediate (rewrite to be upgrade-safe without BTP migration), or migrate to BTP (rebuild as side-by-side extension or RAP object). DEBCOR classifies every Z-program before migration and builds the extension strategy for those that must move. This classification should start before the migration plan is finalised.
Start with the free clean core assessment.
DEBCOR's AI Readiness Assessment scores your clean core posture and AI readiness in 15 minutes — no setup, no sales pitch, immediate results. If the score reveals blockers, we can discuss what the extension strategy looks like for your specific landscape.