topic Re: Passing value from module pool(screen) to Editable ALV(OOPS).. in Application Development and Automation Discussions

Passing value from module pool(screen) to Editable ALV(OOPS)..

former_member651247 — Sun, 01 Nov 2020 17:04:20 GMT

I have a module pool screen with input field and Editable ALV (OOPS)display. I have a customized button in alv toolbar. Value from input field(module pool screen) has to be passed to handle_user_command by clicking the button. How to achieve this?

Re: Passing value from module pool(screen) to Editable ALV(OOPS)..

Sandra_Rossi — Sun, 01 Nov 2020 19:27:29 GMT

Fields of dynpros correspond to global variables in the program. So, you don't need to pass them as parameters, they are directly available anywhere in your program.

Re: Passing value from module pool(screen) to Editable ALV(OOPS)..

former_member651247 — Mon, 02 Nov 2020 05:17:42 GMT

Hello Sandra,

Value is filled only if any event is getting triggered.

For eg : After I fill value and press enter, then dynpro field is filled. But if I fill an value and press alv toolbar button directly, then value is empty. Is their any way to get value from dynpro field without any event? Please provide a valuable suggestion.

Re: Passing value from module pool(screen) to Editable ALV(OOPS)..

FredericGirod — Mon, 02 Nov 2020 06:31:32 GMT

like sandra.rossi said, the value in the dynpro is global variable. You need to create a link between this global variable and the Event on the ALV toolbar.

When you want inside class to send an event to the dynpro part, you could simulate an action like this:

cl_gui_cfw=>set_new_ok_code( 'ENTER' ).

You will directly call the PAI

Re: Passing value from module pool(screen) to Editable ALV(OOPS)..

Sandra_Rossi — Mon, 02 Nov 2020 07:47:04 GMT

I guess that the ALV toolbar events are being registered by ALV so that to not trigger the PAI.

Do:

either as suggested by Frederic,
or read directly the dynpro fields by using the function module DYNP_VALUES_READ.