🗄️ 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.
🏢 Cross-client objects — the building analogy (LIVE-TESTED)
One SAP system = one building. Each client = one apartment inside it. Every apartment has its own furniture (master data, POs, company codes, users). But all apartments share the building's structure — and those shared parts are the cross-client objects: change one, and every client feels it instantly, no transport needed.
| 🏢 Cross-client (one for the whole building) | 🚪 Client-specific (each apartment its own) |
|---|---|
| All programs / ABAP code / screens | Master data (materials, vendors, BPs) |
| Table definitions (e.g. a generated condition table A9xx) | Transactions (POs, invoices, stock) |
| Access sequences (M/07) & condition tables (M/03) | Condition types (M/06), pricing schemas (M/08), company codes, plants — most customizing |
| Units of measure, factory calendar, transaction codes | Users & passwords, number-range intervals |
Why the lock exists: because a cross-client change hits every client with no warning, each client carries an SCC4 setting ("Cross-Client Object Changes") that can block it — that's the "No maintenance authorization for cross-client tables" popup you may meet in Scenario 21 (M/07). On real projects only one "golden client" may change shared objects; Basis owns SCC4. On your own IDES you're also Basis, so unlocking it is fine.
Remember it as: client = apartment, system = building; cross-client = the building's structure — change once, everyone gets it, so only the golden client may touch it.
☁️ And in S/4HANA Cloud?
- Private Edition: technically an on-premise system hosted by SAP — clients, SCC4, golden client, transports all work exactly as above.
- Public Edition: the building has a landlord. Clients still exist under the floor, but you work in one fixed client per system (no client field at login), no SCC4 for customers — SAP owns all Basis/cross-client administration. Config happens in guided apps (SSCUIs / Central Business Configuration) on a fixed development → test → production landscape with automated transports; custom changes only via key-user extensibility + released APIs, so upgrades can't break you.
Interview line: "Private Cloud/on-prem = classic client concept with SCC4 and a golden client; Public Cloud = same concept technically, but one fixed client per system and SAP owns the structure — that strictness is what makes automatic upgrades safe."
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.