Message on clicks on standard button of alv in webdynpro

Hi experts,
I want to show message on clicks on standard button of alv in webdynpro.

Hi Rohit..
Also check this...
http://wiki.sdn.sap.com/wiki/display/Snippets/WebDynproABAP-ALVControllingStandard+Buttons
Cheers,
Kris.

Similar Messages

Disable some standard buttons from ALV display

Hello All,
I am creating an ALV display using object oriented approach. I know how to exclude some of the standard function buttons from the list.
But suppose instead of deleting, the requirement is to disable (I mean grayed out)
some standard buttons from ALV. Could anyone please comment on how to do this.
Many thanks in advance.
Regards
Indrajit

Hello Indrajit
The following sample reports shows how to disable toolbar functions. Run the report and the push the ENTER button repeatedly.
*& Report ZUS_SDN_ALV_EVT_TOOLBAR
*& This sample report explains the handling of event TOOLBAR in order
*% to activate or inactive buttons of the ALV toolbar.
*& Based on: BCALV_GRID_DEMO
*& Procedure: Copy BCALV_GRID_DEMO and replace entire coding OR
            copy screen '0100' and GUI status 'MAIN100' from
            BCALV_GRID_DEMO to this report.
REPORT zus_sdn_alv_evt_toolbar.
TYPE-POOLS: abap, cntb, icon.
DATA:
ok_code                TYPE ui_func,
gt_sflight             TYPE TABLE OF sflight,
g_container        TYPE scrfname VALUE 'BCALV_GRID_DEMO_0100_CONT1',
g_grid1               TYPE REF TO cl_gui_alv_grid,
g_custom_container    TYPE REF TO cl_gui_custom_container.
PARAMETERS:
p_inact    RADIOBUTTON GROUP grp1 DEFAULT 'X', " delete buttons
p_dele     RADIOBUTTON GROUP grp1.               " inactivate buttons
PARAMETERS:
p_newbut   AS CHECKBOX DEFAULT ' ', " add new button
p_newddm   AS CHECKBOX DEFAULT 'X'. " add dropdown menu
      CLASS lcl_eventhandler DEFINITION
CLASS lcl_eventhandler DEFINITION.
PUBLIC SECTION.
    CLASS-DATA:
      md_cnt    TYPE i.
    CLASS-METHODS:
      handle_toolbar FOR EVENT toolbar OF cl_gui_alv_grid
        IMPORTING
          e_object
          e_interactive
          sender.
ENDCLASS.                    "lcl_eventhandler DEFINITION
      CLASS lcl_eventhandler IMPLEMENTATION
CLASS lcl_eventhandler IMPLEMENTATION.
METHOD handle_toolbar.
§ 2.In event handler method for event TOOLBAR: Append own functions
by using event parameter E_OBJECT.
    DATA:
      ls_toolbar TYPE stb_button,
      ls_menu     type STB_BTNMNU.
E_OBJECT of event TOOLBAR is of type REF TO CL_ALV_EVENT_TOOLBAR_SET.
This class has got one attribute, namly MT_TOOLBAR, which
is a table of type TTB_BUTTON. One line of this table is
defined by the Structure STB_BUTTON (see data deklaration above).
A remark to the flag E_INTERACTIVE:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        'e_interactive' is set, if this event is raised due to
        the call of 'set_toolbar_interactive' by the user.
        You can distinguish this way if the event was raised
        by yourself or by ALV
        (e.g. in method 'refresh_table_display').
        An application of this feature is still unknown...
    ADD 1 TO md_cnt. " a simple counter
(1.a) Inactivate toolbar buttons
    IF ( p_inact = abap_true ).
      LOOP AT e_object->mt_toolbar INTO ls_toolbar FROM 1 TO md_cnt.
        ls_toolbar-disabled = 'X'.
        MODIFY e_object->mt_toolbar FROM ls_toolbar.
      ENDLOOP.
(1.b) Delete toolbar buttons
    ELSE.
      DO md_cnt TIMES.
        DELETE e_object->mt_toolbar INDEX 1.
      ENDDO.
    ENDIF.
(2) Add new button
    IF ( p_newbut = abap_true ).
    Add separator to separate default and new buttons
      CLEAR: ls_toolbar.
      ls_toolbar-butn_type = cntb_btype_sep. " separator
      APPEND ls_toolbar TO e_object->mt_toolbar.
    Add new button "DETAIL"
      CLEAR: ls_toolbar.
      ls_toolbar-function = 'DETAIL'.
      ls_toolbar-icon      = icon_detail.
      ls_toolbar-quickinfo = 'QuickInfo'.
      ls_toolbar-butn_type = cntb_btype_button.
      ls_toolbar-disabled = abap_false.
      ls_toolbar-text      = 'Details'.
     ls_toolbar-checked = ' '.
      APPEND ls_toolbar TO e_object->mt_toolbar.
    ENDIF.
(3) Add new dropdown menu
    IF ( p_newddm = abap_true ).
    Add separator to separate default and new buttons
      CLEAR: ls_toolbar.
      ls_toolbar-butn_type = cntb_btype_sep. " separator
      APPEND ls_toolbar TO e_object->mt_toolbar.
    Add new dropdown menu "DETAIL"
      CLEAR: ls_toolbar.
      ls_toolbar-function = 'DDMENU'.
      ls_toolbar-icon      = icon_detail.
      ls_toolbar-quickinfo = 'QuickInfo'.
      ls_toolbar-butn_type = cntb_btype_dropdown.
      ls_toolbar-disabled = abap_false.
      ls_toolbar-text      = 'DD-Menu'.
     ls_toolbar-checked = ' '.
      APPEND ls_toolbar TO e_object->mt_toolbar.
    ENDIF.
ENDMETHOD.                    "handle_toolbar
ENDCLASS.                    "lcl_eventhandler IMPLEMENTATION
START-OF-SELECTION.
      MAIN                                                          *
SELECT * FROM sflight INTO TABLE gt_sflight.
CALL SCREEN 100.
END-OF-SELECTION.
      MODULE PBO OUTPUT                                             *
MODULE pbo OUTPUT.
SET PF-STATUS 'MAIN100'.
IF g_custom_container IS INITIAL.
    CREATE OBJECT g_custom_container
           EXPORTING container_name = g_container.
Instantiate ALV grid control
    CREATE OBJECT g_grid1
           EXPORTING i_parent = g_custom_container.
    CALL METHOD g_grid1->set_table_for_first_display
      EXPORTING
        i_structure_name = 'SFLIGHT'
      CHANGING
        it_outtab        = gt_sflight.
Set event handler for event TOOLBAR
    SET HANDLER:
      lcl_eventhandler=>handle_toolbar FOR g_grid1.
ENDIF.
$Comment: Toolbar can be modified on-the-fly
g_grid1->set_toolbar_interactive( ).
ENDMODULE.                    "PBO OUTPUT
      MODULE PAI INPUT                                              *
MODULE pai INPUT.
to react on oi_custom_events:
CALL METHOD cl_gui_cfw=>dispatch.
CASE ok_code.
    WHEN 'EXIT'.
      PERFORM exit_program.
    WHEN OTHERS.
    do nothing
ENDCASE.
CLEAR ok_code.
ENDMODULE.                    "PAI INPUT
      FORM EXIT_PROGRAM                                             *
FORM exit_program.
CALL METHOD G_CUSTOM_CONTAINER->FREE.
CALL METHOD CL_GUI_CFW=>FLUSH.
LEAVE PROGRAM.
ENDFORM.                    "EXIT_PROGRAM[/code]
Regards
Uwe

Error Messages on clicking the previous button from the review of PCR.

Hi,
When we fill the PCR form and review it. it works fine.
Once i click the 'previous' button from the review stage, A pop up window with title - 'Adobe Reader' comes up which says - 'Message limit exceeded <a number> errors not reported'.
Does this have to do with the Action methods of this button.
This is common across all forms including the standard forms delivered by SAP.
Any pointers or duggestions to this will be highly appreciated.
s/m - NW2004
reg: ISR Adobe forms
Kindly help.
Regards,
Anto

Hi Anto,
i've seen this message too in the ISR scenario on NW2004. It is related to the Active Component Framework (ACF). Please try installing the most recent xACF file. See note 766191 for more info and a link to the file for SP18.
kind regards,
Marijn Sponselee

Standard buttons in ALV

Hi all,
I need to change the text to the standard button "Export" in ALV for the text "Excel" and assing only one function to this button, the function I need is export to excel.
Does anyone knows how to solve this problem please?
Help is really appreciated.
Regards!

In your first post you asked about ALV and now about non-ALV...
So about ALV you have the Excel download by default and you are able to change the text.
About non-ALV download I think you have to use the method: cl_wd_runtime_services=>attach_file_to_response.
Look at the last post in:
File download WD4A
Sergio

Showing error messages on click of Save button only

Hi,
Generally SAP web client GUI is showing the error message on pressing of Enter button (or) picking up any data field and stepping out of it. We want to show error messages for mandatory fields only when user clicks on Save. How can this be done in SAP web client GUI?
Regards
--Hari

Hi Hari,
If you want to raise an error message on save. Try this.
method eh_onsave
DATA: lr_msg_service    TYPE REF TO cl_bsp_wd_message_service.
DATA: ls_msg_no TYPE symsgno.
if ( condition failed)
lr_msg_service = me->view_manager->get_message_service( ).
    lr_msg_service->add_message(
    iv_msg_type       = 'E'
    iv_msg_id         = 'Z_MSG_CLASS'
    iv_msg_number     = ls_msg_no ).
exit the method once the error message is raised
exit
endif.
end method.
Note : specify the message class and message number in the add_message menthod.
Hope this was helpful.
Best Regards,
Lakshminarayana

Deleting progress message when click of a button

hi,
similar to the image shown below, can i use this progress message - liek deleting - inserting- in progress- on top right corner just below mty custom master page.Would like to how to achieve this progress / status message using SP API. if
i wnat to use this ona click of a button in my custom visual web part, whats the API to be used.
thnx.

HI,
You can use "SPLongOperation", please check the below references for more info..
https://social.msdn.microsoft.com/Forums/sharepoint/en-US/b5f8620d-a1dc-4c79-9141-be3e153903ed/progress-bar-in-sharepoint-2010-web-part
http://howtosharepoint.blogspot.in/2010/04/how-to-programatically-show-processing.html
or
use below approach...
http://blog.mastykarz.nl/sharepoint-2010-ui-tip-non-obtrusive-progress-messages/
Don't forget to mark it as an Answer if it resolves your issue and Vote Me as helpful if it useful.
Mahesh

Remove standard button in ALV LIKE APPEND/INSERT/DELETE

Hi Expert,
I have a requirement in which we do not need APPEND/INSERT/DELETE button in ALV,Can you please tell how i can remove that.
Pleaae suggest.
Thanks
Mahesh

Check this
    data lo_cmp_usage type ref to if_wd_component_usage.
    lo_cmp_usage =   wd_this->wd_cpuse_alv1( ). " alv1 is my used alv component
    if lo_cmp_usage->has_active_component( ) is initial.
      lo_cmp_usage->create_component( ).
    endif.
    data lo_interfacecontroller type ref to iwci_salv_wd_table .
    lo_interfacecontroller =   wd_this->wd_cpifc_alv1( ).
    data lo_value type ref to cl_salv_wd_config_table.
    lo_value = lo_interfacecontroller->get_model(    ).
data: lr_std type ref to if_salv_wd_std_functions.
    lr_std ?= lo_value.
lr_std->SET_EDIT_APPEND_ROW_ALLOWED( abap_false ).
lr_std->SET_EDIT_DELETE_ROW_ALLOWED( abap_false ).
lr_std->SET_EDIT_INSERT_ROW_ALLOWED( abap_false ).
Regards
Srinivas

Inactive standard buttons in ALV

Hi Experts,
I had requirement to inactive some buttons in standard alv. For Example, sorting buttons,download to excel should be made inactive. Please provide your solutions to solve the issue.
Thanks and Regards,
Bharat

Hi!
You can try this:
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      it_fieldcat              = wa_fcat[]
      i_grid_title             = gv_title
      i_callback_program       = sy-repid
      i_callback_pf_status_set = 'SET_STATUS'
      is_layout                = gd_layout
    TABLES
      t_outtab                 = it_screen.
FORM set_status USING i_it_excluding TYPE slis_t_extab.
SET PF-STATUS 'z001' EXCLUDING x1 x2.
ENDFORM.                    " SET_STATUS
thanks,
Raul Natu

Getting error message while clicking on proposal button in Automatic Py.Pr

When trying run Automatic payment program, clicking on proposal , getting error message "Company codes SAG1/SAG1 do not appear in proposal 12.05.2010 SAG1;correct"
Please help me in resolving this error message.

Hi Sagar,
This may happen when the particular line items are entered in another proposal and not exequted fully.
So system will block these line items in old app run and will not allow in new app.
you can over come by exequting the old APP run or deleting values in previous APP run and run new APP.
Regards
babu.

Debugging standard button code in ALV

Hi All,
I would like to debug the "Export" button that is available on tool bar.Is it possibe? If yes, pls suggest.
Thank You,
Suresh.

Hi Suresh,
On the View in Which the alv is displaying, go to methods, create a new method , type event handler, then select from drop down on standard_button_click. then put a debugger on the method and run the application. then after wards on click or select of any standard button on alv will trigger the method.from the parameters of the method you can check the button clicked and its properties.
Regards
Sarath

Hide 'Change Layout' button from alv toolbar

Hello All,
can anyone let me know how can we hide the change layout button or exclude the change layout button from the ALV tool bar using OOPS . what's the fcode for it.
Thank You !
Ravi

Hi Ravi,
Please refer to this [Program|http://www.saptechies.com/disable-some-standard-buttons-from-alv-display/].
Hope this helps.
Regards,
Chandravadan

SALV class : Footer display on click of a button

Hi,
     I am using SALV classes to display ALV report. Is it possible to display the footer on click of a button in ALV report (on user command) ?
i am doing the following, but it does not work. there is no footer displayed
METHOD on_user_command.
CASE e_salv_function.
WHEN '&ACT' .
PERFORM set_end_of_page   CHANGING o_table.
WHEN (...)
endcase .
FORM set_end_of_page CHANGING p_o_table type ref to cl_salv_table.
   DATA: lo_footer TYPE REF TO cl_salv_form_layout_grid,
          lo_f_label TYPE REF TO cl_salv_form_label,
      lo_f_flow TYPE REF TO cl_salv_form_layout_flow.
**   footer object
CREATE OBJECT lo_footer.
**   information in bold
lo_f_label = lo_footer->create_label( row = 1 column = 1 ).
lo_f_label->set_text( 'Footer .. here it goes' ).
**   tabular information
lo_f_flow = lo_footer->create_flow( row = 2 column = 1 ).
lo_f_flow->create_text( text = 'This is text of flow in footer' ).
lo_f_flow = lo_footer->create_flow( row = 3 column = 1 ).
lo_f_flow->create_text( text = 'Footer number' ).
lo_f_flow = lo_footer->create_flow( row = 3 column = 2 ).
lo_f_flow->create_text( text = 1 ).
** Online footer
p_o_table->set_end_of_list( lo_footer ).
**   Footer in print
p_o_table->set_end_of_list_print( lo_footer ).
ENDFORM.

H Geetha,
              Add ScrollContainer to your view. In that take textView. Bind the context element to textView. Or Take TextEdit and bind the context. I don't think there is any problem.
regards,
Siva

Page has expired message on clickiong the "Back" button on Browser

Hi ,
I get Page has expired message on clicking the "Back" button in the browser. I want the user to get directed to the previous page with out viewing this message.
I am using tomcat 5.0 web server and struts framework for my application.
Kindly help me in this regard.

me too i am facing the same problem,
what i found is:
1.you can use get instead of post method action.
2 remove the no cache from your system and make the system caching normally.
any one has any other solution?

Buttons in ALV Grid cell need focus to be clicked :-(

Hi,
I have an ALV Grid with single cells displayed as buttons (dependend on the data in the corresponding row). Unfortunatelly the button-cells need focus to be clicked. So you need two clicks: one to get the focus to the desired cell and one to really click the button.
Any ideas how to make this work with one single click ? (Setting a hotspot does not work, cause hotspots have the same problem.)
Regards,
Tobi

Hello Tobias
The proposal by Naimesh is valid for CL_GUI_ALV_GRID, too. You may have a look at sample report ZUS_SDN_ALVGRID_EVENTS_HOTSPOT. Put the focus on any non-button cell and next click on any customer button.
*& Report ZUS_SDN_ALVGRID_EVENTS_HOTSPOT
*& Thread: Buttons in ALV Grid cell need focus to be clicked :-(
*& <a class="jive_macro jive_macro_thread" href="" __jive_macro_name="thread" modifiedtitle="true" __default_attr="1009251"></a>
REPORT zus_sdn_alvgrid_events_hotspot.
DATA:
gd_okcode        TYPE ui_func,
gt_fcat          TYPE lvc_t_fcat,
go_docking       TYPE REF TO cl_gui_docking_container,
go_grid1         TYPE REF TO cl_gui_alv_grid.
DATA:
go_table              TYPE REF TO cl_salv_table,
go_grid_adapter       TYPE REF TO cl_salv_grid_adapter.
DATA:
gt_knb1          TYPE STANDARD TABLE OF knb1.
PARAMETERS:
p_bukrs      TYPE bukrs DEFAULT '2000' OBLIGATORY.
*       CLASS lcl_eventhandler DEFINITION
CLASS lcl_eventhandler DEFINITION.
PUBLIC SECTION.
    CLASS-METHODS:
      handle_hotspot_click FOR EVENT hotspot_click OF cl_gui_alv_grid
        IMPORTING
          e_row_id
          e_column_id
          es_row_no
          sender, " grid instance that raised the event
      handle_button_click FOR EVENT button_click OF cl_gui_alv_grid
        IMPORTING
          es_col_id
          es_row_no
          sender.
ENDCLASS.                    "lcl_eventhandler DEFINITION
*       CLASS lcl_eventhandler IMPLEMENTATION
CLASS lcl_eventhandler IMPLEMENTATION.
METHOD handle_hotspot_click.
*   define local data
    DATA:
      ls_knb1     TYPE knb1,
      ls_col_id   TYPE lvc_s_col.
    READ TABLE gt_knb1 INTO ls_knb1 INDEX e_row_id-index.
    CHECK ( ls_knb1-kunnr IS NOT INITIAL ).
    CASE e_column_id-fieldname.
      WHEN 'KUNNR'.
        SET PARAMETER ID 'KUN' FIELD ls_knb1-kunnr.
        SET PARAMETER ID 'BUK' FIELD ls_knb1-bukrs.
        CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.
      WHEN 'ERNAM'.
*        SET PARAMETER ID 'USR' FIELD ls_knb1-ernam.
*        NOTE: no parameter id available, yet simply show the priciple
        CALL TRANSACTION 'SU01' AND SKIP FIRST SCREEN.
      WHEN OTHERS.
*       do nothing
    ENDCASE.
*   Set active cell to field BUKRS otherwise the focus is still on
*   field KUNNR which will always raise event HOTSPOT_CLICK
    ls_col_id-fieldname = 'BUKRS'.
    CALL METHOD go_grid1->set_current_cell_via_id
      EXPORTING
        is_row_id    = e_row_id
        is_column_id = ls_col_id.
ENDMETHOD.                    "handle_hotspot_click
METHOD handle_button_click.
*   define local data
    DATA:
      ls_knb1     TYPE knb1.
    READ TABLE gt_knb1 INTO ls_knb1 INDEX es_row_no-row_id.
    CHECK ( ls_knb1-kunnr IS NOT INITIAL ).
    SET PARAMETER ID 'KUN' FIELD ls_knb1-kunnr.
    SET PARAMETER ID 'BUK' FIELD ls_knb1-bukrs.
    CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.
ENDMETHOD.                    "handle_button_click
ENDCLASS.                    "lcl_eventhandler IMPLEMENTATION
START-OF-SELECTION.
SELECT        * FROM knb1 INTO TABLE gt_knb1
         WHERE bukrs = p_bukrs.
** TRY.
**      CALL METHOD cl_salv_table=>factory
***      EXPORTING
***      LIST_DISPLAY   = IF_SALV_C_BOOL_SAP=>FALSE
***      R_CONTAINER    =
***      CONTAINER_NAME =
**        IMPORTING
**          r_salv_table   = go_table
**        CHANGING
**          t_table        = gt_knb1.
**    CATCH cx_salv_msg .
** ENDTRY.
** go_table->display( ).
** go_table->get_metadata( ).
** EXIT.
* Create docking container
CREATE OBJECT go_docking
    EXPORTING
      parent = cl_gui_container=>screen0
      ratio = 90
    EXCEPTIONS
      OTHERS = 6.
IF sy-subrc <> 0.
*   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
* Create ALV grid
CREATE OBJECT go_grid1
    EXPORTING
      i_parent = go_docking
    EXCEPTIONS
      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.
* Set event handler
SET HANDLER:
    lcl_eventhandler=>handle_hotspot_click FOR go_grid1,
    lcl_eventhandler=>handle_button_click FOR go_grid1.
* Build fieldcatalog and set hotspot for field KUNNR
PERFORM build_fieldcatalog_knb1.
* Display data
CALL METHOD go_grid1->set_table_for_first_display
    CHANGING
      it_outtab       = gt_knb1
      it_fieldcatalog = gt_fcat
    EXCEPTIONS
      OTHERS          = 4.
IF sy-subrc <> 0.
*   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
* Link the docking container to the target dynpro
CALL METHOD go_docking->link
    EXPORTING
      repid                       = syst-repid
      dynnr                       = '0100'
*      CONTAINER                   =
    EXCEPTIONS
      OTHERS                      = 4.
IF sy-subrc <> 0.
*   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
* ok-code field = GD_OKCODE
CALL SCREEN '0100'.
END-OF-SELECTION.
*&      Module STATUS_0100 OUTPUT
*       text
MODULE status_0100 OUTPUT.
SET PF-STATUS 'STATUS_0100'.
* SET TITLEBAR 'xxx'.
ENDMODULE.                 " STATUS_0100 OUTPUT
*&      Module USER_COMMAND_0100 INPUT
*       text
MODULE user_command_0100 INPUT.
CASE gd_okcode.
    WHEN 'BACK' OR
         'END' OR
         'CANC'.
      SET SCREEN 0. LEAVE SCREEN.
    WHEN OTHERS.
ENDCASE.
CLEAR: gd_okcode.
ENDMODULE.                 " USER_COMMAND_0100 INPUT
*&      Form BUILD_FIELDCATALOG_KNB1
*       text
* --> p1        text
* <-- p2        text
FORM build_fieldcatalog_knb1 .
* define local data
DATA:
    ls_fcat        TYPE lvc_s_fcat.
CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
    EXPORTING
*     I_BUFFER_ACTIVE              =
      i_structure_name             = 'KNB1'
*     I_CLIENT_NEVER_DISPLAY       = 'X'
*     I_BYPASSING_BUFFER           =
*     I_INTERNAL_TABNAME           =
    CHANGING
      ct_fieldcat                  = gt_fcat
    EXCEPTIONS
      inconsistent_interface       = 1
      program_error                = 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.
LOOP AT gt_fcat INTO ls_fcat
          WHERE ( fieldname = 'KUNNR' OR
                  fieldname = 'ERNAM' OR
                  fieldname = 'BUKRS' ).
    IF ( ls_fcat-fieldname = 'BUKRS' ).
      ls_fcat-style = cl_gui_alv_grid=>mc_style_button.
      " column appears as button
    ELSEIF ( ls_fcat-fieldname = 'KUNNR' ).
      ls_fcat-style = cl_gui_alv_grid=>mc_style_button.
      ls_fcat-hotspot = abap_true.
    ELSE.
      ls_fcat-hotspot = abap_true.
    ENDIF.
    MODIFY gt_fcat FROM ls_fcat.
ENDLOOP.
ENDFORM.                    " BUILD_FIELDCATALOG_KNB1
Regards
Uwe

Standard backend service data vanishes on click of a button in HCM Forms

Hi,
I have a form which displays data from standard backend service SAP_PA and also from custom generic service.
When I click on a button in the form, the data from SAP_PA is disappearing.
Error message 'Please enter Personnel Number' is displaying.
Please help me to resolve the issue.

Hi Aravind,
Thanks for your reply...
Data is from standard backend service which is independent of user events..
Data is displaying for the first time when form is dispalyed on the portal but when user clicks on any button, data is disappearing...
Can you tell us the patch level of the system required for ESS MSS ??
As of now our system patch level is 11,,
This might be a problem for data vanishing?

Message on clicks on standard button of alv in webdynpro

Similar Messages

Maybe you are looking for