*which event trigger by event wise in classical, interactive, alv reports*

[Former Member]

Hi Experts,

can any body tell about

event wise trigger in

Q(1). classical reports.

( from initial)

Q(2). Interactive reports.

(from initial)

Q(3). ALV List and Grid

(from initial)

points will be rewarded.

Thanks,

Balakrishna.

[Former Member]

hi,

Please search the forums first before posting any question. This question is posted many times before ... Here are the below related threads ..

/message/5179042#5179042 [original link is broken]

Regards,

Santosh

[Former Member]

please see in help.sap.com.

or type them in google and see.

[GauthamV]

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

SM62 is the Transaction code for creating Events.

Here you can see

System event names

User event names

System event names are standard events .

User event names are customized event name, here click "Maintain" and double click it. it takes to another screen . From here you can create your customized Events.

reward points if hlpful.

[Former Member]

Hi,

Events in alv and their FM The main events in alv and their FM and why we use these:

1. SLIS_PRINT_ALV.

2. SLIS_T_LISTHEADER.

3. SLIS_T_EVENT.

4. SLIS_T_SORTINFO_ALV.

5. SLIS_T_LAYOUT_ALV.

6. SLIS_T_FIELDCAT_ALV.

and in classic reports what is the sequence of events: === Events are

At selection-screen output.

Initialization.

At selection-screen on field

At selection-screen on end of field

At selection-screen on Radiobutton Group R1. (If you have any radio buttons)

At selection-screen on block b1. (If you have any blocks)

Start-of-selection.

Get node. (if the data is retreived from a logical database)

Get node late. (if the data is retreived from a logical database)

Top-of-page. (if the write statement is in the end-of-selection event or we can say that before the first write statement)

end-of-selection.

and fuction modules are

LISTHEADER - Is used to print the header information in the ALV List. Name, Date, Time, ALV Name and other details are called as Header information. EVENT - Basically this is the FM to handle Event's. When the user needs to do some event operation like when double clicking the a particular field we need to perform some operation. These events are captured by this FM. LAYOUT - This FM is used to define the layout of the List. There are many options available in this FM to define the Layout style. FIELDCAT - These are used to populate the List header. We can change them according to our req.

User-defined Text Output Event

Application

print_end_of_list

Define output text to be printed at the end of the entire list

print_top_of_list

Define output text to be printed at the beginning of the entire list

print_end_of_page

Define output text to be printed at the end of each page

print_top_of_page

Define output text to be printed at the beginning of each page

subtotal_text

Define self-defined subtotals texts

Mouse-controlled Actions in the Grid Control Event

Application

button_click

Query a click on a pushbutton in the ALV Grid Control

double_click

Query a double-click on a cell of the ALV Grid control

hotspot_click

Query a hotspot click on columns defined for this purpose in advance

onDrag

Collect information when elements of the ALV Grid Control are dragged

onDrop

Process information when elements of the ALV Grid Control are dropped

onDropComplete

Perform final actions after successful Drag&Drop

onDropGetFlavor

Distinguish between options for Drag&Drop behavior

Processing of Self-defined and Standard Functions Event

Application

before_user_command

Query self-defined and standard function codes

user_command

Query self-defined function codes

after_user_command

Query self-defined and standard function codes

Definition of Self-defined Functions Event

Application

toolbar

Change, delete or add GUI elements in the toolbar

menu_button

Define menus for menu buttons in the toolbar

context_menu_request

Change context menu

onf1

Define self-defined F1 help

All of these can be found under type group SLIS.

• Events

SLIS_EV_ITEM_DATA_EXPAND TYPE SLIS_FORMNAME VALUE 'ITEM_DATA_EXPAND',

SLIS_EV_REPREP_SEL_MODIFY TYPE SLIS_FORMNAME VALUE 'REPREP_SEL_MODIFY', SLIS_EV_CALLER_EXIT_AT_START TYPE SLIS_FORMNAME VALUE 'CALLER_EXIT',

SLIS_EV_USER_COMMAND TYPE SLIS_FORMNAME VALUE 'USER_COMMAND',

SLIS_EV_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE',

SLIS_EV_DATA_CHANGED TYPE SLIS_FORMNAME VALUE 'DATA_CHANGED',

SLIS_EV_TOP_OF_COVERPAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_COVERPAGE',

SLIS_EV_END_OF_COVERPAGE TYPE SLIS_FORMNAME VALUE 'END_OF_COVERPAGE',

SLIS_EV_FOREIGN_TOP_OF_PAGE TYPE SLIS_FORMNAME

VALUE 'FOREIGN_TOP_OF_PAGE', SLIS_EV_FOREIGN_END_OF_PAGE TYPE SLIS_FORMNAME

VALUE 'FOREIGN_END_OF_PAGE',

SLIS_EV_PF_STATUS_SET TYPE SLIS_FORMNAME VALUE 'PF_STATUS_SET',

SLIS_EV_LIST_MODIFY TYPE SLIS_FORMNAME VALUE 'LIST_MODIFY',

SLIS_EV_TOP_OF_LIST TYPE SLIS_FORMNAME VALUE 'TOP_OF_LIST',

SLIS_EV_END_OF_PAGE TYPE SLIS_FORMNAME VALUE 'END_OF_PAGE',

SLIS_EV_END_OF_LIST TYPE SLIS_FORMNAME VALUE 'END_OF_LIST',

SLIS_EV_AFTER_LINE_OUTPUT TYPE SLIS_FORMNAME VALUE 'AFTER_LINE_OUTPUT', SLIS_EV_BEFORE_LINE_OUTPUT TYPE SLIS_FORMNAME VALUE 'BEFORE_LINE_OUTPUT',

SLIS_EV_SUBTOTAL_TEXT TYPE SLIS_FORMNAME VALUE 'SUBTOTAL_TEXT'.

Reward pts if usefull.

Regards,

Dhan