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

Screen calling ...

Former Member
0 Likes
590

Hi,

I have 2 custom module pool applications. Let me say A,B.

I am calling B application from 8000 screen number of A application . Here, If I click on BACK

push button, it should come back directly to A application 8000 screen. In B application 2 screen are there.

When I call B application I am skipping the first screen and going directly to second screen. Here I need help,

If I click BACK button in Second screen of B application, it should not go back to First screen of the B application. It should go

directly to the A application screen 8000. Is there any parameters to handle this issue.

Help me.

Sridhar B

1 ACCEPTED SOLUTION
Read only

MarcinPciak
Active Contributor
0 Likes
562

It depends on how you called those two screens in second program and what is set as NEXT SCREEN for them. Go to first screen which you are skipping and in Next screen attribute type 0 , then go to second and do the same.

Now when you call your second program which skips first screen there has to be some direct call of second screen (CALL SCREEN). When you leave this screen (with BACK) you are back in first screen (which you have just skipped) but as next screen for it is also 0, you will in fact be back in first program.

This should help.

Regards

Marcin

4 REPLIES 4
Read only

Former Member
0 Likes
562

Hi,

Have you tried using , CALL SCREEN '8000'

Regards

Pavan

Read only

0 Likes
562

It will give dump. Because that 8000 screen is designed in A application.

Read only

MarcinPciak
Active Contributor
0 Likes
563

It depends on how you called those two screens in second program and what is set as NEXT SCREEN for them. Go to first screen which you are skipping and in Next screen attribute type 0 , then go to second and do the same.

Now when you call your second program which skips first screen there has to be some direct call of second screen (CALL SCREEN). When you leave this screen (with BACK) you are back in first screen (which you have just skipped) but as next screen for it is also 0, you will in fact be back in first program.

This should help.

Regards

Marcin

Read only

Former Member
0 Likes
562

Hi,,,Hope you have created the transaction codes separately for those two module pool applications...

If so ,when you press BACK button call the first the transaction code and skiip the first screen,but this is possible when the first screen has paramter id valuesfor the fields you have declared.

This is just one option