Transport of copies
Transport of copies (ToC)
A transport request that carries copies of objects to a target system while the original change requests stay open.
A transport of copies contains the current versions of objects that belong to other, still open requests. It is used to move a development to a test system early, or to bundle objects from several requests so they arrive together.
The original requests are not affected: they are released and imported on their own schedule later.
In ERP Preflight
For requests that depend on each other in a circle, Transport Dependency Analyzer recommends merging them into one transport of copies; for a caller that would arrive before the object it references, it recommends importing the callee first or bundling both.
Problems that involve Transport of copies
- BlockerCircular dependency between transports
- MajorCaller imported before the object it references
- MajorObject imported before or without a type it references
- CriticalSubclass or implementing class imported before or without its superclass / interface
- CriticalObject locked in multiple concurrent transports
- CriticalOlder object version overtakes a newer one
- MajorCustomizing imported before its DDIC structure
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.