Skip to content
ERP Preflight

Transport Dependency Analyzer

CTS / gCTS transport sequence, cross-transport dictionary and structural dependency validator

Content reviewed September 26, 2026

Engine
TRANSPORT_DEPENDENCY_ANALYZER
Domain
Release & Transport
Version
2.1.0
Target releases
S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Accepted formats
JSON, CSV, XML

Input contract

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
  • Structural relations: SEOMETAREL rows {clsname, refclsname, reltype} (0 interface composition, 1 interface implementation, 2 inheritance), WBCROSSGT rows {include, otype, name} (OTYPE 'TY' = type reference), or call_references with reference_type INHERITS_FROM / IMPLEMENTS / TYPE_REF.
  • Optional 'target_system_objects' ['CLAS ZCL_BASE', …] lists prerequisites already imported into the target; 'customer_namespaces' ['/ABC/'] extends the Z*/Y* customer namespace.

Finding codes

Finding codes (7)

  • TR_CIRCULAR_DEPENDENCY_DETECTEDDefault severity: BlockerCategory: RELEASE_AND_TRANSPORT

    Circular dependency between transports

    Remediation: Merge the mutually dependent requests into one transport of copies; circular requests have no valid import order.

  • TR_INHERITANCE_DEPENDENCY_RISKDefault severity: CriticalCategory: RELEASE_AND_TRANSPORT

    Subclass or implementing class imported before or without its superclass / interface

    Remediation: Import the transport (or deploy the commit) containing the superclass / interface first, or add it to the import queue; a class cannot be generated while its superclass or implemented interface is missing or outdated in the target (activation error, RC 8).

  • TR_OBJECT_COLLISIONDefault severity: CriticalCategory: RELEASE_AND_TRANSPORT

    Object locked in multiple concurrent transports

    Remediation: Consolidate the object's changes into one transport (or use ChaRM / cross-system object lock, CSOL); otherwise the later import silently overwrites the earlier version.

  • TR_OVERTAKER_DOWNGRADE_RISKDefault severity: CriticalCategory: RELEASE_AND_TRANSPORT

    Older object version overtakes a newer one

    Remediation: Do not import the older transport after the newer one (overtaker); re-sequence the queue or remove the object from the older request.

  • TR_CALL_DEPENDENCY_SEQUENCE_RISKDefault severity: MajorCategory: RELEASE_AND_TRANSPORT

    Caller imported before the object it references

    Remediation: Import the transport containing the referenced object first (adjust the STMS import queue / planned sequence) or bundle caller and callee in one transport of copies.

  • TR_CUSTOMIZING_AHEAD_OF_STRUCTUREDefault severity: MajorCategory: RELEASE_AND_TRANSPORT

    Customizing imported before its DDIC structure

    Remediation: Import the workbench request that creates/changes the table structure before the customizing request carrying its table entries (E071K).

  • TR_TYPE_REFERENCE_SEQUENCE_RISKDefault severity: MajorCategory: RELEASE_AND_TRANSPORT

    Object imported before or without a type it references

    Remediation: 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.

Input validation codes (5)

  • TR_ARCHIVE_REJECTEDDefault severity: MajorCategory: INPUT_VALIDATION

    Archive rejected by ingestion safety limits

    Remediation: The archive exceeded the 100:1 expansion ratio, 500 MB total size, entry-count or 2-level nesting limit, or contained path traversal / encrypted members. Upload a flat, unencrypted archive of the export files. No verdict was produced. Re-export the artifact in one of the formats accepted by Transport Dependency Analyzer (JSON, CSV, XML) and re-run the analysis.

  • TR_INVALID_INPUTDefault severity: MajorCategory: INPUT_VALIDATION

    Artifact does not match the engine input contract

    Remediation: Provide the artifact type documented for this engine; unrelated or structurally invalid documents are rejected. No verdict was produced. Re-export the artifact in one of the formats accepted by Transport Dependency Analyzer (JSON, CSV, XML) and re-run the analysis.

  • TR_PARSE_ERRORDefault severity: MajorCategory: INPUT_VALIDATION

    Artifact could not be parsed

    Remediation: Fix the syntax error at the reported line/column (or re-export the file unmodified from SAP). No verdict was produced. Re-export the artifact in one of the formats accepted by Transport Dependency Analyzer (JSON, CSV, XML) and re-run the analysis.

  • TR_PAYLOAD_TOO_LARGEDefault severity: MajorCategory: INPUT_VALIDATION

    Artifact exceeds the size limit

    Remediation: Split the export (e.g. per package, company code or date range) so each upload stays under the service payload limit. No verdict was produced. Re-export the artifact in one of the formats accepted by Transport Dependency Analyzer (JSON, CSV, XML) and re-run the analysis.

  • TR_INSUFFICIENT_INPUTDefault severity: InfoCategory: INPUT_VALIDATION

    Required input missing

    Remediation: Supply every input the engine's contract marks as required (see the engine catalog entry). No verdict was produced. Re-export the artifact in one of the formats accepted by Transport Dependency Analyzer (JSON, CSV, XML) and re-run the analysis.

Back to the documentation
Transport Dependency Analyzer — ERP Preflight Docs