TRDIR table — TRDIR ABAP Program Directory Table

One row in TRDIR represents a single ABAP program known to the system kernel, identified by its program name. This covers executable reports, module pools, includes, function groups (as generated programs), class pools and interface pools, subroutine pools generated for BDC or dynamic ABAP, and generated programs behind things like Smart Forms or screen painter output. The row carries the program's type and subtype, its unicode-compatibility flag, whether it is flagged as fixed point arithmetic, its logical database assignment if any, and administrative stamps for who created or last changed it and when. TRDIR is populated and maintained by the ABAP runtime and the Repository Information System whenever a program is generated, activated, or its attributes are changed in the ABAP Editor, not by application transactions.

TRDIR is client-independent; there is no MANDT field, so a lookup returns the same row regardless of logon client. It is small relative to most application tables but still spans every program in the system including SAP standard code, so always restrict on NAME with a pattern (LIKE 'Z%' or 'Y%' for custom code, or an exact name when chasing a specific dump) rather than pulling the whole table. Selecting on SUBC alone to find 'all function groups' or 'all classes' is technically possible but slow and rarely the right question - go through TADIR or the class/function directories instead and use TRDIR only to check the generated program's own attributes.

Symptom: a program compiles or activates cleanly in one system but throws a unicode syntax error in another. Select TRDIR where NAME equals the program name and check UCCHECK. If it is blank or space in the failing system and X in the working one, the program was never regenerated with unicode checks active there, which is a generation/activation gap, not a code defect. Compare against REPOSRC for the same program to confirm the source itself is identical across systems before concluding it is a TRDIR flag issue.

TRDIR continues to exist in S/4HANA as part of the classic ABAP runtime and dictionary layer; it has not been replaced by a CDS compatibility view in the way many application master data tables have. Its role is unchanged - the kernel still consults it whenever a program is loaded or generated. What has changed on S/4HANA projects is that a much larger share of relevant logic sits in classes and CDS views rather than classic reports, so TRDIR investigations are proportionally rarer than in an ECC-era custom code base.

This is technical basis/ABAP territory, not a functional master data question. A basis or development-support consultant checks TRDIR when chasing a dump, a generation error, or a unicode activation gap. Functional consultants should escalate to development rather than trying to interpret STATE or SUBC values themselves, since a wrong read here is often mistaken for a missing authorization or transport issue.

REPOSRC holds the actual source code lines for the same program name and is the table to check alongside TRDIR when comparing code across systems. TADIR is the repository object register and the correct place to check package, original system, and transport status. TSTC links transaction codes to the program TRDIR describes, and TFDIR links a function module to its generated group program listed in TRDIR. All of these are maintained through the ABAP Workbench (SE38, SE80, SE37) rather than through any functional transaction.