Wrong messagetype while processing in an alv grid event

Hello,
a brief discription of my problem:
I am processing a standard SAP form "PERIODE_PRUEFEN" which calls the function "READ_CUSTOMIZED_MESSAGE". The routine is called inside an event-handler of the ALV Grid event 'user_command'. The messagetype is selected from a customising table 'T100C'. Despite the messagetype 'W' the program is always aborted with an 'E' message.
What I have tried so far:
1. I debugged the SAP standard transaction 'fb08' which runs exactly the same functions with the same values and it works.
2. I changed the messagetype in the debugger - no success
3. I searched the SAP notes, but theres nothing about my problem
I guess the problem is somewhere in the ALV Grid event, because this is the only difference between the SAP standard an my program. Maybe the message is processed wrong while beeing called within an event.
It would be great to get some useful hints to solve this problem

Hi,
The ABAP runtime environment handles messages according to the type declared in the MESSAGE statement and the context in which the message was sent.
The behaviour of message type 'W' in a dialog is different from a report program.
Run demo program DEMO_MESSAGES, select Main Program, Type 'W' and execute. You will get an error message instead of warning message.
This behaviour is well documeneted in the on-line help for MESSAGE statement.
Regards,
Rao A

Similar Messages

Freeze toolbar while scrolling down in ALV grid using OOPS

Hi,
My program is showing few products in ALV grid using OOPS. But If I scroll down to select a product, then I cant see the toolbar on which I have to press a button using selected product. Is there any way to freeze toolbar while scrolling down also.
As of now I have to scroll up after selecting product and then press the button on toolbar.
Regards,
Seema
Edited by: Seema Naharia on Feb 23, 2012 9:17 AM

Hi ,
You may have to set handler for the toolbars. Check class cl_gui_alv_grid for the events toolbar.
Or just for a try, since your problem is only when scrolling,you can use set_visible_row_count to -1 , so that data will appear in same view without the need to scroll.
Regards,
Ramya

Problem While Saving the editable ALV GRID

Dear Experts,
I have a scenario in which i am display the ALV(using class) with some data in the custom container of module pool screen in the non-editable mode.Also i have save and edit buttons.If i click the edit button i have written the code to edit the some columns in the ALV grid, it is working fine.After editing it,when i click the save button then ALV has to refreshed with edited data and then it should go to non editable mode but it is not working.I have written the code for changing the editable ALv to non editable mode as follows :
call method c_alvgd->set_ready_for_input
    exporting
      i_ready_for_input = 0.
*****Row and column of the alv are refreshed after changing values
stable-row = 'X'.
stable-col = 'X'.
*REfreshed ALV display with the changed values
*This ALV is non editable and contains new values
call method c_alvgd->refresh_table_display
    exporting
      is_stable = stable
    exceptions
      finished = 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.
Could you Suggest me solution for this issue ?
Thanks & Regards,
R.Dhineshraj.

Dhinesh,
I suppose that you are able to get your changes values on screen but not able to get your field in DISPLAY mode from editable mode, let me know if this is not your problem.
When you press SAVE, after the PAI, again PBO will run and hence the editable code for that field will overwrite which will keep it editable.
So, do something like this.
data: gv_edit value 'X'..... "global variable in TOP include
PBO....
loop at ...
if gv_edit = 'X'.
CALL METHOD lo_alv->set_ready_for_input
EXPORTING
    i_ready_for_input = 1.
else.
CALL METHOD lo_alv->set_ready_for_input
EXPORTING
    i_ready_for_input = 0.
endif.
endloop.
PAI.
when 'SAVE'.
gv_edit = space.
When 'EDIT'.
gv_edit = 'X'.
Regards,
Diwakar

CL_SALV_BS_TT_RESULT_TABLE====CP error while downloading data from ALV grid

Hi ,
I am facing a problem when ever i am going to donload data from ALV grid to excel file.I am getting CL_SALV_BS_TT_RESULT_TABLE====CP error in GET_CELL_VALUE. Could you please provide me is there any OSS note or any patch required to solve this issue.
Thanks in Advance,
Venkatarao.

Hi,
Just refer to OSS note 1356898 for guidelines.
Regards,
Vasanth

ALV Grid: event for user return in ALV Grid Control

Hi developers,
i'm wanna do something after a user has pressed the return button in a alv grid control. For that i need probably a event. But i can not find a proper event in the documentation. Could one of you guys help me?
Best regards christian

Hi Christian
ALV grid is an encapsulated object, so it seems there is no way, you ought to implement the data_changed event. So if you want to make bulk data input and after trigger the event by pressing the return key, you should make the ALV Grid get your changes after pressing the key but not after a cell change of a modified cell.
To set this attribute:
CALL METHOD gr_alvgrid->register_edit_event
EXPORTING i_event_id = cl_gui_alv_grid=>mc_evt_enter .
This way "data_changed" event will be triggered whenever you press the return key while editing.
For some more information you can also refer to the tutorial <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/an%20easy%20reference%20for%20alv%20grid%20control.pdf">"An Easy Reference for ALV Grid Control"</a>.
Regards
*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

Error While processing the COBRA qualified Life event

Hi All,
We have setup the Termination Life event as a COBRA qualifying life event.
Also setup the a new monthly payroll as the default payroll and set the benefit assignment to Yes at BG level.
I created an employee on 18 aug 2010 , processed new hire life event and enrolled that employee into the COBRA plan named "Be well Medical Plan".
Then When I terminated the employee as on 18oct2010, While Processing The Termination life event, I am getting an Error saying “When determining pay periods, a payroll Id is required. This error has occurred in the following package : ben_distribute_rates.get_periods_between. "
When I searched for this error in metalink ,it says it does not have a payroll id ,but when I check on 19oct2010 using the People->Total Comp Participation->Person Benefits Assignment window, he has got the default payroll attached to his benefits assignment.
Could you please help me to reslove this issue?
Your help is greatly appreciated.
Thank you,
Anuradha

Hi Anuradha,
This error comes in many scenarios and there are bug fixes also for them. Please check on all patches available for you apps patchset level having the file benelmen.pkb. You may find a fix for it. (This was a common issue sometime back with suspended/terminated assignments) Also, I suggest logging a SR with oracle asap if your terminated assignment and also the benefits assignment have the correct payrolls attached.
Regards,
Vinayaka

Capturing the ALV Grid Event

Hi Experts,
I am working on ALV Grid , Data is Displayed in Grid well , But Can Any one please tell me how can i capture the event (back,exit and cancel) which is persent on standard toolbar on ALV Gried output .
Rgds,
Premraj

Hello PremRaj ,
Please find an dummy program to capture the events below:
TYPE-POOLS slis.
DATA: ITAB_EVENTS TYPE slis_t_event,
      WA_EVENTS TYPE SLIS_ALV_EVENT.
DATA: IT_END TYPE SLIS_T_LISTHEADER,
      WA_END TYPE SLIS_LISTHEADER.
** This function module will get all the events present in alv into internal table itab_events*
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
I_LIST_TYPE           = 0
IMPORTING
   ET_EVENTS             = ITAB_EVENTS
EXCEPTIONS
LIST_TYPE_WRONG       = 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.
** With this read table statement itab_events is read for the desired event*+
READ TABLE itAB_eventS INTO wa_eventS WITH KEY name = 'END_OF_LIST'.
wa_eventS-form = 'END'.
MODIFY itAB_eventS FROM wa_eventS INDEX sy-tabix.
CLEAR wa_eventS.
*Pass the ITAB_EVENTS created in this Function Module
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
    IT_EVENTS                         = ITAB_EVENTS
IMPORTING
   E_EXIT_CAUSED_BY_CALLER           =
   ES_EXIT_CAUSED_BY_USER            =
   TABLES
     t_outtab                          = it_tab
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.
*READ TABLE itAB_eventS INTO wa_eventS WITH KEY name = 'END_OF_LIST'.
wa_eventS-form = 'END'.
MODIFY itAB_eventS FROM wa_eventS INDEX sy-tabix.
CLEAR wa_eventS.
*in these statements ,the second line will automatically try to call subroutine with name end.
FORM END.
WA_END-TYP = 'S'.
WA_END-KEY = TEXT-004.
WA_END-INFO = SY-DATUM.
APPEND WA_end TO IT_END.
CLEAR WA_END.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
    it_list_commentary       = IT_END
I_LOGO                   =
I_END_OF_LIST_GRID       =
I_ALV_FORM               =
ENDFORM.
Hope it helps you.
Thanks Mansi
Code Formatted by: Alvaro Tejada Galindo on Jan 8, 2009 11:02 AM
Edited by: MANSI ASNANI on Jan 9, 2009 7:31 AM

ALV GRID - EVENT HANDLING

Hi all,
Please let me know how to hanldle event handling , making a cell in editable mode ,double click and hotspot creation,colorign a single cell,calling a transatcion when clicked on hotspot in a alv grid display program (not using OO concepts).
Looikng forward for a positive response.
Reagrds,
Mohinder.

Hi,
You can create your own custom status and asign it to your
ALV GRID. Here is a sample code to add custom status and handling events.
http://www.geocities.com/mpioud/Z_DEMO_ALV_REFRESH_BUTTON.html
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

ALV Grid event handlers

Hello Friends;
I have a problem with event handlers. I have defined events for double_click, data_change and hotspot_click. At first run of the program everything runs fine but when I make a change at the screen (like pressing Enter or entering a value at a screen field) the handlers seem to be called a couple of times. For example at a hotspot click I call an accounting document display and when I want to return with back button the program seems to be stuck at document display. Actually it calls event handler over and over again. How can I solve this problem? Can refreshing grid be a solution?
Thx in advance
Ali

Hello Ali
The problem is that after handling the hotspot event the current cell is still on the field with the hotspot. Thus, when you push ENTER the ALV grid checks the current cell which has a hotspot defined which, in turn, raises event HOTSPOT_CLICK.
Therefore, you have to move the current cell to another cell that has no hotspot defined. Have a look at the implementation of the event handler method. The hotspot is on field KUNNR. After calling transaction XD03 I shift the current cell to field BUKRS.
If you comment these lines you will see the same behaviour of the report as you described.
*& Report ZUS_SDN_TWO_ALV_GRIDS
REPORT ZUS_SDN_ALVGRID_EVENTS.
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 '1000' 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.
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 ).
    SET PARAMETER ID 'KUN' FIELD ls_knb1-kunnr.
    SET PARAMETER ID 'BUK' FIELD ls_knb1-bukrs.
    CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.
*   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
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.
* 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.
READ TABLE gt_fcat INTO ls_fcat
       WITH KEY fieldname = 'KUNNR'.
IF ( syst-subrc = 0 ).
    ls_fcat-hotspot = abap_true.
    MODIFY gt_fcat FROM ls_fcat INDEX syst-tabix.
ENDIF.
ENDFORM.                    " BUILD_FIELDCATALOG_KNB1
Regards
Uwe

ALV Grid: event for return

Hi developers,
i'm wanna do something after a user has pressed the return button in a alv grid control. For that i need probably a event. But i can not find a proper event in the documentation. Could one of you guys help me?
Best regards christian

You should post your question in the ABAP forum

ALV Grid Event Problem

Hi,
I have a dialog that contains an ALV grid and three buttons. When the ALV grid is created, it's parent is specified as a custom container.
Container
data : g_custom_container type ref to cl_gui_custom_container.
ALV Grid
data : g_grid             type ref to cl_gui_alv_grid.
    create object g_custom_container
           exporting container_name = p_cont_name.
    create object g_grid
           exporting i_parent = g_custom_container
           I_APPL_EVENTS = 'X'.
I would like the user to be able to just hit enter to accept the values displayed in the ALV. My problem is that when the dialog is created, the ALV has focus so the event isn't getting to the PAI of the dialog. If I click the mouse outside of the ALV to take focus away from the ALV, hitting the enter key does trigger the correct event in the dialog PAI. How can I either set the focus outside of the ALV when the dialog loads, or make the ALV forward the event to the dialog.
Thank you very much for any isight you can lend!
John Richason

Hi John, are you working with an editable ALV grid? If so, the code below will allow an event to be fired when the user hits enter after the data has been changed.
           call method alv_grid->register_edit_event
                        exporting
                           i_event_id = cl_gui_alv_grid=>mc_evt_enter.
You then need to create an event handler to handle the event being fired when the data is changed.
*   create Event Receiver
          create object event_receiver.
*   handler for ALV grid
          set handler event_receiver->handle_data_changed for alv_grid.
REgards,
Rich Heilman

How to find the check box selected while using Class in ALV grid display

hi,
I am displaying the ALV report using Class
For Example: CALL METHOD MYGRID->SET_TABLE_FOR_FIRST_DISPLAY EXPORTING I_STRUCTURE_NAME = 'ACC1'
                                                         IS_VARIANT = GS_VARIANT
                                                         I_SAVE = 'A' "XSAVE
                                                         IS_LAYOUT = LOUT
                                                 CHANGING IT_FIELDCATALOG = IT_FIELD
                                                           IT_OUTTAB = ACC_NO[].
In output i am getting 10 customer with check box, how do i find that customer number is selected.

HI,
Once user selects a check box, he would CLICK on a button ( say PROCESS )inorder to do the processing for the selected records. So in the PAI, under the EVENT ( OK CODE ) of the Button ( say PROCESS ), write the following code.
CALL METHOD MYGRID->check_changed_data.
Now,
Loop at acc_no where check = `X`.
Do the processing.
endloop.
Best regards,
Prashant

Problem while setting PF_status in ALV Grid Display

Hi,
i have a final internal table with first field as a check box. I have delete button on application tool-bar, with usercommand and pf status defined for it.
Once the output is displayed i should have the option of checking the line (check box) and delete then records from the list.
problem here is once i check the box and click on delete button is not getting deleted. but instead if i check the box and double click on the line(ie f2 fuctionality) and then click on refresh, then the records are getting deleted.
i have not provided and pf status for f2 functionality, by default its getting activated before the delete fuctionality is called.
i have attached my code below.
DATA : fk_events   TYPE slis_t_event,
       f_user_command TYPE slis_formname VALUE 'USER_COMMAND',
       f_status TYPE slis_formname VALUE 'STANDARD_SP01',
       fieldnam(10) TYPE c.
DATA: gs_layout TYPE slis_layout_alv.
DATA: ls_event TYPE slis_alv_event.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
    i_list_type = 0
IMPORTING
    et_events   = fk_events.
READ TABLE fk_events INTO ls_event WITH KEY name = slis_ev_user_command
IF sy-subrc = 0.
MOVE f_user_command TO ls_event-form.
MODIFY fk_events FROM ls_event TRANSPORTING form WHERE name =
ls_event-name.
ENDIF.
READ TABLE fk_events INTO ls_event WITH KEY name =
                          slis_ev_pf_status_set
IF sy-subrc = 0.
MOVE f_status TO ls_event-form.
MODIFY fk_events FROM ls_event TRANSPORTING form WHERE name =
ls_event-name.
ENDIF.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
   i_callback_program                 = 'ZWR_SECOND_TO_CREATION1'
i_callback_pf_status_set          = f_status
   i_callback_user_command           = f_user_command
   it_fieldcat                        = gt_fieldcat[]
   it_events                         = fk_events[]
TABLES
    t_outtab                          = gt_final[]
EXCEPTIONS
   program_error                     = 1
   OTHERS                            = 2.
FORM user_command USING r_comm TYPE sy-ucomm
                        rs_selfield TYPE slis_selfield.
fieldnam = rs_selfield-fieldname.
CASE r_comm.
    WHEN 'DELETE''.
      LOOP AT gt_final INTO gk_final.
IF gk_final-del_sat = 'X'.
          DELETE gt_final WHERE vbeln = gk_final-vbeln.
        ENDIF.
        rs_selfield-refresh = 'X'.
ENDLOOP.
    WHEN OTHERS.
      EXIT.
ENDCASE.
FORM standard_sp01 USING extab TYPE slis_t_extab.
SET PF-STATUS 'RAM' EXCLUDING extab. " For PF-Status
ENDFORM.                    "STANDARD_SP01
i wud be very thankful if someone cud help me
thanx
ram

Hi,
i have a final internal table with first field as a check box. I have delete button on application tool-bar, with usercommand and pf status defined for it.
Once the output is displayed i should have the option of checking the line (check box) and delete then records from the list.
problem here is once i check the box and click on delete button is not getting deleted. but instead if i check the box and double click on the line(ie f2 fuctionality) and then click on refresh, then the records are getting deleted.
i have not provided and pf status for f2 functionality, by default its getting activated before the delete fuctionality is called.
i have attached my code below.
DATA : fk_events   TYPE slis_t_event,
       f_user_command TYPE slis_formname VALUE 'USER_COMMAND',
       f_status TYPE slis_formname VALUE 'STANDARD_SP01',
       fieldnam(10) TYPE c.
DATA: gs_layout TYPE slis_layout_alv.
DATA: ls_event TYPE slis_alv_event.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
    i_list_type = 0
IMPORTING
    et_events   = fk_events.
READ TABLE fk_events INTO ls_event WITH KEY name = slis_ev_user_command
IF sy-subrc = 0.
MOVE f_user_command TO ls_event-form.
MODIFY fk_events FROM ls_event TRANSPORTING form WHERE name =
ls_event-name.
ENDIF.
READ TABLE fk_events INTO ls_event WITH KEY name =
                          slis_ev_pf_status_set
IF sy-subrc = 0.
MOVE f_status TO ls_event-form.
MODIFY fk_events FROM ls_event TRANSPORTING form WHERE name =
ls_event-name.
ENDIF.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
   i_callback_program                 = 'ZWR_SECOND_TO_CREATION1'
i_callback_pf_status_set          = f_status
   i_callback_user_command           = f_user_command
   it_fieldcat                        = gt_fieldcat[]
   it_events                         = fk_events[]
TABLES
    t_outtab                          = gt_final[]
EXCEPTIONS
   program_error                     = 1
   OTHERS                            = 2.
FORM user_command USING r_comm TYPE sy-ucomm
                        rs_selfield TYPE slis_selfield.
fieldnam = rs_selfield-fieldname.
CASE r_comm.
    WHEN 'DELETE''.
      LOOP AT gt_final INTO gk_final.
IF gk_final-del_sat = 'X'.
          DELETE gt_final WHERE vbeln = gk_final-vbeln.
        ENDIF.
        rs_selfield-refresh = 'X'.
ENDLOOP.
    WHEN OTHERS.
      EXIT.
ENDCASE.
FORM standard_sp01 USING extab TYPE slis_t_extab.
SET PF-STATUS 'RAM' EXCLUDING extab. " For PF-Status
ENDFORM.                    "STANDARD_SP01
i wud be very thankful if someone cud help me
thanx
ram

Print top of page in ALV Grid by passing in i_callback_html_top_of_page

How to print top of page while displaying data in ALV Grid ........as i m passing subroutine for top of page' in parameter i_callback_html_top_of_page

i_callback_html_top_of_page is different than i_callback_top_of_page...
if you want to use callback_html you will need to define a form routine something like this:
form html_top_of_page using r_top type ref to cl_dd_document.
data: text type sdydo_text_element.
* data: s_table type ref to cl_dd_table_element.
* data: col_key type ref to cl_dd_area.
* data: col_info type ref to cl_dd_area.
data: a_logo type ref to cl_dd_area.
data:
    l_string_with_html type string, "WA Html String Handling
    l_text_wa(20) type c.              "WA String Handling
call method r_top->initialize_document.
** Set Background Color on TOP-document = small white square works well
* this should be a graphic stored in BDS
call method r_top->set_document_background
                                exporting picture_id = 'SmWhiteSquare'.
** split TOP-Document to make space for the logo on the right
call method r_top->vertical_split
                                exporting split_area = r_top
                                          split_width = '70%'
                                importing right_area = a_logo.
** and add a Company logo - stored in BDS as above
call method a_logo->add_picture
                        exporting picture_id = 'YourLogoHere'.
** fill TOP-Document space on the left with data
* first the title
text = sy-repid.   " 'Var with My report name'.
call method r_top->add_text exporting text = text
                                    sap_style = 'HEADING'.
call method r_top->new_line.
* your code here (may list report selections params or whatever)...
endform.

Comments restricted to 25 Characters in ALV grid.

While entering comments in ALV grid it was not allowing to enter more then 25 characters but the comments we select from the dropdown are of more then 25 charcters.
Please advise how i can enter more then 25 char for comments.
Thank you
PVK

Hi,
Check this link
[REUSE_ALV_GRID_DISPLAY maximum length;
Regards,
Surinder

Wrong messagetype while processing in an alv grid event

Similar Messages

Maybe you are looking for