Data Dictionary (SE11) — SAP’s Central Repository

eLearning Solutions - Blog - Data Dictionary (SE11) — SAP’s Central Repository
Data Dictionary (SE11) in ABAP: Complete Guide 2026 | ABAP Zero to Hero
ABAP Zero to Hero

Chapter 05  ·  Core Classic ABAP

Data Dictionary (SE11)

The central repository where SAP defines every table, data element, and structure — and how modern Cloud developers work with it too.

Chapter 5 of 20 22 min read Part 2: Core Classic ABAP 6 Interview Q&A

Welcome to Part 2 of the series. From this chapter onward, we enter the world of Core Classic ABAP — the part of the ABAP ecosystem that still powers roughly 70 percent of SAP jobs today.

Up to now, you have stored data in variables. But variables live only as long as the program is running. The moment you exit, everything is gone. Real enterprise systems need data that persists — that survives program runs, system restarts, and years of business operations.

That is where the ABAP Data Dictionary comes in. It is SAP’s central repository for defining every type and every table used across the entire system. When you write a SELECT statement in Chapter 6, the table you query was defined here. When you create a custom report that stores its output, the structure of that output was defined here. The Data Dictionary is the foundation of everything that stores data in SAP.

What you will produce by the end of this chapter A working understanding of the Data Dictionary, plus a custom domain, data element, structure, and transparent table that you will use to store real data in Chapter 6.

🎯 Who Is This Chapter For?

This is a pivotal chapter because the Data Dictionary is where the free and paid paths diverge the most. Here is how to read it:

  • If you are on the FREE BTP Trial → you cannot access SE11. Instead, you will learn the concepts of the Data Dictionary and see how they map to modern ABAP Cloud equivalents like CDS Views and DDIC-based types available in Eclipse ADT. You will still understand every concept — just through a different lens.
  • If you have PAID SAP access → you will do the full SE11 work. You will create domains, data elements, structures, and transparent tables directly in SAP GUI, then use them from ABAP Cloud (via released CDS Views) and Classic ABAP (via SELECT).
  • Both paths teach the same core ideas: how SAP separates type definitions from data storage, why domains and data elements exist, and what makes a transparent table different from a structure. The tooling differs; the thinking is identical.

🎯 What You Will Learn in This Chapter

  • What the ABAP Data Dictionary is and why SAP has a central repository
  • The three-level type model: domain → data element → table field
  • How to create custom data elements and domains in SE11 (paid path)
  • How to create a custom transparent table (paid path)
  • How the Data Dictionary maps to CDS Views and ABAP Cloud concepts (free path)
  • The difference between a structure and a transparent table
  • How tables are activated and what activation means for DDIC objects

🧭 Which Path Should I Choose?

Before starting, decide which path applies to you. This chapter is where the two paths differ most.

Two learner types — find yourself

🟢
1. Free BTP Trial learner SE11 is not available on BTP Trial. You will learn the Data Dictionary concepts and see their Cloud equivalents in Eclipse ADT — CDS Views, ABAP DDIC types, and RESTful data access through RAP.
🔵
2. Paid SAP access learner You will do the full SE11 work. Create a domain, data element, structure, and transparent table. This is one of the most important skills in Classic ABAP and appears in every interview for junior and mid-level roles.
Both paths lead to the same outcome Free learners understand what the DDIC is and how to work with it via CDS Views. Paid learners can also create DDIC objects directly. In interviews, free learners describe Cloud equivalents; paid learners describe both.

What You Can Do With Each Path

Task🟢 Free Path (BTP Trial)🔵 Paid Path (SAP System)
Access SE11❌ Not available✅ Full access
Create domains and data elements❌ Not available✅ Via SE11
Create transparent tables❌ Not available✅ Via SE11
Work with CDS Views✅ Full support in Eclipse ADT✅ Full support
Use ABAP DDIC types✅ Via released DDIC types✅ Full DDIC access
Define custom tables in Cloud⚠️ Limited — through RAP business objects✅ Full control via SE11
EditorEclipse ADTSAP GUI + Eclipse ADT

📘 What is the ABAP Data Dictionary?

The ABAP Data Dictionary, also called the DDIC, is SAP’s central repository of type definitions. Every table, every field, every structure used in the entire SAP system is defined here. Nothing is stored anywhere else.

Think of it this way:

Analogy If SAP is a library, the Data Dictionary is the card catalog. Every book (table) and every title (field) is documented in one central place. When you want to check out a book, you do not search every shelf — you go to the catalog first.

The Data Dictionary does four essential jobs:

  • Defines types: What is a customer ID? What is an order date? These definitions live here.
  • Defines tables: Where customer data is stored, with which fields, in which order.
  • Enforces consistency: Every program across the system uses the same definition, so data is uniform.
  • Integrates with the database: When you create a transparent table in the DDIC, SAP automatically creates the corresponding table in the underlying database (HANA, Oracle, etc.).

The three-level type model

Before you create anything, you must understand how SAP structures its type definitions. It uses a three-level hierarchy:

LevelWhat it isExample
DomainDefines the technical characteristics: data type and lengthCharacter, length 10
Data ElementAdds semantic meaning: field labels and documentation“Customer ID” (uses the domain)
Table FieldA field in a table, typed by a data element“CUSTOMER_ID” field in a customer table

Why three levels? Because SAP separates technical definitions from business definitions. The domain says “this is a 10-character field”. The data element says “this is a Customer ID and the label is Customer ID”. This separation lets you reuse the same domain across many data elements.

Real-world example A single domain ZDOM_CHAR10 (character, 10 characters) can be reused by a dozen data elements: Customer ID, Vendor ID, Product Code, Employee Number. Each data element has its own meaning and labels, but shares the underlying technical definition.
🟢 Free Path

DDIC Concepts in Cloud

In ABAP Cloud, you do not create DDIC objects manually. Instead, you use released DDIC types provided by SAP and define your own types through CDS Views or ABAP Cloud types.

  1. Read about domains and data elements (concepts)
  2. See how CDS Views replace some DDIC work
  3. Use SAP-released DDIC types in your code
  4. Learn what you would do with SE11 if you had it

Full SE11 Access

You will create each DDIC object step by step, activate it, and see how SAP generates the underlying database table.

  1. Create a custom domain
  2. Create a data element on that domain
  3. Create a structure using data elements
  4. Create a transparent table and activate it

🖥️ The SE11 Transaction — Your DDIC Workspace

All Data Dictionary work happens in transaction SE11. This is one of the most-used transactions in all of SAP.

When you open SE11, you will see a simple screen with radio buttons for the type of object you want to work with:

  • Database Table — Create or edit transparent tables
  • View — Create database views, projection views, and other DDIC views
  • Data Type — Create data elements, structures, and table types
  • Type Group — Rarely used except in older code
  • Domain — Create domains
  • Search Help — Create F4 help dialogs
  • Lock Object — For concurrency control
Free path: read only If you are on BTP Trial, you cannot access SE11. Treat this section as conceptual learning. The objects below exist, but you will interact with them differently through CDS Views and ABAP Cloud types.

📦 Step 1: Create a Domain (Paid Path)

A domain defines the technical characteristics of a field: its data type and length, and optionally a list of allowed values.

🔵 Paid Path (SE11)

1 Open SE11

In SAP GUI, type SE11 in the command field and press Enter.

2 Select “Domain” and name it

Select the Domain radio button. Enter a name like ZDOM_CUST_ID. Click Create.

3 Define the domain properties

On the domain maintenance screen, set:

  • Data Type: CHAR
  • Length: 10
  • Description: Customer ID Domain

Save and activate with Ctrl + F3.

4 Optional: add fixed values

In the Value Range tab, you can add a list of allowed values (for example, “A” = Active, “I” = Inactive). For a Customer ID, you usually skip this — the values are too numerous.

Domain created You now have a reusable technical definition. Any data element can use this domain to inherit the type and length.

🟢 Free Path (ABAP Cloud)

You cannot create a domain. In ABAP Cloud, the equivalent is to define a CDS View with a typed cast, or to use an SAP-released DDIC type that already exists. For example, the SAP-released data element BU_PARTNER serves the same purpose as a domain-plus-data-element for customer/vendor IDs.

📦 Step 2: Create a Data Element (Paid Path)

A data element adds business meaning to a domain. It defines the field labels and documentation.

1 Switch to Data Type in SE11

Go back to SE11. Select Data Type and enter ZDE_CUST_ID. Click Create.

2 Select “Data Element”

Choose the Data Element radio button and click Continue.

3 Assign the domain

In the Type Information section:

  • Type: Domain
  • Domain: ZDOM_CUST_ID
4 Add field labels

Go to the Field Labels tab and enter:

  • Short: Cust. ID
  • Medium: Customer ID
  • Long: Customer Identification Number
  • Heading: Customer ID

These labels appear automatically in reports, screens, and F4 help dialogs. Save and activate.

Data element created Now any table field or structure field can use ZDE_CUST_ID as its type, and it will automatically inherit the technical definition and labels.

🟢 Free Path (ABAP Cloud)

The Cloud equivalent is a CDS View field with an annotation that provides a label. For example, in a CDS View, you can write:

@EndUserText.label: 'Customer ID'
key customer_id as CustomerId

This attaches the same business label to the field. The concept is identical — just expressed in CDS syntax.

🏗️ Step 3: Create a Structure (Paid Path)

A structure groups related fields. Unlike a table, a structure does not store data — it defines the shape of data that will be used somewhere else (as a parameter, a result, or part of a table).

1 Open Data Type in SE11

In SE11, select Data Type and enter ZST_CUSTOMER. Click Create, then choose Structure.

2 Add component fields

Add these components:

  • customer_id TYPE ZDE_CUST_ID
  • customer_name TYPE CHAR50
  • city TYPE CHAR30
  • join_date TYPE DATS
3 Save and activate

Save with Ctrl + S, activate with Ctrl + F3.

What just happened You created a reusable data shape that any ABAP program can reference. In Chapter 6, you will declare a variable of type ZST_CUSTOMER and use it directly.

🟢 Free Path (ABAP Cloud)

In ABAP Cloud, you have two options. You can declare a structure using TYPES: BEGIN OF ... END OF ... as you learned in Chapter 4, or you can use a CDS View as an “interface” for structure-like data. Both approaches work — the choice depends on whether the structure needs to persist or just describe in-memory data.

🗄️ Step 4: Create a Transparent Table (Paid Path)

A transparent table is the most important DDIC object. It corresponds directly to a physical table in the underlying database. When you activate it, SAP automatically creates the table in HANA, Oracle, SQL Server, or whichever database the system uses.

1 Open Database Table in SE11

In SE11, select Database Table and enter ZCUSTOMER. Click Create.

2 Set the Delivery and Maintenance options

On the initial screen:

  • Delivery Class: A (Application table)
  • Data Browser/Table View Maintenance: Display/Maintenance Allowed
3 Add fields

Switch to the Fields tab. Add:

  • MANDT — Type MANDT (client field — required for application tables)
  • CUSTOMER_ID — Type ZDE_CUST_ID (mark as Key field)
  • CUSTOMER_NAME — Type CHAR50
  • CITY — Type CHAR30
  • JOIN_DATE — Type DATS
4 Set the technical settings

Click the Technical Settings button and set:

  • Data Class: APPL0 (Master data)
  • Size Category: 0
  • Buffering: Buffering not allowed (for now)
5 Save and activate

Save with Ctrl + S. SAP will prompt you to create the database table — confirm. Activate with Ctrl + F3. The table now exists in both the DDIC and the underlying database.

Transparent table created You now have a table called ZCUSTOMER that can store actual data. In Chapter 6 you will use INSERT, UPDATE, and SELECT statements to work with it.
MANDT is required Every application transparent table in SAP starts with a MANDT field of type MANDT. This is the client field, used for multi-tenancy. If you forget it, SAP will warn you and most tools will not work with the table.

🟢 Free Path (ABAP Cloud)

In ABAP Cloud, you cannot create a transparent table directly. Instead, you define data as part of a RAP business object, which generates the persistence layer for you. This is covered in Chapter 17. For now, understand that the concept is the same — the difference is that Cloud enforces Clean Core principles, so tables are managed through business objects rather than raw DDIC work.

⚖️ Structure vs Table — What is the Difference?

This is one of the most common interview questions. Both group fields. The difference is entirely about whether data is stored.

AspectStructureTransparent Table
Stores data?❌ No — describes a shape✅ Yes — data persists
Exists in the database?❌ No✅ Yes — SAP creates it automatically
Used as a variable type?✅ Yes — declare with DATA✅ Yes — declare with DATA or SELECT INTO
Can have keys?❌ No✅ Yes — one or more key fields
Typical use caseParameters, method signatures, temporary dataStoring master and transactional data
Naming conventionZST_Z or ZT
The rule of thumb If you need the data to survive after the program ends, use a table. If you only need to pass it around while the program is running, use a structure.

☁️ How DDIC Concepts Map to ABAP Cloud

For free path learners, here is how every classic DDIC concept has a Cloud equivalent:

Classic DDIC (SE11)ABAP Cloud Equivalent
DomainCDS View field type / cast expression
Data ElementCDS View field with @EndUserText.label
StructureABAP Cloud TYPES: BEGIN OF or CDS View interface
Transparent TableRAP Business Object with managed persistence (Chapter 17)
Search HelpValue Help CDS Views with @Consumption.valueHelpDefinition
Lock ObjectManaged RAP with built-in locking
ViewCDS Views (Chapter 16)
Why this matters Even free learners must understand the DDIC conceptually, because interviews ask about it. Being able to say “In Classic ABAP you would do this in SE11; the Cloud equivalent is X” shows deep understanding.

🧠 What Just Happened Under the Hood

When you activate a transparent table, several things happen automatically:

StageWhat SAP Does
DDIC entryStores the definition in the ABAP Data Dictionary
Database tableIssues a CREATE TABLE statement to the underlying database
Runtime typeMakes the type available for use in ABAP programs
Generic servicesEnables the Table Maintenance Generator and Data Browser (SE16N) automatically
Version historyRecords the activation as a version so you can roll back

This is why SAP has such a powerful “single source of truth” model. Because everything is defined in one place and generated automatically, the DDIC, the database, and every program that uses the table are always in sync.

📝 Chapter Summary

  • The ABAP Data Dictionary is SAP’s central repository for all type and table definitions.
  • It uses a three-level hierarchy: domain → data element → table field.
  • Domains define technical characteristics (type, length).
  • Data elements add business meaning (labels, documentation).
  • Structures group fields but do not store data.
  • Transparent tables store data and are created automatically in the underlying database when activated.
  • Every application table requires a MANDT field for client isolation.
  • In ABAP Cloud, the same concepts exist as CDS Views, ABAP types, and RAP business objects.
  • All DDIC work is done in transaction SE11 (Classic ABAP only).

🎤 Interview Questions & Answers

Data Dictionary questions appear in nearly every ABAP interview. Know these answers cold.

1 What is the ABAP Data Dictionary and why is it important?

The ABAP Data Dictionary (DDIC) is SAP’s central repository for defining all data types, tables, and views used in the system. Every table, field, and structure in SAP is defined here, ensuring consistency across the entire system.

It is important because it eliminates redundancy. Instead of each program defining its own version of what a “customer ID” is, the DDIC provides a single definition that every program references. This also automatically generates the underlying database tables when you create transparent tables.

2 What is the difference between a domain and a data element?

A domain defines the technical characteristics of a field: its data type (CHAR, NUMC, INT, etc.), length, and any fixed value list. It says “this is a 10-character text field” but nothing about meaning.

A data element adds business meaning on top of a domain. It provides field labels (short, medium, long, heading) and documentation. It says “this 10-character field is a Customer ID and its label is ‘Customer ID'”.

You can reuse one domain across many data elements. This separation of technical and business definitions is a key DDIC design principle.

3 What is a transparent table and how does it differ from a structure?

A transparent table stores data physically. It corresponds directly to a table in the underlying database (HANA, Oracle, SQL Server, etc.). When you activate a transparent table in SE11, SAP issues a CREATE TABLE statement to the database.

A structure does not store data. It is just a template that describes the shape of data — useful for passing parameters, defining method signatures, and describing in-memory variables.

Rule of thumb: if the data needs to survive after the program ends, use a table. If it is only needed while the program is running, use a structure.

4 Why does every transparent table start with a MANDT field?

MANDT is the client field. SAP systems support multiple clients (essentially separate logical databases) within one physical system. The MANDT field isolates data by client — so client 100 and client 200 can have tables with the same name but completely separate data.

Every application transparent table must have MANDT as the first key field. SAP automatically filters SELECT statements by the user’s client, so users only see their own client’s data. This is called “client isolation” and it is one of SAP’s core multi-tenancy mechanisms.

5 What happens when you activate a transparent table?

When you activate a transparent table in SE11, several things happen automatically:

  • The DDIC stores the definition in the ABAP Data Dictionary
  • SAP issues a CREATE TABLE statement to the underlying database
  • The runtime type becomes available to all ABAP programs
  • The Data Browser (SE16N) and Table Maintenance Generator become available for the table
  • A version is recorded for change history

If you later change the table and reactivate it, SAP issues an ALTER TABLE statement. Some changes (like adding fields at the end) are safe; others (like reordering keys) require data migration.

6 How do Data Dictionary concepts map to ABAP Cloud?

ABAP Cloud uses modern equivalents for all classic DDIC objects:

  • Domains → CDS View field types and casts
  • Data elements → CDS View fields with @EndUserText.label annotations
  • Structures → ABAP Cloud TYPES: BEGIN OF or CDS View interfaces
  • Transparent tables → RAP Business Objects with managed persistence
  • Search helps → Value Help CDS Views

The concepts are the same, but Cloud enforces Clean Core principles so you do not write raw tables directly. This makes Cloud systems upgrade-safe and future-proof.

🛠 Practice Task for This Chapter

Complete the tasks for your path before moving to Chapter 6.

🟢 Free Path (BTP Trial)

  1. Research and list 5 SAP-released DDIC data elements you can use in ABAP Cloud (for example, BU_PARTNER, MATNR, VKORG).
  2. Create a new class ZCL_DDIC_CH5 in your package.
  3. Inside a method, declare variables using those SAP-released DDIC types.
  4. Write a comment above each variable explaining what the underlying DDIC data element represents.
  5. Output the field labels using cl_demo_output and take a screenshot.

🔵 Paid Path (SAP System)

  1. Complete all the free path steps above.
  2. Then open SE11 and create:
    • A domain called ZDOM_EMAIL (CHAR 100)
    • A data element called ZDE_EMAIL using that domain, with labels “Email Address”
    • A structure called ZST_CONTACT with fields: contact_id, name (CHAR50), email (ZDE_EMAIL)
    • A transparent table called ZCONTACTS with MANDT, contact_id (key), name, and email
  3. Activate each object in order (domain first, then data element, then structure, then table).
  4. Open SE16N and try to display the new table (it will be empty). Take a screenshot.
Why this matters Every ABAP interview asks about the DDIC. Being able to describe it clearly — and having created real objects — is what separates candidates who have “read about” SAP from candidates who have “worked with” SAP.
🎯 Chapter 5 Challenge

Test: Kon Banega Crorepati?

5 questions. ₹1 Crore. Prove you understood Chapter 5. No pressure — restart anytime.

₹1,000 ₹10,000 ₹1,00,000 ₹10,00,000 ₹1 Crore
Question 1 of 5
Score: 0
Q1
🏆
You Did It!
0/5 Correct Answers
You won ₹0
➡️ Next Chapter

➡️ Next Chapter

You now know how the Data Dictionary stores definitions. In Chapter 6, you will use Open SQL to read and write data in the tables you just created — the practical bridge between DDIC definitions and real business data.

Chapter 6 Open SQL — Reading & Writing Data →
Want to Learn Faster?

Explore Our Instructor-Led SAP & IT Courses

Self-study works. But if you want guided training, real project practice, and placement support — here are the courses we offer. Book a free demo before you decide.

S SAP Courses

SAP ABAP Training → SAP ABAP: Core programming language of SAP — reports, enhancements, interfaces, and modern RAP development.
SAP SD (Sales & Distribution) → SAP SD: Sales and Distribution — order-to-cash, pricing, billing, and shipping processes.
SAP HR / HCM → SAP HR HCM: Human Capital Management — personnel admin, payroll, and org management.
SAP FICO → SAP FICO: Finance and Controlling — GL, AP, AR, asset accounting, and cost centers.
SAP RAP → SAP RAP: RESTful ABAP Programming model for modern Fiori and S/4HANA apps.
SAP GRC → SAP GRC: Governance, Risk, and Compliance — access control and process control.
SAP BTP → SAP BTP: Business Technology Platform for integration, extension, and data-to-value.
SAP PP → SAP PP: Production Planning — MRP, capacity planning, and shop floor control.
SAP MM → SAP MM: Materials Management — procurement, inventory, and invoice verification.
SAP WM → SAP WM: Warehouse Management — storage bins, transfer orders, and inventory tracking.
SAP HANA → SAP HANA: In-memory database for real-time analytics and applications.
All SAP Courses → Browse the complete catalog of SAP training programs with certification.

T Technology & Other Courses

Oracle Courses → Oracle training for database, PL/SQL, and enterprise applications.
Salesforce Training → Salesforce Admin and Developer training for CRM mastery.
Full Stack Development → Full Stack Development — frontend, backend, and databases.
Software Testing → Software Testing: manual and automation testing for QA careers.
AWS (Amazon Web Services) → AWS: Amazon Web Services cloud certification and training.
Cloud Computing → Cloud Computing fundamentals and advanced cloud architecture.
Data Science → Data Science: Python, ML, and analytics for data-driven roles.
📅 Book a Free Demo 🔍 Explore All Courses

WhatsApp WhatsApp us
Call Now Button