Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | KONV00021 |
| Short Description | Documentation for key figure KONV 00021 |
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 figure should give the observer an overview of the access sequences used.
Optimisation measures are particularly required, if access sequences are often used and contain lots of accesses to tables.
This means that the whole complexity of price relevant dependencies such as customers, and their groupings, products, agreements and markets as well as organizational dependencies within these access sequences must be shown, in order that daily operations can function effectively.
The maintenance of complex models together with their non-trivial simulation of the expected results requires a great deal of personal resources and careful work in accordance with experience. Every type of reduced representation as a rule leads to simplification, acceleration and more comprehensible results.
Information for optimisation
Access sequences can be optimised using several measures:
getting rid of those accesses not required by componentization of the assignation between the access sequence and the condition type, in particular for condition types and their access sequences which are not
used or only seldomly used.
elimination of accesses that have never been or can never be implemented e.g. using accesses to empty condition tables,
break-down into several smaller access sequences with corresponding assignation if need be to new condition types.
These measures are important steps, which should always take place.
If these measures cannot be implemented, there remains only the optimisation approaches which refer to objects within the access sequences, such as for example access optimisation (Prestep), the setting of conditions, exclusive access and initial value checks.
Tolerances
It is generally best to use a maximum of ten (10) tables in an access sequence.
A more ambitious approach is to have an amount or a value with a maximum of five accesses.
Larger access sequences on the one hand lead to complex processing or on the other to unsuitable modelling.
References
For more information see the relevant publications in SAP-TechNet.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
