Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | KONV00023 |
| Short Description | Documentation for key figure KONV 00023 |
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 success of condition types used to determine access sequences and accesses. The level of access is shown in the detailed diagram.
The level of access is defined as follows:
The access in an access sequence with the most hits (the most successful access)
Further optimisation steps can be derived from this.
For example, for a changeover in the access order or for using access optimisation, conditions, exclusive access or initial value checks.
Optimisation measures are only be required if a lot of accesses were defined within an access sequence, but the most successful accesses occur at the end of the diagram.
If, for example, before the first successful access a large number of and/or large tables have to be read, which for some reason are not buffered or may not be buffered, a considerable increase in answering times for a particular transaction should be taken int oaccount.
Pricing will be run through for each item and, if need be, for several. And this for all condition types, which were defined in the pricing procedure !
Structure and use of detail displays
The condition types and related access sequences must be sorted in the detail list according to the frequency with which they occur in the KONV table. The number of accesses and the various condition tables are also displayed in the access sequence in accordance with
Customizing.
By selecting a column, representation of the access level can begin as part of the access sequence. The access levels for those condition tables, which were used regularly should be checked and for which a corresponding number of accesses was defined.
Information for optimisation
Table accesses can be optimised using several measures:
Buffering of condition tables, here there are some restrictions such as the size of the table and the frequency of change, which can affect the buffer quality and increase instead of decrease the load on the
database.
Decreasing the size of the tables by reducing the number of lines to a suitable amount for the buffer,
Use of access optimization (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.
There are also several other alternatives which are cheap and relatively easy to implement.
These are already characteristic of a new design or re-engineering, are sometimes unavoidable and normally require a large amount of work and explanation.
Steps such eliminating accesses that have never been or never can be implemented e.g. using accesses to empty condition tables or getting rid of those acccesses 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 or the changeover of the access order as part of the access sequences, in order to shorten processing times up until the first hit are certainly not to be carried out too quickly and require careful work with consideration paid to all of the environmental aspects concerned and all company areas.
Tolerances
It is recommended that you define at least ten (10) accesses in an access sequence. The ten most successful access sequences should be in rows 1-5.
More accesses to a table can require complex processing and lead to unsuitable modelling.
References
See the relevant publications in SAP-TechNet.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
