Hierarchy
⤷ BC-TWB-TST-P-GPA (Application Component) Global Performance Analysis (Transaction ST30)
⤷ S_PERF_TRA (Package) New Performance Trace / Statistics with DB Connection
Basic Data
Data Element | HOTRUN |
Short Description | Number of eCATT Main Runs of a Performance Analysis |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DEC4 | |
Data Type | DEC | Counter or amount field with comma and sign |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 5 | |
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 | No.eCATTMR |
Medium | 20 | No. eCATT Main Runs |
Long | 23 | No. of eCATT Main Runs |
Heading | 23 | No. of eCATT Main Runs |
Documentation
Definition
The number of eCATT runs whose performance behavior is analyzed can be specified here (Prerequisite: you have chosen one of the "eCATT Test" pushbuttons). These runs are executed after the eCATT preprocesses. The system averages the performance key figures repeated in the individual eCATT runs over all runs before they are processed in any other way. This only applies to the statistics.
After the specified number of eCATT runs has been executed, a final additional eCATT run is started, which is used only to collect trace data (SQL Trace and so on). This run must be processed independently of the runs for collecting statistical data.
This means: there are always at least two eCATT runs. (Exception: "Number of eCATT Preprocesses = 0 and Number of eCATT Main Runs = 1").
Use
Dependencies
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 640 |