LIST_TOO_MANY_LPROS

Hi .
 I am getting this error. pls send me solution
Runtime Errors LIST_TOO_MANY_LPROS
Date and Time 22.07.2008 17:43:27
Short text
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 (function Back=F3 or Cancel=F12).
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
At present, the maximum permitted number of nested screen levels is
restricted to 50.
How to correct the error
If possible, unnecessary screens should be suppressed beforehand.
Remember that you can also output a list at the same screen level as
the details list.
In some cases, it is better to create a new screen level stack by
switching to another program or transaction.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"LIST_TOO_MANY_LPROS" " "
"SAPLKKBL" or "LKKBLU01"
"K_KKB_LIST_DISPLAY"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "lenita"
Network address...... "192.168.10.253"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "LENITA"
Database type..... "MSSQL"
Database name..... "PRD"
Database user ID.. "prd"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 23:08:16"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "SQL_Server_8.00 "
Patch level. 52
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 94070160
Heap.... 0
Page.... 2342912
MM Used. 72271600
MM Free. 16561624
User and Transaction
Client.............. 222
User................ "ADMIN"
Language key........ "E"
Transaction......... "SCC3 "
Program............. "SAPLKKBL"
Screen.............. "SAPMSSY0 0120"
Screen line......... 8
Information on where terminated
Termination occurred in the ABAP program "SAPLKKBL" - in "K_KKB_LIST_DISPLAY".
The main program was "RSCCPROT ".
In the source code you have the termination point in line 430
of the (Include) program "LKKBLU01".
Source Code Extract
Line
SourceCde
400
l_sort_state = '2'.
401
call function 'ALV_EXPORT_TO_BUFFER_KKBLO'
402
exporting
403
is_ltdxkey = ls_ltdxkey
404
 I_LANGU = SY-LANGU
405
it_fieldcat_kkblo = gt_stack-it_fieldcat
406
i_fieldcat_kkblo_state = l_fieldcat_state
407
it_sort_kkblo = gt_stack-it_sort
408
i_sort_kkblo_state = l_sort_state
409
it_filter_kkblo = gt_stack-t_filter
410
is_layout_kkblo = gt_stack-is_layout
411
exceptions
412
no_key = 0
413
no_export = 0
414
others = 0.
415
if sy-subrc ne 0.
416
endif.
417
endif.
418
419
*... Export Stack to Memory
420
perform stack_memory_export.
421
422
if i_screen_start_line ne 0.
423
gt_stack-is_layout-i_am_popup = 'X'.
424
endif.
425
426
if gt_stack-is_layout-detail_only is initial.
427
if gt_stack-is_layout-suppress_dynpro is initial.
428
if i_screen_start_line eq 0.
429
call screen 500.
>>>>>
sy-pagno = g_sypagno. "wegen Dynpro 200 Spoolinfo bei F8+Druck
431
else.
432
call screen 501 starting at i_screen_start_column
433
i_screen_start_line
434
ending at i_screen_end_column
435
i_screen_end_line.
436
sy-pagno = g_sypagno.
437
endif.
438
else.
439
if gt_stack-is_layout-interface_complete is initial.
440
perform first_list_display.
441
else.
442
perform list_output_new tables t_outtab
443
gt_dummy.
444
endif.
445
endif.
446
else.
447
gs_selfield-tabindex = 1.
448
gs_selfield-tabname = gt_stack-i_tabname.
449
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
0
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
RUNW_ALV
SY-UCOMM
SY-TITLE
Client Copy/Transport Log Analysis
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080722
SY-UZEIT
174319
SY-XPROG
SAPLSYST
SY-XFORM
SYSTEM_HOOK_OPEN_DATASET
Active Calls/Events
No. Ty. Program Include Line
Name
419 FUNCTION SAPLKKBL LKKBLU01 430
K_KKB_LIST_DISPLAY
418 FUNCTION SAPLSALV LSALVU07 474
REUSE_ALV_LIST_DISPLAY
417 FORM RSCCPROT RSCCPROT_F04_ALV 228
DISPLAY_SHOWLOG_ALV
416 FORM RSCCPROT RSCCPROT_F04_ALV 181
SHOW_LOG
415 FORM RSCCPROT RSCCPROT_UCOMMAND_ALV 141
USER_COMMAND
414 FORM RSCCPROT RSCCPROT_F04_ALV 717
USERCOMMAND
413 FORM SAPLKKBL LKKBLF90 2183
USER_COMMAND_NEW
412 EVENT SAPLKKBL LKKBLF00 12
ATUSER-COMMAND
411 FUNCTION SAPLKKBL LKKBLU01 429
K_KKB_LIST_DISPLAY
410 FUNCTION SAPLSALV LSALVU07 474
REUSE_ALV_LIST_DISPLAY
409 FORM RSCCPROT RSCCPROT_F04_ALV 228
DISPLAY_SHOWLOG_ALV
408 FORM RSCCPROT RSCCPROT_F04_ALV 181
SHOW_LOG
407 FORM RSCCPROT RSCCPROT_UCOMMAND_ALV 141
USER_COMMAND
406 FORM RSCCPROT RSCCPROT_F04_ALV 717
USERCOMMAND
405 FORM SAPLKKBL LKKBLF90 2183
USER_COMMAND_NEW
404 EVENT SAPLKKBL LKKBLF00 12
ATUSER-COMMAND
403 FUNCTION SAPLKKBL LKKBLU01 429
K_KKB_LIST_DISPLAY
402 FUNCTION SAPLSALV LSALVU07 474
REUSE_ALV_LIST_DISPLAY
401 FORM RSCCPROT RSCCPROT_F04_ALV 228
DISPLAY_SHOWLOG_ALV
400 FORM RSCCPROT RSCCPROT_F04_ALV 181
SHOW_LOG
399 FORM RSCCPROT RSCCPROT_UCOMMAND_ALV 141
USER_COMMAND
398 FORM RSCCPROT RSCCPROT_F04_ALV 717
USERCOMMAND
397 FORM SAPLKKBL LKKBLF90 2183
USER_COMMAND_NEW
396 EVENT SAPLKKBL LKKBLF00 12
ATUSER-COMMAND
395 FUNCTION SAPLKKBL LKKBLU01 429
K_KKB_LIST_DISPLAY
394 FUNCTION SAPLSALV LSALVU07 474
REUSE_ALV_LIST_DISPLAY
393 FORM RSCCPROT RSCCPROT_F04_ALV 228
DISPLAY_SHOWLOG_ALV
392 FORM RSCCPROT RSCCPROT_F04_ALV 181
SHOW_LOG
391 FORM RSCCPROT RSCCPROT_UCOMMAND_ALV 141
USER_COMMAND
390 FORM RSCCPROT RSCCPROT_F04_ALV 717
USERCOMMAND
389 FORM SAPLKKBL LKKBLF90 2183
USER_COMMAND_NEW
388 EVENT SAPLKKBL LKKBLF00 12
ATUSER-COMMAND
387 FUNCTION SAPLKKBL LKKBLU01 429
K_KKB_LIST_DISPLAY
386 FUNCTION SAPLSALV LSALVU07 474
REUSE_ALV_LIST_DISPLAY
385 FORM RSCCPROT RSCCPROT_F04_ALV 228
DISPLAY_SHOWLOG_ALV
384 FORM RSCCPROT RSCCPROT_F04_ALV 181
SHOW_LOG
383 FORM RSCCPROT RSCCPROT_UCOMMAND_ALV 141
USER_COMMAND
382 FORM RSCCPROT RSCCPROT_F04_ALV 717
USERCOMMAND
381 FORM SAPLKKBL LKKBLF90 2183
USER_COMMAND_NEW
380 EVENT SAPLKKBL LKKBLF00 12
ATUSER-COMMAND
379 FUNCTION SAPLKKBL LKKBLU01 429
K_KKB_LIST_DISPLAY
378 FUNCTION SAPLSALV LSALVU07 474
REUSE_ALV_LIST_DISPLAY
377 FORM RSCCPROT RSCCPROT_F04_ALV 228
DISPLAY_SHOWLOG_ALV
376 FORM RSCCPROT RSCCPROT_F04_ALV 181
SHOW_LOG
375 FORM RSCCPROT RSCCPROT_UCOMMAND_ALV 141
USER_COMMAND
374 FORM RSCCPROT RSCCPROT_F04_ALV 717
USERCOMMAND
373 FORM SAPLKKBL LKKBLF90 2183
USER_COMMAND_NEW
372 EVENT SAPLKKBL LKKBLF00 12
ATUSER-COMMAND
371 FUNCTION SAPLKKBL LKKBLU01 429
K_KKB_LIST_DISPLAY
370 FUNCTION SAPLSALV LSALVU07 474
REUSE_ALV_LIST_DISPLAY
369 FORM RSCCPROT RSCCPROT_F04_ALV 228
DISPLAY_SHOWLOG_ALV
368 FORM RSCCPROT RSCCPROT_F04_ALV 181
SHOW_LOG
367 FORM RSCCPROT RSCCPROT_UCOMMAND_ALV 141
USER_COMMAND
366 FORM RSCCPROT RSCCPROT_F04_ALV 717
USERCOMMAND
365 FORM SAPLKKBL LKKBLF90 2183
USER_COMMAND_NEW
364 EVENT SAPLKKBL LKKBLF00 12
ATUSER-COMMAND
363 FUNCTION SAPLKKBL LKKBLU01 429
K_KKB_LIST_DISPLAY
362 FUNCTION SAPLSALV LSALVU07 474
REUSE_ALV_LIST_DISPLAY
361 FORM RSCCPROT RSCCPROT_F04_ALV 228
DISPLAY_SHOWLOG_ALV
360 FORM RSCCPROT RSCCPROT_F04_ALV 181
SHOW_LOG
359 FORM RSCCPROT RSCCPROT_UCOMMAND_ALV 141
USER_COMMAND
358 FORM RSCCPROT RSCCPROT_F04_ALV 717
USERCOMMAND
357 FORM SAPLKKBL LKKBLF90 2183
USER_COMMAND_NEW
Chosen variables
Name
Val.
No. 419 Ty. FUNCTION
Name K_KKB_LIST_DISPLAY
GS_SFC25
0000222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GS_MFC72
0000222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GS_SFC23
0000222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-SUBRC
0
0000
0000
%_DUMMY$$
2222
0000
0000
0000
GS_SFC35
0000222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_SCREEN_START_LINE
0
0000
0000
SYST-REPID
SAPLKKBL
5454444422222222222222222222222222222222
310CBB2C00000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
GS_MFC08
0000222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GT_STACK-IS_LAYOUT+4196(2)
2
0
0
0
GT_STACK-IS_LAYOUT+4188(2)
2
0
0
0
G_ULINE
LIST_OUTPUT_NEW1
445554555555445322222222222222
C934FF54054FE57100000000000000
000000000000000000000000000000
000000000000000000000000000000
%_SPACE
2
0
0
0
SY-XFORM
SYSTEM_HOOK_OPEN_DATASET
555544544445454454454545222222
39345DF8FFBFF05EF4141354000000
000000000000000000000000000000
000000000000000000000000000000
GS_SFC29
0000222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_SCREEN_START_COLUMN
0
0000
0000
GS_SFC30
0000222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GS_SFC31
0000222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_SCREEN_END_COLUMN
0
0000
0000
GS_SFC32
0000222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_SCREEN_END_LINE
0
0000
0000
No. 418 Ty. FUNCTION
Name REUSE_ALV_LIST_DISPLAY
IR_SALV_LIST_ADAPTER
F0000000
F0000000
IS_LAYOUT
###X
2000522222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IS_PRINT
### # 000
2222222222222222222222222222222222222222222022200022202222333222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IS_REPREP_ID
22222222222222222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000
IS_SEL_HIDE
200000FF
000000FF
000000FF
000000FF
IS_VARIANT
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IT_EVENTS
Table IT_8980[17x120]
\FUNCTION=REUSE_ALV_LIST_DISPLAY\DATA=IT_EVENTS
Table reference: 1845
TABH+ 0(20) = 18EFD85100000000000000003507000014230000
TABH+ 20(20) = 1100000078000000FFFFFFFF0403010020120000
TABH+ 40( 8) = 10000000C1248401
store = 0x18EFD851
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 1845 (0x35070000)
label = 8980 (0x14230000)
fill = 17 (0x11000000)
leng = 120 (0x78000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000082
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xA8CA8155
pgHook = 0xC0D27154
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 6533 (0x85190000)
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 48 (0x30000000)
lineAlloc = 48 (0x30000000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_EVENT_EXIT
Table[initial]
IT_EXCEPT_QINFO
Table[initial]
IT_EXCLUDING
Table[initial]
IT_FIELDCAT
Table IT_8981[6x1436]
\FUNCTION=REUSE_ALV_LIST_DISPLAY\DATA=IT_FIELDCAT
Table reference: 1796
TABH+ 0(20) = 08F3915600000000000000000407000015230000
TABH+ 20(20) = 060000009C050000FFFFFFFF04030100100D0000
TABH+ 40( 8) = 01000000C1108401
store = 0x08F39156
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 1796 (0x04070000)
label = 8981 (0x15230000)
fill = 6 (0x06000000)
leng = 1436 (0x9C050000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000055
occu = 1 (0x01000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x58ED9156
pgHook = 0x9050F353
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 6532 (0x84190000)
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 11 (0x0B000000)
lineAlloc = 11 (0x0B000000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_FILTER
Table[initial]
IT_SORT
Table[initial]
IT_SPECIAL_GROUPS
Table[initial]
I_BUFFER_ACTIVE
2
0
0
0
I_BYPASSING_BUFFER
2
0
0
0
I_CALLBACK_PF_STATUS_SET
PF_STATUS_LIST
545554555544552222222222222222
06F341453FC9340000000000000000
000000000000000000000000000000
000000000000000000000000000000
I_CALLBACK_PROGRAM
RSCCPROT
5544554522222222222222222222222222222222
233302F400000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
I_CALLBACK_USER_COMMAND
USERCOMMAND
554544444442222222222222222222
53523FDD1E40000000000000000000
000000000000000000000000000000
000000000000000000000000000000
I_DEFAULT
X
5
8
0
0
I_INTERFACE_CHECK
2
0
0
0
I_SAVE
2
0
0
0
I_SCREEN_END_COLUMN
0
0000
0000
I_SCREEN_END_LINE
0
0000
0000
I_SCREEN_START_COLUMN
0
0000
0000
I_SCREEN_START_LINE
0
0000
0000
I_STRUCTURE_NAME
222222222222222222222222222222
000000000000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
I_SUPPRESS_EMPTY_DATA
2
0
0
0
ES_EXIT_CAUSED_BY_USER
222
000
000
000
E_EXIT_CAUSED_BY_CALLER
2222
0000
0000
0000
T_OUTTAB[]
Table IT_1022[20x552]
\PROGRAM=RSCCPROT\DATA=GT_OUTTAB_SHOWLOG
Table reference: 175
TABH+ 0(20) = B04DC95158A2E15100000000AF000000FE030000
TABH+ 20(20) = 1400000028020000FFFFFFFF04000000B0240000
TABH+ 40( 8) = 10000000C1248001
store = 0xB04DC951
ext1 = 0x58A2E151
shmId = 0 (0x00000000)
id = 175 (0xAF000000)
label = 1022 (0xFE030000)
fill = 20 (0x14000000)
leng = 552 (0x28020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000181
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xC845E451
pgHook = 0xB8DF5055
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 873 (0x69030000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 32 (0x20000000)
lineAlloc = 32 (0x20000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0xE04CBD51
>>>>> 2nd level extension part <<<<<
tabhBack = 0x70DEC851
delta_head = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
SLIS_EV_USER_COMMAND
USER_COMMAND
554554444444222222222222222222
5352F3FDD1E4000000000000000000
000000000000000000000000000000
000000000000000000000000000000
L_FORM_FOREIGN_END_OF_PAGE
222222222222222222222222222222
000000000000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
SLIS_EV_CALLER_EXIT_AT_START
CALLER_EXIT
444445545452222222222222222222
31CC52F58940000000000000000000
000000000000000000000000000000
000000000000000000000000000000
L_FORM_FOREIGN_TOP_OF_PAGE
222222222222222222222222222222
000000000000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
SLIS_EV_ITEM_DATA_EXPAND
ITEM_DATA_EXPAND
454454454545544422222222222222
945DF4141F5801E400000000000000
000000000000000000000000000000
000000000000000000000000000000
L_FORM_GROUPLEVEL_CHANGE
222222222222222222222222222222
000000000000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
SLIS_EV_BEFORE_LINE_OUTPUT
BEFORE_LINE_OUTPUT
444454544445455555222222222222
256F25FC9E5FF54054000000000000
000000000000000000000000000000

Dear,
Please lookat the SAP note : 1010036
Please refer this thread,
Runtime Error LIST_TOO_MANY_LPROS
Regards,
R.Brahmankar

Similar Messages

LIST_TOO_MANY_LPROS error for alv list output

Hi All,
we are displaying two lists in one output by using resue_alv_list_output by passing list_append = 'X' to l IS_LAYOUT   parameter.
when we are using like this we are getting the LIST_TOO_MANY_LPROS error.please suggest.
please find the below error.
Runtime Errors         LIST_TOO_MANY_LPROS
Date and Time          08.09.2009 21:06:33
Short text
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 (function Back=F3 or Cancel=F12).
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
At present, the maximum permitted number of nested screen levels is
restricted to 50.
How to correct the error
If possible, unnecessary screens should be suppressed beforehand.
Remember that you can also output a list at the same screen level as
the details list.
In some cases, it is better to create a new screen level stack by
switching to another program or transaction.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"LIST_TOO_MANY_LPROS" " "
"SAPLKKBL" or "LKKBLU01"
"K_KKB_LIST_DISPLAY"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.

Just want to give a hit in relevance to what Sandra suggested. You can set a breakpoint in one of callback subroutine but skip first 49 its calls. This means that only when it is called 50th time, processing will stop at this breakpoint. To do that, in debugger set a breakpoint -> go to Breakpoints tab -> enter 49 in Skip field. You will avoid counting number of calls yourself, system will do that for you.
Regards
Marcin

Getting dump like LIST_TOO_MANY_LPROS

Hi Friends,
I have created a Dialogue program with 6 subscreens with 3 normal screens.
after doing some processing from Subscreen and to navigate to other screens , I am using Call screen.
The leave to screen XXX is throwing error.
If i use call screen statement often , it is throwing error like LIST_TOO_MANY_LPROS.
Can you please help me with different alternate ways to handle this situation.
When calling screens from Subscreens.
Thanks,
Gokul

The specified item was not found.
dump [LIST_TOO_MANY_LPROS|http://sap.ittoolbox.com/groups/technical-functional/sap-dev/dump-list_too_many_lpros-363302]

Runtime Error LIST_TOO_MANY_LPROS

Hi,
I am getting the following runtime error .
Dump:
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).
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
At present, the maximum permitted number of nested screen levels is
restricted to 50.
I have seen the below link
Runtime Error LIST_TOO_MANY_LPROS
and even i am using the SET SCREEN scrno
                                   LEAVE SCREEN stmts
but still i am getting the same error when the stack reaches to count 50.
How can i resolve this issue....?
Thanks,
Sara

Hi Sara,
In case you have screen 100 is your first screen, use LEAVE TO SCREEN 0 instead of CALL SCREEN 100. Hope this can resolve your issue.
Let me know if you still have issues with runtime error?.
Best Regards,
Krishna

Runtime errors in module pool programming

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

Hi
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.
or
- 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

How to refresh an ALV (CL_SALV_TABLE) after a parallel process

Hello all,
I have created a list using CL_SALV_TABLE. When you click on a line, a new mode must be opened. There, the user will fill in some data that must be retrieved and shown in the main list when the user closes the new mode. To do so Iu2019ve used u201CCALL FUNCTION func STARTING NEW TASK task CALLING meth ON END OF TASKu201D statement.
Iu2019ve tried to refresh the list within meth (called on end of task) but it doesn't work. I've also tried to get all the data again, but it prompts a short dump, set a new ok code using method cl_gui_cfw=>set_new_ok_code, even a WAIT until process is finished (not valid because I need process 1 active all the timeu2026)
SAP help says u201CThe SET USER-COMMAND u2018OKCDu2019 statement replaces the REFRESH SCREEN commandu201D
CALL FUNCTION 'function'
 STARTING NEW TASK w_taskname
 PERFORMING end_of_creation ON END OF TASK
 EXPORTING
 i_zzta = ztztl_zzta
 i_manual_order = space
 EXCEPTIONS
 communication_failure = 1 MESSAGE w_msg
 system_failure = 2 MESSAGE w_msg.
[u2026]
FORM end_of_creation USING p_taskname.
 RECEIVE RESULTS FROM FUNCTION 'function'
 IMPORTING
 e_zzta = ztztl_zzta
 EXCEPTIONS
 communication_failure = 1 MESSAGE w_msg
 system_failure = 2 MESSAGE w_msg.
[Modify list]
 SET USER-COMMAND 'OKCD'.
[u2026]
AT USER-COMMAND.
CASE sy-ucomm.
 WHEN 'OKCD'.
 Perform get_data.
How can I have the same behaviour when using CL_SALV_TABLE??
Thanks in advance!

Hello Matt, 
does not work means that if I write the following within method ON END OF TASK, the report is not refreshed.
 
<pre>
o_alv->refresh( ).
</pre> 
I've also tried:
 
<pre>
o_alv->refresh( ).
o_alv->display( ).
data: o_alv TYPE REF TO cl_salv_table</pre> 
<pre>Short dump: RPERF_ILLEGAL_STATEMENT
Error analysis
There is probably an error in the program
 "SAPLSLVC_FULLSCREEN".
 The program was probably called in a conversion exit
 or in a field exit. These are implemented by
 function modules called CONVERSION_EXIT_xxxxx_INPUT/OUTPUT or
 USER_EXIT_xxxxx_INPUT.
 Conversion exits are triggered during screen field transports or
 WRITE statements, field exits during field transports from the
 screen to the ABAP/4 program.
 In this connection, the following ABAP/4 statements are not allowed:
- CALL SCREEN
- CALL DIALOG
- CALL TRANSACTION
- SUBMIT
- MESSAGE W... and MESSAGE I...
 - COMMIT WORK, ROLLBACK WORK
 - COMMUNICATION RECEIVE
 - STOP
- REJECT
- EXIT FROM STEP-LOOP
Moreover, conversion exits for output conversion
 (implemented by function modules called
 CONVERSION_EXIT_xxxxx_OUTPUT) do not allow
- MESSAGE E...
to be used.
Trigger Location of Runtime Error
 Program SAPLSLVC_FULLSCREEN
 Include LSLVC_FULLSCREENU01
 Row 187
 Module type (FUNCTION)
 Module Name REUSE_ALV_GRID_DISPLAY</pre> 
But this short dump is expected since CALL FUNCTION - STARTING NEW TASK help says u201CIn the callback routine, you are not allowed to execute statements that interrupt the program execution or terminate a SAP LUW. Statements for list output are not executed.u201D 
Thanks Matt, I'll take a look at that forum, but I also tried a self list refresh using a timer and that prompted another short dump: LIST_TOO_MANY_LPROS -> "Error analysis: At present, the maximum permitted number of nested screen levels is restricted to 50." 
If I find a solution I'll let you know. 
 
Thank you!!
Edited by: Matt on Aug 26, 2009 1:16 PM

Short dumps

hI
Can any one explain me the key feautres in analyzing short dumps if we get for any ABAP program.
Thanks.
Venkat.

ABAP Dump Analysis (ST22)
All the data saved in SNAP table. & text messages saved in SNAPT.
ABAP Dumps is the default workspace for the Logs and ABAP Dumps navigator group. The ABAP Dumps workspace provides status information for each mySAP ABAP dump generated for the mySAP managed system that you are monitoring. ABAP Dumps is a predefined workspace that contains the following specific information for each dump:
u2022     Program associated with the dump
u2022     Host computer where the dump originated
u2022     User who created the dump
u2022     Date and time the dump was created
u2022     Names of the instances associated with ABAP dumps
u2022     Summary count of dumps by program
u2022     Summary count of dumps by user
You can use the data for specific dumps for the following purposes:
u2022     Identify the number of ABAP dumps generated for a specific mySAP instance
u2022     Identify runtime problems that are occurring on your system
The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system:
Some common dumps : -
1) COMPUTE_INT_TIMES_OVERFLOW
Whole number overflows on multiplication & addition operation.
Always Declare Result field Larger.
per =    ( act / budget ) * 100.
bal =    it_out1-balance + bal .
pr =     it_out1-t_wtext_pr + pr
2) COMPUTE_BCD_OVERFLOW
A value does not fit in a calculation field.
You may need to define the result field to be larger.
1.     Showu2019s error on internal table. (multiplication & addition)
3) Time out
Reason for error:-
After a certain time, the program terminates to free the work process
for other users who are waiting.
2.     The current setting is 1800 seconds.
3.     Primary Index not Used & Sequencing not proper.
4.     Avoid Nested Loops.
5.     Avoid to use select single in loops
6.     Avoid using INTO CORRESPONDING TO
7.     Avoid using SELECT in loops.
8.     SORT the internal table always and use BINARY SEARCH.
9.     for all entries that time check SY-TFILL.
4)     DBIF_RSQL_INVALID_RSQL
The data read during a SELECT access could not be inserted into the
target field.
Check the Sequence of the select Query field & internal table fields.
5)     DBIF_DSQL2_OBJ_UNKNOWN
Because of Database is not properly connected to Level 2 server.
1)     when ur using set Connection command to connect Level 2 server
That time check the value of Sy-subrc = 0 .
6)     SAPSQL_ARRAY_INSERT_DUPREC
Its show the Error when you are going to insert duplicates record in database using
Insert command.
There are three ways to solve this problem.
1     Delete adjacent duplicate.
ii.     Insert ACCEPTING DUPLICATE KEYS
iii.     modify command
7.     CONVT_NO_NUMBER
Solution:-The program attempted to interpret the value "RTGS " as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
1.     put Input Validation using If Query
2.     when programmer try to pass the Char value to num field
3.     or trying to perform Pack or unpack operation on Char. Fields.
8.      CALL_TRANSACTION_NOT_FOUND
Transaction " " is not listed in the table of transaction codes
The current ABAP/4 program uses CALL TRANSACTION to call the Transaction
& Leave to Transaction
Table TSTC (Transactions) contains no entry for the Transaction " ". This could be due to a program error (incorrect transaction code specified).
Ensure that upper/lower case is correct.
1.     Use capital Values because itu2019s case sensitive.
9)     Table_invalid_index.
When you are going to perform Read Insert, update, Delete operation Using index Value & index value = 0. That time it shows this error.
Check the index value is less then or equal to zero.
10)     DATASET_CANT_OPEN
OPEN DATASET / TRANSFER / CLOSE DATASET
Check Sy-subrc = 0.
11     LIST_TOO_MANY_LPROS
At present, the maximum permitted number of nested screen levels is
restricted to 50.
Set by BASIS.
Use leave to transaction u2018Tcodeu2019 to close all Screens at the end of the program.
12     . DBIF_DSQL2_SQL_ERROR
Because of Database is not properly connected to Level 2 server.
1 when ur using set Connection command to connect Level 2 server
That time check the value of Sy-subrc = 0 .

LIST_TOO_MANY_LPROS

Similar Messages

Maybe you are looking for