Sie sind auf Seite 1von 2

Building Blocks

While preparing a list to be displayed via an ALV grid control, we have some bas
ic components to prepare. These are;
i. List data: Obviously, this is the data in an internal table to be listed. Sta
ndard ALV functions except sorting makes just read access to the list data. Howe
ver, sorting changes state of the internal table. The internal table holding lis
t data may be of any flat type. Deep types are only allowed when set for some fu
nctionalities of ALV Grid.
ii. Field Catalog: We use another internal table to define specifications on how
the fields of our list will be displayed. This internal table is called the fiel
d catalog . The field catalog must comprise some technical and additional informat
ion about display options for each column to be displayed. There are three proce
dures to generate the field catalog as Automatic generation , Semi-automatic generat
ion , and Manual generation . The internal table for the field catalog must be refere
nced to the dictionary type LVC_T_FCAT .
iii. Layout Structure: We fill a structure to specify general layout options for
the grid. With this structure we can set general display options, grid customiz
ing, totals options, color adjustments etc... The layout structure must be of ty
pe LVC_S_LAYO .
iv. Event Handler: We should define and implement an event handler class if we w
ant to handle events triggered by the ALV Grid instance. After creating ALV Grid
instance, we must register an instance of this event handler class to handle AL
V Grid events.
v. Additional Data: To trigger some additional features of ALV Grid we can have
some additional data to pass as parameters. For example, initial sorting criteri
a, buttons to be deactivated, etc...
Building Blocks
While preparing a list to be displayed via an ALV grid control, we have some bas
ic components to prepare. These are;
i. List data: Obviously, this is the data in an internal table to be listed. Sta
ndard ALV functions except sorting makes just read access to the list data. Howe
ver, sorting changes state of the internal table. The internal table holding lis
t data may be of any flat type. Deep types are only allowed when set for some fu
nctionalities of ALV Grid.
ii. Field Catalog: We use another internal table to define specifications on how
the fields of our list will be displayed. This internal table is called the fiel
d catalog . The field catalog must comprise some technical and additional informat
ion about display options for each column to be displayed. There are three proce
dures to generate the field catalog as Automatic generation , Semi-automatic generat
ion , and Manual generation . The internal table for the field catalog must be refere
nced to the dictionary type LVC_T_FCAT .
iii. Layout Structure: We fill a structure to specify general layout options for
the grid. With this structure we can set general display options, grid customiz
ing, totals options, color adjustments etc... The layout structure must be of ty
pe LVC_S_LAYO .
iv. Event Handler: We should define and implement an event handler class if we w
ant to handle events triggered by the ALV Grid instance. After creating ALV Grid
instance, we must register an instance of this event handler class to handle AL
V Grid events.
v. Additional Data: To trigger some additional features of ALV Grid we can have
some additional data to pass as parameters. For example, initial sorting criteri
a, buttons to be deactivated, etc...
Building Blocks
While preparing a list to be displayed via an ALV grid control, we have some bas
ic components to prepare. These are;
i. List data: Obviously, this is the data in an internal table to be listed. Sta
ndard ALV functions except sorting makes just read access to the list data. Howe
ver, sorting changes state of the internal table. The internal table holding lis

t data may be of any flat type. Deep types are only allowed when set for some fu
nctionalities of ALV Grid.
ii. Field Catalog: We use another internal table to define specifications on how
the fields of our list will be displayed. This internal table is called the fiel
d catalog . The field catalog must comprise some technical and additional informat
ion about display options for each column to be displayed. There are three proce
dures to generate the field catalog as Automatic generation , Semi-automatic generat
ion , and Manual generation . The internal table for the field catalog must be refere
nced to the dictionary type LVC_T_FCAT .
iii. Layout Structure: We fill a structure to specify general layout options for
the grid. With this structure we can set general display options, grid customiz
ing, totals options, color adjustments etc... The layout structure must be of ty
pe LVC_S_LAYO .
iv. Event Handler: We should define and implement an event handler class if we w
ant to handle events triggered by the ALV Grid instance. After creating ALV Grid
instance, we must register an instance of this event handler class to handle AL
V Grid events.
v. Additional Data: To trigger some additional features of ALV Grid we can have
some additional data to pass as parameters. For example, initial sorting criteri
a, buttons to be deactivated, etc...
Building Blocks
While preparing a list to be displayed via an ALV grid control, we have some bas
ic components to prepare. These are;
i. List data: Obviously, this is the data in an internal table to be listed. Sta
ndard ALV functions except sorting makes just read access to the list data. Howe
ver, sorting changes state of the internal table. The internal table holding lis
t data may be of any flat type. Deep types are only allowed when set for some fu
nctionalities of ALV Grid.
ii. Field Catalog: We use another internal table to define specifications on how
the fields of our list will be displayed. This internal table is called the fiel
d catalog . The field catalog must comprise some technical and additional informat
ion about display options for each column to be displayed. There are three proce
dures to generate the field catalog as Automatic generation , Semi-automatic generat
ion , and Manual generation . The internal table for the field catalog must be refere
nced to the dictionary type LVC_T_FCAT .
iii. Layout Structure: We fill a structure to specify general layout options for
the grid. With this structure we can set general display options, grid customiz
ing, totals options, color adjustments etc... The layout structure must be of ty
pe LVC_S_LAYO .
iv. Event Handler: We should define and implement an event handler class if we w
ant to handle events triggered by the ALV Grid instance. After creating ALV Grid
instance, we must register an instance of this event handler class to handle AL
V Grid events.
v. Additional Data: To trigger some additional features of ALV Grid we can have
some additional data to pass as parameters. For example, initial sorting criteri
a, buttons to be deactivated, etc...