Migration & Clean Core
SAP fit-to-standard gaps and Clean Core violations in requirements
SAP Gap Radar classifies requirement statements by how they can be met — standard, configuration, extensibility, released API, side-by-side — and flags gaps and Clean Core violations.
Detected by:SAP Gap Radar
Documented problems
- CriticalRequirement implies a Clean Core violation (tier 11)
GAP_RADAR_BLOCKED_CLEAN_CORE_VIOLATION
- MajorKnown product gap (tier 11)
GAP_RADAR_KNOWN_PRODUCT_GAP
- MinorRequirement only partially met by a supported approach
GAP_RADAR_PARTIAL
- MinorRequirement only met by a workaround (tier 10)
GAP_RADAR_SUPPORTED_WORKAROUND
- MinorRequirement could not be classified (tier 12)
GAP_RADAR_UNKNOWN_REQUIREMENT
Informational findings
These findings confirm a good state or document a change. They are listed for completeness and are not problems.
- InfoRequirement met by business events (tier 8)
GAP_RADAR_SUPPORTED_BUSINESS_EVENT
- InfoRequirement met by configuration (tier 2)
GAP_RADAR_SUPPORTED_CONFIGURATION
- InfoRequirement met by developer extensibility (tier 4/7)
GAP_RADAR_SUPPORTED_DEVELOPER_EXTENSIBILITY
- InfoRequirement met by key-user extensibility (tier 3)
GAP_RADAR_SUPPORTED_KEY_USER
- InfoRequirement met by released API (tier 6)
GAP_RADAR_SUPPORTED_RELEASED_API
- InfoRequirement met by released CDS views (tier 5)
GAP_RADAR_SUPPORTED_RELEASED_CDS
- InfoRequirement met side-by-side on SAP BTP (tier 9)
GAP_RADAR_SUPPORTED_SIDE_BY_SIDE
- InfoRequirement met by standard scope item (tier 1)
GAP_RADAR_SUPPORTED_STANDARD
Terms used in this area
Background articles
- 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.
ERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.