Ansicht
Dokumentation

ABENDDIC_DATABASE_TABLES_TECHSTRUC - DDIC DATABASE TABLES TECHSTRUC

RFUMSV00 - Advance Return for Tax on Sales/Purchases   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

- Structure-Dependent Technical Attributes of Database Tables

The following technical attributes are mostly the same as those of a DDIC structure in ABAP Dictionary:

• Table fields (columns)

A table field is a component of the structure of the DDIC database table and describes the name, the data type, and any semantic attributes of a field of a DDIC database table. A table field is a component of the structured data type of the table and the corresponding rules apply to the component name and component type, with the following restrictions:

• The name of a table field cannot be a reserved name. The reserved names that cannot be used are specified in the DDIC database table TRESE. This is also important when using include structures.

• A table field always has one elementary data type. Reference types, substructures, and table types are not possible. The elementary data type is specified directly for the table field or by using a data element and is always based on a built-in type in the ABAP Dictionary. A table field has a platform-dependent type in the physical database table. For each platform, there is a mapping between the elementary types in the ABAP Dictionary and the platform-dependent types. If only is used, this mapping is transparent for ABAP programmers and only the built-in types in the ABAP Dictionary and their ABAP types are relevant for the ABAP program.

• Fields with the type CHAR can have a maximum of 1333 characters.

• Fields with the type LRAW or LCHR must be at the end of the table. Only one such field is allowed per table. Furthermore, a field with the type INT2 or INT4 (for the maximum length of the field) must be located directly in front of this field.

• Fields of the obsolete types DF16_SCL and DF34_SCL must be followed directly by a field of type INT2 for scaling.

• Include structures

DDIC structures, but not DDIC database tables or DDIC views, can be included in a DDIC database table as include structures. A structure can only be included in a table if its components meet the table field prerequisites above. In particular, an included structure cannot contain any substructures. Any naming conflicts must be bypassed by defining suffixes. As in regular structures, the include can be assigned the name of a group.

• When a structure is included, all its fields can be flagged as key fields. The include structure must then be inserted between the existing key fields or directly after them. The corresponding attribute of the individual fields of an included structure does not have an effect. Either all fields are included as key fields or none.

• When an include structure is included, the flag for initial values can be set for the entire include structure. In this case, the fields in the include structure for which this attribute is set also keep their attribute, but it is not switched on for fields where the attribute is not set. If the flag for initial values is not set for the included include structure, this attribute is removed for all its fields.

The fields of an included include structure are still part of the structure. They can only be edited via the structure and any changes made to the structure are affect all including database tables. The fields of an included include structure can also be transformed to direct fields of the DDIC database table that are no longer linked with the originally included structure.

• Enhancement category

The same applies to the enhancement category of DDIC database tables as to the enhancement category of structures.

The following applies with respect to the number of fields and length of the structure of a DDIC database table:

• Number of fields

• A table in the software component SAP_BASIS can contain a maximum of 749 fields.

• A table in a software component other than SAP_BASIS can contain 1000 fields if the storage type is Row Store and 1500 fields if the storage type is Column Store.

• The total of all field lengths is limited. The following applies with respect to the total of the number of bytes of the non-character-like fields and the number of characters of the flat character-like fields:

• In a table in the software component SAP_BASIS, the total cannot be greater than 4030.

• In the ABAP Dictionary, no limit applies to tables in software components other than SAP_BASIS. The limit defined in the current database platform applies (in the SAP HANA database this is 512 KB).

In the case of deep fields such as STRING, RAWSTRING, LRAW, LCHR, and GEOM_EWKB, only the bytes of the references are counted and not the actual content.

Notes

• Nested structures cannot be used to write to DDIC database tables because these structures are not possible in every supported database.

• If it meets the prerequisites above, an existing DDIC structure can be transformed to a DDIC database table. Conversely, a database structure can also be transformed to a regular structure, whereby the database object is deleted.

• The limit on the number of fields and the length of the structure for tables in the software component SAP_BASIS is chosen deliberately so that the requirements of any supported database platform can be met. At SAP, tables can be flagged to allow this limit to be exceeded if enhancements are used. When tables flagged in this way are accessed using , a syntax warning from the extended program check occurs. The warning indicates that a platform-independent replacement implementation may be necessary. The class CL_ABAP_DBFEATURES can be used to identify which limit is supported by a particular database system. The limits applied to tables in other software components for is only defined by the SAP HANA database.

• Renaming of fields that already contain data is not supported. If the name of an existing field is changed in the DDIC database table, an adjustment takes place, where the field with the old name is deleted in the physical database table database and a field with the new name is appended and all data in the column with the old name are lost.

PERFORM Short Reference   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 8866 Date: 20240420 Time: 031216     sap01-206 ( 134 ms )