onedevatlasBeta
Browse the atlas
AllABAPBTPCAPUI5
Web toolWeb tooltypeA hosted utility you use at a URL, rather than run or install. May be free or paid; source_available says whether anything behind it is inspectable.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →Reference

Cloudification Repository

SAP'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.

A custom-code audit has to know which SAP objects a cloud system still allows and what replaces the ones it does not, and that is a list SAP keeps rather than something a checker can work out. This repository is that list: one JSON file per target product (objectReleaseInfoLatest.json for SAP Cloud ERP, objectReleaseInfo_PCELatest.json and the per-release PCE files for SAP Cloud ERP Private, objectClassifications_SAP.json for the data format the August 2025 checks need), with CSV versions for offline processing in a spreadsheet tool. You use it by activating the ATC check and entering the raw URL of the file in the check attributes, which is why the S/4 system needs SSL set up to reach git; the SAP Notes under Requirements are what bring the checks themselves into a system. The Cloudification API Viewer browses the same files at sap.github.io, one URL per target product, and a row with a double arrow opens the successors. Partners generate a JSON for their own namespace with report SYCM_API_CLASSIFICATION_MANAGR and offer it as a pull request, which is the only contribution the repository accepts.

GitHub167 ★
Homepage

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
ABAP
Provides
ABAP Cloud readinessABAPABAP Cloud readinesscapabilityWhether 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.
Serves
BTP/BAIP
Flavors
ABAP CloudStandard ABAP
Requires
GitHubGitHuboutside the atlasThe ATC check reads the object list from the repository's raw URL, so the system running the check needs SSL set up to reach git.

Who is behind it

SAPSAPOrganisationMaintains this
In the atlas: maintains 137, wrote 14@SAPmaintainerAjinkya PatilPersonContributes to this
In the atlas: contributes to 112@ajinkyapatil8190Albert MinkPersonContributes to this
In the atlas: maintains 1, contributes to 8@albertminkChristoph ClausPersonContributes to this
In the atlas: contributes to 1@chrisclaus11Daniel HuserPersonContributes to this
In the atlas: contributes to 1@daniel-huserGuidoJagerPersonContributes to this
In the atlas: contributes to 1@GuidoJagerNicolas HuberPersonContributes to this
In the atlas: contributes to 2@huber-nicolasJonas SobottaPersonContributes to this
In the atlas: contributes to 2@jonassobottaLars HvamPersonContributes to this
In the atlas: maintains 13, contributes to 92, wrote 1@larshpMarkusPersonContributes to this
In the atlas: contributes to 3@Markus1812Markus MalenkePersonContributes to this
In the atlas: contributes to 1@mmalenke22 contributors

Before choosing this

Conditions

PracticalFunctional boundary

It is a catalogue of SAP's objects and not a reading of your code: it states that an object is not released, never that you used it, and the finding is the ATC check's. For SAP Cloud ERP Private the files exist for feature pack stack releases only, with no update per support package, so a system between two stacks is checked against its stack's file.

What it declares

Every artifact

Type
Web tool
Origin
By SAP
Use as
A reference

As a web tool

Access
does not say
What it sends to its vendor
does not say

Connections7

Download
Cloudification Repository connectionsCloudificationRepositoryPROVIDES→ provides1provides stated Publishes which SAP Cloud ERP objects are released and, for the objects that are not, the successor to use, as the content the ATC check "Usage of Released APIs (Cloudification Repository)" reads to analyse existing custom code on ECC and S/4HANA releases. SAP/abap-atc-cr-cv-s4hc — README: https://github.com/sap/abap-atc-cr-cv-s4hc SAP/abap-atc-cr-cv-s4hc — README: https://github.com/sap/abap-atc-cr-cv-s4hcABAP Cloud readinessUSED BY← connected from1connected from derived The release-status JSON files: the Repository field picks one of the statuses SAP publishes there, and the tool loads it. Through: inverted from its connects edge Software-Heroes — CRV Documentation, Form Input: https://software-heroes.com/en/crv-documentation Software-Heroes — CRV Documentation: https://software-heroes.com/en/crv-documentationCloudification Repository Viewer← needed by3needed by derived to grade every SAP object the code uses as clean core Level A–D Through: inverted from its requires edge clean-core.io README: https://github.com/sonnyfrenzel-rgb/clean-core.ioClean-Core.ioneeded by derived Without the repository there is nothing to show: the released standard APIs the page lists, and the successors beside them, are the repository's content. Through: inverted from its requires edge Software-Heroes — CRV Documentation, Introduction: https://software-heroes.com/en/crv-documentation Software-Heroes — CRV Documentation: https://software-heroes.com/en/crv-documentationCloudification Repository Viewerneeded by derived the catalogue of released SAP objects and their successors that ROSA searches and classifies, from the [Cloudification Repository](artifact:sap-abap-atc-cr-cv-s4hc) Through: inverted from its requires edge rosa README: https://github.com/clementringot/rosaROSANEEDS→ connects to1connects to stated The S/4 system reaches this repository's hosted files via git to feed the ATC Cloud Readiness/Clean Core check with the released-API JSON. abap-atc-cr-cv-s4hc README: https://github.com/sap/abap-atc-cr-cv-s4hcSAP S/4HANA→ needs1needs stated The ATC check reads the object list from the repository's raw URL, so the system running the check needs SSL set up to reach git. SAP/abap-atc-cr-cv-s4hc — README, Requirements: https://github.com/sap/abap-atc-cr-cv-s4hcGitHub

README

quoted from SAP/abap-atc-cr-cv-s4hc under Apache-2.0, read
SAP/abap-atc-cr-cv-s4hc/README.mdOn GitHub

SAP Cloud ERP - Released & Classic API list for ATC Cloud Readiness/Clean Core Check (Cloudification Repository)

REUSE status

The repository contains the list of released APIs of SAP Cloud ERP. In addition also the objects that are not released are contained with the specification of successor objects. All objects are contained in one JSON file. This file is used as content for the ABAP Test Cockpit Check "Usage of Released APIs (Cloudification Repository)". This check can be used by customers and partners to analyse existing custom code concerning the usage of released and not released APIs on all ECC and S/4HANA releases. The check is available in SAP BTP, ABAP environment in an latest version.

Requirements

Following the Cloud Readiness approach: Please implement

  • note "ATC Check for Github Repo: 3284711
  • note "Fix error in ATC Check" 3377462
  • note "own released objects support" 3507814

Following the Clean Core approach:

  • for SAP Cloud ERP Private only: Classic APIs support -note 3449860
  • Validate SimplificationitemDB - Using transaction SYCM: Menu Simplification Database - Show Information. Follow the update information in note note 2241080
  • ATC Checks
    • 'Usage of APIs' - Support Classic and Released APIs
    • 'Usage of Released APIs (Cloudification Repository)' - Support Released APIs
  • note function group fix 3710789

Clean Core Check (Since August 2025)

  • ATC Checks "Usage of APIs" and "Allowed Enhancement Technologies" 3565942

Please ensure SSL setup to access git from S/4 system via ATC 3582797 - ATC Check "Usage of APIs": SSL Handshake Failed

Partner Extensions

Partner are able to offer released APIs as part of the extension shipment. Customer will be able to consume the released APIs as part of customer ABAP Cloud development. In case partner wants to offer Classic APIs to support customers to follow a clean core strategy. Please implement note Classic API Support in ATC Check "Usage of APIs" for Partners and use Report SYCM_API_CLASSIFICATION_MANAGR to generate your partner JSON file. Ensure it follows the right JSON structure and includes only objects in own namespace. Every namespace needs it own JSON filename format objectClassifications_NAMESPACE.json. As part of a pull request, the file will be offered in folder src/partner if it is wished by partner.

Download and Usage

Target product SAP Cloud ERP

  1. Activate in your ATC check variant the check "Cloud Readiness" -> Usage of Released APIs (Cloudification Repository)

  2. In the attributes of the check enter the URL to this git repository e.g https://raw.githubusercontent.com/SAP/abap-atc-cr-cv-s4hc/main/src/objectReleaseInfoLatest.json (content valid for SAP Cloud ERP)

Optional: Use another json file with a different content. For SAP Cloud ERP, please use the same URL above and attach the current file objectReleaseInfoLatest.json

The corresponding CSV files can be consumed for offline processing in any spreadsheet tool.

Target product SAP Cloud ERP Private

  1. Activate in your ATC check variant the check "Clean Core" -> Usage of APIs (Cloudification Repository)

  2. In the attributes of the check enter the URL to this git repository e.g https://raw.githubusercontent.com/SAP/abap-atc-cr-cv-s4hc/main/src/objectReleaseInfo_PCELatest.json (content valid only for the latest SAP Cloud ERP Private version)

For SAP Cloud ERP Private or on-premise, you can use the release version file with the string PCE included. e.g. https://raw.githubusercontent.com/SAP/abap-atc-cr-cv-s4hc/main/src/ + filename

SAP Cloud ERP Private; example Release 2025 FPS00 --> https://raw.githubusercontent.com/SAP/abap-atc-cr-cv-s4hc/main/src/objectReleaseInfo_PCE2025.json Remark: The Json files are available for Feature pack stack releases of Cloud ERP Private only. No dedicated support packages update on jason files.

With the note 3449860- ATC Checks 'Usage of APIs' and 'Usage of Released APIs (Cloudification Repository)' support for Classic APIs

With the note 3489660- “Enable deployment into UI5 ABAP Repository with language version "ABAP for Cloud Development" using development namespaces”

With the introduction of the new ATC check 3565942 - ATC Checks "Usage of APIs" and "Allowed Enhancement Technologies" [https://me.sap.com/notes/3565942] a new data format is needed and persited in file objectClassifications_SAP.json

Looking for >20000 Level A released dataelements for SAP Cloud ERP Private.

Object Types Considered by RISE with SAP Methodology Dashboard is listed in the SAP Note 3761018 [https://me.sap.com/notes/3761018]

Cloudification API Viewer

  • New layout of cloudification repository viewer - Blog
  • Cloudification Viewer will display now the number of APIs behind the repository name.
  • Supporting partner classic APIs now (Partner Level A APIs will available as part of the partner addon installation)

SAP Cloud ERP

SAP Cloud ERP Private

SAP Cloud ERP Private - Classic API Clean Core Model

Click on a row with a double arrow to get more details about successors

Related projects

Classic APIs to used as wrapper to bridge ABAP Cloud Use filter value: classic API + label: transactional-consistent

Use the wrapper generator https://github.com/SAP-samples/tier2-rfc-proxy with details on https://community.sap.com/t5/technology-blogs-by-sap/how-to-generate-a-wrapper-for-function-modules-bapis-in-tier-2/ba-p/13692790#M172258

LLM Support for SAP APIs

In pilot mode we support the brand new TOON format and offer a more compressed version of Classic APIs in objectClassifications_SAP.toon with a compression optimization of 18,3% Released API in objectReleaseInfo_PCELatest.toon going down from 3659440 to 2989644 tokens.

How to obtain support

This project is provided "as-is", with no expected changes or support. Of course you can always report bugs via GitHub issues. Request for new APIs please use the corresponding CI channel for

Contributing

This project is provided "as-is" and is mirroring the state as it is used in the SAP Cloud Platform ABAP Environment product, therefore we will only accept bug reports for the repository viewer but unfortunately we can't accept any pull requests from customers. Partner products with own namespace will receive a possibility to contribute via pull requests for own classic APIs JSONs.

Licensing

Copyright 2020-2025 SAP SE or an SAP affiliate company and abap-atc-cr-cv-s4hc contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.

Apache-2.0, read

Others providing2

Compare all 3 on the ABAP Cloud readiness page →
ABAP Cloud readiness
  1. Modernization Agents for SAP on AWSAWS agents for ABAP, PI/PO and BW modernisation work
  2. ROSAMCP server answering whether SAP objects are released for ABAP Cloud

Details

Sources3
GitHub APIdiscovered herechecked
github.com/SAP/abap-atc-cr-cv-s4hctree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

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
discovered viaGitHub API
first seen in the atlas
ecosystem and domainabap, operations-and-runtime
Flavors2
ABAP Cloud
“Customer will be able to consume the released APIs as part of customer ABAP Cloud development.” — SAP/abap-atc-cr-cv-s4hc — README, Partner Extensionschecked
Standard ABAP
“This check can be used by customers and partners to analyse existing custom code concerning the usage of released and not released APIs on all ECC and S/4HANA releases.” — SAP/abap-atc-cr-cv-s4hc — READMEchecked
Contributors22
Ajinkya PatilAlbert MinkChristoph ClausDaniel HuserGuidoJagerNicolas HuberJonas SobottaLars HvamMarkusMarkus Malenkemprevathiorhangoektas-sapBjörn Panterppm230590prasanth23590revathimp25Michael SchneiderSebastian WolfthfiedlerLukas LeistenKatharina Laubensteinyalcingurleksap

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:sap-abap-atc-cr-cv-s4hc
JSON
/artifacts/sap-abap-atc-cr-cv-s4hc.json
MCP
Connecting an agent