Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

SE11 displays definitions of ABAP data objects. SE14 deals with database-related management tasks; a data definition and its physical database state are related but different.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

ABAP is SAP’s programming language for business applications. A program reads data, applies rules and produces a result. Start with the objects involved before investigating code.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for SE11 versus SE14: Dictionary definition and database adjustment are different
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

Classic ABAP Dictionary and Database Utility for applicable database objects; current product, database and managed upgrade procedures take precedence.

Primary documentation reviewed on 14 November 2026 using readable full text. Historical official SAP Library text reviewed; current platform-specific adjustment and upgrade procedures were not executed. All tables, values and verification steps are illustrative.

A MANUFACTURING EXAMPLE

Understand a plant reference-field change

Definition and database state

Named object: Z_ORDER_DATA. SE11 question: What is its definition?. SE14 question: What database state applies?. Before intervention: Confirm exact object type
What to notice: A structure and a physical database table are not the same kind of object. Display evidence before considering adjustments.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Named object
Z_ORDER_DATA
SE11 question
What is its definition?
SE14 question
What database state applies?
Before intervention
Confirm exact object type
Words you’ll meet in this guide
Program
A set of instructions executed by a computer.
Class
A reusable unit that groups data with operations called methods.
Database
Organized information kept beyond one program execution.
Internal table
A list of rows held temporarily in an ABAP program’s memory.
Key
One or more fields used to identify or find a record.
ABAP
SAP’s programming language for business applications.
CDS
Core Data Services: reusable definitions of business data and relationships.
SQL
A language used to read and work with database data.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Dictionary definition → Database object → Application access. Conceptual diagram for SE11 versus SE14: Dictionary definition and database adjustment are different.
Apply the idea: A manufacturer adds an external reference to a custom operational record and must distinguish its Dictionary definition from the database state.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Understand a plant reference-field change

    A manufacturer adds an external reference to a custom operational record and must distinguish its Dictionary definition from the database state.

  2. SE11 describes the object; SE14 manages its database representation

    Use SE11 to inspect the ABAP Dictionary definition and activation context.

  3. Scope and prerequisite knowledge

    The guide applies to classic ABAP Dictionary tables and the documented Database Utility.

  4. Three layers explain why “the field exists” can be ambiguous

    The Dictionary source contains the maintained design: fields, types, keys and related settings.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.