ECC to cloud migration · ECC2Cloud Navigator
Fiori / cloud successor available for transaction
- Default severity
- Info
- Finding code:
- ECC_TCODE_SUCCESSOR_FOUND
- Engine version:
- 2.2.0
This is an informational finding: it confirms a state or documents a change and needs no fix.
What this finding means
ECC2Cloud Navigator reports this finding with the default severity “Info”.
About the engine: Custom code remediation & obsolete transaction migration roadmap
How to fix it
Plan user adoption of the listed Fiori successor app and assign the business role/catalog; retire the classic transaction from roles.
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
- ECC2Cloud Navigator
- Accepted formats
- CSV, JSON, TEXT, ZIP
- What to export
Legacy landscape inventory: ST03N / SUIM usage CSV (TCode / Transaction / object_name column, optional ExecutionCount, AvgResponseTimeMs, UserCount, Module, Process, Owner), TADIR export (OBJECT, OBJ_NAME, DEVCLASS, AUTHOR), JSON rows {name, type, executions, module, process, owner} or typed lists {'img_items', 'tables', 'abap_objects', 'custom_objects', 'requirements'}, 'TCODE [count]' lines, or an abapGit repository ZIP (base64).
- Required input
- At least one transaction, interface, IMG activity, table, ABAP / custom object or requirement
- 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 ECC transaction -> Fiori/cloud successor catalog, a curated catalog that is not verified against an official source.
- Knowledge sources
- ECC transaction -> Fiori/cloud successor catalog — curated, not verified against the source
- SPRO/IMG -> SSCUI/CBC mapping catalog (shared with SPRO2Cloud) — curated, not verified against the source
- Released / not-released object snapshot (shared with Clean Core Object Guard) — curated, not verified against the source
- Gap Radar identifier -> capability catalog (requirements) — curated, not verified against the source
- Gap Radar tier keyword rules (requirements without resolvable identifiers) — curated, not verified against the source
- Target releases of the engine
- S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Related findings
- BlockerIDoc type not supported in the cloud target
- BlockerClassic transaction prohibited in S/4HANA Cloud
- CriticalLegacy object has no equivalent in the cloud target
- MajorUnreleased BAPI / RFC interface
- MajorLegacy object needs a cloud extension
- MajorLegacy object requires process redesign
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.