Migration & Clean Core
SAP ECC to cloud migration blockers
ECC2Cloud Navigator reads usage and interface inventories of a legacy system and classifies each transaction, interface and object: successor available, extension needed, redesign or blocker.
Detected by:ECC2Cloud Navigator
Documented problems
- BlockerIDoc type not supported in the cloud target
ECC_IDOC_UNSUPPORTED_BLOCKER
- BlockerClassic transaction prohibited in S/4HANA Cloud
ECC_TCODE_NO_EQUIVALENT_BLOCKER
- CriticalLegacy object has no equivalent in the cloud target
ECC_OBJECT_NO_EQUIVALENT
- MajorUnreleased BAPI / RFC interface
ECC_BAPI_RFC_UNRELEASED_BLOCKER
- MajorLegacy object needs a cloud extension
ECC_OBJECT_EXTENSION_REQUIRED
- MajorLegacy object requires process redesign
ECC_OBJECT_PROCESS_REDESIGN
- MajorCustom Z/Y transaction needs Clean Core review
ECC_TCODE_CUSTOM_CODE_REVIEW
- MajorTransaction requires process redesign or is not in the cloud catalog
ECC_TCODE_OBSOLETE_REDESIGN
- MinorLegacy object could not be assessed automatically
ECC_OBJECT_NEEDS_REVIEW
- MinorReleased successor replaces the legacy object
ECC_OBJECT_SUCCESSOR_AVAILABLE
Informational findings
These findings confirm a good state or document a change. They are listed for completeness and are not problems.
- InfoReleased API successor for BAPI/RFC interface
ECC_BAPI_RFC_MODERNIZATION_FOUND
- InfoIDoc interface has an event / API successor
ECC_IDOC_MODERNIZATION_EVENT_MESH
- InfoLegacy object is directly supported in the cloud target
ECC_OBJECT_DIRECTLY_SUPPORTED
- InfoFiori / cloud successor available for transaction
ECC_TCODE_SUCCESSOR_FOUND
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.