Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD⤷
SDIC (Package) ABAP Dictionary
Basic Data
| Data Element | CLASSVIEW |
| Short Description | Object class views |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DYNPCHOICE | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Views |
| Medium | 18 | Views |
| Long | 18 | Views |
| Heading | 0 |
Documentation
Definition
Views
General Concept:
In the language of relational databases, a view is a virtual table, that is, a table that is not actually physically stored, instead being derived from one or more other tables.
In the simplest case, this derivation process can involve simply suppressing the display of one or more fields from a base table (Projection) or transferring only certain records from a base table to the view (Selection). More complicated views can be assembled from several base tables, with individual tables being linked using the relational Join operation.
The way views are defined in relational database systems, it is possible to use any desired combination of the three fundamental operations - projection, selection, and join - with the single constraint being that only views derived from a single base table, i.e. without applying the join operation, may be relationally operated on in turn.
SAP view concept:
The SAP view concept is based on the fundamental relational operations, which are projection, selection, and join.
However, whereas in strictly relational systems links between different tables must be dynamically forged using join operations, the SAP data model with its foreign key concept offers the possibility of statically defining semantic foreign keys between tables in the ABAP Dictionary.
In order to ensure that only semantically meaningful views will be generated, the view definition used only permits tables to be joined that are already linked by appropriate foreign keys in the ABAP Dictionary.
This definition of views allows logical cross-sections of data to be generated in response to the needs of specific applications, so that the required data can be directly and efficiently accessed.
The following view types are supported:
Supplementary Documentation - CLASSVIEW 0001
Use
You can maintain the assignment of views to view maintenance authorization groups.
This allows you to restrict authorization for table maintenance of individual views to a specific group of users/developers.
Procedure
- Mark with a cross, select object from the menu or press PF2.
- Generic entry of the object name and/or authorization group.
- Select PF key maintenance.
- Enter the authorization group in the relevant field.
- Save and press PF3 Back.
- Check authorization by carrying out a maintenance test.
Dependencies
You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.
You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.
Examples
History
| Last changed by/on | SAP | 19950209 |
| SAP Release Created in |
