topic Re: add error message in Sapgui_progress_indicator in Application Development and Automation Discussions

add error message in Sapgui_progress_indicator

Former Member — Thu, 24 Aug 2017 17:57:36 GMT

hi, abap newbie here

I am trying to add a error message (something like 'max # of records exceeded) to a report if the data output exceeds 300,000 lines as this will result in an abap dump timeout. I was trying to leverage form Sapgui_progress_indicator for this but I must be doing something wrong.

any input is appreciated.

thanks

Re: add error message in Sapgui_progress_indicator

SimoneMilesi — Thu, 24 Aug 2017 18:06:36 GMT

Why do you think SAPGUI_PROGRESS_INDICATOR can help you?

What's wrong with a classical Message + STOP statement?

Re: add error message in Sapgui_progress_indicator

Former Member — Thu, 24 Aug 2017 18:12:11 GMT

did not think of that - where do you put the stop?

Re: add error message in Sapgui_progress_indicator

SimoneMilesi — Thu, 24 Aug 2017 20:15:47 GMT

it depends by how the report is built.

If you have all the records in an internal table, you can check the row numbers with DESCRIBE TABLE statement before processing it and then choose to stop.

It's up to you to choose the best behaviour.

Anyway, are you sure you cannot "shrink" the performances to allow the report to handle more records?

Re: add error message in Sapgui_progress_indicator

Sandra_Rossi — Fri, 25 Aug 2017 06:32:03 GMT

If you run a program in foreground, and it takes too much time, then there must be a timeout.

You shouldn't try to bypass this mechanism, or the performance of the whole system may decrease.

Instead, when it happens, the users should run the report in background (and they'll learn to always run it in background in the future).

For more information about the timeout, refer to the SAP note 25528 (Parameter rdisp/max_wprun_time https://launchpad.support.sap.com/#/notes/25528/E

Note that the SAPGUI_PROGRESS_INDICATOR function module does not reset the "timeout counter" (you can see this counter in transactions SM50/SM66).