SAP EWM PAI Function Module Importing Values

[former_member231869]

Hi

I have design a custom screen in the Transaction code :- /N/SCWM/RFUI.

As you can see below.

After this user will insert HU and then hit Enter at the time of Enter my Function module getting trigger.

but issue is HU :- GR-YDI1 value is not appearing in that FM

Import parameter IV_HU not able to get the value.

Below Zstep1 Triggering the FM : ZFM_ZEWMF005_SCREEN1_PAI . FM gets trigger but values not populating from the screen.

Please suggest what i need to do in this?

[Daniil]

Hi Panther, check the RF Cookbook. Pay attention to the Chapter "Define Application Data Containers.

BR,

Daniil

[former_member231869]

Hi Daniil,

I follow the Document and Create Application Parameter as below.

then Use the Same Name in the Function Module as Below.

But Still HU is having the Blank values.

Is there anything else i'm missing?

[Daniil]

Registering the data container is mandatory. The best way to do so is to initialize
the registration process on the PBO (process before output) screen and register
all of the data containers that are used on the screen

[former_member231869]

First in the PBO like this initiate screen parameter and then set the application parameter

In PAI getting the data and getting the screen parameter

Is anything wrong in both of this?

[Daniil]

No Need to assign anything. You get automatically your values, FM is called dynamically.

when your PBO is getting called you should get directly your HU structure available.

it should be enough to call
/scwm/cl_rf_bll_srvc=>set_screen_param( 'HU' ).

And in the PAI you can use HU-HUIDENT

And on your screen field should be defined as /scwm/s_aqua/int-huident

I hope I described everything correct 🙂

[former_member231869]

Yes I'm getting structure HU but whole structure is coming blank in PAI and Screen field is also /scwm/s_aqua_int-huident

[former_member231869]

Is it correct way to define.

[Daniil]

you can check if your structure available in

st_param and ST_DATA one step above your FM.

You can set Breakpoint in the method

/scwm/cl_rf_bll_srvc=>get_screen_param( ). To check what goes wrong. Magic happens in USER_COMMAND_SSCR (include /SCWM/LRF_SSCRI01).

BR,

Daniil

[Daniil]

steps customizing looks not correct. If you have step as background it should be code defined for background processing. It would be better for you use some kind template, to copy for example standard tcode, or to read RF Cookbook for more info. I haven't worked for a long time with standard RF framework, maybe somebody can give your a better hint 🙂

[former_member231869]

But when i debug /scwm/cl_rf_bll_srvc=>get_screen_param( )

found the HU parameter get deleted in lt_param

DELETE ADJACENT DUPLICATES FROM rt_param.

lt_param = st_param.
LOOP AT rt_param INTO lv_param.
READ TABLE lt_param INTO ls_param
WITH KEY param_name = lv_param.

IF ls_param-param_stcr IS NOT INITIAL.
lv_flg_table = abap_true.
ENDIF.

DELETE lt_param WHERE param_type =: ls_param-param_type,
ls_param-param_stcr.
ENDLOOP.

[Daniil]

but if you set it with set screen param it is in st_scr_param table and it has to be as well in rt_param . maybe I see it somehow wrong?

[Daniil]

maybe your PBO is not called?