Search Help in ALV Editable Field

Hi,
My requirentment is to get F4 functionality for one Editable field,
These F4 values should come from processing of internal table.
i have searched in SDN but didnt get satisfactory answer for it.
. I dont want to use ALV control table concept and with OOPs ALV,
Please let me know.how we can achieve this functionality,
your suggestions are always welcome.
Regards
Vivek

Hi,
Use the Function module: F4IF_INT_TABLE_VALUE_REQUEST
The below code shows how function module F4IF_INT_TABLE_VALUE_REQUEST is used to display a basic ABAP internal table as an SAP search help.
parameters: p_ebeln type ekko-ebeln.
TYPES: BEGIN OF t_ekko,
ebeln TYPE ekpo-ebeln,
ebelp TYPE ekpo-ebelp,
statu TYPE ekpo-statu,
aedat TYPE ekpo-aedat,
matnr TYPE ekpo-matnr,
menge TYPE ekpo-menge,
meins TYPE ekpo-meins,
netpr TYPE ekpo-netpr,
peinh TYPE ekpo-peinh,
END OF t_ekko.
DATA: it_ekko TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_ekko TYPE t_ekko,
      it_return type STANDARD TABLE OF DDSHRETVAL,
      wa_return like line of it_return.
*at selection-screen
at selection-screen on value-request for p_ebeln.
select *
up to 10 rows
from ekko
into CORRESPONDING FIELDS OF TABLE it_ekko.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
DDIC_STRUCTURE         = 'EKKO'
    RETFIELD               = 'EBELN'
PVALKEY                = ' '
   DYNPPROG               = sy-repid
   DYNPNR                 = sy-dynnr
DYNPROFIELD            = 'EBELN'
STEPL                  = 0
    WINDOW_TITLE           = 'Ekko Records'
VALUE                  = ' '
    VALUE_ORG              = 'S'
   MULTIPLE_CHOICE        = 'X' "allows you select multiple entries from the popup
DISPLAY                = ' '
CALLBACK_PROGRAM       = ' '
CALLBACK_FORM          = ' '
MARK_TAB               =
IMPORTING
USER_RESET             = ld_ret
TABLES
    VALUE_TAB              = it_ekko
   FIELD_TAB              = lt_field
    RETURN_TAB             = it_return
DYNPFLD_MAPPING        =
EXCEPTIONS
   PARAMETER_ERROR        = 1
   NO_VALUES_FOUND        = 2
   OTHERS                 = 3.
READ TABLE it_return into wa_return index 1.
p_ebeln = wa_return-fieldval.
Hope it helps you.
Regards,
Anju

Similar Messages

How to set column names in OVS search help of ALV EDIT

Hi All,
I have a OVS search help for my ALV EDIT column.This OVS will have two columns,I need to give the names(name1 , name2) to the columns.
I am writing the below codo in phase 0.
      ls_text-name = 'Column1'.
      ls_text-value = 'name1'.
      INSERT ls_text INTO TABLE lt_column_texts.
      ls_text-name = 'Column2'.
      ls_text-value = 'name2'.
      INSERT ls_text INTO TABLE lt_column_texts.
      ovs_callback_object->set_configuration(
                label_texts = lt_label_texts
                column_texts = lt_column_texts
                group_header = lv_group_header
                window_title = lv_window_title
                table_header = lv_table_header
                col_count    = 2
                row_count    = 20 ).
Below code in Phase 3.
      Assign ovs_callback_object->selection->* to <ls_selection>.
      if <ls_selection> is assigned.
        ovs_callback_object->context_element->set_attribute(
        name = `ATR1`
        value = <ls_selection>-Column1 ).
      endif.
But,the column names are not getting set.Please provide your inputs.
Regards,
Salma

hi,
About your requirement, i don't know why you need to code in "Phase 3" of OVS.
"Phase 3" is used for transporting your selected value to Your ALV.
I think, the reason why you loose the result table including your customized column title, is that you loose the "Phase 2".
Generally, in the past i used OVS as the following code simply.Just one example:
* declare data structures for the fields to be displayed and
* for the table columns of the selection list, if necessary
types:
    begin of lty_stru_input,
*   add fields for the display of your search input here
      carrid type string,
      connid type string,
    end of lty_stru_input.
types:
    begin of lty_stru_list,
*   add fields for the selection list here
      carrid type string,
      connid type string,
      text   type string,
    end of lty_stru_list.
data: ls_search_input type lty_stru_input,
        lt_select_list   type standard table of lty_stru_list,
        ls_text          type wdr_name_value,
        lt_label_texts   type wdr_name_value_list,
        lt_column_texts type wdr_name_value_list,
case ovs_callback_object->phase_indicator.
    when if_wd_ovs=>co_phase_0. "configuration phase, may be omitted
*   in this phase you have the possibility to define the texts,
*   if you do not want to use the defaults (DDIC-texts)
      ls_text-name = 'CARRID'. "must match a field name of search
      ls_text-value = 'Search Field-Carrid'.
      insert ls_text into table lt_label_texts.
      ls_text-name = 'CONNID'. "must match a field name of search
      ls_text-value = 'Search Field-Connid'.
      insert ls_text into table lt_label_texts.
      ls_text-name = 'CARRID'. "must match a field in list structure
      ls_text-value = 'Result-Carrid'.
      insert ls_text into table lt_column_texts.
      ls_text-name = 'CONNID'. "must match a field in list structure
      ls_text-value = 'Result-Connid'.
      insert ls_text into table lt_column_texts.
      ls_text-name = 'TEXT'. "must match a field in list structure
      ls_text-value = 'Result-Text'.
      insert ls_text into table lt_column_texts.
      lv_group_header = 'Group Header'.
      lv_window_title = 'Window Title'.
      lv_table_header = 'Table Header'.
      ovs_callback_object->set_configuration(
                label_texts = lt_label_texts
                column_texts = lt_column_texts
                group_header = lv_group_header
                window_title = lv_window_title
                table_header = lv_table_header
                col_count    = 3
                row_count    = 8 ).
when if_wd_ovs=>co_phase_2.
*   If phase 1 is implemented, use the field input for the
*   selection of the table.
*   If phase 1 is omitted, use values from your own context.
      if ovs_callback_object->query_parameters is not bound.
******** TODO exception handling
      endif.
      assign ovs_callback_object->query_parameters->*
                              to <ls_query_params>.
SELECT * INTO CORRESPONDING FIELDS OF TABLE lt_select_list FROM ZTABLE_FLIGHT
                       WHERE CARRID LIKE lw_carrid
                             AND CONNID LIKE lw_connid
*ovs_callback_object->set_output_table( output = lt_select_list ).*
Hope it can help.
Best wishes.

How to disappear the search help in alv

hi experts:
   some field's search help in alv appear automaticly,such as bukrs. I want to disappear the search help in ALV.how it come true?
the alv is CL_GUI_ALV_GRID.
Edited by: huiqing wei on Apr 20, 2009 10:35 AM

In the Layout give parameter NO_F4 = 'X'.
DATA:        wa_layo type lvc_s_layo.
wa_layo-no_f4 = 'X'.
call method grid_alv->set_table_for_first_display
    exporting
*    I_BUFFER_ACTIVE               =
*    I_BYPASSING_BUFFER            =
*    I_CONSISTENCY_CHECK           =
*        i_structure_name              = 'T_MARD'
*    IS_VARIANT                    =
*    I_SAVE                        =
      i_default                     = 'X'
    is_layout                     = wa_layo   <<<<<<<<<<<<<<<<<<<<<
*    IS_PRINT                      =
*    IT_SPECIAL_GROUPS             =
*    IT_TOOLBAR_EXCLUDING          =
*    IT_HYPERLINK                  =
*    IT_ALV_GRAPHICS               =
*    IT_EXCEPT_QINFO               =
*    IR_SALV_ADAPTER               =
    changing
      it_outtab                     = i_mard[]
it_fieldcatalog               = i_fieldcat[]
*    IT_SORT                       =
*    IT_FILTER                     =
exceptions
invalid_parameter_combination = 1
program_error                 = 2
too_many_lines                = 3
others                        = 4
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.

F4 help for ALV table field

Hi Experts,
I need to implement F4 help for ALV table field.
I my scenario, I am using two views. If we click on any record in fist view then it displays the popup window (second view) with relevant record details.
Here one of the columns having fieldnames corresponding values (old values), for correcting old values I have created new value editable column, we can enter new value for old value then we can save it. Till this functionality is ok.
Then I have included OVS help for new value field. Here I need to get f4 help for newvalue field relevant to fieldname.
For example: user clicks on f4 in cell (new value) then if corresponding fieldname is u2018WERKSu2019 then it shows the plant values
Here I can get fieldname, domain name and value table using method set_attribute ().
Same concept I have implemented in ALV using F4IF_FIELD_VALUE_REQUEST. It is working fine
Here I have little bit confusion. Please advise me how to implement in OVS.
Regards,
BBC

Hi,
you'll have to create a method for the OVS search help (define it in the "OVS component usage" field in the context).
Sample code (should work for WERKS):
method on_ovs .
declare data structures for the fields to be displayed and
for the table columns of the selection list, if necessary
types:
    begin of lty_stru_input,
add fields for the display of your search input here
      WERKS TYPE WERKS,
    end of lty_stru_input.
types:
    begin of lty_stru_list,
add fields for the selection list here
      WERKS TYPE WERKS_D,
      NAME1 type NAME1,
    end of lty_stru_list.
data: ls_search_input type lty_stru_input,
        lt_select_list   type standard table of lty_stru_list,
        ls_text          type wdr_name_value,
        lt_label_texts   type wdr_name_value_list,
        lt_column_texts type wdr_name_value_list,
        lv_window_title type string,
        lv_group_header type string,
        lv_table_header type string,
        lv_werks type werks_d.
field-symbols: <ls_query_params> type lty_stru_input,
                 <ls_selection>    type lty_stru_list.
case ovs_callback_object->phase_indicator.
    when if_wd_ovs=>co_phase_0. "configuration phase, may be omitted
in this phase you have the possibility to define the texts,
if you do not want to use the defaults (DDIC-texts)
Set label from Medium Description to something more logical...
      ls_text-name = `NAME1`. "must match a field in list structure
      ls_text-value = `Plant description`.
      insert ls_text into table lt_label_texts.
Set col header from Medium Description to something more logical...
      ls_text-name = `NAME1`. "must match a field in list structure
      ls_text-value = `Plant description`.
      insert ls_text into table lt_column_texts.
     lv_window_title = wd_assist->get_text( `003` ).
     lv_group_header = wd_assist->get_text( `004` ).
     lv_table_header = wd_assist->get_text( `005` ).
      ovs_callback_object->set_configuration(
                label_texts = lt_label_texts
                column_texts = lt_column_texts
                group_header = lv_group_header
                window_title = lv_window_title
                table_header = lv_table_header
                col_count    = 2
                row_count    = 20 ).
    when if_wd_ovs=>co_phase_1. "set search structure and defaults
In this phase you can set the structure and default values
of the search structure. If this phase is omitted, the search
fields will not be displayed, but the selection table is
displayed directly.
Read values of the original context (not necessary, but you
may set these as the defaults). A reference to the context
element is available in the callback object.
     ovs_callback_object->context_element->get_static_attributes(
         importing static_attributes = ls_search_input ).
    pass the values to the OVS component
     ovs_callback_object->set_input_structure(
         input = ls_search_input ).
    when if_wd_ovs=>co_phase_2.
If phase 1 is implemented, use the field input for the
selection of the table.
If phase 1 is omitted, use values from your own context.
      if ovs_callback_object->query_parameters is not bound.
      endif.
      assign ovs_callback_object->query_parameters->*
                              to <ls_query_params>.
      if not <ls_query_params> is assigned.
TODO exception handling
      endif.
        call method ovs_callback_object->context_element->get_attribute
          exporting
            name = 'WERKS'
          importing
            value = lv_werks.
        data: lv_subcat_text type rstxtmd.
        select werks
               name1
          into table lt_select_list
          from T001W.
        ovs_callback_object->set_output_table( output = lt_select_list ).
    when if_wd_ovs=>co_phase_3.
apply result
      if ovs_callback_object->selection is not bound.
      endif.
      assign ovs_callback_object->selection->* to <ls_selection>.
      if <ls_selection> is assigned.
        ovs_callback_object->context_element->set_attribute(
                               name = `WERKS`
                               value = <ls_selection>-werks ).
      endif.
endcase.
endmethod.

Web dynpro for abap how to create a customize search help in alv column

   hi:
      Web dynpro for abap how to create a customize search help in alv column and put search help value into alv column?
      Are there specific examples ?
      thanks!!

HI:
   I want to created a freely programed help which include date&time,and put help value to alv column.
I have created a freely programed help in web dynpro for abpa application,I refer:
**************** - WebDynpro for ABAP
but have a problem!
   If you focus on the the input field in the first row, you get the value help
However if I go to the second row and focus on the same input field in this column, I don't get the value help:
What is a good way to solve similar problems？
thanks

Search Help for Infotype Custom Field

Hi,
I have created a search help for a custom field in an infotype. What would be the best way of filtering the help selection based on infotype values such as molga, begda, endda?
Thanks in advance.
/Elvez

Hi Nishanth,
thanks for your reply, perhaps I should clarify my question:
1) I have a custom field in an infotype
2) I have a table containing the search help information
3) I assigned a search help to the custom field
4) I have activated a search help exit
The problem is that the information that I get from the custom field is not sufficient for making the selection. Therefore, I would like to somehow get hold of the addition information, such as BEGDA, ENNDA, MOLGA, to do a proper selection in the search help exit. How can I achieve that?
I read something about function module DYNP_VALUES_READ -would it be possible to call this function module from my search help exit and thereby reach my goal?
/Elvez
Message was edited by: Elvez

How to add a search help on a screen field from screen painter

Hi,
I would like to add an existing Search Help on a screen field in Screen painter.
Of course it's possible to just click on th screen field and in the property box, I just have to set the name of teh search help.
The problem is that I need the screen field to be grey and user musn't be able to change the field value if he doens't use the search help.
I'm not allowed to modify the existing search help or to built it on my own from source code, I must use the existing one.
Do you have an idea on how to do so?
Regards,
Morgan

Dropdown Box:
In the screen painter for that field goto properties -> Dropdown ->select listbox.
Option 1:
Instead let that field be in change mode and if user enters any wrong entry which is not there in the table give a error messgae.
CHAIN.
    FIELD addr1_data-country.
    MODULE modify_screenfields1.
ENDCHAIN.
MODULE modify_screenfields1 INPUT.
CASE sy-ucomm.
    WHEN 'ENTER' OR 'EXECUTE'.
      IF NOT addr1_data-country IS INITIAL.
        SELECT SINGLE landx FROM t005t INTO lws_landx WHERE
                                      land1 = addr1_data-country
                                  AND spras = 'EN'.
        IF sy-subrc <> 0.
          MESSAGE e000(zo_spa) WITH text-022. " Invalid Country code
        ELSE.
          t005t-landx = lws_landx.
        ENDIF.
      ELSE.
        CLEAR: t005t-landx.
      ENDIF.
   ENDCASE.
ENDMODULE.                 " modify_screenfields1 INPUT
Option 2: Other than if u want the way u like, let that field be greyed out. don't attach the search help.
In the PROCESS ON VALUE-REQUEST.
FIELD addr1_data-region MODULE region_pov.
MODULE region_pov INPUT.
Using the F4IF_INT_TABLE_VALUE_REQUEST table value request show the search help.
also make that field input enabled.
ENDMODULE.                 " region_pov INPUT
I think this will solve ur problem.
Regards,
Prakash.
Message was edited by: Prakash Ramu

Search Help In ALV Grid

What is shortest way to attach particular Search Help in ALV grid using OOPS ?

Thanks Gurpreet,
Through search helps attached to data element it is possible but is there any other way to attach searchhelp differet from from the search help attached to the data element ? The new search-elp is not customized search help as given in the above threads ?
Eg. - If I want to attach MAT2 to a field named MATNR in the table instead of the MAT1 which is standard.
Thanks in advance

Attach search help to standard table field

Hi,
I need to attach search help to standard table field VBKD-EMPST.
I have create a z search help and taken acess key from SAP.
But unable to attach this to standard table field.
Kindly help.
Moderator message: duplicate post locked.
Edited by: Thomas Zloch on Oct 27, 2010 6:11 PM

Hi,
just go throw this link
Re: Attaching Search Help to a field
I hope this will help u
Thanks
Regards
Akhilesh Singh

Regarding Search help on selection-screen field

Hi there,
I am working on custom tables.
I have a requirement to maintain search pattern on a selection-screen field.
selection-screen parameter: p_name which is company name filed from Z table.
By giving a string like Holl* and by pressing F4 on the field p_name it has to popup a dialogbox having list of company names starting with Holl.
Thanks in advance.
-Tulasi

Hi
Go through the link given below :
How to create a search help for my own fields in selection screen
F4 search help on report selection screen
also try :
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
DDIC_STRUCTURE = ' '
RETFIELD = 'VKORG'
PVALKEY = ' '
DYNPPROG = SY-REPID
DYNPNR = SY-DYNNR
DYNPROFIELD = 'P_VKORG'
STEPL = 0
WINDOW_TITLE =
VALUE = ' '
VALUE_ORG = 'C'
TABLES
VALUE_TAB = T_TABLE1
FIELD_TAB = field_tab
RETURN_TAB = RET_TAB
DYNPFLD_MAPPING = DYN_TAB
EXCEPTIONS
PARAMETER_ERROR = 1
NO_VALUES_FOUND = 2
OTHERS = 3
With Regards
Nikunj shah

Need some help in creating Search Help for standard screen/field

I need some help in adding a search-help to a standard screen-field.
Transaction Code - PP01,
Plan Version - Current Plan (PLVAR = '01'),
Object Type - Position ( OTYPE = 'S'),
Click on Infotype Name - Object ( Infotype 1000) and Create.
I need to add search help to fields Object Abbr (P1000-SHORT) / Object Name (P1000-STEXT).
I want to create one custom table with fields, Position Abb, Position Name, Job. Position Abb should be Primary Key. And when object type is Position (S), I should be able to press F4 for Object Abb/Object Name fields and should return Position Abbr and Position Name.
I specify again, I have to add a new search help to standard screen/field and not to enhance it.
This is HR specific transaction. If someone has done similar thing with some other transation, please let me know.
There is no existing search help for these fields. If sm1 ever tried or has an idea how to add new search help to a standard screen/field.
It's urgent.
Thanks in advace. Suitable answers will be rewarded

Hi Pradeep,
Please have a look into the below site which might be useful
Enhancing a Standard Search Help
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/daeda0d7-0701-0010-8caa-
edc983384237
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee93446011d189700000e8322d00/frameset.htm
A search help exit is a function module for making the input help process described by the search help more flexible than possible with the standard version.
This function module must have the same interface as function module F4IF_SHLP_EXIT_EXAMPLE. The search help exit may also have further optional parameters (in particular any EXPORTING parameters).
A search help exit is called at certain timepoints in the input help process.
Note: The source text and long documentation of the above-specified function module (including the long documentation about the parameters) contain information about using search help exits.
Function modules are provided in the function library for operations that are frequently executed in search help exits. The names of these function modules begin with the prefix F4UT_. These function modules can either be used directly as search help exits or used within other search help exits. You can find precise instructions for use in the long documentation for the corresponding function module.
During the input help process, a number of timepoints are defined that each define the beginning of an important operation of the input help process.
If the input help process is defined with a search help having a search help exit, this search help exit is called at each of these timepoints. If required, the search help exit can also influence the process and even determine that the process should be continued at a different timepoint.
timepoints
The following timepoints are defined:
1. SELONE
Call before selecting an elementary search help. The possible elementary search helps are already in SHLP_TAB. This timepoint can be used in a search help exit of a collective search help to restrict the selection possibilities for the elementary search helps.
Entries that are deleted from SHLP_TAB in this step are not offered in the elementary search help selection. If there is only one entry remaining in SHLP_TAB, the dialog box for selecting elementary search helps is skipped. You may not change the next timepoint.
The timepoint is not accessed again if another elementary search help is to be selected during the dialog.
2. PRESEL1
After selecting an elementary search help. Table INTERFACE has not yet been copied to table SELOPT at this timepoint in the definition of the search help (type SHLP_DESCR_T). This means that you can still influence the attachment of the search help to the screen here. (Table INTERFACE contains the information about how the search help parameters are related to the screen fields).
3. PRESEL
Before sending the dialog box for restricting values. This timepoint is suitable for predefining the value restriction or for completely suppressing or copying the dialog.
4. SELECT
Before selecting the values. If you do not want the default selection, you should copy this timepoint with a search help exit. DISP should be set as the next timepoint.
5. DISP
Before displaying the hit list. This timepoint is suitable for restricting the values to be displayed, e.g. depending on authorizations.
6. RETURN (usually as return value for the next timepoint)
The RETURN timepoint should be returned as the next step if a single hit was selected in a search help exit.
It can make sense to change the F4 flow at this timepoint if control of the process sequence of the Transaction should depend on the selected value (typical example: setting SET/GET parameters). However, you should note that the process will then depend on whether a value was entered manually or with an input help.
7. RETTOP
You only go to this timepoint if the input help is controlled by a collective search help. It directly follows the timepoint RETURN. The search help exit of the collective search help, however, is called at timepoint RETTOP.
8. EXIT (only for return as next timepoint)
The EXIT timepoint should be returned as the next step if the user had the opportunity to terminate the dialog within the search help exit.
9. CREATE
The CREATE timepoint is only accessed if the user selects the function "Create new values". This function is only available if field CUSTTAB of the control string CALLCONTROL was given a value not equal to SPACE earlier on.
The name of the (customizing) table to be maintained is normally entered there. The next step returned after CREATE should be SELECT so that the newly entered value can be selected and then displayed.
10. APP1, APP2, APP3
If further pushbuttons are introduced in the hit list with function module F4UT_LIST_EXIT, these timepoints are introduced. They are accessed when the user presses the corresponding pushbutton.
Note: If the F4 help is controlled by a collective search help, the search help exit of the collective search help is called at timepoints SELONE and RETTOP. (RETTOP only if the user selects a value.) At all other timepoints the search help exit of the selected elementary search help is called.
If the F4 help is controlled by an elementary search help, timepoint RETTOP is not executed. The search help exit of the elementary search help is called at timepoint SELONE (at the
F4IF_SHLP_EXIT_EXAMPLE
This module has been created as an example for the interface and design of Search help exits in Search help.
All the interface parameters defined here are mandatory for a function module to be used as a search help exit, because the calling program does not know which parameters are actually used internally.
A search help exit is called repeatedly in connection with several
events during the F4 process. The relevant step of the process is passed on in the CALLCONTROL step. If the module is intended to perform only a few modifications before the step, CALLCONTROL-STEP should remain unchanged.
However, if the step is performed completely by the module, the following step must be returned in CALLCONTROL-STEP.
The module must react with an immediate EXIT to all steps that it does not know or does not want to handle.
Hope this info will help you.
***Reward points if found useful
Regards,
Naresh

Custom Search Help for Business Agreement field in transaction BP.

Dear Experts,
My requirement is to add Custom search help to Businees Agreement field (BUPA_CRMM31-BUAG_ID) in transaction code BP.
PLease guide me how to add Custom search help to Businees Agreement field which dont have search help option.
Regards,
Bala

Hello there,
I think the requirement/question is not very clear in your post.
However, the segment Java applet calls a CRM class which has related code and methods.
Class: CL_CRM_MKTTG_SEGAP_COM
Package: CRM_MKTTG_SEG_APPLET.
Please explain the problem in detail.
Regards,
Vinamra.

Search help for a Input Field........

Hi,
I'm fairly new to BSP and I would like to know how to attach Search Help to the Input Field in BSP application.
Thanks
NP.

Hi nagendra
Search Help for input field Provide using attribute of input field is showHelp and onvaluehelp
This is providing the search help .

Change Search Help for Payment Terms Field

Hi,
I would like to change the Search Help for Payment Terms Field, in Customer Master (KNVV-ZTERM). and in Sales Document. I believe it is the same.
Default is From Table T052 / T052U
ZTERM and TEXT1 Fields
I would like to have
From Table TVZBT
ZTERM and VTEXT
PayT Own Explanation Field.
Can we change the Search Help.

Hi,
The search help for the payment terms is not coming from the DDIC search help..
It is coded in the process on value-request event...
The function module FI_F4_ZTERM is called for this..you have to change this function module in case if you want the values from a different table..
OR do implicit enhancement in the subroutine FORM HELP_ZTERM in the include MF02DFH0 to call your search help instead of the function module FI_F4_ZTERM ..And do the same for the sales order also..
Thanks
Naren

Dynamic Search Helps In An Input Field

Hi Experts,
          I need to populate an input field with different search helps based on the user action i.e when user selects "Audit" i hav to show the audit search help for my input field, when he selects "Audit Plan" i would hav to show audit plan search help.
My Questions >
1> i intend to use the method set_attribute_value_help of the interface if_wd_context_info and do the coding as :-
data lo_nd_info type if_wd_context_node_info.
lo_nd_info = lo_nd->get_node_info( ).
CALL METHOD lo_nd_info->set_attribute_value_help
        EXPORTING
          name            = 'identification' (attribute Name)
          value_help_mode = '121'
          value_help      = 'plm_auditplan'.(Help Name)
Is this the correct way to go if not plz suggest a more appropriate method.
2> in the context for that attribute ,what should i specify for the property input field
    Input Help Mode
    i.e should it be deactivated , automatic or should i give the dictionary serach help and specify one of the search helps by giving its name.
Your responses will be greatly appreciated,
Chaitanya.

Hi Ebru,
Yes, it is possible using OVS, freely programmed and dictionary help.
For OVS, refer this blog: /people/shruti.rathour/blog/2008/05/05/ovs-help-in-web-dynpro-abap
For Dictionary Search Help, refer http://help.sap.com/saphelp_nw70/helpdata/EN/47/9f724642314aabe10000000a42189b/frameset.htm
For freely programmed, refer:
http://help.sap.com/saphelp_nw70/helpdata/EN/47/9ef8cc9b5e3c5ce10000000a421937/content.htm
I hope it helps.
Regards
Arjun

Search Help in ALV Editable Field

Similar Messages

Maybe you are looking for