Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Module Pool related error

Former Member
0 Likes
462

Hi All,

We have an application where in user interacts with two screens. In the first screen say there are a number of claim numbers. The next screen has claim details for each claim number. For example if the

first screen has more than 55 claims, user has to enter claim details for each claim. For this to happen user has to go to second screen 55 times & has to come back.

The problem we are facing here is when user finishes maintaining details for 50 claims & comes back to maintain the details for the 51st claim the application is going to dump.

The dump says error message 'no further list processing (too_many_lpros)'.

We have written the codes (example below) as below:-

CALL SCREEN 100. ( 100 screen is CLAIM NUMBERS SCREEN)

LEAVE TO SCREEN 200. (200 Screen is CLAIM DETAILS SCREEN).

Kindly suggest a solution.

Regards

Abby

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
433

This is mostly because of the screen stack count increased to the maximum limit. Similar to the the sy-lsind in list reports.I dont know whether the system variable sy-lsind increases in module pool screen, but you can put a breakpoint and have a look at that , just in case its the problem.

Another suggestion is to change the call screen to LEAVE TO SCREEN because leave to screen will not add to the screenstack count.(at least thats what I think )

read the F1 help for call screen and leave to screen and you might get some more information on screen stack count.

Mathews

2 REPLIES 2
Read only

Former Member
0 Likes
434

This is mostly because of the screen stack count increased to the maximum limit. Similar to the the sy-lsind in list reports.I dont know whether the system variable sy-lsind increases in module pool screen, but you can put a breakpoint and have a look at that , just in case its the problem.

Another suggestion is to change the call screen to LEAVE TO SCREEN because leave to screen will not add to the screenstack count.(at least thats what I think )

read the F1 help for call screen and leave to screen and you might get some more information on screen stack count.

Mathews

Read only

Former Member
0 Likes
433

Hi,

There is a limit for the max no of screen sequences. Go through the below link:

[http://help.sap.com/saphelp_47x200/helpdata/en/d3/2e974d35c511d1829f0000e829fbfe/frameset.htm]

Regards,

Sankar