Hierarchy
⤷ LO-ADM (Application Component) Additionals Management
⤷ WTAD (Package) IS-R: Additionals
Basic Data
Data Element | ADDI_WTKEY |
Short Description | Key for transaction data for additionals |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ADDI_WTKEY | |
Data Type | NUMC | Character string with only digits |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ADDI_KEY | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Key |
Medium | 15 | Key |
Long | 20 | Key |
Heading | 9 | Key |
Documentation
Definition
Dummy key (assigned internally by the system) for three fields:
- Unit of measure of the material to which additionals are assigned,
- The internal class number, and
- The additional itself.
By using this key, you avoid making changes to the real key, which could necessitate a conversion, depending on the database system you use.
From the user's viewpoint, the internal class number is replaced here online by the combination of class type and class, which means that in fact there must be four distinct fields available for input: sales unit, additional, class type and class.
This key is created for technical reasons. If one of the fields which make up the primary key changes, all that this entails is a change in the relevant program routine for assigning the key. Database conversion is avoided entirely.
Use
This field is only used by the system (internally).
The field LFDNR is used in the order form. In the order IDoc (as of basis type ORDERS04) the key is stored in segment E1EDP01 in the POSEX field.
When an additionals IDoc is requested via a BAPI, the additional is identifed by this key.
History
Last changed by/on | SAP | 19980423 |
SAP Release Created in |