Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | KONV00002 |
| Short Description | Documentation for key figure KONV 00002 |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 | 1 |
| Medium | 15 | 1 |
| Long | 20 | 1 |
| Heading | 1 | 1 |
Documentation
Use of key figure for analysis purposes
This key figureshould give the observer an overview of the group conditions used.
Group conditions are to be considered as resource intensive and should only be used when absolutely necessary.
As from 3.0D the processing of group conditions will be triggered by the creation of a new order item or the data release. This is particularly resource intensive for order documents with several order items.
Information for optimisation
You should check whether the condition types should be defined as group condition types. There is also the option to deactivate the group condition processing when creating a new order item or during data release. This is only implemented for example when saving the order.
Tolerances
It is generally a good idea to have a maximum of four (4) group condition types in a procedure.
References
Please note that the relevant publications can be found in SAP-TechNet.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
