👥 SAP Purchasing Group — Complete Guide

A buyer or buyer team identifier. The most-asked interview trap: NOT assigned to anything in config. Free-floating field on every PR/PO. Configuration, release strategy use, and real-world patterns.

📋 Snapshot

What it is	Buyer ID — appears on every PR/PO header
ID format	3-character alphanumeric (e.g. `001`, `IT0`, `SRV`)
Mandatory?	YES on every PR/PO
T-code to define	OME4
Assigned to?	NOTHING — free-floating
Database table	`T024`

1. Why Purch Group exists separately from Purch Org

Two different concerns:

Purchasing Org = legally responsible entity (contracts, vendor relationship)
Purchasing Group = WHO in the team handled this purchase (buyer accountability)

One Purch Org can have multiple Purch Groups specializing by category (raw materials, packaging, IT, services).

The classic interview trap

Purch Group is NOT assigned to Purch Org. No config link. Any user can pick any Purch Group on any PR/PO. Restriction is via authorization roles, not config assignment.

2. Where Purch Group is used

PR header — mandatory field (ME51N)
PO header — mandatory field (ME21N)
Material Master Purchasing view — default Purch Group
Release Strategy — common characteristic for approval routing
Reports — filter POs by buyer team
Vendor evaluation — per Purch Group

3. Customization — Purchasing Group setup

Define Purch Groups — OME4 — 3-char ID, description, buyer name, phone, email, fax
Set default on Material Master — MM02 Purchasing view — Material defaults a Purch Group on PR/PO
Use as Release Strategy characteristic — CT04 — Define EKGRP characteristic; route approvals by buyer team
Authorization roles — PFCG — Restrict which users can pick which Purch Groups (object M_BANF_EKG)

4. Common Purch Group design patterns

Pattern A: By category

001  Raw materials
002  Packaging
003  Maintenance / spares (MRO)
IT0  IT & software
SRV  Services (consultants, contractors)
CAP  Capex / plant items
URG  Urgent / one-offs

Pattern B: By region (less common)

NPK  North Pakistan buyer
SPK  South Pakistan buyer
CPK  Central Pakistan buyer

Pattern C: By individual buyer (rare)

SHM  Mr. Sharma
KHN  Ms. Khan
IQB  Mr. Iqbal

Best practice

Most projects: 5–15 Purch Groups by CATEGORY. Avoid "one per buyer" unless turnover is very low. Easier to maintain and audit.

5. "Is this possible?" — client Q&A

Can I assign Purchasing Group to a Purchasing Organization?

NO. The classic interview trap. Purch Group is free-floating. Any user with PO/PR authorization can pick any Purch Group.

Can I restrict which Purch Groups a user can pick?

Yes — via authorization roles (object M_BANF_EKG / M_RESL_EKG). NOT via config assignment.

Can the same Purch Group be used in multiple Purch Orgs?

Yes — Purch Groups are global. Any Purch Group can appear on any Purch Org's PO.

Can I use Purch Group in release strategy?

Yes — very common. Configure EKGRP as a characteristic via CT04, use in release class via CL02, set in release strategy via CL20N.

Can I rename / delete a Purch Group?

Rename description yes; deletion of ID once used: block via deletion indicator.

PSEC Purchasing Groups

001  Raw materials       Mr. Sharma   +92 21 1234567
002  Packaging           Ms. Khan     +92 21 7654321
003  Maintenance/spares  Mr. Iqbal    +92 21 9876543
IT0  IT & software       Ms. Ahmed    +92 21 5551234
SRV  Services            Mr. Ali      +92 21 4448888
CAP  Capex               Director     +92 21 1111000
URG  Urgent/one-offs     Any sr. buyer

Interview Q&A

Purchasing Group = buyer ID, free-floating, never assigned to Purch Org. Mandatory on PR/PO. Used in release strategy, reporting, buyer contact info. Restrict via authorization, not config.