Time Out Error

[Former Member]

Dear Experts

One of the reports throws a time out error after executing. I was told a suggestion to use the function module SAPGUI_PROGRESS_INDICATOR. I added this into my code, and the report started to work fine. But as the data/transactions kept increasing it started throwing time out error again. Any solution to this please advice.

Thanks & Regards

Zamir Parkar

[ThomasZloch]

What you are doing is trying to tame the symptoms, what you should actually do is find the root cause for the long runtime. So please use the readily available analysis tools of the SAP standard as described in

If your program is already tuned to death, then you are just processing a huge amount of data and should run the process in background.

Thomas

[yuri_ziryukin]

Hello Thomas,

sometimes customers are very restrictive with the max runtime of the dialog work process parameter. I saw customers having there 10 minutes or so.

Hello Zamir,

If the report still has to be executed in the dialog mode and the runtime is significantly longer than 10 minutes, you can call the function that you mentioned above several times. Normally it is done in the following way: after the initial data selection the volume is calculated and split into packages. After processing of each package (you can define the package size yourself) a message is sent to the front-end with the mentioned function to inform the end user about the processing status. Thus you avoid time outs and at the same time give the user information how long he should wait.

Regards,

Yuri

[ThomasZloch]

Max runtime is even set to 5 minutes at my current customer. The idea is to keep people from blocking dialog processes with long running reports. I still think it is the wrong approach to artificially extend the allowed max runtime using more or less nasty workarounds (COMMIT WORK also resets the counter, if I remember correctly).

The program code should be investigated for tuning potential, anything that still runs for a long while should run in background, although the follow-on options like Excel-export are not as comfortable with the resulting spool data.

Thomas

[Former Member]

Thank You everyone for the suggestions you provided me. The issue has been resolved. I tried the parallel cursor technique and missed out to do a binary search in one of my internal table.