Get Example source ABAP code based on a different SAP table
ABAP - Dictionary ( ABAP_DDIC ) ABAP Dictionary is a persistent repository of type definitions (meta data) in the form of dictionary objects>. These dictionary objects are visible in and can be accessed from other repository objects>, particularly ABAP CDS> objects and ABAP programs, as long as this is in line with the package concept. As in the ABAP> programming language, the data types that can be defined in ABAP Dictionary can be elementary, structured, or tabular. Reference types are also possible. The main task of ABAP Dictionary structures is to describe DDIC database tables and DDIC views on the database, while at the same time being visible in all other repository objects and allowing for the definition of type-friendly interface parameters and data objects for handling DDIC database tables and DDIC views. Additionally, ABAP Dictionary manages lock objects and search helps. All ABAP Dictionary objects (definitions) are transportable repository objects. The following ABAP Dictionary objects are available:
Data types> ABAP Dictionary supports the following standalone data types:
Data elements> for elementary data types and reference types.
DDIC structures> that consist of other data types.
DDIC table types> which can have any other DDIC data type except for built-in data types as a line type.
ABAP_NOTE DDIC tables types are not to be confused with DDIC database tables that describe tables on the database. The data types in the ABAP Dictionary serve as reference objects for interface parameters and data objects within AS ABAP. Other repository objects can refer directly to the data types in the ABAP Dictionary.
DDIC database tables> A DDIC database table (not to be confused with a table type) is an object in the ABAP Dictionary that describes a database table. Regarding the data type, a DDIC database table is a non-nested structure in which further technical properties of the DDIC database table can be defined alongside the type properties. The physical database table on the database is created when a DDIC database table is activated. In an ABAP program, a DDIC database table is handled both as a DDIC structure and as a database table. This means that a DDIC database table can be used for typing structured data objects and it can also be accessed using AB_SQL >. BEGIN_SECTION VERSION 5 OUT
DDIC views> A DDIC view defines an application-specific view. It includes columns of one or multiple DDIC database tables. When combining multiple tables, a view usually implements a join with statically defined join conditions. The columns of a view represent a non-nested structure that can be used as a data type. The following types of DDIC views are available:
DDIC table views> for views on database tables in the ABAP Dictionary.
DDIC external views> (obsolete) for views on SAP HANA views>. In AB_SQL , a DDIC view can usually be accessed like a DDIC database table. An exception to this are DDIC maintenance views> and DDIC help views >. END_SECTION VERSION 5 OUT BEGIN_SECTION VERSION 5 OUT
Extensibility> ABAP Dictionary supports extensions of DDIC structures>, DDIC database tables >, DDIC database views>, and domains>. These extensions do not modify the original object.
Replacement objects> DDIC database tables> and DDIC database views> can be assigned a CDS view> as replacement object. In certain access scenarios, the access is then redirected to the replacement object instead of the original object. END_SECTION VERSION 5 OUT
DDIC tuning objects> HANA 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:
A set of built-in ABAP Dictionary data types>, which are the basis for the elementary components of all ABAP Dictionary objects. ABAP CDS> is also based on these elementary data types.
ABAP Dictionary provides a set of built-in database functions> that can be used in ABAP CDS> and/or in AB_SQL >. For common usage in ABAP Dictionary objects, ABAP CDS, and ABAP programs, there is a set of
predefined types> The DDIC types, DDIC database tables, BEGIN_SECTION VERSION 5 OUT and DDIC views END_SECTION VERSION 5 OUT can be used as global data types in ABAP programs. Dictionary objects must be activated before they can be used, just like ABAP programs. 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.
Activating ABAP Dictionary Types> BEGIN_SECTION VERSION 5 OUT For an overview of the tools for dictionary objects, see the following:
Tools for Dictionary Objects> END_SECTION VERSION 5 OUT
Latest notes: NON_V5_HINTS
GUI technologies such as classic dynpros> or Web Dynpro> are closely linked with ABAP Dictionary. This applies especially 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. All valid input values of a field can be provided by means of 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, should not be accessed directly on the database (see Access to ABAP-Managed Database Objects>).
Further dictionary objects are:
Lock objects>
Lock objects serve as a basis for SAP locks >. Lock objects specify DDIC database tables linked by means of foreign key relationships to which a shared lock is to be applied. When a lock object is created, two lock function modules> for use in ABAP programs are generated automatically.
Search helps>
A search help can search for values using a combination of structure components, data elements, and check tables to browse through assigned data. The user does not need to know the exact spelling of a value. This documentation describes the 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 on SAP Help Portal. ABAP_HINT_END