ABAP Program - Urgent

[Former Member]

Hello All,

I was running a program in the debug mode and it goes to a short dump. I looked into the error it says the maximum run time exceeded.

It took something around 20 minutes and showed the error. How can this be prevented.

Madhu.

[Former Member]

Hi Madhu,

Do Runtime analysis(SE30) and SQL trace(ST05) to your report and analyse which statements are consuming more time.

Do optimization to those statements and re run the report.

Runtime analysis tool will display information about:

1) Executed instruction

2) Accessed execution time.

3) Tables and Types of access.

4) Chronological execution flow

SQL trace is a tool which which allows displaying and analyzing the contents for the database calls, which are made by the reports and transactions written in ABAP/4. It monitors programs and transactions on the database level. It generates trace file and analyse the trace file.

Thanks,

Vinay

[SantoshKallem]

max time period for the execution will be set by Basis people.

check the performance.

other alternate is to run background.

reward if useful.

[Former Member]

Thanks for the replies.

Actually this program is in PRD and has been moved to PRD just recently and it did well in QAS. It always runs in the background.

does the time matter if it runs in the background..

Let me know

Madhu.

[RichHeilman]

The problem is that your program runs too long, there is a system setting, that does not allow any program to run after the threshold in a dialog process. Run the program in the background, or you must optimize the program code and make it run in less time. Check ST05 and see if the SELECT statements in your program are running good, if not, fix them.

Regards,

Rich Heilman

[Former Member]

hi Madhu,

check st05,sql trace and find out which statements are taking more time .

Try to reduce the time taken by optimizing the code .Then execut ethe program.

REgards,

keerthi

[Former Member]

Thanks for the replies.

Actually this program is in PRD and has been moved to PRD just recently and it did well in QAS. It always runs in the background.

does the time matter if it runs in the background..

Actually I was just running in the foreground just to see how its doing. But in reality it will tun in the background

Let me know

Madhu.

[RichHeilman]

No, there is not a limit on runtime in background process. At least not in my system. I would imagine that there may be setting for background process too(so that programs don't run for weeks), but I would assume that it would be a very large number. Check with your basis people.

Regards,

RIch Heilman

Message was edited by:

Rich Heilman

[Former Member]

Thanks Rich for the very helpful information.

I ran my Job in background today morining and when i came in i dont see any error message in SM37. It says completed. however i cant check the spool because it dosent have a write statement.

So in SM37 if it says complete so should I assume it Ran.

It send an outbound file to a different place in a different time zone so would take time to here a confirimation fom them ..

Anyways thanks for the help.

Madhu.

[Former Member]

Hi madhu,

1. similar to your case,

2. there are practically / may be practically

programs which will take lot of time,

(even after fine-tuning and optimising)

to execute.

They may take time more than the basis setting.

3. In such cases, for all practical purposes,

its a practice to

run such programs in background, where there is no time limit.

regards,

amit m.

[Former Member]

Thanks Rich for the very helpful information.

I ran my Job in background today morining and when i came in i dont see any error message in SM37. It says completed. however i cant check the spool because it dosent have a write statement.

So in SM37 if it says complete so should I assume it Ran.

It send an outbound file to a different place in a different time zone so would take time to here a confirimation fom them ..

Anyways thanks for the help.

Madhu.

[Former Member]

Can any one answer this...

I ran my Job in background today morining and when i came in i dont see any error message in SM37. It says completed. however i cant check the spool because it dosent have a write statement.

So in SM37 if it says complete so should I assume it Ran.

It send an outbound file to a different place in a different time zone so would take time to here a confirimation fom them ..

Madhu.

[Former Member]

hi,

You are right Madhu, If there is no Write statement we can't verity the spool.

If there is a status Complete on the Job, it means it ran successfully...

Regards,

manju