T024 table — Purchasing Groups Master Table T024

Each record in T024 represents one purchasing group, the code entered in a purchase order or purchase requisition to identify the buyer or buying team responsible for that line of procurement. Unlike a purchasing organization, a purchasing group is not tied to a company code or plant; it is a flat, client-wide code that can be used across multiple purchasing organizations and plants. The table exists purely to give that code a readable name and, in some system setups, contact information such as a telephone number. It is maintained through standard customizing activity for purchasing groups, not through a master data transaction, and it rarely changes once a business goes live except when buying teams are reorganized or new categories of spend are assigned to new buyers.

T024 is tiny, typically a few dozen to a few hundred rows in any real system, so selectivity is not a concern the way it is for transaction tables. Always filter by MANDT when writing native SQL against the underlying database, though ABAP reads on a client-dependent table handle this automatically. The table is safe to select in full for a lookup or dropdown build. The only real reading trap is assuming EKGRP is meaningful outside its code value: two different clients or two different implementations may reuse the same two or three character code for entirely different buying teams, so cross-system comparisons of purchasing group must go through EKNAM, not the code alone.

A purchase order shows a purchasing group code but the printed form or list display shows a blank buyer name. Select T024 with EKGRP equal to the code from the order header. If no row is returned, the code is either a typo introduced at PO creation, a leftover from a migrated document referencing a group that was later deleted from customizing, or a code created in a different client and never replicated. If a row exists but EKNAM is blank, the group was created without maintaining its description, a common gap after a mass upload of customizing.

T024 is unchanged in S/4HANA. It remains a simple customizing table and is not one of the tables affected by the S/4HANA data model simplification of materials management, since it carries no quantity or value fields that were consolidated into the universal journal or the material document table restructuring. Purchasing group as a concept is used identically in both ECC and S/4HANA procurement documents and in the Fiori apps that expose buyer-facing worklists, which read the table through standard value help services rather than direct SQL.

Maintenance of purchasing groups is a procurement customizing task, owned by the MM or procurement functional consultant during configuration, then handed to a business process owner or purchasing operations lead for ongoing changes such as adding a new buyer code. Questions about why a specific document shows a missing or wrong purchasing group usually start with the functional consultant checking T024 before escalating to whoever controls the source system feeding automated PO or requisition creation.

T024 is maintained through the standard purchasing customizing activity for purchasing groups, not through a transaction that generates business documents. It is read by EKKO and EKPO when displaying or printing purchase orders, by EBAN when a requisition is created, and by purchasing reporting transactions that offer purchasing group as a selection or output field. It has no update-generating transaction of its own and no dependent line-item table.