Get Example source ABAP code based on a different SAP table
VERSION 5 IN
ABAP_DDIC - 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 property, 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 AB_SQL >, only database tables can be accessed that are defined in ABAP Dictionary. 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> properties.
Additional technical properties > of the DDIC database table.
Additional semantic properties> 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 DDIC types> used to define the components of the structure are implemented as database-dependent types. BEGIN_SECTION VERSION 5 OUT The definition of a table in the database can be displayed in transaction SE11>> by choosing Utilities -> Database Object>. END_SECTION VERSION 5 OUT Besides transparent tables, there are also 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. Therefore, the order of the table fields, except for key fields, of existing DDIC database tables can be modified without affecting the corresponding database object. When accessing a DDIC database table using AB_SQL >, the database interface considers potential differences and respects the order defined in ABAP Dictionary. BEGIN_SECTION VERSION 5 OUT When using Native SQL>, the order of the columns in the database system must be considered by the developer. END_SECTION VERSION 5 OUT If AMDP> is used, the results are sorted in the same order as in the ABAP Dictionary (if possible).
Technical properties of database tables>
Semantic properties of database tables>
Global temporary tables> DDIC database tables can be defined with BEGIN_SECTION VERSION 5 OUT form-based tools in transaction SE11>> or with END_SECTION VERSION 5 OUT source-code-based editors using Dictionary DDL> in the ABAP Development Tools>. The following section describes the syntax of the source-code-based definition:
Dictionary DDL for Defining Database Tables > If existing DDIC database tables are modified, adjustments may be necessary.