CALL SCREEN nested call

[Former Member]

Hi all

I am getting an error with this dump in my report::

"You requested too many consecutive nested call screens."

I know the reason: I am calling too many screen and I should use LEAVE TO SCREEN instead.

But I cannot do it.

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.

Thanks

Gabriele

[Former Member]

Not sure how you can clear the list of called screen...

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.

Perhaps if you explain why you can't use LEAVE SCREEN we can think in a solution.

Good Luck!

[Former Member]

Not sure how you can clear the list of called screen...

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.

Perhaps if you explain why you can't use LEAVE SCREEN we can think in a solution.

Good Luck!

[RaymondGiuseppi]

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.

Can you explain your

But I cannot do it.

Regards,

Raymond

[Former Member]

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.