Setup Step 13 — Create Purchasing Groups

MANDATORY Layer 4 · Purchasing · owned by MM ⏱️ ~10 min OME4

🎯 Why this setting exists

A Purchasing Group (PG) is a 3-character code naming a buyer or buying desk responsible for a category of spend. It's the "who's buying" identifier stamped on every PR, PO, contract, RFQ, and scheduling agreement (stored in EBAN.EKGRP, EKKO.EKGRP).

Why it's mandatory: every PR/PO must carry a PG — without at least one created, PR/PO creation fails immediately. Crucially, Purchasing Groups are FREE-FLOATING: they are NOT assigned to a Purch Org, Company Code, or Plant. One PG can be used across all Purch Orgs — a common interview trap.

💡 Easy example

At PakSteel, RMT is the raw-materials buying desk (Mr. Ali Khan) and SRV is the services desk (Mr. Hassan). So an iron-ore PO is stamped RMT and routes to the metals buyer, while a consulting PO is stamped SRV and routes to the services buyer.

Later you can ask "how many POs did the spare-parts team handle this month?" and simply filter reports by PG. The buyer's phone and email also live on the PG record, so vendors and colleagues know exactly who to call about a delayed delivery.

🔗 How this connects to everything else

The Purchasing Group is a small master list with an outsized footprint — it threads through reporting, approval, and vendor communication across purchasing. Here's the web.

⬆️ Depends on (must exist first)

Essentially nothing — a PG is a simple, free-floating master list with no link to Purch Org, CC, or Plant.
It just needs to exist before you create any PR or PO that references it.

⬇️ Enables (what this unlocks)

Assigning a buyer / desk on every PR and PO (the EKGRP field).
Reporting & workload by buyer — filter ME2N / ME5A by PG.
Release strategies that branch on the buyer category (e.g. capex needs CFO approval).

🧩 Who owns it & why MM cares

MM Pure MM / Purchasing. The PG is the buyer or buying desk responsible for a category of spend; it appears on every requisition and order, so MM owns and maintains it end-to-end.

🔮 Links to other modules (now & later)

No direct cross-module ownership — but the PG's email feeds output determination (vendor + buyer CC) and its code drives release-strategy approval routing within MM.

🔧 Configuration — fields & steps

OME4 · SPRO → MM → Purchasing → Create Purchasing Groups

Action sequence — create 7 PGs for PakSteel

Run OME4 → click New Entries
For each PG, enter the 3-char code + Description + Buyer Name + Telephone + Fax + Email
Save (Ctrl+S)

PG Code	Description	Buyer (example)	Used in MM scenarios
RMT	Raw Materials	Mr. Ali Khan · +92 21 1234567 · ali.khan@paksteel.pk	Sc 1 (iron ore, coal), Sc 9 (subcontracting), Sc 16 (batch steel)
PKG	Packaging	Ms. Sara · +92 21 1234568	Sc 5 (packaging consumables)
MRO	Maintenance, Repair, Ops	Mr. Iqbal · +92 21 1234569	Sc 2 (bearings, spare parts), Sc 5
ITS	IT & Software	Ms. Ahmed · +92 21 1234570	Sc 4 (IT services, software licenses)
SRV	General Services	Mr. Hassan · +92 21 1234571	Sc 4 (consulting, audit, cleaning)
CPX	Capex / Capital Expenditure	Director's office	Sc 6 (machinery, vehicles, IT hardware)
URG	Urgent / Emergency	On-call buyer	Express purchases — can bypass standard release

Save (Ctrl+S) → Local Object / TR.

💼 5 real-world purposes (where you'll see PG in daily SAP use)

#	Purpose	Real-world example
1	Responsibility tracking	"Who do I call about delayed steel delivery?" → PG `RMT` = Mr. Ali Khan, phone +92-21-XXX, email ali@paksteel.com
2	Reporting & workload mgmt	"How many POs did the spare parts team handle this month?" → ME2N / ME5A filter by PG `MRO` shows workload + KPI
3	Approval workflow (release strategy)	PRs from PG `CPX` (capex) require Director + CFO approval; PRs from PG `URG` auto-released. Configured via CT04 using characteristic CEKKO_EKGRP
4	Output determination	PO emails go to vendor + CC the buyer's email (from PG's email field). NACE/MN04 conditions look up PG contact info
5	Authorization restriction	Buyer Ali can ONLY create POs with PG `RMT` (not other categories) — controlled via SU01 user profile / authorization object M_BEST_EKG

📊 Where Purchasing Group flows through actual transactions

                  ┌──────────────────────────┐
                  │  Purchasing Group "RMT"  │
                  │  Ali Khan, Raw Mat Buyer │
                  │  phone, email stored     │
                  └─────────────┬────────────┘
                                │ used in:
       ┌────────────────────────┼────────────────────────┐
       ▼                        ▼                        ▼
  ┌─────────┐             ┌─────────┐             ┌──────────┐
  │  PR     │             │  PO     │             │ Contract │
  │ (ME51N) │             │ (ME21N) │             │ (ME31K)  │
  │EBAN.EKGRP             │EKKO.EKGRP             │EKKO.EKGRP│
  └────┬────┘             └────┬────┘             └─────┬────┘
       └──────┬──────────┬─────┴────┬──────────┬────────┘
              ▼          ▼          ▼          ▼
        ┌───────┐  ┌───────────┐ ┌──────────┐ ┌──────────────┐
        │Reports│  │ Approval  │ │  Output  │ │ Vendor       │
        │ME2N   │  │ Strategy  │ │  (NACE)  │ │ Communication│
        │ME5A   │  │ (CT04/    │ │  Email   │ │ (default PG  │
        │KPI    │  │  OMGS)    │ │  vendor +│ │  in LFM1)    │
        │       │  │           │ │  buyer CC│ │              │
        └───────┘  └───────────┘ └──────────┘ └──────────────┘

📋 Reporting examples — where PG matters daily

T-code	Report	How PG helps
ME2N	POs by Vendor	Filter by Purch Group → see workload of each buyer team
ME5A	List of PRs	"How many PRs pending in IT dept (PG ITS)?" — KPI for buyer team
ME5K	PRs by Account Assignment	Average PR→PO conversion time per buyer team
ME80FN	General PO Analysis	Drill-down by PG for spend analytics

💼 Pakistani context — why PG choice matters

Scenario	Right PG	Why this PG specifically
Buying iron ore from Mughal Steel (5M PKR)	`RMT`	Raw material category, Ali Khan handles it, no special approval (high-volume routine)
SAP consulting from Lucky Consulting (600K PKR)	`SRV`	Service category, Hassan tracks vendor performance, needs cost center accounting
New CNC machine from Pak Machine Tools (4.5M PKR)	`CPX`	Capex → triggers Director + CFO approval workflow via release strategy
Office paper for finance dept (80K PKR)	`SRV` or new `OFC`	Routine consumable, junior buyer handles
Emergency spare part for production line down (200K PKR)	`URG`	Bypasses standard approval, on-call buyer authorized

🎓 Interview-ready 30-second answer

Q: What's a Purchasing Group in SAP MM?

A: Purchasing Group is the "buyer identifier" — a 3-character code that names the person or team responsible for procurement. It's mandatory on every PR, PO, contract, and RFQ. Its real value is in:

Reporting — filter purchasing data by buyer team for KPI/workload analysis
Release strategies — approval workflows trigger based on PG (e.g., capex needs CFO approval)
Output determination — buyer's email gets CC'd on vendor communications
Responsibility — vendors and stakeholders know who to contact

Unlike Purch Org, Purch Group is FREE-FLOATING — NOT assigned to any organizational structure (no link to Purch Org, CC, or Plant). One Purch Group can be used across all Purch Orgs. This is a common interview trap.

🚨 Issues & fixes

⚠️ Common gotcha — PR/PO creation fails with no PG

Because every PR and PO must carry a Purchasing Group, if none exists yet, document creation fails immediately. Create at least one PG before attempting any procurement transaction. And remember the interview trap: a PG is free-floating — never assigned to a Purch Org, Company Code, or Plant, so one PG works across all of them.

✅ Verification

SE16N → table T024 → expected 7 rows (RMT, PKG, MRO, ITS, SRV, CPX, URG)
OME4 → display → all 7 PGs visible
ME51N → create test PR → enter PG RMT → confirms PG works in PRs

✅ Step 13 complete — 7 Purchasing Groups created with buyer contact info

← Previous

Step 12: Standard Purch Org per Plant

Step 14: Customer / Vendor for Inter-Co STO