Skip to content
Tutorials Center
My learning

Topics

Lesson 24 of 36 ยท Basis and Administration

Transports and the System Landscape

Learn the SAP three-system landscape (DEV, QAS, PRD), clients, transport requests, SE09, STMS, import order and common transport errors with a runnable stand-in.

SAP Basis is the team and the set of tools that keep SAP systems running: installing them, connecting them, patching them and moving changes between them. One of the most important Basis ideas is that you never change a production system directly. Changes (a new report, a configuration setting, a new table) are built in a development system, tested, and then transported to production in a controlled way.

SAP cannot run on this site, so this lesson describes the transactions you would use and gives you a labelled JavaScript stand-in to practice the logic of transport ordering.

The three-system landscape

flowchart LR
  D["DEV<br/>Development"] -->|"release + import"| Q["QAS<br/>Quality / Test"]
  Q -->|"import after approval"| P["PRD<br/>Production"]

Changes flow in one direction only. A fix needed in production is made in DEV and transported through QAS.

  • DEV: developers and consultants build and configure. Test data is unreliable.
  • QAS (quality assurance): testers verify the change with realistic data.
  • PRD: the live system. Only transports that passed QAS arrive here.

Large companies add a sandbox (free experiments, never transported) and a pre-production system. Each system has a three-letter SID (system ID), for example S4D, S4Q, S4P.

Clients

Within one SAP system there are clients (three digits, such as 100 or 200), which are separate business worlds sharing one installation. Each client has its own master and transaction data and its own users. Data is in tables with a MANDT (client) key field.

Data kind Is client dependent? Example
Customizing (configuration) Mostly yes Payment terms, company codes
Master and transaction data Yes Customers, orders
Repository objects (programs, tables definitions) No ABAP reports, data dictionary

Repository objects are valid for all clients in a system; that is why a program written in client 100 is also visible in 200.

Change recording and transport requests

When you change something in DEV, SAP asks for a transport request (a package of changes). There are two kinds:

  • Workbench request: repository objects (reports, tables, classes). Number format S4DK900123 (SID + K + 6 digits).
  • Customizing request: client-dependent configuration, recorded when you work in the IMG (SPRO).

Each request has tasks (one per developer). The flow:

  1. You work and save objects into a task of a request.
  2. You release the task and then the request (in SE09 or SE10), which writes it to the transport directory as data and co-files.
  3. The Basis administrator, or an automatic job, imports it into the target system with STMS (Transport Management System): STMS > Import Overview > pick system > queue.
  4. The import log shows return codes: 0 (OK), 4 (warning), 8 (error), 12 and higher (serious).

Key tcodes

Tcode Purpose
SE09 / SE10 Transport Organizer: own requests
SE01 Transport Organizer (extended view)
STMS Transport Management System: import queues, landscape
SCC4 Client settings (changes allowed or not)
SPRO IMG: configuration
SM30 Maintain table views

Import order matters

Transports can depend on each other. If request 2 uses a table created in request 1, importing 2 first fails. Basis therefore imports in the order released, never picking requests at random. An object list check (SE09 > Display objects) shows what a request contains, and warnings like "object is locked in another request" tell you that an object is already in an unreleased request.

JS Stand-in: transport queue and dependencies

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Return codes and common errors

JS Stand-in: reading transport return codes

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Typical problems:

  • Missing dependency (the example above).
  • Object locked in a different request, so you cannot transport your change.
  • Wrong client (a customizing request imported into a client where it should not apply).
  • Transport sent but client is not open for change: SCC4 prevents changes in a production client.

Beyond classic transports

  • Transport of copies moves objects without releasing the original.
  • Quality gates and approval in the target system keep untested changes out of PRD.
  • Change and Transport System plus gCTS (Git-enabled CTS) and ChaRM (Change Request Management in SAP Solution Manager) add Git-based flows and approvals. New projects on S/4HANA often combine CTS with these.
  • Business changes such as Fiori app configuration and BTP extensions have their own deployment pipelines but follow the same "build, test, then promote" principle.

Understanding this discipline also helps you think about users: who may do what is the topic of Users, Roles and Authorizations.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. In which system are changes normally created?

    Changes are built in DEV, tested in QAS, then imported into PRD.
  2. 2. Which transaction manages import queues across the landscape?

    STMS is the Transport Management System. SE09/SE10 manage requests in the source system.
  3. 3. Repository objects such as ABAP programs are...

    Programs and table definitions live in the repository, which is client independent.
  4. 4. What does return code 8 in an import log mean?

    RC 8 and above signal errors and need investigation.

Summary

  • The standard landscape is DEV, QAS, PRD, and changes travel in one direction.
  • Clients separate business data inside one system; repository objects are shared.
  • Workbench and customizing requests are released in SE09/SE10 and imported with STMS.
  • Import order and return codes are the key checks.
  • Never change production directly.

Next: Users, Roles and Authorizations