New Cloudification Repository Viewer for Clean Cor...

Rundong_Liu · ‎2025 Oct 07

This blog is meant to be a quick read — the idea is to cover the new Clean Core Cloudification Repository Viewer (CRV) features over your morning coffee☕, and kick off a new day of your SAP Clean Core journey.

https://sap.github.io/abap-atc-cr-cv-s4hc/

I am an SAP Clean Core and Extensibility Lifecycle consultant, and I have supported many RISE with SAP customers in establishing Clean Core governance models, solution standardization boards (SSB), and extensibility development guidelines. Through various concrete use cases, I have gained extensive hands-on experience.

From the perspective of Clean Core development and governance, having a unified API repository is of critical importance.

After SAP released the Clean Core Extensibility White Paper and the New Clean Core Level concept, the Cloudification Repository Viewer has now also been updated with a new version, and I am very excited to share its new features with you right away.

SAP Product

In the filter bar, we will see the SAP Products: SAP Cloud ERP, SAP Cloud ERP Private, and SAP BTP ABAP Environment. If the system is SAP Cloud ERP Private, we select SAP Cloud ERP Private.

Release

After selecting SAP Cloud ERP Private, we will then see a Release option. Here, we can choose the Cloud ERP release version and the corresponding SP level. It is worth noting that as the Cloud ERP evolves, the number of available APIs is steadily increasing.

Partner Namespace

One particularly exciting development is the introduction of the “Partner Namespace.” With SAP Clean Core’s certification for partners, certified partners are now able to publish released APIs as well. In my view, this represents a significant step forward for the entire extensibility ecosystem.

State

Next is the “State” field, which is the most interesting part because the Clean Core levels are “hidden” here. This allows us to easily and clearly identify the level mapping.

Here, I would like to highlight a few points for clarification:

Custom objects are assigned levels, whereas SAP objects are categorized into states (for example, ‘Classic APIs,’ which place the extension in Level B).
Released → Allowed in ABAP Cloud developments (Level A).
Deprecated → Still usable in ABAP Cloud developments, but a newer, recommended API exists and should be preferred.
Classic API → Usable only in standard ABAP developments, not in ABAP Cloud (Level B).
Not to be released → Not permitted in ABAP Cloud developments, but a successor API is available and should be used instead.
No API → Not usable in ABAP Cloud, and also not recommended for standard ABAP developments (Level D).

Object Type / Software Component / Application Component

As in the previous version, filtering objects by Object Type, Software Component, or Application Component is also supported.

Label

Within the final Label field, additional details are available — for instance, APIs marked as “transactional-consistent” are suitable for use in RAP-based applications.

To summarize:

The new CRV interface has a clearer layout — first select the Cloud ERP version, then the release version, and then the state/level, which makes the process straightforward.
Released APIs, classic APIs, not-to-be-released APIs, and NO APIs can be presented in a single view, distinguished and filtered by State.
Clean Core levels are mapped to the states of SAP objects, simplifying the classification of custom code.
The Clean Core API framework is becoming increasingly standardized, with more and more Level A and Level B APIs available.
Partner APIs that have been certified are also being included, further expanding the extensibility ecosystem.
Object Type, Software Component, Application Component, and Label are still retained.

With the release of the new CRV version, I’m delighted to have another handy tool added to my Clean Core governance and extensibility development arsenal.

Of course, a single weapon is not enough — we also need to leverage all the Clean Core tools to deliver a true combination punch:

For Clean Core extensibility White paper, please refer to Whitepaper

For Clean Core ATC Checks, please refer to note 3565942

For Clean Core frameworks, technologies and development patterns, please refer to note 3578329

For SAP Build on BTP, please refer to SAP Build

For Clean Core Extensibility Guide, please refer to Extensibility Guide

For Clean Core governance services, intelligent custom code analysis and transformation, extensibility lifecycle management, and AI tools, please don’t hesitate to reach out to me. I’ll be more than happy to share more real project use cases!

Now you’ve probably finished your coffee. And I hope this quick overview has given you a clear taste of the new CRV features.

As a final note, please

don’t forget to upskill on SAP Build on BTP,
establish Clean Core Measurement Framework and KPIs
and always prioritize Fit-to-Standard and extension on Level A for new development use cases!

Let’s keep moving forward on the Clean Core journey — learning, improving, and building smarter together! 🍻

Thanks! 😊