Clean core means your custom logic sits beside SAP, not inside it, so every SAP release installs without rework. It is required for GROW and best practice for RISE. We assess your custom code, build new extensions the upgrade-safe way and keep the core clean.
Clean core
custom logic beside SAP, not inside it
ABAP Cloud and RAP
upgrade-safe development inside S/4HANA and SAP Cloud ERP
CAP on SAP BTP
side-by-side apps that never block a release
Required for GROW
and best practice for RISE
Every line of custom code inside the core is a line someone must test at every upgrade. Clean core keeps what makes you different, without paying for it again with every release.
What clean core means
Your custom logic sits beside SAP and talks to it through released APIs, so every SAP release installs without rework.
What we deliver
Choose an area to see the problems we solve, what we deliver and the technology we use.
Custom code assessment
The problem
- Thousands of custom objects and no idea which are used
- Upgrades delayed by modifications
- Custom code that blocks the move to S/4HANA
What we deliver
- Inventory of custom code and how often it is used
- Checks with ABAP Test Cockpit and SAP Readiness Check
- A decision for each object: retire, replace with standard, move or fix
- A clean-core roadmap
- ABAP Test Cockpit
- SAP Readiness Check
- Custom Code Migration app
The result: Less custom code, and a clear plan for what is left.
ABAP Cloud and RAP
The problem
- Logic that must run inside the ERP
- Classic ABAP that breaks with upgrades
- No standard for new development
What we deliver
- Extensions in ABAP Cloud using only released APIs
- RAP business objects and OData services
- CDS views for reporting and apps
- Developer extensibility in SAP Cloud ERP and S/4HANA
- ABAP Cloud
- RAP
- CDS views
- ABAP Development Tools
The result: In-app extensions that survive every upgrade.
Side-by-side on SAP BTP
The problem
- New apps that don’t belong inside the ERP
- Processes that span SAP and non-SAP systems
- Logic that needs to scale on its own
What we deliver
- Apps built with CAP in Node.js or Java
- Connections to SAP through released APIs and events
- SAP HANA Cloud for app data
- CI/CD pipelines for every app
- CAP
- SAP BTP
- SAP HANA Cloud
- SAP Event Mesh
The result: New capability around SAP, with no impact on the core.
Fiori apps
The problem
- Users stuck on old SAP GUI screens
- Custom screens that are hard to maintain
- No mobile access
What we deliver
- Fiori elements apps on RAP and CAP services
- Custom SAPUI5 apps where needed
- Role-based launchpad set-up
- Accessible, mobile-ready design
- Fiori elements
- SAPUI5
- SAP Build Work Zone
The result: Modern, role-based screens built the upgrade-safe way.
Clean-core governance
The problem
- Every developer extends SAP in a different way
- No review before code goes live
- Clean core lost again after the project
What we deliver
- Extension guidelines: where each kind of change should go
- Code reviews and automated checks
- A design authority for new requests
- Regular clean-core health reports
- ABAP Test Cockpit
- SAP Cloud ALM
- Git and CI/CD
The result: A core that stays clean, release after release.
How we deliver
Assess
Custom code inventory and clean-core checks.
You get: A clean-core roadmap
Decide
Retire, replace, move or fix each object.
You get: Decisions with reasons
Build
ABAP Cloud, RAP, CAP and Fiori, to INK standards.
You get: Upgrade-safe extensions
Test
Automated checks and regression on every change.
You get: Proven quality
Govern
Guidelines, reviews and health reports.
You get: A core that stays clean
Where should new logic go?
1. Standard or configuration
Always the first choice. Most needs are met here.
2. Key-user extensibility
Fields, logic, forms and reports added in the system by trained key users, without code.
3. ABAP Cloud (on-stack)
Logic that must run inside the ERP, using only released, upgrade-safe interfaces.
4. SAP BTP (side-by-side)
New apps, complex processes and integrations that live beside SAP.
Classic customisation or clean core?
Classic customisation
- Modifications inside SAP code
- Every upgrade needs testing and rework
- Custom code grows every year
- Hard to move to the cloud
Clean core with INK
- Extensions beside SAP, through released APIs
- Upgrades install without rework
- Custom code reduced and governed
- Ready for GROW, RISE and SAP Cloud ERP
Related: Development Factory · SAP Business AI Platform & BTP · ECC to S/4HANA Migration · Hire SAP technical consultants
How clean is your core?
Tell us about your SAP system and its custom code. We’ll show you what can be retired, what should move, and how to keep it clean.
Frequently asked questions
What is clean core?
An approach where SAP's standard code stays untouched. Custom logic is built with key-user tools, ABAP Cloud or on SAP BTP, using only released interfaces, so upgrades install without rework.
Do we have to remove all our custom code?
No. We keep what adds value, retire what is unused, replace what the standard now covers, and move or fix the rest.
What is the difference between RAP and CAP?
RAP builds upgrade-safe apps and services inside S/4HANA and SAP Cloud ERP in ABAP. CAP builds side-by-side apps on SAP BTP in Node.js or Java.
Is clean core only for new projects?
No. Existing ECC and S/4HANA systems can move towards a clean core step by step, starting with a custom code assessment.