Setup Step 8 — Create Purchasing Organizations
MANDATORY
Layer 4 · Purchasing · owned by MM
⏱️ ~5 min
OX08
🎯 Why this setting exists
The purchasing organization is who buys — the unit that negotiates with and purchases from vendors, and the legal contracting party on a purchase order. It is the anchor of all procurement: it appears on every purchase requisition, purchase order, info record and contract. Without a purchasing org, no PO can be created — there is literally no "buyer" for SAP to put on the document.
💡 Easy example
PKLO = "Pakistan Local Purchasing" — the department at PakSteel that places orders with local suppliers like Mughal Steel. When a Karachi line runs short on iron, it is PKLO that issues the PO, agrees the price, and holds the contract with the vendor.
Think of it as the buying desk. The plant says "I need 50 tons"; the purchasing org is the team that actually goes out and buys it. One org can buy for several plants, and a business can run several orgs (local, export, global) for different buying scenarios.
Think of it as the buying desk. The plant says "I need 50 tons"; the purchasing org is the team that actually goes out and buys it. One org can buy for several plants, and a business can run several orgs (local, export, global) for different buying scenarios.
🔗 How this connects to everything else
The purchasing org sits at the top of the procurement chain. It barely depends on anything to be created, but almost everything in purchasing depends on it.
⬆️ Depends on (must exist first)
- Nothing is strictly required to define it — but it is best created after Step 1 — Company Code and Step 3 — Plants exist, so it can immediately be assigned to them.
⬇️ Enables (what this unlocks)
- Step 9 — Assign Purch Org → Company Code (which entity pays).
- Step 10 — Assign Purch Org → Plants (which plants it may buy for).
- Vendor purchasing data (Step 18) — vendors are extended per purchasing org.
- All purchase orders, requisitions, info records and contracts.
🧩 Who owns it & why MM cares
MM Core MM. The purchasing org is the unit that negotiates with and buys from vendors. It appears on every PR / PO / info record / contract — you reference it on virtually every procurement transaction.
🔮 Links to other modules (now & later)
- This is a pure-MM definition — no other module owns or shares it. Its downstream assignments (to a company code in Step 9) are where the FI link is formed.
🔧 Configuration — fields & steps
OX08 · SPRO → Enterprise Structure → Definition → Materials Management → Maintain Purchasing Organization
Action sequence
- Run OX08 → click New Entries
- Create 4 Purchasing Orgs (see below)
- Save
Purchasing organizations to create
| Section · Field | Fill | What the field asks (plain words) | Why we choose this — and the impact if wrong |
|---|---|---|---|
| Purchasing organizations to create · OX08 → New Entries (Fill = the description you type next to each 4-char code) | |||
| PKLO · Purch. org code + name | "PakSteel local (Pakistan)" | Names the everyday buying desk for the Pakistan plants — the team that phones local vendors like Mughal Steel and places the order in rupees. | One local desk lets all Pakistan plants buy through shared contracts and prices in PKR. Impact: with no local org, the PK plants have no buyer on their POs and can't raise a purchase order at all. |
| AELO · Purch. org code + name | "PakSteel UAE local" | Names a separate buying desk just for the UAE plant. | The UAE runs in a different currency (AED) with its own vendors and its own company code, so it needs its own desk. Impact: fold it into PKLO and you mix currencies and legal entities on one buyer — messy pricing and wrong-entity invoices. |
| GLBL · Purch. org code + name | "Global procurement" | Names a cross-company buying desk that can buy for plants belonging to different company codes. | Left with no company-code assignment (Step 9) on purpose, so it can serve any entity's plants for group-wide deals. Impact: if you later tie it to one company code it stops being cross-company and can no longer buy across entities. |
| REFR · Purch. org code + name | "Reference Purchasing Org" | Names a holder of master contracts and pricing that other orgs point at — not a desk that raises real orders. | Lets PKLO, AELO and GLBL share one negotiated deal instead of each re-keying it (Step 11). Impact: skip it and every operational org must maintain its own duplicate contracts and info records. |
🚨 Issues & fixes
⚠️ Common gotcha — the org alone can't buy yet
Creating the purchasing org here does not let you raise a PO yet. On its own a fresh purchasing org is inert — it must still be assigned to plants (Step 10, OX17) before any of those plants will appear in its purchase orders, and typically assigned to a company code (Step 9, OX01) so the invoice knows who pays. Define it here, then wire it up in the next two steps.
✅ Verification
- Run SE16N → table
T024E→ all 4 purchasing orgs (PKLO,AELO,GLBL,REFR) visible - Re-open OX08 → the 4 entries appear with their descriptions