Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

abt events

Former Member
0 Likes
610

flow of events in classic reports how?

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
591

Hi Jeevitha,

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

-


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>

Regds,

Srini

Hi Jeevitha,

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

-


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>

Regds,

Srini

4 REPLIES 4
Read only

Former Member
0 Likes
592

Hi Jeevitha,

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

-


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>

Regds,

Srini

Read only

Former Member
0 Likes
591

Hi,

Flow is like this.

1. LOAD-OF-PROGRAM

2.INITIALIZATION

3.AT SELECTION-SCREEN OUPUT

4.AT SELECTION-SCREEN ON <FIELDNAME>

5.AT SELECTION-SCREEN

6. START-OF-SELECTION

7.END-OF-SELECTION

8.TOP-OF PAGE

9.END-OF-PAGE

10.AT-LINE SELECTION

Regs

Manas Ranjan Panda

Message was edited by:

MANAS PANDA

Read only

Former Member
0 Likes
591

Description of Events

This section describes in more detail the events that occur when you run an executable program.

The following events occur when you run a typical executable program with a logical database:

Event

Occurs

INITIALIZATION

Before the standard selection screen is displayed

AT SELECTION-SCREEN

After user input on a selection screen has been processed, but while the selection screen is still active

START-OF-SELECTION

After the standard selection screen has been processed, before data is read from the logical database

GET <table>

After the logical database has read an entry from the node <table>

GET <table> LATE

After all of the nodes of the logical database have been processed that are below <table> in the database hierarchy

END-OF-SELECTION

After all data has been read by the logical database

List processor events:

Event

Occurs

TOP-OF-PAGE

In list processing when a new page starts

END-OF-PAGE

In list processing when a page ends

AT LINE-SELECTION

When the user triggers the predefined function code PICK

AT PF<nn>

When the user triggers the predefined function code PF<nn>

AT USER-COMMAND

When the user triggers a function code defined in the program

For more information about these events, refer this link http://help.sap.com/saphelp_erp2005/helpdata/en/9f/db9a9635c111d1829f0000e829fbfe/frameset.htm

refer this thread for the answer:

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

regards,

Santosh

Read only

Former Member
0 Likes
591

good answer