SAP MM Organizational Structure — Complete Guide

📘 Deep-dive guide per entity

Each entity below has its own dedicated page with full details — configuration T-codes, mandatory vs optional, linkages, customization options, "is this possible" client Q&A, common errors, real-world examples, and interview soundbites.

1. Why SAP separates organizational concerns

Real businesses have multiple dimensions:

• A legal dimension — who files taxes, owns books
• An operational dimension — where physical activity happens
• A functional dimension — who is responsible for buying, selling, producing
• A physical sub-location dimension — where stock actually sits within a plant

SAP separates each of these into its own entity so that real-world complexity can be modeled accurately.

2. Our example — Pakistan Steel & Engineering Co. (PSEC)

Throughout this academy we'll follow a fictional Pakistani manufacturer. Here's the company:

This setup covers nearly every scenario you'll meet on a real project:

• ✅ Multiple plants under one company (Karachi, Lahore, Faisalabad)
• ✅ Multi-country / multi-currency operations (PKR + AED)
• ✅ Cross-company plants for export logistics
• ✅ Mix of manufacturing and distribution
• ✅ Both central procurement (steel, IT) and local procurement (consumables)

3. The 7 organizational entities you must know

3.1 Client

3.2 Company Code

3.3 Plant — ⭐ the most important MM entity

3.4 Storage Location

3.5 Purchasing Organization

3.6 Purchasing Group

3.7 Valuation Area

4. How they link together

Here's our PSEC example fully mapped out:

Client 100
  │
  ├── Company Code 1000  (PSEC Pakistan Ltd, PKR)
  │     ├── Plant 1100  (Karachi factory)
  │     │     ├── SL RM01 (raw materials)
  │     │     ├── SL FG01 (finished goods)
  │     │     └── SL QA01 (quality hold)
  │     ├── Plant 1200  (Lahore factory)
  │     │     └── SL RM01, FG01, QA01
  │     └── Plant 1300  (Faisalabad factory)
  │           └── SL RM01, FG01, QA01
  │
  └── Company Code 2000  (PSEC Trading FZ-LLC, AED)
        └── Plant 2100  (Dubai DC)
              └── SL DC01, EXP1

  Purchasing Orgs (cross-cutting):
    PSEC-PK    → assigned to CC 1000 + plants 1100, 1200, 1300 (local PK buying)
    PSEC-AE    → assigned to CC 2000 + plant 2100 (local UAE buying)
    PSEC-GLOB  → assigned to NO CC + all 4 plants (cross-company strategic buying)

  Purchasing Groups (free-floating):
    001 Raw materials · 002 Packaging · 003 Maint/spares · IT0 IT · SRV Services

  Valuation Area:
    = Plant level (each plant carries its own price)

The assignment rules

5. T-codes to define and assign — your roadmap

The exact sequence to build an org structure in SAP S/4HANA On-Premise:

1. Step 1 — Define Company Code(s) T-code: OX02 · Set the 4-char ID, country, currency, language, fiscal year variant.
2. Step 2 — Define Plant(s) T-code: OX10 · Set the 4-char ID, name, factory calendar.
3. Step 3 — Assign each Plant to its Company Code T-code: OX18 · This is mandatory; without it, the plant can't function.
4. Step 4 — Define Storage Locations T-code: OX09 · Per plant — define 3-5 SLs that make sense (RM, FG, QA, returns).
5. Step 5 — Define Purchasing Organization(s) T-code: OX08 · 4-char ID and description.
6. Step 6 — Assign Purch Org to Company Code T-code: OX17 · Optional — leave blank for cross-company Purch Org.
7. Step 7 — Assign Purch Org to Plant(s) T-code: OX01 · Mandatory; must assign to at least one plant.
8. Step 8 — Define Purchasing Group(s) T-code: OME4 · 3-char ID, buyer name, contact details.
9. Step 9 — Set Valuation Level T-code: OX14 · One-time choice — Plant level (recommended) or CC level.

6. Centralized vs Decentralized — when each makes sense

One of the most important design decisions: should ONE Purchasing Org buy for all plants, or should EACH plant have its own?

When CENTRALIZED is right (one Purch Org)

• Single Company Code, multiple plants, shared vendors
• Want volume leverage from suppliers (better prices)
• Same procurement policy across plants
• Master data team wants minimal duplication

When DECENTRALIZED is right (Purch Org per plant)

• Different Company Codes (legal entities) — each signs its own contracts
• Joint venture / multi-owner plants
• Different vendor currencies for same vendor
• Different statutory compliance per legal entity
• Genuinely autonomous business units

PSEC scenarios mapped

7. Interview Q&A

8. What's next

You now understand the theory. Time to build.

Our interactive Org Structure Builder lets you construct PSEC's organization step-by-step. You'll watch database tables fill with rows, see exactly which T-codes to run in real SAP, and toggle between centralized and decentralized scenarios.