EVENTS IN CLASSICAL REPORTS of SAP ABAP

EVENTS IN CLASSICAL REPORTS:

CLASSICAL REPORT:- A report which can generate only one list, that is Basic List, is called classical
report. First List of a report is called BASIC LIST.

EVENTS IN CLASSICAL REPORTS:

1. INITIALIZATION.
2. AT SELECTION-SCREEN.
(a) AT SELECTION-SCREEN ON <FIELD>.
(b) AT SELECTION-SCREEN OUTPUT.
(c) AT SELECTION-SCREEN ON VALUE-REQUEST FOR <FIELD>.
3. START-OF-SELECTION.
4. TOP-OF-PAGE.
5. END-OF-PAGE.
6. END-OF-SELECTION.

INITIALIZATION:- This is the first event to be triggered. This event is triggered before
the selection-screen is displayed. This event is used to give default vales to selectionscreen
fields.

AT SELECTION-SCREEN:- This event is triggered after giving input in selectionscreen

fields. This event is used to handle the user actions on the screen. This is also used
to validate all the selection-screen fields.

AT SELECTION-SCREEN ON <FIELD>:- This event is used to validate a particular

field present on the selection-screen.

AT SELECTION-SCREEN OUTPUT:- This event is used to change the selection screen

properties dynamically.

AT SELECTION-SCREEN ON VALUE-REQUEST FOR <FIELD>:- This event is

used to give F4 help to a particular field resent on the selection-screen.

START-OF-SELECTION:- The main logic of the program is written in this event.

Usually write statement is recognized from this event.

TOP-OF-PAGE:- This event is used to write something on top of every page. The first
write statement or output statement (SKIP) of a page triggers this event.

END-OF-PAGE: - This event is used to write something at end of every page. Last line
of the page triggers this event. We have to allocate the line for end of page.

END-OF-SELECTION:- Usually program output is written in this event. This event is

used to handle abnormal termination of the program. The stop statement written in startof-
selection event takes the control to end-of-selection event.

No event is mandatory. But default event is start-of-selection.

Because ABAP is an event driven language there is no need to maintain the order
of the events. System will take care of the order of the events.

The write statement written in initialization event can not be seen if the program
is having selection-screen, because initialization event is triggered before the selection screen
is displayed. If the program is not having the selection-screen we can see the write
statement written in Initialization event.
Starting of new event symbolizes ending of previous event.

The STOP statement in start-of-selection takes the control to end-of-selection

statement.

Skip statement also triggers top-of-page event.

Declarations should be written before initialization event.