SAP tableObjectT023ModuleMM_P2P

T023 table — Material Group Master Table

T023 is the customizing table that defines valid material groups (Warengruppe), the classification key stored on the material master and used for reporting, statistics, and price or account determination. One row represents one material group code, valid client-wide. It has no hierarchy of its own; grouping logic above it lives in separate classification tables.

T023 holds the flat list of material groups configured in the system, the code that sits on every material master record's basic data view. The page covers what the table actually stores, how it joins to MARA and transaction data, and the recurring mistake of treating it as a hierarchy or a reporting dimension it was never designed to be.

Published 16 Sept 2026· 969 words

What it stores

One row in T023 represents one material group code (Warengruppe) that has been defined in customizing as valid for use on material master records. The material group is a flat classification key, not a hierarchy node by itself; it is used to group materials for purposes such as purchasing statistics, account determination in some configurations, authorization checks, and reporting cubes. T023 itself carries only the code and its division assignment, not the actual grouping of materials to that code, which lives in the material master. Because it is a customizing table rather than transactional master data, entries here change rarely, usually as part of a project to restructure how materials are classified. The table is client-dependent, so the same code can carry different meaning across clients if customizing was not transported consistently.

Key fields

  • MANDT - client
  • MATKL - material group code, the key value that also appears on the material master
  • SPART - division assigned to the material group in customizing

How it joins the data model

  • T023-MATKL = MARA-MATKL, the primary join, since every material master row carries the material group it belongs to
  • T023-MATKL = EBAN-MATKL, used when a purchase requisition is created for a material group without a material master (limit or service items)
  • T023-MATKL = T024-EKGRP indirectly through customizing tables that map purchasing group defaults to material group, not a direct field join
  • T023T-MATKL = T023-MATKL for the language-dependent description text, held in the companion text table

How to read it safely

T023 is small, typically a few hundred to a few thousand rows per client, so selectivity is rarely a performance concern on its own. Always restrict by MANDT first if querying outside a client-bound tool. The real risk is not performance but assumption: MATKL here is just a code and a division, nothing else. Do not expect a parent group, a hierarchy level, or a controlling area link on this table; those live elsewhere or do not exist at all for material groups in standard SAP. When investigating a material group issue, check the material master's basic data view first to confirm which materials actually carry the code before looking at T023 for the code's own attributes.

How to prove it in the data

Symptom: a material group appears in a purchasing report but purchasing users insist it should not exist. Select T023 on MATKL for that value. If no row is found, the code is invalid customizing that got into a material master or requisition through a data load or manual entry bypassing the check, and the fix is either to create the missing customizing entry or correct the material master. If the row exists, check T023T for the description text and confirm the division assignment matches what the business expects for that material group.

ECC vs S/4HANA

T023 continues to exist as a customizing table in S/4HANA in the same shape as in ECC. Material group logic was not restructured as part of the S/4HANA simplification items that affected material master fields like old dimension or unit tables. Access in reporting and Fiori apps typically goes through a CDS view exposing material group text and code together with MARA attributes, but the underlying customizing table itself is unchanged.

Common pitfalls

  • Assuming T023 encodes a hierarchy: it does not. Any grouping of material groups into higher-level categories is done in separate classification or reporting structures, not in this table.
  • Assuming the division field on T023 controls what division a material can be sold in: SPART here is a default or classification attribute of the group, not an enforcement rule on sales documents.
  • Deleting or renaming a material group code in T023 without checking usage first: existing material masters, open purchase requisitions, and historical documents still reference the old MATKL value, and removing the customizing entry breaks display and can block transactions that revalidate the field.
  • Confusing material group with product hierarchy: they are separate fields with separate customizing tables and separate purposes, one is Warengruppe and the other is a distinct hierarchy string, and mixing them up during data migration is a common source of reporting errors.
  • Expecting T023 to drive account determination directly: in most standard configurations account determination runs off valuation class on MBEW, not off material group, though some custom account determination logic may key off MATKL.
  • Treating a missing T023 entry as a material master data error: it is a customizing gap, and the fix belongs in configuration transport, not in a material master mass change.

Whose problem this is

Ownership sits with the MM customizing team, usually the same group that owns material master configuration and division setup. Changes to the material group list go through a change request process because the code is referenced across purchasing, sales, and reporting; a functional consultant should never add or remove an entry directly in production without checking downstream usage first.

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Source: ERPClimb — https://erpclimb.com/sap-tables/t023ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.