program runtime log

[Former Member]

Hi Experts,

we have one program in PRD is taking more time.

we want to identity the no of records and processing time for each internal table.

can you please guide me how to get the below information ..

after running the program in background

1.processing time for each internal table and database table.

2.no of records in internal table.

Thanks

Sai

[Sandeep_Panghal]

The runtime depends on various factors like data volume in PRD system , hardware used etc...

Check the SQL trace and you may also have a look at the SAT transaction for aggregates.

[Former Member]

Hi Sandeep,

we are using 4.6C .

we don't have SAT t code.

Coming to ST05 we can get only select statement details.

but i need internal table details like no of records and processing time.

Thanks

Sai

[paul_bakker2]

Hello Sai,

Transaction SE30 (ABAP Runtime analysis) is your friend.

You can use it to monitor reads and updates of internal tables, as well as database accesses.

Be sure to set up your own variant (don't use the SAP standard). Choose a large 'Max size of file' (eg 10,000 KB)

and also choose Aggregation = none. On the 'Statements' tab, tick the 'Internal tables' boxes.

This will give you a clear idea of which internal tables are causing problems. Then use the debugger to examine more closely what the actual problems are.

Most READ problems on internal can be solved with a 'binary search' extension.

hope this helps

Paul Bakker

[Former Member]

Hello Paul,

Thanks for your reply.

Here Problem is our program is taking 9 hrs to complete.so we have to run the program in background.

1.Can we measure the Run time analasys using SE30 by running program in background.

if yes please guide me.

2.can you please tell me the steps for max file size setting and aggregation.

we are using 4.6c Version.

Thanks

Sai

[marcin_cholewczuk]

Hello Sai,

In that case run this report in SE30 as was suggested, but on quality system with not so big amount of data. You wll still get results like what part took the most of runtime.

Best regards

Marcin Cholewczuk

[Former Member]

> Be sure to set up your own variant (don't use the SAP standard). Choose a large 'Max size of file' (eg 10,000 KB)

> and also choose Aggregation = none. On the 'Statements' tab, tick the 'Internal tables' boxes.

sorry, the aggregation none is rarely and not in this case. Together with internal table it will create easily an overflow (latest in display, which can not be inpluenced by setting).

4.6c ...

Use aggregation, forget increase 10.000kb (larger ones will hard to handle).

Background .... manually either with debugger or in parallel session and manual activation.

The more convenient solutions come with newer releases.

[Former Member]

Hi,

if the standard tools dont do the job / trick, you always have the option to write your

own log.

Of course this may mean modification of standard SAP coding, but who said, that the

modification needs to be there forever.

If you encapsulate your coding very tightly, you should not have any side effects.

With kind regards

Uwe Gebhardt