agentsclimarketplace
Sign in

Atc cloudification

Skill likweitan/abap-skills/skills/atc-cloudification

Configure 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 code to ABAP Cloud. Triggers include "configure ATC cloud readiness", "set up clean core check", "cloudification repository URL", "released APIs check", or "which JSON file for my S/4HANA version".From its SKILL.md

Install
npx -y skills add likweitan/abap-skills --skill atc-cloudification

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • fetches URLsInstructs the agent to fetch 3 URLs, including https://raw.githubusercontent.com/SAP/abap-atc-cr-cv-s4hc/main/src/objectReleaseInfoLatest.json and 2 more.

SKILL.md

5.3 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

ATC Cloudification Repository Check

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.

Overview

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.

Quick Reference

Read references/quick-reference.md for:

  • JSON file URLs for each target product and version
  • ATC check variant configuration steps
  • Available JSON files and their purpose
  • SAP Notes required for setup

Configuration by Target Product

SAP Cloud ERP

  1. Activate in your ATC check variant: "Cloud Readiness" → Usage of Released APIs (Cloudification Repository)
  2. In the check attributes, enter the URL: 
    https://raw.githubusercontent.com/SAP/abap-atc-cr-cv-s4hc/main/src/objectReleaseInfoLatest.json

SAP Cloud ERP Private

  1. Activate in your ATC check variant: "Clean Core" → Usage of Released APIs (Cloudification Repository)
  2. In the check attributes, enter the URL for your version:
    • Latest version: https://raw.githubusercontent.com/SAP/abap-atc-cr-cv-s4hc/main/src/objectReleaseInfo_PCELatest.json
    • Specific release: Replace PCELatest with the version, e.g. PCE2025_0 for Release 2025 FPS00

New Clean Core Check (Note 3565942)

For 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

Clean Core Levels and API State Mapping

Custom objects are assigned Clean Core levels, while SAP objects are categorized into states. The mapping is:

Clean Core LevelAPI StateMeaning
Level AReleasedAllowed in ABAP Cloud developments (language version "ABAP for Cloud Development")
Level ADeprecatedStill usable in ABAP Cloud, but a newer recommended API exists and should be preferred
Level BClassic APIUsable only in standard ABAP developments (language version "Standard ABAP"), not in ABAP Cloud
Level CNot to be releasedNot permitted in ABAP Cloud developments, but a successor API is available and should be used instead
Level DNo APINot usable in ABAP Cloud, and also not recommended for standard ABAP developments

Key rules

  • Level A (Released): Use these APIs for all new ABAP Cloud development. These are the target.
  • Level B (Classic API): Permitted for clean core extensions in standard ABAP only. Use the wrapper pattern (Tier 2 RFC proxy) to bridge to ABAP Cloud when no Level A successor exists.
  • Level C (Not to be released): A successor API exists — migrate to the successor.
  • Level D (No API): Avoid entirely. No successor is planned.
  • Deprecated: Technically still Level A, but plan migration to the newer replacement API.

JSON files and states

  • objectReleaseInfo*.json files contain states: released, deprecated, notToBeReleased, notReleased
  • objectClassifications*.json files contain states: classicAPI, noAPI, internalAPI
  • Labels: remote-enabled (RFC-enabled), transactional-consistent (suitable for RAP-based applications)

Workflow

  1. Determine the target product: SAP Cloud ERP or SAP Cloud ERP Private
  2. Identify the correct JSON file using the quick reference
  3. Verify prerequisites: Ensure required SAP Notes are implemented
  4. Configure ATC check variant with the appropriate check and JSON URL
  5. Run ATC checks on custom code to identify usage of unreleased APIs
  6. Review findings and plan remediation using successor API information and the level mapping above

Cloudification API Viewer

Use the online viewers to browse released APIs interactively:

What ships with it: 1 file

10.6 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most quality gates skills give in ~1.1k tokens

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

  • Read full output and check exit codein 45 of 1524, across 40 files
  • Verify output confirms the claimin 44 of 1524, across 39 files
  • Identify the command that proves the claimin 43 of 1524, across 39 files
  • Execute the full verification commandin 36 of 1524, across 30 files
  • Produce a verification reportin 34 of 1524, across 18 files
  • Review git diff changesin 30 of 1524, across 16 files
  • Fix build failures immediatelyin 29 of 1524, across 9 files
  • Group findings by severityin 28 of 1524
  • State claim only with evidencein 27 of 1524, across 22 files
  • Verify regression tests with red-green cyclein 26 of 1524, across 22 files
  • Run the full test suitein 26 of 1524, across 25 files
  • Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

  • Determine the target product
  • Identify the correct JSON file
  • Verify required SAP Notes are implemented
  • Configure ATC check variant with JSON URL
  • Run ATC checks on custom code

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.