MAKT table — Material Descriptions Table MAKT

One row in MAKT represents the description of a single material in a single language. A material with descriptions maintained in five languages has five rows in MAKT, one for each language key, all pointing back to the same material number in MARA. The table carries no plant, valuation, or sales data whatsoever; it is purely the text layer of the material master. When a material is created, at minimum the description in the logon language of the user creating it is written here. Additional language rows only exist if someone has explicitly maintained a translation, either manually or through a translation transaction. If a language row is missing, the material still exists and functions normally in every other respect; only the description defaults to blank or falls back to another language depending on the calling program.

Always restrict by MANDT even in tools that hide it by default, and always restrict by SPRAS when reading more than a handful of materials, otherwise every material returns one row per maintained language and totals look inflated. MATNR alone is not selective across a large material master; combine it with SPRAS or run it for a specific material number when troubleshooting a single case. There is no plant or organizational filter available on this table because none of that data lives here, so joins to MARC or MVKE are the only way to scope a description lookup to a business context like a specific plant or sales area.

A user reports that a material shows the correct description in one language but blank or wrong text in another screen or report. Select MAKT with MATNR equal to the material number in question, no SPRAS restriction, and inspect every row returned. If only one language row exists, the blank description elsewhere is expected behavior, not a data error; the fix is to maintain the missing translation, not to investigate the transaction that displayed it blank.

MAKT is unchanged in structure and continues to be the live table for material descriptions on S/4HANA. It is exposed through standard CDS views used by Fiori material apps and analytical reporting, but the underlying table itself was not restructured or merged as part of the simplification of inventory management tables. Consultants coming from ECC can rely on the same key fields and the same join pattern to MATNR without adjustment.

The material master data team owns description content and translation completeness; they are the ones who maintain or correct MAKTX through the material master transaction. Functional consultants confirm which language context a failing document or report is using before escalating a blank description as a data issue. A missing translation is a master data maintenance task, not a configuration or development defect.

MARA holds the basic data record that MAKT descriptions attach to, and both are written together whenever a material is created or renamed through the material master maintenance transaction. MARC and MVKE carry the plant and sales views that reports typically join to MAKT for a business-scoped description. Purchasing and sales documents such as EKPO and its downstream text pulls read MAKT once at document creation and then store their own copy independently of later changes.