brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
atc-cloudificationConfigure ATC Cloud Readiness and Clean Core checks using the SAP Cloudification Repository for Released APIs. Use when users ask about ATC check variants for cloud readiness, clean core compliance, released API checks, cloudification repository setup, objectReleaseInfo JSON files, SAP Cloud ERP or SAP Cloud ERP Private API validation, or migrating custom c…
Independent GitHub snapshot · Automated classification · Original documentation governs
Configure the ABAP Test Cockpit (ATC) check "Usage of Released APIs (Cloudification Repository)" to validate custom code against SAP's released API list for SAP Cloud ERP and SAP Cloud ERP Private.
The SAP Cloudification Repository contains the list of released and unreleased APIs for SAP Cloud ERP. The JSON files from this repository are used as content for the ATC check, enabling customers and partners to analyse existing custom code for released API usage across all ECC and S/4HANA releases.
Read references/quick-reference.md for:
https://raw.githubusercontent.com/SAP/abap-atc-cr-cv-s4hc/main/src/objectReleaseInfoLatest.json
https://raw.githubusercontent.com/SAP/abap-atc-cr-cv-s4hc/main/src/objectReleaseInfo_PCELatest.jsonPCELatest with the version, e.g. PCE2025_0 for Release 2025 FPS00For the newer ATC checks "Usage of APIs" and "Allowed Enhancement Technologies", use:
https://raw.githubusercontent.com/SAP/abap-atc-cr-cv-s4hc/main/src/objectClassifications_SAP.json
Custom objects are assigned Clean Core levels, while SAP objects are categorized into states. The mapping is:
| Clean Core Level | API State | Meaning |
|---|---|---|
| Level A | Released | Allowed in ABAP Cloud developments (language version "ABAP for Cloud Development") |
| Level A | Deprecated | Still usable in ABAP Cloud, but a newer recommended API exists and should be preferred |
| Level B | Classic API | Usable only in standard ABAP developments (language version "Standard ABAP"), not in ABAP Cloud |
| Level C | Not to be released | Not permitted in ABAP Cloud developments, but a successor API is available and should be used instead |
| Level D | No API | Not usable in ABAP Cloud, and also not recommended for standard ABAP developments |
objectReleaseInfo*.json files contain states: released, deprecated, notToBeReleased, notReleasedobjectClassifications*.json files contain states: classicAPI, noAPI, internalAPIremote-enabled (RFC-enabled), transactional-consistent (suitable for RAP-based applications)Use the online viewers to browse released APIs interactively: