INTERACTIVE REPORTS
Display the basic information on the basic list and the detailed information in the Secondary list is called Interactive report.
The first list is called basic list and the number is 0.
The remaining lists are called as secondary lists and the number start from 1 to 20. So totally there are 21 lists.
The lists no are stored in a system variable SY-LSIND.
If you select any line, then the selected line data is stored in SY-LISEL.
Interactive Reports Events:-
AT Line selection
AT User command
Top of page during line selection
AT PF <Function Key>.
AT Line Selection: - This event is triggered whenever the user double clicks on any list line. To know the selected line contents, we have two keywords or statements
1)HIDE
2)GET CURSOR
HIDE: - It is a keyword which is used to hide the data into a temporarily memory called as hide area for further processing. We use the hide statement within the loop….end loop, so that the HIDE keyword will hide the values into hide area.
Functionality of hide: - Whenever the user double clicks on any list line, the event at line selection will be triggered.
The system automatically identifies the line no where the user has double clicked and reads the corresponding record into hide variable.
Ex Program: Will be discussed separately.
GET CURSOR: - This statement is used to read or get the selected line content i.e. fieldname, field value into the variables.
Syntax: -
GET CURSOR field <v_fname>
Value <v_fvalue>.
|
The main Advantage of get cursor is,
We don’t have any hide area or temporary memory
We can generate interactive report based on field name and field value which is not possible with HIDE statement.
The other difference between hide and get cursor is, with the hide statement the system uses line no and gets the value into hide variable without knowing what is the fieldname.
Whereas the get cursor will get the exact field name and field value with which we can generate various interactive reports based on filed names.
Ex Program: Will be discussed separately.
AT User command: - This event is triggered whenever the user clicks on custom GUI buttons.
Top of page during line selection: - This event is used for providing the constant page heading for all the secondary lists.
AT PF <Function Key>: - This event is used or triggered whenever the user clicks on function keys (f1, f2, .etc)
This event is obsolete in new versions (ECC 5.0 or 6.0)
Conversion Routine: - It is a function module which is used to convert a value from internal format to external format and vice-versa.
Conversion exits are maintained at domain level.
Go to the domain and double click on conversion exit.
Conversion exit function module will be displayed
Example: -
Conversion_exit_Alpha_input :- used to convert a value from exeternal format to internal format.
Conversion_exit_Alpha_output:- used to convert a value from internal format to external format
AT user command: - This event is triggered whenever the user clicks on Custom GUI button.
Custom GUI: - It is used to create our menus in the menu bar, our own buttons in the application toolbar, enabling or disabling the standard buttons on the standard toolbar.
Syntax: - SET PF-status <CustomGUI MenuName>
‘SE41’is the tcode for creating custom GUI (also called as MENU PAINTER)
FCT CODE (Function code):- It is a shortcut code assigned to a button or menu to identify the button or menu which is clicked .
The FCT codes are automatically stored in a system variable SY-UCOMM.
Ex Program: Will be discussed separately.
If you wish to understand more on interactive reports kindly check below links:
This is dummy text. It is not meant to be read. Accordingly, it is difficult to figure out when to end it. But then, this is dummy text. It is not meant to be read. Period.
ConversionConversion EmoticonEmoticon