SAP Cloudification
How to cloudify custom ABAP: move legacy code off unreleased objects onto released S/4HANA APIs, aligned with SAP Clean Core. Grounded in SAP's official Cloudification Repository.
Cloudifying SAP means making custom ABAP cloud-ready for S/4HANA: replacing direct access to standard tables and unreleased objects with SAP-released APIs and CDS views, and rewriting logic either in-app in ABAP Cloud (RAP) or side-by-side on SAP BTP (CAP). It follows SAP's Clean Core principle so extensions stay decoupled from the digital core and upgrades stay clean. There is no single SAP product called 'Cloudify'; the reference dataset that drives it is SAP's public Cloudification Repository, which maps legacy objects to their released successors.
What is SAP cloudification?
Cloudification is the work of making custom SAP ABAP cloud-ready — aligning it with SAP's Clean Core extensibility model so the digital core stays standard and upgradeable. In practice, it means replacing direct reads and writes on standard tables (VBAK, BSEG, LIKP…) and calls to unreleased objects with SAP-released APIs, CDS views and RAP business objects.
Logic that legitimately belongs on the core is rebuilt in-app in ABAP Cloud (RAP); logic that does not is decoupled into a side-by-side service on SAP BTP (CAP). The result is an extension layer that survives S/4HANA upgrades instead of breaking on them.
There is no SAP product literally called “Cloudify”. “Cloudify SAP” and “SAP cloudification” are informal names for making custom code cloud-ready and clean-core-compliant. The concrete asset SAP publishes for it is the SAP Cloudification Repository — the released-successor dataset that also backs SAP ATC’s clean-core checks.
How to cloudify SAP custom code
1. Assess the custom code
Run a deterministic ABAP static code analysis to inventory every standard object your code touches and flag risky table access, unreleased calls and modifications — as line-level evidence.
2. Map objects to released successors
Each object is resolved against SAP's Cloudification Repository (23,696 classified objects) plus curated field-level mappings — returning the released OData/CDS successor, or an honest “no released path” verdict.
3. Route: in-app RAP vs side-by-side CAP
Based on the degree of coupling, the router recommends rewriting the logic in-app in ABAP Cloud (RAP) or decoupling it as a side-by-side service on SAP BTP (Node.js CAP) — a recommendation for a qualified architect to sign off.
4. Draft the compliant version + evidence
The engine drafts the first clean-core-compliant RAP or CAP version with a multi-file abapGit export and ABAP-Unit tests, plus a signed audit evidence pack — a starting point to review, never a production-ready deliverable.
What blocks cloudification
Not every object has a clean path. The assessment is honest about what cannot simply be re-pointed:
- Objects with no released successor — flagged for re-architecture (e.g. a side-by-side extension), not force-fit to a fake mapping.
- Modifications, implicit enhancements and native SQL — the not-recommended patterns that break on upgrade.
- Dynamic ABAP, Dynpro / classic UI and BDC flows — need manual redesign rather than an automated lift-and-shift.
Clean-Core.io is a free community tool that accelerates this assessment — complementary to SAP ADT and ATC, which remain the authoritative checks.
From the Cloudification Repository
- 23,696 classified SAP objects
- Released successors, source-attributed
- Weekly auto-synced & versioned
- Same source that backs SAP ATC
Related Topics
Frequently Asked Questions (FAQ)
What is SAP cloudification?
SAP cloudification is the process of making custom ABAP cloud-ready for S/4HANA: replacing direct access to standard tables and unreleased objects with SAP-released APIs and CDS views, and moving logic to a clean-core-compliant model — in-app ABAP Cloud (RAP) or side-by-side on SAP BTP (CAP). The goal is a decoupled extension layer, so future upgrades stay clean.
How do you cloudify SAP custom code?
Assess each object your code touches against SAP’s released-object contract, replace unreleased calls with their released successors (OData/CDS/RAP BOs), and route the remaining logic to the right target: in-app ABAP Cloud (RAP) where it belongs on the core, or a decoupled side-by-side CAP service on SAP BTP where it does not. Objects with no released path are re-architected, not force-fit. Clean-Core.io automates the assessment and drafts the first compliant version for an architect to review.
Is “SAP Cloudify” an official SAP product?
No. There is no SAP product literally named “Cloudify.” “Cloudify” / “cloudification” is the informal verb for making SAP custom code cloud-ready and clean-core-compliant. The concrete reference dataset SAP publishes for it is the SAP Cloudification Repository, which maps thousands of legacy objects to their released successors and also backs the SAP ABAP Test Cockpit (ATC) clean-core checks.
What is the SAP Cloudification Repository?
The SAP Cloudification Repository is SAP’s public dataset that maps classic ABAP objects (tables, function modules, classes) to their released S/4HANA successors — the same source that backs ATC’s clean-core checks. Clean-Core.io syncs it weekly and layers curated field-level mappings on top, so an object lookup returns a released successor with its source layer and confidence.
Does cloudification mean rewriting everything?
No. Most custom code is decoupled rather than rewritten from scratch: direct table reads are re-pointed to released CDS views or OData APIs, and only genuinely coupled logic is re-implemented in RAP or moved side-by-side to CAP. Objects that truly have no released path are flagged for re-architecture — an honest limitation, surfaced as evidence, not silently ignored.