TSTC table — TSTC Transaction Code Table

One row in TSTC represents a single transaction code defined in the system: the four-to-twenty character code a user types into the command field, together with the ABAP program and initial screen number that code launches. For parameter or variant transactions, the row instead carries the additional start parameters that get applied when the transaction runs, and the program field is left blank. Every transaction created through SE93, whether standard SAP delivered or custom Z/Y, results in a row here. It is the runtime lookup table the kernel consults the moment a user enters a transaction code, before any authorization or lock checks happen. It says nothing on its own about whether the transaction is currently usable.

Always filter on TCODE, the key field; lookups are single-value so there is rarely a reason to scan without one. The table is small relative to most application tables (tens of thousands of rows across a system), so a full read is not expensive, but restricting on TCODE first still avoids pulling in unrelated entries when joining to TRDIR or TADIR. Transaction codes are case-sensitive and always uppercase internally, so a value copied from a document with trailing blanks or lower case will not match and will look like a missing entry when it is actually a formatting problem in the selection.

Symptom: a user reports 'transaction XYZ does not exist' or gets a 'transaction cannot be started' message. Select single from TSTC where TCODE = 'XYZ'. No row at all means the transaction was never created in this client/system, or existed and was deleted; check TADIR for a matching TRAN entry and E071 in the relevant transport request to see if it should have arrived. A row with PGMNA blank and CPARAM populated is a parameter transaction, not a data error; resolve the underlying target transaction from CPARAM before concluding anything is broken.

TSTC exists in S/4HANA in the same shape and role as in ECC; the transaction code dispatch mechanism was not replaced or restructured for HANA. It is still maintained through SE93 and read the same way. A transaction code being present in TSTC has no bearing on whether a corresponding Fiori app tile exists in the launchpad catalog, and the reverse is also true; the two are separate frameworks and separate tables entirely.

TSTC is a development object maintained through SE93 and owned by the ABAP/Basis or development team, transported like any other workbench object. Functional consultants should not edit it directly. When a transaction appears missing, locked, or misrouted, raise it as a development/transport question rather than attempting a fix in the table itself.

Closest neighbors are TSTCT for the description text, TSTCA for the authorization objects checked at start, TRDIR for the target program's own attributes, and TADIR for the transaction's package and original-system metadata. Transport movement of a transaction shows up in E071/E071K entries under object type TCOD. SE93 is the maintenance transaction for TSTC; SE16 or SE16N gives read-only access for troubleshooting.