Skip to content
Tutorials Center
My learning

Topics

Lesson 4 of 36 ยท SAP Architecture and Navigation

SAP Architecture: Three Tiers, Work Processes, Landscape and Clients

Understand SAP's three-tier architecture, dialog and background work processes, the DEV-QAS-PRD system landscape, transports and what a client is, with diagrams.

When you press Enter in SAP, a lot happens behind the screen. Knowing the pieces helps you understand slow screens, error messages, why changes are made in a development system, and what an administrator actually does. This lesson covers the technical architecture (three tiers), what runs inside the application server (work processes), and how companies organize several SAP systems into a landscape.

The three tiers

Classic SAP follows a three-tier client-server design:

  1. Presentation tier: what the user sees. SAP GUI on a PC, or a browser running Fiori.
  2. Application tier: one or more application servers that run the business logic (ABAP programs).
  3. Database tier: a database server that stores all data (SAP HANA in S/4HANA, or Oracle, SQL Server, DB2 and others in older systems).
flowchart LR
    U1["SAP GUI / Browser"] --> A1["Application server 1"]
    U2["SAP GUI / Browser"] --> A2["Application server 2"]
    A1 --> D[("Database server")]
    A2 --> D
    M["Message server"] -.-> A1
    M -.-> A2

Many users, several application servers, one database. A message server balances logons across servers.

Why split it? The database is the single source of truth and is hard to scale, so it is kept separate. Application servers are cheap to add: when more users arrive, you add another one. The presentation tier needs almost no resources.

Inside an application server: work processes

An application server runs a fixed number of work processes. Each one handles a request at a time. They come in types:

Type Short name Job
Dialog DIA Runs interactive user steps (one screen round trip)
Background BTC Runs scheduled batch jobs without a user
Update UPD Writes database changes made by a transaction, asynchronously
Enqueue ENQ Manages locks so two users cannot change the same record
Spool SPO Prepares print output
Gateway GW Communicates with other systems (RFC)

A dialog step has a time limit (often 10 minutes by default and configurable). Long jobs therefore run as background jobs, which you schedule and monitor rather than watch.

The lock managed by the enqueue process is why you see "Material 4711 is being processed by user JONES" when you open an object someone else is editing.

What happens on one click

  1. Your front end sends the request to a dispatcher.
  2. The dispatcher puts it in a queue and assigns it to a free dialog work process.
  3. The ABAP program runs, reads from the database (usually through a buffer in memory) and prepares a screen.
  4. The result goes back to your screen. The work process is released at once, so one process serves many users.
Python Stand-in: a dispatcher with a queue

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

This simplified model shows why more requests than work processes means waiting, which a user experiences as a slow system.

The system landscape: DEV, QAS, PRD

A company never changes its live system directly. A typical landscape has three systems, each with its own database:

  • DEV (development): consultants and developers configure and code.
  • QAS (quality assurance / test): testers verify changes with realistic data.
  • PRD (production): the live system for daily business.

Some companies add a sandbox (SBX) for experiments, a training system, or a pre-production system. A system in the landscape is identified by a three-letter system ID (SID) such as DEV, QAS, PRD.

flowchart LR
    DEV["DEV<br/>develop"] -->|"transport"| QAS["QAS<br/>test"] -->|"transport"| PRD["PRD<br/>live"]

Changes move forward in one direction, never backward.

Transports

A change made in DEV (a configuration setting, a new program) is recorded in a change request, also called a transport request. Its number has the form DEVK900123 (system ID, K, number). After release, the Transport Management System (TMS) imports it into QAS and later PRD, in the same order. This keeps all systems consistent and gives an audit trail: who changed what, when and why. Transaction SE09 or SE10 shows your requests, and STMS is the transport management console.

Two kinds of changes exist:

  • Customizing (configuration in tables, done in transaction SPRO): usually moved as customizing requests.
  • Workbench (programs, screens, dictionary objects): moved as workbench requests.

What is a client?

Inside one system, a client is a separate business entity with its own master data, transaction data and users, identified by a three-digit number (for example 100 or 200). Technically, nearly every table has a first key column, MANDT, that holds the client number, so data of different clients is separated.

Client type Purpose
000 SAP's delivery client (copy and administration)
001 Delivery template for new clients
100, 200, ... Your working clients: customizing, test or production
Production client One client in PRD where real business happens

Customizing may be client-dependent (valid only in that client) or client-independent (valid for the whole system, such as repository objects). In a development system, you often have a customizing client where you configure, and a separate test client with sample data.

Python Stand-in: client separation in a table

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

SAP's database access (Open SQL) adds the client filter automatically, so a program running in client 100 never sees client 200 rows by accident.

Roles around the architecture

  • Basis administrators maintain servers, work processes, jobs, transports and security. (They are covered later in this track on the track page, SAP Fundamentals.)
  • Developers work in DEV and create transport requests.
  • Testers validate in QAS.
  • Business users work in PRD.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which tier stores the data?

    The database tier holds all data; the application tier runs ABAP logic.
  2. 2. Which work process type runs scheduled batch jobs?

    Background (BTC) processes run jobs without a user; dialog (DIA) handles interactive steps.
  3. 3. In which direction do transports normally move?

    Changes are made in DEV, tested in QAS and only then imported into PRD.
  4. 4. What does the first key column MANDT hold?

    MANDT stores the client, which separates data of different clients in one system.

Summary

  • SAP uses three tiers: presentation, application, database.
  • Application servers run work processes (dialog, background, update, enqueue, spool, gateway).
  • A landscape of DEV, QAS and PRD protects the live system; changes travel in transport requests.
  • A client is a self-contained business unit inside a system, separated by the MANDT column.

Next: Organizational structure