OO ALV to classic ALV

I need to change my report list from OO ALV to classic grid , but there are some functionalities which I do not apply to the classic ALV . Can you help me..? Functionalities are listed below
CALL METHOD grid_201->set_toolbar_interactive.
CALL METHOD grid_201->set_ready_for_input
    EXPORTING
      i_ready_for_input = 1.
CALL METHOD grid_201->register_edit_event
    EXPORTING
      i_event_id = cl_gui_alv_grid=>mc_evt_enter. "event_id = 18
CREATE OBJECT event_receiver_201
    TYPE
      lcl_event_receiver.
SET HANDLER event_receiver_201->handle_data_changed_finished FOR ALL INSTANCES.

Hi,
Please refer to the following link where detailed information is available:
http://help.sap.com/saphelp_nw04/helpdata/en/5e/88d440e14f8431e10000000a1550b0/frameset.htm

Similar Messages

Regarding Reading contents in classical ALV

Hi Experts,
I have a problem in Classical ALV Grid Display.
I donot know how to read the contents of modified fields after the grid is displayed.ie. i will modify some cells and press a button which is defined by me then the modified contents need to be read and updated in the data base.i am not able to read those modified contents.so please help me.i am using REUSE_ALV_GRID_DISPLAY.that is my requirement.i cannot use ALV Objects.i am posting the code.please verify and help me.
REPORT ZMRMMO_CUSTPOCHANGE.
*******************************TABLES***************************************
TABLES : VBAK,   "Sales Document:Header Data.
         VBUK,   "Sales Document:Header Status And Administrative Data.
         VBAP.   "Sales Document:Item Data.
********************************TYPES***************************************
INCLUDE ZPOCHANGE_DECLARATIONS.   "Include Program for declaration part.
****************************SELECTION SCREEN********************************
INCLUDE ZPOCHANGE_SELSCREEN.      "Include Program for selection screen.
****************************INITIALIZATION**********************************
INITIALIZATION.
COM1 = 'Select Reject Open Sale Order Radio Button To Delete An Open Sale Order'.
COM2 = 'Select Remove Rejection Radio Button To Undo The Delete sale Order'.
****************************START OF SELECTION******************************
START-OF-SELECTION.
*CREATE OBJECT obj1.
PERFORM F_CUSTPOSELECTION. "Subroutine for selection of data from the tables.
PERFORM F_BUILDFCAT.      "Subroutine To bulid a field catalog.
*I_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
*I_LAYOUT-BOX_TABNAME = 'I_FINAL'.
*I_LAYOUT-BOX_FIELDNAME = 'X'.
*APPEND I_LAYOUT.
PERFORM F_EVENTSGET.
IF FLAG = 'X'.
PERFORM F_ALVGRIDDISPLAY. "Subroutine to call the ALV Grid Display Function Module inorder to display the data
ELSE.
EXIT.
ENDIF.
FORM F_POCHANGEPFSTATUS USING RT_EXTAB TYPE SLIS_T_EXTAB.
SET PF-STATUS 'PO_CHANGE'. "EXCLUDING RT_EXTAB.
ENDFORM.
FORM F_POCHNGUSERCOMMAND USING R_UCOMM LIKE SY-UCOMM RS_SELFIELD TYPE SLIS_SELFIELD.
RS_SELFIELD-REFRESH = 'X'.
IF R_UCOMM EQ 'UPD'.
PERFORM F_POCHANGECHECK." USING RS_SELFIELD.
ENDIF.
ENDFORM.
INCLUDE ZMRMMO_CUSTPOCHANGE_F_BUILDF01.
INCLUDE ZMRMMO_CUSTPOCHANGE_F_POPULF01.
INCLUDE ZMRMMO_CUSTPOCHANGE_F_ALVGRF01.
INCLUDE ZMRMMO_CUSTPOCHANGE_F_CUSTPF01.
INCLUDE ZMRMMO_CUSTPOCHANGE_F_TESTF01.
INCLUDE ZMRMMO_CUSTPOCHANGE_F_POCHAF01.
INCLUDE ZMRMMO_CUSTPOCHANGE_F_EVENTF01.
*& Include           ZPOCHANGE_DECLARATIONS
TYPE-POOLS : SLIS.
TYPES :BEGIN OF TY_VBAK,
       VBELN LIKE VBAK-VBELN,
       BSTNK LIKE VBAK-BSTNK,
       KUNNR LIKE VBAK-KUNNR,
       LIFSK LIKE VBAK-LIFSK,
       GWLDT LIKE VBAK-GWLDT,
       END OF TY_VBAK,
       BEGIN OF TY_VBUK,
       VBELN LIKE VBUK-VBELN,
       LFGSK LIKE VBUK-LFGSK,
       END OF TY_VBUK,
       BEGIN OF TY_VBAP,
       VBELN LIKE VBAP-VBELN,
       LPRIO LIKE VBAP-LPRIO,
       ABGRU LIKE VBAP-ABGRU,
       END OF TY_VBAP,
       BEGIN OF TY_FINAL,
       VBELN LIKE VBAK-VBELN,
       BSTNK LIKE VBAK-BSTNK,
       KUNNR LIKE VBAK-KUNNR,
       LFGSK LIKE VBUK-LFGSK,
       LIFSK LIKE VBAK-LIFSK,
       GWLDT LIKE VBAK-GWLDT,
       LPRIO LIKE VBAP-LPRIO,
       ABGRU LIKE VBAP-ABGRU,
       END OF TY_FINAL.
****************************INTERNAL TABLES*********************************
DATA :I_VBAK TYPE STANDARD TABLE OF TY_VBAK,
      I_VBUK TYPE STANDARD TABLE OF TY_VBUK,
      I_VBAP TYPE STANDARD TABLE OF TY_VBAP,
      I_FINAL TYPE STANDARD TABLE OF TY_FINAL,
      WA_VBAK TYPE TY_VBAK,
      WA_VBUK TYPE TY_VBUK,
      WA_VBAP TYPE TY_VBAP,
      WA_FINAL TYPE TY_FINAL.
DATA : I_FCAT TYPE SLIS_T_FIELDCAT_ALV,
       I_LAYOUT TYPE SLIS_LAYOUT_ALV, "OCCURS 0,
       WA_FCAT LIKE LINE OF I_FCAT,
      WA_LAYOUT TYPE SLIS_LAYOUT_ALV,
       I_EVENTS TYPE SLIS_T_EVENT,
       WA_EVENTS LIKE LINE OF I_EVENTS,
       I_FCAT1 TYPE SLIS_T_FIELDCAT_ALV,
       WA_FCAT1 LIKE LINE OF I_FCAT1.
*DATA : obj1 TYPE REF TO CL_GUI_ALV_GRID_BASE.
*DATA :G_ROWNO TYPE I.
DATA FLAG VALUE 'X'.
*& Include           ZPOCHANGE_SELSCREEN
****************************SELECTION SCREEN********************************
SELECTION-SCREEN : BEGIN OF BLOCK SC1 WITH FRAME TITLE TEXT-000.
PARAMETERS : P_KUNNR TYPE VBAK-KUNNR OBLIGATORY,
             P_BSTNK TYPE VBAK-BSTNK.
SELECTION-SCREEN : END OF BLOCK SC1.
SELECTION-SCREEN : BEGIN OF BLOCK SC2 WITH FRAME TITLE TEXT-001.
PARAMETERS : R_REMSET RADIOBUTTON GROUP RAD1,
             R_CNGGAR RADIOBUTTON GROUP RAD1,
             R_CNGDEL RADIOBUTTON GROUP RAD1,
             R_REJSO RADIOBUTTON GROUP RAD1,
             R_REMREJ RADIOBUTTON GROUP RAD1.
SELECTION-SCREEN : COMMENT /1(79) COM1,
                   COMMENT /1(79) COM2.
SELECTION-SCREEN : END OF BLOCK SC2.
***INCLUDE ZMRMMO_CUSTPOCHANGE_F_CUSTPF01 .
*&      Form F_CUSTPOSELECTION
      text
--> p1        text
<-- p2        text
FORM F_CUSTPOSELECTION .
IF P_BSTNK IS INITIAL.
SELECT VBELN BSTNK KUNNR LIFSK GWLDT
         FROM VBAK
         INTO TABLE I_VBAK
         WHERE KUNNR EQ P_KUNNR.
IF SY-SUBRC <> 0.
    MESSAGE I000(YMES).
    FLAG = '0'.
ELSE.
    SORT I_VBAK BY VBELN.
ENDIF.
ELSE.
SELECT VBELN BSTNK KUNNR LIFSK GWLDT
         FROM VBAK
         INTO TABLE I_VBAK
         WHERE KUNNR EQ P_KUNNR AND
               BSTNK EQ P_BSTNK.
IF SY-SUBRC <> 0.
    MESSAGE I000(YMES).
    FLAG = '0'.
    ELSE.
    SORT I_VBAK BY VBELN.
ENDIF.
ENDIF.
*IF I_VBAK[] IS NOT INITIAL.
LOOP AT I_VBAK INTO WA_VBAK.
   WRITE :/    WA_VBAK-VBELN,
         10 WA_VBAK-BSTNK,
         20 WA_VBAK-KUNNR,
         30 WA_VBAK-LIFSK,
         40 WA_VBAK-GWLDT.
ENDLOOP.
*ENDIF.
IF I_VBAK[] IS NOT INITIAL.
SELECT VBELN LFGSK
         FROM VBUK
         INTO TABLE I_VBUK
         FOR ALL ENTRIES IN I_VBAK
         WHERE VBELN = I_VBAK-VBELN AND
               LFGSK <> 'C'.
ENDIF.
IF SY-SUBRC <> 0.
MESSAGE I000(YMES).
FLAG = '0'.
ELSE.
SORT I_VBUK BY VBELN.
ENDIF.
*IF I_VBUK[] IS NOT INITIAL.
LOOP AT I_VBUK INTO Wa_VBUK.
   WRITE :/ WA_VBUK-VBELN,
         10 WA_VBUK-LFGSK.
ENDLOOP.
*ENDIF.
IF I_VBUK IS NOT INITIAL.
SELECT VBELN LPRIO ABGRU
         FROM VBAP
         INTO TABLE I_VBAP
         FOR ALL ENTRIES IN I_VBUK
         WHERE VBELN = I_VBUK-VBELN.
ENDIF.
IF SY-SUBRC <> 0.
MESSAGE I000(YMES).
FLAG = '0'.
ELSE.
SORT I_VBAP BY VBELN.
ENDIF.
LOOP AT I_VBUK INTO WA_VBUK.
MOVE :WA_VBUK-VBELN TO WA_FINAL-VBELN,
      WA_VBUK-LFGSK TO WA_FINAL-LFGSK.
READ TABLE I_VBAK INTO WA_VBAK WITH KEY WA_VBUK-VBELN.
MOVE :WA_VBAK-BSTNK TO WA_FINAL-BSTNK,
      WA_VBAK-KUNNR TO WA_FINAL-KUNNR,
      WA_VBAK-LIFSK TO WA_FINAL-LIFSK,
      WA_VBAK-GWLDT TO WA_FINAL-GWLDT.
READ TABLE I_VBAP INTO WA_VBAP WITH KEY WA_VBUK-VBELN.
MOVE :WA_VBAP-LPRIO TO WA_FINAL-LPRIO,
      WA_VBAP-ABGRU TO WA_FINAL-ABGRU.
APPEND WA_FINAL TO I_FINAL.
CLEAR WA_FINAL.
ENDLOOP.
ENDFORM.                    " F_CUSTPOSELECTION
***INCLUDE ZMRMMO_CUSTPOCHANGE_F_BUILDF01 .
*&      Form F_BUILDFCAT
      text
--> p1        text
<-- p2        text
FORM F_BUILDFCAT .
PERFORM F_POPULATE_FCAT USING '1' 'VBELN' 'I_FINAL' '' '' '10' 'Sales Document' 'VBELN' 'VBAK'.
PERFORM F_POPULATE_FCAT USING '2' 'BSTNK' 'I_FINAL' '' '' '10' 'Customer PO No.' 'BSTNK' 'VBAK'.
PERFORM F_POPULATE_FCAT USING '3' 'KUNNR' 'I_FINAL' '' 'X' '10' 'Sold-to Party' 'KUNNR' 'VBAK'.
PERFORM F_POPULATE_FCAT USING '4' 'LFGSK' 'I_FINAL' '' '' '1' 'Delivery Status' 'LFGSK' 'VBUK'.
CASE 'X'.
WHEN R_REMSET.
PERFORM F_POPULATE_FCAT USING '5' 'LIFSK' 'I_FINAL' '' '' '2' 'Delivery BlocK' 'LIFSK' 'VBAK'.
PERFORM F_POPULATE_FCAT USING '6' 'LIFSK' 'I_FINAL' 'X' '' '2' 'Present Delivery BlocK' 'LIFSK' 'VBAK'.
WHEN R_CNGGAR.
PERFORM F_POPULATE_FCAT USING '5' 'GWLDT' 'I_FINAL' '' '' '8' 'Guarantee Date' 'GWLDT' 'VBAK'.
PERFORM F_POPULATE_FCAT USING '6' 'GWLDT' 'I_FINAL' 'X' '' '8' 'Present Guarantee Date' 'GWLDT' 'VBAK'.
WHEN R_CNGDEL.
PERFORM F_POPULATE_FCAT USING '5' 'LPRIO' 'I_FINAL' '' '' '2' 'Delivery Priority' 'LPRIO' 'VBAP'.
PERFORM F_POPULATE_FCAT USING '6' 'LPRIO' 'I_FINAL' 'X' '' '2' 'Present Delivery Priority' 'LPRIO' 'VBAP'.
WHEN R_REJSO.
PERFORM F_POPULATE_FCAT USING '5' 'ABGRU' 'I_FINAL' '' '' '2' 'Reason For Rejection' 'ABGRU' 'VBAP'.
PERFORM F_POPULATE_FCAT USING '6' 'ABGRU' 'I_FINAL' 'X' '' '2' 'Reason For Rejection' 'ABGRU' 'VBAP'.
WHEN R_REMREJ.
PERFORM F_POPULATE_FCAT USING '5' 'ABGRU' 'I_FINAL' '' '' '2' 'Reason For Rejection' 'ABGRU' 'VBAP'.
PERFORM F_POPULATE_FCAT USING '6' 'ABGRU' 'I_FINAL' 'X' '' '2' 'Reason For Rejection' 'ABGRU' 'VBAP'.
ENDCASE.
ENDFORM.                    " F_BUILDFCAT
***INCLUDE ZMRMMO_CUSTPOCHANGE_F_EVENTF01 .
*&      Form F_EVENTSGET
      text
--> p1        text
<-- p2        text
FORM F_EVENTSGET .
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
   I_LIST_TYPE           = 0
IMPORTING
   ET_EVENTS             = I_EVENTS
EXCEPTIONS
   LIST_TYPE_WRONG       = 1
   OTHERS                = 2
IF SY-SUBRC <> 0.
SORT I_EVENTS BY NAME.
ENDIF.
*READ TABLE I_EVENTS INTO WA_EVENTS WITH KEY NAME = 'USER_COMMAND'.
*IF SY-SUBRC = 0.
*MOVE 'USER_COMMAND' TO WA_EVENTS-FORM.
*MODIFY I_EVENTS FROM WA_EVENTS INDEX SY-TABIX."TRANSPORTING FORM WHERE NAME = 'WA_EVENT-NAME'.
*ENDIF.
READ TABLE I_EVENTS INTO WA_EVENTS WITH KEY NAME = 'LIST_MODIFY'.
IF SY-SUBRC = 0.
MOVE 'LIST_MODIFY' TO WA_EVENTS-FORM.
MODIFY I_EVENTS FROM WA_EVENTS INDEX SY-TABIX.
ENDIF.
*READ TABLE I_EVENTS INTO WA_EVENTS WITH KEY NAME = 'PF_STATUS_SET'.
*IF SY-SUBRC = 0.
*MOVE 'PF_STATUS_SET' TO WA_EVENTS-FORM.
*MODIFY I_EVENTS FROM WA_EVENTS INDEX SY-TABIX.
*ENDIF.
ENDFORM.                    " F_EVENTSGET
***INCLUDE ZMRMMO_CUSTPOCHANGE_F_ALVGRF01 .
*&      Form F_ALVGRIDDISPLAY
      text
--> p1        text
<-- p2        text
FORM F_ALVGRIDDISPLAY .
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_INTERFACE_CHECK                 = ' '
I_BYPASSING_BUFFER                = ' '
I_BUFFER_ACTIVE                   = ' '
   I_CALLBACK_PROGRAM                = SY-REPID
   I_CALLBACK_PF_STATUS_SET          = 'F_POCHANGEPFSTATUS'
   I_CALLBACK_USER_COMMAND           = 'F_POCHNGUSERCOMMAND'
I_CALLBACK_TOP_OF_PAGE            = ' '
I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
I_CALLBACK_HTML_END_OF_LIST       = ' '
I_STRUCTURE_NAME                  =
I_BACKGROUND_ID                   = ' '
I_GRID_TITLE                      =
I_GRID_SETTINGS                   =
   IS_LAYOUT                         = I_LAYOUT
   IT_FIELDCAT                       = I_FCAT
IT_EXCLUDING                      =
IT_SPECIAL_GROUPS                 =
IT_SORT                           =
IT_FILTER                         =
IS_SEL_HIDE                       =
I_DEFAULT                         = 'X'
   I_SAVE                            = 'U'
IS_VARIANT                        =
   IT_EVENTS                         = I_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        =
IMPORTING
E_EXIT_CAUSED_BY_CALLER           =
ES_EXIT_CAUSED_BY_USER            =
TABLES
    T_OUTTAB                          = I_FINAL
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.
*CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_DATA_GET'
EXPORTING
   I_HEADER_TABNAME       =
   I_ITEM_TABNAME         =
IMPORTING
ET_FIELDCAT            =
ET_SORT                =
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.                    " F_ALVGRIDDISPLAY
***INCLUDE ZMRMMO_CUSTPOCHANGE_F_POCHAF01 .
*&      Form F_POCHANGECHECK
      text
--> p1        text
<-- p2        text
FORM F_POCHANGECHECK.
ENDFORM.                    " F_POCHANGECHECK

Hi
I sure that there is a better way,but this one will work also...
In PBO enter rows you will show in report to itab you define (same type)
In PAI (after change) compare this tables (your grid table and itab with values before the change) and you will get rows which have been changed...
REGARDS
Yossi

How to disable the custom push button in Classic ALV

Hi All,
Iam Using Classic Alv (with out classes).I have a created a push button.now at run time i want to make it dynamic .
iam using REUSE_ALV_GRID_DISPLAY
for ex.
i have some records in my out put.
i have a push button "INSERT"
For first time when i clicked it will be inserted.
Now if i run the report for the same inputs as top,i will get the records.But the "INSERT" push button should be disable.IS that Possible ??
If yes kindly send me the solution.

Hi,
Here is the piece of code for your understanding...
FORM f4200_pf_status_set USING i_extab TYPE slis_t_extab.
REFRESH i_extab.
PERFORM f4210_exclude_fcodes CHANGING i_extab.( This form is mentioned below ).
SET PF-STATUS 'STANDARD' OF PROGRAM '(Program name)' EXCLUDING i_extab.( This line of code will excude the function u don't want)
ENDFORM.
FORM f4210_exclude_fcodes USING i_extab TYPE slis_t_extab.
DATA: ws_fcode TYPE slis_extab.
CLEAR ws_fcode.
ws_fcode = '&EB9'.
APPEND ws_fcode TO i_extab.
ws_fcode = '&ABC'.
APPEND ws_fcode TO i_extab.
ws_fcode = '&NFO'.
APPEND ws_fcode TO i_extab.
ws_fcode = '&LFO'.
APPEND ws_fcode TO i_extab.
ENDFORM.                    " f4210_exclude_fcodes
I hope this clarifies. Revert for any queries.
Cheers,
Venkat

ALV Control and Classical ALV

Hi all,
Please let me know the advantages and disadvantages of ALV control over Classical ALV.
Thanks & regards,
Naresh.

ALV LIST Can be coded using only FMs
ALV control Can be coded using FMs and object oriented concepts
ALV LIST Can be displayed hieraicharlly
ALV GRID cannot be displayed hierarichally
Alv grid (using oo concept) requires
designing the screen layout .
Hence, in one screen, we can show more
then one alv grid
(we cannot show more than
one alv list on one screen)
ALV LIST is Display Only.
Whereas
ALV Grid Can Be made EDITABLE for entry purpose.

EVENTS in Classical ALV

Hi,
I want to know the Purpose of using the below Events in Classical ALV (if possible with example).
1. CALLER_EXIT
2. REPREP_SEL_MODIFY
3. top_of_coverpage
4. END_OF_COVERPAGE
5. TOP_OF_FOREIGN_PAGE
6. END_OF_FOREIGN_PAGE
7.SUBTOTAL_TEXT
Thanks in Advance,
Sumi

The I_EVENTS table returns with the following possible constants:
1.     Slis_ev_item_data_expand TYPE slis_formname VALUE 'ITEM_DATA_EXPAND'.
Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT. Exit for passing item entries (ITEM table) for a header record that was expanded interactively by the user.
2.     Slis_ev_reprep_sel_modify TYPE slis_formname VALUE 'REPREP_SEL_MODIFY'.
RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to       be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header that is to be expanded.
RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that    entries are not repeated in the item table.
    RS_SELFIELD is initial in this case.
3.     Slis_ev_caller_exit_at_start TYPE slis_formname VALUE 'CALLER_EXIT'.
Is called at the beginning of the function module to make special settings. It is not usually used.
4.     Slis_ev_user_command TYPE slis_formname VALUE 'USER_COMMAND'.
As this is a frequently-used Callback event, the form routine can also be passed        directly in the interface by passing the user command in the IMPORTING parameter           I_CALLBACK_USER_COMMAND.
5.     Slis_ev_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.
   Equivalent to the list processing TOP-OF-PAGE event.
6.     Slis_ev_top_of_coverpage TYPE slis_formname VALUE 'TOP_OF_COVERPAGE'.
The selection information and list status are output together (if they exist) on a separate page by default
7.     Slis_ev_end_of_coverpage TYPE slis_formname VALUE 'END_OF_COVERPAGE'.
Analogously to TOP_OF_COVERPAGE the user can add other information
to the information output by ALV (selection information, list status) at this event.
8.     Slis_ev_foreign_top_of_page TYPE slis_formname VALUE FOREIGN_TOP_OF_PAGE'.
The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).
In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.
9.     Slis_ev_foreign_end_of_page TYPE slis_formname VALUE 'FOREIGN_END_OF_PAGE'.
The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).
In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.
10.     Slis_ev_pf_status_set TYPE slis_formname VALUE 'PF_STATUS_SET'.
If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).
The STANDARD status of the function group SALV should be used as a          template for a user-specific status. As this is a frequently used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.
11.     Slis_ev_list_modify TYPE slis_formname VALUE 'LIST_MODIFY'.
LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME
                                         R_INDEX LIKE SY-TABIX
                                         R_INDEX_ITEM LIKE SY-TABIX
                                         R_INDEX_SUM LIKE SY-TABIX.
12.     Slis_ev_top_of_list TYPE slis_formname VALUE 'TOP_OF_LIST'.
Information output at the start of the list
13.     Slis_ev_end_of_page TYPE slis_formname VALUE 'END_OF_PAGE'.
Information output at the end of a page. This is only called for printing.
14.     Slis_ev_end_of_list TYPE slis_formname VALUE 'END_OF_LIST'.
Information output at the end of the list
15.     Slis_ev_after_line_output TYPE slis_formname VALUE 'AFTER_LINE_OUTPUT'.
Output information after each output line. Should only be used in justified cases because it costs a lot of performance.
16.     Slis_ev_before_line_output TYPE slis_formname VALUE   'BEFORE_LINE_OUTPUT'.
Output information before each output line. Should only be used in justified cases because it costs a lot of performance.
17.     Slis_ev_subtotal_text TYPE slis_formname VALUE 'SUBTOTAL_TEXT'.
This event table (I_EVENTS) is now checked with the desired constants. If the desired constant is found, then the corresponding field for the FORM NAME is populated with the name of the routine containing the corresponding event.

Classical ALV

How to display ALV GRID in the middle of the screen.I am using classical ALV not OOP's concept.
Thanks in Advance,
Sumithra

Hi,
If you are using reuse_alv_grid_display, have a look at the parameters.
I_SCREEN_START_COLUMN
I_SCREEN_START_LINE
I_SCREEN_END_COLUMN
I_SCREEN_END_LINE
Fill the necessary values and try the output.

Search Help in Classical ALV

Hi All,
I have a small problem. Can anybody tell me how can i add a search help to a specific column in my classical ALV?
Regards,
Prakash Pandey

Hi Prakash,
In the Field Catalog there are two fields which are used to get the Search Help of any of the Column in ALV. Those are : REF_FIELDNAME and REF_TABNAME.
For example,
ls_fieldcat-fieldname = 'VBELN'.
ls_fieldcat-fix_column = 'X'.
ls_fieldcat-key = 'X'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-seltext_m = 'Sales Document'.
ls_fieldcat-edit = 'X'.
ls_fieldcat-ref_fieldname = 'VBELN'.
ls_fieldcat-ref_tabname = 'VBAP'.
append ls_fieldcat to p_fieldcat.
clear ls_fieldcat.
The above code will show the F4 for the column VBELN in the ALV.

Classical report to classical ALV report

Hi All,
       Please help in converting classical report to classical ALV report as in my classical report between the program ,after calculation block i have deleted all the WRITE statement to convert it into classical ALV and after end of the program i have used
PERFORM LAYOUT_INIT    USING    gs_layout.
PERFORM COMMENT_BUILD USING    gt_list_top_of_page[].
PERFORM build_fldcat   CHANGING field_cat1.
PERFORM build_layout.
PERFORM set_events     CHANGING lt_events.
and FM Reuse_alv_grid_display.
Please suggest the right way where to use these perform statements & the FM Reuse_alv_grid_display.
either in place of the deleted write statements or any where else in the program so that the calculation part output is displayed in Grid form.
Thanks.

use in place of the write statements only....
Regards,
SAPient

Classic & ALV

Hi Friends,
I'm doing a comparison between ALV and classic report and I am trying to find differences. So far, I have gathered information regarding their
1) Interactivity (sorting etc. Classic needs more coding in this sense)
2) Capabilities (ability to export to other file format)
Does anyone know of any other major/important differences? It does not have to be too technical. Thanks in advance
Regards,
r3venant

r3venant,
Check
what are ALV reports? how they are different from normal reports?;&#57089;
ALV is nothing but "application list viewer.
An ALV displays the output directly in the form of a grid or a list.
ie,in a tabular format with the required field names as headings.
while in a normal report,user has to design and format his output in a list or table fashion,which is a tedious process.
it is to overcome the user designing the output in list,SAP has given ALV,thro which one can deirectly get a tabulated list output.
type-pool:slis is basically declared to call the respective function module for the ALV display.
its mandatory that type-pool:slis is declared.
Imagine you have to write a report that lists out customer addresses. You will write code to get the input from the user via selection screen and then read the data based on the seletion from the database into an internal table(or a set of internal tables). Now once you have the data you will need to output this. In normal list reports, you will have to use 'WRITE' statements to format the output into columns and rows. Now suppose user wants some interactivity in it. Then you will have to provide some buttons and/or menu options through custom pf-status and then write logic for reacting to the user actions. After writing many such reportsm, you will feel like some of this can generalized and reused in every report.
That is exactly what ALV does. It takes out most of repeated sections of the code from out of you and provides you with excellent outputting functionality. It provides many standard functions like 'print', 'sort', 'filter', 'sum' etc by default. Imagine writing code yourself for all these if you were writing normal list program. One more major difference is the editing feature. If you were write a program that gives the user with editing features, then you will have to write a lot of logic. But with ALV, all the features like adding a row, deleting a row, copying a row, editing some fields of a row etc come by default.
Likewise, interactivity has become quite easy to implement. Like double clicking on a customer number, if the user wants to go to display customer transaction, it is very easy using ALV.
As pointed out here by others, go through the documentation of ALV and go through some of those demo programs and you will know the difference. ALV takes out a lot of burden of coding everything away from you and lets you worry about the business functionality that your report provides, rather than formatting the output or providing interactivity to the output.
Check ---ALV
              differences between normal list and ALV list
              http://www.allsaplinks.com/alv2.html
              http://www.allsaplinks.com/alv1.html
Pls. MArk if useful

Report with ALV tree and ALV list?

I need to create a report with layout as same as this one
[http://trangiegie.com/MyFile/output.JPG]
It looks like a report with combination of ALV tree and list. The tree works like a navigation bar. Wonder if there are any demo programs like this. Will appreciate any help.

For Tree alone - You can check program : BCALV_TREE_02
Program Name                   Report title
BCALV_GRID_DND_TREE            ALV Grid: Drag and Drop with ALV Tree
BCALV_GRID_DND_TREE_SIMPLE     ALV GRID: Drag and drop with ALV tree (simple)
BCALV_TEST_COLUMN_TREE         Program BCALV_TEST_COLUMN_TREE
BCALV_TEST_SIMPLE_TREE         Program BCALV_TEST_SIMPLE_TREE
BCALV_TREE_01                  ALV Tree Control: Build Up the Hierarchy Tree
BCALV_TREE_02                  ALV Tree Control: Event Handling
BCALV_TREE_03                  ALV Tree Control: Use an Own Context Menu
BCALV_TREE_04                  ALV Tree Control: Add a Button to the Toolbar
BCALV_TREE_05                  ALV Tree Control: Add a Menu to the Toolbar
BCALV_TREE_06                  ALV tree control: Icon column and icon for nodes/items
BCALV_TREE_DEMO                Demo for ALV tree control
BCALV_TREE_DND                 ALV tree control: Drag & Drop within a hierarchy tree
BCALV_TREE_DND_MULTIPLE        ALV tree control: Drag & Drop within a hierarchy tree
BCALV_TREE_EVENT_RECEIVER      Include BCALV_TREE_EVENT_RECEIVER
BCALV_TREE_EVENT_RECEIVER01
BCALV_TREE_ITEMLAYOUT          ALV Tree: Change Item Layouts at Runtime
BCALV_TREE_MOVE_NODE_TEST      Demo for ALV tree control
BCALV_TREE_SIMPLE_DEMO         Program BCALV_TREE_SIMPLE_DEMO
BCALV_TREE_VERIFY              Verifier for ALV Tree and Simple ALV Tree

Problem with same layout (variant) for two ALV Grid and ALV Tree

Hello!
I have two docking containers on the screen. On the left i have cl_gui_alv_tree, on the right cl_salv_table.
When a user set a default layout for ALV Grid (or ALV Tree), raport starts and sets this layout in both objects (tree and grid).
How to avoid this?

Hi,
Take Two radio buttons.
First radion button display the two containers in grid format,
second radio button display the two containers in tree format base on user selection.
CREATE OBJECT G_DOCING_CONTAINER
    EXPORTING PARENT = G_CUSTOM_CONTAINER."G_CONTAINER.
DISPLAY THE DATA IN GRID FORMATA
CREATE OBJECT r_grid
    EXPORTING
      i_parent          = G_DOCING_CONTAINER
CALL METHOD g_docing_container->set_width
      EXPORTING
        width      = 1300.
DISPLAY THE GRID DATA IN SECOND CONTAINER
CREATE OBJECT r_grid1
    EXPORTING
      i_parent          = G_DOCING_CONTAINER
CALL METHOD g_docing_container->set_width
      EXPORTING
        width      = 1300.
OTHERWISE WE CAN DISPLAY THE TWO CONTAINERS DATA IN A GRID FORMAT
CREATE OBJECT g_tree
    EXPORTING
      parent                = g_docing_container"g_custom_container
IF R1 = 'X'. "FOR GRID DISPLAY
CALL METHOD r_grid1->set_table_for_first_display
CALL METHOD r_grid2->set_table_for_first_display
ELSE.
************TREE DISPLAY
ENDIF.
regards,
muralii

Differences between the alv's and alv grid dispaly

hi guys
.........please send the differences between the alv's and alv grid display.
thanks....

Hi Midathala,
Plz go through the links might be useful to you.
Simple ALV report
http://www.sapgenie.com/abap/controls/alvgrid.htm
http://wiki.ittoolbox.com/index.php/Code:Ultimate_ALV_table_toolbox
ALV
1. Please give me general info on ALV.
http://www.sapfans.com/forums/viewtopic.php?t=58286
http://www.sapfans.com/forums/viewtopic.php?t=76490
http://www.sapfans.com/forums/viewtopic.php?t=20591
http://www.sapfans.com/forums/viewtopic.php?t=66305 - this one discusses which way should you use - ABAP Objects calls or simple function modules.
2. How do I program double click in ALV?
http://www.sapfans.com/forums/viewtopic.php?t=11601
http://www.sapfans.com/forums/viewtopic.php?t=23010
Check the program in the following link:
http://sap-img.com/abap/display-secondary-list-using-alv-grid.htm
3. How do I add subtotals (I have problem to add them)...
http://www.sapfans.com/forums/viewtopic.php?t=20386
http://www.sapfans.com/forums/viewtopic.php?t=85191
http://www.sapfans.com/forums/viewtopic.php?t=88401
http://www.sapfans.com/forums/viewtopic.php?t=17335
http://www.sapdevelopment.co.uk/reporting/alv/alvgrid_basic.htm
4. How to add list heading like top-of-page in ABAP lists?
http://www.sapfans.com/forums/viewtopic.php?t=58775
http://www.sapfans.com/forums/viewtopic.php?t=60550
http://www.sapfans.com/forums/viewtopic.php?t=16629
5. How to print page number / total number of pages X/XX in ALV?
http://www.sapfans.com/forums/viewtopic.php?t=29597 (no direct solution)
6. ALV printing problems. The favourite is: The first page shows the number of records selected but I don't need this.
http://www.sapfans.com/forums/viewtopic.php?t=64320
http://www.sapfans.com/forums/viewtopic.php?t=44477
7. How can I set the cell color in ALV?
http://www.sapfans.com/forums/viewtopic.php?t=52107
8. How do I print a logo/graphics in ALV?
http://www.sapfans.com/forums/viewtopic.php?t=81149
http://www.sapfans.com/forums/viewtopic.php?t=35498
http://www.sapfans.com/forums/viewtopic.php?t=5013
9. How do I create and use input-enabled fields in ALV?
http://www.sapfans.com/forums/viewtopic.php?t=84933
http://www.sapfans.com/forums/viewtopic.php?t=69878
10. How can I use ALV for reports that are going to be run in background?
http://www.sapfans.com/forums/viewtopic.php?t=83243
http://www.sapfans.com/forums/viewtopic.php?t=19224
11. How can I display an icon in ALV? (Common requirement is traffic light icon).
http://www.sapfans.com/forums/viewtopic.php?t=79424
http://www.sapfans.com/forums/viewtopic.php?t=24512
12. How can I display a checkbox in ALV?
http://www.sapfans.com/forums/viewtopic.php?t=88376
http://www.sapfans.com/forums/viewtopic.php?t=40968
http://www.sapfans.com/forums/viewtopic.php?t=6919
13. Top-of-page in ALV
selection-screen and top-of-page in ALV
14. ALV Group Heading
http://www.sap-img.com/fu037.htm
How to add list heading like top-of-page in ABAP lists?
http://www.sapfans.com/forums/viewtopic.php?t=58775
http://www.sapfans.com/forums/viewtopic.php?t=60550
http://www.sapfans.com/forums/viewtopic.php?t=16629
15. ALV output to PDF conversion
It has an example code for PDF Conversion.
http://www.erpgenie.com/abap/code/abap51.htm
converting the output of alv in pdf
Thanks
Mohinder Singh Chauhan

ALV Grid and ALV List difference?

Hello,
Can you help me differentiate ALV List and ALV grid and the low-level definition or context of each?
Also, can you give me a transaction code that outputs an ALV list as well as a tcode for ALV grid?
Thanks,
Jennah

Hi Kirtish,
Thanks but I havent done any function module stuff as I am not an ABAPer but anyway can you guide me through thios?
"I hope this might slove your query. For more please refer to documentation on ALV and also implement the ALV LIST and GRID reports. By using class Class CL_GUI_ALV_GRID, Function module REUSE_ALV_LIST_DISPLAY , REUSE_ALV_GRID_DISPLAY and some more functions like that only."
I will give you some tcode can you please try tcode FBL1n? then execute the report. What is the output is it an ALV list?
I wish to see an ALV list also an ALV grid to see difference.
Tjhakns,
Jennah

Subtotal text in ALV using OO ALV

HI All,
How to display subtotal text in ALV using OO ALV?
My output of ALV should be as follows
COL1    COL2   COL3
ABC      900       M1
PQR      100       M1
M1 Subtotal 1000
XYZ      2100    M2
M2 Subtotal 2100
I could put the subtotal, but couldnu2019t add subtotal text.
My code
TRY.
      CALL METHOD cl_salv_table=>factory
        IMPORTING
          r_salv_table   = g_alv
        CHANGING
          t_table        = gt_report
    CATCH cx_salv_msg .
ENDTRY.
u2026u2026
*Display the table.
g_alv->display( ).

Hi
REPORT z_alv_demo_total_text.
Type declaration for final table to display the output
TYPES: BEGIN OF ty_mara,
        srno TYPE char40, " Storing the total text
        matnr TYPE matnr, " Material
        ersda TYPE ersda, " Creation date
        ernam TYPE ernam, " Created by
        laeda TYPE laeda, " Last change date
        aenam TYPE aenam, " Last change by
        vpsta TYPE vpsta, " Maintenance status
        brgew TYPE brgew, " Gross weight
        ntgew TYPE ntgew, " Net weight
        gewei TYPE gewei, " Weight Unit
       END OF ty_mara.
Type declaration for table storing temp. data
TYPES: BEGIN OF ty_mara_tmp,
        matnr TYPE matnr, " Material
        ersda TYPE ersda, " Creation date
        ernam TYPE ernam, " Created by
        laeda TYPE laeda, " Last change date
        aenam TYPE aenam, " Last change by
        vpsta TYPE vpsta, " Maintenance status
        brgew TYPE brgew, " Gross weight
        ntgew TYPE ntgew, " Net weight
        gewei TYPE gewei, " Weight Unit
      END OF ty_mara_tmp.
Internal table for storing final data
DATA: i_mara TYPE STANDARD TABLE OF ty_mara INITIAL SIZE 0.
Work area for final table
DATA: w_mara TYPE ty_mara.
Internal table for storing temp. data
DATA: i_mara_tmp TYPE STANDARD TABLE OF ty_mara_tmp INITIAL SIZE 0.
Work area for temp. table
DATA: w_mara_tmp TYPE ty_mara_tmp.
Object variable for ALV grid
DATA: oref1 TYPE REF TO cl_gui_alv_grid.
Field catalog table for ALV grid
DATA: fieldcat TYPE lvc_t_fcat.
Workarea for field catalog table
DATA: w_field TYPE lvc_s_fcat.
Internal table for storing info. for ALV grid
data: i_sort2 TYPE STANDARD TABLE OF lvc_s_sort INITIAL SIZE 0.
Workarea for sort table
DATA: wa_sort2      TYPE lvc_s_sort.
Workarea for ALV layout
data: wa_layout     TYPE lvc_s_layo.
START-OF-SELECTION.
Fetch data
SELECT matnr   " Material
        ersda   " Creation date
        ernam   " Created by
        laeda   " Last change date
        aenam   " Last change by
        vpsta   " Maintenance status
        brgew   " Gross weight
        ntgew   " Net weight
        gewei   " Weight Unit
FROM mara
INTO TABLE i_mara_tmp
UP TO 100 ROWS.
CHECK sy-subrc = 0.
Populate final table
LOOP AT i_mara_tmp INTO w_mara_tmp.
Storing the Total text need to be displayed in
ALV
    w_mara-srno = 'Total weight (Gross & Net)'.
    w_mara-matnr = w_mara_tmp-matnr.
    w_mara-ersda = w_mara_tmp-ersda.
    w_mara-ernam = w_mara_tmp-ernam .
    w_mara-laeda = w_mara_tmp-laeda.
    w_mara-aenam = w_mara_tmp-aenam.
    w_mara-vpsta = w_mara_tmp-vpsta.
    w_mara-brgew = w_mara_tmp-brgew.
    w_mara-ntgew = w_mara_tmp-ntgew.
    w_mara-gewei = w_mara_tmp-gewei.
    APPEND w_mara TO i_mara.
ENDLOOP.
Calling the screen to display ALV
CALL SCREEN 100.
*&      Module STATUS_0100 OUTPUT
      Display ALV report
MODULE status_0100 OUTPUT.
IF oref1 IS INITIAL.
Create ALV grid object
In this case we have not created any custom container in the screen,
Instead of that dummy container name is passed
ADVANTAGE: we can run this report in background without any problem
    CREATE OBJECT oref1
      EXPORTING
        i_parent          = cl_gui_custom_container=>screen0
      EXCEPTIONS
        error_cntl_create = 1
        error_cntl_init   = 2
        error_cntl_link   = 3
        error_dp_create   = 4
        OTHERS            = 5
    CHECK sy-subrc = 0.
Preparing the field catalog
ZDEMO: Defined in DDIC, it's structure is same as TYPE ty_mara
defined in the program
    CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
      EXPORTING
        i_structure_name       = 'ZDEMO'
      CHANGING
        ct_fieldcat            = fieldcat
      EXCEPTIONS
        inconsistent_interface = 1
        program_error          = 2
        OTHERS                 = 3.
    IF sy-subrc = 0.
      LOOP AT fieldcat INTO w_field.
        IF w_field-fieldname = 'BRGEW' OR
          w_field-fieldname = 'NTGEW'.
        Summation for Gross & Net weight
          w_field-do_sum = 'X'.
          MODIFY fieldcat FROM w_field TRANSPORTING do_sum.
        ENDIF.
        IF w_field-fieldname = 'SRNO'.
        Hide this field so that it can display it's content i.e.
        Total text in Subtotal level
          w_field-tech = 'X'.
          w_field-no_out = 'X'.
          MODIFY fieldcat FROM w_field TRANSPORTING tech no_out.
        ENDIF.
        CLEAR w_field.
      ENDLOOP.
    ENDIF.
Populate Sort table with SRNO field so that we can display the total
text in it's subtotal level
    wa_sort2-spos = 1.
    wa_sort2-fieldname = 'SRNO'.
    wa_sort2-up = 'X'.
    wa_sort2-subtot = 'X'.
    APPEND wa_sort2 TO i_sort2.
Hide the total line
    wa_layout-no_totline = 'X'.
Display the ALV grid
    CALL METHOD oref1->set_table_for_first_display
      EXPORTING
        is_layout                     = wa_layout
      CHANGING
        it_outtab                     = i_mara[]
        it_fieldcatalog               = fieldcat
        it_sort                       = i_sort2
      EXCEPTIONS
        invalid_parameter_combination = 1
        program_error                 = 2
        too_many_lines                = 3
        OTHERS                        = 4.
    IF sy-subrc <> 0.
    ENDIF.
Set the focus on the grid
    CALL METHOD cl_gui_alv_grid=>set_focus
      EXPORTING
        control           = oref1
      EXCEPTIONS
        cntl_error        = 1
        cntl_system_error = 2
        OTHERS            = 3.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
ENDMODULE.                 " STATUS_0100 OUTPUT
These will defintely help in u displaying subtotal text check it
thanks

Display totals on the first line in ALV grid and ALV LIST

Generally we wll display totals at the end..
bu the requirement is to display it in the first line of the column.
how to display the totals in the first line?
I have used ALV GRID and ALV LIST (choice) using function modules.
Plz help me
.for example : Po qty : Should display total po qty on the first line of the Po line item.

IN LAYOUT
ILAYOUT-totals_before_items = 'X'.
REGARDS
SHIBA DUTTA

OO ALV to classic ALV

Similar Messages

Maybe you are looking for