Setup Step 9 — Assign Purch Org → Company Code

MANDATORY Layer 4 · MM↔FI bridge ⏱️ ~5 min OX01

🎯 Why this setting exists

This assignment ties buying to a paying legal entity. It tells SAP which company code foots the bill for a purchasing org's orders, so when the vendor invoice arrives it posts to the right set of books. A purchasing org is normally assigned to one company code ("company-specific" — the standard). It can be left unassigned to enable cross-company / centralized purchasing, but that is the rare, deliberate design choice — not the default.

💡 Easy example

You are telling SAP that anything PKLO buys is paid for by PakSteel (PSPK). So when PKLO orders iron from Mughal Steel and the invoice comes in, it lands on PakSteel's books — not the UAE company's, not anyone else's.

Think of it as naming the cardholder behind the buying desk. PKLO is the desk that places the order; PSPK is the company whose account gets charged when the bill is due.

🔗 How this connects to everything else

This is a small assignment with a big consequence: it's the point where the MM purchasing world hands the bill over to FI.

⬆️ Depends on (must exist first)

Step 1 — Company Code: the paying entity (PSPK) must exist.
Step 8 — Purchasing Organization: the buying unit (PKLO) must exist before it can be assigned.

⬇️ Enables (what this unlocks)

Purchase orders that know which company code pays the invoice — the PO carries the paying entity, so invoice receipt has a home.

🧩 Who owns it & why MM cares

MM MM config that ties buying to a paying legal entity. A purchasing org can be left cross-CC for centralized purchasing, but the standard is one company code. MM owns the setting; FI feels the result.

🔮 Links to other modules (now & later)

FI The vendor invoice posts to this company code. This assignment is the bridge that decides whose accounts payable and balance sheet absorb the purchase.

🔧 Configuration — fields & steps

OX01 · SPRO → Enterprise Structure → Assignment → Materials Management → Assign purchasing organization to company code

Action sequence

Run OX01
Assign as below
Save

Assignments

Purch Org	CC Assignment	Why
PKLO	PSPK PakSteel	Company-specific to Pakistan entity
AELO	PSAE PakSteel UAE	Company-specific to UAE entity
GLBL	LEAVE BLANK	This makes it cross-company. Can buy for plants from any CC.
REFR	LEAVE BLANK	Used only for shared conditions; doesn't issue real POs

💡 Why one Purch Org can't be assigned to two CCs

A purchasing org may be assigned to exactly one company code, or to none. There is no "many CCs" option — it's an SAP hard limit. To buy across several company codes you use the "no CC assignment" route: an unassigned purchasing org becomes cross-company and can purchase for plants belonging to any company code.

🚨 Issues & fixes

⚠️ Important — don't "fix" the blank entries

The "leave blank" choice for GLBL and REFR is intentional. Don't try to close the gap by assigning a company code — that converts them from cross-company to company-specific and changes the entire procurement design. A blank CC here is a feature, not an error.

✅ Verification

Re-open OX01 → PKLO → PSPK and AELO → PSAE show their company codes; GLBL and REFR remain blank
Run SE16N → table T024E → the BUKRS (company code) column is filled for PKLO / AELO and empty for GLBL / REFR

✅ Step 9 complete — purchasing orgs assigned to company codes

← Previous

Step 8: Create Purchasing Organizations

Step 10: Assign Purch Org → Plants