RUNTIME ANALYSIS

Functional Overview
The runtime analysis tool allows you to examine the performance of
any transaction, ABAP program, or function module that you create
in the ABAP Workbench. It saves its results in performance data
files, which you can display on the screen. You can use these
results to identify runtime-intensive statements, SQL statements,
and show the hierarchy of program calls. If you want to keep
performance data files for future reference, you can store them
locally on the frontend.
To start the runtime analysis, choose Tools ABAP Workbench,
Test Runtime analysis (or transaction SE30). . On the initial
screen, you can choose one of the four main functions:
From the results of the runtime analysis, you can identify:
Excessive or unnecessary use of modularization units
(subroutines or function modules) and ABAP statements
CPU-intensive program functions
User-specific functions that could be replaced with ABAP
statements
Inefficient or redundant database access.
Initial Screen
Starting the Tool
From the initial screen, you can start the following main
functions:
Tips & Tricks
Setting the measurement restrictions
Start the runtime analysis in the current session
Start the runtime analysis in a parallel session
Display and process performance files
Main Functions
In the simplest case, you would enter a short description
and a measurement object (transaction, program, or
function module) to run the analysis in the current session.
Setting the measurement restrictions:
In the Measurement restrictions group box, you can
make more specific restrictions for the measurement.
For example, you may want to include only certain
statements or time periods.
Main Functions
From the initial screen, you can specify whether the
analysis should run in the same session or in a parallel
session using the Enable/Disable button in the In parallel
session group box.
The Performance file group box contains options for
analyzing performance files.
Analysis
SQL TRACE
Objective
The SQL Trace part of the Performance Trace tool allows you to see
how the OPEN SQL statements that you use in ABAP programs are
converted to standard SQL statements and the parameters with
which the embedded SQL statements are passed to the database
system.
While the trace is switched on, the SQL Trace function records all
database activity by a particular user or group of users. The R/3
System takes OPEN SQL statements and converts them in to
embedded SQL statements that it passes to the database.
The SQL trace tells you:
The SQL statements executed by your program.
The values that the system uses for particular database access and
changes.
How the system converts ABAP Open SQL statements (such as
SELECT) into Standard SQL statements.
Where your application executes COMMITs.
Where your application repeats the same database access.
The database accesses and changes that occur in the update part
of your application.
Screen looks like :
SOURCE CODE INSPECTOR
Overview ..
The Code Inspector tests single objects or object sets (programs,
function groups, classes, interfaces, Dictionary objects) for
performance, security, serviceability, error proneness, and statistical
information.
Object sets, check variants, and inspections are created using
transaction SCI.
Object Sets and Check Variants (that is, combinations of single
checks to which you can assign parameters) are managed
independently of one another. An Inspection connects one check
variant with an object set. Inspections, object sets, and check
variants are created by one user locally or visible to all users
globally
An inspection returns a Check Result, from which you can derive
another object set.
Screen Looks like ..
Name of an
Inspection
Name of an
Object Set
Name of Check
Variant
Important Terms in Source Code Inspection
Element name of inspection :
An inspection consists of an object set (or a single object) and a
check variant. If the inspection is executed, the single checks in the
check variant are carried out on the objects in the object set. The
result is a list of errors, warnings, and information.
Important Terms in Source Code Inspection
Object Set :
An object set consists of one or more single objects. The Single
Objects can be:
-- Program
-- Function group
-- Class
-- Interface or
-- Dictionary object.
Important Terms in Source Code Inspection
Check Variant :
A check variant consists of one or more single checks, some of
which can be assigned parameters.
Code Inspector Results
Thank You