SAP ABAP Data Element RUNWSCI_STAT (With or Without Static Program Analysis)
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 | RUNWSCI_STAT |
Short Description | With or Without Static Program Analysis |
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 | 10 | Stat.Anal. |
Medium | 18 | Stat.Prog.Analysis |
Long | 24 | Static Program Analysis |
Heading | 24 | Static Program Analysis |
Documentation
Definition
This determines whether the performance checks of the Code Inspector (see transaction SCI) are used with the programs automatically executed during a performance test (eCATT). These programs are not usually explicitly known to the user of an eCATT. The list of program objects to be analyzed is therefore currently automatically determined from the SQL trace.
The point of this function is to identify inefficient database accesses that are contained statically in the coding.
You can only activate the static program analysis, if you also select "With run for SQL trace", since otherwise there is no SQL trace available to determine the programs.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 700 |