ABAP Cloud & Clean Core · Clean Core Object Guard
Call to a function module not released for cloud development
- Default severity
- Critical
- Finding code:
- CLEAN_CORE_UNRELEASED_API
- Engine version:
- 2.2.0
What this finding means
Clean Core Object Guard reports this finding with the default severity “Critical”.
About the engine: Tier 1/2/3 extensibility classification & classic modification detector
How to fix it
Replace the call with the released successor named in the finding (Cloudification Repository). Function modules absent from the released list must be treated as unreleased until SAP releases them.
How ERP Preflight detects it
The analysis is deterministic: the same exported files and the same knowledge snapshot always produce the same findings. No SAP system connection is required — you upload exports.
- Engine
- Clean Core Object Guard
- Accepted formats
- ABAP, ZIP, JSON
- What to export
Custom ABAP source (report, class, function group include), an abapGit repository ZIP containing *.abap files, or an object list JSON {'objects': [{'name', 'type': TABL|FUNC|CLAS|DDLS}]} for release-status lookup.
- Required input
- ABAP source with at least one statement, an abapGit ZIP, or an object list
- Evidence
- Each finding points to the artifact path, line and column, the code snippet and the SHA-256 of the uploaded file. Findings without such a pointer are demoted to confidence UNKNOWN.
- Confidence
- Up to VERIFIED (1.0) when the finding rests on Knowledge-graph released-object snapshot (configuration.released_objects); at most RULE_DERIVED (0.85) when it rests on Released / not-released object snapshot.
- Knowledge sources
- Released / not-released object snapshot — curated, not verified against the source
- Knowledge-graph released-object snapshot (configuration.released_objects) — verified against the official source
- Target releases of the engine
- S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Related findings
- BlockerDirect write to an SAP standard table
- CriticalDirect read of an SAP standard table
- CriticalObsolete or cloud-forbidden ABAP statement
- CriticalUse of a class not released for cloud development
- MajorUse of a deprecated SAP object
- MajorDynamic call target cannot be verified
Terms used on this page
Background reading
- Clean core extensibility explained: tiers, released APIs and classic modificationsA practical overview of how SAP classifies extensions by their upgrade stability, from ABAP Cloud on released APIs to classic modifications, and how to assess existing custom code.