Search Help like standard

Hi
I need to give search help for document number for a program exactly as it is there in the transaction CV04. Now in the transcation, doing F4 produces a subscreen where we may put additional fields like BOM too. After that the values are shown.
It's a module pool program where I need to do the changes. Decalring the doc number (doknr) as draw-doknr, as it is in the stadndard transaction, doesn't help.
Any ideas?
Pushpraj

Hi,
You can use Matchcode object CV01
fr ex:
Select-optiions: SO_DOCNO for draw-doknr matchcode object CV01.
Hope it helps.

Similar Messages

  • How to create an  search help for standard Screen

    Hi,
    Can any one help me out ... How to create a search help for standard screen field.......
    thanks & regards,
    Naveen...

    Hi Naveen.
    I would like to suggest a couple of references,
    [SDN - Standard Reference for create a search help for own fields in selection screen |How to create a search help for my own fields in selection screen;
    [SDN - Standard Reference for Attaching search help to standard screen|Attach search help to standard screen;
    [SDN - Reference for want to add a field in standard search help screen|want to add a field in standard search help screen;
    [SDN - Reference for Attaching a search help to a standard screen - Case 2 |attaching a search help to a standard screen;
    Hope that's usefull.
    Good Luck & Regards.
    Harsh Dave

  • 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

  • How to change search help for standard field in me51n.

    hi frnds,
              I want to change search help option for 'Advice code' field under Additional DFPS tab in me51n. But i dont know how to change or add search help for standard field. so plz help..
    best regards,
    sudip biswas

    Hi Abhi,
    Try using any one option:
    Create a Search Help in SE11.
    Now Goto SE11 -> Enter Ztable -> Select that field -> Click Search Help and try to assign the created Search help to that field in your Ztable explicitly
    OR
    Create a Zdata element in SE11.
    In Data Element, under Further Characteristics tab, enter Name  Parameters of Search Help.
    Assign this data element to that field in ur Ztable.
    OR
    Create a Zdomain and maintain a Value Table or Fixed Values for it.
    Assign this domain to that field in ur Ztable.

  • Search help like tree structure.

    Hi All,
    I have a requirement to display the F4 search help like a tree structure  , with  different
    Node(category fields ), under each node(category fields ) different work centers  will exist.
    Please suggest how I can achieve the tree format categories in search help.
    Thanks for your cooperation.
    Thanks,
    Sri.

    Hi Sri,
    U can have a look at the search help PRCTH in se11, which has an search help exit K_F4IF_SHLP_STANDARD_HIERARCHY
    just execute this and try to debugg it...
    Hope this solves your problem...
    please ack if helpful .
    Best of luck !
    Thanks,
    Ravi Aswani
    Edited by: Ravi Aswani on Mar 15, 2010 8:45 AM

  • How to add search help for standard field LIKP-TRAID

    Hi friends,
    How to add search help for standard field LIKP-TRAID ,
    refer screen
    Program Name       SAPMV50A  
    Screen Number      2108      
    TrnsIDCode ( LIKP-TRAID ) ..
    I need to add a search help, so that i can retrieve data from Ztable.
    Thanks.
    Abhi

    Hi Abhi,
    Try using any one option:
    Create a Search Help in SE11.
    Now Goto SE11 -> Enter Ztable -> Select that field -> Click Search Help and try to assign the created Search help to that field in your Ztable explicitly
    OR
    Create a Zdata element in SE11.
    In Data Element, under Further Characteristics tab, enter Name  Parameters of Search Help.
    Assign this data element to that field in ur Ztable.
    OR
    Create a Zdomain and maintain a Value Table or Fixed Values for it.
    Assign this domain to that field in ur Ztable.

  • 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

  • Attach search help to standard screen

    Hi Gurus,
    I have to populate order quantity KWMENG in screen subscreen 4900 of VA01 ( Create Sales Order) from a ztable based on customer and date.
    I have tried customer-exits ..<b>There exists none</b> satisfying this req. Could anyone pls tell how I can go about this now?
    I believe , one way is to create a search help attaching to the screen-field . Can anyone help what is the process ? Has anyone done this earlier -<b>attaching search help to standard screen</b>
    Rewards for helpful answers are sure!!
    Regards,
    Shweta

    Hi Shweta,
    Check this matter.
    There are 3 ways:
    1)In the PAI of the screen, add a module Process on value request.For example:
    PROCESS AFTER INPUT.
    MODULE USER_COMMAND_100.
    PROCESS ON VALUE-REQUEST.
    FIELD field_name MODULE value_request_for_field_name.
    *field_name is the field for which you require search help.
    In the Module value_request_for_field_name call this function 'F4IF_INT_TABLE_VALUE_REQUEST'.
    2)The above procedure can be used if the field you have defined doesnt have an existing search help.If it already has search help and the field in the screen is taken from the dictionary,then in the attributes,u can check from from dictionary under the dictionary tab.
    3)A manual search help can also be created in the se11 transaction by clicking on the search help radio button and giving the table and field name for which search help is required.
    Hope this resolves your query.
    Reward all the helpful answers.
    Regards

  • Add search help to standard field in shopping cart

    Hi Experts,
    We are on a SRM 5.0 implementation for classic scenario.
    In the item basic details we have a field tracking number. (BE_TRACKING_NO). We have a requirement to add a search help (drop down with fixed values) to this field. Is this possible to do on a standard way? The fixed values we will need to get from the attributes the user has assigned.
    Regards,
    Tom

    it needs to be done from backend
    you can customise the field to appear from the backend in the portal, and then add a code like  a normal field has to build
    a help
    check ptarQ>customising > additional fields

  • Adding search help to standard SAP field

    Hi Experts,
    I need to add search help to field ZUONR i.e assignment field in various tcode like fb70,fb60,f-02.etc which will select data from
    Z tables . I have found out serach help exit F4IF_SHLP_EXIT_EXAMPLE but as per my knowledge that is to change existing standard search help.But to field ZUONR there is no search help attached.How can new Z search help be added to field ZUONR without use of access key.
    Please suggest.
    Regards,
    Kaustubh Kabre.

    Hi,
    I don't know how to change "Value table" field on domain without access key, but if nothing else work, you can add new fixed values. From menu Goto->fixed value append.
    Other possibility is to use GuiXT -> write script that will call your FM that will get data from your table and show them.
    Best regards
    Marcin Cholewczuk

  • Custom  search help on standard field of PO Item

    Hi all,
    any one know a way to build a custom search help on field EKPO-AFNAM in transaction ME21n,ME22N?
    I'd prefer don't change the standard data element adding the search help. Is there a standard way, like badi or user exit?
    I'm using ECC 6.0
    Regards,
    enzo

    Check all Ewxits
    Transaction Code - ME21N                    Create Purchase Order
    Exit Name           Description
    LMEDR001            Enhancements to print program
    LMELA002            Adopt batch no. from shipping notification when posting a GR
    LMELA010            Inbound shipping notification: Transfer item data from IDOC
    LMEQR001            User exit for source determination
    LMEXF001            Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001            Customer-Specific Source Determination in Retail
    M06B0001            Role determination for purchase requisition release
    M06B0002            Changes to comm. structure for purchase requisition release
    M06B0003            Number range and document number
    M06B0004            Number range and document number
    M06B0005            Changes to comm. structure for overall release of requisn.
    M06E0004            Changes to communication structure for release purch. doc.
    M06E0005            Role determination for release of purchasing documents
    ME590001            Grouping of requsitions for PO split in ME59
    MEETA001            Define schedule line type (backlog, immed. req., preview)
    MEFLD004            Determine earliest delivery date f. check w. GR (only PO)
    MELAB001            Gen. forecast delivery schedules: Transfer schedule implem.
    MEQUERY1            Enhancement to Document Overview ME21N/ME51N
    MEVME001            WE default quantity calc. and over/ underdelivery tolerance
    MM06E001            User exits for EDI inbound and outbound purchasing documents
    MM06E003            Number range and document number
    MM06E004            Control import data screens in purchase order
    MM06E005            Customer fields in purchasing document
    MM06E007            Change document for requisitions upon conversion into PO
    MM06E008            Monitoring of contr. target value in case of release orders
    MM06E009            Relevant texts for "Texts exist" indicator
    MM06E010            Field selection for vendor address
    MMAL0001            ALE source list distribution: Outbound processing
    MMAL0002            ALE source list distribution: Inbound processing
    MMAL0003            ALE purcasing info record distribution: Outbound processing
    MMAL0004            ALE purchasing info record distribution: Inbound processing
    MMDA0001            Default delivery addresses
    MMFAB001            User exit for generation of release order
    MRFLB001            Control Items for Contract Release Order
    AMPL0001            User subscreen for additional data on AMPL
    No of Exits:         35
    Transaction Code - ME22N                    Change Purchase Order
    Exit Name           Description
    LMEDR001            Enhancements to print program
    LMELA002            Adopt batch no. from shipping notification when posting a GR
    LMELA010            Inbound shipping notification: Transfer item data from IDOC
    LMEQR001            User exit for source determination
    LMEXF001            Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001            Customer-Specific Source Determination in Retail
    M06B0001            Role determination for purchase requisition release
    M06B0002            Changes to comm. structure for purchase requisition release
    M06B0003            Number range and document number
    M06B0004            Number range and document number
    M06B0005            Changes to comm. structure for overall release of requisn.
    M06E0004            Changes to communication structure for release purch. doc.
    M06E0005            Role determination for release of purchasing documents
    ME590001            Grouping of requsitions for PO split in ME59
    MEETA001            Define schedule line type (backlog, immed. req., preview)
    MEFLD004            Determine earliest delivery date f. check w. GR (only PO)
    MELAB001            Gen. forecast delivery schedules: Transfer schedule implem.
    MEQUERY1            Enhancement to Document Overview ME21N/ME51N
    MEVME001            WE default quantity calc. and over/ underdelivery tolerance
    MM06E001            User exits for EDI inbound and outbound purchasing documents
    MM06E003            Number range and document number
    MM06E004            Control import data screens in purchase order
    MM06E005            Customer fields in purchasing document
    MM06E007            Change document for requisitions upon conversion into PO
    MM06E008            Monitoring of contr. target value in case of release orders
    MM06E009            Relevant texts for "Texts exist" indicator
    MM06E010            Field selection for vendor address
    MMAL0001            ALE source list distribution: Outbound processing
    MMAL0002            ALE source list distribution: Inbound processing
    MMAL0003            ALE purcasing info record distribution: Outbound processing
    MMAL0004            ALE purchasing info record distribution: Inbound processing
    MMDA0001            Default delivery addresses
    MMFAB001            User exit for generation of release order
    MRFLB001            Control Items for Contract Release Order
    AMPL0001            User subscreen for additional data on AMPL
    No of Exits:         35
    Rewards if useful....................
    Minal

  • Custom search help over standard search help

    Hello all,
    i made a selection screen with some standard fields and it is shoeing F4 as well, but now problem is that now i want to display customized search help, means wants to add our data in F4, can anyone please help me?
    i m doing below code but it is showing nothing, neither standard one nor customized one.
    code:
    SELECT-OPTIONS: so_mesty FOR edidc-mestyp.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR so_mesty-low.
      PERFORM f4_help.
    FORM F4_HELP .
    TYPES : BEGIN OF gst_stat,
            ZZVALUE like ZCS_PARAM-ZZVALUE,
            ZZPARADES like zcs_param-ZZPARADES,
      END OF gst_stat.
      data : lt_stat TYPE TABLE OF gst_stat.
    CONSTANTS: gc_obj(7) type c value 'MMR0320',
                gc_par(6) type c value 'MTYP*'.
       refresh lt_stat.
      select zzvalue ZZPARADES from ZCS_PARAm into table lt_stat where ZZOBJECT = gc_obj and ZZPARANAME = gc_par.
      if lt_stat[] is not initial.
        CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
          EXPORTING
            RETFIELD        = 'ZZVALUE'
            DYNPPROG        = sy-repid
            DYNPNR          = sy-dynnr
            DYNPROFIELD     = 'SO_MESTY-LOW'
            VALUE_ORG       = 'S'
          TABLES
            VALUE_TAB       = lt_stat
          EXCEPTIONS
            PARAMETER_ERROR = 1
            NO_VALUES_FOUND = 2
            OTHERS          = 3.
        IF SY-SUBRC <> 0.
          MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                  WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
      endif.
    ENDFORM.                    " F4_HELP
    Regards.

    Hi,
    You can try doing like:
    On At Selection Screen on value-request for Fieldname.
    First select the data from your multiple table and populate
    one final table then that final internal table needs to be passed
    in FM:
    For Eg:
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_CLASCN-LOW.
    *F4 help for material classification data
      PERFORM F4_HELP_CLASIFC USING S_CLASCN-LOW.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_CLASCN-HIGH.
    *F4 help for material classification data
      PERFORM F4_HELP_CLASIFC USING S_CLASCN-HIGH.
    *&      Form  F4_HELP_CLASIFC
    *       text
    *      -->P_S_CLASCN_LOW  text
    FORM F4_HELP_CLASIFC  USING    P_S_CLASCN_LOW.
    *To fetch the classification data on the sel screen
      SELECT CLINT CLASS FROM KLAH UP TO 500 ROWS
      INTO TABLE IT_KLAH.
      IF SY-SUBRC <> 0 .
        MESSAGE TEXT-006 TYPE 'E'.
      ELSE.
        CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
        EXPORTING
    * DDIC_STRUCTURE = ' '
        RETFIELD = 'CLASS'    "Field name on which custom F4 is required
    * PVALKEY = ' '
        DYNPPROG = SY-REPID
        DYNPNR = SY-DYNNR
        DYNPROFIELD = 'p_s_clascn_low'
        VALUE_ORG = 'S'
        DISPLAY = ' '
        TABLES
        VALUE_TAB = IT_KLAH.   "Final Internal table
      ENDIF.
    ENDFORM.                    " F4_HELP_CLASIFC
    Hope it helps
    Regards
    Mansi

  • Enhancing F4 Search Help Issue - Standard Component

    Hello All,
    We have a requirement in SRM to customize couple of standard Search helps attached to the Webdynpro components. As such I know the concept of how we can handle this requirement but hitting an issue.
    Standard Working scenario -
    1) Standard Structure available with multiple fields. Two fields that are of our interest are SH_VALUE and SH_VALUE_LABEL.
    2) Standard Search help for this being used has fields VALUE and VALUE_LABEL.
    3) In the Structure the both the fields SH_VALUE and SH_VALUE_LABEL are mapped to the Search help VALUE and VALUE_LABEL.
    4) In the WD component the node is mapped to the standard structure.
    Running the application and the picking up the values from F4 on the SH_VALUE field will return its corresponding value and also map the SH_VALUE_LABEL field with the Label from the F4 since the structure and Search help mapping are there.
    So far good when its standard.
    Issue I am facing -
    We need to modify this standard search help to customize our needs.
    1) Did a Copy of the standard Search help and then modified to suit our needs. The output structure of the search is still the same as the standard one.
    2) Did a Post Exit in the WD component to call our custom search help through the below code -
    data lo_nd_attrib type ref to if_wd_context_node.
    data lo_nd_attrib_info type ref to if_wd_context_node_info.
    lo_nd_attrib = wd_context->path_get_node( path = `ATTRIBUTES_DATA.ATTR_DTLS_MULT` ).
    lo_nd_attrib_info = lo_nd_attrib->get_node_info( ).
    lo_nd_attrib_info->set_attribute_value_help( name = 'SH_VALUE' value_help_mode = '121' value_help = 'Z_ORG_ATTR' ).
    lo_nd_attrib_info->set_attribute_value_help( name = 'SH_VALUE_LABEL' value_help_mode = '121' value_help = 'Z_ORG_ATTR' ).
    Running the application just returns the SH_VALUE field but does not get the data for the SH_VALUE_LABEL.
    Is there something wrong in the way I am calling the Custom Search help or should I need to approach this differently?
    Thanks,
    Nagarajan.

    Hi Nagarajan,
    Well, you are trying to set the search help to both attributes ( sh_value, sh_value_label) individually and it is having no link between these two attributes
    i.e. once you select a value from search help of SH_VALUE, its no where linked that the other details to be passed to SH_VALUE_LABEL.
    We generally, do the linking of attributes to search help parameters at structure level as below
    So, if you need the same behaviour, then you need to assign the Zsearch help at strucuture field SH_VALUE and link the parameters to both fields SH_VALUE & SH_VALUE_LABEL
    In case, if find it not possible to to this way,
    You need to populate the value of field SH_VALUE_LABEL upon selection of value from search help of SH_VALUE.
    i.e. by registering the search help selection event to an OnEnter action and write the logic to populate the value to SH_VALUE_LABEL
    Please refer the below link
    Automatically Trigger onEnter event after selecting value from the Value Help(F4 Help)
    Hope this helps you.
    Regards,
    Rama

  • Re: Search Help for Standard field in a Standard Component

    Dear Experts
    i enhanced  a standard screen with one inputfield and mapped a context attribute(The attribute is also standard one which doesnot have search help) my requirement is to assign a search help to the context attribute so that at runtime the user can click on the search help and the value will be passed to backend for processing.
    i tried it with dynamic programmin but im getting null access error,
    Experts please guide me to set a dynamic search help to the standard context attribute.
    Regards
    Arun.K.P

    Hi Friends,
    I solved the issue this is the solution
    DATA lo_nd_location_data TYPE REF TO if_wd_context_node.
    navigate from <CONTEXT> to <ACCOUNT_DETAIL> via lead selection
    lo_nd_location_data = wd_context->path_get_node( path = `LOCATION_DATA` ).
    lo_nd_location_data = wd_context->get_child_node( name = wd_this->wdctx_location_data ).
      DATA lr_node_info TYPE REF TO if_wd_context_node_info.
      lr_node_info = lo_nd_location_data->get_node_info( ).
      CALL METHOD lr_node_info->set_attribute_value_help
        EXPORTING
          name            = `COMPANY_CODE`
          value_help_mode = lr_node_info->C_VALUE_HELP_MODE-DDIC
          value_help      = 'BBP_LOCATION_VALUE'.
    Best Regards
    Arun.K.P

  • SEARCH HELP FOR STANDARD SAP DATA ELEMENT AFNAM

    Hello All,
    Is there any possibility for adding a search help for the standard SAP field AFNAM.
    Thanks in Advance!
    Ashish

    Hi Ashish,
    You can APPEND your own search help to an SAP field that has search help defined. This is similar to APPENDing fields to an SAP table.
    You can also attach the search help to a field on a screen, i.e. limit the scope to that single screen, but this would still require a modification to the system, and hence, an access key.
    Hence if you want to attach search help to the standard SAP field, then you will need access key for that.
    If the access key will be available then you can attach your search help to the standard SAP field.
    For more reference go through the link :
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/3d/e53642e2a3ab04e10000000a1550b0/frameset.htm
    Thanks,
    Nitesh Jain

Maybe you are looking for