Transport request
Transport request (Change and Transport System)
Also known as: CTS, transport
The unit in which the SAP Change and Transport System (CTS) moves development and customizing changes between systems.
A transport request lists the objects (and, for customizing, table entries) of a change. Real changes rarely fit into one request: a program can depend on a data element, table field, class or customizing released in a different request.
Importing a request before its predecessor causes activation or generation errors (return code 8). Importing only part of a feature can succeed technically and then fail at runtime, and importing requests out of sequence can let an older object version overwrite a newer one.
In ERP Preflight
Transport Dependency Analyzer reads exported transport metadata (E070, E071, E071K) and reports missing predecessors, circular dependencies, object collisions and overtakers before the import.
Problems that involve Transport request
- MajorCustom field name violates key-user naming
- BlockerCyclic extension dependency
- MajorHigh change blast radius
- MajorCustom dependency not transported with the object
- CriticalChange pointers globally deactivated (BD61)
- CriticalMessage type change pointers inactive (BD50)
- BlockerCircular dependency between transports
- CriticalSubclass or implementing class imported before or without its superclass / interface
Related terms
Free tools
- Knowledge & error search
Search the reviewed knowledge base, SAP objects and the finding codes of the analysis engines.
Background articles
- 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.
Written for ERP Preflight · reviewed September 27, 2026
All glossary termsERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.