‎2006 Sep 13 1:24 AM
I modified an elementary search setting the export flag
on 3 parameters in addition to the 1 export parameter
previously set. There are a total of 7 parameters. My intent is to map these 3 additional fields to the screen.
I call function module 'F4IF_FIELD_VALUE_REQUEST' passing a callback form F4_WR_CALLBACK. After the call to 'F4IF_FIELD_VALUE_REQUEST' I read the return table lt_return and then update the 3 screen fields using function 'DYNP_VALUES_UPDATE'. It works perfectly in my
dev system. After transporting to QA it no longer works.
In going through debug, I can see that in my QA environment when executing the following statement: IMPORT shlp callcontrol-attachkind timestamp timerelobj_tab
FROM SHARED BUFFER ddshoffld(if) ID sh_buf_id.
the shlp-interface table does not include the 3 new parameters added to the search help whereas it does in dev.
Any ideas would be greatly appreciated.
<u>The code follows:</u>
call function 'F4IF_FIELD_VALUE_REQUEST'
exporting
tabname = 'ZIX_SCG_INTORD'
fieldname = 'AUFNR'
dynprofield = 'GS_ES_ATTRS-WORK_REQ'
callback_program = 'SAPLZES_SCREENS'
callback_form = 'F4_WR_CALLBACK'
tables
return_tab = lt_return
exceptions
field_not_found = 1
no_help_for_field = 2
inconsistent_help = 3
no_values_found = 4
others = 5.
form f4_wr_callback tables record_tab structure seahlpres
changing shlp type shlp_descr_t
callcontrol like ddshf4ctrl.
data: interface like line of shlp-interface.
interface-valtabname = 'GS_ES_ATTRS'.
interface-valfield = 'WORD'.
modify shlp-interface from interface
transporting valtabname valfield
where shlpfield = 'WORD'.
interface-valtabname = 'GS_ES_ATTRS'.
interface-valfield = 'WORK_REQ'.
modify shlp-interface from interface
transporting valtabname valfield
where shlpfield = 'WORK_REQ'.
interface-valtabname = 'GS_ES_ATTRS'.
interface-valfield = 'PROJ'.
modify shlp-interface from interface
transporting valtabname valfield
where shlpfield = 'PROJ'.
endform.
‎2006 Sep 13 2:16 AM
Hi Bob,
Every Import Statement should have an export statement. I hope you have transported the object/report/program which has that EXPORT statement.
I would say, that the only problem `The program which has the Export statement is not transported to QA`. Once you transport it, the problem would be solved.
Best regards,
Prashant
‎2006 Sep 13 5:40 PM
Thank You Prashant. Actually the Export is done in one of the standard SAP Search Help function modules DD_SHLP_GET_HELPMETHOD which is invoked when calling
F4IF_FIELD_VALUE_REQUEST. It seems to me that it is not retrieving the new definition of the interface from the dictionary.
‎2006 Sep 13 7:57 AM
Hello Bob
I would recommend to make a simple version comparison of the search help between DEV and PROD. If you see any difference there then transport your search help again to PROD.
Regards
Uwe
‎2006 Sep 13 6:00 PM
Thank You Uwe. I already did the compare and it checks out fine.
Some additional information:
If I run FM DD_SHLP_GET_HELPMETHOD in my Dev and QA systems the changing parameter SHLP-interface returns the 4 paramters in QA and correctly returns the 7 in my Dev system. The SHLP is updated in form SHARED_BUFFER_IMP_INTERFACE using the Import statement I included in my first post.