Hierarchy

⤷

⤷

Basic Data
Data Element | WPKEYIDENT |
Short Description | Data Element Identifies Object Type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR1_X | |
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 | Identifies |
Medium | 15 | Identifies |
Long | 20 | Identifies |
Heading | 15 | Identifies |
Documentation
Definition
If the business object key consists of more than one field, one of these fields must be marked as being "identifying". The system creates object links only for this field or the data element behind it.
In the case of simple keys, there is only the identifying data element.
Example: The key of the business object Cost center consists of the fields Controlling area and Cost center. In this case, the field Cost center is flagged as being identifying. The system creates object links for the business object Cost center only for the data element(s) that are assigned to the key field Cost center. The system does not create object links for data elements that are assigned to the key field Controlling area (for example, KORKS), since the controlling area does not identify an object.
However, you could create metadata for the business object Controlling area, where the data element KORKS does identify an object. Then, the system creates object links for the business object Controlling area for this data element or the corresponding screen field.
History
Last changed by/on | SAP | 20080415 |
SAP Release Created in |