topic events in Application Development and Automation Discussions

If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).

The STANDARD status of the function group SALV should be used as a template for a user-specific status.

As this is a frequently-used Callback event, its form routine can also be passed directly in the interface in the IMPORTING

parameter I_CALLBACK_PF_STATUS_SET.

ITEM_DATA_EXPAND USING RS_SELFIELD TYPE SLIS_SELFIELD RFLG_ALL TYPE C

Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT.

Exit for passing item entries (ITEM table) for a header record which was expanded interactively by the user.

RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header which is to be expanded.

RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table.

RS_SELFIELD is initial in this case.

CALLER_EXIT USING RS_DATA

Is called at the beginning of the function module to make

special settings. It is not usually used.

List processing events

IMPORTANT: The application Callback routine must not manipulate

the internal output table and/or its header record. This

restriction applies to all Callbacks which are called in the list output and run under the 'List processing events'.

TOP_OF_LIST no USING parameter

Information output at the start of the list

END_OF_LIST no USING parameter

Information output at the end of the list

TOP_OF_PAGE no USING parameter

Equivalent to the list processing TOP-OF-PAGE event

END_OF_PAGE no USING parameter

Not available for hierarchical-sequential lists.

Information output at the end of a page. This is only called for printing.

TOP_OF_COVERPAGE no USING parameter

The selection information and list status are output together(if they exist) on a separate page by default. See also the documentation of the parameters:

IS_PRINT-NO_COVERPAGE

IS_PRINT-NO_PRINT_SELINFOS

IS_PRINT-NO_PRINT_LISTINFOS

IS_LAYOUT-GET_SELINFOS

The user can format the header area of the 'cover page' himself or herself by specifying a Callback routine for this event.

END_OF_COVERPAGE no USING parameter

Analogously to TOP_OF_COVERPAGE the user can add other

information to the information output by ALV (selection

information, list status) at this event.

FOREIGN_TOP_OF_PAGE no USING parameter

The Top-of-page event is always processed in ALV and is only

passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with

additional information about the list record selected and

displayed by ALV).

In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller.

The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.

FOREIGN_END_OF_PAGE no USING parameter

The event end-of-page is always processed in ALV and only passed

to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).

In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller.

The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.

BEFORE_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO

Output information before each output line. Should only be used in justified cases because it costs a lot of performance.

AFTER_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO

Output information after each output line. Should only be used in justified cases because it costs a lot of performance.

regards,

sai ramesh

Re: events

Former Member — Wed, 07 Mar 2007 08:44:26 GMT

hi,

Events in ALV are as follows,

CALLER_EXIT

USER_COMMAND

TOP_OF_PAGE

TOP_OF_COVERPAGE

END_OF_COVERPAGE

FOREIGN_TOP_OF_PAGE

FOREIGN_END_OF_PAGE

PF_STATUS_SET

LIST_MODIFY

TOP_OF_LIST

END_OF_PAGE

END_OF_LIST

AFTER_LINE_OUTPUT

BEFORE_LINE_OUTPUT

REPREP_SEL_MODIFY

SUBTOTAL_TEXT

GROUPLEVEL_CHANGE

u can find the ALV events with the help of function module called 'REUSE_ALV_EVENTS_GET.

ALV function moduls are as follows,

REUSE_ALV_BLOCK_LIST_APPEND

REUSE_ALV_BLOCK_LIST_DATA_GET

REUSE_ALV_BLOCK_LIST_DATA_SET

REUSE_ALV_BLOCK_LIST_DISPLAY

REUSE_ALV_BLOCK_LIST_HS_APPEND

REUSE_ALV_BLOCK_LIST_INIT

REUSE_ALV_BLOCK_LIST_REFRESH

REUSE_ALV_BLOCK_STATUS_GET

REUSE_ALV_CHECKBOX_SET

REUSE_ALV_COMMENTARY_WRITE

REUSE_ALV_EVENTS_GET

REUSE_ALV_EVENTS_TRANSFER

REUSE_ALV_EVENT_NAMES_GET

REUSE_ALV_FIELDCATALOG_MERGE

REUSE_ALV_HIERSEQ_LIST_DISPLAY

REUSE_ALV_HS_LIST_WIDTH_GET

REUSE_ALV_HS_TABLES_GET

REUSE_ALV_LIST_DISPLAY

REUSE_ALV_LIST_LAYOUT_INFO_GET

REUSE_ALV_LIST_LAYOUT_INFO_SET

REUSE_ALV_LIST_SELECTIONS_GET

REUSE_ALV_LIST_SELECTIONS_SET

REUSE_ALV_LIST_WIDTH_GET

REUSE_ALV_POPUP_TO_SELECT

REUSE_ALV_GRID_COMMENTARY_SET

REUSE_ALV_GRID_DISPLAY

REUSE_ALV_GRID_DISPLAY_LVC

REUSE_ALV_GRID_LAYOUT_INFO_GET

REUSE_ALV_GRID_LAYOUT_INFO_SET

REUSE_ALV_TREE_DISPLAY_OM

regards,

seshu.