Process Flow of Events in ABAP Report

Hi every one,
Could some body explain about each and every event how and when it trigerrs.
I am always confusing with these events.
Plz tell me abt all the Driver events, User Events, Program events how they are Trigerred .
Explain me with complete details.
And more over what is the first event trigerred if i have all the events in my report program.
If you have Good Links plz do send me .
Thanks & Regards,
Sudheer.

Hi,
Chk this info.
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.
Regards
Sandeep REddy

Similar Messages

What is the need of END-OF-SELECTION event in ABAP reporting

Hi,
Can anyone explain the need of the END-OF-SELECTION event in ABAP Reports?
This event is used to terminate the previous event. Is that right? or is there any specific use of it?
and when exactly we use this event while writing a report? I mean what purpose?
Thanks,
Paddu.

Hi,
END-OF-SELECTION makes more sense when you are using logical database in your program.
See these links.
http://help.sap.com/saphelp_46c/helpdata/en/34/8e74266df74873e10000009b38f9b8/frameset.htm
http://help.sap.com/saphelp_46c/helpdata/en/9f/db9aca35c111d1829f0000e829fbfe/frameset.htm
After all the data has been selected END-OF-SELECTION event writes the data to the screen
The END-OF-SELECTION event is triggered in executable programs once the logical database has finished reading all data and before the list processor is started.
Try to go thro this link.
http://help.sap.com/saphelp_46c/helpdata/en/9f/db9a1435c111d1829f0000e829fbfe/frameset.htm
Mostly end-of-selection is used in logical data base. It is not mandatory.
Ex:
If you use a logical database in your report then this event is mandatory because when all the data selection from the database is finished this events get triggers.
For example if you are populating a internal table using a logical data base event 'GET' then you need this event because if you don't use this you get display again and again for each selection.
START-OF-SELECTION.
GET PERNR.
itab-pernr = pernr-pernr.
append itab.
*this get triggers after all selection from database.
END-OF-SELECTION.
loop at itab.
write:/ itab-pernr.
endloop.
Regards,
Padmam.

Pging Over flow runtime error in Abap report

Hi all,
I have a report if it is exuted for higher selection criteria in the production ,
its giving a run time error .what could be the problem??
Thanks,
Regards,
Rajesh S.

Hi,
The runtime error occured, because of the complex program time exceeds for execution. Ask the basis time to increase the execution time or make sure that use all primary keys in select statements.
Check the any select statements in LOOPs.
Otherwise make the selection screen with mandatory fields.
Regards,
Anil

Training and Event management.Process Flow..

Hi, Experts,
Can any body give me some notes on Training and event management and process flow also like integration between ECC-6.0 to Non SAP
1.Training request
2.Appraisal documents for performance feedback
3.Tracking Feedback processes
Pls help me in configuring these services.
With Regards,
San Rao.

Hi san rao,
as per your reply you using the new appraisal template and also you have released the template now simply run the BSP application HAP_DOCUMENT and access the appraisal documents
attach these BSP applications in your portal system.
following pages of the above application will be help full
documents_todo
documents_received_open2
documents_where_participated
Regards,
Umesh Chaudhari.

Start BPM process from ABAP report. Need some investigations.

Hi there!
I have to start a BPM process from ABAP report. I found an article http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10d75b45-7fef-2b10-bc8e-c6012e0a9457?QuickLink=index&overridelayout=true and have done everything it describes but the process doesn't start.
What I've done:
1) Created a service proxy in SE80.
2) Created a logical port in SOAMANAGER.
3) Write a code to start a WebService in ABAP Report.
But when I start a program nothing happens, no errors.
What analysis I did:
1) See logs and traces in SOAMANAGER - there is nothing appears after I start the report.
2) Tried to test connection to my WebService in SM59 - the connection works, but it use a POST method instead of GET:
Error: com.sap.engine.services.webservices.espbase.server.additions.wsa.WSAddressingException: com.sap.SOA.wsr.030104 - Expected request method POST. Found GET.
But I think it is OK and from the report it use a right method.
3) Tried to delete a logical port - the error of communication problem appears. So it means that all settings are right.
4) No logs in NWA logs
My thoughts - if there is not any errors and no result, it can be because the user authorization. E.g. it tried to start a process by a user who doesn't have SAP_BPM_SuperAdmin role. But I can't find a way how to check what really happens. So I want to ask for a help, colleagues:).

Dear Kirill Zhuklinets,
Can you share your solution as i am facing the same error while trying to consume BPM webservice from SRM ECC
Error Message from SRM ECC :
Exception occurred in communication framework:Error in HTTP Framework:405Method Not Allowed
Log from BPM Web service
Error: process()
[EXCEPTION]
com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException: com.sap.engine.services.webservices.espbase.server.additions.wsa.WSAddressingException: com.sap.SOA.wsr.030104 - Expected request method POST. Found GET.
Please share your solution..
Regards,
Yasin

How to setup PCG Flow Rule Process flow with Business Event subscription

Hi,
How to setup PCG Flow Rule Process flow with Business Event subscription type?
When should Business Events be used?
The latest user guide does not provide ay information on this functionality of Flow rules.
Thanks

You should find it's usage noted in the new PCG user guide on page 3-26 under the heading "Configuring Workflow/Event Rules". This way you can have a Flow Rule call a business event component or a workflow. This would be kicked off within a process flow as one of the steps.
I hope that helps.

Sequence of events execution in ABAP reports

can anyone explain me the Sequence of events execution in ABAP reports

Ámit Güjärgoüd wrote:
> search-before-post Event Must before any posting.Else <delete-after-input event triggered by moderator> would be trigger and thread may be going to Dump as well without ST22 information(What haapend,How to correct error) available
>
> Edited by: Ámit Güjärgoüd on Oct 7, 2008 7:42 AM
this looks perfect ABAP event sequence example.

Executing ABAP Report- No memory for processing HTTP, HTTPS or SMTP query

Hello experts,
I am getting same error while running ABAP Report- /OSP/TRIGGER_LEAVE_SCHEDULER
Error-
No memory for processing HTTP, HTTPS or SMTP query .
Please help.
Regards,
Shashank

Hello
This should solve it
1562539 - No memory for processing HTTP, HTTPS, or SMTP queries.
Thanks
Alagappan

Can anyone give me the process flow for MTBF report?

hi all
can anyone give me the process flow of MTBF Report?
regards
asha

And Full form of MTBF is ???
Regards
Amitava

Process flow for Maintenance Event Builder integrated with PS

Dear EAM Master ,
Good Day. Can anyone show me how's the process flow for Process flow for Maintenance Event Builder integrated with PS.
Appreciate.
Thank you.

[SAP Help|http://help.sap.com/erp2005_ehp_05/helpdata/en/d7/d0b83a47d0c649e10000000a114084/frameset.htm]
Thanks
Narasimhan

Process chain with abap report

Hi all,
I have an abap report which is used to fill a table . This report is scheduled on daily basis .
Now i want to do is , whenever this report completes my process chain should start in BI so that data in table can be filled in GDS .
How to do that ???
Please help.
Regards
Shweta

Hi,
You can do it in two ways.
1) Include the ABAP program as the first process in your process chain. Once the program is completd the following processes will continue.
2) Use "After Job" Scheduling options to schedule your process chain.
Mention the job name of the program in the After job. The process chain will get triggered once the job is completed.
Regards,
Balaji V

Events in Interactive reports

hi gurus,
i want detailed explanation each n every event of standard report...
Regards
baskar

HI
<b>INITIALIZATION</b>
This event keyword defines an event block whose event is triggered by the ABAP runtime environment during the flow of an executable program, directly after LOAD-OF-PROGRAM and before the selection screen processing of any existing standard selection screen. This gives you the one-time opportunity to initialize the input fields of the selection screen, including those defined in the logical database linked with the program.
When an executable program defines a standard selection screen, it is called again by the ABAP runtime environment after execution, which triggers the INITIALIZATION event again. In this case, initializing parameters or selection criteria of the selection screen has no effect, because they are automatically supplied with the preceding user inputs from the selection screen during the selection screen event AT SELECTION-SCREEN OUTPUT. To explicitly initialize the selection screen for each call, you must use the event AT SELECTION-SCREEN OUTPUT.
<b>START-OF-SELECTION</b>
This event keyword defines an event block whose event is triggered by the ABAP runtime environment when calling the executable program selection screen processing of a selection screen.
In an executable program, all statements that are not declarations, and are listed before the first explicit processing block, are assigned to this event block. If the program does not contain an explicitly defined event block START-OF-SELECTION, these statements form the complete event block START-OF-SELECTION. If a program contains an explicitly defined event block START-OF-SELECTION, these statements are added to the beginning of the event block. If the program contains no explicitly defined event blocks, these statements form the entire event block START-OF-SELECTION.
If the program is linked to a logical database, preparations can be made here before the logical database reads data. If the program is not linked to a logical database, this event block even displays a "main program" from which procedures or screen layouts are called.
<b>GET node</b>
Use GET to handle two types of events after submitting executable programs: Get events and events at the end of a hierarchy level of a logical database. If during a GET event a list is written, previously an automatic line feed is created.
The event blocks after GET are implemented internally as procedures. Declarative statements in GET event blocks create local data.
<b>END-OF-SELECTION</b>
This statement defines an event block, whose event is raised by the ABAP-runtime environment during the calling of an executable program , if the logical database, with which the program is linked, has completely finished its work.
In this event block, all data read by the logical data base , can be processed summarically. In an executable program without logical data base, there is no need to implement the event block END-OF-SELECTION.
<b>LOAD-OF-PROGRAM</b>
This event keyword defines an event block whose event is triggered by the ABAP-runtime environment when an executable program, a module pool, a function group or a sub-routine pool is loaded in the internal session.
When calling a program through SUBMIT or through a transaction code, then, at every call, a new internal session is opened and the event block is executed once at every call. You can initialize global data objects of the program here.
At the first call of an external Procedure (sub-program or function module), the framework program of the called procedure is loaded into the internal session of the caller, thus triggering the event LOAD-OF-PROGRAM. The event block is executed before the called procedure. At any further call of a procedure of the same framework program by a caller of the same internal session, the event LOAD-OF-PROGRAM is triggered no longer.
The event LOAD-Of-PROGRAM should mainly be used to initialize global data when calling external procedures or Transactions. If you call executable programs with SUBMIT, we recommend that you use the event INITIALIZATION, as the Starting values for parameter and selection criteria are set after LOAD-OF-PROGRAM (see program flow after SUBMIT).
<b>AT SELECTION-SCREEN</b>
AT SELECTION-SCREEN selscreen_event.
This statement defines event blocks for different events selscreen_event that are triggered by the ABAP runtime environment during selection screen processing.
Selection screen events occur immediately before sending a selection screen and after certain user actions on a displayed selection screen. They assist in selection screen processing in the ABAP program.
AT SELECTION-SCREEN is triggered at least twice during actions on selection screens that are linked into another selection screen as a subscreen - first for the linked selection screen itself, and then for the linking selection screens.
The event blocks after AT SELECTION-SCREEN are implemented internally as procedures. Declarative statments in these event blocks create local data.
<b>AT SELECTION-SCREEN OUTPUT</b>
This event is triggered at the screen event PBO of a selection screen. In the event block, the selection screen can be prepared through assignments to the data objects of parameters and selection criteria and through dynamic screen modifications.
The assignments to input fields in the event block AT SELECTION-SCREEN OUTPUT always affect the selection screen and overwrite the user inputs from previous displays of the same selection screen. Assignments in the event blocks LOAD-OF-PROGRAM oder INITIALIZATION, on the other hand, only have an effect at first program start.
<b>AT SELECTION-SCREEN ON {para|selcrit}</b>
This event is triggered at the screen event PAI of a selection screen if the content of the input field of a parameter para or a line of a selection criterion selcrit was passed to the ABAP program. In the event block, the user input can be checked. Sending a warning or an error message in the event block makes the fields para and selcrit ready for input again.
No parameter that is defined as a radio button can be specified. For this purpose, the addition ON RADIOBUTTON GROUP is provided.
If a user action takes place in the dialog box for the multiple selection of a selection criterion selcrit, the entries of the selection table are passed to the program, line by line. For each line, the event AT SELECTION-SCREEN ON selcrit is triggered.
<b>AT SELECTION-SCREEN ON END OF selcrit</b>
This event is triggered after the selection table selcrit has been fully passed to the program after a user action in the dialog box for the multiple selection has taken place. In the event block, the entire selection table can be checked.
<b>AT SELECTION-SCREEN ON BLOCK block</b>
This event is triggered at the screen event PAI of a selection screen if all the input fields of a block block of the selection screen were passed to the ABAP program. In the event block, the user inputs can be checked. Sending a warning or an error message in the event block makes all the fields of the block block ready for input again.
<b>AT SELECTION-SCREEN ON RADIOBUTTON GROUP radi</b>
This event is triggered at the screen event PAI of a selection screen if all the fields of a radio button group radi of the selection screen were passed to the ABAP program. In the event block, the user input can be checked. Sending a warning or error message in the event block makes all the radion buttons of the block radi ready for input again.
The individual fields of a radio button group are not passed individually and do not trigger the event AT SELECTION-SCREEN ON par.
<b>AT SELECTION-SCREEN { ON { HELP-REQUEST | VALUE-REQUEST } FOR
{para|selcrit-low|selcrit-high} }</b>
The two events ON HELP-REQUEST and ON VALUE-REQUEST are triggered at the screen events POH and POV of a selection screen if - for the input field of a parameter para or one of the input fields of a selection criterion selcrit - the field help F1 or the input help F4 was called. Other selection events are not triggered.
In the event blocks, a self-defined field or input field can be programmed, which overrides any helps possibly defined in the ABAP Dictionary.
These event blocks can only be implemented for fields of the selection screen that are defined in the same ABAP program and not in a possibly linked logical database.
With the events for the field and input help, no data is transported between the selection screen and the ABAP program. As with general screens, suitable function modules must be used for these. The parameters and selection criteria changed for the input help are transported to the selection screen.
<b>AT LINE-SELECTION</b>
This statement defines an event block whose event is triggered by the ABAP runtime environment during the display of a screen list - provided the scren cursor is on a list line and you select a function using the function code PICK. Through the definition of this event block, the standard list status is automatically enhanced in such a way that the function code F2 and, with it, the double-click mouse function is linked up to the function code PICK.
If the function key F2 is linked with a function code different than PICK, each double click will trigger its even, usually AT USER-COMMAND, and not AT LINE-SELECTION.
<b>AT USER-COMMAND</b>
This statement defines an event block whose event is triggered by the ABAP runtime environment if, during the display of a screen list, a function with a self-defined function code was chosen.
Self-defined function codes are all those that include character combinations, except for the following:
The function codes PICK and PF## ("##" stands for 01 to 24) do not cause the event AT USER-COMMAND, but the events AT LINE-SELECTION and AT PF##.
All function codes that start with the character "%" are interpreted as system functions and do not cause the event AT USER-COMMAND. The system functions for lists are listed in the following table 1.
The function codes in the following table 2, likewise, do not cause the event AT USER-COMMAND, but are handled by the list processor.
<b>AT PF##</b>
This statemet defines an event block whose event is triggered by the ABAP runtime environment during list display - provided the screen cursor is on a list line and a function is selected using the function code PF##. Here ## stands for a number between 01 and 24. In the= standard list status, these function codes are assigned to the function keys of the input device.
Instead of AT PF## , AT USER-COMMAND should always be used and special function codes should be assigned to the required function keys.
<b>TOP-OF-PAGE</b>
Effect
This statement defines an event block whose event is triggered by the ABAP runtime environment during the creation of a list. This occurs when a new page is started - that is, immediately before the first line in a new page is to be output. All list outputs that take place in the event block are placed below the standard page header of the list. You cannot output more lines than are available in the page within the event block. The NEW-PAGE statement is ignored within this event block.
The entire output written to the list in the event block belongs to the page header of the current list page. The top page header cannot be moved when you scroll vertically in a list displayed on the screen.
<b>TOP-OF-PAGE DURING LINE-SELECTION</b>
If you do not use an addition, an event block is triggered for event TOP-OF-PAGE during the creation of a basic list. If you use the addition DURING LINE-SELECTION, an event block is triggered for the corresponding events during the creation of details lists. You have to use system fields like sy-lsind to distinguish between the individual details lists.
<b>END-OF-PAGE</b>
This statement defines an event block that is raised by the ABAP-runtime during creation of a basic list, if there is a line reservation in the addition LINE-COUNT of the initiating statement for a page footer, which was reached while writing to this page. A list output that takes place in the event block, is placed in this area. Output statements that exceed the reserved area will be ignored.
<b>Reward if usefull</b>

Events in ABAP runtime.

Can Any one explain me the events in ABAP runtime with proper example please.

Hi Srnivas,
Here are the events in order
Classical Report Events:
Initialization
At selection-screen
at selection-screen output
start-of-selection
end-of-selection
top-of-page
end-of-page
Interactive Report Events:
Above events and also,
at line-selection,
at user-command,
at pfn
The following events occur at runtime of a typical report program which uses logical databases:
Event keyword Event
INITIALIZATION Point before the selection screen
is displayed
When you start a program in which a selection screen is defined (either in the program itself or in the linked logical database program), the system normally processes this selection screen first. If you want to execute a processing block before the selection screen is processed, you can assign it to the event keyword INITIALIZATION.
AT SELECTION-SCREEN Point after processing user
input on the selection screen while the selection screen is still active
The event keyword AT SELECTION-SCREEN provides you with several possibilities to carry out processing blocks while the system is processing the selection screen.
START-OF-SELECTION Point after processing the selection screen
The event START-OF-SELECTION gives you the possibility of creating a processing block after processing the selection screen and before accessing database tables using a logical database. You can use this processing block, for example, to set the values of internal fields or to write informational statements onto the output screen.
At the START-OF-SELECTION event, also all statements are processed that are not attached to an event keyword except those that are written behind a FORM-ENDFORM block
GET <table> Point at which the logical database
offers a line of the database table <table>.
The most important event for report programs with an attached logical database is the moment at which the logical database program has read a line from a database table (see Accessing Data Using Logical Databases ). To start a processing block at this event, use the GET statement as follows:
Syntax
GET <table> FIELDS <list>.
After this statement, you can work with the current line of the database table <table>. The data is provided in the table work area <table>.
GET <table> LATE Point after processing all tables which
are hierarchically subordinate to the database table <table> in the structure of the logical database.
To start a processing block at the moment after the system has processed all database tables of a logical database that are hierarchically inferior to a specific database table, use the event keyword GET as follows:
Syntax
GET <table> LATE FIELDS <list>.
In analogy to report programs that use only SELECT statements (see table in Comparison of Access Methods ), the processing block of a GET <table> LATE statement would appear directly before the ENDSELECT statement in the SELECT loop for the database table <table>.
END-OF-SELECTION Point after processing all lines offered
by the logical database.
To define a processing block after the system has read and processed all database tables of a logical database, use the keyword END-OF-SELECTION.
The following events occur during the processing of the output list of a report program:
Event keyword Event
TOP-OF-PAGE Point during list processing when
a new page is started
END-OF-PAGE Point during list processing when a page
is ended
The following events occur during the display of the output list of a report program:
Event keyword Event
AT LINE-SELECTION Point at which the user selects a line
AT USER-COMMAND Point at which the user presses a function key or enters a command in the command field.
AT PF<nn> Point at which the user presses the
function key with the function code PF<n>
With the selection screen, ABAP/4 offers an interactive element also for report programs. You can define a selection screen without having to bother about all the details required in dialog programming.
The selection screen is always processed directly after a report program is started. The user can enter field values and selection criteria on this screen.
Reward points if useful.
Cheers,
Swamy Kunche

Pushbutton on the application bar on an abap report

Hello All,
I need to have a pushbutton (labelled Download) on the application bar on the abap report screen .
This button should enable me to download the report contents in a file format (like excel).
Please can you guys help me acheive this.How should the button with this functionality be placed in application bar?
Thanks in advance for the kind help
Swati

Hi Swathi,
In such case, as said above, create a new GUi status and then assign to the report using the below statement:
AT PFnn.
Effect
This obsolete statement defines an event block whose event is triggered by the ABAP runtime environment during list display - provided the screen cursor is on a list line and a function is selected using the function code PFnn. Here nn stands for a number between 01 and 24. In the standard list status, these function codes are assigned to the function keys of the input device.
Then what processing needs to be done when the user presses the button, will be written in the below control statement..
AT USER-COMMAND
Effect
This statement defines an event block whose event is triggered by the ABAP runtime environment if, during the display of a screen list, a function with a self-defined function code was chosen.
Note
Self-defined function codes are all those that include character combinations, except for the following:
The function codes "PICK" and "PFnn" ("nn"stands for 01 to 24) do not cause the event AT USER-COMMAND, but the events AT LINE-SELECTION and AT PFnn.
All function codes that start with the character "%" are interpreted as system functions and do not cause the event AT USER-COMMAND. The system functions for lists are listed in the following table 1.
The function codes in the following table 2, likewise, do not cause the event AT USER-COMMAND, but are handled by the list processor.
Table 1
Function code Function
%CTX Call a context menu
%EX Exit
%PC Save to file
%PRI Print
%SC Search for ...
%SC+ Find next
%SL Search in office
%ST Save to report tree
Table 2
Function code Function
BACK Back
P- Scroll to previous page
P-- Scroll to first page
P+ Scroll to next page
P++ Scroll to last page
PFILE name Store list lines in a text file named "abap.lst" in standard character representation in the standard directory of the application server. If a name is entered using name, this is converted to lowercase letters and used as the file name.
PL- Scroll to first line of the page
PL-n Scroll n lines back
PL+ Scroll to last line of the page
PL+n Scroll n lines up
PNOP No effect
PP- Scroll back one page
PP-n Scroll n pages back
PP+ Scroll one page forward
PP+n Scroll n pages forwad
PPn Scroll to beginning of page n
PRI, PRINT Print
PS-- Scroll to first column
PS++ Scroll to last column
PS- Scroll one column to the left
PS-n Scroll n columns to the left
PS+ Scroll one column to the right
PS+n Scroll n columns to the right
PSn Scroll to column n
PZn Scroll to line n
RW Cancel
Example
This program works with a self-defined GUI status MYLIST. The function that is linked there with the function code MY_SELECTION causes the event AT USER-COMMAND during list display and also creates details lists.
REPORT demo_at_user_command.
START-OF-SELECTION.
SET PF-STATUS 'MYLIST'.
WRITE 'List line'.
AT USER-COMMAND.
IF sy-lsind = 20.
    SET PF-STATUS 'MYLIST' EXCLUDING 'MY_SELECTION'.
ENDIF.
CASE sy-ucomm.
    WHEN 'MY_SELECTION'.
      WRITE: / 'You worked on list', sy-listi,
             / 'You are on list', sy-lsind.
ENDCASE.
Regards
Shiva

What are the events in interactive reports?

what are the events in interactive reports?
could plz explain

hi,
First event -
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 : before leaving the selection screen.
start-of-selection : the first event for displaying the report.
This event keyword defines an event block whose event is triggered by the ABAP runtime environment
when calling the executable program selection screen processing of a selection screen.
In an executable program, all statements that are not declarations,
and are listed before the first explicit processing block, are assigned to this event block.
If the program does not contain an explicitly defined event block START-OF-SELECTION,
these statements form the complete event block START-OF-SELECTION.
If a program contains an explicitly defined event block START-OF-SELECTION,
these statements are added to the beginning of the event block.
If the program contains no explicitly defined event blocks,
these statements form the entire event block START-OF-SELECTION.
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.
at user-command
<b>http://help.sap.com/saphelp_47x200/helpdata/en/56/1eb6c705ad11d2952f0000e8353423/content.htm</b>
Rgds
Anver

Process Flow of Events in ABAP Report

Similar Messages

Maybe you are looking for