Hierarchy
⤷ AP-MD-PRO (Application Component) Central Part of Product Master
⤷ COM_SETTYPE_ATTRIBUTE (Package) Generating Set Types and Attributes
Basic Data
Data Element | COMT_ATTR_TABNAME |
Short Description | Value Table for Attributes |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DBOBJ_NAME | |
Data Type | CHAR | Character String |
Length | 16 | |
Decimal Places | 0 | |
Output Length | 16 | |
Value Table |
Further Characteristics
Search Help: Name | DD_DBTB_16 | |
Search Help: Parameters | TABNAME | |
Parameter ID | DTB | |
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Table |
Medium | 18 | Value Table |
Long | 18 | Value Table |
Heading | 10 | Table |
Documentation
Database table
Tables can be defined independently of the database in the ABAP Dictionary. The fields of the table are defined together with their (database-independent) data types and lengths.
A table definition in the ABAP Dictionary has the following components:
- Table fields: The field names and the data types of the fields contained in the table are defined here.
- Foreign keys: The foreign keys define the relationships between this table and other tables.
- Technical settings: The technical settings define how the table is created on the database.
- Indexes: Indexes can be defined for the table to speed up data selection from the table.
There are three categories of database tables in the ABAP Dictionary.
A physical table definition is created in the database for the table definition stored in the ABAP Dictionary for transparent tables when the table is activated. The table definition is translated from the ABAP Dictionary to a definition of the particular database.
On the other hand, pooled tables and cluster tables are not created in the database. The data of these tables is stored in the corresponding table pool or table cluster. It is not necessary to create indexes and technical settings for pooled and cluster tables.
Supplementary Documentation - COMT_ATTR_TABNAME0001
Use
If you would like to provide a language-dependent description for single values, create a text table for the value table. Besides the language, this text table must contain the same key field as the value table. The foreign key dependency between the value table and text table must be created using this key field.
Dependencies
Example
The example shows a value table with the related text table.
Value table:
Field in T006 Description
MNDT Client
MSEHI Unit of measurement
Related text table:
Field in T006T Description
MNDT Client
MSEHI Unit of measurement
History
Last changed by/on | SAP | 20040312 |
SAP Release Created in | 30A |