Setup Step 12 — Standard Purch Org per Plant
OPTIONAL
Layer 4 · Purchasing · owned by MM
⏱️ ~5 min
OMKI
🎯 Why this setting exists
When a plant has more than one purchasing org that can buy for it (e.g. PK01 is assigned to both PKLO and GLBL), SAP needs to know which one to use by default for scenarios where it isn't typed in by hand: pipeline procurement, consignment, and stock-transport orders (STO). That default is the plant's Standard Purchasing Org. It is optional — skip it if each plant has only one purchasing org — but those automatic scenarios fail without it.
💡 Easy example
The Karachi DC (PK03) can be served by two buying orgs, but you set PKLO as its Standard Purchasing Org. Now when PK03 raises a stock-transfer order to pull stock from the Lahore factory, SAP auto-picks PKLO as the buying org — the user never has to choose it manually each time.
The same default kicks in for consignment settlement and pipeline postings at that plant. For an ordinary PO (NB), the buyer still picks the org explicitly, so the Standard PO setting is ignored there — it only matters where SAP must decide on its own.
The same default kicks in for consignment settlement and pipeline postings at that plant. For an ordinary PO (NB), the buyer still picks the org explicitly, so the Standard PO setting is ignored there — it only matters where SAP must decide on its own.
🔗 How this connects to everything else
This setting is the tie-breaker that makes automatic source determination possible. Here's the web of settings and scenarios that depend on it.
⬆️ Depends on (must exist first)
- Step 8 — Create Purchasing Orgs: the orgs you'll nominate as the default must exist.
- Step 10 — Assign Purch Org → Plants: a plant must already be linked to its purchasing org(s) before you can pick one as the standard.
⬇️ Enables (what this unlocks)
- Automatic source determination + pricing for STO and consignment when a plant has multiple purchasing orgs.
- Pipeline procurement — consumption settlement (MRKO) picks the standard PO.
- STO — the receiving plant's standard PO is used automatically.
🧩 Who owns it & why MM cares
MM Pure MM / Purchasing. It tells SAP the default buying org for a plant so STO and consignment can auto-pick it instead of erroring out. Configured and referenced entirely within MM.
🔮 Links to other modules (now & later)
- Relevant to MM STO flows — see Scenario 7 (Stock Transport Order).
- Relevant to consignment — see Scenario 10 (Consignment).
🔧 Configuration — fields & steps
OMKI · SPRO → Enterprise Structure → Assignment → Materials Management → Assign Standard Purchase Organization to Plant
📍 Official SPRO Path (verified)
SPRO
→ SAP Reference IMG (F5)
→ Enterprise Structure
→ Assignment
→ Materials Management
→ Assign Standard Purchase Organization to Plant
Transaction code: OMKI⚠️ Note: OX17 ("Assign Purch Org to Plant", Step 10) is many-to-many — it lists ALL Purch Orgs that CAN buy for a plant. OMKI is different — it picks ONE of those as the DEFAULT for specific scenarios (consignment, STO, pipeline). Both nodes live under the same Enterprise Structure → Assignment → MM section.
Action sequence
- Run OMKI (or navigate via the SPRO IMG path above)
- Click New Entries
- For each plant, enter the default Purch Org:
| Section · Field | Fill | What the field asks (plain words) | Why we choose this — and the impact if wrong |
|---|---|---|---|
| Standard (default) purchasing org per plant · OMKI | |||
| Plant PK01 — standard purch org | PKLO | When SAP must pick a buyer for this plant on its own — for STO, consignment or pipeline — which one? Like the default card kept on file for automatic charges. | PK01 can be served by both PKLO and GLBL, but its routine buying is local, so PKLO is the sensible default; GLBL is only for global-vendor cases. Impact: leave it unset and an STO or consignment posting at PK01 fails with "Standard Purch Org not defined for plant". |
| Plant PK02 — standard purch org | PKLO | Same question for the Lahore factory. | Lahore's day-to-day buying is also local, so PKLO is its default too. Impact: without it, the automatic scenarios at PK02 error out the same way. |
| Plant PK03 — standard purch org | PKLO | Same question for the Karachi DC. | The Karachi DC is supplied through the local desk PKLO, so it is the natural default — e.g. an STO pulling stock from Lahore auto-picks PKLO. Impact: unset, that STO can't work out a buyer. |
| Plant AE01 — standard purch org | AELO | Same question for the Dubai plant. | The Dubai plant's local buyer is AELO (its own currency and entity), so AELO is its default. Impact: set PKLO here by mistake and UAE auto-postings would try to buy through the Pakistan desk. |
Save (Ctrl+S) → Local Object / TR.
💡 Where this matters in real transactions
- Pipeline procurement — automatic consumption posting picks the Standard PO for vendor invoice settlement (MRKO)
- Consignment — vendor consignment settlement uses the Standard PO
- Stock Transport Order (STO) — when creating an STO, the receiving plant's Standard PO is used
- Regular POs (NB doc type) — user explicitly picks which PO to use, so the Standard PO setting doesn't matter
🚨 Issues & fixes
⚠️ Common gotcha — wrong T-code & the "not defined" error
If you skip this step, pipeline / consignment / STO scenarios fail with "Standard Purch Org not defined for plant" when you reach them (Scenarios 10, 11, and 7 in the P2P guide). Regular procurement works fine without it — so skip for now and come back when you need those specific scenarios. Also: some older guides incorrectly cite OMKL — the correct T-code is OMKI.
✅ Verification
- Re-open OMKI → each of PK01, PK02, PK03, AE01 shows its standard Purch Org.
- Create a test STO for a receiving plant → confirm SAP auto-fills the standard Purch Org without a "not defined" error.
📚 Source verified: SAP Online Tutorials, SAP Help Portal community Q&A. Some older guides incorrectly cite OMKL — the correct T-code is OMKI.