Community
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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

CALL SCREEN Dumps

Former Member

‎2009 Apr 17 5:06 PM

0 Likes
820

In a custom application we use CALL SCREEN <dynnr>; it seems though we cannot replace it with LEAVE SCREEN since we have a tree control docked to the left with a list of <objects> and the <objects> get displayed on the right hand side of the dock on double-cliks.

So after 50 double-clicks we hit the dump with TOO_MANY_LPROS error.

Is there anyway to get around the situation? Is there a way to clear the dynpro sequence stack?

Though many posts say LEAVE SCREEN is the only possible option, I have seen SAP program that use CALL SCREEN <dynnr>, but run without dumping. In travel module, tcode TRIP, SAPMP56T '3000' is repeatedly called by CALL SCREEN '3000', but never dumps. And in the program I could not find any process that probably clears the dynpro sequence or similar things.

Can somebody please help?

Thank you,

Fred.

In a custom application we use CALL SCREEN <dynnr>; it seems though we cannot replace it with LEAVE SCREEN since we have a tree control docked to the left with a list of <objects> and the <objects> get displayed on the right hand side of the dock on double-cliks.

So after 50 double-clicks we hit the dump with TOO_MANY_LPROS error.

Is there anyway to get around the situation? Is there a way to clear the dynpro sequence stack?

Though many posts say LEAVE SCREEN is the only possible option, I have seen SAP program that use CALL SCREEN <dynnr>, but run without dumping. In travel module, tcode TRIP, SAPMP56T '3000' is repeatedly called by CALL SCREEN '3000', but never dumps. And in the program I could not find any process that probably clears the dynpro sequence or similar things.

Can somebody please help?

Thank you,

Fred.

Reply
2 REPLIES 2
Read only

Former Member

‎2009 Apr 17 5:16 PM

0 Likes
631

HI,

If you want to use Leave to screen 0 properly then you need to clear the NEXT SCREEN value from the attributes of the screen which you are calling.

Read only

Former Member

‎2009 May 07 7:17 PM

0 Likes
631

Was able to use LEAVE TO and rid of the dumps. But dont know how SAPMP56T uses CALL SCREEN but doesnt ever dump.