Which is first event triggred in interactive report

pls let me know

<b>The event are triggered depended on the way the output is generated . </b>
for eg:
"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 / <field> :
before leaving the selection screen.
"start-of-selection :
the first event for displaying the report.
"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.
reward points if it is usefull ....
Girish

Similar Messages

*what are the step by step events trigger in interactive report*

Hi gurus,
pls explain event by event triggers in interactive report.
points will be rewarded.
Thanks,
Balakrishna.

Hi,
Interactive reporting allows the user to participate in retrieving and presenting data at each level during the session. Instead of presenting one extensive and detailed list with cluttered information, with interactive reporting you can create a condensed basic list from which the user can call detailed information by positioning the cursor and entering commands.
Detailed information is presented in secondary lists. A secondary list may either overlay the basic list completely or appear in an additional dialog window on the same screen. The secondary list can itself be interactive again. The basic list is not deleted when secondary list is created.
User can interact with the system by:
u2022     Double clicking or pressing F2
u2022     Selecting menu option
Like classical report, the interactive report is also event driven. Both the action mentioned above trigger events and code is written to handle these events. The events triggered by this action are as follows:
u2022     At line-selection
u2022     At user-command
u2022     Top-of-Page During Line-Selection for Secondary Page Header info
Interactive report consists of one BASIC list and 20 secondary list. Basic list is produced by START-OF-SELECTION event. When the user double clicks on the basic list or chooses the menu option, the secondary list is produced. All the events associated with classical report except end-of-page are applicable only to basic list.
AT LINE-SELECTION event
Double clicking is the way most users navigate through programs. Double clicking on basic list or any secondary list triggers the event AT LINE-SELECTION. SY-LSIND denotes the index of the list currently created. For BASIC list it is always 0. Following piece of code shows how to handle the event.
Start-of-selection.
Write: / u2018this is basic listu2019.
At line-selection.
Write : u2018this is first secondary listu2019.
In this case the output will be displayed on basic list i.e.
This is basic list.
When user double clicks on this line, the event at line-selection gets triggered and secondary list is produced, i.e. This is first secondary list.
You can go back to basic list by clicking on F3 or back icon on the standard tool bar. For this list, the value of sy-lsind will be 1.
HIDE technique
In this case thins are much simpler. Consider the case, wherein you display fields from table sflight in basic list. When user double clicks on any sflight-carrid, you are displaying the detailed information related to that particular carrid on secondary list. Hence there is a need to store the clicked carrid in some variable. So that you can access this carrid for next list. ABAP/4 has facility; a statement called HIDE, which provides the above functionality.
HIDE command temporarily stores the content of clicked field in system area.
Syntax:
HIDE <FIELDS>.
This statement stores the contents of variable <f> in relation to the current output line (system field SY-LINNO) internally in the so-called HIDE area. The variable <f> must not necessarily appear on the current line.
You have to place the HIDE statement always directly after the output statement i.e., WRITE for the variable <f>. As when you hide the variable, control is passed to next record. While writing, WRITE statement takes that record from header and writes it on to the list, but when writing onto your interactive list you will miss out 1st record.
To hide several variables, use chain HIDE statement.
As soon as the user selects a line for which you stored HIDE fields, the system fills the variables in the program with the values stored. A line can be selected.
u2022     By an interactive event.
For each interactive event, the HIDE fields of the line on which the cursor is positioned during the event are filled with the stored values.
The HIDE area is a table, in which the system stores the names and values of all HIDE fields for each list and line number. As soon as they are needed, the system reads the values from the table. (Please try to find the name of this table.)
Sy-lsind indicates the index of the list and can be used to handle all the secondary lists. When the user double clicks on the line or presses F2, sy-lsind is increased by one and this new sy-lsind can be handled. For example:
Write: / u2018this is basic listu2019.
u2022     Will create a basic list.
If sy-lsind = 1.
Write: / u2018this is first secondary listu2019.
Elseif sy-lsind = 2.
Write: / u2018This is second secondary listu2019.
Endif.
When this code is executed,
u2022     Basic list is produced.
u2022     When the user clicks on the basic list, sy-lsind becomes one.
u2022     AT LINE-SELECTION event is triggered.
u2022     Whatever is written under IF Sy-lsind = 1, gets executed.
u2022     Secondary list is produced.
u2022     Again if user clicks on this list, sy-lsind becomes two.
u2022     AT LINE-SELECTION gets triggered.
u2022     Code written under IF Sy-lsind = 2, gets executed.
A sample program for AT LINE-SELECTION.
AT USER-COMMAND
When the user selects the menu item or presses any function key, the event that is triggered is AT USER-COMMAND, and can be handled in the program by writing code for the same. The system variable SY-UCOMM stores the function code for the clicked menu item or for the function key and the same can be checked in the program. Sample code would look like
AT USER-COMMAND.
Case sy-ucomm.
When u2018DISPu2019.
        Select * from sflight.
        Write sflight-carrid, sflight-connid.
        Endselect.
When u2018EXITu2019.
     LEAVE.
If GUI status, suppose you have set menu bar for two items and the function code is u2018DISPu2019 and u2018EXITu2019 respectively. If the user clicks the menu item u2018DISPLAYu2019, then function code u2018DISPu2019 is stored in the sy-ucomm and whatever is written under the when u2018DISPu2019, gets executed. This is applicable for EXIT as well.
Sy-lsind for the screen increases when the user clicks the menu item.
Usually you have combination of all the three navigations in your user interface, i.e., you have to create menu bar, assign function code for the function keys and write code to handle all this in addition to handling double clicking.
Things to remember while using all the combinations:
u2022     Sy-lsind increases even if you select menu-item.
u2022     When the user double clicks on particular line, value of sy-ucomm is u2018PICK.
u2022     If you set sy-lsind = 2 for your 4th secondary list, when control is transferred to the 2nd secondary list, all the other lists after 2nd are lost or memory allocated to them is lost.
u2022     Sy-lisel also gives you the value of clicked line but in this case you cannot differentiate between field. To retrieve the exact field, you have to know the field length of each field.
u2022     If you use statement SY-LSIND = 1.
The system reacts to a manipulation of SY-LSIND only at the end of an event, directly before displaying the secondary list. So, if within the processing block, you use statements whose INDEX options access the list with the index SY-LSIND, make sure that you manipulate the SY-LSIND field only after processing these statements. The best way is to have it always at the `as the last statementu2019 of the processing block.
Regards,
Bhaskar

Last and First pages of the Interactive report

Hello,
I have successfully inserted this code
<div style="">
<table>
<tr>
<td style="">
<img align="absmiddle" alt="<<" title="<<" src="#IMAGE_PREFIX#srmvall.gif" onclick="gReport.navigate.paginate('pgR_min_row=1max_rows='+$v('apexir_NUM_ROWS')+'rows_fetched='+$v('apexir_NUM_ROWS'))" />
</td>
<td style="">
<img align="absmiddle" alt=">>" title=">>" src="#IMAGE_PREFIX#smvall.gif" onclick="gReport.navigate.paginate('pgR_min_row='+RetMinRow()+'max_rows='+$v('apexir_NUM_ROWS')+'rows_fetched='+$v('apexir_NUM_ROWS'))" />
</td>
</tr>
</table>
</div>
<script type="text/javascript">
function RetMinRow(){
var lN = $v('P1_MAX_ROWS')*1 / $v('apexir_NUM_ROWS')*1;
lN = Math.floor(lN*1);
lN = lN*1 * $v('apexir_NUM_ROWS')*1 + 1;
return lN;
</script>
BUT, I can not figure it out how to calculate the report max rows to set the value of P1_MAX_ROWS.
If anyone knows how to do that, please help me.
Thanks,
froggica
Edited by: froggica on Oct 6, 2010 10:55 PM
Edited by: froggica on Oct 6, 2010 10:56 PM

Hi,
Ok, good
I do have another version of javascript that catch IR pagination
function IRgetPagination(pVal){
       parameter pVal values:
       first = Return IR first row
       last = Return IR last row
       max = Return IR max rows
       if parametter pVal is something else return all values in array
var p=$.trim($('#apexir_DATA_PANEL').find('td.pagination').find('span.fielddata').text());
var a=new Array();var n=new Array();a=p.split(' ');
$.each(a,function(i,v){if(!isNaN(v)){n.push(v)}});
switch(pVal){case 'first':return n[0];case 'last':return n[1];case 'max':return n[2];default:return n}
}And with this you can do bit simple
$s('Px_MY_ITEM', IRgetPagination('max')); /* Set item Px_MY_ITEM value to IR max rows */Regards,
Jari

Can u please tell me events trigaring and first event in report

hi experts,
can u please tell me events trigaring and first event in report

actually first event triggering in a report is intialization
but before that there is one more event get triggered that is load of program.....This is the very first event which is trigger in a report program. Really I have never needed a reason to use this. But I would assume that it can be used when you want to do something before the INITIALIZATION event.
Classical Reports can have these events, in the given order :
initialization
at selection-screen
start-of-selection
end-of-selection
top-of-page
end-of-page
In addition o the above, the following events are possible in case of Interactive Reports -
at line-selection
at user-command
at PFnn.

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

Regarding Interactive reports

Hi All,
Yesterday i submitted a query regarding Interactive reports.and i recieved lots of reply .But the replies are all about ALV interactive report.I want to know just about the interactive reports where ew use AT LINE OF SELECTION, HIDE e.c.
PLZ send methe documents related that.
Thanks and Regards
RASHMI

Hi
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.
REPORT ZTEJ_INTAB1 LINE-SIZE 103 LINE-COUNT 35(5) NO STANDARD PAGE
HEADING.
*TABLES DECLARATION
TABLES : KNA1, VBAK, VBAP.
*SELECT OPTIONS
SELECT-OPTIONS: CUST_NO FOR KNA1-KUNNR.
*INITIALIZATION
INITIALIZATION.
CUST_NO-LOW = '01'.
CUST_NO-HIGH = '5000'.
CUST_NO-SIGN = 'I'.
CUST_NO-OPTION = 'BT'.
APPEND CUST_NO.
*SELECTION SCREEN VALIDATION
AT SELECTION-SCREEN ON CUST_NO.
LOOP AT SCREEN.
IF CUST_NO-LOW < 1 OR CUST_NO-HIGH > 5000.
MESSAGE E001(ZTJ1).
ENDIF.
ENDLOOP.
*BASIC LIST SELECTION
START-OF-SELECTION.
SELECT KUNNR NAME1 ORT01 LAND1 INTO
(KNA1-KUNNR, KNA1-NAME1,KNA1-ORT01,KNA1-LAND1)
FROM KNA1
WHERE KUNNR IN CUST_NO.
WRITE:/1 SY-VLINE,
KNA1-KUNNR UNDER 'CUSTOMER NO.' HOTSPOT ON,
16 SY-VLINE,
KNA1-NAME1 UNDER 'NAME',
61 SY-VLINE,
KNA1-ORT01 UNDER 'CITY',
86 SY-VLINE,
KNA1-LAND1 UNDER 'COUNTRY',
103 SY-VLINE.
HIDE: KNA1-KUNNR.
ENDSELECT.
ULINE.
*SECONDARY LIST ACCESS
AT user-command.
IF SY-UCOMM = 'IONE'.
PERFORM SALES_ORD.
ENDIF.
IF SY-UCOMM = 'ITWO'.
PERFORM ITEM_DET.
ENDIF.
*TOP OF PAGE
TOP-OF-PAGE.
FORMAT COLOR 1.
WRITE : 'CUSTOMER DETAILS'.
FORMAT COLOR 1 OFF.
ULINE.
FORMAT COLOR 3.
WRITE : 1 SY-VLINE,
3 'CUSTOMER NO.',
16 SY-VLINE,
18 'NAME',
61 SY-VLINE,
63 'CITY',
86 SY-VLINE,
88 'COUNTRY',
103 SY-VLINE.
ULINE.
FORMAT COLOR 3 OFF.
*TOP OF PAGE FOR SECONDARY LISTS
TOP-OF-PAGE DURING LINE-SELECTION.
*TOP OF PAGE FOR 1ST SECONDARY LIST
IF SY-UCOMM = 'IONE'.
ULINE.
FORMAT COLOR 1.
WRITE : 'SALES ORDER DETAILS'.
ULINE.
FORMAT COLOR 1 OFF.
FORMAT COLOR 3.
WRITE : 1 SY-VLINE,
3 'CUSTOMER NO.',
16 SY-VLINE,
18 'SALES ORDER NO.',
40 SY-VLINE,
42 'DATE',
60 SY-VLINE,
62 'CREATOR',
85 SY-VLINE,
87 'DOC DATE',
103 SY-VLINE.
ULINE.
ENDIF.
FORMAT COLOR 3 OFF.
*TOP OF PAGE FOR 2ND SECONDARY LIST
IF SY-UCOMM = 'ITWO'.
ULINE.
FORMAT COLOR 1.
WRITE : 'ITEM DETAILS'.
ULINE.
FORMAT COLOR 1 OFF.
FORMAT COLOR 3.
WRITE : 1 SY-VLINE,
3 'SALES ORDER NO.',
40 SY-VLINE,
42 'SALES ITEM NO.',
60 SY-VLINE,
62 'ORDER QUANTITY',
103 SY-VLINE.
ULINE.
ENDIF.
FORMAT COLOR 3 OFF.
*END OF PAGE
END-OF-PAGE.
ULINE.
WRITE :'USER :',SY-UNAME,/,'DATE :', SY-DATUM, 85 'END OF PAGE:',
SY-PAGNO.
SKIP.
*& Form SALES_ORD
*& FIRST SECONDARY LIST FORM
FORM SALES_ORD .
SELECT KUNNR VBELN ERDAT ERNAM AUDAT INTO
(VBAK-KUNNR, VBAK-VBELN, VBAK-ERDAT, VBAK-ERNAM, VBAK-AUDAT)
FROM VBAK
WHERE KUNNR = KNA1-KUNNR.
WRITE:/1 SY-VLINE,
VBAK-KUNNR UNDER 'CUSTOMER NO.' HOTSPOT ON,
16 SY-VLINE,
VBAK-VBELN UNDER 'SALES ORDER NO.' HOTSPOT ON,
40 SY-VLINE,
VBAK-ERDAT UNDER 'DATE',
60 SY-VLINE,
VBAK-ERNAM UNDER 'CREATOR',
85 SY-VLINE,
VBAK-AUDAT UNDER 'DOC DATE',
103 SY-VLINE.
HIDE : VBAK-VBELN.
ENDSELECT.
ULINE.
ENDFORM. " SALES_ORD
*& Form ITEM_DET
*& SECOND SECONDARY LIST FORM
FORM ITEM_DET .
SELECT VBELN POSNR KWMENG INTO
(VBAP-VBELN, VBAP-POSNR, VBAP-KWMENG)
FROM VBAP
WHERE VBELN = VBAK-VBELN.
WRITE : /1 SY-VLINE,
VBAP-VBELN UNDER 'SALES ORDER NO.',
40 SY-VLINE,
VBAP-POSNR UNDER 'SALES ITEM NO.',
60 SY-VLINE,
VBAP-KWMENG UNDER 'ORDER QUANTITY',
103 SY-VLINE.
ENDSELECT.
ULINE.
ENDFORM. " ITEM_DET
REPORT demo_list_at_pf.
START-OF-SELECTION.
WRITE 'Basic List, Press PF5, PF6, PF7, or PF8'.
AT pf5.
PERFORM out.
AT pf6.
PERFORM out.
AT pf7.
PERFORM out.
AT pf8.
PERFORM out.
FORM out.
WRITE: 'Secondary List by PF-Key Selection',
/ 'SY-LSIND =', sy-lsind,
/ 'SY-UCOMM =', sy-ucomm.
ENDFORM.
After executing the program, the system displays the basic list. The user can press the function keys F5 , F6 , F7 , and F8 to create secondary lists. If, for example, the 14th key the user presses is F6 , the output on the displayed secondary list looks as follows:
Secondary List by PF-Key Selection
SY-LSIND = 14
SY-UCOMM = PF06
Example for AT USER-COMMAND.
REPORT demo_list_at_user_command NO STANDARD PAGE HEADING.
START-OF-SELECTION.
WRITE: 'Basic List',
/ 'SY-LSIND:', sy-lsind.
TOP-OF-PAGE.
WRITE 'Top-of-Page'.
ULINE.
TOP-OF-PAGE DURING LINE-SELECTION.
CASE sy-pfkey.
WHEN 'TEST'.
WRITE 'Self-defined GUI for Function Codes'.
ULINE.
ENDCASE.
AT LINE-SELECTION.
SET PF-STATUS 'TEST' EXCLUDING 'PICK'.
PERFORM out.
sy-lsind = sy-lsind - 1.
AT USER-COMMAND.
CASE sy-ucomm.
WHEN 'FC1'.
PERFORM out.
WRITE / 'Button FUN 1 was pressed'.
WHEN 'FC2'.
PERFORM out.
WRITE / 'Button FUN 2 was pressed'.
WHEN 'FC3'.
PERFORM out.
WRITE / 'Button FUN 3 was pressed'.
WHEN 'FC4'.
PERFORM out.
WRITE / 'Button FUN 4 was pressed'.
WHEN 'FC5'.
PERFORM out.
WRITE / 'Button FUN 5 was pressed'.
ENDCASE.
sy-lsind = sy-lsind - 1.
FORM out.
WRITE: 'Secondary List',
/ 'SY-LSIND:', sy-lsind,
/ 'SY-PFKEY:', sy-pfkey.
ENDFORM.
When you run the program, the system displays the following basic list with a the page header defined in the program:
You can trigger the AT LINE-SELECTION event by double-clicking a line. The system sets the status TEST and deactivates the function code PICK. The status TEST contains function codes FC1 to FC5. These are assigned to pushbuttons in the application toolbar. The page header of the detail list depends on the status.
Here, double-clicking a line no longer triggers an event. However, there is now an application toolbar containing five user-defined pushbuttons. You can use these to trigger the AT USER-COMMAND event. The CASE statement contains a different reaction for each pushbutton.
For each interactive event, the system decreases the SY-LSIND system field by one, thus canceling out the automatic increase. All detail lists now have the same level as the basic list and thus overwrite it. While the detail list is being created, SY-LSIND still has the value 1.
Regards
Anji

Difference between class report and interactive report

please give me the differences between classical report and interactive report

Hi,read the following :
In ABAP, there are a total of 7 types of reports. They are:
Classical Reports
Interactive Reports
Logical Database Reports
ABAP query
ALV Reports (ALV stands for ABAP List Viewer)
Report Writer/Report Painter
Views (There are different types of views also)
Classical Reports
These are the most simple reports. 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
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).
Logical Database Reports
Logical database is another tool for ABAP reports. Using LDB we can provide extra features for ABAP reports.
While using LDB there is no need for us to declare Parameters.
Selection-screen as they will be generated automatically.
We have to use the statement NODES in ABAP report.
ABAP Query Reports
ABAP query is another tool for ABAP. It provides efficency for ABAP reports. These reports are very accurate.
Transaction Code : SQ01
Report Writer / Report painter
Super users and end users can use Report Painter/Report Writer tools to write their own reports.
Giving them the ability to report on additional fields at their discretion shifts the report maintenance burden to them, saving SAP support groups time and effort normally spent creating and maintaining the reports.
ALV reports
Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length.
In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output.
The report output can contain up to 90 columns in the display with the wide array of display options.
There is no difference between drill down and interactive report, they are the same.
With drilldown reporting, SAP provides you with an interactive information system to let you evaluate the data collected in your application. This information system is capable of analyzing all the data according to any of the characteristics that describe the data. You can also use any key figures you wish to categorize your data. You can display a number of objects for a given key figure, or a number of key figures for a given object. In addition, the system lets you carry out any number of variance analyses (such as plan/actual comparisons, fiscal year comparisons, comparisons of different objects, and so on).
*More on Classical Vs Interactive*
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.
Reward if found helpful

Setting default page in Interactive Report Dashboard (Version 9.3.1)

Does any one know how I can set the default page (to be the first page) in Hyperion Interactive Report Dashboard version 9.3.1?
I have a report with dashboard that returns 56 pages (and the user scrolls down to page 8 of page 56) and selects a filter (which only has one page of data). However, since the user had scrolled down to page 8, the default page remains at 8 and when the user scrolls up, he/she sees blank pages (thereby causing Servlet error which Hyperion has identified as being reproducible and a bug).
They have recommened that I use the onClick event trigger for the Set Filter command button to always default the page to 1 (when the set Filter button is clicked). This will put the user on page one always and prevent the Servlet error (and them seeing unnecessary blank pages).
Any help will be greatly appreciated!
Thanks in advance
Nancy

Does any one know how I can set the default page (to be the first page) in Hyperion Interactive Report Dashboard version 9.3.1?
I have a report with dashboard that returns 56 pages (and the user scrolls down to page 8 of page 56) and selects a filter (which only has one page of data). However, since the user had scrolled down to page 8, the default page remains at 8 and when the user scrolls up, he/she sees blank pages (thereby causing Servlet error which Hyperion has identified as being reproducible and a bug).
They have recommened that I use the onClick event trigger for the Set Filter command button to always default the page to 1 (when the set Filter button is clicked). This will put the user on page one always and prevent the Servlet error (and them seeing unnecessary blank pages).
Any help will be greatly appreciated!
Thanks in advance
Nancy

First event

what is the first event that trigger in an abap program and what is the order of other events which usually trigger in an report

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

Interactive Report uncheck Filter when adding new filter

Is there any possibliity to uncheck all Filters which are already defined in a interactive report when a new filter will be created?
My first approach started by adding a dynamic action which is related to the search field:
event = key_down
jQuery Selector = #apexir_SEARCH
event Scope = live
The Action contains:
$('input:checkbox').attr('checked', false);
There are 2 problems at the moment:
1. When the user hits "go" or "enter" the checkbox are checked again when the result is shown
2. If a filter is defined where the search field is not used, it doesn't work

Hi Oliver,
too much hassle I think. You can try to hijack any POST message, analyze it, and if it's about p_widget_action=FILTER you'd stop the action and interfere with an AJAX call to APEX_UTIL.IR_FILTER or IR_RESET. After the AJAX request has returnd (synchronously), you can fire the original POST again which sets the new filter.
Hmm. Sounds to me like you'd better ask the client if he is willing to pay for that sort of convenience.
Greetings from Northern Germany,
Andreas

JavaScript error on Interactive Report

When clicking on the Magnifying glass of my interactive report search bar, I receive a JavaScript error.
Line: 2 Char: 15193 Error: Syntax Error
The page that I am navigating to has 2 regions. The first is an interactive report and the second is an html region that has an Iframe reference to another interactive report. Based upon the selection of a radio group, the corresponding region(interactive report) displays. All other interactive reports work fine when their pages don't have a region with a Iframe reference.
If I navigate to another page after the error occurs and then come back to the page, everything then works fine. The error only happens on the first use. I have installed the latest patch set for Apex 3.2 I currently am running 3.2.1.00.11. I read a bug on Metalink that referenced this javascript error, but applying the patch set does not seem to fix the issue. The bug was 8568894.
Any help would be appreciated.

This might be useful for others also...
After hours and hours of debugging headers and responses and comparing pages to others which work, I realised that this interactive report's display condition is based on REQUEST = SUBMIT.
As such, the actions menu will NOT set the Request parameter when clicking in the actions menu and the Apex engine refuses to send anything back to the browser - not even an error message.
I'll raise a bug for this via Oracle Support.
Cheers, Pete

What is interactive report , difference bet interactive and classic report

what is interactive report , difference bet interactive and classic report

Hi
Check this thread to get more idea about ALVs.
Interactive ALV
DIRLL DOWN AND INTERACTIVE REPORT
http://www.sap-img.com/abap/difference-between-drilldown-report-and-interactive-report.htm
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:
AT LINE-SELECTION
AT USER-COMMAND
AT PF<key>
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.
http://abapprogramming.blogspot.com/search/label/INTERACTIVE%20REPORT%20BASICS

Interactive reports list

 Reports: I want to jump from 2nd detail list to 10th list. Is it possible? How?
 Suppose Iam in 10th list , I want to move to 3nd list directly? How?

Hi
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:
AT LINE-SELECTION
AT USER-COMMAND
AT PF<key>
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.
MAX we can go for 20 SECONDARY LIST AND ONE BASIC LIST TOTAL 21
sy-lsind EQ 5.
sy-lsind = 9.
endif.
Ex:
REPORT demo_list_interactive_2 .
START-OF-SELECTION.
WRITE: 'Basic List, SY-LSIND =', sy-lsind.
AT LINE-SELECTION.
IF sy-lsind = .5
sy-lsind = 9.
ENDIF.
WRITE: 'Secondary List, SY-LSIND =', sy-lsind.
I just gave an example at this link for filling and retrieving data to a text editor.
Save the text from Text Editor to customised table
reward if usefull.

Interactive Report with 2 tables

I want to create an Interactive Report (and Form) based on 2 tables which are joined together with FK_MODULE from FORM table 2 PK_ID from MODULE table.
Do I just edit the SQL that got created from the wizard (which only asked for 1 table) to display the appropriate description (instead of primary key) or is there another way to creat a list of values like in a form?
FORM
PK_ID
FORM_CODE
FK_MODULE
MODULE
PK_ID
MODULE
DESCRIPTION

Hi Bob,
Interactive Report is not so much different than how you would do it in a normal report.
You can change the sql, if you don't know how to do a join in sql, use the Query Builder.
You can also create a view first and base the Interactive report on that.
Regards,
Dimitri
-- http://dgielis.blogspot.com/
-- http://apex-evangelists.com/
-- http://apexblogs.info/

Interactive Report does not maintain / remain on current page

Fellow APEX gurus,
In my APEX application (APEX 4.0), I have an Interactive Report that displays rows of data and each row has an EDIT link which on clicking pops up a Form (Dynamic HTML Page) on top of the Interactive Report Report.
The problem is -- when on the Interactive Report page, when I navigate to next page of records (Page 2 or above), and EDIT a row on that page, the resulting Form pops up correctly on top of the Interactive Report, however, in the background, the Interactive Report navigates back to Page 1.
There is only one default branch on the Interactive Report page and I have "Save State before branching" checked.
How do I maintain the current Page and not allow APEX to navigate back to the First Page of the Interactive Report?
Thanks,
Ed

Mini,
I already had the Reset Pagination Unchecked. I did uncheck the "save state before branching" but the behavior was the same.
Once again, I have only one "Unconditional" Branch on this page with the following settings:
reset pagination for this page - unchecked
include process success message - checked
save state before branching - checked
Anything else to look for?
Thanks,
Ed.

Which is first event triggred in interactive report

Similar Messages

Maybe you are looking for