Transports · Transport Dependency Analyzer
Object imported before or without a type it references
- Default severity
- Major
- Finding code:
- TR_TYPE_REFERENCE_SEQUENCE_RISK
- Engine version:
- 2.1.0
What this finding means
Transport Dependency Analyzer reports this finding with the default severity “Major”.
About the engine: CTS transport sequence & cross-transport dictionary dependency validator
How to fix it
Import the transport containing the referenced DDIC type (data element, structure, table type, domain) or class/interface type first, or bundle both objects in one transport of copies; otherwise the using object fails the import syntax check.
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
- Transport Dependency Analyzer
- Accepted formats
- JSON, CSV, XML
- What to export
CTS transport metadata: CSV export of E070/E071/E071K with a TRKORR header row, JSON {'transports': {TRKORR: ['TABL ZTAB', …]}, 'e070': [...], 'e071': [...], 'call_references': [...], 'seometarel': [...], 'wbcrossgt': [...], 'planned_sequence': [...]}, XML with <E070>/<E071> sections, or the cloud-aware gCTS / abapGit adapter JSON {'adapter': 'GCTS', 'commits': [{id, parents, timestamp, objects | files}], 'planned_sequence': [commit ids]}.
- Required input
- At least one transport request (or gCTS / abapGit commit) with its object list
- 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 SEOMETAREL relation types / program include naming (structural relation semantics), a curated catalog that is not verified against an official source.
- Knowledge sources
- SEOMETAREL relation types / program include naming (structural relation semantics) — curated, not verified against the source
- Target releases of the engine
- S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Related findings
- BlockerCircular dependency between transports
- CriticalSubclass or implementing class imported before or without its superclass / interface
- CriticalObject locked in multiple concurrent transports
- CriticalOlder object version overtakes a newer one
- MajorCaller imported before the object it references
- MajorCustomizing imported before its DDIC structure
Terms used on this page
Background reading
- Transport dependencies: why imports fail or break production in the wrong orderHow dependencies between transport requests arise, what happens when a transport is imported without its predecessors, and how to check sequencing before an import.