Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Runtime Analysis for VOFM

abhishek37373
Participant
0 Likes
1,113

Hi Folks,

Can we take a runtime analysis for VOFM routines?Please explain i am new at it.

Thanks in Advance.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
929

1) Create a user variant in SE30 and tick particular units. ( Check the link given below)

2) Set the breakpoint on your routine's first statement and on the last statement.

3) Now run VC01 transaction through SE30.Debugger will stop at the first statement. Change to classic debugger and on the command line put /RON. ( I think for new debugger, it sometimes doesn't work )

4) Press F8. Once it reaches your routines last statement. Put /ROFF in the command line.

5) Now go back and see the analysis in SE30.

Refer the following external link

http://zevolving.com/2009/12/measure-the-performance-between-break-points-using-se30/  ( External )


6 REPLIES 6
Read only

nabheetscn
SAP Champion
SAP Champion
0 Likes
929

Abhishek

Dont know why such a requirement.. If you run SAT for the whole tcode it will show you in detail which part took what time. You will see VOFM routine their...

Nabheet

Read only

0 Likes
929

Hi Nabheet,

The requirement is because i have made a VOFM routine for sales activity (VC01) and the object needs to be checked performance wise.I have ran the transaction se30 for the transaction "VC01" but how do i get the results only the include i created (VOFM Routine)

Read only

0 Likes
929

the result will contain the call of your subroutine..But in case you want to do it only for VOFM routine then in new debugger you can switch on the trace via /RON...Their is a wonderful blog by Olga explaining these tricks

http://scn.sap.com/community/abap/testing-and-troubleshooting/blog/2010/11/10/new-abap-debugger-tips...

Nabheet

Read only

0 Likes
929

Thanks a lot..:)

Read only

Former Member
0 Likes
930

1) Create a user variant in SE30 and tick particular units. ( Check the link given below)

2) Set the breakpoint on your routine's first statement and on the last statement.

3) Now run VC01 transaction through SE30.Debugger will stop at the first statement. Change to classic debugger and on the command line put /RON. ( I think for new debugger, it sometimes doesn't work )

4) Press F8. Once it reaches your routines last statement. Put /ROFF in the command line.

5) Now go back and see the analysis in SE30.

Refer the following external link

http://zevolving.com/2009/12/measure-the-performance-between-break-points-using-se30/  ( External )


Read only

0 Likes
929

Thanks a lot...it worked fine..