RunTime Analysis-different values each time

[Former Member]

Hi,

I have a doubt regarding Run Time Analysis(SE30). Here, when I execute the same program by giving the same input several times, I get different values for 'Execution Time' every time. There is a vast difference.

For example, first time I got the values as 56% and 19% for ABAP and Database execution time respectively. Next time, I got 34% and 53% resp. for the same input. How can this be possible?

Please clarify.

Thanks and Regards,

Vidhya.

[Former Member]

Hi Vidhya ,

Bcos while running for second time , it uses buffers , so u cannt depend upon Se30 , better to use ST05.

Regards

Peram

[Former Member]

The SE30 is usually quite o.k., it is a user problem especially if you not experienced.

Try it 3 times in a system where not too many other people are working, open second mode and check the sm50.

After finishing the trace wirte down TOTAL TIME and times for ABAP and DB, NOT THE PERCENTAGES !!!

Post them here, I guess execution number 2 and 3 are quite similar.

Siegfried

[Former Member]

HI

Changing Field Values at Runtime

You can change the values of fields at runtime to see how the change would affect the program flow. Suppose you have found out that a field contains an incorrect value. You would be able to replace it with another value in the Debugger to test whether the program would run properly in that case.

You can change the values of the following data objects of your program. If you enter a value with an incompatible type, the system displays an error message.

• Single fields

• Structured fields

• Strings

• Fields of internal tables

• Fields of classes and interfaces

Procedure

To replace the contents of a single field, proceed as follows:

1. Choose Fields to open the field display mode.

2. Double-click or enter the name of a field in the source code to place it in the field display. The field name and its current value appear in the display.

3. Enter a new value for the field.

4. Choose the pencil icon (Change field contents) at the end of the field display.

With certain data objects such as structures or internal tables, you first have to double-click the appropriate field name to display the attributes. You then have to double-click the individual fields again to open the display mode.

Result

The Debugger writes the new value to the program field and the system records the change in the system log. If you do not click the pencil icon, the changed value is ignored.

The Debugger accepts the values exactly as you entered them. You must, therefore, ensure that you use the correct format (upper and lowercase, left-justified entry for hexadecimal numbers).

[Former Member]

Hi Vidhya..

I agree with Prabhu, this happens because of buffers..the total percentage is always 100%.

so, when u execute for the second time, system will use the buffers, so DB % will go down and to adjust this ABAP will go high..

Try this.. execute once.. note down the percentages.. log off from the SAP logon.. re login and do the same.. u will see the deifference..

Thanks and Best Regards,

Vikas Bittera.

[Former Member]

Try this.. execute once.. note down the percentages.. log off from the SAP logon.. re login and do the same.. u will see the deifference..

why logout ????

Just repeat the measurements several times ...

[Former Member]

Hellow Vidhya,

Whenever your are running the SE30 means your checking the performance of

the program at application server level. It depends upon the services available at that point of time.In other words want to say how your CPU changes every second similarly whenever you are running the program gives different values depend upon the load of the server.

Hope it clarifies your doubt.

Regards,

Ameer Baba.

[Former Member]

Thanks for all your replies.

Regards,

Vidhya.