Make ALV GRID screen resizable

Hi All,
I have created an object V_MAPBOX using reference to class CL_GUI_DIALOGBOX_CONTAINER.
CREATE OBJECT v_mapbox
      EXPORTING
        width = 300
        height = 130
        style = cl_gui_control=>ws_sysmenu
        repid = 'ZMAP'
        dynnr = '1000'
        top = v_top2
        left = v_left2
        caption = 'Mapping Information'
      EXCEPTIONS
        cntl_error = 1
        cntl_system_error = 2
        create_error = 3
        lifetime_error = 4
        lifetime_dynpro_dynpro_link = 5
        event_already_registered = 6
        error_regist_event = 7
        OTHERS = 8.
Then created an object V_MAPALV with reference to class CL_GUI_ALV_GRID exporting V_MAPBOX.
Finally I am calling the method SET_TABLE_FOR_FIRST_DISPLAY of CL_GUI_ALV_GRID to display the screen on my custom container of screen 1000.
    CALL METHOD v_mapalv->set_table_for_first_display
      EXPORTING
        i_save                        = 'A'
        is_layout                     = wa_layout
      CHANGING
        it_outtab                     = i_map
        it_fieldcatalog              = i_fieldcat_map
      EXCEPTIONS
        invalid_parameter_combination = 1
        program_error                 = 2
        too_many_lines                = 3
        OTHERS                        = 4.
    IF sy-subrc <> 0.
    ENDIF.
The screen is getting displayed as expected. But I require to make this ALV screen to be resizable while it is displayed.
Have tried calling     CALL METHOD v_mapbox->resize, before calling the V_MAPALV methods but it does not work.
Need to know how can I make this resizable.

Hi,
ABAP objects are used to implement the controls in programs.
An SAP Container can contain other controls (for example, SAP ALV Grid Control, Tree Control, SAP Picture Control, SAP Splitter Control, and so on). It administers these controls logically in one collection and provides a physical area for the display.
Every control exists in a container. Since containers are themselves controls, they can be nested within one another. The container becomes the parent of its control. SAP containers are divided into five groups:
SAP custom container: Displays within an area defined in Screen Painter on screens or sub screens.
Class: CL_GUI_CUSTOM_CONTAINER
SAP dialog box container: Displays in a modeless dialog box or as a full screen. Class:
CL_GUI_DIALOGBOX_CONTAINER
SAP docking container: Displays as docked, resizable sub-window with the option of displaying it as a modeless dialog box. Class: CL_GUI_DOCKING_CONTAINER
SAP splitter container: Displays and groups several controls in one area - that is, splits the area into cells Class: CL_GUI_SPLITTER_CONTAINER
SAP easy splitter container: Displays controls in two cells, which the user can resize using a split bar. Class: CL_GUI_EASY_SPLITTER_CONTAINER.
In the control, you can adjust the column width by dragging, or use the 'Optimum width' function to adjust the column width to the data currently displayed. You can also change the column sequence by selecting a column and dragging it to a new position.
Thanks,
Pradeep.

Similar Messages

ALV grid screen dynamic resizing.

Hello Experts,
I have written a functionality to display a report program using the CL_GUI_ALV_GRID class.
I need to add a functionality so that the scrollbars and the custom container area resize themselves dynamically if I am changing the window size of the window in which my ALV grid is displayed.
Any pointers in this direction will be very helpful.
Thank you.
Gaurav.

You could try this thread...if it helps...
Resizing ALV Grid When Changing Screen Resolution
Thanks,
Ketan

Stretch alv grid screen

Hi,
I've a screen with alv grid in a custom control.
I'd like to make it stretch (+-) with the mouse, is it possible?
Thanks in advance,
Maria João Rocha

Maria,
I am assuming that the GRID is not occupying the entire space on your screen and you want to pull and fit into the screen.
FOr this what you need to do is.
1. On the Screen you have placed a CUSTOM CONTROL, right?
Stretch to the extent possible - if you don't have anything else on the screen, make the control occupy the entire screen.
2. Double click, shows the properties. There will be HORIZONTAL AND VERTICAL properties at the end of the screen. Check both the boxes and give 1 and 1 in the field next to them.
This automatcially makes sure that the container will occupy the entire space available on the screen.
Regards,
Ravi
Note : Please mark the helpful answers.

ALV Grid screen limit for a long field

Hi, i am having a problem making an ALV Grid of IDOC contents, i want to show de SDATA field of de EDIDD structure, but it is a 1000 char field, and when the ALV comes out i can only see part of the field.
I think the problem is the scrollbar, because it seems it not allows to scroll unless a field is starting or ending at the right or left of the screen.
It is a way to solve this problem?
thanks
best regards
Mariano Billinghurst.

a®s, thank you I have already tougth that solution but my client wants to see all in the alv to compare the lines.
I anyonelse have an idea it is wellcome!
thanks.
mariano.

Dynamic ALV GRID screen in a class? Possible?

I have created a class(I have done it locally as to be able to use it for mutiple clients) that I include in programs that I want to implement the alv grid for using the FM approach. Doing this allows me to easily implement the ALV quickly. However, I am wanting to use the OO ALV grid approach since there is more flexibility and control doing it this way. But I do not want to have to create a screen for every program that I want to do this for, I would like to just have a method in my existing class that would call a screen and then be able to control it like normal. I know that screens can not be called from a method so I was thinking of doing something similiar to another post using a FM to call the screen. I realize that this could be complicated because certain methods for the ALV GRID are called in the PBO/PAI events. Any help or suggestions would be appreciated.
Note: I am on 6.20 and have searched all over the web before posting.
Thanks.

Yes, i have written a function module which calls a generice ALV grid in a dialog box. Everything about the ALV grid is encapsulated in a function module. In this case, all I need to do is send this function module a fieldcatalog and the data, that's about it. Doing this may limit the functionality of event handling or you would just have to handle everything by doing more code for it..   This function module is very simple, not a whole lot to it.   You could do something like this only instead of using a model dialog box, you would throw a regular dynpro.
function z_popup_with_alvgrid.
*"*"Global interface:
*" IMPORTING
*"     REFERENCE(ENDPOS_COL) TYPE I DEFAULT 90
*"     REFERENCE(ENDPOS_ROW) TYPE I DEFAULT 22
*"     REFERENCE(STARTPOS_COL) TYPE I DEFAULT 10
*"     REFERENCE(STARTPOS_ROW) TYPE I DEFAULT 2
*"     REFERENCE(TEXTLINE1) TYPE C OPTIONAL
*"     REFERENCE(TEXTLINE2) TYPE C OPTIONAL
*"     REFERENCE(TEXTLINE3) TYPE C OPTIONAL
*"     REFERENCE(TEXTLINE4) TYPE C OPTIONAL
*"     REFERENCE(TITLE) TYPE C OPTIONAL
*"     REFERENCE(FIELDCAT) TYPE LVC_T_FCAT
*" TABLES
*"      I_ALV
call screen 0200 starting at startpos_col
                               startpos_row
                     ending at endpos_col
                               endpos_row.
endfunction.
*      Module STATUS_0200 OUTPUT
module status_0200 output.
set pf-status '0200'.
set titlebar '0200' with title.
data: alv_container type ref to cl_gui_custom_container.
data: alv_grid       type ref to cl_gui_alv_grid.
data: xfieldcat type lvc_t_fcat.
xfieldcat = fieldcat.
* Create Controls
create object:
     alv_container
             exporting
                   container_name    = 'ALV_CONTAINER',
     alv_grid
             exporting
                   i_parent          = alv_container.
* Set grid for first display
call method alv_grid->set_table_for_first_display(
      exporting
           i_structure_name       = 'I_ALV'
      changing
           it_outtab       = i_alv[]
           it_fieldcatalog = xfieldcat[] ).
endmodule.
*     Module USER_COMMAND_0100 INPUT
module user_command_0200 input.
case sy-ucomm.
    when 'CONTINUE' or 'CANCEL'.
      set screen 0.
      leave screen.
endcase.
endmodule.
Regards,
Rich Heilman

How to make alv grid cell as image cell

Dear All,
I want to create one alv report in abap. Acutually i need a output in report like machine number , machine name, model,
finally i want to display the images in the last colum( cell ) corresponding to the machines for each row. Machine no,name,model ..etc.. i fetched from the custom table. I maintaned the machines images in se78. Can any one help for this requirment..
Thanks and Regards,
Kavin

in my opinion you will not be able to do that in a ALV grid
the only way to do it is to build a HTML content and to display it into HTML viewer
then the images should be loaded as mime objects (SMW0) and not as text elements (SE78)

ALV GRID Field Resizing

I am using REUSE_ALV_LIST_DISPLAY FM to display the Data in ALV Report here how can i use the Condnse or How to reduse the unwanted sapce in the data field.
my code is like this
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
    EXPORTING
      i_callback_program      = v_repid
      i_callback_user_command = text-004               "'USER_COMMAND'
      is_layout               = t_layo
      i_default               = 'X'
      i_save                  = c_a
      it_fieldcat             = i_fcat[]
      it_events               = i_fevents[]
    TABLES
      t_outtab                = i_final[].

Hello Friend,
Its there in the layout paramater )
DATA: t_layo TYPE slis_layout_alv.
t_layo-colwidth_optimize = 'X'.
Hope this helps.
BR,
Suhas
Edited by: Suhas Saha on Mar 3, 2009 12:22 PM

How to use ALV Grid?

Hi,
I am totally new to ALV Grids. Could you give a full example of creating a ALV Grid with 2 columns, thinking there is a internal table itab with itab-col1 & itab-col2. Please start from initialising variables and onwards.
Thanks,
Kishan

Hi,
Simple example of how to implement an ALV grid
Note that this example uses table ZSFLIGHT. The table is equivalent to the table SFLIGHT.
Steps:
1.        Create an executable program (Report)
2.        Create a screen (100) and place a custom container named ALV_CONTAINER on the screen
3.        Create a Pushbutton. Give it the text Exit and the functioncode EXIT
REPORT sapmz_hf_alv_grid .
TABLES: zsflight.
G L O B A L   I N T E R N A L   T A B L E S
DATA: gi_sflight TYPE STANDARD TABLE OF sflight.
G L O B A L   D A T A
DATA: ok_code LIKE sy-ucomm,
g_wa_sflight LIKE sflight.
Declare reference variables to the ALV grid and the container
DATA:
go_grid             TYPE REF TO cl_gui_alv_grid,
go_custom_container TYPE REF TO cl_gui_custom_container.
S T A R T - O F - S E L E C T I O N.
START-OF-SELECTION.
SET SCREEN '100'.
*&      Module USER_COMMAND_0100 INPUT
MODULE user_command_0100 INPUT.
CASE ok_code.
WHEN 'EXIT'.
LEAVE TO SCREEN 0.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_0100 INPUT
*&      Module STATUS_0100 OUTPUT
MODULE status_0100 OUTPUT.
Create objects
IF go_custom_container IS INITIAL.
CREATE OBJECT go_custom_container
EXPORTING container_name = 'ALV_CONTAINER'.
CREATE OBJECT go_grid
EXPORTING
i_parent = go_custom_container.
PERFORM load_data_into_grid.
ENDIF.
ENDMODULE.                 " STATUS_0100 OUTPUT
*&      Form load_data_into_grid
FORM load_data_into_grid.
Read data from table SFLIGHT
SELECT *
FROM zsflight
INTO TABLE gi_sflight.
Load data into the grid and display them
CALL METHOD go_grid->set_table_for_first_display
EXPORTING i_structure_name = 'SFLIGHT'
CHANGING it_outtab        = gi_sflight.
ENDFORM.                    " load_data_into_grid
Allow the user to save and reuse the layout
A button can be shown on the grid toolbar, allowing the user to save and reuse a layout. The button looks like this:
See also example in SAP standard program BCALV_GRID_09.
To do this use the parameters IS_VARIANT and I_SAVE of the set_table_for_first_display method. Note that the IS_VARIANT
parameter must have the structure DISVARIANT.
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
Add the following code to the example:
FORM load_data_into_grid.
DATA:
For parameter IS_VARIANT
l_layout TYPE disvariant.
Code..........
Load data into the grid and display them
l_layout-report = sy-repid.
CALL METHOD go_grid->set_table_for_first_display
EXPORTING i_structure_name = 'SFLIGHT'
     is_variant       = l_layout
     i_save           = 'A'
CHANGING it_outtab        = gi_
Integrate user defined functions in the grid toolbar
Possibilities:
·        Replace existing functions in the toolbar or context men with user defined functions
·        Add new functions to the toolbar or context menu
Note that the whole toolbar can be removed using the IT_TOOLBAR_EXCLUDING parameter of the set_table_for_first_display
method.
See also example in SAP standard program BCALV_GRID_05
1) To get access to the icons insert the following statement in the top of the program:
TYPE-POOLS: icon.
2) To allow the declaration of o_event_receiver before the lcl_event_receiver class is defined, declare it as deferred in the start of
the program
To allow the declaration of o_event_receiver before the lcl_event_receiver class is defined, declare it as deferred in the
start of the program
CLASS lcl_event_receiver DEFINITION DEFERRED.
3) Declare reference to the event handler class
DATA:
o_event_receiver TYPE REF TO lcl_event_receiver.
4) Class for event receiver. This class adds the new button to the toolbar and handles the event when the button is pushed
CLASS lcl_event_receiver DEFINITION.
PUBLIC SECTION.
METHODS:
handle_toolbar FOR EVENT toolbar OF cl_gui_alv_grid
IMPORTING
e_object e_interactive,
handle_user_command FOR EVENT user_command OF cl_gui_alv_grid
IMPORTING e_ucomm.
ENDCLASS.
      CLASS lcl_event_receiver IMPLEMENTATION
CLASS lcl_event_receiver IMPLEMENTATION.
METHOD handle_toolbar.
Event handler method for event toolbar.
CONSTANTS:
Constants for button type
c_button_normal           TYPE i VALUE 0,
c_menu_and_default_button TYPE i VALUE 1,
c_menu                    TYPE i VALUE 2,
c_separator               TYPE i VALUE 3,
c_radio_button            TYPE i VALUE 4,
c_checkbox                TYPE i VALUE 5,
c_menu_entry              TYPE i VALUE 6.
DATA:
ls_toolbar TYPE stb_button.
Append seperator to the normal toolbar
CLEAR ls_toolbar.
MOVE c_separator TO ls_toolbar-butn_type..
APPEND ls_toolbar TO e_object->mt_toolbar.
Append a new button that to the toolbar. Use E_OBJECT of
event toolbar. E_OBJECT is of type CL_ALV_EVENT_TOOLBAR_SET.
This class has one attribute MT_TOOLBAR which is of table type
TTB_BUTTON. The structure is STB_BUTTON
CLEAR ls_toolbar.
MOVE 'CHANGE'        TO ls_toolbar-function.
MOVE icon_change    TO ls_toolbar-icon.
MOVE 'Change flight' TO ls_toolbar-quickinfo.
MOVE 'Change'        TO ls_toolbar-text.
MOVE ' '             TO ls_toolbar-disabled.
APPEND ls_toolbar    TO e_object->mt_toolbar.
ENDMETHOD.
METHOD handle_user_command.
Handle own functions defined in the toolbar
CASE e_ucomm.
WHEN 'CHANGE'.
LEAVE TO SCREEN 0.
ENDCASE.
ENDMETHOD.
ENDCLASS.
5) In the PBO module, crate object for event handler and set handler
CREATE OBJECT o_event_receiver.
SET HANDLER o_event_receiver->handle_user_command FOR go_grid.
SET HANDLER o_event_receiver->handle_toolbar FOR go_grid.
6) In the PBO module after the CALL METHOD go_grid->set_table_for_first_display, raise event
toolbar to show the modified toolbar
CALL METHOD go_grid->set_toolbar_interactive.
Set focus to the grid
After CALL METHOD go_grid->set_table_for_first_display insert the following statement:
CALL METHOD cl_gui_control=>set_focus EXPORTING control = go_grid.
Set the title of the grid
Fill the grid_title field of structure lvc_s_layo.
Note that the structure lvc_s_layo can be used for to customize the grid appearance in many ways.
DATA:
ALV control: Layout structure
gs_layout TYPE lvc_s_layo.
Set grid title
gs_layout-grid_title = 'Flights'.
CALL METHOD go_grid->set_table_for_first_display
   EXPORTING i_structure_name = 'SFLIGHT'
                           is_layout               = gs_layout
   CHANGING   it_outtab               = gi_sflight.
Customize the appearence of the grid
The structure lvc_s_layo contains fields for setting graphical properties, displaying exceptions, calculating totals and enabling specific
interaction options.
Fill the apporpiate fields of structure lvc_s_layo and insert it as a parameter in the CALL METHOD
go_grid->set_table_for_first_display. See the example under Set the title of the grid.
If you want to change apperance after list output, use the methods get_frontend_layout and set_frontend_layout.
Examples of fields in structure lvc_s_layo:
GRID_TITLE Setting the title of the grid
SEL_MODE. Selection mode, determines how rows can be selected. Can have the following values:
·        A Multiple columns, multiple rows with selection buttons.
·        B Simple selection, listbox, Single row/column
·        C Multiple rows without buttons
·        D Multiple rows with buttons and select all ICON
Setting and getting selected rows (Columns) and read line contents
You can read which rows of the grid that has been selected, and dynamic select rows of the grid using methods get_selected_rows
and set_selected_rows. There are similar methods for columns.
Note that the grid table always has the rows in the same sequence as displayed in the grid, thus you can use the index of the selected
row(s) to read the information in the rows from the table. In the examples below the grid table is named gi_sflight.
Data declaration:
DATA:
Internal table for indexes of selected rows
gi_index_rows TYPE lvc_t_row,
Information about 1 row
g_selected_row LIKE lvc_s_row.
Example 1: Reading index of selected row(s) and using it to read the grid table
CALL METHOD go_grid->get_selected_rows
IMPORTING
et_index_rows = gi_index_rows.
DESCRIBE TABLE gi_index_rows LINES l_lines.
IF l_lines = 0.
CALL FUNCTION 'POPUP_TO_DISPLAY_TEXT'
EXPORTING
     textline1 = 'You must choose a valid line'.
EXIT.
ENDIF.
LOOP AT gi_index_rows INTO g_selected_row.
READ TABLE gi_sflight INDEX g_selected_row-index INTO g_wa_sflight.
ENDIF.
ENDLOOP.
Example 2: Set selected row(s).
DESCRIBE TABLE gi_index_rows LINES l_lines.
IF l_lines > 0.
CALL METHOD go_grid->set_selected_rows
exporting
it_index_rows = gi_index_rows.
ENDIF.
Make an Exception field ( = Traffic lights)
There can be defined a column in the grid for display of traffic lights. This field is of type Char 1, and can contain the following values:
·        1 Red
·        2 Yellow
·        3 Green
The name of the traffic light field is supplied inh the gs_layout-excp_fname used by method set_table_for_first_display.
Example
TYPES: BEGIN OF st_sflight.
INCLUDE STRUCTURE zsflight.
TYPES: traffic_light TYPE c.
TYPES: END OF st_sflight.
TYPES: tt_sflight TYPE STANDARD TABLE OF st_sflight.
DATA: gi_sflight TYPE tt_sflight.
Set the exception field of the table
LOOP AT gi_sflight INTO g_wa_sflight.
IF g_wa_sflight-paymentsum < 100000.
g_wa_sflight-traffic_light = '1'.
ELSEIF g_wa_sflight-paymentsum => 100000 AND
    g_wa_sflight-paymentsum < 1000000.
g_wa_sflight-traffic_light = '2'.
ELSE.
g_wa_sflight-traffic_light = '3'.
ENDIF.
MODIFY gi_sflight FROM g_wa_sflight.
ENDLOOP.
Name of the exception field (Traffic light field)
gs_layout-excp_fname = 'TRAFFIC_LIGHT'.
Grid setup for first display
CALL METHOD go_grid->set_table_for_first_display
EXPORTING i_structure_name = 'SFLIGHT'
                     is_layout               = gs_layout
CHANGING it_outtab                 = gi_sflight.
Color a line
The steps for coloring a line i the grid is much the same as making a traffic light.
To color a line the structure of the table must include a Char 4 field for color properties
TYPES: BEGIN OF st_sflight.
INCLUDE STRUCTURE zsflight.
      Field for line color
types: line_color(4) type c.
TYPES: END OF st_sflight.
TYPES: tt_sflight TYPE STANDARD TABLE OF st_sflight.
DATA: gi_sflight TYPE tt_sflight.
Loop trough the table to set the color properties of each line. The color properties field is
Char 4 and the characters is set as follows:
Char 1 = C = This is a color property
Char 2 = 6 = Color code (1 - 7)
Char 3 = Intensified on/of = 1 = on
Char 4 = Inverse display = 0 = of
LOOP AT gi_sflight INTO g_wa_sflight.
IF g_wa_sflight-paymentsum < 100000.
g_wa_sflight-line_color    = 'C610'.
ENDIF.
MODIFY gi_sflight FROM g_wa_sflight.
ENDLOOP.
Name of the color field
gs_layout-info_fname = 'LINE_COLOR'.
Grid setup for first display
CALL METHOD go_grid->set_table_for_first_display
EXPORTING i_structure_name = 'SFLIGHT'
                    is_layout                = gs_layout
CHANGING it_outtab                 = gi_sflight.
Refresh grid display
Use the grid method REFRESH_TABLE_DISPLAY
Example:
CALL METHOD go_grid->refresh_table_display.
Complete code for the ALV grid example
This example shows and ALV grid with flights. After selecting a line a change button can be pushed to display a change screen. After
the changes have been saved, the ALV grid screen is displayed again, and the grid is updated with the changes.
The example shows:
·        How to setup the ALV grid
·        How to ste focus to the grid
·        How to set the title of the grid
·        How to allow a user to save and reuse a grid layout (Variant)
·        How to customize the ALV grid toolbar
·        Refresh the grid
·        Set and get row selection and read line contents
·        Make and exception field (Traffic light)
·        Coloring a line
Steps:
·        Create screen 100 with the ALV grid. Remember to include an exit button
·        Add a change button to the ALV grid toolbar
·        Create screen 200 the Change screen
The screens:
The code:
REPORT sapmz_hf_alv_grid .
Type pool for icons - used in the toolbar
TYPE-POOLS: icon.
TABLES: zsflight.
To allow the declaration of o_event_receiver before the
lcl_event_receiver class is defined, decale it as deferred in the
start of the program
CLASS lcl_event_receiver DEFINITION DEFERRED.
G L O B A L   I N T E R N A L   T A B L E S
*DATA: gi_sflight TYPE STANDARD TABLE OF sflight.
To include a traffic light and/or color a line the structure of the
table must include fields for the traffic light and/or the color
TYPES: BEGIN OF st_sflight.
INCLUDE STRUCTURE zsflight.
      Field for traffic light
TYPES: traffic_light TYPE c.
      Field for line color
types: line_color(4) type c.
TYPES: END OF st_sflight.
TYPES: tt_sflight TYPE STANDARD TABLE OF st_sflight.
DATA: gi_sflight TYPE tt_sflight.
G L O B A L   D A T A
DATA: ok_code         LIKE sy-ucomm,
    Work area for internal table
g_wa_sflight    TYPE st_sflight,
    ALV control: Layout structure
gs_layout       TYPE lvc_s_layo.
Declare reference variables to the ALV grid and the container
DATA:
go_grid             TYPE REF TO cl_gui_alv_grid,
go_custom_container TYPE REF TO cl_gui_custom_container,
o_event_receiver    TYPE REF TO lcl_event_receiver.
DATA:
Work area for screen 200
g_screen200 LIKE zsflight.
Data for storing information about selected rows in the grid
DATA:
Internal table
gi_index_rows TYPE lvc_t_row,
Information about 1 row
g_selected_row LIKE lvc_s_row.
C L A S S E S
CLASS lcl_event_receiver DEFINITION.
PUBLIC SECTION.
METHODS:
handle_toolbar FOR EVENT toolbar OF cl_gui_alv_grid
IMPORTING
   e_object e_interactive,
handle_user_command FOR EVENT user_command OF cl_gui_alv_grid
IMPORTING e_ucomm.
ENDCLASS.
      CLASS lcl_event_receiver IMPLEMENTATION
CLASS lcl_event_receiver IMPLEMENTATION.
METHOD handle_toolbar.
Event handler method for event toolbar.
CONSTANTS:
Constants for button type
c_button_normal           TYPE i VALUE 0,
c_menu_and_default_button TYPE i VALUE 1,
c_menu                    TYPE i VALUE 2,
c_separator               TYPE i VALUE 3,
c_radio_button            TYPE i VALUE 4,
c_checkbox                TYPE i VALUE 5,
c_menu_entry              TYPE i VALUE 6.
DATA:
ls_toolbar TYPE stb_button.
Append seperator to the normal toolbar
CLEAR ls_toolbar.
MOVE c_separator TO ls_toolbar-butn_type..
APPEND ls_toolbar TO e_object->mt_toolbar.
Append a new button that to the toolbar. Use E_OBJECT of
event toolbar. E_OBJECT is of type CL_ALV_EVENT_TOOLBAR_SET.
This class has one attribute MT_TOOLBAR which is of table type
TTB_BUTTON. The structure is STB_BUTTON
CLEAR ls_toolbar.
MOVE 'CHANGE'        TO ls_toolbar-function.
MOVE icon_change    TO ls_toolbar-icon.
MOVE 'Change flight' TO ls_toolbar-quickinfo.
MOVE 'Change'        TO ls_toolbar-text.
MOVE ' '             TO ls_toolbar-disabled.
APPEND ls_toolbar    TO e_object->mt_toolbar.
ENDMETHOD.
METHOD handle_user_command.
Handle own functions defined in the toolbar
CASE e_ucomm.
WHEN 'CHANGE'.
PERFORM change_flight.
       LEAVE TO SCREEN 0.
ENDCASE.
ENDMETHOD.
ENDCLASS.
S T A R T - O F - S E L E C T I O N.
START-OF-SELECTION.
SET SCREEN '100'.
*&      Module USER_COMMAND_0100 INPUT
MODULE user_command_0100 INPUT.
CASE ok_code.
WHEN 'EXIT'.
LEAVE TO SCREEN 0.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_0100 INPUT
*&      Module STATUS_0100 OUTPUT
MODULE status_0100 OUTPUT.
DATA:
For parameter IS_VARIANT that is sued to set up options for storing
the grid layout as a variant in method set_table_for_first_display
l_layout TYPE disvariant,
Utillity field
l_lines TYPE i.
After returning from screen 200 the line that was selected before
going to screen 200, should be selected again. The table gi_index_rows
was the output table from the GET_SELECTED_ROWS method in form
CHANGE_FLIGHT
DESCRIBE TABLE gi_index_rows LINES l_lines.
IF l_lines > 0.
CALL METHOD go_grid->set_selected_rows
EXPORTING
    it_index_rows = gi_index_rows.
CALL METHOD cl_gui_cfw=>flush.
REFRESH gi_index_rows.
ENDIF.
Read data and create objects
IF go_custom_container IS INITIAL.
Read data from datbase table
PERFORM get_data.
Create objects for container and ALV grid
CREATE OBJECT go_custom_container
EXPORTING container_name = 'ALV_CONTAINER'.
CREATE OBJECT go_grid
EXPORTING
i_parent = go_custom_container.
Create object for event_receiver class
and set handlers
CREATE OBJECT o_event_receiver.
SET HANDLER o_event_receiver->handle_user_command FOR go_grid.
SET HANDLER o_event_receiver->handle_toolbar FOR go_grid.
Layout (Variant) for ALV grid
l_layout-report = sy-repid. "Layout fo report
Setup the grid layout using a variable of structure lvc_s_layo
Set grid title
gs_layout-grid_title = 'Flights'.
Selection mode - Single row without buttons
(This is the default mode
gs_layout-sel_mode = 'B'.
Name of the exception field (Traffic light field) and the color
field + set the exception and color field of the table
gs_layout-excp_fname = 'TRAFFIC_LIGHT'.
gs_layout-info_fname = 'LINE_COLOR'.
LOOP AT gi_sflight INTO g_wa_sflight.
IF g_wa_sflight-paymentsum < 100000.
      Value of traffic light field
g_wa_sflight-traffic_light = '1'.
      Value of color field:
      C = Color, 6=Color 1=Intesified on, 0: Inverse display off
g_wa_sflight-line_color    = 'C610'.
ELSEIF g_wa_sflight-paymentsum => 100000 AND
       g_wa_sflight-paymentsum < 1000000.
g_wa_sflight-traffic_light = '2'.
ELSE.
g_wa_sflight-traffic_light = '3'.
ENDIF.
MODIFY gi_sflight FROM g_wa_sflight.
ENDLOOP.
Grid setup for first display
CALL METHOD go_grid->set_table_for_first_display
EXPORTING i_structure_name = 'SFLIGHT'
          is_variant       = l_layout
          i_save           = 'A'
          is_layout        = gs_layout
CHANGING it_outtab        = gi_sflight.
*-- End of grid setup -
Raise event toolbar to show the modified toolbar
CALL METHOD go_grid->set_toolbar_interactive.
Set focus to the grid. This is not necessary in this
example as there is only one control on the screen
CALL METHOD cl_gui_control=>set_focus EXPORTING control = go_grid.
ENDIF.
ENDMODULE.                 " STATUS_0100 OUTPUT
*&      Module USER_COMMAND_0200 INPUT
MODULE user_command_0200 INPUT.
CASE ok_code.
WHEN 'EXIT200'.
LEAVE TO SCREEN 100.
WHEN'SAVE'.
PERFORM save_changes.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_0200 INPUT
*&      Form get_data
FORM get_data.
Read data from table SFLIGHT
SELECT *
FROM zsflight
INTO TABLE gi_sflight.
ENDFORM.                    " load_data_into_grid
*&      Form change_flight
Reads the contents of the selected row in the grid, ans transfers
the data to screen 200, where it can be changed and saved.
FORM change_flight.
DATA:l_lines TYPE i.
REFRESH gi_index_rows.
CLEAR   g_selected_row.
Read index of selected rows
CALL METHOD go_grid->get_selected_rows
IMPORTING
et_index_rows = gi_index_rows.
Check if any row are selected at all. If not
table gi_index_rows will be empty
DESCRIBE TABLE gi_index_rows LINES l_lines.
IF l_lines = 0.
CALL FUNCTION 'POPUP_TO_DISPLAY_TEXT'
   EXPORTING
        textline1 = 'You must choose a line'.
EXIT.
ENDIF.
Read indexes of selected rows. In this example only one
row can be selected as we are using gs_layout-sel_mode = 'B',
so it is only ncessary to read the first entry in
table gi_index_rows
LOOP AT gi_index_rows INTO g_selected_row.
IF sy-tabix = 1.
READ TABLE gi_sflight INDEX g_selected_row-index INTO g_wa_sflight.
ENDIF.
ENDLOOP.
Transfer data from the selected row to screenm 200 and show
screen 200
CLEAR g_screen200.
MOVE-CORRESPONDING g_wa_sflight TO g_screen200.
LEAVE TO SCREEN '200'.
ENDFORM.                    " change_flight
*&      Form save_changes
Changes made in screen 200 are written to the datbase table
zsflight, and to the grid table gi_sflight, and the grid is
updated with method refresh_table_display to display the changes
FORM save_changes.
DATA: l_traffic_light TYPE c.
Update traffic light field
Update database table
MODIFY zsflight FROM g_screen200.
Update grid table , traffic light field and color field.
Note that it is necessary to use structure g_wa_sflight
for the update, as the screen structure does not have a
traffic light field
MOVE-CORRESPONDING g_screen200 TO g_wa_sflight.
IF g_wa_sflight-paymentsum < 100000.
g_wa_sflight-traffic_light = '1'.
C = Color, 6=Color 1=Intesified on, 0: Inverse display off
g_wa_sflight-line_color    = 'C610'.
ELSEIF g_wa_sflight-paymentsum => 100000 AND
   g_wa_sflight-paymentsum < 1000000.
g_wa_sflight-traffic_light = '2'.
clear g_wa_sflight-line_color.
ELSE.
g_wa_sflight-traffic_light = '3'.
clear g_wa_sflight-line_color.
ENDIF.
MODIFY gi_sflight INDEX g_selected_row-index FROM g_wa_sflight.
Refresh grid
CALL METHOD go_grid->refresh_table_display.
CALL METHOD cl_gui_cfw=>flush.
LEAVE TO SCREEN '100'.
ENDFORM.                    " save_changes
rgds,
latheesh

ALV grid on TABSTRIP- Subscreen

Hi,
How to display ALV grid screen on Tabstrip- Subscreen.
Please send sample code.
Thanks in advance.
-Mohan

Its not going to be different that what you do on a normal screen. I am assuming that you are using OO ALV control.
Here you do this on the sub screen instead of the main screen. Take a look at my weblog.
/people/ravikumar.allampallam/blog/2005/06/01/alv-reporting-using-controls--part-i
regards,
Ravi
Note :Please close the thread if this resolves the issue

ALV GRID Using oo abap example

Hi Friends,
I am new to oo abap, Can any one give me a basic example how i can create alv grid in oo abap.
regards,
DVNS

HI,
Programming for ALV grid display using the classes involves creation of a screen and calling it for display.
Since there has to be a linking between the program and the screen we have created , this comes in the form of a container. We use two important classes during the programming for displaying ALV grid, CL_GUI_ALV_GRID and CL_GUI_CUSTOM_CONTAINER.
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 = MY_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 X and (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.
METHODS OF IMPLEMENTING SOME EXTRA FEATURES
Set focus to the grid
After CALL METHODgrid->set_table_for_first_display insert the following stament:
CALL METHOD cl_gui_control=>set_focus EXPORTING control = grid
Refresh grid display
Use the grid method REFRESH_TABLE_DISPLAY
Example:
CALL METHOD grid->refresh_table_display.
Set the title of the grid
Fill the grid_title field of structure lvc_s_layo.
DATA:
gs_layout TYPE lvc_s_layo.
gs_layout-grid_title = 'TITLE'.
CALL METHOD go_grid->set_table_for_first_display
EXPORTING i_structure_name = 'structure name'
is_layout               = gs_layout
CHANGING   it_outtab               = Output table.
The structure lvc_s_layo contains fields for setting graphical properties, displaying exceptions, calculating totals and enabling specific interaction options
Event Handling
We can handle the events triggered by
1. User defined Text Output
2. Mouse-controlled Actions
3. Self-defined and Standard Functions
Steps for Event Handling
1. Define a (local) class for event handling
2. Define a method for each event you need to handle
3. Implement your event handler methods.
4. Create Object of the above class
5. Link used events and event handler methods of the receiver object and the grid
object.
Example program : Handling Double Click Event
Step1.Define a class.
class lcl_my_event_receiver definition.
public section.
methods:
handle_double_click
for event double_click of cl_gui_alv_grid.
endclass.
Step 2. Implement the class
class lcl_my_event_receiver implementation.
method handle_double_click.
message i001(zz) with ' double click event - Triggerd '.
endmethod.
endclass.
Step 3. Declare and create Object for the local class defined and implemented in steps 1 and 2 respectively
o_receiver   TYPE REF TO lcl_my_event_receiver   (Declaration)
create object o_receiver.                                            (Instantiation)
Step 4. Link the method for handling the event with the grid object in the PBO of screen after instantiating the grid object
set handler o_receiver->handle_double_click for grid.
EXAMPLE PROGRAM TO CHANGE A CLASSICAL REPORT OUTPUT TO A ALV GRID
This can be used as a template program to convert a classical report layout to a ALV grid.
Report<Report name>
Grid data Declarations----------------------------------------------*
INCLUDE ZVINALVD.
Internal table for ALV grid
TYPES: BEGIN OF T_ALV,
         Field1 like table-field1,
         Field2 like table-field2,
       END OF T_ALV.
DATA: I_ALV TYPE TABLE OF T_ALV.
DATA: WA_ALV TYPE T_ALV.
-Class declarations----
INCLUDE ZVINALVE.
Add a checkbox in selection screen for ALV grid display. If it is unchecked
output will be of classical type.
SELECTION-SCREEN BEGIN OF BLOCK box01.
SELECTION-SCREEN: BEGIN OF LINE.
SELECTION-SCREEN: COMMENT 4(30) To display repot output as a ALV grid.
PARAMETERS: p_alv AS CHECKBOX.
SELECTION-SCREEN: END OF LINE.
SELECTION-SCREEN END OF BLOCK box01.
START-OF-SELECTION.
Fill the ALV grid internal table
END-OF-SELECTION.
IF P_ALV = X.
PERFORM ALV_DISPLAY.
ELSE.
PERFORM CLASSICAL_DISPLAY.
ENDIF.
Alv Display
FORM ALV_DISPLAY.
CALL SCREEN 100.
ENDFORM.
Module STATUS_0100 OUTPUT
PBO for ALV Grid
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'GRID_DISPLAY'.
DATA:
For parameter IS_VARIANT that is used to set up options for storing
the grid layout as a variant in method set_table_for_first_display
l_layout TYPE disvariant.
GS_LAYOUT-SEL_MODE = 'B'.
Optimize column width
GS_LAYOUT-CWIDTH_OPT = 'X'.
Read data and create objects
IF go_custom_container IS INITIAL.
Create objects for container and ALV grid
    CREATE OBJECT go_custom_container
      EXPORTING container_name = 'ALV_CONTAINER'.
    CREATE OBJECT go_grid
      EXPORTING i_parent = go_custom_container.
Create object for event_receiver class
and set handlers
    CREATE OBJECT o_event_receiver.
    SET HANDLER o_event_receiver->handle_user_command FOR go_grid.
    SET HANDLER o_event_receiver->handle_toolbar FOR go_grid.
Layout (Variant) for ALV grid
    l_layout-report = sy-repid. "Layout to report
To built fieldcatalog
    PERFORM alv_build_fieldcatalog.
Grid setup for first display
    CALL METHOD go_grid->set_table_for_first_display
      EXPORTING
                is_variant      = l_layout
                i_save          = 'A'
                is_layout       = gs_layout
      CHANGING it_outtab       = I_ALV
                it_fieldcatalog = fieldcat.
Raise event toolbar to show the modified toolbar
    CALL METHOD go_grid->set_toolbar_interactive.
ENDIF.
ENDMODULE.                 " STATUS_0100 OUTPUT
Form ALV_BUILD_FIELDCATALOG.
Store contents of selected line in a internal table
FORM alv_build_fieldcatalog.
CLEAR afield.
afield-fieldname = 'FIELD1'.
afield-tabname   = 'I_ALV'.
afield-coltext   = Field Name 1.
afield-lzero     = ' '.
afield-key       = 'X'.
afield-outputlen = XX.
APPEND afield TO fieldcat.
CLEAR afield.
afield-fieldname = 'FIELD2'.
afield-tabname   = 'I_ALV'.
afield-coltext   = Field Name 2.
APPEND afield TO fieldcat.
ENDFORM.                    " alv_build_fieldcatalog
Module USER_COMMAND_0100 INPUT
PAI for ALV Grid
MODULE USER_COMMAND_0100 INPUT.
CASE OK_100.
    WHEN 'BACK'.
      LEAVE TO SCREEN 0.
    WHEN 'EXIT'.
      LEAVE PROGRAM.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_0100 INPUT
Form SELECT_LINE
Store contents of selected line in a internal table
FORM SELECT_LINE.
DATA:l_lines TYPE i.
REFRESH gi_index_rows.
CLEAR   g_selected_row.
Read index of selected rows
CALL METHOD go_grid->get_selected_rows
    IMPORTING et_index_rows = gi_index_rows.
Check if any row are selected at all. If not
table gi_index_rows will be empty
DESCRIBE TABLE gi_index_rows LINES l_lines.
IF l_lines = 0.
    CALL FUNCTION 'POPUP_TO_DISPLAY_TEXT'
         EXPORTING
              textline1 = 'You must choose a line'.
    EXIT.
ENDIF.
Read indexes of selected rows.
LOOP AT gi_index_rows INTO g_selected_row.
    IF sy-tabix = 1.
      READ TABLE I_ALV INDEX g_selected_row-index INTO
                     WA_ALV.
    ENDIF.
ENDLOOP.
ENDFORM.                    " SELECT_LINE
Includes:
1. ZVINALVD for data declarations
INCLUDE ZVINALVD .
Type pool for icons - used in the toolbar
TYPE-POOLS: icon.
To allow the declaration of o_event_receiver before the
lcl_event_receiver class is defined, decale it as deferred in the
start of the program
CLASS lcl_event_receiver DEFINITION DEFERRED.
GLOBAL DATA FOR ALV GRID
DATA:
OK code for alv grid screen
OK_100(4)           TYPE C,
ALV control: Layout structure
gs_layout           TYPE   lvc_s_layo,
Declare reference variables to the ALV grid and the container
go_grid             TYPE REF TO cl_gui_alv_grid,
go_custom_container TYPE REF TO cl_gui_custom_container,
o_event_receiver    TYPE REF TO lcl_event_receiver,
Data for storing information about selected rows in the grid
Internal table
gi_index_rows       TYPE lvc_t_row,
Information about 1 row
g_selected_row      LIKE lvc_s_row.
fieldcatalog
DATA: fieldcat        TYPE LVC_T_FCAT,
      afield          TYPE LVC_S_FCAT.
2. ZVINALVE for Class/object declarations
INCLUDE ZVINALVE.
C L A S S E S
CLASS lcl_event_receiver DEFINITION.
PUBLIC SECTION.
    METHODS:
      handle_toolbar FOR EVENT toolbar OF cl_gui_alv_grid
        IMPORTING e_object e_interactive,
      handle_user_command FOR EVENT user_command OF cl_gui_alv_grid
        IMPORTING e_ucomm.
ENDCLASS.
CLASS lcl_event_receiver IMPLEMENTATION
CLASS lcl_event_receiver IMPLEMENTATION.
METHOD handle_toolbar.
Event handler method for event toolbar.
    CONSTANTS:
Constants for button type
        c_button_normal           TYPE i VALUE 0,
        c_menu_and_default_button TYPE i VALUE 1,
        c_menu                    TYPE i VALUE 2,
        c_separator               TYPE i VALUE 3,
        c_radio_button            TYPE i VALUE 4,
        c_checkbox                TYPE i VALUE 5,
        c_menu_entry              TYPE i VALUE 6.
    DATA: ls_toolbar              TYPE stb_button.
Append seperator to the normal toolbar
    CLEAR ls_toolbar.
    MOVE c_separator TO ls_toolbar-butn_type..
    APPEND ls_toolbar TO e_object->mt_toolbar.
Append a new button that to the toolbar. Use E_OBJECT of
event toolbar. E_OBJECT is of type CL_ALV_EVENT_TOOLBAR_SET.
This class has one attribute MT_TOOLBAR which is of table type
TTB_BUTTON. The structure is STB_BUTTON
    CLEAR ls_toolbar.
    MOVE 'DISPLAY'        TO ls_toolbar-function.
    MOVE icon_DISPLAY    TO ls_toolbar-icon.
    MOVE 'Displaying customer' TO ls_toolbar-quickinfo.
    MOVE 'Display'        TO ls_toolbar-text.
    MOVE ' '             TO ls_toolbar-disabled.
    APPEND ls_toolbar    TO e_object->mt_toolbar.
ENDMETHOD.
METHOD handle_user_command.
Handle own functions defined in the toolbar
    CASE e_ucomm.
      WHEN 'DISPLAY'.
        PERFORM SELECT_LINE.
    ENDCASE.
ENDMETHOD.
Reward if useful

ALV Grid OOPS error

Hi all,
I am using ALV oops for displaying table.
CL_GUI_ALV_GRID->set_table_for_first_display.
I have cretaed an Custom Container for this.
Now scenario is like, First i have to display normal classical report when user double click on classical report
it will show alv grid on other screen depending on the row of report user clicks i am picking data and showing it on other screen as ALV grid.
First time its showing correct data when i press back on ALV grid screen and came back on report screen and select other row and double click its not showing anything ..
Please help.
Its required very urgently by client.
Thanks in advance..
Harsh

Hi,
Check whether the internal table in which you are passing data to the grid has the correct data.
Do not call the method set_table_for_first_display once again.
Instead call the method REFRESH_TABLE_DISPLAY.
Call the method SET_TABLE_FOR_FIRST_DISPLAY only once when the ALV grid object is created.
Call the method flush of the class cl_gui_cfw in the PBO after the grid is displayed; after the method SET_TABLE_FOR_FIRST_DISPLAY
Check if this works.
Regards,
Ankur Parab

Resizing ALV Grid When Changing Screen Resolution

I have an ALV Grid imbedded in a custom container. I would like for the Grid to resize if the user switches from 1024x768 to 800x600 resolution. I obviously could size it for the lower res screen (and it would be ok on the higher res screen), but I ultimately would like it to resize. Does anyone know how to make this happen?

Is your Grid running within a custom container that was placed in the screen painter? If so this is very easy. Just make you screen very large (much larger then even 1024x768). When you lay down the custom container, make it large enough to fill the entire empty area. Your custom container should have a Resizing section in the attributes window. Just check on Vertical and Horizontal resizing and choose you minimum size.

ALV Grid with size of the whole screen

I need to create ALV Grid, that fits any screen. How can i do this?
I tried cl_gui_docing_container, but in the constructor it's possible to make it to occupy only 95% of the screen.

If you are using a custom control on the screen and then a custom container you can easily do this.
Create a screen(Size 200 x 240), place a custom control on the screen and make it to the max size 200 x 240. Now in the attributes of the custom control, check the Resizing option for both horizontal and vertical, with some minimum numbers there.
Now, your ALV grid automatically occupies all the space available on the screen irrespective of the size if the screen and you will have only one scroll bar.
Regards,
Ravi
Note - Please mark all the helpful answers

How to suppress the protocol dialog screen in ALV grid ?

To check the values in the ALV grid we make use of the method add_protocol_entry from the class interface CL_ALV_CHANGED_DATA_PROTOCOL. The coloring of the wrong cells in the ALV grid is a nice feature but the popup screen that appears on every entry that is incorrect is not so nice. Is there a possibility to suppress this dialog screen without stopping the coloring feature? Or is there an other way to get this coloring feature in the specific cells of the ALV grid. We have already tried the emphasize option in the field catalog but in this case the coloring of a cell disappears when the cursor is set on the colored field in the ALV grid.
I hope somebody can help us.
Thanks and greetings,
Ad Pegels
Suiker Unie
Netherlands

As I understand by adding the PROTOCOL you are trying to validate some fields and display those with a different color.
Instead, if you can validate and can change the color manually I think the pop ups can be avoided. All you have to do is to add a nested internal table to the main internal table that has the display data. This nested table will be of type LVC_T_STYLE. You can add rows, one for each field that you want to display in a different color and also spcify the style in which you want to display.
Once you do that those fields should be displayed with different colors.
Regards,
Ravi
Note : Please allocate points if you find this useful.

Change Layout in Selection Screen for OO ALV-Grid

Hello everyone,
I got a problem regarding layouts for objectoriented ALV Grid. I want to make it possible that user can take the layout for ALV he wants to on the selection screen. So far thats no problem and it works. But there are some little problems which I do not know how to fix them. But first the facts:
(1) I got my parameter for layout
PARAMETER: p_vari TYPE disvariant-variant.
(2) I fill my global layout structure in initialization
INITIALIZATION.
* Variante vorbelegen
   gs_variant-username = sy-uname.
   gs_variant-report   = sy-repid.
* Layout holen
   CALL FUNCTION 'LVC_VARIANT_DEFAULT_GET'
     EXPORTING
       i_save        = 'A'
     CHANGING
       cs_variant    = gs_variant
     EXCEPTIONS
       wrong_input   = 1
       not_found     = 2
       program_error = 3
       OTHERS        = 4.
   IF sy-subrc = 0.
     p_vari = gs_variant-variant.
   ENDIF.
(3) I got my handling for F4-value help on variant parameter
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_vari.
   CALL FUNCTION 'LVC_VARIANT_F4'
     EXPORTING
       is_variant    = gs_variant
       i_save        = 'A'
     IMPORTING
       es_variant    = gs_variant
     EXCEPTIONS
       not_found     = 1
       program_error = 2
       OTHERS        = 3.
   IF sy-subrc <> 0.
     MESSAGE text-m01 TYPE 'S'.
   ELSE.
     p_vari = gs_variant-variant.
   ENDIF.
(4) I give back my parameters content into the variant structure at start of selection
START-OF-SELECTION.
   gs_variant-username = sy-uname.
   gs_variant-report   = sy-repid.
   gs_variant-variant = p_vari.
This works all fine but I got some problems when using default variants/layouts. For example I got a default variant only for me. When starting the selection screen it works fine that the default layout was written. It is displayed automatically in the variant parameter. But I want that if i I empty the content (blank it out) from my variant parameter, that report should start with "normal" layout how it was written in the report and NOT with default layout.
When I clear the gs_variant it works like I want it, but then the alv layout button looks like (without functions for layout), because I do not have the reference to my report.
So what to do? :-)
Regards
Michael

Wow that was fast, works great, thanks :-)
I did not use this parameter in set table method but now I fill it dynamically.
Ok next problem, one step harder ;-)
Now I have one selection screen for one ALV-Grid, but four radio buttons which control with which data the ALV gets filled (four different fieldcats, data tables and so on). Each Grid got an own HANDLE so that the layouts can be separated in four categories.
Now I want that by changing the radio button the individual standard layout for the chosen alv grid is getting filled.
This works fine when using it in selection screen output.
AT SELECTION-SCREEN OUTPUT.
   CLEAR gs_variant.
* Layout-Handles individuell für Klausel-Radiobuttons setzen
   IF     p_py IS NOT INITIAL.
     gs_variant-username = sy-uname.
     gs_variant-report   = sy-repid.
     gs_variant-handle   = 'KLPY'.
   ELSEIF p_rh IS NOT INITIAL.
     gs_variant-username = sy-uname.
     gs_variant-report   = sy-repid.
     gs_variant-handle   = 'KLRH'.
   ELSEIF p_aj IS NOT INITIAL.
     gs_variant-username = sy-uname.
     gs_variant-report   = sy-repid.
     gs_variant-handle   = 'KLAJ'.
   ELSEIF p_sr IS NOT INITIAL.
     gs_variant-username = sy-uname.
     gs_variant-report   = sy-repid.
     gs_variant-handle   = 'KLSR'.
   ENDIF.
* Layout holen
   CALL FUNCTION 'LVC_VARIANT_DEFAULT_GET'
     EXPORTING
       i_save        = 'A'
     CHANGING
       cs_variant    = gs_variant
     EXCEPTIONS
       wrong_input   = 1
       not_found     = 2
       program_error = 3
       OTHERS        = 4.
   IF sy-subrc = 0.
     p_vari = gs_variant-variant.
   ELSE.
     CLEAR p_vari.
   ENDIF.
But unfortunately selection screen output is getting passed by EACH changing in the selection screen. This means when I try to clear the default layout in my parameter field, it gets refilled automatically with default layout. If I do a condition around the filling (only if not initial) the default value filling does not work fine in every case, e.g. when clearing the parameters field and then change the radiobutton -> then it does not get filled automatically.

Make ALV GRID screen resizable

Similar Messages

Maybe you are looking for