Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | KONV00001 |
| Short Description | Documentation for key figure KONV 00001 |
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 the key figure for analysis purposes
This key figure shouzld give the observer an overview of the condition types used.
Using the key figure Unused condition types as well you can determine which condition types can be taken out of the pricing procedures.
A condition type is then used, if it is contained at least once in the KONV table for the particular anaylsis stage.
Information for optimisation
In order to determine for example, whether condition types are still required by the specialist departments, they can be manually labeled in the pricing procedure. When a specific period comes to an end without any reaction they can be taken out of the procedure.
If these measures can not be implemented, only those optimisation approaches, concerned with objects in the procedures, e.g. access optimisation and setting conditions remain.
Tolerances
It is generally recommended to use a maximum of thirty (30) 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 |
