SAP DDIC
The SAP DDIC (Data Dictionary) centrally manages data structures such as tables, fields, data types and relationships. In SAP S/4HANA, it continues to form the basis for consistent data models and high-performance applications.
What is the SAP DDIC?
The SAP DDIC serves as the central metadata management system in SAP. It defines tables, fields, data types and relationships, and ensures that data is used consistently across the system.
In SAP S/4HANA in particular, the DDIC remains a key foundation for modern data models and high-performance applications.
The SAP DDIC manages what is known as metadata, i.e. technical descriptions of data objects. These include:
- Tables
- Data elements
- Domains
- Structures
- Views
- Search aids
- Lock objects
Thanks to the centralised definition, data objects can be reused without having to recreate them each time.
Structure of the SAP DDIC
The following table provides a concise overview of the structure, key terms and functions of the SAP DDIC.
| Object | Function |
| Table | Storage of business data |
| Data element | Technical description of a field |
| Domain | Technical definition of a field |
| Structure | Summary of several fields |
| View | A virtual view of data |
| Search help | Assistance with submissions |
| Blocking object | Prevents concurrent changes |
Domain and data element
Domain
The domain defines technical characteristics such as:
- Data type
- Length
- Value range
Example:
- CHAR 10
- Numeric values
- Date format
Data element
The data element clarifies the business meaning of a field, for example:
- Material number
- Customer number
- Company code
This ensures that fields are used consistently across the system.
Tables in SAP DDIC
The transparent table is the most common type of table in the SAP DDIC. It corresponds directly to a physical database table and stores data in a format that is uniquely mapped at the database level.
Examples of transparent tables:
- MARA – Material master
- KNA1 – customer base
- VBAK – Sales document header
Depending on their intended use and the type of data they contain, transparent tables can also be categorised by function, for example into master data tables, transaction data tables and customising/configuration tables.
Master Data Tables: These tables store core, rarely changed business entities used across processes. Examples: MARA (General Material Data), KNA1 (Customer Master). Characteristics: High read frequency, low update frequency.
Transactional Data Tables: These tables record daily business activities and transactions, often referencing master data. Examples: VBAK/VBAP (Sales Order Header/Item), EKKO/EKPO (Purchase Order Header/Item). Characteristics: Heavily updated daily, high volume, and frequently changing.
Customizing/Configuration Tables: These tables hold configuration settings (customizing) that define system behavior and business rules.
DDIC in SAP S/4HANA
The data model has been simplified in SAP S/4HANA. Many of the old aggregate and cluster tables are no longer required.
Example MATDOC
In S/4HANA, the MATDOC table replaces several previous material document tables, such as:
- MKPF
- MSEG
This significantly improves performance.
CDS Views
In S/4HANA, Core Data Services (CDS Views) play a key role. They enable:
- modern data models
- high-performance analyses
- Fiori integration
The DDIC remains the technical foundation.
Search aids and blocked items
Search aids
Search aids assist users with data entry via the familiar F4 Help function.
Examples:
- Material search
- Supplier selection
- Company code
Blocked items
Locked objects prevent simultaneous changes to the same data and ensure consistent processes.
Key SAP transactions in the DDIC
| Transaction | Function |
| SE11 | ABAP Dictionary |
| SE16 / SE 16N | Table view |
| SE14 | Manage database objects |
| SM30 | Table maintenance |
| SE80 | Development environment |
Advantages and challenges of SAP DDIC
The SAP Dictionary offers numerous advantages:
- Consistent data structures
- Higher data quality
- Faster development
- Reusable objects
- Tight integration with ABAP
This makes maintenance and upgrades much easier.
Typical challenges include:
- redundant data elements
- lack of naming conventions
- outdated table structures
- lack of documentation
A well-organised DDIC structure is therefore particularly important, especially in S/4HANA projects.
FAQ on SAP DDIC
What does DDIC stand for?
DDIC stands for ‘Data Dictionary’.
Which transaction is used for the DDIC?
SE11
What role does DDIC play in S/4HANA?
The DDIC remains the foundation for tables, data types and modern CDS-based data models.
Conclusion
The SAP DDIC forms the central foundation for data structures in SAP systems. It ensures consistent data models, standardised development and high data quality.
The Data Dictionary remains indispensable in SAP S/4HANA too – particularly when used in conjunction with CDS views and modern HANA data models.
