topic Re: Call Screen Dump in Application Development and Automation Discussions

Call Screen Dump

former_member212001 — Mon, 21 Jun 2010 13:48:24 GMT

Hi ,

I am facing Runtime error LIST_TOO_MANY_LPROS dump saying "No further list processing possible."

SAP only supports 50 consecutive screen calls u201Cso when the limit of 50 is reached itu2019s throwing the error "No further list processing possible"

i checked in old threads they suggested to use leave to screen . but in my code old version already leave to screen was there they changed to call screen.

Also i checked the standard program SAPMP56T, in this functionmodule PTRA_SCREEN_MEM_CLEAR_ALL is used to clear screen memory but thsi also not working for my case.

Also i got from forum to use FM SCREEN_INIT. Nothing is working .

Please help me out from this.

Regards,

Priya.

Re: Call Screen Dump

Former Member — Mon, 21 Jun 2010 14:50:01 GMT

hi,

use sy-lsind = 0. This statement will set the list indicator to zero and all you previous lists be lost. Maximum you can go upto 20 lists.

or try something like this

if sy-lsind GE 19.

sy-lsind = 19.

endif.

Re: Call Screen Dump

Former Member — Mon, 21 Jun 2010 14:56:40 GMT

hi,

use sy-lsind = 0. This statement will set the list indicator to zero and all you previous lists be lost. Maximum you can go upto 20 lists.

or try something like this

if sy-lsind GE 19.

sy-lsind = 19.

endif.

Re: Call Screen Dump

Former Member — Mon, 21 Jun 2010 14:56:40 GMT

hi,

use sy-lsind = 0. This statement will set the list indicator to zero and all you previous lists be lost. Maximum you can go upto 20 lists.

or try something like this

if sy-lsind GE 19.

sy-lsind = 19.

endif.

Re: Call Screen Dump

former_member212001 — Mon, 21 Jun 2010 15:04:39 GMT

Hi phani,

Thanksfor your reply.

I cheked that already for me SY-LSIND is 0 . even though its going to dump.

Any other sugestion please.

Regards,

Priya.

Re: Call Screen Dump

Former Member — Mon, 21 Jun 2010 15:22:50 GMT

Check your dump content for what is set to 50 or greater...I would have guessed the SYST field would be LISTI...

Re: Call Screen Dump

former_member212001 — Mon, 21 Jun 2010 15:36:06 GMT

SY-SUBRC 0

SY-INDEX 0

SY-TABIX 8

SY-DBCNT 0

SY-FDPOS 40

SY-LSIND 0

SY-PAGNO 0

SY-LINNO 1

SY-COLNO 1

SY-PFKEY

SY-UCOMM

SY-TITLE test

SY-MSGTY

SY-MSGID

SY-MSGNO 000

SY-MSGV1

SY-MSGV2

SY-MSGV3

SY-MSGV4

SY-MODNO 2

SY-DATUM 20100621

SY-UZEIT 084021

SY-XPROG

SY-XFORM

SY-LSIND and SY-LISTI are Zero

Re: Call Screen Dump

Former Member — Mon, 21 Jun 2010 17:09:29 GMT

You're right...I made an SALV output I'm working on dump with the same occurrence (50+ REFRESH presses). Looks like it's beyond program control to me...

Internal notes                                                 
    The termination was triggered in function "ab_pushlpro"    
    of the SAP kernel, in line 698 of the module               
     "//bas/701_REL/src/krn/runt/ablist1.c#2".                 
    The internal operation just processed is "BRAX".           
    Internal mode was started at 20100621124729.

Edited by: BreakPoint on Jun 21, 2010 7:09 PM

Re: Call Screen Dump

Former Member — Mon, 21 Jun 2010 19:17:58 GMT

just use the command LEAVE TO SCREEN 'NNNN' instead of call screen or set screen

Re: Call Screen Dump

former_member212001 — Tue, 22 Jun 2010 05:55:19 GMT

Hi Sebasitan,

I checked with leave to screen ' ' in all places instead of call screen in test program its working fine not going to dump.

But i wil check my program since in my requirement program in old version leave to screen ' ' was there they changed to call screen. dono for what functionality they changed.

Thanks a lot for your reply.

Regards,

Priya.

Re: Call Screen Dump

Former Member — Tue, 22 Jun 2010 06:07:55 GMT

Hi,

To return from the detail to the main screen u have used

a 'LEAVE TO SCREEN 100' command (Eg : 100 was the main

screen). It seems that caused the problem - when

replacing it with 'SET SCREEN 0. LEAVE SCREEN.' the

dump doesn't occur any more...

so I guess ur problem will solve.

Regards,

Raj.

Re: Call Screen Dump

former_member212001 — Fri, 02 Jul 2010 05:23:57 GMT

Hi All ,

In test program its working .

But not in original program.

CALL SCREEN 2000.

LEAVE TO SCREEN '2000'.

so now am getting dump like "" Dynpro does not exist "" . if i click on that screen , screen exists. since i used leave to screen after that its not coming to the original screen .

help me ..

Regards,

Priya.

Re: Call Screen Dump

former_member212001 — Thu, 12 Aug 2010 14:27:31 GMT

This message was moderated.