Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD⤷
SDVI (Package) ABAP/4 Dictionary: Views, Lock Objects
Basic Data
| Data Element | DCVIFD0007 |
| Short Description | Test: Are required fields in view key? |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DD_CHECK | |
| Data Type | CHAR | Character String |
| Length | 6 | |
| Decimal Places | 0 | |
| Output Length | 6 | |
| 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 | Req.Flds |
| Medium | 15 | Req. fields |
| Long | 20 | Required fields |
| Heading | 6 | ReqFld |
Documentation
Definition
The set of required fields of a view is a certain subset of the set of all key fields of all the base tables of the view. It is defined as small as possible with the attribute that there may be at most one entry in each of the base tables when defining the required fields.
There is a check whether the set of required fields of the view to be activated is contained in the set of key fields of the view. More precisely, the following two steps are executed:
1. The required fields are determined: All the key fields of the primary table are first made to required fields. The set of required fields is then enlarged step by step. All the joins of the view are scanned successively. Two cases must be distinguished here:
a) The predecessor table (when making this join) is the foreign key table of the foreign key relationship implementing this join. Only the key fields of the successosr table referenced partially in this foreign key relationship are then required.
b) The predecessor table is the check table of the foreign key relationship implementing the join. All the key fields of the successor table which are not foreign key fields of this foreign key relationship are then required.
2. Test if there are required fields in the key of the view: Two fields of two base tables of the view are called equivalent if the foreign key relationships which implement the joins used to build the view ensure that the same entry is in both fields. There is now a check if there is an equivalent field in the key of the view for each required field of the view to be activated.
History
| Last changed by/on | SAP | 19950209 |
| SAP Release Created in |
