SAP tables · LessonBy Arjun, SAP Solution Architect · Published · SAP S/4HANA 2023 · all levels
MAKT
MAKT is a key SAP table in MM (Materials). It stores material descriptions (short texts) by language, so a material has a readable name in each maintained language.
Quick answer
When a report shows material descriptions, they usually come from MAKT for the logon language.
Key takeaways
- The key is MATNR + SPRAS, one description per material per language.
- SPRAS, language key (key).
- MARA, general material data.
- Watch out: Reading tables directly instead of using CDS/reports where appropriate.
What it stores
It stores material descriptions (short texts) by language, so a material has a readable name in each maintained language.
Key fields
- MATNR, material (key).
- SPRAS, language key (key).
- MAKTX, material description (short text).
- MAKTG, description in uppercase (search).
Keys and relationships
The key is MATNR + SPRAS, one description per material per language. It is the go-to table to get a material’s readable name for reports.
Working with it
When a report shows material descriptions, they usually come from MAKT for the logon language. Join MARA–MAKT on MATNR (and filter SPRAS) for numbers with names. View its structure in SE11 and its data (with authorization) in SE16N.
Common pitfalls
- Reading tables directly instead of using CDS/reports where appropriate.
- Ignoring header/item relationships.
- Performance: querying large tables without indexed selection.
Practice challenge
+0 XPStreak ×0
Question 1 of 3
Which statement is true of MAKT?
Frequently asked questions
What does MAKT stand for in SAP?
MAKT is a key SAP table in MM (Materials). It stores material descriptions (short texts) by language, so a material has a readable name in each maintained language.
What is worth remembering about MAKT in practice?
When a report shows material descriptions, they usually come from MAKT for the logon language.
What is another point to note about MAKT?
The key is MATNR + SPRAS, one description per material per language.
What tends to go wrong with MAKT?
Reading tables directly instead of using CDS/reports where appropriate. Ignoring header/item relationships. Performance: querying large tables without indexed selection.