0

SAP Grid Control

Contents:
 SAP Grid Control - Standard Application
 Preview of Other Techniques

 SAP AG 2002

© SAP AG TAW12 20-1

0.2
SAP Grid Control: Unit Objectives

At the conclusion of this unit, you will be able to:

 Explain how the SAP Grid Control collects and

formats data
 Name the standard functions
 Explain how the control can be used for basic
interactive reporting

 SAP AG 2002

© SAP AG TAW12 20-2

0.3
SAP Grid Control

SAPGrid
SAP Grid Control:
Control: Simple
Simple Application
Application

MoreComplex
More ComplexTechniques
Techniques

Outlook
Outlook

 SAP AG 2002

© SAP AG TAW12 20-3

0.4
Controls:
Technical Background I

SAP Grid Control: What are controls?

 Independent binary software components

 Installed locally on the frontend using SAPGUI
 Move functions from the application server to the frontend
 Have a wrapper class in ABAP Objects
 Intended for reuse

 SAP AG 2002

 This task is performed by the SAP Control Framework.

 The R/3 System allows you to create custom controls using ABAP Objects. The application server is
the Automation Client, which drives the custom controls (automation server) at the frontend.

 If custom controls are to be included on the frontend, then the SAPGUI acts as a container for them.
Custom controls can be ActiveX Controls or JavaBeans.
 The system uses a Remote Function Call (RFC) to transfer methods for creating and using a control
to the front end.
 ABAP objects are used to implement the controls in programs.

© SAP AG TAW12 20-4

0.5
Controls:
Technical Background II

Every control that you want to

display on the screen must be
allocated to a container control. The
Area diagram to the left shows how a
custom container control is used to
integrate an SAP grid control. A
container defined in the Screen
Painter must be used to define an
Custom container area that the custom container
control control is supposed to fill.

SAP Grid Control

 SAP AG 2002

 An SAP Container can contain other controls (for example, SAP Grid Control, Tree Control, SAP
Picture Control, SAP Splitter Control, and so on). The SAP Container 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 subscreens.
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.

© SAP AG TAW12 20-5

0.6
SAP Example and Standard Functions

Details Find Total Download

Sort Filter Print Display variant

Toolbar

AA 17 2000-01-17 USD 513.69 A321

AA 17 2000-02-20 USD 513.69 A321
AA 17 2000-03-11 USD 513.69 747-400
AA 64 2000-05-19 USD 369.00 747-400
LH 400 2000-01-13 DEM 1234.56 A310-300
LH 400 2000-02-26 DEM 1234.56 A310-300
LH 400 2000-03-21 DEM 1234.56 A310-300
LH 402 2000-03-04 DEM 1234.56 A319
LH 402 2000-05-28 DEM 1234.56 A319

 SAP AG 2002

 Within the control, you can manually make the columns wider and narrower or use the AutoFit
function. You can also rearrange the columns by dragging a selected column to the new position.
 Standard functions are available in the control toolbar. The detailed display appears as a modal
dialog box containing all the fields in the row (including hidden ones) at the current cursor position.
 The ALV control supports the Sort function for any number of columns. You can define complex sort
criteria and sort the columns in ascending or descending order.
 You can use the Find function to search for a string in rows or columns within a selected area
(wildcard search does not require *).
 You can calculate totals for one or more numerical columns. You can then use the Subtotals function
to set up control level lists. Select the columns (non-numeric fields only) to calculate and the system
displays the appropriate control level totals.
 When you print or download, the system always processes the complete list, not just the displayed
screen sections.
 You can define display variants to meet your own specific requirements. Saving variants: See Other
Techniques

© SAP AG TAW12 20-6

0.7
SAP Grid Control: Principle

Data source Interface SAP GRID CONTROL

Collect data in
SELECT ... an internal table

Display data from

Field description internal table
GET ...
• Field catalog according to field
• DIC Structure description and
standard functions
List like sorting and totals
Query

QuickView

 SAP AG 2002

 The SAP grid control is a generic tool for displaying lists in screens. The control offers standard
functions such as sorting by any column, adding numeric columns, and fixed lead columns
 Data collection is performed in the program using SELECT statements or GET eventsse. The data
records are saved in an internal table and passed on to the SAP control along with a field description.
 The field description contains information about the characteristics of each column, such as the
column header and output length. This information can defined either globally in the Dictionary
(structure in the Dictionary) or in the field catalog in the program itself. You can also merge both
techniques.
 The SAP link is a standard function of Query and QuickViewer. If multiline queries or QuickView
lists have been defined, they will automatically compress into a single line and output in the SAP
control as a long, single line list.

© SAP AG TAW12 20-7

0.8
The Inheritance Hierarchy of the SAP Grid Control

CL_GUI_OBJECT

CL_GUI_CONTROL

CL_GUI_ALV_GRID_BASE

CL_GUI_ALV_GRID

 SAP AG 2002

 The inheritance hierarchy for the class CL_GUI_ALV_GRID is shown above.

 This class encapsulates communication with the instance on the presentation server, along with many
other functions. For this reason, you should instantiate this class, not its superclass.

© SAP AG TAW12 20-8

0.9
Implementing the Control: Screen

Create in Screen Painter:

Screen 100

Create in Menu Painter:

Status

Create layout in Screen

MY_CONTROL_AREA
C Painter
100

In the flow logic of screen 100

PBO Define status

PAI OK_CODE processing for BACK, EXIT, and CANCEL

 SAP AG 2002

 Use Screen Painter to create a container for the SAP grid control. The control requires an area where
it can be displayed in the screen. You have to create a container control that determines this area.
 Use the corresponding icon in the Screen Painter layout to create the container control. The size of
area MY_CONTROL_AREA determines the subsequent size of the SAP control.
 A dialog status with the standard BACK, EXIT, and CANCEL functionality must be set during the
PBO event. You must also add the necessary coding for these function codes in the PAI event.

© SAP AG TAW12 20-9

0.10
Implementation in the Program

Container control * CONTROLS

DATA: g_custom_container
TYPE REF TO cl_gui_custom_container,
sap_grid
TYPE REF TO cl_gui_alv_grid.
SAP Grid Control

SAP grid control can be displayed using class CL_GUI_ALV_GRID.

 SAP AG 2002

 The reference variables for the custom container and the ALV grid control must be declared.
 To create reference variables, use ABAP statement TYPE REF TO <class name>.
 The global classes you need to do this are called cl_gui_custom_container (for the custom container
control) and cl_gui_alv_grid (for the SAP grid control).
 The global classes are defined in the Class Builder. You can use the Class Builder to display
information for the methods, their parameters, exceptions, and so on.

© SAP AG TAW12 20-10

0.11
Generating and Linking Objects

MODULE create_objects OUTPUT.

IF g_custom_container IS INITIAL.

CREATE
CREATE OBJECT
OBJECT g_custom_container
EXPORTING container_name = 'MY_CONTROL_AREA'.

CREATE
CREATE OBJECT
OBJECT sap_grid C
EXPORTING i_parent = g_custom_container.

ENDIF.

ENDMODULE. " CREATE_OBJECTS OUTPUT

 SAP AG 2002

 Use ABAP statement CREATE OBJECT <name> to create the objects for the container and the
ALV control. Objects are instances of a class.
 When an object is created (CREATE), method CONSTRUCTOR of the corresponding class is
executed. The parameters of method CONSTRUCTOR determine which parameters have to be
supplied with data when the object is created. In the above example, object sap_grid is given the
name of the container control (g_custom_container) in exporting parameter i_parent,
which links the two controls. For information on which parameters method CONSTRUCTOR
possesses and which of these parameters are required, see the Class Builder.
 Objects should only be created once during the program. To ensure that this is the case, enclose the
CREATE OBJECT statement(s) in an IF <object_name> IS INITIAL. ... ENDIF
clause. The objects must be generated before the control is displayed for the first time - that is,
during the PBO event of the ALV subscreen container.

© SAP AG TAW12 20-11

0.12
Program Flow

START-OF-SELECTION
Internal table with data Description of columns
itab_sflight Field catalog DIC
A B C sflight
SELECT * FROM A A B C
sflight ... B
C

CALL SCREEN 100.

Process Before Output Process After Input

MODULE status_0100. MODULE exit AT EXIT-COMMAND.

MODULE create_objects. MODULE user_command_0100.

MODULE transfer_data.

 SAP AG 2002

 To display the requested dataset in the SAP Grid Control, the data must be passed on to the control as
an internal table, and a field description must exist indicating the order in which the columns will be
output.
 In the simplest case, the field description can use a structure from the Dictionary. The Dictionary also
determines the technical field attributes like type and length, as well as the semantic attributes like
short and long texts. The SAP Grid Control uses this information to determine the column widths and
headers. The column sequence is determined by the field sequence in the structure.
 If no suitable structure is active in the Dictionary, or you want to output internal program fields in the
control, then you will have to define information like the output length and column header in the
field catalog.
 In a typical report application, the data is read first using SELECT...INTO TABLE or using a
logical database and then APPEND/INSERT the data into an internal table. When the data retrieval
is complete, the ABAP statement CALL SCREEN <number> is used to call the screen containing
the SAP Grid Control.

© SAP AG TAW12 20-12

0.13
Displaying the Data in the Control

Process Before Output

MODULE status_0100.

MODULE create_objects.

MODULE transfer_data.

MODULE transfer_data OUTPUT.

CALL METHOD sap_grid->set_table_for_first_display

EXPORTING i_structure_name = 'SFLIGHT'
CHANGING it_outtab = itab_sflight.

ENDMODULE. " TRANSFER_DATA OUTPUT

SET_TABLE_FOR_FIRST_DISPLAY is a method of class

CL_GUI_ALV_GRID.

 SAP AG 2002

 The data transfer to the ALV control takes place during the call of method
set_table_for_first_display from class cl_gui_alv_grid. The method call must be programmed at
the PBO event of the screen with the SAP Grid Control container.
 The name of the Dictionary structure that supplies the field description is specified in exporting
parameter i_structure_name. The name of the internal table that contains the data records to
display is specified in changing parameter it_outtab.

© SAP AG TAW12 20-13

0.14
SAP Grid Control

SAPGrid
SAP Grid Control:
Control: Simple
Simple Application
Application

MoreComplex
More ComplexTechniques
Techniques

Outlook
Outlook

 SAP AG 2002

© SAP AG TAW12 20-14

0.15
Field Catalog

You want to output internal fields, such as

available seats, in the SAP grid control

TYPES: BEGIN OF t_con,

carrid like sflight-carrid,
... Additional fields
free_seat
free_seats LIKE sflight-seatsmax,
Available seats
icon_name (30),

END OF t_con.

DATA: gt_outtab type STANDARD TABLE OF t_con,

... Output table
gt_fieldcat
gt_fieldcatTYPE lvc_t_fcat,
lvc_t_fcat
TYPE ,
lvc_t_fcat,
lvc_t_fcat
wa_fieldcat LIKE line of gt_fieldcat.
Field catalog

 SAP AG 2002

 The field description for the SAP Grid Control can be taken from an active Dictionary structure
(fully automatic), by passing a field catalog (manual), or through a mixture of the two options
(merge).
 The field catalog is in internal table with type lvc_t_fcat. This type is defined globally in the
Dictionary.
 Each line in the field catalog table corresponds to a column in the SAP control.

© SAP AG TAW12 20-15

0.16
Selected Fields in the Field Catalog

Table type lvc_t_fcat has a global DIC definition.

• fieldname Field name in output table

• ref_table Name of DIC reference structure
• ref_field Name of DIC reference field
• inttype Data type (c, f, i, ...)
•outputlen Column width
• coltext Column header
• seltext Field name in detail view
• col_pos Column position
• no_out Column hidden
• icon Output columns as icon

 SAP AG 2002

 The field characteristics (= column characteristics) are defined in the field catalog. The field catalog
is in internal table with type lvc_t_fcat. Each line that is explicitly described in the ALV control
corresponds to a column in the field catalog table.
 The link to the data records to output that are saved in internal table <outtab> is established through
field name <outtab-field>. This name must be specified in column fieldname in the field catalog.
 This field can be classified through a Dictionary reference (ref_table and ref_field) or by specifying
an ABAP data type (inttype).
 Column headers and field names in the detail view of an SAP control line can be determined in the
field catalog in coltext and seltext, respectively.
 The position of a field during output can be determined with col_pos in the field catalog.
 If you want to hide a column, fill field no_out with an X in the field catalog. Hidden fields can be
displayed again in a user display variant.
 Icons can be displayed in the SAP control. If you want a column to be interpreted as an icon, then the
icon name must be known to the program (include <icon>.) and icon = X must be specified for this
column in the field catalog.

© SAP AG TAW12 20-16

0.17
Filling and Passing On the Field Catalog

CLEAR wa_fieldcat.
wa_fieldcat-fieldname = 'FREE_SEATS'.
wa_fieldcat-ref_table = 'SFLIGHT'.
wa_fieldcat-ref_field = 'SEATSMAX'.
wa_fieldcat-coltext = text-001.
wa_fieldcat-seltext = text-001. Fill field catalog
wa_fieldcat-col_pos = pos_free.
APPEND wa_fieldcat TO gt_fieldcat. for additional fields

CLEAR wa_fieldcat.
wa_fieldcat-fieldname = 'ICON_NAME'.
wa_fieldcat-icon = 'X'. " Displayed as Icon
wa_fieldcat-coltext = text-001.
wa_fieldcat-seltext = text-001.
wa_fieldcat-col_pos = pos_icon.
APPEND wa_fieldcat TO gt_fieldcat.

CALL METHOD alv_grid->set_table_for_first_display

EXPORTING i_structure_name = 'SFLIGHT'
CHANGING it_outtab = gt_outtab
it_fieldcatalog
it_fieldcatalog == gt_fieldcat.
gt_fieldcat.
gt_fieldcat
gt_fieldcat

 SAP AG 2002

 The above example shows a semi-automatic field description: Part of the field description comes
from the Dictionary structure (sflight), while another part is explicitly defined in the field catalog
(gt_fieldcat).
 The field catalog (internal table) which fills in the program, passes on together with the name of the
Dictionary structure during the method call. The information merges accordingly in method
set_table_for_first_display.

© SAP AG TAW12 20-17

0.18
Grid Layout Options
Which parameters of the SET_TABLE_FOR_FIRST_DISPLAY method must be filled, and
in which situations?

Structure types in the A1 A2 A3

ABAP Dictionary
F1 F2 F3 F4 B1 B2 B3 B4

F1 F2 F3 F4 Z
Data table in the A2 B2 B4 Z

calling program

Display in the
F1 F2 F3 F4 F1 Z F2 F3 F4 A2 B2 B4 Z
SAP Grid Control

Parameter
I_STRUCTURE_NAME

Parameter
IT_FIELDCATALOG

 SAP AG 2002

 Field catalogs are created in one of the following three ways depending on the line type used by the
data table:
 Case 1:
All the fields of the global structure type have an identically-named column in the data table. You
want to display precisely these columns. In this case, you can have the proxy instance generate the
field catalog. You need only pass the name of the global structure type. Data table columns are not
displayed on the screen unless they are defined in the global structure type.
 Case 2:
All fields of the global structure type have an identically-named column in the data table, but you
want to adapt the attributes derived from the ABAP Dictionary or you want to add columns or both.
In this case, you need to add lines in the field catalog matching the columns you want to add or
change.
 Case 3:
Either there are no Dictionary references in the line type of the data table or there are references only
for some of the global structure fields. In this case, the calling program must generate the field
catalog from scratch.

© SAP AG TAW12 20-18

0.19
Saving Display Variants

* Save variants
data: gs_variant type disvariant,
x_save.

* Filling variant structure

* At least the report name has to be filled
gs_
gs__variant-
gs
gs_ variant--report
variant
variant- report == sy-
sy--repid.
sy
sy- repid
cprog.
cprog

*Determine saving options.

x_save = 'A'. "The user may save ALL types of variants

CALL METHOD sap_grid->set_table_for_first_display

EXPORTING
i_structure_name = 'SFLIGHT'
is_
is_variant = gs_
gs_variant
i_save = x_save
is_layout = gs_layout

CHANGING
it_outtab = gt_outtab
it_fieldcatalog = gt_fieldcat.

 SAP AG 2002

 For a user to save display variants, parameters is_variant and i_save must be passed on
during method call set_table_for_first_screen. To assign display variants uniquely to a
program, at least the program name must be supplied in the transferred structure (gs_variant).
Program names can be up to 30 characters long.
 If you only pass on the current parameters for is_variant, then existing variants can be loaded,
but no new ones can be saved. If you use parameter i_save, you must pass on a variant structure
with is_variant.

 I_SAVE = SPACE No variants can be saved.

 I_SAVE = 'U' The user can only save user-specific variants.

 I_SAVE = 'X' The user can only save general (shared) variants.

 I_SAVE = 'A' The user can save both user-specific and general (shared) variants.

© SAP AG TAW12 20-19

0.20
Filling and Passing On the Layout Structure

* Layout
DATA: gs_layout TYPE lvc_s_layo.

* Filling laoyout structure

gs_layout-grid_title = 'SAP Grid Title'(002).
gs_layout-detailtitl = 'Detail Title'(003).
gs_layout-zebra = 'X'.

CALL METHOD sap_grid->set_table_for_first_display

EXPORTING
i_structure_name = 'SFLIGHT'
is_variant = gs_variant
i_save = x_save
is_layout = gs_layout
is_layout = gs_layout

CHANGING
it_outtab = gt_outtab
it_fieldcatalog = gt_fieldcat.

 SAP AG 2002

 You can use parameter is_layout of method set_table_for_first_display, for example, to define the
header in the ALV control and the detail display.
 To do this, define a query area <gs_layout> in the program in accordance with Dictionary structure
lvc_s_layo, and pass on the text to display in field <gs_layout>-grid_title or <gs_layout>-detailtitl.
 If you want to create print lists with zebra stripes, set field <gs_layout>-zebra to X. You can display
a print preview for print lists by requesting standard function Print.

© SAP AG TAW12 20-20

0.21
Interface to Display Method

CALL METHOD sap_grid->set_table_for_first_display

EXPORTING i_structure_name = Name of structure, table, or view

is_variant = Display variants

i_save = Save display variant

i_default = Select initial layout

is_layout = Change technical configuration

is_print = Parameters for printing on backend

it_special_groups = Groupings

it_toolbar_excluding = Hide standard functions

CHANGING
it_outtab = Output table

it_fieldcatalog = Field catalog

it_sort = Sort criteria for first list output

it_filter = Filter criteria for first list output

 SAP AG 2002

 All parameters of method SET_TABLE_FOR_FIRST_DISPLAY from global class

CL_GUI_ALV_GRID are defined in the Class Builder.

© SAP AG TAW12 20-21

0.22
SAP Grid Control

SAPGrid
SAP Grid Control:
Control: Simple
Simple Application
Application

MoreComplex
More ComplexTechniques
Techniques

Outlook
Outlook

 SAP AG 2002

© SAP AG TAW12 20-22

0.23
Mouse Operations

DOUBLE_CLICK (double-clicking a cell or row)

Export parameters:
 E_ROW (line ID, type LVC_S_ROW)
< INDEX (line number in data table)
( E_COLUMN (column ID, type LVC_S_COL)
< FIELDNAME (column name in data table)
Air... Flug... Datum Preis Währ...
AA 17 2000-01-17 513,69 USD
AA 17 2000-02-20 513,69 USD
AA 17 2000-03-11 513,69 USD
AA 64 2000-05-19 369,00 USD
LH 400 2000-01-13 1234,56 DEM
LH 400 2000-02-16 1234,56 DEM
LH 400 2000-03-21 1234,56 DEM
LH 400 2000-03-04HOTSPOT_CLICK
1234,56 DEM (clicking a hot spot)
Export parameters:
LH 402 2000-05-28 1234,56 DEM
 E_ROW_ID (line ID, type LVC_S_ROW)
< INDEX (line number in data table)
( E_COLUMN (column ID, type LVC_S_COL)
< FIELDNAME (column name in data table)

 SAP AG 2002

 If the user double-clicks a data area, the DOUBLE_CLICK event is triggered in the calling
program.
 The export parameters contain information about the data table. Note that both parameters are
structures.
 E_ROW:
The INDEX field contains the line number in the internal table that belongs to the double-clicked
row in the data area.
 E_COLUMN:
The FIELDNAME field contains the name of the column in the internal table that belongs to the
double-clicked cell in the data area.
 If a column is characterized as a hot spot, the HOTSPOT_CLICK event is triggered when the user
clicks this column in the data area. The export parameters are filled in a similar way to those of the
DOUBLE_CLICK event.
 For further information about other mouse operation events, refer to the online documentation.

© SAP AG TAW12 20-23

0.24
Outlook: Handling Events I

Events are defined in class CL_GUI_ALV_GRID, such as DOUBLE_CLICK

DOUBLE_CLICK.

 SAP AG 2002

 Events are defined in global class cl_gui_alv_grid; you can use these events to implement
user interaction within the program. To respond to a double-click on a table line, you must respond
to event DOUBLE_CLICK.
 You receive control in the program, allowing you to implement interactive reporting - such as a full-
screen details list. The events for cl_gui_alv_grid are located in the Class Builder.

© SAP AG TAW12 20-24

0.25
Outlook: Handling Events II

CLASS lcl_ils DEFINITION.

PUBLIC SECTION.
Definition of a local class
METHODS on_dblclick FOR EVENT double_click
OF cl_gui_alv_grid IMPORTING e_row.
ENDCLASS.

CLASS class lcl_ils IMPLEMENTATION.

METHOD on_dblclick .
Implementing a local
class with handler [ own functionality ].
method
ENDMETHOD.
ENDCLASS.

DATA alv_dblclick TYPE REF TO lcl_ils.

Generating the object CREATE OBJECT sap_dblclick.

Registration of
SET HANDLER sap_dblclick->on_dblclick
handler method
FOR alv_grid.
for event double_click
 SAP AG 2002

 To define and implement a local class in the program, you use a handler method. In this handler
method, you program the functionality to trigger by a double-click in the output table.
 To activate a handler method at runtime, a class or an object from that class registers itself with an
event using command SET HANDLER. The names of the IMPORTING parameters in the handler
method correspond to the names of the EXPORTING parameters of the related event.
 In the above example, the local class is LCL_ILS and the handler method is ON_DBLCLICK. An
object - SAP_DBLCLICK - is created and registers itself for event DOUBLE_CLICK.
 You can query parameter e_row-index to determine which output line was requested by the double-
click. This parameter corresponds to the line number of the output table (internal table with the data
records to output). If you need information for the selected line, you have to read it with READ
TABLE itab INDEX e_row-index.
 This subsequent read in the output table generally corresponds to the HIDE area in conventional
reporting. You first have to make sure that the user has double-clicked a line in the output table
(similar to the valid line selection with the HIDE technique).

© SAP AG TAW12 20-25

0.26
Demo Programs Delivered for the SAP Grid Control

Package Programs Demonstrates

SLIS BCALV_GRID_01 Print list events

BCALV_GRID_02 Basic and detail lists with an instance
BCALV_GRID_03 Detail list in a modal dialog box
BCALV_GRID_04 Threshold value handling (exceptions/traffic light icons)
BCALV_GRID_05 Adding your own functions to the application toolbar
BCALV_GRID_06 Context menus
BCALV_GRID_07 Adding your own menus to the application toolbar
BCALV_GRID_08 Menu with standard pushbutton
BCALV_GRID_09 Options for managing display variants
BCALV_GRID_10 Initial use of display variants

 SAP AG 2002

 As well as these demonstration and test programs, you will also find other Repository objects for the
SAP Grid Control in the SLIS package.
 This package is part of the standard SAP R/3 System - that is, it is always delivered with the ABAP
Workbench.
 You can also analyze and execute these and other demonstration and test programs in a comfortable
test environment. In the ABAP Workbench, choose Environment  Examples  Control examples.

© SAP AG TAW12 20-26

0.27
ALV Grid Control: Unit Summary

You are now able to:

 Explain how the SAP Grid Control collects and
formats data
 Name the standard functions
 Explain how the control can be used for basic
interactive reporting

 SAP AG 2002

© SAP AG TAW12 20-27

0.28Exercises

Unit: ALV Grid Control

Topic: Using the ALV Grid Control to Output a List

When you have completed these exercises, you will be able to:
 Use the applications of the ALV grid control

1-1 Copy template SAPBC405_ALVT_1 to program Z##ALV1_... . Copy all the

program objects (including screens, GUI status, and so on). Sample solution for
exercise: SAPBC405_ALVS_1.

The OK code processing for screen 100 is included in the template (BACK, EXIT,
CANCEL). Do not work in the Screen Painter.
All the necessary program objects are contained in the TOP include.
1-1-1 Familiarize yourself with the program.

2-1 Read data from table SFLIGHT and display the data on screen 100 in an ALV grid
control.
2-1-1 Calculate the number of free seats.
2-1-2 Include the following fields in the ALV control:
carrid, connid, fldate, price, planetype, seatsmax, seatsocc, paymentsum,
free_seats.
Use the method SET_TABLE_FOR_FIRST_DISPLAY of class
CL_GUI_ALV_GRID.
2-1-3 Place the field free_seats in position 10 and make sure that the column
is colored (for example, colour 3, intensified display).

3-1 Change the layout.

3-1-1 Enter a title in the control and the detail view. Use text elements so that the
text can be translated.
3-1-2 Create a striped pattern (zebra).

© SAP AG TAW12 20-28

0.29Solutions

Unit: ALV Grid Control

Topic: Using the ALV Grid Control to Output a List

*&---------------------------------------------------------------------*
*& SAPBC405_ALVS_1 *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*

INCLUDE bc405_alvs_1top.

*&---------------------------------------------------------------------*
*& Event START-OF-SELECTION
*&---------------------------------------------------------------------*
START-OF-SELECTION.
SELECT * FROM sflight INTO CORRESPONDING FIELDS OF wa_outtab
WHERE carrid IN so_car.
wa_outtab-free_seats = wa_outtab-seatsmax - wa_outtab-seatsocc.
APPEND wa_outtab TO gt_outtab.
ENDSELECT.

CALL SCREEN 100.

*&---------------------------------------------------------------------*
*& Module STATUS_0100 OUTPUT
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
MODULE status_0100 OUTPUT.
SET PF-STATUS 'S100'.
SET TITLEBAR 'T100'.
ENDMODULE. " STATUS_0100 OUTPUT

*&---------------------------------------------------------------------*
*& Module EXIT INPUT

© SAP AG TAW12 20-29

*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
MODULE exit INPUT.
LEAVE PROGRAM.
ENDMODULE. " EXIT INPUT

*&---------------------------------------------------------------------*
*& Module USER_COMMAND_0100 INPUT
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
MODULE user_command_0100 INPUT.
MOVE ok_code TO save_ok_code.
CLEAR ok_code.
CASE save_ok_code.
WHEN 'BACK'.
CALL METHOD g_custom_container->free.
LEAVE TO SCREEN 0.
WHEN 'EXIT'.
CALL METHOD g_custom_container->free.
LEAVE TO SCREEN 0.
ENDCASE.
ENDMODULE. " USER_COMMAND_0100 INPUT

*&---------------------------------------------------------------------*
*& Module CREATE_OBJECTS OUTPUT
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
MODULE create_objects OUTPUT.

IF g_custom_container IS INITIAL.
CREATE OBJECT g_custom_container
EXPORTING container_name = 'MY_CONTROL_AREA'.

CREATE OBJECT alv_grid

EXPORTING i_parent = g_custom_container.
ENDIF.

ENDMODULE. " CREATE_OBJECTS OUTPUT

*&---------------------------------------------------------------------*

© SAP AG TAW12 20-30

*& Module TRANSFER_DATA OUTPUT
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
MODULE transfer_data OUTPUT.

CALL METHOD alv_grid->set_table_for_first_display

EXPORTING
i_structure_name = 'SFLIGHT'
is_layout = gs_layout

CHANGING
it_outtab = gt_outtab
it_fieldcatalog = gt_fieldcat.

ENDMODULE. " TRANSFER_DATA OUTPUT

*&---------------------------------------------------------------------*
*& Module FIELD_CATALOG OUTPUT
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
MODULE field_catalog OUTPUT.

CLEAR wa_fieldcat.

wa_fieldcat-fieldname = 'FREE_SEATS'.
wa_fieldcat-ref_table = 'SFLIGHT'.
wa_fieldcat-coltext = 'Free seats'(001).
wa_fieldcat-seltext = 'Free seats'(001).
wa_fieldcat-col_pos = pos_free.
wa_fieldcat-emphasize = 'C310'.

APPEND wa_fieldcat TO gt_fieldcat.

ENDMODULE. " FIELD_CATALOG OUTPUT

*&---------------------------------------------------------------------*
*& Module LAYOUT OUTPUT
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
MODULE layout OUTPUT.

© SAP AG TAW12 20-31

 gs_layout-grid_title = 'ALV Grid Title'(002).
gs_layout-detailtitl = 'Detail Title'(003).
gs_layout-zebra = 'X'.

ENDMODULE. " LAYOUT OUTPUT

*&---------------------------------------------------------------------*
*& Include BC405_ALVS_1TOP *
*& *
*&---------------------------------------------------------------------*

PROGRAM sapbc405_alvs_1 .

TYPES: BEGIN OF t_con,

carrid LIKE sflight-carrid,
connid LIKE sflight-connid,
fldate LIKE sflight-fldate,
price LIKE sflight-price,
currency LIKE sflight-currency,
planetype LIKE sflight-planetype,
seatsmax LIKE sflight-seatsmax,
seatsocc LIKE sflight-seatsocc,
paymentsum LIKE sflight-paymentsum,
free_seats LIKE sflight-seatsmax,
END OF t_con.

* OK code handling
DATA: ok_code LIKE sy-ucomm,
save_ok_code LIKE sy-ucomm.

* Data, which will be displayed in the ALV Control

DATA: gt_outtab TYPE STANDARD TABLE OF t_con,
wa_outtab TYPE t_con.

* Field position
DATA: pos_free TYPE i VALUE 10.

* Fieldcatalog
DATA: gt_fieldcat TYPE lvc_t_fcat,
wa_fieldcat LIKE LINE OF gt_fieldcat.

© SAP AG TAW12 20-32

* Layout
DATA: gs_layout TYPE lvc_s_layo.

* CONTROLS
DATA: g_custom_container TYPE REF TO cl_gui_custom_container,
alv_grid TYPE REF TO cl_gui_alv_grid.

* Selection Screen
SELECTION-SCREEN BEGIN OF BLOCK connection WITH FRAME.
SELECT-OPTIONS: so_car FOR wa_outtab-carrid.
SELECTION-SCREEN END OF BLOCK connection.

© SAP AG TAW12 20-33