Classic Objects in ABAP Dictionary
The most important classic objects in ABAP Dictionary are:
- 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.
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.
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:
7.31 | 7.40 | 7.54
- 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).