Skip to content

ABAP Keyword Documentation →  ABAP - Dictionary 

Classic Objects in ABAP Dictionary

The most important classic objects in ABAP Dictionary are:

ABAP Dictionary can handle the following standalone data types:
  • Data elements

    Elementary data types or reference types with semantic attributes (such as documentation or descriptions). The type attributes of a data element are defined either directly or using a domain.

    A domain describes the attributes of data elements, such as the actual data type or the value range. A domain can be used by any number of data elements, but a data element does not itself need to use a domain. In other repository objects, most specifically ABAP programs, it is not possible to make a direct reference to a domain.
  • Structures

    Complex types that can comprise any other number of data types.
  • Table types

    Complex types that describe internal tables in ABAP. These should not be confused with database tables that describe tables in the database.
The data types in ABAP Dictionary are used in ABAP as reference objects for interface parameters and data objects which can be referenced in common by all repository objects.
A table (not to be confused with a table type) is an object in ABAP Dictionary that designates a database table. As far as its data type is concerned, a database table is a flat structure for which further technical attributes of the database table can be defined alongside the type attributes. The physical database table is created when a table is activated on the database. An ABAP program handles a database table both as a structure and as a database table. This means that the table can be used as a template for structured data objects and also accessed using ABAP SQL .
A view is a grouping of columns in one or more database tables in accordance with an application-specific view. When multiple tables are joined, a view usually implements a join with statically defined join conditions. The columns of a view make a flat structure that can be used as a data type. In ABAP SQL, a view can usually be used as a database table. An exception to this are the special maintenance views and help views.
A lock object is used as a basis for SAP locks. Lock objects specify database tables associated using foreign key relationships and to which a shared lock applies. When a lock object is created, two lock function modules are generated automatically for use in ABAP programs.
A search help uses a combination of structure components, data elements, and check tables plus assigned data to find values without the user needing to enter the exact value in question.

This documentation describes the classic type definitions in ABAP Dictionary and how they interact with the ABAP programming language. Detailed information about lock objects and search helps can be found in the ABAP Dictionary documentation in SAP Help Portal. The following provides an overview of tools for the classic objects in ABAP Dictionary:

Other versions: 7.31 | 7.40 | 7.54


Notes

  • The data types in ABAP Dictionary can only be used by AS ABAP and instances of these types are not created as types of the database system.

  • If existing dictionary objects used to define database tables are changed, it may be necessary to convert these tables. This can be a very lengthy process for tables with a large number of rows. Furthermore, foreign keys in the converted tables can become inconsistent. A where-used list should be created before dictionary objects such as data elements or domains are changed.

  • GUI technologies such as classic dynpros or Web Dynpro are closely integrated with ABAP Dictionary. This applies more specifically to input checks plus field helps and input helps of input fields (see Field Helps, Input Helps, and Dropdown List Boxes). If the data type of an input field is declared using a type from ABAP Dictionary, the documentation of the data elements is used implicitly as the F1 help. Fixed values from domains, check tables (foreign keys), and search helps can all be used for the F4 help. The valid input values can be fixed using the value range of a domain. Any changes to existing dictionary objects that are used directly or indirectly on UIs can, in the worst cases, modify the behavior of the UIs to the extent that they become unusable.

  • Database objects managed by ABAP Dictionary (such as database tables or views defined in the dictionary) should not be accessed directly in the database (see Access to ABAP-Managed Database Objects).

Continue

Data Types

Database Tables

Views

Enhancements

Replacement Objects

Tools for Classic ABAP Dictionary