Application Development 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
Showing results for 
Search instead for 
Did you mean: 

screen redirect.

Former Member
0 Kudos

hi guys,

i am using report, in the i have 2 screen, 100 and 200. its a table maintenance. suppose if i am deleting the record in scr 200, it will ask the confirmation whether to delete or not, if i delete the record automatically it should come to sel scr, but it is coming to scr 100.

i am using leave to screen 0.

i also tried in giving leave to screen 100, it working but after some time i am getting some error pop up.(call selection screen should be called using call sel scr)

i also tried in calling call sel-screen '1000'.

still i am getting the error.

can anyone help me in this.....

3 REPLIES 3

Former Member
0 Kudos

After reading your post, I have a doubt regarding the term "Table Maintenance".

Table Maintenance :

a) Have you generated table maintenance using SE11 ?

b) Have you created your own screens and your own table control in those screens ?

It can be either <b>(a)</b> or <b>(b)</b>.

Regards,

Subramanian V.

0 Kudos

Have you tried......

Set screen 100.

Leave screen.

Regards,

Rich Heilman

Former Member
0 Kudos

This may be a common problem if you are new to screen processing. From screen 100 are you doing a CALL SCREEN 200? If so then you are starting a new screen processing session and when you SET SCREEN 0 and LEAVE SCREEN from 200, you are ending the CALL SCREEN 200 and returning to execute the next line of code from screen 100. Your screen 100 probably has the value of 100 as the next screen in the screen attributes and so you wind up redisplaying screen 100.

The proper technique is to invoke screen 200 from 100 by:

SET SCREEN 200. LEAVE SCREEN.

That way, you still only have one screen processing session active and SET SCREEN 0, LEAVE SCREEN, from 200 will terminate the screen session.

If you want to stick to CALL SCREEN 200 then you will have to code around this problem. Maybe changing the attributes of screen 100 so that the next screen is 0 will do the trick but may disrupt some other processing that you are doing.

Let us know how it goes.