Ansicht
Dokumentation

ABENABAP_DICTIONARY - ABAP DICTIONARY

ABENABAP_DICTIONARY - ABAP DICTIONARY

Vendor Master (General Section)   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

ABAP - Dictionary ()

ABAP Dictionary is a persistent repository of type definitions (meta data) in the form of dictionary objects visible in all repository objects, particularly in ABAP CDS objects and in ABAP programs, and usable as part of the package concept. As in the ABAP programming language, the definable data types in the ABAP Dictionary can be elementary, structured, or tabular. Reference types are also possible. The structures of the ABAP Dictionary have the important task of describing DDIC database tables and DDIC views in the database, while also being visible in all other repository objects. This makes it possible to define type-friendly interface parameters and data objects for handling DDIC database tables and DDIC views. In addition to the data types, lock objects and search helps, among other things, are also managed in the ABAP Dictionary. All objects (definitions) in the ABAP Dictionary are themselves transportable repository objects.

The main objects in the ABAP Dictionary are as follows:

ABAP Dictionary supports the following standalone data types:

  • DDIC table types with any line type (not to be confused with DDIC database tables that describe the tables on the database).

The data types in the ABAP Dictionary are used within AS ABAP as reference objects for interface parameters and data objects. All repository objects working with these can refer directly to the data types in the ABAP Dictionary
A DDIC database table (not to be confused with a table type) is an object in the ABAP Dictionary that describes a database table. According to its data type, a DDIC database table is a non-nested structure in which further technical attributes of the DDIC database table can be defined alongside the type attributes. The physical database table on the database is created when a DDIC database table is activated. An ABAP program handles a DDIC database table both as a DDIC structure and as a database table. This means that the DDIC database table can be used as a template for structured data objects and also accessed using .
A DDIC view is a grouping of columns in one or more DDIC database tables as 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 non-nested structure that can be used as a data type. ABAP Dictionary supports the following DDIC views:

In , a DDIC view can usually be used like a DDIC database table. An exception to this are the special DDIC maintenance views and DDIC help views.
ABAP Dictionary makes it possible to enhance DDIC structures, DDIC database tables, DDIC database views, or domains, without making modifications.
DDIC database tables and DDIC database views in the ABAP Dictionary can be assigned to CDS views as replacement objects, which are then used as replacement objects in certain accesses.
DDIC tuning objects can be created for DDIC objects to define technical settings and tunings that can be transported separately.

ABAP Dictionary has the following built-in data types and functions:

For common usage in ABAP Dictionary objects, ABAP CDS and ABAP programs, there is a set of

The DDIC types, DDIC database tables, and DDIC views can be used as global data types in ABAP programs. Like ABAP programs, dictionary objects must be activated before they can be used. Once activated, new or modified definitions are available directly for all other repository objects. If an existing dictionary object is changed, the repository objects that use it continue to work with the previous active version until the modified dictionary object is activated successfully. A dictionary object can only be deleted once all objects that use it have been removed.

For an overview of the tools for dictionary objects, see the following:

Notes

  • Further dictionary objects are as follows:

A lock object is used as a basis for SAP locks. Lock objects specify DDIC database tables linked using foreign key relationships and to which a shared lock is to be applied. When a lock object is created, two lock function modules are generated automatically for use in ABAP programs.

A search help can search for values using a combination of structure components, data elements, and check tables using assigned data without needing to know the exact spelling of a value.
This documentation describes the type definitions in the 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 the SAP Help Portal.
  • GUI technologies such as classic dynpros or Web Dynpro are closely linked with ABAP Dictionary. This applies more specifically to input checks as well as 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 the 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 can no longer be executed.
  • Database objects managed by the ABAP Dictionary, such as DDIC database tables or DDIC views defined in the dictionary, should not be accessed directly in the database (see Access to ABAP-Managed Database Objects).





CL_GUI_FRONTEND_SERVICES - Frontend Services   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 11252 Date: 20240329 Time: 025905     sap01-206 ( 203 ms )