Classical Reports

These are the most simple reports. Programmers learn this one first. It is just an output of data using the Write statement inside a loop.

• Classical reports are normal reports. These reports are not having any sub reports. IT IS HAVING ONLY ONE SCREEN/LIST FOR OUTPUT.

Events In Classical Reports.

• INTIALIZATION: This event triggers before selection screen display.
• AT-SELECTION-SCREEN: This event triggers after proccesing user input still selection screen is in active mode.
• START OF SELECTION: Start of selection screen triggers after proceesing selection screen.
• END-OF-SELECTION : It is for Logical Database Reporting.

Interactive Reports

As the name suggests, the user can Interact with the report. We can have a drill down into the report data. For example, Column one of the report displays the material numbers, and the user feels that he needs some more specific data about the vendor for that material, he can HIDE that data under those material numbers.

And when the user clicks the material number, another report (actually sub report/secondary list) which displays the vendor details will be displayed.

We can have a basic list (number starts from 0) and 20 secondary lists (1 to 21).

Events associated with Interactive Reports are:

1. AT LINE-SELECTION
2. AT USER-COMMAND
3. AT PF<key>
4. TOP-OF-PAGE DURING LINE-SELECTION.

HIDE statement holds the data to be displayed in the secondary list.

sy-lisel : contains data of the selected line.

sy-lsind : contains the level of report (from 0 to 21)

Interactive Report Events:

• AT LINE-SELECTION : This Event triggers when we double click a line on the list, when the event is triggered a new sublist is going to be generated. Under this event what ever the statements that are been return will be displayed on newly generated sublist.
• AT PFn: For predefined function keys...
• AT USER-COMMAND : It provides user functions keys.
• TOP-OF-PAGE DURING LINE-SELECTION :top of page event for secondary list.

 

An interactive report generally works in the following fashion:

1. Basic list is displayed.
2. User double clicks on any valid line
    or
    User selects a line and presses as button on the tool bar.
3. The corresponding event is triggered
4. Then in the code, the line on which action was done, is read.
5. Depending on the values in that selected line, a secondary list is displayed.
6. Steps from 2-5 are repeated till the end.

From the above explanation, I believe, its clear that, the 20th list, will essentially depend on the "selected line" of 19th list. According to your question, you want to move to 20th list directly, without "a prior list". May I know the exact requirement so that, an appropriate solution can be suggested? 

Again, your question was, how to move to 20th list directly on pressing of execute button. Its not possible to move to 20th list.  

What are Drilldown reports?

The lines of basic list of a drilldown report when clicked, will take the user to the corresponding (standard) object's display.
 
For eg: Suppose your report's primary component is purchase requisition, (assume you are printing PR details), and the basic list displays details of many PRs.
 
Eg: when clicked on a particular line of the PR basic list, it takes you to std t-code me53 (display of purchase requisition). This is the 'Drill-down' functionality.
 
For this, in the at-line selection of your program, as per the above ex: you'll set the parameter ID of PR number BAN (that you can get from Data element) in memory (using set parameter id) and then calling the corresponding transaction (usually skipping initial screen of the std t-code).   
 
Likewise, if it's Material Number (Matnr), you'll be displaying MM03 transaction w.r.t. the line's matnr.

FREE website of Beep.com
 
The responsible person for the content of this web site is solely
the webmaster of this website, contactable via this form!