From ABAP/4 development workbench select Test – Runtime Analysis.
From ABAP/4 editor, select utilities – more utilities – Runtime Analysis.
From ABAP/ source code screen, select Execute – Runtime Analysis.
From R3 screen, select System – Utilities – Runtime Analysis.
Entering Transaction code SE30 in the command field.
Following screen is the initial screen for SE30 transaction.
On the initial screen, select the needed object you want to analyze i.e. program or transaction. Enter the name of the object. Click on execute. The system will execute the specified object and will generate a trace file or performance data file, which can then be analyzed when the transaction or program is finished.
Analyzing a performance data file
These files are created at operating system level and many times occupy large memory space, so be sure to remove the files, which are no longer needed.
To analyze the files:
Click on Analysis
Following screen is displayed
From GOTO option you can get overview of runtime analysis.
The options are as follows:
Hit List – Displays a list with the most system expensive instructions.
Tables – Displays the most important tables, the number of accesses and the time needed for the accesses.
Group hit list – Displays a list with the performed instructions classified by instruction type.
Call hierarchy – Presents a chronological listing with the flow of calls during the execution of a program.
During Runtime Analysis, the system measures the statements and stores these measurements in a performance data file. If you measure the same program or transaction several times, the data can vary. Many factors make it difficult to reproduce identical result.
E.g., Network traffic.
When you evaluate this file, the system displays the overview - Runtime Analysis Evaluation screen including a bar chart for total execution time. From this screen, you can analyze several types of information like:
Hit list: displays the list with the most `system-expensive’ instructions.
Tables: displays the most important tables, the number of accesses and the time needed for the accesses.
Group hit list: displays a list of performed instruction classified by its type.
Call hierarchy: presents a chronological listing with the flow of calls during the execution of program.
SQL TRACE
The SQL trace is a tool, which allows displaying and analyzing the contents for the database calls, which are made by the reports and transactions written in ABAP/4. It monitors programs and transactions on the database level. With the help of this facility for every open SQL instructions, you can display, about which SQL Embedded (DECLARE, OPEN, FETCH) Statement have been executed, besides analyzing the system performance.
Steps to Creation
From R3 screen, select system –-> Utilities –-> SQL trace. Or Enter transaction ST05.
Click the trace on button.
Enter the user name whose programs are going to be traced.
Execute the program or transaction you want to trace.
Return to SQL trace initial screen and press the button SQL trace off. This switching off is necessary because if it is not done then SQL trace will trace each and every program executed by a particular user. And it is quite expensive in terms of memory and time of the system.
Analyzing The Trace File
To analyze the created trace, press the button list trace. Using this file you can see exactly how the system handles database requests. The first screen of the SQL trace data file displays each measured database requests, the application made. The trace file records when the request occurred and its duration.
To display dictionary definition information about the table field, position the cursor on the table field and click on the DDIC info button. When this button is clicked, it displays system information like object name, table class, whether buffering is allowed or not i.e. information related to dictionary.
Explain SQL: This button provides the functionality, which includes the utility for providing detailed information about the SQL Operation Strategy followed by the underlying database system. You need to click on Explain SQL button. The system displays the execution plan for SQL statements. Here you can display the actual SQL statement like Select, which fields are being accessed, Table being accessed, all where conditions.
ABAP/4 Display Gives you the actual ABAP/4 code.
More information gives the detailed information for time, select statement, client, number of records selected etc. Replace variable will display the SQL statement with another variables.
Workbench Organizer & Transport System
SAP recommends three types of systems for implementation purpose
Development System
Test System
Production System
Though number of systems used by an organization depends upon many factors such as size of implementation, budget etc. However even in the smallest installation, a second system is a must.
Development system
Development system is the system where the actual development takes place. Normally the development is carried out for objects and these objects are original for these systems.
Test system
Also known as quality assurance system and are used to test the objects. You can test objects on development system also, but on Test System the object is tested against real data. When the tests are validated the development objects are transported to the production system.
Production System
The production system is where the end user enters real business data and where the actual business runs. No development takes place in this system. You need to transfer the object from test system to production system.
The overall flow of objects can be understood in the following diagram:
Developer creates the objects in the development system, these objects are transported to the Test system to test them against the real data and when validated, these objects are transported to the Production System.
To transport these objects from one system to another, ABAP/4 development work bench provides the tool called Work bench organizer which is also used to manage activities that are important in the overall development environment.
Example, for these activities are.
The management and control of new development requests.
Modification of objects
Version management
In a distributed environment, workbench Organizer transports the development object between different SAP systems. In the following example, the objects are transported from the development system to production system.
E.g., between development and Production System
Develop System: New Development No development
DEVELOPMEN