Hierarchy

⤷

⤷

Basic Data
Data Element | DIP2514 |
Short Description | View 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 | View type |
Medium | 15 | View type |
Long | 18 | View type |
Heading | 2 | VT |
Documentation
Definition
The view type defines how a view is implemented and how one can access the view.
Six different view types are supported at the moment:
Database view (type D): implemented with an equivalent view on the database.
Projection view (type P): used to mask out fields from a table.
Help views (type H): used in the online help system.
Structure view (type S): used to generate a structure from the view fields. The creation of structure views is no longer supported as of Release 3.0.
Maintenance view (type C): permits a business view on data and enables maintenance of this data.
Entity view (type E): used to map entity types of the EDM to tables of the ABAP Dictionary. This view type is no longer supported as of Release 3.0.
Use
Procedure
Please observe the following input conventions:
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 *.
Examples
Dependencies
History
Last changed by/on | SAP | 19970314 |
SAP Release Created in |