DD07T table — Domain Fixed Values Text Table

One row represents the text, in one language, for one fixed value of one domain. Domains in the ABAP Dictionary can carry a list of fixed values (a value range restriction), for example a domain for order status carrying values 'A', 'B', 'C'. DD07L holds the actual value or value range for each entry. DD07T holds only the accompanying description, split out by language, because SAP dictionary objects separate the technical definition from its translated text. When a screen field built on that domain offers an F4 dropdown, the values come from DD07L and the labels shown next to them come from DD07T, filtered to the logon language. If a fixed value exists in DD07L but has no corresponding DD07T row in the user's language, the dropdown shows the raw value with no description, or falls back to another language if one is maintained.

DD07T has no client field, it is cross-client dictionary data, same content in every client of the system. Selectivity comes from DOMNAME and DDLANGUAGE together; querying by DOMNAME alone across all languages returns duplicates that look like inconsistent data but are just the translated variants. Restrict to a single language before comparing texts, and remember that the logon language of whoever reported the issue is the one that matters, not English. Do not query this table directly in application logic; use the dictionary text lookup function modules or the domain value help APIs, because direct table reads bypass buffer handling and fallback language logic that the standard dictionary access already provides.

Symptom: a dropdown on a custom screen shows the technical code instead of a description for users in a specific language. Select DD07T where DOMNAME equals the domain assigned to the field (found via DD03L) and DDLANGUAGE equals the user's logon language. If no row comes back, the text was never translated into that language, confirming the gap. If a row exists but DDTEXT is blank, the value was added to DD07L without ever entering a text, which is a data entry gap in domain maintenance, not a program bug.

DD07T is unchanged in S/4HANA. Domains and their fixed values remain a core ABAP Dictionary concept and this table continues to carry the translated texts exactly as in ECC. There is no compatibility view replacing it because it is dictionary metadata, not application master data, and dictionary metadata tables were not part of the S/4HANA simplification of finance and logistics tables.

This is an ABAP development question, not a functional configuration question. Domain and fixed value maintenance belongs to whoever owns the data element or domain in the development team, usually the technical lead on a custom development object or the SAP Basis or development team for standard SAP domains, since standard domain texts should never be modified directly.

DD03L supplies the table-field-to-domain link needed to find which domain governs a given field. DD02L identifies the table itself before drilling into its fields. DD04T carries the text for data elements, a related but separate translation layer above the domain level. T002 resolves language keys used throughout dictionary text tables including this one. Domain and fixed value maintenance is done through the ABAP Dictionary domain editor, not through a direct table maintenance transaction.