Hi Abhay,
Check out the Descriptions:
Events in Reporting :
The following events occur at runtime of a typical report program which uses logical databases:
Event keyword Event
-
<b>INITIALIZATION </b> 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.
<b>AT SELECTION-SCREEN</b> 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.
<b>START-OF-SELECTION</b> 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
<b>GET <table></b> 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
<b>GET <table> [FIELDS <list>].</b>
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>.
<b>GET <table> LATE</b> 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>.
<b>END-OF-SELECTION</b> 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
-
<b>TOP-OF-PAGE </b> 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
-
<b>AT LINE-SELECTION</b> 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>
Reward points if this helps.
Manish
Bluesky
