s_alr_87013611 runnign long time.

[Former Member]

Hi All,

the t-code s_alr_87013611 taking long time. it ran for 30min and later terminated when put abap trace SE30. in analysis graph, for ABAP it took more than 100%. in st03 for t-code S

alr87013611 i noticed cpu time is 3times equalent to DB time.

Please suggest me how to reduce the execution time.

[Former Member · Accepted solution]

Hi,

Troubleshooting steps

1. SM50--- See the status of the dialog work processes.

2. STAD--- Check the last column which shows data taken by tcode in kbs.

3. ST05--- Run the trace to see the performance.

In your case as only one tcode is taking long time and this may be the cause of wrong programming and abap program need to be checked.

Rakesh

[Former Member · Accepted solution]

Hi Rakesh,

Thanks for your reply.

I do feel that it's because of poor coding problem. In SE30(ABAP Trace) for ABAP time taken is very long (more than 95%) and For DB it is very less.

I do not have access to ST05 and STAD/STAT in QAS. once I get access I will run SQL trace. I think no need to run sql trace because , in st03 it is showing cpu time is 3times greater than db time. if CPU time more than obviously there is some problem with ABAP program.

[Former Member · Accepted solution]

if CPU time more than obviously there is some problem with ABAP program.

That is correct, one easy thing you can do, is to debug the running transaction and look for nested loops and large internal tables. Just do severel debugger starts, if you always get the same code section, this is where you need to look closer.

Regards Michael