topic Re: Runtime errors in module pool programming in Application Development and Automation Discussions

Runtime errors in module pool programming

Former Member — Wed, 05 Nov 2008 04:02:21 GMT

HI all,

I have done a module pool program for invoice tracking level wise.

I am encountering a runtime error, LIST_TOO_MANY_LPROS, while execution ie., for two and more than two updations of the database.

The error analysis says that "At present, the maximum permitted number of nested screen levels is restricted to 50".

Short Text :- "No further list processing possible".

Can anyone please come out with a solution for this problem.

regards

samarendra.

Edited by: samarendra penugonda on Nov 5, 2008 5:03 AM

Re: Runtime errors in module pool programming

Former Member — Wed, 05 Nov 2008 13:13:16 GMT

Hi Samarendra.

Without knowing your code or the programm flow, it seems, that you are using the 'Call screen xxxx' order repeatedly.

If this is so, try to substitute 'Call screen xxxx' with 'Leave to screen xxxx'.

Greetings

Joerg

Re: Runtime errors in module pool programming

Former Member — Wed, 05 Nov 2008 13:19:15 GMT

U should replace the comand CALL SCREEN with LEAVE TO SCREEN.

The command CALL SCREEN create an internal mode to link the calling screen to called screen automatically: in this way when it needs to back to calling screen it doesn't need to specify the screen number but only to use:

- LEAVE TO SCREEN 0.

- SET SCREEN 0. LEAVE SCREEN.

Now if you use LEAVE TO SCREEN, u need to indicate the screen when it needs to back to calling screen:

- Go from 100 to 200

LEAVE TO SCREEN 200. (Instead of CALL SCREEN 200)

- Back to 100.

LEAVE TO SCREEN 100. (Instead of LEAVE TO SCREEN 0)

Max

Re: Runtime errors in module pool programming

Former Member — Wed, 05 Nov 2008 14:50:11 GMT

Hi,

You need to Replace your Call Screen statements with LEAVE SCREEN statements.

Re: Runtime errors in module pool programming

Former Member — Thu, 06 Nov 2008 04:47:49 GMT

hi,

i think you are used CALL SCREEN statement in PBO. Don't do that.