topic Re: runtime analysis in Application Development and Automation Discussions

runtime analysis

Former Member — Fri, 29 Feb 2008 09:39:25 GMT

How to use runtime analysis ? Any good document..

Re: runtime analysis

Former Member — Fri, 29 Feb 2008 09:42:36 GMT

Hi,

see this link.It will be helpfull.

http://help.sap.com/saphelp_bw30b/helpdata/en/c6/617cafe68c11d2b2ab080009b43351/content.htm

with regards,

sowjanyagosala.

Re: runtime analysis

Former Member — Fri, 29 Feb 2008 09:48:21 GMT

hi,

refer to the links.

http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cafe68c11d2b2ab080009b43351/content.htm

http://help.sap.com/saphelp_bw30b/helpdata/en/c6/617cafe68c11d2b2ab080009b43351/content.htm

SE30 - Runtime Analysis Tool

This runtime analysis tools allows the ABAP/4 programmer to trace the tables used by the SAP dialog/reports programs. In the Analyze button, you can see four more buttons like:-

Hit List

Displays the execution time of each statement in the program.

Tables

Displays the tables accessed during run time.

Group hit list

Displays the execution time of all the statements and grouping them based on the type of command. e.g. performs, SQL and internal tables used.

Hirarchy

Displays the execution time of each statement in the actual order in which were executed. Uses indentation to indicate the level of nesting of statements within subroutines.

Any tables use by the transaction or program can be easily trace with the runtime analysis tools.

Go to transaction SE30

Type in the transaction code you want to analyze

4.6x

In the Restriction section: select the TMP -> Temporary variant

Click the Change button

Click the Duratn/type

Select None for Aggregation

Save the variant and execute again

After finishing the process, click back to SE30

Use F3 to move back to the initial screen of SE30

Click the Analyze Button

Click Goto -> Object-centered hit list -> Database tables

3.0x

Click Execute

After finishing the process, click back to SE30

Click the Analyze Button

Click the Table Button

After retrieving the table names, you can check the raw data with transaction SE16 - Data Browser or SE11 - Dictionary.

For example, if you want to display the data for MSEG - Material Document table

Transaction SE16

Type in MSEG for Table name and click execute.

Data Browser will display the default selection for you to display data. If you did not change the default and click execute the data browser will display the first 500 records.

Click Settings to change the List formats, User parameters and Fields for selection.

In 4.6x, you can use SE16N.

Transaction SE11 or SE12 (4.6x)

Type in MSEG for Object name and click the Display button.

Click Utilities -> Table contents for the default selection screen. If you did not change the default and click execute, the Dictionary will display the first 500 record.

Click Settings to change the List formats, User parameters and Fields for selection.

Transaction SE17

Type in the Table Name, put in the Selection value, put a 'X' in the Output column to display the data field and put in the Sort number from 01..99 (if you want to sort).

regards,

sreelakshmi

Re: runtime analysis

Former Member — Fri, 29 Feb 2008 09:50:39 GMT

It's checks program execution time in microseconds. When you go to se30.if you give desired program name in performance file. It will take you to below screen. You can get how fast is your program.

http://www.sap-basis-abap.com/sapta002.htm

Re: runtime analysis

Former Member — Fri, 29 Feb 2008 10:15:11 GMT

Program SAPBC402_RTAD_RUNTIME = Demonstration Program for Time 11:09:37

User TAW10-12 Date 29.02.08

Execution time in microseconds:

ABAP 0 = 0,0%

Database 0 = 0,0%

System 0 = 0,0%

0% 50% 1 00% 0 = 100,0%

Analysis not complete (wrong record type read).

Message no. S7204

What might be the probable mistake?

Edited by: Amurta Khatua on Feb 29, 2008 11:16 AM

Re: runtime analysis

Former Member — Fri, 29 Feb 2008 10:32:36 GMT

Follow the guideline here SE30

/people/siegfried.boes/blog/2007/11/13/the-abap-runtime-trace-se30--quick-and-easy

Set the measurement restrictions as explained.

Maybe there is something else woring with your program, or with the setting of the

SE30.

Test SE30 simple, just trace a very basic report from Se38, RSPARAM.

Siegfried

Re: runtime analysis

Former Member — Thu, 06 Mar 2008 04:45:30 GMT

some hint was enough.