F4IF_SHLP_EXIT_EXAMPLE

Anybody used this function in HELP SEARCH?

Hai Avalor,
Here are the links which give you some useful stuff...
http://help.sap.com/saphelp_46c/helpdata/en/8b/415d363640933fe10000009b38f839/frameset.htm
http://help.sap.com//saphelp_470/helpdata/EN/cf/21ee52446011d189700000e8322d00/content.htm
Re: search help
Re: My custom exit in search help is not triggering
Re: How to implement search help exit
Regards,
Srikanth.
Please reward points if helpful.

Similar Messages

Search help F4IF_SHLP_EXIT_EXAMPLE

I have a requirement regarding F4 help. When I click on the zoom button for vendor code, the list of values according to the coding given in serach help exit should get displayed with only company code as input.
The list of vendors is picked from LFa1 table as per the foll. code:
    SELECT LIFNR BUKRS FROM LFB1 CLIENT SPECIFIED
         INTO TABLE IT_LFB1
           WHERE MANDT = SY-MANDT
           AND BUKRS = M_BUKRS.
      SELECT LIFNR NAME1 FROM LFA1 CLIENT SPECIFIED
           INTO TABLE IT_LFA1 FOR ALL ENTRIES IN IT_LFB1
             WHERE MANDT = SY-MANDT
             AND LIFNR = IT_LFB1-LIFNR
             AND ( KTOKK LIKE '%07' OR KTOKK LIKE '%06' )
             AND SPRAS = 'E'
             AND LZONE = '0000000002'.
How do I put this coding in the search help exit program ?
Please help.
Regards,
Tom Jerry.

Hi,
No you can't get import parameters from screen while you are using search help exit,
Because everything is limited to parameters of exit function.
There is another way to limit the range of search help hit list
you should use on the VALUE-REQUEST event of your screen.
Check this code :
DATA: lv_shelp_name TYPE shlpname,
        ls_shelp TYPE shlp_descr,
        ls_selopt TYPE ddshselopt,
        ls_rc LIKE sy-subrc,
        lt_return_values TYPE TABLE OF ddshretval,
        ls_return_values TYPE ddshretval,
        ls_interface LIKE LINE OF ls_shelp-interface,
        lw_field_ranges LIKE LINE OF ip_field_ranges.
lv_shelp_name = f4help_name.
* get description for search help
CALL FUNCTION 'F4IF_GET_SHLP_DESCR'
    EXPORTING
      shlpname = lv_shelp_name
    IMPORTING
      shlp     = ls_shelp.
* set range for search help field :
   ls_selopt-shlpname = lv_shelp_name.
   ls_selopt-shlpfield = 'BUKRS'.
   ls_selopt-sign      = 'I'.
   ls_selopt-option    = 'BT'.
   ls_selopt-low       = lv_company_code
   COLLECT ls_selopt INTO ls_shelp-selopt.
ls_interface-valfield = 'X'.
ls_interface-valtabname = 'X'.
MODIFY ls_shelp-interface FROM ls_interface
         TRANSPORTING valtabname valfield
         WHERE shlpfield = ip_ret_fieldname.
* call F4 dialog
CALL FUNCTION 'F4IF_START_VALUE_REQUEST'
    EXPORTING
      shlp          = ls_shelp
    IMPORTING
      rc            = ls_rc
    TABLES
      return_values = lt_return_values.
I hope it can be useful for u

Searchhelp-Exit: F4IF_SHLP_EXIT_EXAMPLE

Dear developers,
our company produces SAP add-ons which are supposed to
run under 4.6C as well as under 4.7 Enterprise.
As far as ABAP commands are concerned some of which
behave a little differently in both environments,
we usually solve those problems by calling up FM modules
dynamically after checking the appropriate syst-variable.
Unfortunetaly this doesn't work for our searchhelp-exits,
where 4.6C and 4.7-systems demand different references
for the SHLP and SHLP_TAB parameters of the exit-FM.
4.6 wants the SHLP_TAB to refer to SHLP_DESCR_TAB_T and
SHLP to refer to SHLP_DESCR_T, both of which are
definitions in type group SHLP.
4.7 wants the SHLP_TAB to refer to SHLP_DESCT (DDIC) and
the SHLP parameter to SHLP_DESCT (DDIC).
Both types of system do not know the structures of the
"other" system and you have difficulties activating a
searchhelp, when both of thoses parameters remain without
a reference. It is possible to do it though, but I
don't feel comfortable with the warnings we get during
the imports of our program transports.
Does anyone have an idea how to get rid of that problem?
Thanks in advance
Andreas

Hello Andreas,
it shouldn't be a real problem, because when you look in Rel.4.7 into the type-pool SHLP, you'll find the definition:
TYPES: SHLP_INTDESCR_T TYPE SHLP_INTDS,
 SHLP_DESCR_T TYPE SHLP_DESCR,
SHLP_DESCR_TAB_T TYPE SHLP_DESCT.
Regards Wolfgang

F4IF_SHLP_EXIT_EXAMPLE problem

Hallo all,
i can not how this search help exit pass the value from record_tab to search help fields. I saw that record_tab hold the values in one string field but how to pass in the search help to trwo different field. For example in search help i have
pr_type and description , but this is stored in one field in record_tab.So i have to use some other function to split the values. Is somebody knows which fm i can use?
Full points for helpful answers!!!

hi,
Here is a search help exit I created. You can use the code as reference.
function Z_SHLP_BATCH_EXIT.
""Local Interface:
*" TABLES
*" SHLP_TAB TYPE SHLP_DESCR_TAB_T
*" RECORD_TAB STRUCTURE SEAHLPRES
*" CHANGING
*" VALUE(SHLP) TYPE SHLP_DESCR_T
*" VALUE(CALLCONTROL) LIKE DDSHF4CTRL STRUCTURE DDSHF4CTRL
data: l_record like line of record_tab,
 l_records like record_tab occurs 0,
 l_interface like line of shlp-interface,
 l_selopt like LINE OF shlp-SELOPT,
 l_name TYPE SHLPNAME,
 wa_shlp TYPE SHLP_DESCR.
data: l_sf_type type tdsftype,
 l_sf_name type tdsfname,
 l_fp_runtime type tdsfmtype,
 l_type_req type tdsftype,
 l_idx like sy-tabix.
DATA : i_mchb TYPE TABLE OF mchb,
 wa_mchb LIKE LINE OF i_mchb,
 i_mard TYPE TABLE OF mard,
 wa_mard LIKE LINE OF i_mard.
DATA : v_matnr TYPE matnr_d,
 l_matnr TYPE matnr_d,
 v_werks TYPE werks_d,
 l_werks TYPE werks_d.
DATA : BEGIN OF i_final OCCURS 0,
 matnr TYPE matnr_d,
 werks TYPE werks_d,
 charg TYPE charg_d,
 lgort TYPE lgort_d,
 clabs TYPE labst,
 END OF i_final.
DATA : l_dynpro TYPE STANDARD TABLE OF DYNPREAD.
READ TABLE shlp_tab INTO wa_shlp INDEX 1.
l_name = wa_shlp-SHLPNAME.
case callcontrol-step.
 when 'SELONE'. " before selection screen
 when 'SELECT'. " before selection
 REFRESH i_mchb.
 when 'DISP'. " before selected data is displayed
Extract the material number and plant from the interface
 read table shlp-SELOPT into l_selopt WITH key shlpfield = 'MATNR'.
 l_matnr = l_SELOPT-low.
 CLEAR l_SELOPT.
 READ TABLE shlp-SELOPT INTO l_SELOPT WITH key shlpfield = 'WERKS'.
 l_werks = l_SELOPT-low.
 CLEAR l_SELOPT.
select data from MCHB table to put as output.
 SELECT *
 FROM mchb
 INTO TABLE i_mchb
 WHERE matnr = v_matnr
 AND werks = v_werks.
 if NOT i_mchb[] IS INITIAL.
 LOOP AT i_mchb INTO wa_mchb.
 MOVE-CORRESPONDING wa_mchb to i_final.
 APPEND i_final.
 CLEAR : wa_mchb,
 i_final.
 ENDLOOP.
 call function 'F4UT_RESULTS_MAP'
 TABLES
 shlp_tab = shlp_tab
 source_tab = i_final
 record_tab = record_tab
 CHANGING
 shlp = shlp
 callcontrol = callcontrol
 EXCEPTIONS
 others = 1.
 endif.
 CLEAR : wa_item,
 wa_input1,
 WA_FGINPUT.
 when others.
endcase.
endfunction.

Populate and display internal table results using search help exit...

I have copied F4IF_SHLP_EXIT_EXAMPLE and made changes. I want this search help exit to populate and display contents related to 'FIELD1' when the user enters a specific value for it in the search help screen, meaning when the user restricts the search by that value. For field2, field3, field4, field5, field6, field7, and field8 I am using a custom view.
Following is the code:
TYPES: BEGIN OF t_search,
               field2 TYPE field2,
               field3 TYPE field3,
               field4 TYPE field4,
               field5 TYPE field5,
               field6 TYPE field6,
               field7 TYPE field7,
               field8 TYPE field8,
               field1 TYPE field1,
            END OF t_search.
DATA: it_itab TYPE TABLE OF t_search,
        wa TYPE t_search,
     wa_selopt TYPE ddshselopt,
        wa_fielddescr TYPE dfies.
ranges: r_field1 for std_table1-field1
STEP SELECT    (Select values)
    FREE: r_field1.
**Get the value entered for FIELD1 in search help
    LOOP AT shlp-selopt INTO wa_selopt.
      CASE wa_selopt-shlpfield.
        WHEN 'FIELD1'.
          r_field1-sign = wa_selopt-sign.
          r_field1-option = wa_selopt-option.
          r_field1-low = wa_selopt-low.
          r_field1-high = wa_selopt-high.
          APPEND r_field1.
          CLEAR: r_field1.
      ENDCASE.
    ENDLOOP.
**Select 'ID' and 'FIELD1' from table into lt_itab
    SELECT id field1
          INTO TABLE lt_itab
            FROM std_table1
              WHERE field1 IN r_field1.
    IF sy-subrc = 0.
**Now, based on the particular IDs from lt_itab, I need to select other values
from other tables which also have 'ID' as the key.
       SELECT std_table2~field2
            std_table2~field3
            std_table3~field4
            std_table3~field5
            std_table3~field6
            std_table4~field7
            std_table4~field8
            std_table1~field1
          INTO CORRESPONDING FIELDS OF TABLE it_itab
          FROM std_table2
                     INNER JOIN std_table3 ON
                            std_table3mandt = std_table2mandt AND
                            std_table3id = std_table2id
                     INNER JOIN std_table4 ON
                            std_table4mandt = std_table2mandt AND
                            std_table4id = std_table2id
                     INNER JOIN std_table1 ON
                            std_table1mandt = std_table2mandt AND                                           std_table1id = std_table2id
          WHERE
                std_table1~field1 IN r_field1.
'id' is common in all the std_tables --> std_table1, std_table2, std_table3, std_table4.
STEP DISP     (Display values)
**Then I need to gather all the results in my internal table it_itab and display
in search help results for the value of FIELD1 entered by the user in the search help.
    CALL FUNCTION 'F4UT_PARAMETER_RESULTS_PUT'
      EXPORTING
        parameter   = 'FIELD1'
        fieldname   = 'FIELD1'
      TABLES
        shlp_tab    = shlp_tab
        record_tab = record_tab
        source_tab = it_itab
      CHANGING
        shlp        = shlp
        callcontrol = callcontrol.
I am not getting all the data in my internal table and wanted to know if there is anyting wrong in my select statement.
Any guidance will be appreciated and awarded appropriate points.
Thanks.

the webdynpro fieldname and the search help input parameter name were made same.

SELECT-OPTIONS Values via DYNP_VALUES_READ in a Search Help Exit

Hi all,
I appended a standard search help of a standard report with a search help of my own. Now I am trying to retrieve the values the user has entered into the selection screen of the report using the FM DYNP_VALUES_READ in my search help exit FM. It works fine for single values defined by PARAMETERS and for low and high values of SELECT-OPTIONS (so_example-LOW and so_example-HIGH), but I need the entire SELECT-OPTIONS table. I cannot make any changes in the report, so do you have any solutions I could implement in my search help exit FM?
Many thanks!
Vladan
P.S.
I found several questions on this topic but they either just different enough not to be applicable in my case or the formatting has made the replies useless.

Most of the time we just copy the standard FM F4IF_SHLP_EXIT_EXAMPLE to a new one and give our own name.
You can see that on the 12th line there is the following code
* EXIT immediately, if you do not want to handle this step
IF CALLCONTROL-STEP <> 'SELONE' AND
 CALLCONTROL-STEP <> 'SELECT' AND
 " AND SO ON
 CALLCONTROL-STEP <> 'DISP'.
 EXIT.
ENDIF.
you should comment those line in order for the control to reach the PRESEL step (which is already defined in the SH Exit FM) which is on line 44.
Most of the time, when someone says they don't hit PRESEL, this is the problem.
Edited by: ajithkpunnoose on Jan 5, 2012 12:00 PM

Validation of G/L account field in selection screen

Hi,
can you help me on this issue.
I have G/L account no type SAKNR as select-option as input field.
I want to validate this field with condition only G/L starting with '5' will be accepted.
how can i do this,.
Ans will be really appreciated.
Kind Regards.

hello... i think you should create a <h3>custom matchcode</h3> for the table SKA1 with an Exit Function that allows you to filter 5* accounts. This way it would works in every report or program that you need to do the same!
Enter SE11 and Create Z_SAKNR Matchcode for the table SKA1 and copy the function F4IF_SHLP_EXIT_EXAMPLE to ZFI_SHLP_EXIT_SAKNR and assign it to the matchcode
Enter SE37 and edit ZFI_SHLP_EXIT_SAKNR exit function, in the source code find:
check callcontrol-step = 'DISP'.
and code something like this:
data: listfields like dfies occurs 0 with header line.
listfields[] = shlp-fielddescr.
refresh record_tab.
select * into table LT_SKA1
from SKA1
where SAKNR LIKE '5%'
LOOP AT LT_SKA1
 READ TABLE listfields WITH KEY fieldname = 'SAKNR'.
 record_tab+listfields-offset(listfields-leng) =LT_SKA1-SAKNR.
 APPEND record_tab.
ENDLOOP.
That way youfill your Matchcode only with 5* G/L Accounts and it is rehusable in any other program or report that you need to do the same...
Edited by: Marcos Carrasco on May 31, 2010 3:19 PM

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

Steps for creation of search help exit for a search help

Hi,
I have created a search help. I need to create a search help exit for this search help.
Please let me know how to create a search help exit as well as how to link it to my search help.

1)Copy the FM F4IF_SHLP_EXIT_EXAMPLE to write your own FM. (check the documentation and coding of FM F4IF_SHLP_EXIT_EXAMPLE).
2)write your code depending upon the functionality you want.
3)attach the FM in search help through SE11 in "search help exit" field.
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.
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.
For more detailed information please refer to the documentation describing the concept of the search help exit.
The module must react with an immediate EXIT to all steps that it does not know or does not want to handle.

What is the significance of data collection nad search help exit field ?

Dear Gurus
I know i am asking very basic quetion of abap but sdn is the only source to learn sap for me.I want to thanks you all for your kind support.
i read most of the post related to search help and trying to create one.
for elementary search help.
SE11 -> SEACH HELP -> ELEMENTARY SEARCH HELP
I have doubts regarding to fields "DATA COLLECTION" and "SEARCH HELP EXIT".
reference to a tutorial it is a maintenance view shall i have to reate a maintenace view first.
and other field is SEARCH HELP EXIT what is this.
please help me .
Thanks in advance.
Chitta Ranjan mahato.
Edited by: chitto123 on Oct 8, 2010 5:59 AM

Howdy,
DATA COLLECTION - refers to a database table or view. This is the data that the search help will search through and display based on the parameters provided, so you can create your own view for the search help if you want the search to cover multiple tables.
SEARCH HELP EXIT - You can create a function module to be able to alter the Search Help's selection and results at various events throughout the search help. An example of this function module is provided with some documentation in function module F4IF_SHLP_EXIT_EXAMPLE.
Cheers
Alex

Issue in search help

Hi,
A search help which has search help exit is attached to a attribute in webdynpro.
In search help exit default values are populated.
When i click on F4, search help appears with default values coded in Fm exit. Selected one and added to personal list.
Now returned to main screen. Clicked on F4. Personalised popup displayed. Clicked on all entries(General value list). Now the defaulted values(coded in FM) are not appearing.
Could some one let me know whether any SAP note is available to fix this? I tried few. Not able to find it.
Steps to replicate.
1. Create a search help exit FM (by copying F4IF_SHLP_EXIT_EXAMPLE )
2. Write coding to default values of the screen in PRESEL method
3. Create a elementary search help and assign the created FM to it.Make this search help as Values with restriction.
4. Create webdynpro with an attribute and attach the above search help
5. Execute the webynpro. Click on F4 button. This will now show the defaulted value. Click on search and select one as personal list.
6. Close the window
7. Click on F4. Personalised search help popup will be displayed. Click on view all (General value list).
The default values wont be populated.
Regards,
GN

Did you check the screen field names & search help name? is it identical & unique?
Raja T

Applying filters to F4 Search help - how so with many entries?

Hello all,
I have a problem that I have to filter a search help for employees. We use a DB view that unions infotypes 1, 2 and 105. Now I need to restrict potential employees to a given company code BUKRS.
I now invoke search help in REQUEST ON-VALUE REQUEST within a DynPro screen and call function module F4IF_INT_TABLE_VALUE_REQUEST which I am passing the restricted internal table.
Fine, that works - however, in the DynPro (which is actually used as an EWT within our portal), the entire internal table is sent to the frontent instead of, say, 250 or so.
The search help dialog offers the possibility to manually restrict for first and last name - is it perhaps possible, that this search only applies on the server (ITAB) and just returns the results according to the user input?
Otherwise, sending all potential employees to the frontend is consuming too much resources (time and traffic).
In function group SDHI there is an "example" module F4IF_SHLP_EXIT_EXAMPLE which tries to explain how to use callbacks but from my point of view I understand very few (it misses the big picture).
Do you know an alternative, e.g. using the other module F4IF_FIELD_VALUE_REQUEST and to apply a filter to BUKRS using a callback mechanism? There are module parameters indicating that possibility (passing some report?). Perhaps one of you has some sample code, because I am much more trained in BAPI and web stuff only...
Any hints? Thank you in Advance!
Regards,
Timo

Hi,
if I can understand you, you tell me that you search information in the view and all found records (let´s say 300) are saved in the internal table, which in time you pass to function F4IF_INT_TABLE_VALUE_REQUEST for display. Now, you think it is too much to display 300 records because of time and traffic.
Try this:
REPORT ztest NO STANDARD PAGE HEADING.
TABLES mara.
DATA: mytable TYPE TABLE OF ddshretval WITH HEADER LINE.
DATA l_repid TYPE syrepid.
PARAMETERS p_mtart LIKE mara-mtart.
AT SELECTION-SCREEN ON VALUE-REQUEST
             FOR p_mtart.
l_repid = sy-repid.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
    EXPORTING
      tabname           = 'MARA'
      fieldname         = 'MTART'
      dynpprog          = l_repid
      callback_program = l_repid
      callback_form     = 'F4CALLBACK'
    TABLES
      return_tab        = mytable
    EXCEPTIONS
      field_not_found   = 1
      no_help_for_field = 2
      inconsistent_help = 3
      no_values_found   = 4
      OTHERS            = 5.
START-OF-SELECTION.
*&      Form F4_form
      Exclude all material types that start with F & H
FORM f4callback
     TABLES   record_tab STRUCTURE seahlpres
     CHANGING shlp TYPE shlp_descr
              callcontrol LIKE ddshf4ctrl.
DATA: aux_struc TYPE ddshselopt.
MOVE: 'H_T134' to aux_struc-shlpname,
        'MTART' TO aux_struc-shlpfield,
        'E'      TO aux_struc-sign,
        'CP'     TO aux_struc-option,
        'F*'     TO aux_struc-low.
append aux_struc to SHLP-SELOPT.
MOVE: 'H_T134' to aux_struc-shlpname,
        'MTART' TO aux_struc-shlpfield,
        'E'      TO aux_struc-sign,
        'CP'     TO aux_struc-option,
        'H*'     TO aux_struc-low.
append aux_struc to SHLP-SELOPT.
ENDFORM.                                                    "F4_form

How to validate a filed in a search help which is created in se11

hi
i got a requirement that validate a search help. i created a ztable with 3 fileds for that one i have to create a search help so help me to how to validate fields in a search help.
regards
krishna

Hello Krishna,
What do you mean by validating a field? Usually you use a search help to display possible values for a certain input field based on values in another table. You can restrict the values that are displayed by certain conditions if you need to.
If you want to allow only values based on complex conditions or authorizations of the user, you can always create a search help exit and in there you have complete control over what the user is allowed to see in the search help and what he is allowed to select.
Function Module F4IF_SHLP_EXIT_EXAMPLE gives you an idea what you can do in a search help exit.
Regards,
Michael

Help needed in configuring Dynamic F4

Hi All
I am trying to configure Dynamic F4 help for Actvities appln.
In Actvities Appln I have the Partners tab.In this Partner tab I have partner function and partner Id fields. When I make a search for partner Id I need to launch the search screen based on thepartner function selected.
I guess we can use dynamic F4 help but how to achieve this I am not sure. If anyone has done simliar stuff please do give your inputs.
Thanks
Regards
Senthil

Hi Senthil,
You can use Search Help Exit for your problem.
Search help exit : 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 time points 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.
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.
For more detailed information please refer to the documentation describing the concept of the search help exit.
The module must react with an immediate EXIT to all steps that it does not know or does not want to handle.
Time Points :
During the input help process, a number of time points 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 time points. If required, the search help exit can also influence the process and even determine that the process should be continued at a different time point.
The following time points are defined:
1. SELONE
Call before selecting an elementary search help. The possible elementary search helps are already in SHLP_TAB. This time point 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 time point.
The time point 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 time point 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 time point 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 time point with a search help exit. DISP should be set as the next time point.
5. DISP
Before displaying the hit list. This time point is suitable for restricting the values to be displayed, e.g. depending on authorizations.
6. RETURN (usually as return value for the next time point)
The RETURN time point 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 time point 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 time point if the input help is controlled by a collective search help. It directly follows the time point RETURN. The search help exit of the collective search help, however, is called at time point RETTOP.
8. EXIT (only for return as next time point)
The EXIT time point 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 time point 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 time points 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 time points SELONE and RETTOP. (RETTOP only if the user selects a value.) At all other time points the search help exit of the selected elementary search help is called.
If the F4 help is controlled by an elementary search help, time point RETTOP is not executed. The search help exit of the elementary search help is called at time point SELONE (at the moment). This search help exit should not do anything at this time point. Any preparatory work should be carried out at time point PRESEL1.
Steps for creating search help :
1. Run Transaction SE11
2. Give search help name
3. Click on Create
4. Make selection for Elementary or Collective search
 Help
For Elementary Search Help
5. Elementary search Help screen.
6. Give short description.
7. Dialog type specifies the data display in the hit
 list.
8. Give selection method
A] Search for database tables
B] Search for Views
9. Hot key specifies the letter or number displayed with every elementary search help.
10. Search help Exit: Specify the function module developed for the search of data for the elementary search help.
11. Search help parameter
A] Specify the input and output fields in the search help parameter column.
B] IMP column is input parameter for the search help.
C] EXP column is output parameter of the search help, to be displayed in the Hit list after selection.
D] LPos specifies the order in which fields are displayed in the hit list.
E] SPos specifies the order in which fields are displayed in the search help pop up screen.
F] Specify Data element in the field.
G] Specify the default value for any field required.
For Collective Search Help :
12. Search help exit: Specify the function module developed for the search of data for the elementary search help.
13. Search help parameter: Specify the import and export parameters.
14. Search help: Specify the elementary search help and the short text.
15. Parameter Assignment: Select the elementary search help and click on the parameter assignment. System proposes fields. User has to select the fields as per requirement, fields to be displayed in the output
hit list. Parameter assignment has to be done compulsorily for every elementary search help designed for the collective search help.
Please reward points if it helps.
Regards,
Amit Mishra

Function Module for search help Exit

How to create a function Module for search help exits?
please explain in details with step by step process.

Hi,
How to create a function Module for search help exits?
function module for search help F4IF_SHLP_EXIT_EXAMPLE
dynamic search help use 'F4IF_INT_TABLE_VALUE_REQUEST'
please check out the link below it will help you
A repository object maintained in the ABAP Dictionary. It supplies input fields on Dynpros with single- or multi-column input helps. Search helps can be linked in the Dictionary with components from structures, data elements, and check tables. A search help enables you to search for entry values with assigned data, without you having to know the exact spelling of the value.
http://help.sap.com/saphelp_46c/helpdata/EN/cf/21ee52446011d189700000e8322d00/content.htm
please explain in details with step by step process.
create a search help exit:
1. create an fm with this interface:
*" TABLES
*" SHLP_TAB TYPE SHLP_DESCR_TAB_T
*" RECORD_TAB STRUCTURE SEAHLPRES
*" CHANGING
*" VALUE(SHLP) TYPE SHLP_DESCR_T
*" VALUE(CALLCONTROL) LIKE DDSHF4CTRL STRUCTURE DDSHF4CTRL
put this logic in it:
Delete duplicate filter logic.
This logic only needs to apply at the 'DISP' event - which is just
before the hit list is displayed
if callcontrol-step = 'DISP'.
delete adjacent duplicates from record_tab.
endif.
2. edit your search help in se11 and enter the name of the above search help exit fm
check this sample code..for dynamic search help
REPORT ZTEST_F4HELP                              .
*---Report with selection screen and to display the list of
possible entries for field 'B' as per the value in field 'A'.
parameters: p_vbeln type vbak-vbeln,
            p_posnr type vbap-posnr.
at selection-screen on value-request for p_posnr.
data: begin of help_item occurs 0,
          posnr type vbap-posnr,
          matnr type vbap-matnr,
          arktx type vbap-arktx,
        end of help_item.
data: dynfields type table of dynpread with header line.
dynfields-fieldname = 'P_VBELN'.
append dynfields.
call function 'DYNP_VALUES_READ'
       exporting
            dyname               = sy-cprog
            dynumb               = sy-dynnr
            translate_to_upper   = 'X'
       tables
            dynpfields           = dynfields
       exceptions
            invalid_abapworkarea = 1
            invalid_dynprofield = 2
            invalid_dynproname   = 3
            invalid_dynpronummer = 4
            invalid_request      = 5
            no_fielddescription = 6
            invalid_parameter    = 7
            undefind_error       = 8
            double_conversion    = 9
            stepl_not_found      = 10
            others               = 11.
read table dynfields with key fieldname = 'P_VBELN'.
p_vbeln = dynfields-fieldvalue.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
       exporting
            input = p_vbeln
       importing
            output = p_vbeln.
select posnr matnr arktx into table help_item
                 from vbap
                      where vbeln = p_vbeln.
call function 'F4IF_INT_TABLE_VALUE_REQUEST'
       exporting
            retfield    = 'POSNR'
            dynprofield = 'P_POSNR'
            dynpprog    = sy-cprog
            dynpnr      = sy-dynnr
            value_org   = 'S'
       tables
            value_tab   = help_item.
also check this link it will help you
/message/3854825#3854825 [original link is broken]
*********please reward points if the information is helpful to you*************

F4IF_SHLP_EXIT_EXAMPLE

Similar Messages

Maybe you are looking for