Migration & Clean Core
ABAP Cloud and Clean Core code problems
Clean Core Object Guard analyses custom ABAP code and classifies the SAP objects it references against released-object data from the knowledge snapshot.
Detected by:Clean Core Object Guard
Documented problems
- BlockerDirect write to an SAP standard table
CLEAN_CORE_DIRECT_DB_MUTATION
- CriticalDirect read of an SAP standard table
CLEAN_CORE_DIRECT_DB_ACCESS
- CriticalObsolete or cloud-forbidden ABAP statement
CLEAN_CORE_OBSOLETE_SYNTAX
- CriticalCall to a function module not released for cloud development
CLEAN_CORE_UNRELEASED_API
- CriticalUse of a class not released for cloud development
CLEAN_CORE_UNRELEASED_CLASS
- MajorUse of a deprecated SAP object
CLEAN_CORE_DEPRECATED_OBJECT_USED
- MajorDynamic call target cannot be verified
CLEAN_CORE_DYNAMIC_CALL_UNVERIFIABLE
- MajorReference to an object not in the released-object snapshot
CLEAN_CORE_UNRELEASED_OBJECT
- MajorType reference to a DDIC object not released for cloud development
CLEAN_CORE_UNRELEASED_TYPE_REFERENCE
Informational findings
These findings confirm a good state or document a change. They are listed for completeness and are not problems.
- InfoObject is released for cloud development
CLEAN_CORE_OBJECT_RELEASED
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.
ERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.