🗄️ SAP Client — The Top of the Hierarchy
The highest organizational unit in SAP. A complete isolated SAP universe. Data is scoped to one client; nothing is shared across clients. Most MM consultants don't configure this — but you must understand it.
📋 Snapshot
| What it is | The whole SAP system instance — the top of every hierarchy |
|---|---|
| ID format | 3-digit number (e.g. 100, 200, 800) |
| Mandatory? | Yes — you log into one at every session |
| T-code (Basis) | SCC4 (manage clients) |
| Database table | T000 |
| Owner | Basis / system admin (not MM) |
1. What is a Client?
An isolated SAP universe. Everything you do — master data, transactions, configuration — happens inside one client. Data is partitioned by client number; nothing is shared.
Common client uses
| Client | Typical use |
|---|---|
000 | SAP delivered reference |
100 | Production |
200 | QA testing |
300 | Development / customizing |
800 | SAP IDES (demo / training) |
900 | Sandbox / throw-away |
2. Why clients exist
So one SAP installation can host multiple environments without data leakage. Production data stays separate from training data; QA tests don't pollute production books.
800. When you log in, the client field is the first thing you fill — it determines which universe of data you'll work with.
3. Configuration (Basis area)
As an MM consultant, you typically don't configure clients. Basis admins do. But understand:
- SCC4 — display/maintain clients
- SCC1 — client copy from another client
- SCC5 — delete a client
- SCCL — local client copy
4. Is this possible?
Can I share master data between two clients?
No — clients are isolated. To replicate data, use Client Copy (Basis activity).
Can a vendor exist in client 100 but not client 200?
Yes — they're isolated. Each client has its own copy of all master data.
Can I change a client ID?
No — fixed at creation.