Ansicht
Dokumentation
ABENDDIC_DATABASE_TABLES - DDIC DATABASE TABLES
Vendor Master (General Section) General Data in Customer MasterThis documentation is copyright by SAP AG.
- Database Tables
The term DDIC database table (or database table or table for short) describes a physical database table in the current standard database in the ABAP Dictionary:
- A DDIC database table is a two-dimensional matrix that consists of rows and columns.
- A field or combination of fields that uniquely identifies every row in a table is known as a table key. This is a minimal attribute, that is, if one of the fields is removed from the key, the remaining fields cannot uniquely identify the table rows.
- A primary key must exist for every table.
- In the relational model, the relationship between objects is expressed by a foreign key.
In , only DDIC database tables can be accessed.
The name of a DDIC database table must follow the naming rules for DDIC database tables.
The definition of a DDIC database table consists of the following:
- A non-nested DDIC structure with its technical and semantic attributes
- Additional technical attributes of the DDIC database table
- Additional semantic attributes of the DDIC database table
The most common table category of a DDIC database table is the transparent table. When the table is activated, the platform-dependent SQL DDL statement CREATE TABLE is used to generate a physical database table with all indexes from its definition in the ABAP Dictionary for those indexes for which this is not excluded explicitly in the definition. This is done in the ABAP database schema in the standard AS ABAP database. The built-in types in the ABAP Dictionary used to define the components of the structure are implemented as database-dependent types. The definition of a table in the database can be displayed in transaction SE11 by choosing Utilities → Database Object. In addition to regular transparent tables, there are also special global temporary tables (GTTs) for storing temporary data within a work step.
The order of the fields in the ABAP Dictionary and on the database does not need to match. More specifically, the order of the table fields, except for key fields, of existing DDIC database tables in the dictionary can be modified without affecting the database object. When using , this is handled accordingly in the database interface and the order in the ABAP Dictionary always applies. When using Native SQL, the order of the columns in the database system must be applied explicitly. If AMDP is used, the results are sorted in the same order as in the ABAP Dictionary (if possible).
DDIC database tables can be defined with form-based tools in transaction SE11 or with source-code-based editors using Dictionary DDL in the ABAP Development Tools. The following section is a summary of the syntax of the source code-based definition:
If existing DDIC database tables are modified, adjustments may be necessary.
Notes
- Customizing includes and append structures can be used to enhance DDIC database tables in the ABAP Dictionary delivered by SAP without making modifications.
- Suitable CDS views can be defined as replacement objects for transparent DDIC database tables. In this case, reads in access the replacement objects rather than the DDIC database tables.
- If existing dictionary objects used to define DDIC database tables are changed, it may be necessary to adjust these tables on the database. This can be very time-consuming 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.
- DDIC database tables managed by the ABAP Dictionary should not be accessed directly in the database (see Access to ABAP-Managed Database Objects).
BAL_S_LOG - Application Log: Log header data PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 7872 Date: 20240426 Time: 123843 sap01-206 ( 92 ms )
