Setup Step 11 — Reference Purchasing Org
OPTIONAL
Layer 4 · Purchasing · owned by MM
⏱️ ~5 min
SPRO (no dedicated T-code)
🎯 Why this setting exists
The Reference Purchasing Organization pattern lets several purchasing organizations share one org's contracts, info records, and pricing conditions. You negotiate and maintain a deal once at a central reference org (here REFR), and the local operational orgs inherit it instead of each re-keying the same vendor agreement. It is optional — basic P2P works without it — but it removes duplicate master-data effort for multi-country or multi-unit companies that buy from the same global suppliers.
💡 Easy example
A central "PakSteel Group" purchasing org (REFR) negotiates one steel-supply contract with a global vendor. Once REFR is set as their reference, the Karachi buying org (PKLO) and the UAE buying org (AELO) can both release against that same contract — they don't each negotiate their own.
Update the price once at REFR and every linked org sees the new rate next time they order. Each operational PO still posts to its own company code (book separation via the plant → CC link is unchanged) — only the pricing and contracts are shared, not the accounting.
Update the price once at REFR and every linked org sees the new rate next time they order. Each operational PO still posts to its own company code (book separation via the plant → CC link is unchanged) — only the pricing and contracts are shared, not the accounting.
🔗 How this connects to everything else
The reference org assignment is a thin link that rides on top of purchasing orgs you already created. Here's the web of settings it touches — useful whether you set it up now or come back to it for shared-pricing scenarios.
⬆️ Depends on (must exist first)
- Step 8 — Create Purchasing Orgs: both the reference org (REFR) and the operational orgs (PKLO, AELO, GLBL) must already exist before you can link them.
⬇️ Enables (what this unlocks)
- Shared contracts — a contract created under REFR (ME31K) becomes usable by the linked operational orgs.
- Shared conditions — info records / pricing maintained at REFR (ME11) are inherited by the local orgs.
- Central deals negotiated once, released locally — less duplicate master-data maintenance.
🧩 Who owns it & why MM cares
MM Pure MM / Purchasing. It lets several buying units reuse one org's negotiated contracts and conditions, cutting duplicate maintenance. You configure and reference it entirely inside MM.
🔮 Links to other modules (now & later)
- No direct cross-module links — this is an internal purchasing convenience.
- Indirectly, cleaner shared pricing means consistent values flowing to FI when each operational PO posts to its own company code.
🔧 Configuration — fields & steps
SPRO (no dedicated T-code) · SPRO → Enterprise Structure → Assignment → Materials Management → Assign purchasing organization to reference purchasing organization
📍 Official SPRO Path (verified)
This assignment lives under Enterprise Structure → Assignment (same parent as the other Purch Org assignment configs), NOT under MM → Purchasing.
SPRO
→ SAP Reference IMG (F5)
→ Enterprise Structure
→ Assignment
→ Materials Management
→ Assign purchasing organization to reference purchasing organization
Transaction code: No dedicated T-code in S/4HANA — accessed via the SPRO IMG path only.
Action sequence (official method)
- Run SPRO → click SAP Reference IMG (F5)
- Navigate the IMG tree (expand each ▶): Enterprise Structure → Assignment → Materials Management → Assign purchasing organization to reference purchasing organization
- Click the 🕓 execute icon
- Click New Entries
- For each row, fill the fields below
Fields explained
| Field | What it means | Value |
|---|---|---|
| Purchasing Organization | Your standard operational Purch Org | PKLO / AELO / GLBL |
| Ref. Purchasing Org | The reference org being inherited from | REFR |
| Release Order (RelOrd) flag | Tick to allow this Purch Org to issue release orders against contracts at REFR | ✅ tick |
| Conditions under Reference Data flag | Tick to allow this Purch Org to access pricing conditions from REFR | ✅ tick |
Rows to create for your PSEC structure
| Standard Purch Org | Reference Purch Org | Release Ord | Conditions |
|---|---|---|---|
| PKLO | REFR | ✅ | ✅ |
| AELO | REFR | ✅ | ✅ |
| GLBL | REFR | ✅ | ✅ |
Save (Ctrl+S) → Local Object / TR.
💡 How it works after assignment
- Create contract under REFR via ME31K → becomes visible to PKLO, AELO, GLBL (when "RelOrd" ticked)
- Create info record under REFR via ME11 → operational orgs inherit pricing (when "Conditions" ticked)
- POs created via PKLO/AELO/GLBL can reference REFR's contracts via Document Overview
- Each operational PO still posts to its OWN CC (book separation via plant→CC link, unchanged)
- Update REFR's contract price → all linked Purch Orgs see new price next time
🚨 Issues & fixes
⚠️ Common gotcha — don't confuse this with Step 12
Some guides mix this step up with Step 12 (Standard Purch Org per Plant), which uses T-code OMKI. For Reference Purch Org assignment there is NO dedicated T-code — use the SPRO IMG path above only. If you skip this step entirely, each Purch Org simply maintains its own info records and contracts independently: slightly more master-data effort, but everything still works. Add it later when you need shared pricing across orgs.
✅ Verification
- Re-open the SPRO node → your 3 rows (PKLO, AELO, GLBL → REFR) are present with both flags ticked.
- Create a test contract under
REFRvia ME31K → confirm PKLO can reference it in a PO's Document Overview.
📚 Source: Verified against saponlinetutorials.com and SAP Help Portal community Q&A. Note: for Reference Purch Org assignment there's NO dedicated T-code — use the SPRO IMG path above only.