gCTS
git-enabled Change and Transport System
SAP’s integration of the ABAP Change and Transport System with Git repositories, so that ABAP changes can be versioned and distributed through Git.
With gCTS, the objects of a change are pushed as files to a Git repository, and target systems pull a commit to import the change. Branches and commit history then describe the state of each system.
Dependencies between objects still matter: importing a change without the objects it references causes the same activation errors as a classic import in the wrong order.
In ERP Preflight
ERP Preflight does not read Git repositories. Transport Dependency Analyzer works on exported CTS transport metadata (as CSV, JSON or XML).
Problems that involve gCTS
- 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
- MajorObject imported before or without a type it references
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.