SAP ABAP Data Element RUNWSCI (With or Without SQL - Trace 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

Basic Data

Data Element	RUNWSCI
Short Description	With or Without SQL - Trace 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	SQL Anal.
Medium	18	SQL Analysis
Long	18	SQL Trace Analysis
Heading	18	SQL Trace Analysis

Documentation

Definition

This determines whether performance checks of the Code Inspector (see transaction SCI)are used with the SQL trace generated during a performance test (such as an eCATT run).

The point of this function is to identify inefficient database accesses that may arise from SQL statements dynamically formulated in the program to be checked. Program code parts of this type therefore only become known at the runtime of the program. The Code Inspectcor cannot therefore statically check them using the program code. The execution of these database accesses (SQL) can be traced using the SQL trace. The Code Inspector therefore analyzes the SQL trace here. This means, of course, that SQL statements that are explicitly forumlated in the program code are also taken into account.

It is only possible to activate the SQL trace analysis, if "With run for SQL trace" was also chosen, since otherwise there is no SQL trace available to be analyzed.

Use

Dependencies

Example

History

Last changed by/on	SAP	20110908
SAP Release Created in	700