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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Issue in getting back to alv screen from called module pool

Go to solution
Former Member

‎04-09-2008 7:19 PM

0 Kudos

Hi all,

Am using following statements in my alv report to call module pool program after execution so that the first module pool screen is skiped .

SET PARAMETER ID 'AUN' FIELD PU_SELFIELD-VALUE.

CALL TRANSACTION 'ZMSTM029' AND SKIP FIRST SCREEN.

But after clicking 'back' form module pool screen ALV screen is not displayed instead the first module pool screen is displayed whish was skipped.

I will be thankful if anybody can help to come back to ALV screen so that while coming back to to alv first module pool screen is avoided.

Thanks.

1 ACCEPTED SOLUTION

Go to solution
RichHeilman
Developer Advocate
Developer Advocate

‎04-09-2008 7:26 PM

0 Kudos

Right, you can not control how you leave the called transaction unless you specifically handle it in that program. You would need to do something like, setting some value in memory using EXPORT statement, and then in the PAI of the screen in the called transaction, you can try to IMPORT this value, and if it is the value which you passed from the the EXPORT, then you can put code to immedatialy leave the program instead of going back to the initial skipped screen. You can only do this since it appears that you are calling a custom program, otherwise you would have to hack the standard program, which i don't think you want to do.

Regards,

Rich Heilman

1 REPLY 1

Go to solution
RichHeilman
Developer Advocate
Developer Advocate

‎04-09-2008 7:26 PM

0 Kudos

Right, you can not control how you leave the called transaction unless you specifically handle it in that program. You would need to do something like, setting some value in memory using EXPORT statement, and then in the PAI of the screen in the called transaction, you can try to IMPORT this value, and if it is the value which you passed from the the EXPORT, then you can put code to immedatialy leave the program instead of going back to the initial skipped screen. You can only do this since it appears that you are calling a custom program, otherwise you would have to hack the standard program, which i don't think you want to do.

Regards,

Rich Heilman