Hierarchy
⤷ BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
⤷ SDIC (Package) ABAP Dictionary
Basic Data
Data Element | DIP0203 |
Short Description | Table type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SELPAR | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
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 type |
Medium | 20 | Table type |
Long | 20 | Table type |
Heading | 30 | Table type |
Documentation
Definition
The table category defines whether a physical table exists for the logical table description defined in the ABAP Dictionary and how the table is stored on the database.
The following table types exist:
Transparent Tables
There is a physical table on the database for each transparent table. The names of the physical table and the logical table definition in the ABAP/4 Dictionary agree. All the business and application data is stored in transparent tables.
Structure
No data records exist on the database for a structure. Structures are used for the interface definition between programs or between screens and programs.
Append Structure
An Append structure defines a subset of fields which belong to another table or structure but which are treated as a separate object in the correction management.
Append structures are used to support modifications.
The following table types are used for internal purposes, for example to store control data or for continuous texts:
Pooled table
Pooled tables can be used to store control data (e.g. screen sequences, program parameters or temporary data). Several pooled tables can be combined to form a table pool. The table pool corresponds to a physical table on the database in which all the records of the allocated pooled tables are stored.
Cluster table
Cluster tables contain continuous text, for example documentation. Several cluster tables can be combined to form a table cluster. Several logical lines of different tables are combined to form a physical record in this table category. This permits object-by-object storage or object-by-object access. In order to combine tables in clusters, at least part of the keys must agree. Several cluster tables are stored in one corresponding table on the database.
Generated view structure
A structure is generated for a view during activation. This structure is used as the interface for the runtime environment. It is not usually displayed in the ABAP Dictionary.
Please note the following input conventions when using character strings in a search.
char
All characters (apart from those mentioned below) stand for themselves, with no distinction made between upper and lower case. Upper and lower case are distinguished in text fields, such as short descriptions.
*
denotes any character string.
+
denotes exactly one character.
<>
denotes negation (applies if the specified character string does not match).
$
tests for a blank field (entering <>$ means that the system searches for all fields containing at least one character).
>
greater than.
<
less than.
&
logical AND (intersection), followed by the next character string without blanks.
or/
logical OR (union), followed by the next character string without blanks.
Priority starts at the top, i.e. & is evaluated before , but after *.
History
Last changed by/on | SAP | 19970314 |
SAP Release Created in |