SAP ABAP Data Element CAT_ONCE (Control: Execute Test Case Once or Twice)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-TWB-TST-P-GPA (Application Component) Global Performance Analysis (Transaction ST30)
⤷ S_PERF_TRA (Package) New Performance Trace / Statistics with DB Connection
⤷ 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 | CAT_ONCE |
Short Description | Control: Execute Test Case Once or Twice |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
This specifies whether, in the case of an automatic performance analysis, test cases are to be started automatically, and whether they should be started once or twice. If two test cases are started in direct succession, only the second run is evaluated for performance behavior.
Reason: It is highly probable that in the first test case run the buffers (database buffer and program buffer on the currently-used application server) are not yet filled. Significantly, the load times for the buffers may be included with the performance data, which, depending on the case, may not be wanted. Consequently, you can monitor a test case run in which you can assume that the buffers are filled.
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 610 |