Transports
Transport administration is the operational side of moving changes through the landscape: importing transport requests into QAS and PRD in the right order, monitoring imports, and keeping the Transport Management System healthy. It is a core Basis duty.
Controlled, scheduled imports (rather than ad-hoc) and strict sequence discipline keep QAS and PRD consistent and changes traceable.
- While consultants and developers create and release transports in DEV, the Basis administrator manages the import side, using the…
- Every import produces a return code: 0/4 are success/warnings, while 8 or higher indicate errors that need investigation.
- Import transports into QAS and then PRD via STMS.
- Watch out: Importing out of sequence, inconsistencies result.
The administrator’s role
While consultants and developers create and release transports in DEV, the Basis administrator manages the import side, using the TMS (transaction STMS) to import queued transports into target systems, in sequence, at controlled times, and to verify each import’s result.
Key activities
- Import transports into QAS and then PRD via STMS.
- Maintain the correct import sequence (dependencies matter).
- Review import logs and return codes for errors.
- Configure and maintain transport routes and the domain controller.
Return codes and errors
Every import produces a return code: 0/4 are success/warnings, while 8 or higher indicate errors that need investigation. Reading import logs and resolving errors (often missing dependent transports or object conflicts) is everyday transport administration.
Discipline and scheduling
Controlled, scheduled imports (rather than ad-hoc) and strict sequence discipline keep QAS and PRD consistent and changes traceable. Good transport administration is much of what keeps a landscape stable.
Common pitfalls
- Importing out of sequence, inconsistencies result.
- Ignoring high return codes from imports.
- Ad-hoc, unscheduled imports into production.