events

[Former Member]

wht are the events in repots,explain it

classical,

interactive,

alv

module pool

[Former Member]

HI

CLASSICAL REPORT EVENTS :

INITIALIZATION : TO INITIALISE THE SELECTION SCREEN ELEMENTS

START- OF-SELECTION: NORMALLY WE WRITE THE REPORT LOGIC HERE

AT SELECTION-SCREEN : SELECTION SCREEN VALIDATIONS

WHETHER U ENTERED IS CORRECT OR NOT AT SELECTION SCREEN LEVEL

AT SELECTION-SCREEN ON FIELD : TO PROVIDE INPUT HELP[S FOR THE FILDS AT SELECTION SCREEN

FOR EX : MATNR IF U PREESS F4 AT SELECTION SCREEN.

TOP-OF-PAGE : TO PROVIDE LIST HEADING ( OUTPUT HEADINGS)

END-OF-PAGE : TO PROVIDE FOOTER I.E., PAGE NUMBERS

END-OF-SELECTION : TO FREE THE MEMORY , NO NEED OF USING THIS SPECIALLY

_______________________

INTERACTIVE EVENTS :

__________________________

AT LINE-SELECTION : IT IS USED TO HENDLE SECONDARY LISTS

AT USER-COMMAND : TO PROVIDE OUR OWN GUI ( PUSH BUTTONS ETC) AT OUTPUT

AT PF-STATUS : TO PROVIDE FUNCTIONS FOR OUR OWN PROVIDED GUI BUTTONS AT OUTPUT

LOAD-OF-PROGRAM.

Triggers the associated event in an internal session after loading a program of type 1, M, F, or S. Also runs the associated processing block once and once only for each program and internal session.

INITIALIZATION.

the associated event is executed before the selection screen is displayed.

START-OF-SELECTION.

In an executable program, the corresponding event is processed after the selection screen has been displayed and before data is read using a logical database

GET

Triggers the associated events when data is read in an executable (type 1) program using a logical database.

END-OF-SELECTION.

The END-OF-SELECTION event is triggered in type 1 programs once the logical database has finished reading all data and before the list processor is started.

END of page and top page

while displaying the list as the name suggest fired at the top and end of page

******************************************

The event are triggered depended on the way the output is generated .

for eg:

Initialization : triggered when the report is loaded in memory.

At selection-screen output : triggered when the selection screen is loaded in memory before being displayed.

At selection-screen / <field> : before leaving the selection screen.

start-of-selection : the first event for displaying the report.

end-of-selection : after the start-of-selection is completed.

classiscal report events.

top-of-page : every time a new page is started in the list.

end-of-page : every time the list data reaches the footer region of the page.

interactive report events.

top of page during line selection : top of page event for secondary list.

at line-selection : evey time user dbl-clicks(F2) on the list data.

at pF<key> : function key from F5 to F12 to perform interactive action on the list.

*****************************************************************************************

There are 4 events in Dialog programming.(main events)

PBO - Process Before Output

PAI -Process After Input

POV-Process on Value Request

POH-Process on Help Request

As the name suggest PBO is process before OUTPUT, ie the the processing before screen is displayed

and PAI processing after screen is diplayed

now actually i dont know what your code does

but still i can figure out that

During the PBO loop, a loop is executed at it_vbak, where the row index corresponds to the current row of the table control.

During the PAI loop, the rows of the internal table, whose row index corresponds to the current row of the table control, are overwritten with the contents of the work area(not present here)

After the PAI loop, user input is processed in the module USER_COMMAND.

AT SELECTION-SCREEN

This event is processed before leaving the Selection Screen i.e. when the selection screen has been processed (at the end of PAI once the ABAP runtime environment has passed all the input data from selection screen to the ABAP program).

This event is used to validate the input provided through selection screen. If an error message occurs in this processing block, the selection screen is redisplayed with all of its fields ready for input. This allows you to check input values for consistency.

AT SELECTION-SCREEN OUTPUT

This event gets triggered for the first time when the screen is building up and the screen is about to appear. It gets triggered again and again for every dialog step/the selection screen is refreshed/ enter key is pressed.

This event is to control the display of the screen at runtime. lilke hiding the fields, making the fields Active/Inactive, to modify the field attributes. It is a PBO Event.

[Former Member]

Hi,

CLASSICAL REPORT EVENTS :

LOAD OF PROGRAM:

INITIALIZATION :

START- OF-SELECTION:

AT SELECTION-SCREEN :

AT SELECTION-SCREEN ON FIELD :

TOP-OF-PAGE :

END-OF-PAGE :

ITERACTIVE EVENTS :

ALONG WITH THE ABOVE EVENT THE FOLLOWING

AT LINE-SELECTION :

AT USER-COMMAND :

AT PF-STATUS :

*****************************************************************************************

There are 4 events in Dialog programming.(main events)

PBO - Process Before Output

PAI -Process After Input

POV-Process on Value Request

POH-Process on Help Request

For event in alv go to pattern and type REUSE* u will get all the function modules and go to SLIS fro events there are so many,

Regards,

kavitha.k