Search help for posting key

Hi ,
Please help me to find search help for posting key (NEWBS).
I tried BSCHL. But it is not working.
Thanks,
Sandeep Garg

Hi,
Create the search help with table entires from
TBSL this is a value table.
Or
use the FM to have a search help for this field.
AT selection screen on value-request for <<FIEDLNAME>>
F4IF_INT_TABLE_VALUE_REQUEST'
*CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
DDIC_STRUCTURE         = 'FVALUETAB-CARRID'
   retfield               = t_connid
PVALKEY                = ' '
DYNPPROG               = 'W_REPID'
DYNPNR                 = 'W_DYNNR'
DYNPROFIELD            = 'W_FIELD'
STEPL                  = 0
WINDOW_TITLE           =
VALUE                  = 'W_VALUE'
VALUE_ORG              = 'C'
MULTIPLE_CHOICE        = ' '
DISPLAY                = ' '
CALLBACK_PROGRAM       = 'SY-CPROG'
CALLBACK_FORM          = ' '
MARK_TAB               =
IMPORTING
USER_RESET             =
tables
   value_tab              = T_VALUE1
FIELD_TAB              = w_ftab
RETURN_TAB             =
DYNPFLD_MAPPING        = w_ftab
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.
Thanks & Regards,
Chandralekha.

Similar Messages

How to disable search help for material key?

Hi Expert,
I have a input field of matarial number in the screen, and the search help is always shown with the field although I do not want it.
I want the customer to enter the material number manually without using the search help.
What should I do
Thanks for your time,
Anna

Anna,
set the input help mode property to Deactivated of the context attribute associated with input field
Thanks
Bala Duvvuri

Search help for selection screen field

Hi ,
steps for creating search help for a key field in selection screen..
tables is a userdefined from which the field is taken..
thxs,
vind

hi,
c this.
REPORT ZXYZ_0002 .
data: dynfields type table of dynpread with header line.
data: return type table of ddshretval with header line.
selection-screen begin of block b1 with frame title text-001 .
selection-screen begin of line.
PARAMETERS: P_BUKRS type T001-BUKRS.
selection-screen comment 30(20) BUTXT for field p_bukrs.
selection-screen end of line.
selection-screen end of block b1.
at selection-screen output.
if butxt is initial.
   select single butxt into butxt
         from t001
        where bukrs = p_bukrs.
endif.
at selection-screen on value-request for p_bukrs.
call function 'F4IF_FIELD_VALUE_REQUEST'
       exporting
            tabname           = 'T001'
            fieldname         = 'BUKRS'
            dynpprog          = sy-cprog
            dynpnr            = sy-dynnr
            dynprofield       = 'P_BUKRS'
       tables
            return_tab        = return
       exceptions
            field_not_found   = 1
            no_help_for_field = 2
            inconsistent_help = 3
            no_values_found   = 4
            others            = 5.
read table return with key fieldname = 'P_BUKRS'.
Add it back to the dynpro.
dynfields-fieldname = return-retfield.
dynfields-fieldvalue = return-fieldval.
append dynfields.
Get the company code from db and add to dynpro
data: xt001 type t001.
clear xt001.
select single * into xt001
         from t001
        where bukrs = return-fieldval.
dynfields-fieldname = 'BUTXT'.
dynfields-fieldvalue = xt001-butxt.
append dynfields.
Update the dynpro values.
call function 'DYNP_VALUES_UPDATE'
       exporting
            dyname     = sy-cprog
            dynumb     = sy-dynnr
       tables
            dynpfields = dynfields
       exceptions
            others     = 8.
start-of-selection.
rgsds
anver
if hlped mark points

How to create Search Help for a field in Table control !!

Hello Friends,
              I like to know - How to create Search Help for a field in Table control. Is it possible, if it is please share ur knowledge, I wud be happy if U provide some source code example for this.
Thanks,
Senthil

Check the sample code:
*& Include           ZSRO_MPRN_SEARCH                                 *
MODULE PSTLZ_F4 INPUT
MODULE pstlz_f4 INPUT.
reading post code
DATA: stepl TYPE systepl,
        stepl_index TYPE systepl.
CLEAR: stepl, stepl_index.
CLEAR:   lt_returntab,lt_dynpfields,i_mprn1.
REFRESH: lt_returntab,lt_dynpfields,i_mprn1.
lt_dynpfields-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields-stepl     = stepl.
APPEND lt_dynpfields. CLEAR lt_dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = c_x
      determine_loop_index = c_x
    TABLES
      dynpfields           = lt_dynpfields
    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.
IF sy-subrc EQ 0.
    READ TABLE lt_dynpfields INDEX 1.
ENDIF.
ws_outcode = lt_dynpfields-fieldvalue.
stepl_index = lt_dynpfields-stepl.
REPLACE '*' WITH ' ' INTO lt_dynpfields-fieldvalue.
IF NOT lt_dynpfields-fieldvalue IS INITIAL.
    MOVE lt_dynpfields-fieldvalue TO ws_outcode.
    ws_len = STRLEN( lt_dynpfields-fieldvalue ).
    IF ws_len GE 7.
      ws_len = ws_len - 3.
     ws_icode = ws_code+ws_len(3).
      lt_dynpfields-fieldvalue = lt_dynpfields-fieldvalue+0(ws_len).
      CONCATENATE lt_dynpfields-fieldvalue '%'
          INTO ws_outcode.
      CONDENSE lt_dynpfields-fieldvalue.
   REPLACE ws_icode WITH ' ' INTO lt_dynpfields-fieldvalue.
    ELSE.
      CONCATENATE lt_dynpfields-fieldvalue+0(4) '%'
        INTO ws_outcode.
    ENDIF.
   ws_ocode = ws_code+0(3).
ENDIF.
reading MPRN
CLEAR:   lt_returntab,lt_dnpfields,i_mprn1.
REFRESH: lt_returntab,lt_dnpfields,i_mprn1.
lt_dnpfields-fieldname = 'I_MPRN-MPRN'.
lt_dnpfields-stepl     = stepl_index.
APPEND lt_dnpfields. CLEAR lt_dnpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = 'X'
    TABLES
      dynpfields           = lt_dnpfields
    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.
IF sy-subrc EQ 0.
    READ TABLE lt_dnpfields INDEX 1.
ENDIF.
MPRN blank and Post code exist
IF lt_dnpfields-fieldvalue IS INITIAL.
    IF NOT lt_dynpfields-fieldvalue IS INITIAL.
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE outcode LIKE ws_outcode.
    ELSE.
MPRN blank and Post code blank
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1.
    ENDIF.
ELSE.
MPRN exist and Post code exist
    IF NOT lt_dynpfields-fieldvalue IS INITIAL.
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE outcode LIKE ws_outcode AND
                   mprn EQ lt_dnpfields-fieldvalue.
    ELSE.
MPRN exist and Post code blank
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE mprn EQ lt_dnpfields-fieldvalue.
    ENDIF.
ENDIF.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield        = 'MPRN'
      dynpprog        = sy-repid
      dynpnr          = sy-dynnr
      window_title    = 'Select MPRN'
      value_org       = 'S'
    TABLES
      value_tab       = i_mprn1 "lt_mprn
      return_tab      = lt_returntab
    EXCEPTIONS
      parameter_error = 1
      no_values_found = 2
      OTHERS          = 3.
IF sy-subrc EQ 0.
    READ TABLE lt_returntab INDEX 1.
    READ TABLE i_mprn1 WITH KEY mprn = lt_returntab-fieldval.
    IF sy-subrc EQ 0.
Updating post code
      CONCATENATE i_mprn1-outcode i_mprn1-incode
                    INTO ws_postcode
                         SEPARATED BY space.
      MOVE ws_postcode TO i_mprn-post_code.
      CLEAR   : i_dnpfld,
                ws_dynpfld.
      REFRESH : i_dnpfld.
      ws_dyname   = 'ZSRO_MASTER_DATA'.
      ws_dynumb   = '0301'.
      ws_dynpfld-fieldname ='I_MPRN-POST_CODE'.
      ws_dynpfld-fieldvalue = ws_postcode .
      ws_dynpfld-stepl      = stepl_index.
      APPEND ws_dynpfld TO i_dnpfld.
      CALL FUNCTION 'DYNP_VALUES_UPDATE'
        EXPORTING
          dyname               = ws_dyname
          dynumb               = ws_dynumb
        TABLES
          dynpfields           = i_dnpfld
        EXCEPTIONS
          invalid_abapworkarea = 1
          invalid_dynprofield = 2
          invalid_dynproname   = 3
          invalid_dynpronummer = 4
          invalid_request      = 5
          no_fielddescription = 6
          undefind_error       = 7
          OTHERS               = 8.
      IF sy-subrc <> 0.
      ENDIF.
Updating MPRN
      MOVE i_mprn1-mprn TO i_mprn-mprn.
      CLEAR   : i_dnpfld,
                ws_dynpfld.
      REFRESH : i_dnpfld.
      ws_dyname   = 'ZSRO_MASTER_DATA'.
      ws_dynumb   = '0301'.
      ws_dynpfld-fieldname ='I_MPRN-MPRN'.
      ws_dynpfld-fieldvalue = i_mprn1-mprn .
      ws_dynpfld-stepl      = stepl_index.
      APPEND ws_dynpfld TO i_dnpfld.
      CALL FUNCTION 'DYNP_VALUES_UPDATE'
        EXPORTING
          dyname               = ws_dyname
          dynumb               = ws_dynumb
        TABLES
          dynpfields           = i_dnpfld
        EXCEPTIONS
          invalid_abapworkarea = 1
          invalid_dynprofield = 2
          invalid_dynproname   = 3
          invalid_dynpronummer = 4
          invalid_request      = 5
          no_fielddescription = 6
          undefind_error       = 7
          OTHERS               = 8.
      IF sy-subrc <> 0.
      ENDIF.
    ENDIF.
ELSEIF sy-subrc EQ 2.
    MESSAGE s005(zspa) WITH ws_postcode .
ENDIF.
ENDMODULE.                    "PSTLZ_F4 INPUT
MODULE MPRN_F4 INPUT
MODULE mprn_f4 INPUT.
reading post code
DATA: stepl TYPE systepl,
       stepl_index TYPE systepl.
CLEAR: stepl, stepl_index.
CLEAR:   lt_returntab,lt_dynpfields,i_mprn1.
REFRESH: lt_returntab,lt_dynpfields,i_mprn1.
lt_dynpfields-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields-stepl     = stepl.
APPEND lt_dynpfields. CLEAR lt_dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = c_x
      determine_loop_index = c_x
    TABLES
      dynpfields           = lt_dynpfields
    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.
IF sy-subrc EQ 0.
    READ TABLE lt_dynpfields INDEX 1.
ENDIF.
ws_outcode = lt_dynpfields-fieldvalue.
stepl_index = lt_dynpfields-stepl.
REPLACE '*' WITH ' ' INTO lt_dynpfields-fieldvalue.
IF NOT lt_dynpfields-fieldvalue IS INITIAL.
    MOVE lt_dynpfields-fieldvalue TO ws_outcode.
    ws_len = STRLEN( lt_dynpfields-fieldvalue ).
    IF ws_len GE 7.
      ws_len = ws_len - 3.
     ws_icode = ws_code+ws_len(3).
      lt_dynpfields-fieldvalue = lt_dynpfields-fieldvalue+0(ws_len).
      CONCATENATE lt_dynpfields-fieldvalue '%'
          INTO ws_outcode.
      CONDENSE lt_dynpfields-fieldvalue.
   REPLACE ws_icode WITH ' ' INTO lt_dynpfields-fieldvalue.
    ELSE.
      CONCATENATE lt_dynpfields-fieldvalue+0(4) '%'
        INTO ws_outcode.
    ENDIF.
   ws_ocode = ws_code+0(3).
ENDIF.
reading MPRN
CLEAR:   lt_returntab,lt_dnpfields,i_mprn1.
REFRESH: lt_returntab,lt_dnpfields,i_mprn1.
lt_dnpfields-fieldname = 'I_MPRN-MPRN'.
lt_dnpfields-stepl     = stepl_index.
APPEND lt_dnpfields. CLEAR lt_dnpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = 'X'
    TABLES
      dynpfields           = lt_dnpfields
    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.
IF sy-subrc EQ 0.
    READ TABLE lt_dnpfields INDEX 1.
ENDIF.
MPRN blank and Post code exist
IF lt_dnpfields-fieldvalue IS INITIAL.
    IF NOT lt_dynpfields-fieldvalue IS INITIAL.
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE outcode LIKE ws_outcode.
    ELSE.
MPRN blank and Post code blank
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1.
    ENDIF.
ELSE.
MPRN exist and Post code exist
    IF NOT lt_dynpfields-fieldvalue IS INITIAL.
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE outcode LIKE ws_outcode AND
                   mprn EQ lt_dnpfields-fieldvalue.
    ELSE.
MPRN exist and Post code blank
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE mprn EQ lt_dnpfields-fieldvalue.
    ENDIF.
ENDIF.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield        = 'MPRN'
      dynpprog        = sy-repid
      dynpnr          = sy-dynnr
      window_title    = 'Select MPRN'
      value_org       = 'S'
    TABLES
      value_tab       = i_mprn1 "lt_mprn
      return_tab      = lt_returntab
    EXCEPTIONS
      parameter_error = 1
      no_values_found = 2
      OTHERS          = 3.
IF sy-subrc EQ 0.
    READ TABLE lt_returntab INDEX 1.
    READ TABLE i_mprn1 WITH KEY mprn = lt_returntab-fieldval.
    IF sy-subrc EQ 0.
Updating MPRN
      MOVE i_mprn1-mprn TO i_mprn-mprn.
      CLEAR   : i_dnpfld,
                ws_dynpfld.
      REFRESH : i_dnpfld.
      ws_dyname   = 'ZSRO_MASTER_DATA'.
      ws_dynumb   = '0301'.
      ws_dynpfld-fieldname ='I_MPRN-MPRN'.
      ws_dynpfld-fieldvalue = i_mprn1-mprn .
      ws_dynpfld-stepl      = stepl_index.
      APPEND ws_dynpfld TO i_dnpfld.
**code changed by laxman 10.08.2005
     ws_dynpfld-stepl = mprn-current_line.
**code changed by laxman 10.08.2005
      CALL FUNCTION 'DYNP_VALUES_UPDATE'
        EXPORTING
          dyname               = ws_dyname
          dynumb               = ws_dynumb
        TABLES
          dynpfields           = i_dnpfld
        EXCEPTIONS
          invalid_abapworkarea = 1
          invalid_dynprofield = 2
          invalid_dynproname   = 3
          invalid_dynpronummer = 4
          invalid_request      = 5
          no_fielddescription = 6
          undefind_error       = 7
          OTHERS               = 8.
      IF sy-subrc <> 0.
      ENDIF.
Updating post code
      CONCATENATE i_mprn1-outcode i_mprn1-incode
                    INTO ws_postcode
                         SEPARATED BY space.
      MOVE ws_postcode TO i_mprn-post_code.
      CLEAR   : i_dnpfld,
                ws_dynpfld.
      REFRESH : i_dnpfld.
      ws_dyname   = 'ZSRO_MASTER_DATA'.
      ws_dynumb   = '0301'.
      ws_dynpfld-fieldname ='I_MPRN-POST_CODE'.
      ws_dynpfld-fieldvalue = ws_postcode .
      ws_dynpfld-stepl      = stepl_index.
      APPEND ws_dynpfld TO i_dnpfld.
**code changed by laxman 10.08.2005
     break gblap0.
     ws_dynpfld-stepl = mprn-current_line.
     LOOP AT i_mprn.
       MOVE i_mprn1-mprn TO i_mprn-mprn.
       MOVE ws_postcode TO i_mprn-post_code.
       MODIFY i_mprn INDEX
                mprn-current_line." transporting MPRN POST_CODE.
     ENDLOOP.
**code changed by laxman 10.08.2005
      CALL FUNCTION 'DYNP_VALUES_UPDATE'
        EXPORTING
          dyname               = ws_dyname
          dynumb               = ws_dynumb
        TABLES
          dynpfields           = i_dnpfld
        EXCEPTIONS
          invalid_abapworkarea = 1
          invalid_dynprofield = 2
          invalid_dynproname   = 3
          invalid_dynpronummer = 4
          invalid_request      = 5
          no_fielddescription = 6
          undefind_error       = 7
          OTHERS               = 8.
      IF sy-subrc <> 0.
      ENDIF.
    ENDIF.
ELSEIF sy-subrc EQ 2.
    MESSAGE s006(zspa) WITH i_mprn1-mprn .
ENDIF.
ENDMODULE.                    "MPRN_F4 INPUT
MODULE GNTC_F4 INPUT
MODULE gntc_f4 INPUT.
DATA: BEGIN OF lt_gntc OCCURS 0,
          gntc LIKE iflot-zzgntc,
        END OF lt_gntc.
CLEAR:   lt_returntab, lt_gntc.
REFRESH: lt_returntab, lt_gntc.
lt_gntc-gntc = 'DM'.
APPEND lt_gntc. CLEAR lt_gntc.
lt_gntc-gntc = 'NDM'.
APPEND lt_gntc. CLEAR lt_gntc.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield        = 'ZZGNTC'
      dynpprog        = sy-repid
      dynpnr          = sy-dynnr
      window_title    = 'Select Gas Nomination Type Code'
      value_org       = 'S'
    TABLES
      value_tab       = lt_gntc
      return_tab      = lt_returntab
    EXCEPTIONS
      parameter_error = 1
      no_values_found = 2
      OTHERS          = 3.
IF sy-subrc EQ 0.
    READ TABLE lt_returntab INDEX 1.
    i_mprn-dm_ndm = lt_returntab-fieldval.
ENDIF.
ENDMODULE.                    "GNTC_F4 INPUT
*&      Module mprn1_f4 INPUT
      text
MODULE mprn1_f4 INPUT.
DATA: lt_f4          TYPE ddshretval OCCURS 0 WITH HEADER LINE,
        lt_returntab1 LIKE ddshretval OCCURS 0 WITH HEADER LINE,
        lt_dynpfields1 LIKE dynpread OCCURS 0 WITH HEADER LINE,
        lt_dnpfields1 LIKE dynpread OCCURS 0 WITH HEADER LINE.
DATA: stepl1 TYPE systepl,
        stepl_index1 TYPE systepl.
DATA : i_dnpfld1      LIKE dynpread OCCURS 0 WITH HEADER LINE,
         ws_dyname1     LIKE d020s-prog,
         ws_dynumb1     LIKE d020s-dnum,
         ws_dynpfld1    LIKE dynpread.
CLEAR: i_dnpfld1, ws_dyname1, ws_dynumb1, ws_dynpfld1,
         lt_f4, lt_returntab1,lt_dynpfields1, lt_f4,
         stepl1, stepl_index1.
REFRESH: i_dnpfld1, lt_returntab1,lt_dynpfields1, lt_f4.
To Determine Steploop Index
lt_dynpfields1-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields1-stepl     = stepl1.
APPEND lt_dynpfields1. CLEAR lt_dynpfields1.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = 'X'
      determine_loop_index = 'X'
    TABLES
      dynpfields           = lt_dynpfields1
    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.
IF sy-subrc EQ 0.
    READ TABLE lt_dynpfields1 INDEX 1.
ENDIF.
stepl_index1 = lt_dynpfields1-stepl.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
    EXPORTING
      tabname           = 'IFLOT'
      fieldname         = 'I_MPRN-MPRN'
      searchhelp        = 'ZS_MPRN_PC'
      dynpprog          = sy-repid
      dynpnr            = sy-dynnr
    TABLES
      return_tab        = lt_f4
    EXCEPTIONS
      field_not_found   = 1
      no_help_for_field = 2
      inconsistent_help = 3
      no_values_found   = 4
      OTHERS            = 5.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Update tablecontrol
READ TABLE lt_f4 WITH KEY fieldname = 'MPRN'.
IF sy-subrc = 0.
    MOVE lt_f4-fieldval TO i_mprn-mprn.
    ws_dyname1   = 'ZSRO_MASTER_DATA'.
    ws_dynumb1   = '0301'.
    ws_dynpfld1-fieldname ='I_MPRN-MPRN'.
    ws_dynpfld1-fieldvalue = i_mprn-mprn.
    ws_dynpfld1-stepl      = stepl_index1.
    APPEND ws_dynpfld1 TO i_dnpfld1.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
      EXPORTING
        dyname               = ws_dyname1
        dynumb               = ws_dynumb1
      TABLES
        dynpfields           = i_dnpfld1
      EXCEPTIONS
        invalid_abapworkarea = 1
        invalid_dynprofield = 2
        invalid_dynproname   = 3
        invalid_dynpronummer = 4
        invalid_request      = 5
        no_fielddescription = 6
        undefind_error       = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
CLEAR : i_dnpfld1, ws_dynpfld1.
REFRESH: i_dnpfld1.
READ TABLE lt_f4 WITH KEY fieldname = 'ZZPSTLZ'.
IF sy-subrc = 0.
    MOVE lt_f4-fieldval TO i_mprn-post_code.
    ws_dyname1   = 'ZSRO_MASTER_DATA'.
    ws_dynumb1   = '0301'.
    ws_dynpfld1-fieldname ='I_MPRN-POST_CODE'.
    ws_dynpfld1-fieldvalue = i_mprn-post_code.
    ws_dynpfld1-stepl      = stepl_index1.
    APPEND ws_dynpfld1 TO i_dnpfld1.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
      EXPORTING
        dyname               = ws_dyname1
        dynumb               = ws_dynumb1
      TABLES
        dynpfields           = i_dnpfld1
      EXCEPTIONS
        invalid_abapworkarea = 1
        invalid_dynprofield = 2
        invalid_dynproname   = 3
        invalid_dynpronummer = 4
        invalid_request      = 5
        no_fielddescription = 6
        undefind_error       = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
ENDMODULE.                 " mprn1_f4 INPUT
*&      Module pstlz1_f4 INPUT
      text
MODULE pstlz1_f4 INPUT.
CLEAR: i_dnpfld1, ws_dyname1, ws_dynumb1, ws_dynpfld1,
          lt_f4, lt_returntab1,lt_dynpfields1, lt_f4,
          stepl1, stepl_index1.
REFRESH: i_dnpfld1, lt_returntab1,lt_dynpfields1, lt_f4.
To Determine Steploop Index
lt_dynpfields1-fieldname = 'I_MPRN-MPRN'.
lt_dynpfields1-stepl     = stepl1.
APPEND lt_dynpfields1. CLEAR lt_dynpfields1.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = 'X'
      determine_loop_index = 'X'
    TABLES
      dynpfields           = lt_dynpfields1
    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.
IF sy-subrc EQ 0.
    READ TABLE lt_dynpfields1 INDEX 1.
ENDIF.
stepl_index1 = lt_dynpfields1-stepl.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
    EXPORTING
      tabname           = 'IFLOT'
      fieldname         = 'I_MPRN-POST_CODE'
      searchhelp        = 'ZS_MPRN_PC'
      dynpprog          = sy-repid
      dynpnr            = sy-dynnr
    TABLES
      return_tab        = lt_f4
    EXCEPTIONS
      field_not_found   = 1
      no_help_for_field = 2
      inconsistent_help = 3
      no_values_found   = 4
      OTHERS            = 5.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Update tablecontrol
READ TABLE lt_f4 WITH KEY fieldname = 'ZZPSTLZ'.
IF sy-subrc = 0.
    MOVE lt_f4-fieldval TO i_mprn-post_code.
    ws_dyname1   = 'ZSRO_MASTER_DATA'.
    ws_dynumb1   = '0301'.
    ws_dynpfld1-fieldname ='I_MPRN-POST_CODE'.
    ws_dynpfld1-fieldvalue = i_mprn-post_code.
    ws_dynpfld1-stepl      = stepl_index1.
    APPEND ws_dynpfld1 TO i_dnpfld1.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
      EXPORTING
        dyname               = ws_dyname1
        dynumb               = ws_dynumb1
      TABLES
        dynpfields           = i_dnpfld1
      EXCEPTIONS
        invalid_abapworkarea = 1
        invalid_dynprofield = 2
        invalid_dynproname   = 3
        invalid_dynpronummer = 4
        invalid_request      = 5
        no_fielddescription = 6
        undefind_error       = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
CLEAR : i_dnpfld1, ws_dynpfld1.
REFRESH: i_dnpfld1.
READ TABLE lt_f4 WITH KEY fieldname = 'MPRN'.
IF sy-subrc = 0.
    MOVE lt_f4-fieldval TO i_mprn-mprn.
    ws_dyname1   = 'ZSRO_MASTER_DATA'.
    ws_dynumb1   = '0301'.
    ws_dynpfld1-fieldname ='I_MPRN-MPRN'.
    ws_dynpfld1-fieldvalue = i_mprn-mprn.
    ws_dynpfld1-stepl      = stepl_index1.
    APPEND ws_dynpfld1 TO i_dnpfld1.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
      EXPORTING
        dyname               = ws_dyname1
        dynumb               = ws_dynumb1
      TABLES
        dynpfields           = i_dnpfld1
      EXCEPTIONS
        invalid_abapworkarea = 1
        invalid_dynprofield = 2
        invalid_dynproname   = 3
        invalid_dynpronummer = 4
        invalid_request      = 5
        no_fielddescription = 6
        undefind_error       = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
ENDMODULE.                 " pstlz1_f4 INPUT
Regards,
Prakash.

Search help for business partner ID in segmentation applet

Hello,
In CRM 2007 I'm using the segmentation toll. When creating filters for Business Partner ID criterium I'm using a search help functionality to find the desired records. However search help for business partners used in this area is very different from the search help used in any other parts of WEB UI (it is restricted to only few fields, that are not enough for our requirements).
Segmentation applet is written in Java but the search help looks like normal WEB UI screen. I wonder if any of you could help me with replacing this serach help called by segmentation applet (java application) with a standard search help for business partners (BP_HEAD_SEARCH)?
Kind reagrds
Marek

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.

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

Search help for input fields in a screen

Hi,
Pls help me
how to set search help property for the I/O fields in screen in se80?
1. do we want to add any property for search help in the property window?
2.do we want to create a MODULE PROCESS ON VALUE REQUEST ?
PLS tell me how to set search for the I/O field in se80?pls tell me the process?
i want to set the search help for more I/O fields in se80 but all the fields belongs to the same table?
can i create a single search for all these fields and use that for all the I/O fields ?
elementary search help or collective search help?
thanks & regards in advance,
vsnl.

Hi,
Input Help on the Screen
Within the Screen Painter, you can define two types of input help:
1. The FIELD statement with one of the additions VALUES or SELECT.
2. Linking a search help directly to a screen field.
If you link a search help directly to a screen field, it overrides the additions of the FIELD
statement. However, the input check [Page 581] functions of the FIELD statement remain
unaffected.
Input Help in Flow Logic
The following input help methods are obsolete and should not be used. They are still supported
for compatibility reasons.
In the screen flow logic, you can specify a value list for a screen field <f> as follows:
FIELD <f> VALUES (<val1>, <val2>,...).
The value list contains a series of single values <vali>. The NOT and BETWEEN additions for the
input check [Page 581] are not appropriate for input help.
You can also create a value list by accessing a database table as follows:
FIELD <f> SELECT *
FROM <dbtab>
WHERE <k1> = <f1> AND <k2> = <f2> AND...
In the WHERE condition, the fields of the primary key <ki> of the database table <dbtab> are
checked against the screen fields <fi>. The WHENEVER addition, used with input checks [Page
581], is not necessary for input help.
If you have used a ABAP Dictionary reference for field <f>, the selection and the hit list formatting
may be affected by any check table attached to the field.
Attaching a Search Help
Search helps from the ABAP Dictionary can be attached to a screen field [Ext.]. To do this, enter
the name of the search help in the corresponding field in the attributes of the screen field in the
Screen Painter. This assigns the first parameter of the search help to the screen field. It is only
possible to place a value from the hit list onto the screen.
Input help on a screen.
REPORT DEMO_DYNPRO_F4_HELP_DYNPRO MESSAGE-ID AT.
DATA: CARRIER(3) TYPE C,
CONNECTION(4) TYPE C.
CALL SCREEN 100.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
602 April 2001
Cancel
Airline
Flight number
Screen field with search help
Input help in the flow logic
The input fields have been adopted from the program fields CARRIER and
CONNECTION. The function code of the pushbutton is CANCEL, with function type
E. The search help DEMO_F4_DE with the search help parameter CARRID is
assigned to the screen field CARRIER. The search help uses the database table
SCARR.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
FIELD CARRIER VALUES ('AA', 'LH').
FIELD CONNECTION SELECT *
FROM SPFLI
WHERE CARRID = CARRIER
AND CONNID = CONNECTION.
When the user chooses the input help for the individual fields, the following input
help is displayed:
For the Airline field, the search help displays the names of the airlines and places the airline
code in the input field for the chosen line. If the airline code is not one of those listed in the
VALUES list of the screen flow logic, the input check triggers an error message in the PAI
event. So the search help overrides the VALUES addition for the input help, but not for the
input checks. This is therefore not an appropriate place to use the VALUE addition.
For the Flight number field, the flow logic displays the selected entries from the database
table SPFLI and places the selected line in the input field.
Regards,
Bhaskar

Search help for field in SM30

Hi Experts,
This is a Z table with first field as GROUP and second field as KEY.
User can select values for first field using a search help. It has three possibel entries
1. Purchasing Org
2. Region
3. Coutnry
In second field the user has to enetr value based on selection in first field, for eg. if 1 is chosen in 1st field user will enter name of a purchasing organisation.
Can we dispay a search help for second field based on the selection in first field?
Like if 1 is selected in 1st field second field should display search help for Purchasing Org
if 2 is selected in 1st field second field should display search help for Region....in SM30?
How can we achieve this?
Thank you,
Anubhav

Hi Anubhav,
1.Go to the table maintenance generator screen from SE11 (Utilities -> Table Maintenance Generator).
2. In the Table maintenance generator screen , navigate to Environment -> Modifications -> Maintenance Screens
3. Select and Edit the screen where you need this new search help
4. Create a Process on Value Request module for your second field at the end of the screen flow logic after MODULE LISTE_AFTER_LOOP.
5. In the POV module, use funcntion DYNP_VALUES_READ to read the value of field 1 on the screen
6. Fill your own table with the values for field 2 based on field 1 and display selection using the function F4IF_INT_TABLE_VALUE_REQUEST
Hope this helps.
- Puneet

Search help for date in ALV grid

I have ALV grid with field type date and search help for this:
ws_field-ref_table = 'ADCP'.
ws_field-ref_field = 'DATE_FROM'.
ws_field-inttype = 'D'
After I have clicked on this key F4 then I see a calendar and I have choosen some date, but in input grid field there aren't
choosen value. Why? Another search helps works perfect except this. Where is the problem?
Edited by: Kosmo on Jul 7, 2009 8:48 AM

Hi,
Find the code below
TYPE-POOLS: slis.
DATA: it_fcat TYPE slis_t_fieldcat_alv,
      wa_fcat LIKE LINE OF it_fcat.
DATA: it_data TYPE vbap_t.
SELECT *
FROM VBAP
INTO TABLE it_data
UP TO 20 ROWS.
wa_fcat-fieldname = 'VBELN'.
wa_fcat-tabname = 'IT_DATA'.
wa_fcat-ref_fieldname = 'VBELN'.
wa_fcat-ref_tabname = 'VBAK'.
APPEND wa_fcat TO it_fcat.
clear wa_fcat .
wa_fcat-fieldname = 'POSNR'.
wa_fcat-tabname = 'IT_DATA'.
wa_fcat-seltext_l = 'Date'.
wa_fcat-ref_fieldname = 'ERDAT'.
wa_fcat-ref_tabname = 'VBAK'.
APPEND wa_fcat TO it_fcat.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      i_interface_check       = sy-repid
      it_fieldcat             = it_fcat
    TABLES
      t_outtab                = it_data
    EXCEPTIONS
      program_error           = 1.
I have derived the above code from WIKi link
https://wiki.sdn.sap.com/wiki/display/Snippets/f4helpforalvgrid+display
Regards,
Murthy.

Custom search help for a custom field in SRM 7

EDIT: I'm gonna clarify on this thread since my first post wasn't explicative enough... thanks for the patience
Hi all gurus,
the question is about a search help in SRM7 but since the task is about abap development, I guess this is the right section to ask for.
Shortly; every purchase doc in our SRM7 has a custom header table which contains data which are retrieved from the connected backends. In this custom table, the user has the opportunity to add manually a line, and for a specific input field in table, we have to define a search help which should retrieve the appropriate possible values w.r.t. the "target" backend for the document.
A bit of technical data: say the field is called ZZ_R3_ROLE; it's included in a custom structure ZR7_HEADER_CST_GEN which is itself an append for BBP_PDHCF.
I defined a Search Help for that field and the corresponding exit FM to manage our task.
Unfortunately, to retrieve the possible values for the specific backend I need some informations like:
- the backend on which the document will be distributed;
- the process type of the document.
This means that my search help should take into account additional informations that comes from the document I'm processing; I don't know what's the "clean" solution to do this.
I've seen on an old system (a SAP SRM 3.0) a workaround based on IMPORT/EXPORT ... TO MEMORY ID has been used. Actually, I'd like to find a more elegant solution, if any.
So... as you can see, I'm absolutely a newbie on the argument, but since I can trigger the search help only from a purchase document (PO, contract) process, I should need at least the GUID of the document to retrieve, for example, what's the target backend for that document in order to provide proper values.
Any hint/suggestion and in particular, a sketch of code as example is welcome.
Edited by: Matteo Montalto on Oct 22, 2010 3:01 PM

Hi,
into your modify view,
extract data you need in your search help in an itab (do it into a class do not perform select directly into modify view) and then bind it as value help to your WD element.
Regards,
Ivan

Maintain acct determination (table T030B) for posting key IRX / IGX (M8395)

Dear Guru,
I am testing IS-Oil & Gas (Downstream) - Exchanges.
Created Exchange Agreement and Purchase Contract and Sales Contract, Purchase Contract and Sales Contract are assigned to the Exchange Contract.
A PO is created with reference to the Purchase Contract.
Upon post goods receipt in MIGO, encountered error message "Maintain account determination (table T030B) for posting key IRX (Message no. M8395)" that does not allow PGR to get through.
A call-off is created with reference to the Sales Contract.
Similarly, when PGI is performed in VL01N, encountered error message "Maintain account determination (table T030B) for posting key IGX (Message no. M8395)" that does not allow PGI to get through.
Checked in OBYC, there is no transaction key for IRX and IGX.
Please advise. Thank you.
Regards,
WL

Hi WL,
Please use transaction code O54E to maintain the required configuration.
I hope this helps you.
Thanks & Regards
Kalpesh Chavda

Maintain account determination (table T030B) for posting key IRX (M8395)

Dear Guru,
I am testing IS-OIL - Exchanges.
Created Exchange Agreement and Purchase Contract and Sales Contract, Purchase Contract and Sales Contract are assigned to the Exchange Contract.
A PO is created with reference to the Purchase Contract.
Upon post goods receipt in MIGO, encountered error message "Maintain account determination (table T030B) for posting key IRX (Message no. M8395)" that does not allow PGR to get through.
A call-off is created with reference to the Sales Contract.
Similarly, when PGI is performed in VL01N, encountered error message "Maintain account determination (table T030B) for posting key IGX (Message no. M8395)" that does not allow PGI to get through.
Checked in OBYC, there is no transaction key for IRX and IGX.
Please advise. Thank you.
Regards,
WL

Hi WL,
In an Exchange scenario, the account determination entry would have to go added through tcode O54E for this purpose. You would see both the IRX and IGX entry in the above mentioned tcode.
Menu path: IS-OIL Downstream --> EXG --> Account Assignment
You would not be able to see the IRX or IGX transaction key in OBYC.
Hope the above helps.
Thanks.
Edited by: Kok Wai Phang on Jul 10, 2011 7:58 AM

How to add a search help for a field in Screen Personas?

I just started learning to use a Screen Personas, and I want to know how to add a search help for a field.
I found a property in the help document named "IsLookupSupported". Is it the key? But I saw it was gray in the field I created, and its value is "false". I could not change it.

Hi, Tamas,
I found the reason. The function Z_WEBRFC_READ_DATA_SH had a string concatenation error.
CONCATENATE '{"results":[{"key": "shlpname", "value": "' l_shlp '"},"key": "fieldname", "value": "' l_field '"}]}' INTO htmldoc-line.
The correct code is like:
CONCATENATE '{"results":[{"key": "shlpname", "value": "' l_shlp '"},{"key": "fieldname", "value": "' l_field '"}]}' INTO htmldoc-line.
Another question is, I can't get any words in Chinese from WebRFC. It returns error when I try it. How can I configure it?
Xin

FB01 Enter Trading Partner for Posting Key 01 (Customer Invoice)

Dear Experts,
I would like to ask is it possible to enter the Trading Partner for the FI Document line item with Posting Key 01.
I can modify the Trading Partner for Posting Key 40 and 50 but I cannot find field in the More Data Button.
Can anyone help me to solve this issue?
Thanks.

hi,
Check whether the document type you are using to post is allowed to enter the trading partner.
To check use the TCODe OBA7 and select the relevent document type. then select the check box enter trading partner under control data.
and also check the customer you assigned for that posting key 01 is got assigned trading partner in the master record or not(TCOD XD02/XD03).
thanks.

Reverse posting key specification is missing for posting key 80

A FI document was wrongly posted with posting key "80" instead of 40. And now we are not able to reverse it. System is giving following error --
"Reverse posting key specification is missing for posting key 80"
Document posted as
50     207200     CASH - MAIN-O.H.     762.00-
40     410120     CONVEYANCE EXPENSES     702.00
<b>80     402440     STAFF WELFARE EXPENS     60.00</b>
Please suggest
Thanks & Regards

Hi,
Go to OB41, select the posting key 80 and in the third tab "Other attributes" mention Reversal Posting key. Like you can observe for posting key 40, reversal key 50 would have been assigned.
Pl assign points, if helpful.

Search help for posting key

Similar Messages

Maybe you are looking for