DD02L table — ABAP Dictionary table catalog

One row in DD02L represents the header definition of a single ABAP Dictionary table-like object: a transparent table, a pooled table, a cluster table, a database view, or a structure. The row records what kind of object it is and what version state that definition is in, not its fields and not its description text. Every time a table or structure is created or changed in SE11, a row here is written or updated to reflect the new active or inactive version. Standard SAP tables, custom Z/Y tables, and generated structures (for example those behind a BAPI or an IDoc segment) all appear here identically, distinguished only by TABNAME and TABCLASS. This is the table an ABAP developer checks first when asking whether an object exists in the system at all, before looking at its fields.

DD02L is cross-client Dictionary metadata; there is no MANDT field to restrict on. Always restrict on TABNAME first, ideally with a pattern anchored to a known prefix (Z*, Y*, or a specific module prefix) — the table holds every SAP standard and custom object in the system, easily tens of thousands of rows, and an unrestricted browse in SE16 is slow and unhelpful. If scanning by TABCLASS to find, for example, every custom transparent table, combine it with the TABNAME pattern; TABCLASS alone returns huge result sets dominated by SAP-delivered objects. AS4LOCAL should be checked explicitly if the question is about activation state, not assumed.

Symptom: activation or usage of a table fails with 'table does not exist' or a runtime short dump referencing an unknown object. Select DD02L where TABNAME equals the exact object name. No row at all means the object was never created, or was deleted, in this system. A row with AS4LOCAL showing the inactive/saved state (and no corresponding active version) means someone changed the definition and never activated it — the object exists in the Dictionary but is not usable by programs yet.

DD02L continues to exist unchanged in shape and purpose on S/4HANA; the ABAP Dictionary catalog itself was not restructured by the S/4HANA data model simplifications. The compatibility-view mechanism that replaced many classic application tables (finance and logistics tables in particular) sits one layer above the Dictionary catalog, not inside it — DD02L still describes those compatibility views, the underlying pooled/cluster tables, and every custom table exactly as it did in ECC, and is still browsed the same way in SE11 or SE16.

This is Dictionary metadata, so questions about it belong to the ABAP development team, not to a functional module owner. When a functional consultant hits a missing-table error, the first move is to hand the object name to a developer who can check DD02L and DD03L directly rather than guessing from the application layer.

DD03L holds the field list for each object catalogued in DD02L. DD04T supplies the human-readable short texts for the data elements attached to those fields. TADIR classifies every object, including tables, by package, object type, and original system. E070 and E071 record which transport requests carried changes to a given table definition. All of these are populated or read through SE11/SE80 activity rather than by any application transaction.