Cloudification Repository Viewer
A browser form over the Cloudification RepositoryCloudification RepositorySAP's list of released APIs for SAP Cloud ERP, with the successors of the objects that are not released — the content the ABAP test cockpit's cloud readiness and clean core checks are pointed at.sap official, abap, the list SAP publishes of which standard objects are released for ABAP Cloud and what replaces the ones that are not.
SAP publishes the Cloudification RepositoryCloudification RepositorySAP's list of released APIs for SAP Cloud ERP, with the successors of the objects that are not released — the content the ABAP test cockpit's cloud readiness and clean core checks are pointed at.sap official, abap as JSON files that say which standard objects are released for ABAP Cloud, and what to use where one is not; this loads one of them in a browser page. Which one is a choice: the latest On-Premise or Public Cloud state, a fix-pack level of On-Premise 2022 or 2023, or On-Premise 2025, with 'Latest' carrying the most objects by the documentation's own account. Object, module and state then narrow what the page lists, and the states are the repository's own — Released for an object cleared for use in ABAP Cloud, Deprecated for one released but flagged in ADT, Not to be Released for one that has a successor or a wrapper instead, Stable for one SAP leaves unreleased but no longer changes. Where ROSAROSAAnswers whether an SAP object is released for ABAP Cloud, and what to use instead when it is not — served from SAP's own Cloudification Repository over MCP and over plain REST.independent, abap serves the same repository to an agent over MCP, this is the copy a person reads by hand.
Where it sits
Who is behind it
Before choosing this
Conditions
PracticalFunctional boundary
Not for an automated check: the answer arrives as a page in a browser, so a rule that has to run over a codebase, or an agent mid-task, needs the repository as data rather than as a form.
What it declares
Every artifact
- Type
- Web tool
- Origin
- Independently maintained
As a web tool
- Access
- does not say
- What it sends to its vendor
- does not say
Connections
Whether code can run in ABAP Cloud, and what to do when it cannot
SAP's list of released APIs for SAP Cloud ERP with successors
SAP's list of released APIs for SAP Cloud ERP with successors
Download
Others providing
Compare all 11 on the ABAP Cloud readiness page →- abap-cloud-guiabap-cloud-guiA report-style programming model for abap2UI5: one class produces a selection screen with a WRITE list or an ALV grid, running as a UI5 app on ABAP Cloud as well as on NetWeaver 7.02.independent, abapReport-style programming model for abap2UI5 on ABAP Cloud
- codepagecodepageA polyfill class, ZCL_ABAP_CODEPAGE, that converts strings to binary and back behind one interface, where Clean Core blocks CL_ABAP_CODEPAGE and older systems lack CL_ABAP_CONV_CODEPAGE.independent, abapPolyfill for CL_ABAP_CODEPAGE under Clean Core
- Modernization Agents for SAP on AWSModernization Agents for SAP on AWSAWS's suite of agents for SAP modernisation work: custom ABAP converted for S/4HANA, PI/PO interfaces moved to Integration Suite, BW objects moved to SAP Datasphere, deployed into a customer's own AWS account and reached only after registration.partner, abapAWS agents for ABAP, PI/PO and BW modernisation work
- ROSAROSAAnswers whether an SAP object is released for ABAP Cloud, and what to use instead when it is not — served from SAP's own Cloudification Repository over MCP and over plain REST.independent, abapMCP server answering whether SAP objects are released for ABAP Cloud
- Cloudification RepositoryCloudification RepositorySAP's list of released APIs for SAP Cloud ERP, with the successors of the objects that are not released — the content the ABAP test cockpit's cloud readiness and clean core checks are pointed at.sap official, abapSAP's list of released APIs for SAP Cloud ERP with successors
- code pal for ABAP — Cloud Editioncode pal for ABAP — Cloud EditionThe same Clean ABAP check set for ABAP Cloud, where the legacy edition cannot run.sap official, abapClean ABAP check set for ABAP Cloud
- Clean-Core.ioClean-Core.ioA free hosted workspace that reads one piece of custom ABAP, redraws its business process as BPMN with a line anchor on every element, grades the SAP objects it uses Level A–D and ends in a keep, rebuild, move-to-standard or retire decision.independent, abapHosted workspace redrawing custom ABAP as BPMN and grading it
- Clean Core MeasurementClean Core MeasurementAn ABAP application for a central ATC system that imports Clean Core check results and reports them per system as Level A to D KPIs, technical debt scores and documented assignments.independent, abapReports Clean Core ATC results per system as Level A to D KPIs
- ABAP Select ConverterABAP Select ConverterConverts a classic Open SQL SELECT against dictionary tables to the equivalent statement against released Core Data Services entities and their fields.independent, abapConverts classic Open SQL SELECTs to released CDS entities
- abap-system-fieldsabap-system-fieldsAn ABAP Cloud class that wraps SY system fields and calendar-date functions behind an injectable instance, so code that reads them stays stable under unit tests.independent, abapInjectable wrapper for SY fields and date functions in ABAP Cloud
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
Flavors
“The Cloudification Repository is part of the new ABAP Cloud development model and lists released standard APIs that can be used to build the TIER 1 layer.” — Software-Heroes — CRV Documentation, Introduction
History in the atlas
- The documentation's Introduction places what the viewer shows in one flavor: "The Cloudification Repository is part of the new ABAP Cloud development model and lists released standard APIs that can be used to build the TIER 1 layer." Neither page states a standard ABAP use, so that flavor is left unstated.
- SAP's Cloudification Repository entered the graph, so the repository this reads is a node rather than a name in a sentence. Both edges rest on the viewer's own documentation: the repository "lists released standard APIs that can be used to build the TIER 1 layer", and the Repository field is a "Selection of the different release statuses that are made available by SAP in different JSON files". No protocol, direction or condition: the documentation states none.
- Entered from software-heroes.com's tools page, as the first artifact_type web-tool in the corpus alongside xexer-abap-select-converter, xexer-cds-field-mapping, xexer-odata-batch-creator and xexer-xlf-translator.
- First seen.
For your agent
- Ref
artifact:xexer-cloudification-repository-viewer- JSON
- /artifacts/xexer-cloudification-repository-viewer.json
- MCP
- Connecting an agent