ABAP Cloud & Clean Core · Clean Core Object Guard
Dynamic call target cannot be verified
- Default severity
- Major
- Finding code:
- CLEAN_CORE_DYNAMIC_CALL_UNVERIFIABLE
- Engine version:
- 2.2.0
What this finding means
Clean Core Object Guard reports this finding with the default severity “Major”.
About the engine: Tier 1/2/3 extensibility classification & classic modification detector
How to fix it
Dynamic targets (FROM (lv_tab), CALL FUNCTION lv_fm, CALL METHOD (…)) cannot be checked statically. Replace them with static calls, or restrict the possible values to released objects and document the allow-list; ABAP Cloud checks dynamic targets only at runtime.
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
- Each finding names the knowledge it relies on (Knowledge-graph released-object snapshot (configuration.released_objects)) and is capped by that source’s verification status.
- Knowledge sources
- 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
- CriticalCall to a function module not released for cloud development
- CriticalUse of a class not released for cloud development
- MajorUse of a deprecated SAP object
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.