SEOCLASS table — SEOCLASS table for ABAP class definitions

SEOCLASS stores one row per ABAP class per version, active or inactive, created through the Class Builder (SE24) or through ABAP Development Tools. The row carries structural, header-level attributes of the class itself: its category, whether it is final, whether it is abstract, its state, and audit fields for who created or last changed the definition. It does not carry the class's methods, attributes, events, or types, and it does not carry documentation text or source code. Interfaces are a separate object type in the same OO repository family and are not rows in this table; they live in their own header table. A missing row for a name a developer expects to see is therefore not proof that nothing was ever built under that name, only that no class header exists under that exact name and version.

SEOCLASS is a cross-client repository table, so there is no client field to restrict on. Always restrict on CLSNAME, ideally with an exact name rather than a wildcard, since the table spans the entire class population of the system including SAP standard classes. When a class has both an active and an inactive version, both rows exist with the same CLSNAME and different VERSION values; filtering on VERSION = 'A' avoids confusing an unreleased change with the live definition. Selecting by CATEGORY alone across the whole table is expensive and rarely useful without also joining through TADIR to a package, since the table has no package field of its own.

Symptom: a developer insists a custom class ZCL_FOO exists but a transport or call fails as if it does not. Select single from SEOCLASS where CLSNAME = 'ZCL_FOO' and VERSION = 'A'. No row means no active class header exists under that exact name, regardless of what is visible in an editor buffer. If a row exists only with VERSION = 'I', the class was saved but never activated, which explains why other objects referencing it fail at runtime or activation.

SEOCLASS is unchanged in shape and purpose on S/4HANA. It is still populated the same way by the Class Builder and by ABAP Development Tools, and it has not been superseded by a CDS compatibility view, since it is core ABAP repository metadata rather than an application table exposed to reporting. Consultants working across ECC and S/4HANA on the same custom development can rely on the same field layout and the same lookup logic on either side.

Any question about what SEOCLASS actually contains belongs to the ABAP development team, specifically whoever owns the class in question. Basis or transport teams get pulled in only when the question is about which request carries the object, via the TADIR and E071 join, not about the class's internal attributes.

SEOCOMPO holds the class's methods, attributes, events and types and is the table most people actually want when they think they want SEOCLASS. A companion text table holds the class's short description in each language, and a relationship table tracks inheritance and interface implementation, but neither is safe to name here with full certainty of spelling. TADIR and E071 place the class in its package and transport context. The transactions that write to SEOCLASS are the Class Builder and ABAP Development Tools; SE80 and mass transport tools read it but do not write to it directly.