EVENTS IN ALV OOPS

HI GUYS,
CAN ANYONE PLS HELP ME OUT HANDLING EVENTS IN ALV(OOPS)....iS THERE ANY CLASS TO BE DEFINED ?????? PLS HELP IF ANYONE HAS THE CODE FOR THAT...........

Hi,
Declare as below.
CLASS LCL_EVENT_RECEIVER DEFINITION DEFERRED.
DATA : O_ALVGRID TYPE REF TO CL_GUI_ALV_GRID ,
       O_DOCKINGCONTAINER TYPE REF TO CL_GUI_DOCKING_CONTAINER ,
       O_EVENTRECEIVER TYPE REF TO LCL_EVENT_RECEIVER.
Then class definition should be as follows:
CLASS LCL_EVENT_RECEIVER DEFINITION.
Event receiver definitions for ALV actions
PUBLIC SECTION.
    CLASS-METHODS:
Row Double click for dirll down.
       HANDLE_DOUBLE_CLICK
         FOR EVENT DOUBLE_CLICK OF CL_GUI_ALV_GRID
            IMPORTING E_ROW
                      E_COLUMN
                      ES_ROW_NO.
ENDCLASS.
Then implementation should be as follows:
CLASS LCL_EVENT_RECEIVER IMPLEMENTATION.
*&      Method handle_double_click
This method is called when the user double clicks on a line to drill
down.
The following are exported from the ALV
LVC_S_ROW
LVC_S_COL
LVC_S_ROID
METHOD HANDLE_DOUBLE_CLICK.
The double click drill down processing should be
coded in the form below.
    PERFORM F9007_HANDLE_DOUBLE_CLICK USING E_ROW
                                            E_COLUMN
                                            ES_ROW_NO.
ENDMETHOD.
ENDCLASS.
*&      Form F9007_HANDLE_DOUBLE_CLICK
This form is called when the user double clicks on a line to drill
down.
     -->P_E_ROW_ID    - Row ID text
     -->P_E_COLUMN_ID - Column ID
     -->P_ES_ROW_NO   - Row number
FORM f9007_handle_double_click USING p_row
                                     p_column
                                     p_row_no.
DATA: lw_output LIKE LINE OF i_output.
Need to check that a subtotal or grand total line has *not been double-clicked, otherwise the report will *produce a short dump!
check p_row+0(1) is initial.
READ TABLE i_output INDEX p_row INTO lw_output.
CASE p_column.
    WHEN 'KNUMA'.
      IF NOT lw_output-knuma IS INITIAL.
        SET PARAMETER ID 'VBO' FIELD lw_output-knuma.
        CALL TRANSACTION 'VBO3' AND SKIP FIRST SCREEN.
      ENDIF.
   ENDCASE.
ENDFORM.                    " F9007_HANDLE_DOUBLE_CLICK
In PBO of the screen,
MODULE status_9001 OUTPUT.
IF o_dockingcontainer IS INITIAL.
   SET HANDLER o_eventreceiver->handle_double_click FOR o_alvgrid.
ENDMODULE.                 " STATUS_9001 OUTPUT
In this I have mentioned double click event.
Similarly you have to do for others.
Regards,
J.Jayanthi

Similar Messages

Double click event in alv oops

Hi,
can any one please help me out... i dont know how to call events in alv oops...so can any one provide me with some help..
My requirment is i have to generate a mail grid containing customer details and if i double click on a customer it should go to the transaction XD03 second screen.....

u have to declae an event like this.
class event_receiver definition.
public section.
    methods handle_double_click
      for event double_click of cl_gui_alv_grid
      importing e_row.
endclass.
then u have to implement it in the implementation
class lcl_event_receiver implementation.
method lmt_handle_double_click.
    perform double_click using e_row
                               tbl_final_display.
endmethod.
endclass.
form double_click
        using fu_e_row             type lvc_s_row
              fu_tbl_final_display type typ_tbl_display.
read table fu_tbl_final_display into l_h_tbl_final_display
                          index fu_e_row-index.
if sy-subrc = 0.
    set parameter id cns_aun field l_h_tbl_final_display-vbeln.
    call transaction cns_trans and skip first screen.
endif.
endform.
hope it will help u

Handle single click event in ALV OOPS

Hi,
I have to display 2 ALV grid...one above the other.
Top ALV will contain Header info and bottom ALV witll display line item.
I am use ALV OOPS.
Now when user will click on the top ALV ...bottom ALV should show corresponding data.
I don't have to use HOTSPOT or Double click event.
How can I handle single click event.
Please guide me..thanks in advance
Regards,
Prasoon

hi,
 for this in ALV OOPS take 2 custom containers( cl_gui_custom_container)in the same screen and on the 1st container display the header data(use set_tale_for_first_display method of class cl_gui_alv_grid).
 On the 2nd screen item data for this use EVENT handling(you want single click). use hotspot_click or button_click events.
for this you have to register the events. the code for that.
CLASS lcl_event_handler DEFINITION .
PUBLIC SECTION .
METHODS:
*--Hotspot click control
handle_hotspot_click
FOR EVENT hotspot_click OF cl_gui_alv_grid
IMPORTING e_row_id e_column_id es_row_no ,
*--To control button clicks
handle_button_click
FOR EVENT button_click OF cl_gui_alv_grid
IMPORTING e_oject e_ucomm .
PRIVATE SECTION.
ENDCLASS.
CLASS lcl_event_handlerIMPLEMENTATION .
*--Handle Hotspot Click
METHOD handle_hotspot_click .
PERFORM handle_hotspot_click USING e_row_id e_column_id es_row_no .
ENDMETHOD .
METHOD handle_button_click .
PERFORM handle_button_click USING e_object e_ucomm .
ENDMETHOD .
ENDCLASS .
DATA gr_event_handler TYPE REF TO lcl_event_handler .
*--Creating an instance for the event handler
CREATE OBJECT gr_event_handler.
*--Registering handler methods to handle ALV Grid events
SET HANDLER gr_event_handler->handle_hotspot_click FOR gr_alvgrid .
SET HANDLER gr_event_handler->handle_button_click FOR gr_alvgrid .
do n't forget to use refresh_table_display
 other wise only the record which you first you clicked will display in the 2nd container.
Reward points for useful Answers

Event handling in alv oops With buttons

Hi Experts
 I have some doubt in ALV OOPS using Events. Could any one please tell me the procedure to how to handle events in oops ( Like interactive reports using events ).
 Thank you
Satyendra.

Hello Satyendra
The following sample report shows you how to handle the event HOTSPOT_CLICK and BUTTON_CLICK.
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: gt_knb1 TYPE STANDARD TABLE OF knb1.
PARAMETERS: p_bukrs TYPE bukrs DEFAULT '2000' OBLIGATORY.
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.
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.
 CALL TRANSACTION 'SU01' AND SKIP FIRST SCREEN.
 WHEN OTHERS.
 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
* 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.
SET PF-STATUS 'STATUS_0100'.
* SET TITLEBAR 'xxx'.
ENDMODULE. " STATUS_0100 OUTPUT
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 .
* 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
 ELSE.
 ls_fcat-hotspot = abap_true.
 ENDIF.
 MODIFY gt_fcat FROM ls_fcat.
ENDLOOP.
ENDFORM. " BUILD_FIELDCATALOG_KNB1
Regards
Uwe

ALV OOPS Double-click event

Hi,
I want to handle the double-click event in ALV grid (OOPs).
The output should be shown in the same fashion as it is shown in SE16 when we double-click on any record in the result set.
i.e. if you have selected the ALV grid display for the Data browser in SE16 and when you double click on any record, the complete record is shown in a window.
I want this in my ALV as well..
Can anyone please suggest how to achieve this?
Regards
s.a.k

Hi siemens.a.k ,
The solution for the issue would be to create a custom screen and add a custom table controller in a container.
In this table controller you map the respective fields required for your output
Now once you are done with data population in the custom controller for ALV grid display using cl_gui_alv_grid_display class...
create events in your custom class to handle the on click event.
If you observe the standard functionality it could be clearly seen that sap has created another screen for the display of records in different view.
You could also replicate the similar thing by creating another screen and populating the required fields into the second screen.
As of now i am providing this information ...I would even try to simulate the scenario at my system.
So once i am done i would update you the same...
Thanks
M.Naveen Kumar....

ALV OOP- Catching the event when the user clicks a cell

Hi Experts,
i have 2 alvs to display using custom containers, now the problem is that i need to make some lines uneditable and some lines editable. On making this i find that ALV does not offer this functionality of selective editable rows, right? I offered a workaround by just popping an error message if a user clicks a row which suppose to be disabled/uneditable. My problem is that how can i catch the single click event in ALV using OOP?
Thanks to replies and points will be given...

hi,
hope this helps.
creating Editable Cells in ALV
Making a column editable in ALV:
IT_FIELDCAT is an internal table which has the structure of the data to be displayed. Each row in this internal table creates a column in ALV. The fieldcat structure has an optional field u2018EDITu2019 which is not required to be passed all the time. By default the column is non-editable. If the value of the field EDIT is u2018Xu2019, that column becomes editable in the display.
Example:
wa_fieldcat-fieldname = 'CHECK'.
wa_fieldcat-edit      = 'X'.
wa_fieldcat-coltext   = 'Delete'.
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
The column DELETE in the ALV display is editable. The corresponding output internal table field name is CHECK.
Making individual cells editable or non-editable:
1.     Include an internal table of type lvc_t_styl in the output internal table (as a field) of the ALV. This inner table is like other output fields of the internal table.
Example:
TYPES: BEGIN OF tt_project,
            check TYPE c,
            status(132) TYPE c,
            it_styletab TYPE lvc_t_styl.
TYPES: END OF tt_project.
2.     This inner internal table controls the style of each cell in the row of the output internal table.
3.     Same like other fields of the output internal table, this style table (inner internal table) should be filled for each row of the table.
4.     The structure of the output internal table.
CHECK     STATUS     IT_STYLETAB
X     ABC     Fieldname     Style
CHECK     Non-editable(MC_STYLE_DISABLED)
STATUS     editable(MC_STYLE_ENABLED)
     CDF     Fieldname     Style
     Non-editable(MC_STYLE_DISABLED)
      wa_stylerow-fieldname = u2018CHECKu2019. -
> Optional
      wa_stylerow-style = cl_gui_alv_grid=>mc_style_disabled. (Non-editable)
      or
      wa_stylerow-style = cl_gui_alv_grid=>mc_style_enabled. (Editable)
      Append wa_stylerow to wa_project-it_styletab.
     Wa_stylerow is a work area for IT_STYLETAB.
       Wa_project is work area for output internal table.
5.     Refresh the inner internal table for each row in outer internal table.
6.     If the fieldname is not provided for the style internal table, the entire row becomes editable or non-editable.
7.     This provides the ability to enable input for a cell dynamically.
8.     The layout of the ALV Grid should also be changed in order to achieve this. The layout has a parameter, u2018STYLENAMEu2019. The name of the style internal table should be given as the value for this field. The layout should be passed in SET_TABLE_FOR_FIRST_DISPLAY.
     Example:
     wa_layout-stylefname = 'IT_STYLETAB'.
reward if useful.
regards
srishti

To set HOTSPOT for a field in ALV-oops and when clecked should call transac

Hi,
I need to set HOTSPOT for a field in O/P list using ALV-oops and when clecked should take me to Transaction VA01. Please help....
Thanks,
Prabhu

Hi,
Please go through this code it may help u.
REPORT zcls_alv_oops MESSAGE-ID z1.
TABLES : mara.
Types Declaration..\
TYPES :
BEGIN OF t_mara,
matnr TYPE matnr,
mtart TYPE mtart,
maktx TYPE maktx,
END OF t_mara,
BEGIN OF t_marc,
matnr TYPE matnr,
werks TYPE werks_d,
mtart TYPE mtart,
maktx TYPE maktx,
END OF t_marc.
Internal Tables Declaration..\
DATA :
i_mara TYPE TABLE OF t_mara,
i_marc TYPE TABLE OF t_marc,
i_fcat1 TYPE lvc_t_fcat,
i_fcat2 TYPE lvc_t_fcat.
Constants Declaration..\
CONSTANTS :
c_cont1 TYPE scrfname VALUE 'CONT1',
c_cont2 TYPE scrfname VALUE 'CONT2'.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME.
SELECT-OPTIONS:
s_matnr FOR mara-matnr NO INTERVALS.
SELECTION-SCREEN SKIP 1.
PARAMETERS :
p_hotspt RADIOBUTTON GROUP r1 DEFAULT 'X',
p_bttn RADIOBUTTON GROUP r1.
SELECTION-SCREEN END OF BLOCK b1.
\* Class forward referncing.
CLASS lcl_rcvr_class DEFINITION DEFERRED.
\* Pointers Declaration..
DATA :
lp_rcvr TYPE REF TO lcl_rcvr_class,
lp_cont1 TYPE REF TO cl_gui_custom_container,
lp_cont2 TYPE REF TO cl_gui_custom_container,
lp_grid1 TYPE REF TO cl_gui_alv_grid,
lp_grid2 TYPE REF TO cl_gui_alv_grid.
\* Local Class Definiton.
CLASS lcl_rcvr_class DEFINITION.
PUBLIC SECTION.
METHODS :
hotspot_click FOR EVENT hotspot_click OF cl_gui_alv_grid
IMPORTING e_row_id e_column_id es_row_no,
handle_double_click FOR EVENT double_click OF cl_gui_alv_grid
IMPORTING e_row e_column.
ENDCLASS.
\* Local Class Implementation.
CLASS lcl_rcvr_class IMPLEMENTATION.
METHOD hotspot_click.
DATA :
wa_mara TYPE t_mara,
wa_marc TYPE t_marc.
DATA :
l_index TYPE sy-tabix.
READ TABLE i_mara INTO wa_mara INDEX e_row_id-index.
IF sy-subrc EQ 0.
REFRESH i_marc.
SELECT matnr
werks
INTO TABLE i_marc
FROM marc
WHERE matnr EQ wa_mara-matnr.
IF sy-subrc EQ 0.
LOOP AT i_marc INTO wa_marc.
l_index = sy-tabix.
wa_marc-mtart = wa_mara-mtart.
wa_marc-maktx = wa_mara-maktx.
MODIFY i_marc FROM wa_marc INDEX l_index
TRANSPORTING mtart maktx.
ENDLOOP.
CALL SCREEN 200.
ELSE.
MESSAGE e121 WITH text-005 wa_mara-matnr.
ENDIF.
ENDIF.
ENDMETHOD.
METHOD handle_double_click.
DATA :
wa_mara TYPE t_mara,
wa_marc TYPE t_marc.
DATA :
l_index TYPE sy-tabix.
READ TABLE i_mara INTO wa_mara INDEX e_row-index.
IF sy-subrc EQ 0.
REFRESH i_marc.
SELECT matnr
werks
INTO TABLE i_marc
FROM marc
WHERE matnr EQ wa_mara-matnr.
IF sy-subrc EQ 0.
LOOP AT i_marc INTO wa_marc.
l_index = sy-tabix.
wa_marc-mtart = wa_mara-mtart.
wa_marc-maktx = wa_mara-maktx.
MODIFY i_marc FROM wa_marc INDEX l_index
TRANSPORTING mtart maktx.
ENDLOOP.
CALL SCREEN 200.
ELSE.
MESSAGE e121 WITH text-005 wa_mara-matnr.
ENDIF.
ENDIF.
ENDMETHOD.
ENDCLASS.
\* Start of Selection
START-OF-SELECTION.
\* Extract the Material Master data for the Input Material.
SELECT a~matnr
a~mtart
b~maktx
INTO TABLE i_mara
FROM mara AS a
INNER JOIN makt AS b
ON a~matnr EQ b~matnr
WHERE a~matnr IN s_matnr
AND b~spras EQ sy-langu.
END-OF-SELECTION.
IF NOT i_mara\[\] IS INITIAL.
\* Call Screen to display the Material Master data.
CALL SCREEN 100.
ELSE.
MESSAGE s121 WITH text-006.
ENDIF.
\*& Module DISP_GRID OUTPUT
\* text
MODULE disp_grid OUTPUT.
\* Build the Field catelog for Material Master data.
PERFORM build_fcat.
\* Display the Material Master data using ALV.
PERFORM disp_alv.
ENDMODULE. " DISP_GRID OUTPUT
\*& Module USER_COMMAND_0100 INPUT
\* text
MODULE user_command_0100 INPUT.
\*when exit or cancel is clicked program has to come out
CASE sy-ucomm.
WHEN 'EXIT' OR 'CANC'.
LEAVE PROGRAM.
WHEN 'BACK'.
LEAVE TO SCREEN 0.
ENDCASE.
ENDMODULE. " USER_COMMAND_0100 INPUT
\*& Form build_fcat
\* text
\* \--> p1 text
\* <-\- p2 text
FORM build_fcat.
DATA : ws_fcat TYPE lvc_s_fcat.
ws_fcat-fieldname = 'MATNR'.
ws_fcat-scrtext_m = text-001.
ws_fcat-tabname = 'I_MARA'.
IF p_hotspt EQ 'X'.
ws_fcat-hotspot = 'X'.
ENDIF.
APPEND ws_fcat TO i_fcat1.
CLEAR ws_fcat.
ws_fcat-fieldname = 'MTART'.
ws_fcat-scrtext_m = text-002.
ws_fcat-tabname = 'I_MARA'.
APPEND ws_fcat TO i_fcat1.
CLEAR ws_fcat.
ws_fcat-fieldname = 'MAKTX'.
ws_fcat-scrtext_m = text-003.
ws_fcat-tabname = 'I_MARA'.
APPEND ws_fcat TO i_fcat1.
CLEAR ws_fcat.
ENDFORM. " build_fcat
\*& Form disp_alv
\* text
\* \--> p1 text
\* <-\- p2 text
FORM disp_alv.
IF lp_cont1 IS INITIAL.
\* Create the Container Object of Material Master.
CREATE OBJECT lp_cont1
EXPORTING
container_name = c_cont1
EXCEPTIONS
cntl_error = 1
cntl_system_error = 2
create_error = 3
lifetime_error = 4
lifetime_dynpro_dynpro_link = 5
others = 6 .
IF sy-subrc NE 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
\* Create the Object for Grid of Material Master.
CREATE OBJECT lp_grid1
EXPORTING
i_parent = lp_cont1
EXCEPTIONS
error_cntl_create = 1
error_cntl_init = 2
error_cntl_link = 3
error_dp_create = 4
others = 5.
IF sy-subrc NE 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
\* Dipslay Material Master data by calling method.
CALL METHOD lp_grid1->set_table_for_first_display
CHANGING
it_outtab = i_mara
it_fieldcatalog = i_fcat1
EXCEPTIONS
invalid_parameter_combination = 1
program_error = 2
too_many_lines = 3
OTHERS = 4.
IF sy-subrc NE 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
\* Set Handler for the Hot Spot Event.
CREATE OBJECT lp_rcvr.
IF p_hotspt EQ 'X'.
SET HANDLER lp_rcvr->hotspot_click FOR lp_grid1.
ELSE.
SET HANDLER lp_rcvr->handle_double_click FOR lp_grid1.
ENDIF.
ENDIF.
ENDIF.
ENDIF.
ENDIF.
ENDFORM. " disp_alv
\*& Module STATUS_0100 OUTPUT
\* text
MODULE status_0100 OUTPUT.
SET PF-STATUS 'MAIN_STAT'.
SET TITLEBAR 'T_100'.
ENDMODULE. " STATUS_0100 OUTPUT
\*& Module STATUS_0200 OUTPUT
\* text
MODULE status_0200 OUTPUT.
SET PF-STATUS 'PLANT_STAT'.
SET TITLEBAR 'T_200'.
ENDMODULE. " STATUS_0200 OUTPUT
\*& Module DISP_GRID_plant OUTPUT
\* text
MODULE disp_grid_plant OUTPUT.
\* Build the Field catelog for Material Plant data.
PERFORM build_fcat_plant.
\* Display the Material Master Plant data using ALV.
PERFORM disp_alv_plant.
ENDMODULE. " DISP_GRID_plant OUTPUT
\*& Module USER_COMMAND_0200 INPUT
\* text
MODULE user_command_0200 INPUT.
\*when exit or cancel is clicked program has to come out
CASE sy-ucomm.
WHEN 'EXIT' OR 'CANC'.
LEAVE PROGRAM.
WHEN 'BACK'.
LEAVE TO SCREEN 0.
ENDCASE.
ENDMODULE. " USER_COMMAND_0200 INPUT
\*& Form build_fcat_plant
\* text
\* \--> p1 text
\* <-\- p2 text
FORM build_fcat_plant.
DATA : ws_fcat TYPE lvc_s_fcat.
ws_fcat-fieldname = 'MATNR'.
ws_fcat-scrtext_m = text-001.
ws_fcat-tabname = 'I_MARC'.
APPEND ws_fcat TO i_fcat2.
CLEAR ws_fcat.
ws_fcat-fieldname = 'WERKS'.
ws_fcat-scrtext_m = text-004.
ws_fcat-tabname = 'I_MARC'.
APPEND ws_fcat TO i_fcat2.
CLEAR ws_fcat.
ws_fcat-fieldname = 'MTART'.
ws_fcat-scrtext_m = text-002.
ws_fcat-tabname = 'I_MARC'.
APPEND ws_fcat TO i_fcat2.
CLEAR ws_fcat.
ws_fcat-fieldname = 'MAKTX'.
ws_fcat-scrtext_m = text-003.
ws_fcat-tabname = 'I_MARC'.
APPEND ws_fcat TO i_fcat2.
CLEAR ws_fcat.
ENDFORM. " build_fcat_plant
\*& Form disp_alv_plant
\* text
\* \--> p1 text
\* <-\- p2 text
FORM disp_alv_plant.
IF lp_cont2 IS INITIAL.
\* Create the Container Object of Material Plant data.
CREATE OBJECT lp_cont2
EXPORTING
container_name = c_cont2
EXCEPTIONS
cntl_error = 1
cntl_system_error = 2
create_error = 3
lifetime_error = 4
lifetime_dynpro_dynpro_link = 5
others = 6.
IF sy-subrc NE 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
\* Create the Object for Grid of Material Plant data.
CREATE OBJECT lp_grid2
EXPORTING
i_parent = lp_cont2
EXCEPTIONS
error_cntl_create = 1
error_cntl_init = 2
error_cntl_link = 3
error_dp_create = 4
others = 5.
IF sy-subrc NE 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
\* Dipslay Material Plant data by calling method.
CALL METHOD lp_grid2->set_table_for_first_display
CHANGING
it_outtab = i_marc
it_fieldcatalog = i_fcat2
EXCEPTIONS
invalid_parameter_combination = 1
program_error = 2
too_many_lines = 3
OTHERS = 4.
IF sy-subrc NE 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDIF.
ENDIF.
ELSE.
\* Call method 'REFRESH_TABLE_DISPLAY' to refresh the grid data.
CALL METHOD lp_grid2->refresh_table_display.
ENDIF.
ENDFORM. " disp_alv_plant

Events in Alv

hi
Experts
   i hav e requirement on   report in alv oops .
in this , let me know the details   how to   display the events liken "top-of-page", end of page
and   list header , list footer in oops,
please provide the suitable code
Regards
Spandana

hi,
Check this link for Events in Alv
https://www.sdn.sap.com/irj/sdn/wiki?path=/pages/viewpage.action?pageId=37715
http://howforge.com/abap-4-example-code-alv-grid-control-by-applying-object-cl-gui-alv-grid
Check out the following link for top_of_page event in OOPs ALV.
Best code
/people/vijaybabu.dudla/blog/2006/07/21/topofpage-in-alv-using-clguialvgrid
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e8a1d690-0201-0010-b7ad-d9719a415907
Reward All Helpfull Answers
Regards
Fareedas

Problem while placing a button in the Output using ALV OOPs

Hi,
I am using ALV OOPs to display report output.
In the toolbar i have to palce an update button and if i click on that update it should then call the selection screen 500 .
So,please help me to achieve this using ALV OOPs.
THANKS & REGARDS,
Kiranmai.

Hi,
you can use set pf-status statement with the OOPs' concept where in you will have to give this in the events table and pass it to the method to display the alv ...
Regards,
Siddarth

F4 link in ALV OOPs

I am using ALV OOPs. I need to link F4 help to field in Selection Screen, Instead of normal method F4IF_INT_TABLE_VALUE_REQUEST, I need to implement this in ALV OOPs. Can anybody help on this.
Regards,
Naseer.

Hi Naseer!
At Selection Screen you don't call method to create the ALV OO yet.
So you can you the FM 'F4IF_INT_TABLE_VALUE_REQUEST' in the event AT SELECTION-SCREEN ON VALUE-REQUEST FOR your_parameter.
I hope its helpful.

Normal ALVs vrs ALV OOPs

I am using ALV OOPs. In ALV OOPs Appl tool bar is working by default when we create PF-STATUS. But in case of normal ALVs we need to write code for SY-UCOMM in PAI. why this happens, can anybody give tips.
Regards,
Naseer.

Hi Naseer,
In Normal ALV we use Function mnodule and in OOPs we use classes and methods.
In Normal ALV we cannot place grids on screens but in OOALV we can place grids on screens.
we can insert logos in OOPS ALV.
see the code below
for displaying LOGO in ALV GRID CONTROL, we work with
Predefined global class. CL_GUI_ALV_TREE_SIMPLE. FOR
displaying LOGO. AND we use CL_GUI_CUSTOM_CONTAINTER for
identifies the location where we r goinh to display.
DECLARATIONS;
TYPE-POOLS: SDYDO, SLIS.
DATA: L_LOGO TYPE SDYDO_VALUE, FOR DISPLAYING LOGO
L_LIST TYPE SLIS_T_LISTHEADER. FOR LIST HEADING
DATA: LOGO TYPE SCRFNAME VALUE SLOGO,
CONTAINER TYPE REF TO CL_GUI_CUSTOM_CONTAINER,
LOGO1 TYPE REF TO CL_GUI_ALV_TREE_SIMPLE.
CREATE INSTANCE FOR ABOVE DEFINED CLASSES IN PBO EVENT
OF SCREEN FLOW LOGIC.
IF CONTAINER IS INITIAL.
CREATE OBJECT CONTAINER EXPORTING CONTAINER_NAME =
LOGO.
CREATE OBJECT LOGO1 EXPORTING I_PARENT = CONTAINER.
NOW CALL THE METHOD FOR DISPLAYING LOGO IN GRID CONTROL
CALL METHOD LOGO->CREATE_REPORT_HEADER
EXPORTING
I_LIST_COMMENTARY = L_LIST
I_LOGO = HERE PASS WHERE LOGO EXISTING.
THE ABOVE METHOD EXISTING
Please reward points if helpful..
Cheers,
Chaitanya.

How to do it in ALV OOPS

Hi
Im using ALV OOPS.o/p I have 10 records with checkbox(at user command I have to select record selected by check box). Now on the menu bar I hav a button for "SELECT ALL". If "selected all" 10 recored will be selected. If I filter upon some criteria no. of records will be 3..Now in GUI if I select SELECT all it will display 3 records r selected, but I have to process further internally ,,,but internally 10 records are selected. So how to write code for that is after filterring 3 records r selected and I "select all"..only 3 records will be selected instead of 10?
Part of my code like this..
SELECT all
CALL METHOD G_GRID->CHECK_CHANGED_DATA
    IMPORTING
      E_VALID = L_VALID.
IF L_VALID EQ 'X'.
    LOOP AT PT_OUTTAB INTO LS_OUTTAB.
DATA LS_CELLTAB TYPE LVC_S_STYL.
LOOP AT PS_OUTTAB-CELLTAB INTO LS_CELLTAB.
    IF LS_CELLTAB-FIELDNAME = 'CHECKBOX'.
      IF LS_CELLTAB-STYLE EQ CL_GUI_ALV_GRID=>MC_STYLE_DISABLED.
        P_LOCKED = 'X'.
      ELSE.
        P_LOCKED = SPACE.
      ENDIF.
    ENDIF.
ENDLOOP.
      IF L_LOCKED IS INITIAL
         AND NOT LS_OUTTAB-CHECKBOX EQ '-'.
        LS_OUTTAB-CHECKBOX = 'X'.
      ENDIF.
      MODIFY PT_OUTTAB FROM LS_OUTTAB.
    ENDLOOP.
    CALL METHOD G_GRID->REFRESH_TABLE_DISPLAY.
ENDIF.

Hello Kaushik
Using method go_grid->GET_FILTERED_ENTRIES you get an index list of the filtered entries.
DATA: lt_filtered     TYPE lvc_t_fidx,
          ld_indx        LIKE LINE OF lt_filtered.
CALL METHOD go_grid->GET_FILTERED_ENTRIES
     IMPORTING
       ET_FILTERED_ENTRIES = lt_filtered.
LOOP AT lt_filtered INTO ld_indx.
    READ TABLE gt_outtab INTO ls_outtab INDEX ld_indx.
ENDLOOP.
Regards
Uwe

About double click event in ALV report

Hi all,
I want to program a double-click event in ALV reprot.
I am not suppose to use module pool approach for the same.
If a user double clicks on the any of the row of ALV report, the transaction should get called.
Again, I am using function 'REUSE_ALV_GRID_DISPLAY' for displaying ALV.
Can you please help me to solve this?
Thanks,
-Siddhi

Hi Sidhi,
You can do it easily by using Reuse_ALV_GRID_DISPALY.
The User Command subroutine which you pass to this function module in that you can check which field is selected and what is the value of that and also you can get the table index.
I am giving you a code example where interactivity of ALV report is done .
*& Report ZRAIL_LOT_REPORT
REPORT zrail_lot_report.
TABLES :qals,aufk.
TYPE-POOLS:slis.
TYPES:BEGIN OF x_lot,
 sel(1) TYPE c, "SELECTION
 prueflos TYPE qals-prueflos, "INSPECTION LOT NUMBER
 werk TYPE qals-werk, "PLANT
 losmenge TYPE qals-losmenge, "LOT QUANTITY
 mengeneinh TYPE qals-mengeneinh, "BASE UNIT OF MEASURE FOR THE INSPECTION LOT QUANTITY
 matnr TYPE qals-matnr, " MATERIAL NO. ATTACHED TO ORDER
 zzequnr TYPE qals-zzequnr, "EQUIPMENT NO.
 zzassembly TYPE qals-zzassembly, "ASSEMBLY
 herkunft TYPE qals-herkunft, "INSPECTION LOT ORIGIN
 aufnr TYPE qals-aufnr, "ORDER NO.
 sttxt TYPE qals_d02-sttxt, "LOT STATUS
 objnr TYPE qals-objnr, "OBJECT NUMBER
 enstehdat TYPE qals-enstehdat, "lot creation date
 pruefer TYPE qamr-pruefer, "Name of the Inspector
 END OF x_lot.
TYPES:BEGIN OF x_ordmat,
 aufnr TYPE aufk-aufnr, "Order No.
 equnr TYPE afih-equnr, "Equipment No. attached to Order
 zmatnr TYPE aufk-zmatnr, "Material No. attached to Order
 bautl TYPE afih-bautl, "Assembly attached to Order
 END OF x_ordmat.
TYPES:BEGIN OF x_status,
 objnr TYPE jest-objnr,
 stat TYPE jest-stat,
 txt04 TYPE tj02t-txt04,
 END OF x_status.
DATA:it_qals TYPE STANDARD TABLE OF x_lot,
 wa_qals TYPE x_lot.
DATA:it_ordmat TYPE TABLE OF x_ordmat,
 wa_ordmat TYPE x_ordmat.
DATA:it_status TYPE STANDARD TABLE OF x_status,
 wa_status TYPE x_status.
DATA:mytabix TYPE sy-tabix.
DATA: wa_layout TYPE slis_layout_alv,
 wa_fieldcat TYPE slis_fieldcat_alv,
 it_fieldcat TYPE TABLE OF slis_fieldcat_alv,
 it_fcat TYPE TABLE OF slis_fieldcat_alv.
DATA:mytabix1 TYPE sy-tabix.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS: s_werks FOR qals-werk,
 s_zmatnr FOR aufk-zmatnr,
 s_assbly FOR qals-zzassembly,
 s_equnr FOR qals-zzequnr,
 s_lotor FOR qals-herkunft,
 s_lotdat FOR qals-enstehdat.
SELECTION-SCREEN END OF BLOCK b1.
INITIALIZATION.
s_lotdat-low = sy-datum - 7.
s_lotdat-high = sy-datum.
APPEND s_lotdat.
START-OF-SELECTION.
PERFORM get_data_qals.
PERFORM build_fieldcat.
PERFORM display_data.
EXIT.
END-OF-SELECTION.
*& Form get_data_qals
 text
--> p1 text
<-- p2 text
FORM get_data_qals .
IF it_qals[] IS INITIAL.
 SELECT a~prueflos
 a~werk
 a~losmenge
 a~mengeneinh
 a~zzequnr
 a~zzassembly
 a~herkunft
 a~aufnr
 a~objnr
 a~matnr
 a~enstehdat
 b~pruefer
 FROM qals AS a INNER JOIN qamr AS b
 ON aprueflos = bprueflos
 INTO CORRESPONDING FIELDS OF TABLE it_qals
 WHERE werk IN s_werks
 AND zzassembly IN s_assbly
 AND zzequnr IN s_equnr
 AND herkunft IN s_lotor
 AND enstehdat IN s_lotdat.
ENDIF.
IF it_ordmat[] IS INITIAL.
 SELECT a~aufnr
 a~zmatnr
 b~bautl
 b~equnr
 FROM aufk AS a INNER JOIN afih AS b
 ON aaufnr = baufnr
 INTO CORRESPONDING FIELDS OF TABLE it_ordmat FOR ALL ENTRIES IN it_qals
 WHERE a~aufnr = it_qals-aufnr
 AND zmatnr IN s_zmatnr.
ENDIF.
IF it_status[] IS INITIAL.
 SELECT a~objnr
 a~stat
 b~txt04
 FROM tj02t AS b
 INNER JOIN jest AS a ON bistat = astat
 INTO CORRESPONDING FIELDS OF TABLE it_status FOR ALL ENTRIES IN it_qals
 WHERE a~objnr = it_qals-objnr
 AND b~spras = sy-langu
 AND a~inact = space.
ENDIF.
LOOP AT it_qals INTO wa_qals.
 mytabix = sy-tabix.
 READ TABLE it_ordmat INTO wa_ordmat WITH KEY aufnr = wa_qals-aufnr.
 IF sy-subrc = 0.
 IF wa_qals-herkunft = '14'.
 wa_qals-matnr = wa_ordmat-zmatnr.
 wa_qals-zzequnr = wa_ordmat-equnr.
 wa_qals-zzassembly = wa_ordmat-bautl.
 MODIFY it_qals FROM wa_qals INDEX mytabix TRANSPORTING matnr zzassembly zzequnr.
 ENDIF.
 ENDIF.
 LOOP AT it_status INTO wa_status WHERE objnr = wa_qals-objnr.
 CONCATENATE wa_qals-sttxt wa_status-txt04 INTO wa_qals-sttxt SEPARATED BY space.
 CLEAR :wa_status.
 ENDLOOP.
 MODIFY it_qals FROM wa_qals INDEX mytabix TRANSPORTING sttxt.
 CLEAR :wa_qals,wa_ordmat,mytabix.
ENDLOOP.
IF s_zmatnr[] IS NOT INITIAL.
 DELETE it_qals WHERE matnr IS INITIAL.
ENDIF.
ENDFORM. " get_data_qals
*& Form build_fieldcat
 text
--> p1 text
<-- p2 text
FORM build_fieldcat .
wa_layout-zebra = 'X'.
wa_layout-colwidth_optimize = 'X'.
wa_layout-box_fieldname = 'SEL'.
wa_layout-box_tabname = 'IT_QALS'.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
 EXPORTING
 I_PROGRAM_NAME =
 i_internal_tabname = 'IT_QALS'
 i_structure_name = 'QALS_D02'
 I_CLIENT_NEVER_DISPLAY = 'X'
 I_INCLNAME =
 I_BYPASSING_BUFFER =
 I_BUFFER_ACTIVE =
 CHANGING
 ct_fieldcat = it_fieldcat
IF sy-subrc = 0.
 LOOP AT it_fieldcat INTO wa_fieldcat.
 CASE wa_fieldcat-fieldname .
 WHEN 'PRUEFLOS'.
 wa_fieldcat-col_pos = 1.
 wa_fieldcat-hotspot = 'X'.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'WERK'.
 wa_fieldcat-col_pos = 3.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'LOSMENGE'.
 wa_fieldcat-col_pos = 4.
 wa_fieldcat-no_out = ''.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'MENGENEINH'.
 wa_fieldcat-col_pos = 5.
 wa_fieldcat-no_out = ''.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'ZZEQUNR'.
 wa_fieldcat-col_pos = 6.
 wa_fieldcat-no_out = ''.
 wa_fieldcat-hotspot = 'X'.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'ZZASSEMBLY'.
 wa_fieldcat-col_pos = 7.
 wa_fieldcat-no_out = ''.
 wa_fieldcat-hotspot = 'X'.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'HERKUNFT'.
 wa_fieldcat-col_pos = 8.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'AUFNR'.
 wa_fieldcat-col_pos = 9.
 wa_fieldcat-hotspot = 'X'.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'ENSTEHDAT'."enstehdat
 wa_fieldcat-col_pos = 10.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'STTXT'.
 wa_fieldcat-col_pos = 12.
 wa_fieldcat-hotspot = 'X'.
 APPEND wa_fieldcat TO it_fcat.
 WHEN OTHERS.
 ENDCASE.
 CLEAR wa_fieldcat.
 ENDLOOP.
 wa_fieldcat-fieldname = 'MATNR'.
 wa_fieldcat-tabname = 'IT_QALS'.
 wa_fieldcat-col_pos = 2.
 wa_fieldcat-ref_tabname = 'AUFK'.
 wa_fieldcat-hotspot = 'X'.
 wa_fieldcat-seltext_l = 'Material No.'.
 APPEND wa_fieldcat TO it_fcat.
 wa_fieldcat-fieldname = 'PRUEFER'.
 wa_fieldcat-tabname = 'IT_QALS'.
 wa_fieldcat-col_pos = 11.
 wa_fieldcat-ref_tabname = 'QAMR'.
 wa_fieldcat-seltext_l = 'Name of the Inspector'.
 APPEND wa_fieldcat TO it_fcat.
ENDIF.
ENDFORM. " build_fieldcat
*& Form display_data
 text
--> p1 text
<-- p2 text
FORM display_data .
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 i_callback_program = 'ZRAIL_LOT_REPORT'
I_CALLBACK_PF_STATUS_SET = ' '
 i_callback_user_command = 'USER_COMMAND'
 is_layout = wa_layout
 it_fieldcat = it_fcat
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_DEFAULT = 'X'
I_SAVE = ' '
IS_VARIANT =
IT_EVENTS =
IT_EVENT_EXIT =
IS_PRINT =
IS_REPREP_ID =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
I_HTML_HEIGHT_TOP = 0
I_HTML_HEIGHT_END = 0
IT_ALV_GRAPHICS =
IT_HYPERLINK =
IT_ADD_FIELDCAT =
IT_EXCEPT_QINFO =
IR_SALV_FULLSCREEN_ADAPTER =
 TABLES
 t_outtab = it_qals
EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " display_data
*& Form USER_COMMAND
 text
 -->R_UCOMM text
 -->RS_SELFIELD text
FORM user_command USING r_ucomm TYPE sy-ucomm rs_selfield TYPE slis_selfield.
CASE rs_selfield-fieldname .
 WHEN 'PRUEFLOS'.
 SET PARAMETER ID 'QLS' FIELD rs_selfield-value.
 CALL TRANSACTION 'QA03' AND SKIP FIRST SCREEN.
 WHEN 'ZZEQUNR'.
 SET PARAMETER ID 'EQN' FIELD rs_selfield-value.
 CALL TRANSACTION 'IE03' AND SKIP FIRST SCREEN.
 WHEN 'ZMATNR'.
 SET PARAMETER ID 'MAT' FIELD rs_selfield-value.
 CALL TRANSACTION 'MM03' AND SKIP FIRST SCREEN.
 WHEN 'ZZASSEMBLY'.
 SET PARAMETER ID 'MAT' FIELD rs_selfield-value.
 CALL TRANSACTION 'MM03' AND SKIP FIRST SCREEN.
 WHEN 'AUFNR'.
 SET PARAMETER ID 'ANR' FIELD rs_selfield-value.
 CALL TRANSACTION 'IW33' AND SKIP FIRST SCREEN.
 WHEN 'STTXT'.
 MOVE rs_selfield-tabindex TO mytabix1.
 PERFORM show_status.
ENDCASE.
ENDFORM. "USER_COMMAND
*& Form show_status
 text
--> p1 text
<-- p2 text
FORM show_status .
DATA:it_systat TYPE TABLE OF bapi2045ss,
 wa_sysstat TYPE bapi2045ss,
 it_bapi2045us TYPE TABLE OF bapi2045us.
DATA:it_fsys TYPE TABLE OF slis_fieldcat_alv.
DATA:insplot TYPE bapi2045d_il0-insplot.
DATA:language TYPE bapi2045la.
CLEAR wa_qals.
READ TABLE it_qals INTO wa_qals INDEX mytabix1.
insplot = wa_qals-prueflos.
language-langu = sy-langu.
CALL FUNCTION 'BAPI_INSPLOT_GETSTATUS'
 EXPORTING
 number = insplot
 language = language
 TABLES
 system_status = it_systat
 user_status = it_bapi2045us.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
 EXPORTING
 i_program_name = 'ZRAIL_LOT_REPORT'
 i_internal_tabname = 'IT_SYSTAT'
 i_structure_name = 'BAPI2045SS'
 CHANGING
 ct_fieldcat = it_fsys.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 i_callback_program = 'ZRAIL_LOT_REPORT'
 it_fieldcat = it_fsys
 TABLES
 t_outtab = it_systat.
ENDFORM. " show_status
IIn the subrouitne the User command the Parameter rs_selfield will give you the selected or clicked field and its value its record no .
I hope this will help you.

How to Trigger SY-UCOMM User Event in ALV

Hi Folks,
Currently I have a classic ALV report where I need to remove all the standard ALV buttons and replace it with one custom button. Given that, there is a parameter in REUSE_ALV_GRID_DISPLAY that deals with the user command event. But during the debug/execution of the custom button, the value of sy-ucomm(R_UCOMM in my example below), is always blank.
Moreover, I did some relevant search here in SDN also before I paste my F1 here. If you're going to take a look at my code below, it's exactly the same as what the other relevant topic in user event in ALV.
PERFORM pf_status_kanban USING rt_extab.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      i_callback_program       = w_repid
      i_callback_top_of_page   = 'F_TOPOF_PAGE'
      i_callback_pf_status_set = 'PF_STATUS_KANBAN' "Exclude ALV standard buttons
      i_callback_user_command = 'F_USER_COMMAND'     "Subroutine for SY-UCOMM
*      i_callback_top_of_page   = 'TOP_OF_PAGE'
      is_layout                = t_alv_layout
      it_fieldcat              = t_alv_fcat[]
      it_sort                  = t_alv_sort
      is_variant               = t_gs_variant
      it_events                = t_events            "Events for AT USER-COMMAND
*      IT_EVENT_EXIT            = 'AT USER-COMMAND'
    TABLES
      t_outtab                 = t_output.
FORM F_USER_COMMAND USING    p_r_ucomm   LIKE sy-ucomm
                              rs_selfield TYPE slis_selfield.
CASE r_ucomm.
    WHEN 'DOWNLOAD'.
      PERFORM f_generate_col USING t_output.
    WHEN OTHERS.
ENDCASE.
ENDFORM.                    " F_USER_COMMAND
FORM F_USER_COMMAND USING    p_r_ucomm   LIKE sy-ucomm
                              rs_selfield TYPE slis_selfield.
CASE r_ucomm.
*    WHEN 'EXCEL'.
*      PERFORM f_generate_col USING t_output.
    WHEN 'DOWNLOAD'.
      PERFORM f_generate_col USING t_output.
    WHEN OTHERS.
ENDCASE.
ENDFORM.                    " F_USER_COMMAND
Thanks and regards,
Jaime

Hi Martin,
Yes, I ensure that the function code in my custom button is exactly the same as the condition for the sy-ucomm.
The call routine for the PF_STATUS_KANBAN is just a test since it seems like Iu2019m chasing a phantom issue here.
Yes, w_repid is set correctly.
DATA:
w_repid LIKE sy-repid.                                              "Report ID.
INITIALIZATION.
w_repid = sy-repid.
It seems like the documentation im reading
Parameter R_UCOMM contains the function code triggered. is not happening as expected...
Thanks.
Jaime
Edited by: Jaime Cabanban on May 7, 2009 10:16 AM

Possible max no. of events in alv

Hi
is there any maximum no of events possible in ALV reporting.
i.e. what is the maximum no of events of alv possible in one program.

Hi ,
The possible events in ALV are,
'ITEM_DATA_EXPAND',
'REPREP_SEL_MODIFY',
'CALLER_EXIT',
'USER_COMMAND',
'TOP_OF_PAGE',
'DATA_CHANGED',
'TOP_OF_COVERPAGE',
'END_OF_COVERPAGE',
'FOREIGN_TOP_OF_PAGE',
'FOREIGN_END_OF_PAGE',
'PF_STATUS_SET',
'LIST_MODIFY',
'TOP_OF_LIST',
'END_OF_PAGE',
'END_OF_LIST',
'AFTER_LINE_OUTPUT',
'BEFORE_LINE_OUTPUT',
'SUBTOTAL_TEXT',
'CONTEXT_MENU'.
Regards,
Balakumar.G.
Reward Points if helpful.

EVENTS IN ALV OOPS

Similar Messages

Maybe you are looking for