Application Development 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: 

LIST_TOO_MANY_LPROS ,the maximum permitted number of nested screen levels is restricted to 50.

mahabaleshwar_patil
Participant
0 Kudos

Hello

I have searched many thread for this I did get clear cur idea about ir.

I am getting this dump to many call screen statements in Z module pool program.But with current system can handle only 50 call transaction in sap.

I am calling my Z tcode from LM01 transaction which has 5 screens.

1000 -> 1002-> 103-> 1004

from my first screen 1000 till last screen 1004 is called and after last screen 10404 again main screen 1000 is called.

I am processing these screen continuously 1000->1002->103->1004

again after 1004 -> 1000 main screen is called

so by this way my call screens reach the maximum system capacity i e 50 getting dumps

Can you please suggest me for below my questions

1. where i can see the call screen count in ABAP stack

2. is there any way to clear my ABAP stack / Clear the maximum count i e 50 once I finishg my processing first series of screes
i g 1001->1002>1003>1004>

after 1004 gain 100 is called here is there any possibility clear my ABAP stack or the count ?

3. how to re-set the transaction ?

1 REPLY 1

raymond_giuseppi
Active Contributor
0 Kudos

You must not continue to stack screens but first leave to previous ones, clearing the stack, before re-stacking those.

LOOP in PAI of 1000 - CALL SCREEN -> 1002 - CALL SCREEN -> 1003 - CALL SCREEN -> 1004 - LEAVE TO SCREEN 0 -> 1003 - LEAVE TO SCREEN 0 -> 1002 - LEAVE TO SCREEN 0 -> ENDLOOP in PAI of 1000

To code your PAI logic, remember that the LEAVE TO SCREEN 0 (or SET SCREEN 0, LEAVE SCREEN) will continue at the statement following the CALL SCREEN of current screen.

Regards,
Raymond