Skip to Content
0
Former Member
Jul 20, 2007 at 07:31 AM

module pool runtime error---too many consecutive nested call screens.

779 Views

Hi guys,

Attach Dump Analysis generated from system. i'm having this problem after several calls of module pool screen. Appreciate your advise to fix this.

Runtime errors LIST_TOO_MANY_LPROS

Occurred on 07/20/2007 at 00:11:14

-


>> Short dump has not been completely stored. It is too big.

No further list processing possible.

What happened?

-


You requested too many consecutive nested call screens.

-

What can you do?

-


If possible, leave the current screen level before making a further

selection (Back=F3 or Cancel=F12).

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

Error analysis

-


At present, the maximum permitted number of nested screen levels is

restricted to 50.