Hierarchy
PI_BASIS (Software Component) Basis Plug-In⤷
CA (Application Component) Cross-Application Components⤷
PORX (Package) Drag & Relate (Workplace Plugin)
Basic Data
| Data Element | WPKEYTYPE |
| Short Description | Key Type (Alternative Key) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUMC3 | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 | Key type |
| Medium | 15 | Key type |
| Long | 20 | Key type |
| Heading | 12 | Key type |
Documentation
Definition
The key type is used to define keys with the same semantics for an object type with different data elements. A key type is created for each identifying data element.
Key type 1 is the primary key, which defines the key structure (for keys with multiple fields) as well as the technical properties, such as the length and type (more precisely, the domain(s)). This information is read when metadata is created from the Business Object Repository unless key conversion is active for the current object type.
The data type of all other key types and the data element used must correspond to the primary key (exception: NUMC is allowed if the primary key is defined as CHAR). If the lengths differ, a warning is given when the key type is created because key information might be lost when the object URL is generated (if the primary key is shorter).
History
| Last changed by/on | SAP | 20080415 |
| SAP Release Created in |
