reporting

[Former Member]

can any give me sequence of events in 1 classical

2 interactive

3 alvs

[Former Member]

hi suresh,

sequence ofevents in reports,

classical reporting,

initiliazation.

at selection-screen ouptut.

at selection-screen.

start-of-select.

end-of-selection.

if u use <b>at pf</b> and <b>at use-command</b> these'll come b/w start-of and end of selection.

interactive repoting,

sequence is same as above,

two events can add,

at line-selection and top-of-page during line.

same sequesce for alv.

regards,

seshu.

[Former Member]

hi,

in classical reports sequence of events are

1. initialization.

2. at selection-screen.

3. start-of-selection.

4.top-of-page.

5.end-of-selection.

6. end-of-page.

in interactive reports sequence of events are

1. initialization.

2. at selection-screen.

3. start-of-selection.

4.top-of-page.

5. at user-command.

6. at line-selection.

7.end-of-selection.

8. end-of-page.

we can also some events like

-> at selection-scren on output.

-> at selection-screen on value request.

-> at selection-screen on help request.

in alv we some extra events which we can get from SLIS.

if helpful reward some points.

with regards,

suresh.

[Former Member]

Hi,

Driver events are

initialization

at selection-screen

start-of-selection

get

end-of-selection

User events are:

at line-selection

at pfn

at user-command

Program events are

top-of-page

end-of-page

Thanks,

Sandeep.

[Former Member]

Hi suresh

The program then follows this sequence of steps:

It triggers the initialization event, causing the code belonging to initialization to be executed. If you have not coded an initialization event in your program, the driver program skips this step.

It shows the selection screen for your program. (A selection screen is the screen that contains the input fields for your parameter statements.) If your program doesn't have a selection screen, it skips this step.

It triggers the start-of-selection event, causing the code belonging to that event to be executed. If you have not coded a start-of-selection event in your program, it skips this step.

It triggers the end-of-selection event in your program, executing all of the code belonging to it. If you haven't coded an end-of-selection, it skips this step.

It shows the output list to the user.

The order of execution for events is determined by the driver program, not by your program. Therefore, you can code the events in any order and the execution order will still be the same. The order of events in your program doesn't matter; they will always be triggered in the same sequence by the driver program.

There will be different types of events in ABAP.

So be clear what events you need ind etail.

Some related to Classical reports, some to Interactive reports and some related to Module Pool Programming(Dialog)

Events in Dialog Program

PBO - Process Before Output

PAI - Process After Input

POH - Process on Help

POV - Process on Valure Request.

Events in ABAP Programming

INITIALIZATION

AT SELECTION-SCREEN OUTPUT

AT SELECTION-SCREEN

START-OF–SELECTION.

TOP OF PAGE

END OF PAGE

END-OF-SELECTION.

Control Break events related to Internal Tables:

AT NEW FIELD

AT END OF FIELD

AT FIRST

AT LAST

Events in Interactive Report

AT USER-COMMAND.

AT LINE-SELECTION

AT PF-FUNCTION KEY

http://www.sap-img.com/abap/events-related-to-reporting.htm

The program then follows this sequence of steps:

It triggers the initialization event, causing the code belonging to initialization to be executed. If you have not coded an initialization event in your program, the driver program skips this step.

It shows the selection screen for your program. (A selection screen is the screen that contains the input fields for your parameter statements.) If your program doesn't have a selection screen, it skips this step.

It triggers the start-of-selection event, causing the code belonging to that event to be executed. If you have not coded a start-of-selection event in your program, it skips this step.

It triggers the end-of-selection event in your program, executing all of the code belonging to it. If you haven't coded an end-of-selection, it skips this step.

It shows the output list to the user.

The order of execution for events is determined by the driver program, not by your program. Therefore, you can code the events in any order and the execution order will still be the same. The order of events in your program doesn't matter; they will always be triggered in the same sequence by the driver program.

There will be different types of events in ABAP.

So be clear what events you need ind etail.

Some related to Classical reports, some to Interactive reports and some related to Module Pool Programming(Dialog)

Events in Dialog Program

PBO - Process Before Output

PAI - Process After Input

POH - Process on Help

POV - Process on Valure Request.

Events in ABAP Programming

INITIALIZATION

AT SELECTION-SCREEN OUTPUT

AT SELECTION-SCREEN

START-OF–SELECTION.

TOP OF PAGE

END OF PAGE

END-OF-SELECTION.

Control Break events related to Internal Tables:

AT NEW FIELD

AT END OF FIELD

AT FIRST

AT LAST

Events in Interactive Report

AT USER-COMMAND.

AT LINE-SELECTION

AT PF-FUNCTION KEY

http://www.sap-img.com/abap/events-related-to-reporting.htm

reward all helpfull answers

Regards

Pavan

[Former Member]

hi all thanks for solving my query