TSTCT table — TSTCT - Transaction Code Text Table

Each row in TSTCT stores the short text label for one transaction code in one language, nothing else. When a user opens the SAP Easy Access menu, runs SE93 to inspect a transaction, or types a partial name into the transaction search, the label they see comes from TSTCT keyed by the current logon language. The table is cross-client, meaning the text is the same regardless of which client the user is logged into, but it is not automatically the same across systems unless transported. A transaction code can exist perfectly well in TSTC with a working program assignment and still have no row in TSTCT for a particular language, in which case the system falls back to another language or shows the text blank. TSTCT never determines execution behavior, screen flow, or authorization - it is purely descriptive metadata.

TSTCT is a small, flat, cross-client table, so it is not a performance risk even without restriction, but always filter on SPRSL first when doing a lookup, otherwise every language variant of the text comes back and gives a false impression of duplication. When comparing systems, remember that the same TCODE can carry different TTEXT values in each system if the underlying transport was never released, so a mismatch in text is not evidence of a functional difference. Do not use TSTCT alone to check whether a transaction exists; TSTC is the authoritative existence check, TSTCT is only the label attached to it.

Symptom: a transaction shows correctly in the menu for English users but appears blank or shows the technical code instead of a description for German users. Select TSTCT where TCODE equals the transaction code and SPRSL equals 'D'. If no row returns, the German text was never maintained or never transported, and the English fallback (or blank) is expected behavior, not a bug in the transaction itself.

TSTCT is unchanged in S/4HANA and continues to be maintained the same way, through SE93 when creating or changing a transaction code, with the language-specific text propagated by standard translation and transport mechanisms. It has not been replaced by a CDS compatibility view and is still queried directly by tools that build transaction lists or menu trees. No structural changes are expected between ECC and S/4HANA for this table.

This is an ABAP development or Basis housekeeping question, not a functional one. When a custom transaction shows an empty or wrong description, the developer who created it in SE93 owns the fix; when the discrepancy spans multiple languages or systems, the transport team owns tracing whether the text object was released and imported. Functional consultants only encounter this table when documenting or auditing which transactions exist for a process area.

TSTC is the parent table holding the actual transaction definition, program assignment, and screen number; TSTCA holds the authorization object checks tied to a transaction code; TADIR with object type TRAN records the package and transport classification of the transaction; T002 supplies the readable name for the SPRSL language key. SE93 is the transaction used to create or edit both the TSTC entry and its TSTCT text in one screen; SE16N or a similar table browser is used only to inspect the data, never as the normal maintenance path.