Implementation of ALV Grid with Docking Container

using ALV
Framework

The implantation steps of ALV grid with custom container using ALV
framework as below:

1. Data extraction & output table preparation :

The output data like sales, Invoice is extracted from the corresponding tables
and an output table with the exact fields that need to output are prepared in
the report program.
2. Set the class attribute GV_CONT_NAME of the frame work class
Z_CLU_REPT_FRMWRK with a value z_clu_rept_frmwrk=>gc_cust as below.

This is the parameter that denotes the type of ALV in ALV output.
Note: This is a required parameter for any ALV output.

3. Create a custom screen with custom control on that and attach the screen to
the report program.

4. Set the class attribute gv_cont_name of class Z_CLU_REPT_FRMWRK as DOCK.

5. Set the docking position and ratio of grid on the ALV output as below:
6. In the PBO module of the custom screen created in above step call method
create_container_pbo of interface zif_rept_frmwrk by passing the container
name. The method returns the object of the container which is parent to ALV
grid.

7. Call method disp_alv_op of interface zif_rept_frmwrk by passing the

parameters container objet received from the method call in above step,
container name on the custom screen, and the report ID and passing the
output table as a changing parameter.

8. If the ALV requires any of the field catalogue, aggregations, or sorting the
corresponding attributes of the frame work class Z_CLU_REPT_FRMWRK has
to be set in the PBO module.
9. The ALV grid supports the events hotspot, double click, button click of any of
the buttons added and added function for any of the buttons added in the
application tool bar. The ALV with container does not support print events like
TOP-OF-PAGE and END-OF_PAGE. To implement any of the events requires the
corresponding field to be set in the class instance attribute
Z_CLU_REPT_FRMWRK-> GW_EVENTS and pass the ALV instance before the
event handler method is implemented.

10.If the ALV output requires any custom PF status or title bar, these need to be
added in the PBO module.

11.The screen exist logic need to be added in the PAI event of the screen
created.