Extensions · Extension Impact Guard
No active consumers in the supplied graph
- Default severity
- Info
- Finding code:
- EXT_SAFE_TO_DELETE
- Engine version:
- 2.0.0
This is an informational finding: it confirms a state or documents a change and needs no fix.
What this finding means
Extension Impact Guard reports this finding with the default severity “Info”.
About the engine: Cloud BAdI & key-user extensibility upgrade stability analyzer
How to fix it
Deletion is safe with respect to the supplied inventory only; confirm the inventory is complete for the target system, then delete via Key-User Extensibility and transport the deletion.
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
- Extension Impact Guard
- Accepted formats
- JSON
- What to export
Extension inventory JSON: {'extensions': [{object_name, object_type, status, dependencies, data_type, length, software_collection}], 'dependencies': {object: [consumers]}, 'target_object': '…', 'action': 'DELETE'|'MODIFY'|'CHANGE_TYPE'|'CHANGE_LENGTH'|'TRANSPORT', 'change': {new_type, new_length}}. Deletion / change / transport verdicts require an explicit target_object.
- Required input
- extensions or dependencies/graph adjacency map
- target_object for deletion/impact verdicts
- 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 () and is capped by that source’s verification status.
- Target releases of the engine
- S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Related findings
- CriticalDeletion blocked by active consumers
- BlockerCyclic extension dependency
- CriticalType / length change breaks consumers
- MajorHigh change blast radius
- MajorModification impacts downstream consumers
- MajorRequested extension object absent from the dependency graph
Terms used on this page
Background reading
- Custom fields with key user extensibility: why a field does not appear in the app, form or APIHow custom fields created with key user extensibility reach UIs, reports, forms and APIs, and why a field that exists on one document is missing on the follow-on document.
- 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.