BlogBlogA post on somebody's own site or a community platform. Nobody edits it after publication, so it dates from the day it was written.See every one →SAP Community
ABAP development under the Clean Core paradigm: From BAPIs to BO and CDS
SAP's Level Based Clean Core classification (2025) grades ABAP APIs A through D by cloud readiness, and this piece uses the S/4HANA Cloudification Repository's own count — of 3,847 BAPI function modules for SAP Cloud ERP Private, only 23 are Level A — to show how much Classic API (Level B) code needs to move to RAP business objects instead. A worked Bank Master example matches each BAPI to its EML statement or ABAP CDSABAP CDSThe modelling layer of ABAP Cloud — view entities, projections and annotations defined above database tables, delivered with the platform rather than installed.sap official, abap SELECT equivalent, and states when that move is actually required: mandatory once on SAP Public Cloud, optional but advisable on Private Cloud/On-Premise as BAPIs stop gaining new fields.
Where it sits
Explains
ABAP Cloud readinessABAPABAP Cloud readinessWhether code can run in ABAP Cloud — released APIs only, no direct table access, no obsolete statements — and what to do with the code that cannot.
Source
reachable
Who is behind it
Lutzi3Lutzi3Wrote this
In the atlas: contributes to 1, wrote 1@Lutzi3author
In the atlas: contributes to 1, wrote 1@Lutzi3author
Properties
About this work
In topics
The atlas is now in betaTopic, edition 1
onedevatlas is open for browsing. Find tools for SAP development, compare their documented capabilities, ask your AI assistant, and join a flight during TechEd week.
Group by10 of 10 pieces
Piece, what it offersStill applies
CCM - Calculate Key FiguresCCM - Calculate Key FiguresExplains how the Clean Core Measurement (CCM) project turns ABAP Test Cockpit findings into the Technical Debt Score shown on its Clean Core Dashboard: messages from the ABAP_CLEAN_CORE_READINESS check are weighted by severity level (B/C/D) and summed per object, while the object's overall classification follows its highest message level rather than the point total. Covers where the calculation can be tuned — configurable weights, an exemption process, and additional metrics for documented but unreleased API use — and how the resulting score and classification drive the object list and per-object processing views.Björn S., published 2026-08-05
050: Clean Core Measurement (Preview)050: Clean Core Measurement (Preview)Walks through Clean Core Measurement (CCM), an open-source tool for tracking ABAP Cloud readiness across a system landscape: a dashboard showing Cloud Ready and Upgrade Stable status and a Technical Debt Score per system, runs recorded under administration, and a process area where custom APIs not released by SAP can be documented and excluded from the score. Reporting breaks the score down to individual objects, the unreleased APIs behind them, and which team or product cluster carries the most outstanding work.Björn S., published 2026-08-03
Recommendations for Wrapper Interface DesignRecommendations for Wrapper Interface DesignWalks through designing a wrapper interface that encapsulates a classic BAPI (BAPI_USER_GET_DETAIL) behind a C1-released interface, so the code released for ABAP Cloud stays limited to types and structures ABAP Cloud can actually access. Covers when a non-released SAP structure can still be referenced safely, when it cannot, and how the API_CONSISTENCY and API_COMPATIBILITY ATC checks catch the difference before an upgrade breaks it.kaidehmann, published 2026-06-25
ARC-1 with Joule Studio: Bringing Real ABAP System Context into JouleARC-1 with Joule Studio: Bringing Real ABAP System Context into JouleBrings the same BTP-deployed ARC-1 endpoint into Joule through a Joule Studio, classic edition agent configured with Anthropic Claude Sonnet 4 and two MCP servers, ARC-1 and mcp-sap-docs, for work that starts in SAP where the previous part started in Microsoft 365. Two read-only showcases carry the ABAP Cloud readiness edge: a clean core check of one class that reports it is not released, uses USR02 and BUT000 directly and has no ATC findings, and a modernisation backlog for package ZSD_LEGACY which, as that package did not exist, grouped 28 ZSD* objects into risk buckets instead. The route through SAP Integration Suite API Management or a future MCP gateway is presented as a target architecture and not yet a productive setup, because Joule Studio's documentation requires streamable HTTP destinations and does not support MCP servers that need interactive OAuth user authorisation.published 2026-05-06
ARC-1 with Joule Studio: Bringing Real ABAP System Context into Joule
arc-1 has been through 2 major lines since this was published: 0.9 (2026-05), 1 (2026-07). Affects Runnable code.
Object Release State in Cloudification Repository Viewer for Clean Core ExtensibilityObject Release State in Cloudification Repository Viewer for Clean Core ExtensibilityWalks through the five release states the Cloudification Repository Viewer assigns to an object — Released, Deprecated, Classic API, Not to be Released, and No API — and what each means for ABAP Cloud readiness: the clean core level it maps to and the ATC check priority it triggers. Explains why the same object can carry two states at once, such as a Classic API that later also becomes Released, and why the check has to be run against the specific release being developed on rather than assumed to hold across releases.PrasanthPadmanabhan, published 2026-03-20
Taking Control of Clean Core: When to Use Project Kernseife in addition to Standard SAP ToolsTaking Control of Clean Core: When to Use Project Kernseife in addition to Standard SAP ToolsWalks through how SAP's standard path classifies custom ABAP extensions into Clean Core Levels A through D, running ABAP Test Cockpit against the Cloudification Repository's release status for each SAP object an extension touches, then feeding results into the RISE with SAP Methodology Dashboard in SAP Cloud ALM. Contrasts that with Project Kernseife, an open-source custom ATC check that lets a team override SAP's classification with project-specific rules, define its own successor objects (including custom wrappers), and expose a Score and Potential Score per finding through a CDS view for prioritizing cleanup — at the cost of owning and maintaining that classification. States which situations favor each: Kernseife where the standard rules are too rigid for the project's reality, the standard dashboard where cross-system comparability and low maintenance effort matter more.LBretschneider, published 2025-11-04
Clean Core IndexClean Core IndexDescribes a company-built KPI, the Clean Core Index, that scores existing custom ABAP code by object type — reports, function modules, SAPScript/Smartforms, ATC S/4 readiness-check findings, user exits and modifications — each weighted by a severity the author sets for redesign effort and upgrade risk, with counts read off CDS views built for the purpose. The index is the author's own definition rather than an official one and does not by itself certify public-cloud readiness, but tracking it weekly shows where custom code still blocks a move to ABAP Cloud and lets progress be read per module or per object type.patrick_weber11, published 2025-08-15
Transitioning Architectures from SAP NetWeaverTransitioning Architectures from SAP NetWeaverA community contribution from Glencore, an SAP customer, on what replaces NetWeaver-based products as their standard maintenance ends in 2027: the scenarios where NetWeaver-era solutions fall short — integration with cloud-based landscapes, extensibility — and the successor options per use case, pointing at SAP's product availability matrix and note 1648480 for the official successors. Customer-authored, so the framing is a migration decision rather than a product description.published 2025-08-02
The journey with clean core continues for SAP Cloud ERP PrivateThe journey with clean core continues for SAP Cloud ERP PrivateClean core in SAP S/4HANA Cloud Private Edition as it stands in 2026: what is new in extensibility, new capabilities in the dashboard for the RISE with SAP Methodology, how AI helps make custom code compliant with clean core, and new guidance on data, integration and clean core in relation to SAP's API policy. The edges are to Extensibility, the concern the session is about, and to ABAP Cloud readiness, the concern behind making custom code compliant; the abstract names no tool for either and the dashboard is not held here. A TechEd 2026 session (Wednesday 28 October, Berlin; also TM108V, virtual), presented by Markus Goebel and Olga Dolinskaja, written here from SAP's abstract; the recording is not yet published.
Migrate and modernize your custom code using RISE with SAP and agentic AIMigrate and modernize your custom code using RISE with SAP and agentic AIThe Custom Code Migration Agent in SAP Joule for Developers, ABAP AI capabilities, shown on the RISE with SAP path that moves custom extensions from SAP ERP Central Component to SAP Cloud ERP Private: the abstract says the agent adapts the code through MCP tools and the AI for ABAP features in the custom code tools, and that the adapted code is then reworked along the clean core approach, the concern ABAP Cloud readiness covers. Which MCP tools, and what the clean core step changes in the code, the abstract leaves open. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Hitesh Bindal, Ingo Braeuninger, Jonas Helin of GitHub, Olga Dolinskaja and Thomas Fiedler, written here from SAP's abstract; the recording is not yet published.
Details
Graph
ABAP Cloud readinesscapability, core and community
SAP Communitypublishing source
SAP Communityabap-cloud-tag
SAP Communityabap-development-tag
SAP Communityabap-rap-tag
Source
Type
blog
Published on
Host
community.sap.com
Discovered via
First seen
History
- Entered the atlasDiscovered via SAP Community · abap-cloud-tag, SAP Community · abap-development-tag, SAP Community · abap-rap-tag.
For your agent
- Ref
content:abap-development-under-the-clean-core-paradigm-from-bapis-to-bo-and-cds- JSON
- /content/abap-development-under-the-clean-core-paradigm-from-bapis-to-bo-and-cds.json
- MCP
- Connecting an agent