Hierarchy
⤷ CA-GTF (Application Component) General Application Functions
⤷ BAM (Package) Technical Application Analysis
Basic Data
Data Element | COMB00003 |
Short Description | Documentation for key figure COMB 00003 |
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
Description
This key figure indicates the most important control elements for all procedures used in documents.
It is intended to provide an overview of the complexity in pricing.
Using the key figure for analysis
The detail display shows the number of documents, condition types, group condition types, requirements, access sequences and subtotals for each procedure.
Example :
Pricing procdure ZPROC
Number of documents 4500
Condition types 35
Of which used 15
With access sequence 28
Of which used 3
Manual conditions 10
Group conditions 15
Of which used 1
Statistical conditions 0
Requirements 5
Subtotals formed 5
Interpretation : Pricing procedure ZPROC is used in 4500 documents. It contains 35 condition types, of which 15 are used. Of the 35 condition types, 28 contain an access sequence. We see that about 13 access sequences were processed via conditin tables, but the resulting accesses to condition tables did not result in a valid condition. This may the first sign of a problem. We need to take a closer look at the access sequences.
Also, 15 of the condition types are group condition types of which only one is used. A requirement is entered for 5 condition types. The procedure also contains 5 subtotals and no statistical condition types.
Hints on optimization
Before carrying out any optimization, you should taker a closer look at important elements such as condition types and access sequences.
You can optimize as follows:
Differentiate the procedures, to reduce the number of condition types with access sequences
Use more requirements, so that certain access sequences are not considered in given situations
Differentiate the access sequences to reduce the number of accesses per sequence
Optimization measures such as prestep and table buffering.
Tolerance
Condition types with access sequence < 25
Used group conditions < 4
Number of access sequences used should not be much smaller than the total number of access sequences
Links
See the relevant texts in the SAP-TechNet.
History
Last changed by/on | SAP | 19990223 |
SAP Release Created in |