agentleFS
Sign inStart free
williamcorrea23williamcorrea23/sap-router-skill/.agents/skills/atc-cloudification/SKILL.md

atc-cloudification

Skill1 starsChanged 4 months agoMITView on GitHub

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".

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify prerequisites: Ensure required SAP Notes are implemented

    line 78
  2. Distinctive:

    Use the online viewers to browse released APIs interactively:

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free