Run any Skill in Manus with one click

atc-cloudification

Stars27

Forks11

UpdatedApril 1, 2026 at 13:29

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

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

likweitan

likweitan/abap-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name

atc-cloudification

description

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

Activate in your ATC check variant: "Cloud Readiness" → Usage of Released APIs (Cloudification Repository)

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

Activate in your ATC check variant: "Clean Core" → Usage of Released APIs (Cloudification Repository)
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 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

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

Determine the target product: SAP Cloud ERP or SAP Cloud ERP Private
Identify the correct JSON file using the quick reference
Verify prerequisites: Ensure required SAP Notes are implemented
Configure ATC check variant with the appropriate check and JSON URL
Run ATC checks on custom code to identify usage of unreleased APIs
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:

SAP Cloud ERP: https://sap.github.io/abap-atc-cr-cv-s4hc/
SAP Cloud ERP Private: https://sap.github.io/abap-atc-cr-cv-s4hc/?version=objectReleaseInfo_PCELatest.json
Classic API Clean Core Model: https://sap.github.io/abap-atc-cr-cv-s4hc/?version=objectClassifications_SAP.json

More from this repository

same repository

btp-diagram-generator

likweitan/abap-skills

Generate SAP BTP (Business Technology Platform) solution architecture diagrams as native draw.io (.drawio) files following the official SAP BTP Solution Diagram guidelines (Fiori Horizon design system) and open them via a configured draw.io MCP server. USE WHEN: user asks to create/draw/design/sketch a BTP diagram, BTP architecture, BTP landscape, BTP solution diagram, BTP reference architecture, SAP Business Technology Platform diagram, or wants to visualize SAP BTP services (CAP, Build, Integration Suite, SAC, AI Core, HANA Cloud, Cloud Foundry, Kyma, Workzone, etc.) and their interdependencies in draw.io / drawio / diagrams.net. DO NOT USE FOR: non-BTP architecture diagrams, generic flowcharts, sequence/UML diagrams, or diagrams that should remain in Mermaid/PlantUML.

2026-07-1427

clean-abap

likweitan/abap-skills

Check ABAP code for compliance with Clean ABAP principles. Use this skill when users ask to check, validate, review, or analyze ABAP code for clean code compliance, code quality, best practices, or adherence to Clean ABAP guidelines. Triggers include requests like "check this ABAP code", "is this clean ABAP", "review my ABAP for clean code", "validate ABAP against clean code principles", or "analyze ABAP code quality".

2026-07-1427

sap-fiori-apps-reference

likweitan/abap-skills

Generate SAP Fiori Launchpad URLs from app names using AppList.json. Looks up app information by name and constructs proper FLP URLs with required parameters like sap-client and sap-language.

2026-07-1427

abap-unit-testing

likweitan/abap-skills

Help with ABAP Unit testing including test class setup, assertions, test doubles, mocking frameworks, dependency injection, CDS test environments, SQL test environments, RAP BO test doubles, and test fixtures. Use when users ask about ABAP unit tests, test classes, test methods, CL_ABAP_UNIT_ASSERT, test doubles, mocking, CDS test environment, SQL test environment, RAP testing, ABAP test injection, test seams, behavior-driven testing, TDD in ABAP, test isolation, or writing automated tests for ABAP code. Triggers include "write a unit test", "create test class", "mock a dependency", "test a CDS view", "test a RAP BO", "test double", "assertion", "test fixture", "test isolation", or "ABAP unit".

2026-04-1727

rap

likweitan/abap-skills

Help with RAP (RESTful ABAP Programming Model) development including behavior definitions, EML statements, managed and unmanaged BOs, draft handling, actions, validations, determinations, side effects, and business events. Use when users ask about RAP, BDEF, BDL, EML, behavior definitions, behavior pools, managed BO, unmanaged BO, draft-enabled BO, RAP actions, RAP validations, RAP determinations, RAP side effects, RAP business events, create/read/update/delete in RAP, or building transactional Fiori apps with ABAP Cloud. Triggers include "create a RAP BO", "write a behavior definition", "EML syntax", "managed vs unmanaged", "enable draft", "add an action", "add a validation", "RAP handler method", or "RAP saver class".

2026-04-1727

abap-cloud-migration

likweitan/abap-skills

Help with migrating classic ABAP custom code to ABAP Cloud including custom code adaptation, identifying unreleased API replacements, generating wrapper classes for unreleased objects, ATC Cloud Readiness checks, handling incompatible language constructs, and step-by-step migration workflows. Use when users ask about migrating to ABAP Cloud, custom code migration, cloud readiness, unreleased API replacement, wrapper pattern, ATC cloud checks, code adaptation, classic to cloud migration, S/4HANA cloud migration, or clean core compliance. Triggers include "migrate to ABAP Cloud", "cloud readiness check", "unreleased API", "replace with released API", "custom code adaptation", "wrapper for unreleased", "ATC cloud", "clean core migration", "move to tier 1", or "ABAP Cloud compatibility".

2026-04-1727

name

atc-cloudification

description

ATC Cloudification Repository Check

Overview

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

Activate in your ATC check variant: "Cloud Readiness" → Usage of Released APIs (Cloudification Repository)

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

Activate in your ATC check variant: "Clean Core" → Usage of Released APIs (Cloudification Repository)
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 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

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

Determine the target product: SAP Cloud ERP or SAP Cloud ERP Private
Identify the correct JSON file using the quick reference
Verify prerequisites: Ensure required SAP Notes are implemented
Configure ATC check variant with the appropriate check and JSON URL
Run ATC checks on custom code to identify usage of unreleased APIs
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:

SAP Cloud ERP: https://sap.github.io/abap-atc-cr-cv-s4hc/
SAP Cloud ERP Private: https://sap.github.io/abap-atc-cr-cv-s4hc/?version=objectReleaseInfo_PCELatest.json
Classic API Clean Core Model: https://sap.github.io/abap-atc-cr-cv-s4hc/?version=objectClassifications_SAP.json