What is ALV grid and describe its implementation procedure

Question

Hi all,
           Can you tell me the step by step implementation procedure of ALV grid

Answer 1

hi..
Steps To Use ALV Grid in a Program
1. Declare reference variables for,
       Container (class CL_GUI_CUSTOM_CONTAINER) and
       Grid (class CL_GUI_ALV_GRID)
Example
DATA: grid  TYPE REF TO cl_gui_alv_grid,
            custom_container  TYPE REF TO cl_gui_custom_container
2. Create Standard Screen and a container on that screen  and give a name to that container ( Use custom control button from tool bar) . This name will be used to link the container we have created on the screen with the object reference of class CL_GUI_CUSTOM_CONTAINER, which we have declared in the first step
3. Call the screen which has been created
4. Instantiate the container control and the ALV Grid Control in PBO of the screen.
Example
IF custom_container IS INITIAL.
  CREATE OBJECT custom_container
         EXPORTING
        CONTAINER_NAME = u2018MY_CONTAINER'.
CREATE OBJECT grid
       EXPORTING
       I_PARENT = custom_container.
ENDIF
5. For displaying the data, call the method set_table_for_first_display of object reference of CL_GUI_ALV_GRID.
Example
CALL METHOD grid->set_table_for_first_display
EXPORTING
I_BUFFER_ACTIVE               =
I_BYPASSING_BUFFER            =
I_CONSISTENCY_CHECK           =
I_STRUCTURE_NAME              =
IS_VARIANT                    =
I_SAVE                        =
I_DEFAULT                     =
IS_LAYOUT                     =
IS_PRINT                      =
IT_SPECIAL_GROUPS             =
IT_TOOLBAR_EXCLUDING          =
IT_HYPERLINK                  =
IT_ALV_GRAPHICS               =
IT_EXCEPT_QINFO               =
CHANGING
IT_OUTTAB                     =
IT_FIELDCATALOG               =
IT_SORT                       =
IT_FILTER                     =
EXCEPTION
INVALID_PARAMETER_COMBINATION =
PROGRAM_ERROR                 =
TOO_MANY_LINES                =
others                        =
EXPLANATION OF SOME IMPORTANT PARAMETERS.
I_BYPASSING_BUFFER & I_BUFFER_ACTIVE :
When the program is run for the first time, the fields present in the output table and their positions are stored in a buffer.  So the buffer is taken as reference for the successive executions.  In order to bypass this buffer the above parameter values should be u2018Xu2019 and  u2018 u2018(space)  respectively. If these values are not passed  to the function module, the changes made in the structure of the internal table will not be reflected in the output.
I_STRUCTURE_NAME:
If the structure of your output table corresponds to a structure stored in the Data Dictionary (DDIC), the ALV Grid Control can use this information to generate the field catalog automatically. Pass the table structure as parameter. In this case, all fields of this DDIC structure are displayed in the list.
IS_VARIANT :
It allows the user to save and reuse the layout. It is a structure of type DISVARIANT and contain the display variant name. It  facilitates pre-assignment for a layout, rather than displaying report and then choosing displaying variant.
I_SAVE:
This single character variable specifies whether the user specific display variants can be saved or not.
The I_SAVE "Options for saving layouts" parameter can have the following values:
U Only user specific layouts can be saved
X Only global layouts can be saved
A Both user specific and global layouts can be saved
Space Layouts can not be saved
IS_LAYOUT:
This structure of type LVC_S_LAYO
is used to control the layout of the ALV.  Two important fields are:
GRID TITLE. : Title of grid
ZEBRA : Alternate lines in list are displayed in different colors.
IT_FIELDCATALOG:
This internal table of type LVC_T_FCAT
is used to specify the position of various fields in the report itab.
There are three ways we can fill the field catalog table
1. Automatically through data dictionary structure (DDIC). In this case we pass the table structure to I_STRUCTURE_NAME.
2. Manually in ABAP program. Filling the internal table of type LVC_T_FCAT
1.                  . With each row corresponding to each column of output table. Each row of this table will hold value like
i). TABNAME & FIELDNAME specifies the reference fields for F1 help
ii). CTABNAME & CFIELDNAME specifies the reference fields for currency formatting
iii). QTABNAME & QFIELDNAME specifies the reference fields for quantity formatting
iv). SELTEXT_L holds the long description of the field
v).  SELTEXT_M holds the medium description of the field
vi). SELTEXT_S holds the small description of the field
vii). KEY specifies the Key field ( cannot be hidden )
viii). OUTPUTLEN species the output length of the field
ix). DO_SUM specifies that subtotal is required on this field
x). NO_OUT specifies a hidden field
3.  Semi-Automatically by combining the above 2 procedures.
Call function Module REUSE_ALV_FIELDCATALOG_MERGE and pass DDIC
structure or the output table to generate the field catalog.
Add additional Rows or modify existing properties of the fields to be displayed.
hope this will help you.
regards
lokesh