Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | KONV00022 |
| Short Description | Documentation for key figure KONV 00022 |
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 should give the observer an overview of the condition tables used.
Optimisation measures are particularly required if a large number of tables are used often.
This means that the whole complexity of price relevant dependencies for example 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 reduced form of representation as a rule leads to simplification, acceleration and more comprehensible results.
Information for optimisation
Table accesses can be optimised using several measures:
buffering of condition tables, here some restrictions such as the size of the table and the frequency of change apply, as these can affect the buffer quality and increase instead of decreasing the load on the
database.
reducing the size of the tables by reducing the number of lines to a suitable amount for the buffer,
use of access optimisation (Pre-Step),
use of conditions,
use of exclusive access and
use of initial value checks.
These measures are important steps, which should always take place.
As well as these measures which are cheap and relatively easy to implement, there are several other alternatives.
These are already characteristic of a new design or re-engineering, are partly unavoidable and normally require a relatively large amount of time and project work.
Steps such as the elimination of accesses that have never been or never can be implemented e.g. using accesses to empty condition tables or 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.
The changeover of the access order as part of the access sequences, in order to shorten processing times up until the first hit.
Tolerances
It is generally best to use a maximum of thirty (30) new condition tables.
More tables 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 |
