Basisbeginner
SAP Transport Management System (TMS)
How ABAP changes move safely from Development to Quality Assurance to Production through change requests and transport routes.
Changes are made in development and must reach production without anyone editing production directly. TMS is the mechanism that moves them.
A transport request is like a sealed shipping container listing exactly what's inside (which programs/configs changed); TMS is the shipping company's route map ensuring every container passes through the quality inspection port (QAS) before it's ever allowed into the destination warehouse (PRD).
Key Concepts
1
DEV ----> QAS ----> PRD
export import import2
A change is recorded, not saved. The first time you save an object in a client set to record changes,
the system asks for a transport request. From then on every change to that object goes into it.
3
A request holds one or more tasks — one per developer — so a team can work on the same request and each
person releases their own task first.
4
Two types, and the difference decides what moves.
Workbench request repository objects: programs, classes, DDIC.
Cross-client: affects every client in the system.
Customizing request configuration table entries.
Client-specific: only the client it was made in.5
Getting this wrong is a common incident: configuration made in the wrong client, or a customizing request
that arrives in production without the workbench request holding the field it depends on.
6
Release, then import. SE09 or SE10 releases a request, which exports it to files at operating-system
level. It then appears in the import queue of the next system in the route.
SE09SE10
7
STMS is where the routes are configured and where imports are run. Quality systems often import
automatically; production is imported deliberately, inside a change window.
STMS
8
Return codes are the thing to actually check.
0 imported successfully
4 imported with warnings <- read these
8 errors; objects may be missing
12 fatal; the import failed9
A code of 4 is the one that causes trouble, because the import looks green in a summary. It routinely means
a generated object did not activate, so the program in production is not the program that was tested.
10
Order matters, and cannot be recovered afterwards. Transports are applied in the sequence they are
imported. Import them in a different order than they were released and later changes can be overwritten by
earlier ones.
11
That is also why one large request per sprint is a bad habit: it cannot be partially imported, so one
broken object blocks everything else in it. Small requests, each holding one logical change, can be
sequenced and, if necessary, left behind.
12
The pieces of the landscape. One system is the domain controller, holding the TMS configuration for
all of them. A transport layer classifies which route an object follows, which is how a package of
custom objects can be routed differently from SAP's own.
13
The habits an interviewer listens for. Nothing goes to production without passing quality. Nobody
imports a single request out of sequence to fix something quickly. Import logs are read, not just checked
for green. And the object list of a request is reviewed before release, because an object that got picked
up by accident travels with it.
14
What the interviewer is probing.1. "Why does transport sequence matter?" Probing: the common outage cause. Stalls: "It does
not." Moves up: imports apply in order, so a transport containing a dependency imported after its
dependent leaves the system inconsistent.
15
2. "What is the difference between a workbench and a customizing request?" Probing: the
basics. Stalls: "Nothing." Moves up: workbench carries repository objects and is
client-independent; customizing carries client-specific configuration.
16
3. "What does return code 8 on an import mean?" Probing: practical reading. Stalls: "It
failed." Moves up: errors occurred and objects may be partially imported — it needs investigation
in the import log, not a retry.
17
4. "How do you handle a transport that must not go to production?" Probing: process
discipline. Stalls: "Delete it." Moves up: release it into a separate buffer or project, or use
transport of copies — never rely on remembering not to import it.