Fit-to-standard gaps · SAP Gap Radar
Requirement met by standard scope item (tier 1)
- Default severity
- Info
- Finding code:
- GAP_RADAR_SUPPORTED_STANDARD
- Engine version:
- 1.2.0
This is an informational finding: it confirms a state or documents a change and needs no fix.
What this finding means
SAP Gap Radar reports this finding with the default severity “Info”.
About the engine: Fit-to-standard vs custom delta analyzer with Clean Core recommendations
How to fix it
Activate the SAP Best Practices scope item; do not build custom objects for this requirement.
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
- SAP Gap Radar
- Accepted formats
- JSON, TEXT
- What to export
Business / technical requirement statements: JSON {'requirements': [{'requirement': '…', 'scope_items': [...]}]}, {'requirement': '…'}, a JSON list, or plain text (one statement, or a bulleted / numbered / ID-prefixed list with one requirement per item).
- Required input
- At least one non-empty requirement statement
- Every statement must be an SAP business or technical requirement (SAP process, object, configuration or extensibility term); unrelated prose is rejected as GAP_RADAR_INVALID_INPUT
- 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
- At most RULE_DERIVED (0.85): the verdict rests on 12-tier Clean Core resolution keyword rules, a curated catalog that is not verified against an official source.
- Knowledge sources
- Identifier -> capability catalog (scope items, SSCUIs, IMG activities, released CDS views / APIs / BAdIs / events, not-released objects) — curated, not verified against the source
- 12-tier Clean Core resolution keyword rules — curated, not verified against the source
- Target releases of the engine
- S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Related findings
- CriticalRequirement implies a Clean Core violation (tier 11)
- MajorKnown product gap (tier 11)
- MinorRequirement only partially met by a supported approach
- MinorRequirement only met by a workaround (tier 10)
- MinorRequirement could not be classified (tier 12)
- InfoRequirement met by business events (tier 8)
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.
- From SPRO IMG customizing to SSCUIs and Central Business Configuration (CBC)How classic SPRO IMG customizing tables map to Self-Service Configuration UIs (SSCUIs) and Central Business Configuration in SAP S/4HANA Cloud, and how to spot unsupported table settings early.