SAP ABAP Data Element SE30L3AGG1 (RT Analy. Measurement Type: Fully Aggregated (Kernel: agg=2))
Hierarchy
SAP_BASIS (Software Component) SAP Basis Component
   BC-DWB-TOO-RTA (Application Component) Runtime Analysis
     STRA (Package) Runtime Analysis
Basic Data
Data Element SE30L3AGG1
Short Description RT Analy. Measurement Type: Fully Aggregated (Kernel: agg=2)  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type FLAG    
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 Fully-ag. 
Medium 15 Fully-aggregatd 
Long 20 Fully-aggregated 
Heading 15 Fully-aggregatd 
Documentation

Definition

The option "fully aggregated" is obsolete. Varients for which "full aggregation" is configured can continue to be used for runtime measurements. They can no longer be edited however.

Instead of using the option "fully aggregated", you should use the option Aggregation per call positiion.

Using aggregation, measurement data of the same type (for example all calls of a specific method or all SELECT calls to the same table) is grouped together and recorded as one single entry. For complex applications the following procedure is recommended:

  • Execute an sggregation per call positiion first.
    The result is a hit list of the aggregated entries. You can then remove the most runtime intensive program parts from this overview and analyze them in detail.
  • Execute a further, non-aggregated measurement.
    This measurement is made using a measurement restriction variant, which contains the program parts that prove to be runtime intensive during the aggregated measurement. The result is a detailed analysis with all the hit lists and the call hierarchy.

History
Last changed by/on SAP  20130604 
SAP Release Created in