T100 table — SAP Message Texts

T100 is the central repository table for classic ABAP message texts. A message is identified by message class and number, with one text row per language. ABAP programs, function modules, classes, and framework code raise these messages at runtime, substituting variables into placeholders. The table is repository/translation content rather than application transaction data.

Message identity requires class, number, and language.

T100A provides message-class-level attributes. SE91 maintains message classes and messages. Application logs, dumps, IDoc statuses, and business transactions may store or display a message class/number plus variables, which can then be resolved to T100 text for the user's language.

Always filter by language, message class, and message number. Do not search only by message number because each class has its own numbering. Text can differ by language and placeholders can make the displayed runtime message look different from the stored template. Use the class/number from the technical message details whenever possible.

For an error whose wording differs between users, capture the technical message class and number plus runtime variables, then compare T100 rows for the relevant languages. If one translation is missing, determine the fallback or translation process. If the T100 text is correct but the displayed values are wrong, debug the code that supplies message variables rather than changing the message text.

Trace the reported error to message ID and number using the exception or technical details. Inspect the corresponding T100 rows in the affected languages and compare the text placeholders with the actual variables passed by the caller. If a message exists but seems wrong, look at the MESSAGE statement or application layer, not only the text table. Never edit translated text with direct SQL.

T100 remains a core ABAP repository message table in S/4HANA and is not part of business-data simplification. Fiori or OData applications can surface backend T100 messages through service error handling, but UI5 applications may also have their own i18n resources. Distinguish an ABAP backend message from a frontend text resource before editing translations.

Production incident: an error appears in English for one user but a different message is displayed in German, even though both users execute the same ABAP path. Check message class, message number, language key and the runtime substitution variables separately. T100 is a template repository; the application chooses variables and can format or supplement the final error. Changing an English text will not necessarily fix a missing translation or a message raised by the wrong class.

ABAP/application teams own custom message classes and the code that raises them. Translation teams own language versions. Functional teams own the business cause of standard application messages; changing T100 text should not be used to hide the underlying process or configuration error.

T100A stores message-class metadata. SE91 maintains message classes and texts. ST22, SLG1, IDoc monitors, and application logs often expose technical message identifiers that can be resolved through T100.