<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: CALL SCREEN nested call in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-screen-nested-call/m-p/7624228#M1570538</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not sure how you can clear the list of called screen...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But i've been throught a similar issue in the past, and we changed the process so we could use LEAVE SCREEN. It  was an Online with a lot screens, but we managed to do the trick.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Perhaps if you explain why you can't use LEAVE SCREEN we can think in a solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good Luck!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 11 Feb 2011 13:32:45 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2011-02-11T13:32:45Z</dc:date>
    <item>
      <title>CALL SCREEN nested call</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-screen-nested-call/m-p/7624227#M1570537</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;I am getting an error with this dump in my report::&lt;/P&gt;&lt;P&gt;"You requested too many consecutive nested call screens."&lt;/P&gt;&lt;P&gt;I know the reason: I am calling too many screen and I should use LEAVE TO SCREEN instead.&lt;/P&gt;&lt;P&gt;But I cannot do it.&lt;/P&gt;&lt;P&gt;The question is: I don't need to hold the list of screen visisted, so I would like to know if is it possible to blank somehow the structure that holds this list.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Gabriele&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Feb 2011 11:45:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-screen-nested-call/m-p/7624227#M1570537</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-11T11:45:00Z</dc:date>
    </item>
    <item>
      <title>Re: CALL SCREEN nested call</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-screen-nested-call/m-p/7624228#M1570538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not sure how you can clear the list of called screen...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But i've been throught a similar issue in the past, and we changed the process so we could use LEAVE SCREEN. It  was an Online with a lot screens, but we managed to do the trick.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Perhaps if you explain why you can't use LEAVE SCREEN we can think in a solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good Luck!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Feb 2011 13:32:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-screen-nested-call/m-p/7624228#M1570538</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-11T13:32:45Z</dc:date>
    </item>
    <item>
      <title>Re: CALL SCREEN nested call</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-screen-nested-call/m-p/7624229#M1570539</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can only clear the screen sequence via LEAVE TO SCREEN (0 - deletes last item on stack, nnnn replaces last item with new item) or harder statements like LEAVE TO TRANSACTION.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you explain your&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;But I cannot do it.&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raymond&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Feb 2011 14:04:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-screen-nested-call/m-p/7624229#M1570539</guid>
      <dc:creator>RaymondGiuseppi</dc:creator>
      <dc:date>2011-02-11T14:04:31Z</dc:date>
    </item>
    <item>
      <title>Re: CALL SCREEN nested call</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-screen-nested-call/m-p/7624230#M1570540</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've had this issue a few times with ALV reports. In my case, my program was just displaying a sequence of ALV grids and the users navigated through them using ALV events. I refreshed the grid data instead of creating new grids whenever possible to get around the issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Feb 2011 17:27:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-screen-nested-call/m-p/7624230#M1570540</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-11T17:27:10Z</dc:date>
    </item>
  </channel>
</rss>

