Setup Step 10 — Assign Purch Org → Plants

MANDATORY Layer 4 · Purchasing · owned by MM ⏱️ ~5 min OX17

🎯 Why this setting exists

This assignment authorizes a purchasing org to procure for specific plants. It is what links the buyer to the places it is allowed to buy for. Without it, the plant won't even appear in that org's purchase order — PO creation fails outright. The relationship is many-to-many: one purchasing org can serve many plants, and one plant can be served by many purchasing orgs.

💡 Easy example

You are allowing PKLO to buy for both the Karachi (PK01) and Lahore (PK02) factories. After this, when a buyer in PKLO raises a PO, both plants show up as valid "ship-to" sites.

Think of it as the route permit for the buying desk: PKLO is licensed to deliver purchases to PK01 and PK02. A plant that isn't on the permit simply can't be selected — SAP won't let PKLO order for a factory it was never authorized to serve.

🔗 How this connects to everything else

This is the final wiring that makes a purchasing org actually usable. It needs both ends to exist first, and once done it switches on PO creation.

⬆️ Depends on (must exist first)

Step 3 — Plants: the plants (PK01, PK02, …) must exist to be assigned.
Step 8 — Purchasing Organization: the buying unit must exist before plants can be hung off it.

⬇️ Enables (what this unlocks)

A purchasing org to procure for those plants — the plant finally appears in the org's PO.
Many-to-many coverage: assign the same plant to several orgs (e.g. local + global) so either can buy for it.

🧩 Who owns it & why MM cares

MM Pure MM. This controls which plants a buying unit may purchase for. Without it the plant won't appear in that org's PO — so it's a setting MM owns and checks first whenever a PO refuses a plant.

🔮 Links to other modules (now & later)

This is a self-contained MM assignment — no other module owns or shares it. Its whole job is internal to purchasing: connecting the buyer to its plants.

🔧 Configuration — fields & steps

OX17 · SPRO → Enterprise Structure → Assignment → Materials Management → Assign purchasing organization to plant

Action sequence

Run OX17 → click New Entries
Create 8 assignments (see below)
Save

Assignments

Purch Org	Plant	Why
PKLO	PK01	Local PK buys for Karachi factory
PKLO	PK02	Same — Lahore factory
PKLO	PK03	Same — Karachi DC
AELO	AE01	UAE local buys for Dubai DC
GLBL	PK01	Cross-company can also buy for PK plants
GLBL	PK02	Same
GLBL	PK03	Same
GLBL	AE01	And for UAE plant — that's how it works cross-CC

💡 Why GLBL is assigned to every plant

Because GLBL was left with no company-code assignment in Step 9, it is a cross-company purchasing org. Assigning it to plants in both the Pakistan and UAE entities is exactly how centralized, cross-CC procurement is set up — one buying unit serving plants that belong to different company codes.

🚨 Issues & fixes

⚠️ This is the most common error source for POs

If you later get "Plant XXXX not assigned to Purch Org YYYY" (or "Purch Org not authorized for Plant") while creating a PO, check this table first. A missing row here is the usual cause — the buying unit was simply never authorized for that plant. Add the assignment in OX17 and the plant becomes selectable.

✅ Verification

Run SE16N → table T024W → exactly 8 rows

✅ Step 10 complete — all 8 purch-org → plant assignments created

← Previous

Step 9: Assign Purch Org → Company Code

Step 11: Reference Purchasing Org