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: 

Must choose 'BACK' twice to exit report

Former Member
0 Kudos

Hello.

Suppose I trigger a report with the SUBMIT statement. To get out of the new report, the user has to press BACK twice. [F3][F3]. Why is this? I wish the user to be able to press BACK once and return to the original report that triggered the new report.

Here is the code that triggers the report:


submit zr_claims_consistency via selection-screen
                             and return.

Much thanks!

Brett

7 REPLIES 7

govind_seenivasan
Participant
0 Kudos

Hi,

Use "set screen to 0 " in your second program for the 'ESC' key.

Thanks

former_member188685
Active Contributor
0 Kudos

what are you doing in the submit program...

vijay

Former Member
0 Kudos

remove the and return option

Former Member
0 Kudos

Hi Brett,

Do you mean,when you press back it is going to the selection screen of the new report & then going to the old report??

0 Kudos

Sorry. Here is a clarification:

If the user is at the selection screen and presses the BACK button, it is ignored. User has to press the BACK button again to get back to the original report.

Removing "and return" doesn't fix the problem. That only causes the second report not to return to the first report... instead the program exits immediately.

Thanks,

Brett

former_member188685
Active Contributor
0 Kudos

submit zr_claims_consistency via selection-screen

and return.

instead of that pass the parameters and select options and remove via selection-screen.

Former Member
0 Kudos

You are calling the second program via selection-screen and so you have to press 'BACK' once to come out of the output of the second report which will take you to the selection screen of the second report. Then you have to press 'BACK' another time to come out of the selection screen of the second program and go to its caller which is your first program.

If you don't want this behaviour, then you have the following options.

Get the selections of the second program from the user in your first program itself and then do a SUBMIT ... WITH option and not go through the selection screen of the second program.

If the second program is also custom program, then change the 'BACK' functionality of the second program to exit the program immediately instead of going back to selection screen.