SAP Transport objects
Transports move configuration and development changes through the landscape (DEV → QAS → PRD). This guide outlines creating, releasing and importing them.
To transport a change, make it in DEV so it is recorded in a transport request, describe the request clearly with every related object in it, release the tasks and then the request, and Basis imports it into QAS through STMS and then into PRD in release order. Read the import log; return code 8 or higher means errors.
- Watch out: transports import in release order, so releasing out of sequence breaks the target system.
Step by step
- Make your change in DEV; it is recorded in a transport request (create/assign when prompted).
- Give the transport a clear description; add all related objects/tasks.
- Release the task(s) and then the request when the change is complete.
- Basis imports the transport into QAS (via STMS), where it is tested.
- After sign-off, the same transport is imported into PRD, in the correct sequence.
Notes and tips
Describe transports clearly and keep related changes together. Import in the same order they were released, dependencies matter, and out-of-sequence imports cause errors and inconsistencies. Never change production directly; everything flows via transports. Check import logs/return codes (8+ means errors).
Common pitfalls
- Following steps without understanding the concept.
- Skipping testing in a non-production system.
- Applying blindly to a different scenario.