User interaction button

Question

Hi Experts,
       I have developed a function module and after running it , in the output screen i want to have user interaction by giving proceed button and if press the buttoon o/p of the FM should be downloaded.
To add the button in o/p screen i used the Screen statement AT USER COMMAND, AT LINE-SELECTION. But FM not access these screen statements.Then i created a screen 100 with PF Status, in that screen i have maintained the proceed button. Then i call this screen inside the FM. The screen is coming along with the proceed button. But the FM o/p not coming along this proceed button screen.
Please help out to have a button for user interaction in o/p of the FM.
Thanks.
Kelvin

Answer 1

Hi Kelvin,
     You have created a screen and then you have added the Proceed button in the screen. Later you have called the screen in the FM . When executing the FM you are able to see the proceed button but you are not able to download the data after that.
The solution is.
     Move your data to a Global variable declared in the TOP INCLUDE of the function group of the FM. Now In the FM before calling screen move all the processed data in FM to that Global variable then in you PAI of the screen, under USER_COMMAND module, Check if the Proceed button is pressed. And if pressed Enter your LOGIC. Code sample given below.
Lets day the data you have to download is in internal table it_data.
Do as mentioned below.
1). In your top include.
DATA: it_data TYPE STANDARD TABLE OF ty_data.
2). In your FM.
it_final is the table in FM which has your processed data and this is also of same structure ty_data.
it_data[] = it_final[].  " moving all the data to global variable.
CALL SCREEN 100.
3). in the PAI of screen 100.
MODULE USER_COMMAND INPUT.
CASE sy-ucomm.
WHEN 'PROCEED'.
<logic to download the it_data table>
ENDCASE.
ENDMODULE.
Thus your requirement can be achieved by moving the data to a global variable then downloading it using user interaction button.
Please do let me know for more details.
Regards,
Praveenkumar T.