🛒 SAP Purchasing Organization — Complete Guide
The unit legally responsible for buying. Signs POs, negotiates with vendors, holds contracts. Centralized vs decentralized design, cross-company scenarios, Reference Purch Org pattern — and the PSEC example.
📋 Snapshot
| What it is | Unit responsible for purchasing — contracts, vendor management, POs |
|---|---|
| ID format | 4-character alphanumeric (e.g. 1000, CENT) |
| Mandatory? | YES — every PO needs one |
| T-code to define | OX08 |
| T-code to assign to CC | OX17 (optional) |
| T-code to assign to Plant | OX01 (mandatory ≥1) |
| Database tables | T024E (master), T024W (PO→Plant), T024Z (PO→CC) |
1. Purpose
Purchasing Org answers two business questions on every PO:
- Who is legally responsible for this purchase?
- Whose pricing, terms, and contracts apply?
Without a Purch Org, SAP can't process a PO — there's no contracting entity, no pricing master to look up, no contract to apply.
2. Three flavors of Purchasing Org
| Type | CC assignment | Plant assignment | When used |
|---|---|---|---|
| 1. Plant-specific | One CC | One plant only | Highly autonomous plants, JV setups, very rare |
| 2. Company-specific (cross-plant) |
One CC | Multiple plants of that CC | Most common — centralized buying within one legal entity |
| 3. Cross-company | NONE (OX17 blank) | Plants from multiple CCs | Global procurement strategy across legal entities |
3. Reference Purchasing Organization
A Reference Purch Org is a special Purch Org that holds shared conditions, contracts, and info records. Other Purch Orgs reference it via OMKI to inherit the shared pricing.
When to use Reference Purch Org
- Multiple Purch Orgs buy from same global vendor
- You want central pricing but local PO-issuing
- Global procurement strategy with regional execution
Example — Reference Purch Org pattern
REFR Reference Purch Org
└── Master contract with ArcelorMittal: $780/tonne (global)
PSPK India local ──references via OMKI──▶ REFR
PSAE UAE local ──references via OMKI──▶ REFR
PSGB UK local ──references via OMKI──▶ REFR
Each local PO issues POs in own region.
Pricing pulls from REFR's contract.4. Centralized vs Decentralized — when forced
Decentralization is FORCED only when one of these is true:
- Multiple Company Codes — each must legally sign its own contracts
- Joint Venture / Multi-owner plants
- Different currencies for the same vendor relationship
- Statutory audit trail required per legal entity
- Different vendor partner functions per plant for same vendor
Things people THINK force decentralization (but don't):
| "Reason" | Workaround under centralized |
|---|---|
| Different prices per plant | Use plant-specific info records (EINE) |
| Different release strategies | Use Plant as release-strategy characteristic |
| Per-plant spend reporting | Filter ME2N by Plant, or use CDS views |
| Different buyer teams | Use Purchasing GROUPS |
| Authorization separation | Use M_BEST_EKO + Plant authorization |
| Per-plant compliance | Authorization roles |
5. Customization — Purchasing Org setup
- Define Purch Org — OX08 — 4-char ID, description
- Assign to Company Code (optional) — OX17 — for company-specific. Leave blank for cross-company.
- Assign to Plants — OX01 — mandatory, at least one.
- Set Reference Purch Org (optional) — OMKI — for shared conditions.
- Set Standard Purch Org per Plant (optional) — OMKL — for source determination default.
- Maintain vendor purchasing data per Purch Org — BP (S/4) / XK01 (ECC).
- Authorization roles per Purch Org — PFCG — to restrict who can use which PO.
6. Common errors and fixes
| Error | Cause | Fix |
|---|---|---|
Purch Org not authorized for Plant |
Missing OX01 assignment | Run OX01, assign PO → Plant |
Vendor not maintained for Purch Org |
Vendor purchasing view (LFM1) missing for this PO | BP → extend vendor purchasing data for this PO |
| Wrong pricing on PO | Info record under wrong PO or missing | Create IR via ME11 under correct PO, or use Reference PO |
7. PSEC real-world example
PSEC Purchasing Org design:
PSPK PSEC Pakistan local Type: Company-specific
→ CC 1000 (PSEC Pakistan Ltd)
→ Plants 1100, 1200, 1300 (Karachi, Lahore, Faisalabad)
Buys local raw materials, packaging, services in PKR
PSAE PSEC UAE local Type: Company-specific
→ CC 2000 (PSEC Trading FZ-LLC)
→ Plant 2100 (Dubai DC)
Buys local items in AED
PGLB PSEC Global Type: Cross-company
→ NO CC assignment (cross-company)
→ All 4 plants (1100, 1200, 1300, 2100)
Buys strategic global vendors (e.g. ArcelorMittal steel)
REFR Reference Purch Org Type: Reference only
→ Holds master global contracts
→ PSPK, PSAE, PGLB all reference REFR via OMKI8. Interview Q&A
What is a Purchasing Organization?
The unit legally responsible for purchasing — negotiates with vendors, signs POs. Every PO is created under a Purch Org. Must be assigned to at least one plant; optionally to a Company Code.
Three types of Purchasing Org?
(1) Plant-specific — assigned to one plant only. (2) Cross-plant / Company-specific — multiple plants of one CC. (3) Cross-company — assigned to NO CC, plants from multiple CCs.
Can a Purchasing Org be assigned to multiple Company Codes?
No — at most ONE CC via OX17. For cross-company buying, leave CC assignment blank.
What's a Reference Purch Org?
A Purch Org that other POs reference (via OMKI) for shared conditions, contracts, info records. Enables central pricing without central PO-issuing.
Is Purchasing Group assigned to Purchasing Org?
No — Purch Group is free-floating, not assigned to anything in config. Classic interview trap.