DD04T table — DD04T Data Element Text Table

One row in DD04T represents the language-specific text set for a single data element, at a single dictionary version. A data element is defined once (in DD04L) with its type, length and domain assignment, but its display texts are maintained separately, per language, in DD04T. Those texts are what a user actually sees: the short field label next to an input field, the column heading in a list, the description shown when browsing the dictionary in SE11 or SE80. Changing a data element's underlying type does not touch DD04T; changing what a user reads on the screen does. Because texts are translated independently of structure, a data element can exist correctly for years with an English row present and a French row missing, silently falling back to the fallback language wherever the program runs.

DD04T is client-independent, like the rest of the ABAP Dictionary, so there is no MANDT field to restrict on. Always filter by ROLLNAME first, the table carries a row per data element per language and is large across a fully translated system. Restrict AS4LOCAL to the active indicator unless the goal is specifically to inspect a pending, not-yet-activated change. Restrict DDLANGUAGE to the language actually being investigated; scanning without a language filter returns every translation and makes the result hard to read. Never query this table expecting a MANDT-scoped answer — a text change here is visible in every client at once.

Symptom: a field label reads correctly in German but shows the wrong text, or no text, in English. First identify the data element behind the field, either from the ABAP Dictionary field display or by joining DD03L to the table and field name. Then select DD04T where ROLLNAME equals that data element, DDLANGUAGE = 'E', and AS4LOCAL is the active indicator. Compare SCRTEXT_S, SCRTEXT_M and SCRTEXT_L against what the screen actually renders — if no row comes back for English, the translation was never maintained and the system is falling back to another language.

DD04T is unchanged in S/4HANA. It is a core ABAP Dictionary table, not a business data table, and none of the S/4HANA data model simplifications touch it. There is no CDS compatibility view layered over it because nothing about its structure or purpose needed to change; the Dictionary's own text handling for data elements works the same way it did in ECC.

A wrong or missing field label is normally raised as a functional defect but the fix belongs to whoever owns the custom or modified data element, typically the ABAP developer who created it. Standard SAP data elements are not to be edited; if a standard label is wrong, the fix path is a modification or an object-specific text override, not a direct table change.

DD02L is the table master that anchors DD03L's field list, which in turn supplies the ROLLNAME used to reach DD04T. DD07T plays the equivalent text role for domain fixed values and is easy to mistake for DD04T when the wrong screen element is misbehaving. Text maintenance normally happens inside SE11 or SE80 rather than by writing to DD04T directly.