Solved: Re: define event

Former Member · ‎2008 Feb 18

hi,

where i can define event and how?

Regards

Former Member · ‎2008 Feb 18

EVENTS

ABAP program

INITIALIZATION.

pa_date = pa_date - 7.

START-OF-SELECTION.

WRITE pa_date.

The easiest events to understand are those for an executable program (type 1).

The ABAP runtime system calls event blocks in a sequence designed for generating and processing

lists:

First, the INITIALIZATION event block is called

Then a selection screen is sent to the presentation server

After the user leaves the selection screen, START-OF-SELECTION is called

If the START-OF-SELECTION event block contains the ABAP statements WRITE, SKIP or ULINE,

a list buffer is filled.

Event Blocks in Executable Programs

INITIALIZATION.

START-OF-SELECTION.

Default event block:

START-OF-SELECTION

Event blocks are processing blocks that are called by the ABAP runtime system. The sequence if which

they are processed is determined by the runtime system.

In executable programs, there are different event blocks for the various tasks involved in creating lists.

Syntax: Event Blocks

REPORT ...

PARAMETERS: pa_date LIKE sy-datum DEFAULT sy-datum.

INITIALIZATION. " Default values for selection screen

pa_date = pa_date - 7.

START-OF-SELECTION.

" Start of data processing

WRITE pa_date.

The sequence of event blocks in the

source code has no effect on the sequence in

which they are called by the ABAP runtime system.

call

initialization

STARTOFSELECTION..

In an ABAP program, an event block is introduced with an event key word. It ends when the next

processing block starts. There is no ABAP statement that explicitly concludes an event block.

Event blocks are called by the ABAP runtime system. The order in which you arrange the event blocks in

your program is irrelevant - the system always calls them in a particular order.

START-OF-SELECTION is the first event for processing data and generating a list. It is called by the

ABAP runtime system as soon as you have left the standard selection screen.

INITIALIZATION is an event that you can use if you need to set a large number of default values. This

event block allows you to set default values that can only be determined at runtime. In the above

example, the date 'A week ago' is calculated and placed in data object pa_date. The ABAP runtime

system then sends a selection screen to the presentation server containing the calculated value as a

default. The value can, of course, still be changed.

Selection screen processing is event-driven. Events are ABAP processing blocks that are called by the

runtime system in a particular order and processed sequentially. In the program, each event is

introduced by an event keyword. The processing block ends when the next event block starts, or the

definition of a subroutine or dialog module occurs.

AT SELECTION-SCREEN OUTPUT is processed before the selection screen is displayed on the

screen. You can use this event to modify the selection screen dynamically.

AT SELECTION-SCREEN ON HELP-REQUEST FOR <sel_field> and

AT SELECTION-SCREEN ON VALUE-REQUEST FOR <sel_field> allow you to define your own F1

and F4 help.

AT SELECTION-SCREEN is processed when the user presses ENTER or chooses another function on

the selection screen.

-

An ABAP program consists of a sequence of processing blocks (events) that are processed by the

runtime system in a particular order.

LOAD-OF-PROGRAM is triggered directly after the system has loaded a program with type 1, M, F, or S

into an internal session. The processing block is executed once only for each program in each internal

session.

INITIALIZATION is processed in executable (type 1) programs, directly before the selection screen is

displayed. You can use the corresponding processing block to pre-assign values to the parameters and

selection options on the selection screen.

START-OF-SELECTION is processed after the selection screen has been processed. If you are

working with a logical database, the corresponding GET events are triggered after START-OFSELECTION.

END-OF-SELECTION is processed after all of the data has been read, and before the list is displayed.

TOP-OF-PAGE is an event in list processing. The associated processing block is always executed when

you start a new page in the list.

module pool

GET GET ...

You can only assign a report transaction to an executable (type 1) program. In a report transaction,

the system calls particular events in a fixed sequence, and calls a series of standard screens. The

following steps occur when you run a report transaction:

First, the LOAD-OF-PROGRAM event is triggered.

Then the INITIALIZATION event is triggered.

Next, the standard selection screen is called (if you have declared one), and its corresponding events

are triggered: AT SELECTION-SCREEN OUTPUT and AT SELECTION-SCREEN.

Next, the START-OF-SELECTION event is triggered. (This is the default event block. If you omit this

event keyword, all statements that are not assigned to another processing block are treated as though

they belong to it.)

If you have attached a logical database to your program, the system triggers the GET <node> and GET

<node> LATE events.

Then the END-OF-SELECTION event is triggered.

You can also include screen processing (as in module pools) by using the CALL SCREEN statement.

You can start executable (type 1) programs without using a transaction code. You can also run them in

the background.

(C) SAP AG BC402 2-11

SAP AG 1999

WRITE ...

SKIP ...

ULINE.

List Processing Events

TOP TOP-OF-PAGE.

EOP END-OF-PAGE.

AT LINE-SELECTION.

WRITE ...

SKIP ...

ULINE.

ALS

List buffer for basic list

AUC AT USER-COMMAND.

List buffer for detail list

If you fill the list buffer of the basic list (using the WRITE, SKIP, and ULINE statements), two further

events are triggered: At the beginning of each new page, the TOP-OF-PAGE event is triggered, and the

END-OF-PAGE event is triggered at the end of each page.

Once the END-OF-SELECTION event block has been processed, interactive list processing starts.

The system displays the formatted basic list . The user can now trigger further events.

If the user double-clicks a line or triggers the function code PICK in some other way, the AT LINESELECTION

event is triggered. In the standard list status, this function code is always assigned to

function key <F2>. In turn, <F2> is always assigned for a mouse double-click.

If you fill the list buffer of the detail list (of which you may have up to twenty) using the WRITE, SKIP,

and ULINE statements, two further events are triggered:

At the beginning of each new page, the TOP-OF-PAGE DURING LINE-SELECTION event is triggered,

and the END-OF-PAGE DURING LINE-SELECTION event is triggered at the end of each page. (These

events are not displayed in the graphic.) Interactive list processing is started again. The system

displays the formatted detail list (screen 120).

Any other function codes that have not been "trapped" by the system trigger the event AT USERCOMMAND.

DONT FORGET TO REWARD IF USEFUL

Former Member · ‎2008 Feb 18