Explain ABAP Dictionary (Data Dictionary / DDIC) in SAP

8 / 65

ABAPbeginner

ABAP Dictionary (Data Dictionary / DDIC)

Central repository for defining database tables, structures, data elements, domains, and views used across ABAP programs.

The ABAP Dictionary (SE11) is where SAP's entire data model lives, and interviewers use it to check whether a candidate understands the layered design SAP uses to keep field definitions consistent across thousands of tables and programs. Getting this wrong (e.g., hard-coding field lengths instead of referencing a data element) is a classic sign of inexperience.

A domain is like a raw material spec (steel, grade, dimensions); a data element is a labeled component built from that material (a bolt of that steel with a part number and description) usable in many different assemblies while sharing the same underlying material spec.

Key Concepts

The object hierarchy runs domain (technical properties: data type, length, value range/fixed values) -> data element (semantic meaning: field labels, F1 documentation, referencing a domain) -> table field (referencing a data element inside a transparent table, structure, or view). This separation means changing a domain's length in one place propagates everywhere it's referenced, which is exactly why SAP objects are so consistent across the system.

Transparent tables map 1:1 to an actual physical database table; other DDIC table types include cluster tables (multiple logical tables stored in one physical table, mostly legacy HR/logistics use) and pooled tables (small control tables grouped physically), both largely superseded on HANA where nearly everything is transparent. Views (database views built with joins, projection views, maintenance views, help views) let developers expose combined or restricted data without denormalizing it physically.

Candidates should also mention foreign keys, check tables, and search helps (SE11 "search help" objects, F4 value help) as the mechanisms that enforce referential integrity and provide the dropdown/value-help behavior end users rely on, plus append structures and include structures as the standard, upgrade-safe way to add customer fields to SAP standard tables.

SE11