Detecting Events in a report

Hi,
I'm trying to detect when a user double clicks on a selection screen, how to detect that this has been done and call some code.
I have the code for radio button etc.. which you set using the PF-status screen, but how do I detect when a user double click a line, and details for that line?
AT SELECTION-SCREEN.
   PERFORM check_fields.
AT USER-COMMAND.
IF sy-lsind = 1.
     CLEAR w_list_screen.
ENDIF.
CASE sy-ucomm.
*--- list spool screen
    WHEN 'UPDA'.
       PERFORM refresh_spool_list.
    WHEN 'DPRI'.
       PERFORM print_spool.
    WHEN 'DELE'.
thanks

Hi Sims,
I understood that you want to raise an event when the user double click on a particular line in the report output. For this,
If you are using standard PF status (ie. you have not specified a PF status) then use the event AT LINE SELECTION. For getting the field you have double clicked use the command HIDE. Please have a look at the help of these two.
If you are using your own PF status, then give a status code for 'F2' and write the code in the AT USER COMMAND event as you did for others.
Hope this will help you.
Thanks
Vinod

Similar Messages

PVC2300 - Alternative to Motion Detection Event / FTP Upload

Hi Cisco Community,
My apologies if I am not posting this in the correct section / allowed to post here.
I've got a PVC2300 mounted inside a pelco enclosure that is positioned 6 meters high. Sometimes the motion detection event doesn't work to well (this is due to the fact that its in an enclosure and pointed out towards the ocean at a beach location).
Also the motion detection event is pretty much useless at night without surrounding illumination.
In Australia we also have severe lack of broadband speed and also download allowance, therefore it is not practical to broadcast streaming video (we would get charged excessive fees for exceeding download quotas and only one person could view the camera at any one time).
I've written a custom windows service that reads the PVC2300's MJPEG stream over http at a specified interval and saves a single .JPG file in which the windows service uploads the .JPG file to a specified website. This means that you will always get an updated image from the camera every 5 minutes, rather than based on motion detection. It would have been nice if cisco / linksys implemented this within the camera's firmware (maybe in a future version?).
Anyway, communities share things with each other, so i've made the software freely available to anyone who wishes to use it. I would appreciate any feedback from Cisco / Linksys.
http://www.airbiscuit.com.au/pvc2300-service.html - PVC2300 Windows Service
http://www.airbiscuit.com.au/camera.aspx - The actual PVC2300 in operation
Regards,
David Zielinski

You came to the right place and thats a very cool post IMO.
First, thanks for using Cisco Small Business products and you can look forward enhancements and options in our line, of course. I think I noticed your other post mentioning you are in Australia? We have a few really top BU folks (TMEs and Biz Dev) down under and they are very active in the BU solutions area for Small Business. Do you know Leah Davis and Dave Harper (they are Participants on this community as well)?
In any event, I think compressed streaming is a very valid design idea and we are actually looking at similar partners in the US experimenting with the same. In one Partners case he has a lightweight application (java) that runs on your mobile and allows all the mobile streams to come compressed from a server farm.
Typical use case is a Day Care where 15 parents want to watch the same camera, and the compression benefit becomes crucial in scale. But your case is a financial one (therefore good too) where you would have to pay for streaming video.
While we dont offer this today (the external managed service that is), I am sure you have played with the camera GUI and realize you can try some of the following to reduce bandwidth
1- lower quality of video (resolution, FPS, illuminate Audio, etc)
2- reduce motion detection size (seconds)
3- Purchase a local NSS2100 or NSS3x00 to store High Quality video on the LAN and only alert for motion via email (not realy friendly for remote monitoring I admit).
For sensitivity in an enclosure, have you played with Sensitivity settings thresholds in the Camera GUI under motion detection?
For night illumination without an external IR Illuminator, have you tried the 'night schedule', which activates (or deactivates) the IR Cut Filter?
For the periodic updates, I'll let Davin Oishi comment as he is about ready to announce the PVC300 and I know it offers a browser based periodic refresh and I am not sure how far he has extended that to an API for external access.....
Thanks for your post
Steve DiStefano
Systems Engineer in the US field channel
RTP, N.C.

Process Flow of Events in ABAP Report

Hi every one,
Could some body explain about each and every event how and when it trigerrs.
I am always confusing with these events.
Plz tell me abt all the Driver events, User Events, Program events how they are Trigerred .
Explain me with complete details.
And more over what is the first event trigerred if i have all the events in my report program.
If you have Good Links plz do send me .
Thanks & Regards,
Sudheer.

Hi,
Chk this info.
CLASSICAL REPORT EVENTS :
INITIALIZATION : TO INITIALISE THE SELECTION SCREEN ELEMENTS
START- OF-SELECTION: NORMALLY WE WRITE THE REPORT LOGIC HERE
AT SELECTION-SCREEN : SELECTION SCREEN VALIDATIONS
WHETHER U ENTERED IS CORRECT OR NOT AT SELECTION SCREEN LEVEL
AT SELECTION-SCREEN ON FIELD : TO PROVIDE INPUT HELP[S FOR THE FILDS AT SELECTION SCREEN
FOR EX : MATNR IF U PREESS F4 AT SELECTION SCREEN.
TOP-OF-PAGE : TO PROVIDE LIST HEADING ( OUTPUT HEADINGS)
END-OF-PAGE : TO PROVIDE FOOTER I.E., PAGE NUMBERS
END-OF-SELECTION : TO FREE THE MEMORY , NO NEED OF USING THIS SPECIALLY
INTERACTIVE EVENTS :
AT LINE-SELECTION : IT IS USED TO HENDLE SECONDARY LISTS
AT USER-COMMAND : TO PROVIDE OUR OWN GUI ( PUSH BUTTONS ETC) AT OUTPUT
AT PF-STATUS : TO PROVIDE FUNCTIONS FOR OUR OWN PROVIDED GUI BUTTONS AT OUTPUT
LOAD-OF-PROGRAM.
Triggers the associated event in an internal session after loading a program of type 1, M, F, or S. Also runs the associated processing block once and once only for each program and internal session.
INITIALIZATION.
the associated event is executed before the selection screen is displayed.
START-OF-SELECTION.
In an executable program, the corresponding event is processed after the selection screen has been displayed and before data is read using a logical database
GET
Triggers the associated events when data is read in an executable (type 1) program using a logical database.
END-OF-SELECTION.
The END-OF-SELECTION event is triggered in type 1 programs once the logical database has finished reading all data and before the list processor is started.
END of page and top page
while displaying the list as the name suggest fired at the top and end of page
SM62 is the Transaction code for creating Events.
Here you can see
System event names
User event names
System event names are standard events .
User event names are customized event name, here click "Maintain" and double click it. it takes to another screen . From here you can create your customized Events.
Regards
Sandeep REddy

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
http://help.sap.com/saphelp_47x200/helpdata/en/56/1eb6c705ad11d2952f0000e8353423/content.htm
Rgds
Anver

Reg. Events in ALV Reports

Hi all,
Can anybody send me the sample program, related to Events on ALV Reports.
Use ful answers rewards more.

Hi Raj,
Here I'm sending 2 programs with user command on grid and list.
along with interaction and commentory boxes and all.
separate box ****************
TABLES: KNA1,VBAK,VBAP.
TYPE-POOLS: SLIS.
SELECT-OPTIONS: CUST FOR KNA1-KUNNR.
DATA: BEGIN OF ITAB OCCURS 0,
 KUNNR LIKE KNA1-KUNNR,
 NAME LIKE KNA1-NAME1,
 LAND1 LIKE KNA1-LAND1,
 END OF ITAB.
DATA: BEGIN OF JTAB OCCURS 0,
 VBELN LIKE VBAK-VBELN,
 NETWR LIKE VBAK-NETWR,
 END OF JTAB.
DATA: BEGIN OF KTAB OCCURS 0,
 POSNR LIKE VBAP-POSNR,
 MATNR LIKE VBAP-MATNR,
 END OF KTAB.
DATA: REPID LIKE SY-REPID,
*INTERNAL TABLE AND STRUCTURE.
*SLIS_T_FIELDCAT_ALV IS AN INTERNAL TABLE.
*SLIS_FIELDCAT_ALV IS AN STRUCTURE.
 F_KNA11 TYPE SLIS_T_FIELDCAT_ALV,
 F_KNA1 TYPE SLIS_FIELDCAT_ALV,
 F_VBAK1 TYPE SLIS_T_FIELDCAT_ALV,
 F_VBAK TYPE SLIS_FIELDCAT_ALV,
 F_VBAP1 TYPE SLIS_T_FIELDCAT_ALV,
 F_VBAP TYPE SLIS_FIELDCAT_ALV,
 I_EVENTS TYPE SLIS_T_EVENT,
 S_EVENTS TYPE SLIS_ALV_EVENT.
PERFORM GET-VAL.
REPID = SY-REPID.
SELECT KUNNR NAME1 LAND1 FROM KNA1 INTO TABLE ITAB WHERE KUNNR IN
CUST
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
 I_CALLBACK_PROGRAM = REPID
 IT_FIELDCAT = F_KNA11
 IT_EVENTS = I_EVENTS
 TABLES
 T_OUTTAB = ITAB.
GET VAL
FORM GET-VAL.
 F_KNA1-FIELDNAME = 'KUNNR'.
 F_KNA1-REF_TABNAME = 'KNA1'.
 F_KNA1-REF_FIELDNAME = 'KUNNR'.
 APPEND F_KNA1 TO F_KNA11.
 F_KNA1-FIELDNAME = 'NAME'.
 F_KNA1-REF_TABNAME = 'KNA1'.
 F_KNA1-REF_FIELDNAME = 'NAME1'.
 APPEND F_KNA1 TO F_KNA11.
 F_KNA1-FIELDNAME = 'LAND1'.
 F_KNA1-REF_TABNAME = 'KNA1'.
 F_KNA1-REF_FIELDNAME = 'LAND1'.
 APPEND F_KNA1 TO F_KNA11.
 F_VBAK-FIELDNAME = 'VBELN'.
 F_VBAK-REF_TABNAME = 'VBAK'.
 F_VBAK-REF_FIELDNAME = 'VBELN'.
 APPEND F_VBAK TO F_VBAK1.
 F_VBAK-FIELDNAME = 'NETWR'.
 F_VBAK-REF_TABNAME = 'VBAK'.
 F_VBAK-REF_FIELDNAME = 'NETWR'.
 F_VBAK-DO_SUM = 'X'.
 APPEND F_VBAK TO F_VBAK1.
 F_VBAP-FIELDNAME = 'POSNR'.
 F_VBAP-REF_TABNAME = 'VBAP'.
 F_VBAP-REF_FIELDNAME = 'POSNR'.
 APPEND F_VBAP TO F_VBAP1.
 F_VBAP-FIELDNAME = 'MATNR'.
 F_VBAP-REF_TABNAME = 'VBAP'.
 F_VBAP-REF_FIELDNAME = 'MATNR'.
 APPEND F_VBAP TO F_VBAP1.
 S_EVENTS-NAME = 'USER_COMMAND'.
 S_EVENTS-FORM = 'VAL'.
 APPEND S_EVENTS TO I_EVENTS.
ENDFORM.
FORM VAL USING USER_COMMAND LIKE SY-UCOMM SEL TYPE SLIS_SELFIELD.
DATA: CUS(10) TYPE N,
 SALNO(10) TYPE N,
 MAT(10) TYPE C.
display lists
IF SEL-FIELDNAME = 'KUNNR'.
 CUS = SEL-VALUE.
 SELECT VBELN NETWR FROM VBAK INTO TABLE JTAB WHERE KUNNR = CUS.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
 I_CALLBACK_PROGRAM = REPID
 IT_FIELDCAT = F_VBAK1
 IT_EVENTS = I_EVENTS
 TABLES
 T_OUTTAB = JTAB.
ENDIF.
IF SEL-FIELDNAME = 'VBELN'.
 SALNO = SEL-VALUE.
 SELECT POSNR MATNR FROM VBAP INTO TABLE KTAB WHERE VBELN = SALNO.
CALL FUNCTION 'REUSE_ALV_POPUP_TO_SELECT'
EXPORTING
 I_TITLE = ' ITEM DETAILS'
 I_TABNAME = VBAP
 IT_FIELDCAT = F_VBAP1
 I_CALLBACK_PROGRAM = REPID
IMPORTING
 ES_SELFIELD = SEL
TABLES
 T_OUTTAB = KTAB.
ENDIF.
IF SEL-FIELDNAME = 'MATNR'.
MAT = SEL-VALUE.
SET PARAMETER ID 'MAT' FIELD MAT.
CALL TRANSACTION 'MM03' AND SKIP FIRST SCREEN.
ENDIF.
ENDFORM.
Grid Display ***************
TYPE-POOLS: SLIS.
TABLES: KNA1.
*DATA: ITAB TYPE STANDARD TABLE OF ZJKNA1 WITH HEADER LINE.
DATA: BEGIN OF ITAB OCCURS 0,
 KUNNR TYPE KUNNR,
 NAME1 TYPE KNA1-NAME1,
 END OF ITAB.
DATA: JTAB LIKE ITAB OCCURS 0 WITH HEADER LINE.
DATA: IT_TOP TYPE SLIS_T_LISTHEADER.
DATA: W_TOP TYPE SLIS_LISTHEADER.
DATA: IT_EVENT TYPE SLIS_T_EVENT.
DATA: W_EVENT TYPE SLIS_ALV_EVENT.
W_EVENT-NAME = 'TOP_OF_PAGE'.
W_EVENT-FORM = 'TOPS'.
APPEND W_EVENT TO IT_EVENT.
W_EVENT-NAME = 'USER_COMMAND'.
W_EVENT-FORM = 'UCOM'.
APPEND W_EVENT TO IT_EVENT.
DATA: S_LAYOUT TYPE SLIS_LAYOUT_ALV.
*S_LAYOUT-NO_VLINE = 'X'.
S_LAYOUT-ZEBRA = 'X'.
S_LAYOUT-NO_COLHEAD = ''.
S_LAYOUT-TOTALS_ONLY = 'TL'.
DATA: IT_LISTHEADER TYPE SLIS_T_LISTHEADER.
DATA: W_LISTHEADER TYPE SLIS_LISTHEADER.
W_LISTHEADER-TYP = 'H'.
W_LISTHEADER-KEY = 'THIS IS LIST'.
APPEND W_LISTHEADER TO IT_LISTHEADER.
DATA: IT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV.
DATA: W_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
W_FIELDCAT-COL_POS = 1.
W_FIELDCAT-FIELDNAME = 'KUNNR'.
W_FIELDCAT-TABNAME = 'ITAB'.
W_FIELDCAT-SELTEXT_M = 'CUST. NO'.
W_FIELDCAT-HOTSPOT = 'X'.
APPEND W_FIELDCAT TO IT_FIELDCAT.
CLEAR W_FIELDCAT.
W_FIELDCAT-COL_POS = 2.
W_FIELDCAT-FIELDNAME = 'NAME1'.
W_FIELDCAT-TABNAME = 'ITAB'.
W_FIELDCAT-SELTEXT_M = 'CUST. NAME'.
W_FIELDCAT-OUTPUTLEN = 30.
APPEND W_FIELDCAT TO IT_FIELDCAT.
CLEAR W_FIELDCAT.
SELECT KUNNR NAME1 FROM KNA1 INTO CORRESPONDING FIELDS OF TABLE ITAB
UP TO 50 ROWS.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_INTERFACE_CHECK = ' '
I_BYPASSING_BUFFER = ' '
I_BUFFER_ACTIVE = ' '
 I_CALLBACK_PROGRAM = SY-REPID
I_CALLBACK_PF_STATUS_SET = ' '
I_CALLBACK_USER_COMMAND = ' '
I_CALLBACK_TOP_OF_PAGE = W_LISTHEADER
I_CALLBACK_HTML_TOP_OF_PAGE = ' '
I_CALLBACK_HTML_END_OF_LIST = ' '
I_STRUCTURE_NAME =
I_BACKGROUND_ID = 'ENJOY.BMP'
I_GRID_TITLE = 'THIS IS MY FIRST ALV REPORT'
I_GRID_SETTINGS = W_LISTHEADER
 IS_LAYOUT = S_LAYOUT
 IT_FIELDCAT = IT_FIELDCAT
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_DEFAULT = 'X'
I_SAVE = ' '
IS_VARIANT =
 IT_EVENTS = IT_EVENT
IT_EVENT_EXIT =
IS_PRINT =
IS_REPREP_ID =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
IT_ALV_GRAPHICS =
IT_HYPERLINK =
IT_ADD_FIELDCAT =
IT_EXCEPT_QINFO =
I_HTML_HEIGHT_TOP =
I_HTML_HEIGHT_END =
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =
TABLES
 T_OUTTAB = ITAB
EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
**& Form TOPS
 text
--> p1 text
<-- p2 text
FORM TOPS .
REFRESH IT_TOP.
W_TOP-TYP = 'H'.
*W_TOP-KEY = 'JAGAN'.
W_TOP-INFO = 'THIS IS SAMPLE HEADER'.
APPEND W_TOP TO IT_TOP.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
 IT_LIST_COMMENTARY = IT_TOP
 I_LOGO = 'IDLOGO1'
I_END_OF_LIST_GRID =
ENDFORM. " TOPS
*& Form UCOM
 text
--> p1 text
<-- p2 text
FORM UCOM USING USER_COMMAND LIKE SY-UCOMM SEL TYPE SLIS_SELFIELD.
DATA: CUS(10) TYPE N VALUE '0000000000'.
CUS = SEL-VALUE.
REFRESH ITAB.
SELECT KUNNR NAME1 FROM KNA1 INTO TABLE ITAB WHERE KUNNR = CUS.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
 I_CALLBACK_PROGRAM = SY-REPID
 IT_FIELDCAT = IT_FIELDCAT
 IT_EVENTS = IT_EVENTS
 TABLES
 T_OUTTAB = ITAB.
ENDFORM. " UCOM

Events in Interactive reports

hi gurus,
i want detailed explanation each n every event of standard report...
Regards
baskar

HI
INITIALIZATION
This event keyword defines an event block whose event is triggered by the ABAP runtime environment during the flow of an executable program, directly after LOAD-OF-PROGRAM and before the selection screen processing of any existing standard selection screen. This gives you the one-time opportunity to initialize the input fields of the selection screen, including those defined in the logical database linked with the program.
When an executable program defines a standard selection screen, it is called again by the ABAP runtime environment after execution, which triggers the INITIALIZATION event again. In this case, initializing parameters or selection criteria of the selection screen has no effect, because they are automatically supplied with the preceding user inputs from the selection screen during the selection screen event AT SELECTION-SCREEN OUTPUT. To explicitly initialize the selection screen for each call, you must use the event AT SELECTION-SCREEN OUTPUT.
START-OF-SELECTION
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.
If the program is linked to a logical database, preparations can be made here before the logical database reads data. If the program is not linked to a logical database, this event block even displays a "main program" from which procedures or screen layouts are called.
GET node
Use GET to handle two types of events after submitting executable programs: Get events and events at the end of a hierarchy level of a logical database. If during a GET event a list is written, previously an automatic line feed is created.
The event blocks after GET are implemented internally as procedures. Declarative statements in GET event blocks create local data.
END-OF-SELECTION
This statement defines an event block, whose event is raised by the ABAP-runtime environment during the calling of an executable program , if the logical database, with which the program is linked, has completely finished its work.
In this event block, all data read by the logical data base , can be processed summarically. In an executable program without logical data base, there is no need to implement the event block END-OF-SELECTION.
LOAD-OF-PROGRAM
This event keyword defines an event block whose event is triggered by the ABAP-runtime environment when an executable program, a module pool, a function group or a sub-routine pool is loaded in the internal session.
When calling a program through SUBMIT or through a transaction code, then, at every call, a new internal session is opened and the event block is executed once at every call. You can initialize global data objects of the program here.
At the first call of an external Procedure (sub-program or function module), the framework program of the called procedure is loaded into the internal session of the caller, thus triggering the event LOAD-OF-PROGRAM. The event block is executed before the called procedure. At any further call of a procedure of the same framework program by a caller of the same internal session, the event LOAD-OF-PROGRAM is triggered no longer.
The event LOAD-Of-PROGRAM should mainly be used to initialize global data when calling external procedures or Transactions. If you call executable programs with SUBMIT, we recommend that you use the event INITIALIZATION, as the Starting values for parameter and selection criteria are set after LOAD-OF-PROGRAM (see program flow after SUBMIT).
AT SELECTION-SCREEN
AT SELECTION-SCREEN selscreen_event.
This statement defines event blocks for different events selscreen_event that are triggered by the ABAP runtime environment during selection screen processing.
Selection screen events occur immediately before sending a selection screen and after certain user actions on a displayed selection screen. They assist in selection screen processing in the ABAP program.
AT SELECTION-SCREEN is triggered at least twice during actions on selection screens that are linked into another selection screen as a subscreen - first for the linked selection screen itself, and then for the linking selection screens.
The event blocks after AT SELECTION-SCREEN are implemented internally as procedures. Declarative statments in these event blocks create local data.
AT SELECTION-SCREEN OUTPUT
This event is triggered at the screen event PBO of a selection screen. In the event block, the selection screen can be prepared through assignments to the data objects of parameters and selection criteria and through dynamic screen modifications.
The assignments to input fields in the event block AT SELECTION-SCREEN OUTPUT always affect the selection screen and overwrite the user inputs from previous displays of the same selection screen. Assignments in the event blocks LOAD-OF-PROGRAM oder INITIALIZATION, on the other hand, only have an effect at first program start.
AT SELECTION-SCREEN ON {para|selcrit}
This event is triggered at the screen event PAI of a selection screen if the content of the input field of a parameter para or a line of a selection criterion selcrit was passed to the ABAP program. In the event block, the user input can be checked. Sending a warning or an error message in the event block makes the fields para and selcrit ready for input again.
No parameter that is defined as a radio button can be specified. For this purpose, the addition ON RADIOBUTTON GROUP is provided.
If a user action takes place in the dialog box for the multiple selection of a selection criterion selcrit, the entries of the selection table are passed to the program, line by line. For each line, the event AT SELECTION-SCREEN ON selcrit is triggered.
AT SELECTION-SCREEN ON END OF selcrit
This event is triggered after the selection table selcrit has been fully passed to the program after a user action in the dialog box for the multiple selection has taken place. In the event block, the entire selection table can be checked.
AT SELECTION-SCREEN ON BLOCK block
This event is triggered at the screen event PAI of a selection screen if all the input fields of a block block of the selection screen were passed to the ABAP program. In the event block, the user inputs can be checked. Sending a warning or an error message in the event block makes all the fields of the block block ready for input again.
AT SELECTION-SCREEN ON RADIOBUTTON GROUP radi
This event is triggered at the screen event PAI of a selection screen if all the fields of a radio button group radi of the selection screen were passed to the ABAP program. In the event block, the user input can be checked. Sending a warning or error message in the event block makes all the radion buttons of the block radi ready for input again.
The individual fields of a radio button group are not passed individually and do not trigger the event AT SELECTION-SCREEN ON par.
AT SELECTION-SCREEN { ON { HELP-REQUEST | VALUE-REQUEST } FOR
{para|selcrit-low|selcrit-high} }
The two events ON HELP-REQUEST and ON VALUE-REQUEST are triggered at the screen events POH and POV of a selection screen if - for the input field of a parameter para or one of the input fields of a selection criterion selcrit - the field help F1 or the input help F4 was called. Other selection events are not triggered.
In the event blocks, a self-defined field or input field can be programmed, which overrides any helps possibly defined in the ABAP Dictionary.
These event blocks can only be implemented for fields of the selection screen that are defined in the same ABAP program and not in a possibly linked logical database.
With the events for the field and input help, no data is transported between the selection screen and the ABAP program. As with general screens, suitable function modules must be used for these. The parameters and selection criteria changed for the input help are transported to the selection screen.
AT LINE-SELECTION
This statement defines an event block whose event is triggered by the ABAP runtime environment during the display of a screen list - provided the scren cursor is on a list line and you select a function using the function code PICK. Through the definition of this event block, the standard list status is automatically enhanced in such a way that the function code F2 and, with it, the double-click mouse function is linked up to the function code PICK.
If the function key F2 is linked with a function code different than PICK, each double click will trigger its even, usually AT USER-COMMAND, and not AT LINE-SELECTION.
AT USER-COMMAND
This statement defines an event block whose event is triggered by the ABAP runtime environment if, during the display of a screen list, a function with a self-defined function code was chosen.
Self-defined function codes are all those that include character combinations, except for the following:
The function codes PICK and PF## ("##" stands for 01 to 24) do not cause the event AT USER-COMMAND, but the events AT LINE-SELECTION and AT PF##.
All function codes that start with the character "%" are interpreted as system functions and do not cause the event AT USER-COMMAND. The system functions for lists are listed in the following table 1.
The function codes in the following table 2, likewise, do not cause the event AT USER-COMMAND, but are handled by the list processor.
AT PF##
This statemet defines an event block whose event is triggered by the ABAP runtime environment during list display - provided the screen cursor is on a list line and a function is selected using the function code PF##. Here ## stands for a number between 01 and 24. In the= standard list status, these function codes are assigned to the function keys of the input device.
Instead of AT PF## , AT USER-COMMAND should always be used and special function codes should be assigned to the required function keys.
TOP-OF-PAGE
Effect
This statement defines an event block whose event is triggered by the ABAP runtime environment during the creation of a list. This occurs when a new page is started - that is, immediately before the first line in a new page is to be output. All list outputs that take place in the event block are placed below the standard page header of the list. You cannot output more lines than are available in the page within the event block. The NEW-PAGE statement is ignored within this event block.
The entire output written to the list in the event block belongs to the page header of the current list page. The top page header cannot be moved when you scroll vertically in a list displayed on the screen.
TOP-OF-PAGE DURING LINE-SELECTION
If you do not use an addition, an event block is triggered for event TOP-OF-PAGE during the creation of a basic list. If you use the addition DURING LINE-SELECTION, an event block is triggered for the corresponding events during the creation of details lists. You have to use system fields like sy-lsind to distinguish between the individual details lists.
END-OF-PAGE
This statement defines an event block that is raised by the ABAP-runtime during creation of a basic list, if there is a line reservation in the addition LINE-COUNT of the initiating statement for a page footer, which was reached while writing to this page. A list output that takes place in the event block, is placed in this area. Output statements that exceed the reserved area will be ignored.
Reward if usefull

What are the external events of a report?

Hi,
Please tell me if you have any idea about what are the external events of a Report?
Thanks in advance.
MD.

Hi,
When you run an executable program, the program flow is controlled by the external events in the ABAP runtime environment. The following diagram shows the sequence of the events:
check this link for more....
http://help.sap.com/saphelp_nw70/helpdata/en/9f/db99fa35c111d1829f0000e829fbfe/content.htm
Regards,
Shanthi.P
Reward points if useful ***

What is the need of END-OF-SELECTION event in ABAP reporting

Hi,
Can anyone explain the need of the END-OF-SELECTION event in ABAP Reports?
This event is used to terminate the previous event. Is that right? or is there any specific use of it?
and when exactly we use this event while writing a report? I mean what purpose?
Thanks,
Paddu.

Hi,
END-OF-SELECTION makes more sense when you are using logical database in your program.
See these links.
http://help.sap.com/saphelp_46c/helpdata/en/34/8e74266df74873e10000009b38f9b8/frameset.htm
http://help.sap.com/saphelp_46c/helpdata/en/9f/db9aca35c111d1829f0000e829fbfe/frameset.htm
After all the data has been selected END-OF-SELECTION event writes the data to the screen
The END-OF-SELECTION event is triggered in executable programs once the logical database has finished reading all data and before the list processor is started.
Try to go thro this link.
http://help.sap.com/saphelp_46c/helpdata/en/9f/db9a1435c111d1829f0000e829fbfe/frameset.htm
Mostly end-of-selection is used in logical data base. It is not mandatory.
Ex:
If you use a logical database in your report then this event is mandatory because when all the data selection from the database is finished this events get triggers.
For example if you are populating a internal table using a logical data base event 'GET' then you need this event because if you don't use this you get display again and again for each selection.
START-OF-SELECTION.
GET PERNR.
itab-pernr = pernr-pernr.
append itab.
*this get triggers after all selection from database.
END-OF-SELECTION.
loop at itab.
write:/ itab-pernr.
endloop.
Regards,
Padmam.

IPS event monitor and reports not working

Dear after upgrading my IPS from E3 to E4  the event monitor and reports not working, can you please advice my to solve this issues

Hi All,
Filter settings below:
The filter works partially as I don't get alerts on the IPS itself.
Firewall LOG:
4          Feb 14 2014          15:33:22                              39715                    514          IPS requested to drop UDP packet from SOURCE_VLAN_NUMBER:/39715 to DESTINATION_VLAN_NUMBER:/514
IPS LOG (when enabled):
evIdsAlert: eventId=1352793300955167909 vendor=Cisco severity=low
originator:
    hostId: SSM02
    appName: sensorApp
    appInstanceId: 1192
time: Feb 14, 2014 15:33:22 UTC offset=0 timeZone=GMT00:00
signature:   description=IP Fragment Too Small id=1206 version=S212 type=anomaly created=20030801
    subsigId: 0
    sigDetails: Too many small IP fragments in datagram
interfaceGroup: vs0
vlan: 0
participants:
    attacker:
      addr: 172.x.x.x locality=OUT
      port: 39715
    target:
      addr: x.x.x.x locality=OUT
      port: 514
      os:   idSource=unknown type=unknown relevance=relevant
alertDetails: InterfaceAttributes: context="single_vf" physical="Unknown" backplane="GigabitEthernet0/1" ;
riskRatingValue: 50 targetValueRating=medium attackRelevanceRating=relevant
threatRatingValue: 50
interface: GigabitEthernet0/1 context=single_vf physical=Unknown backplane=GigabitEthernet0/1
protocol: udp
Our next step is to make a service policy exception on the firewall itself. We are also considering reloading the IPS device or at least the analysis engine.
Thanks for all your help so far. Any more suggestions are most welcome. I'll keep you up to date.
Regards
Mariusz

Event Viewer Error Reports

How do I send all my event viewer error reports from 3/1/15 to the manufacturer of my computer? IN the event viewer window there seems to be a lock on opening submenu to perform a copy and paste or a SEND option available. I have a WINDOWS 8.1
OPERATING SYSTEM.

You should be able to right click on each indivudual log "App, Sec, Setup, System, etc" and click on Save all events as.

Monitoring GC events - CMS MBean reporting vs verboce gc log

With verbose gc logging on, we see, say, 7 major collections reported by the CMS collector, but only 3 of them are reported by its MBean. Can anyone explain what events the MBean is reporting on, and how we can best monitor all of these major collections (some of which are Full GCs)? Also, why no notification API in com.sun.management.GcInfo?
In addition, I am trying to correlate the starting times reported by the MBean to the log's, and I can do so to within <1ms or so - fine. However, the verbose gc log output is not easily grep'able to be able to easily search for something specific. For example, here are the 3 events that are reported by the log and MBean, and which cannot be easily searched for in the log:
7241.257: [Full GC 7241.257: [CMS: 493360K->263554K(983040K), 3.4341793 secs] 508315K->263554K(1042048K), [CMS Perm : 261924K->114742K(262144K)], 3.4343021 secs]
9717.604: [GC 9717.604: [ParNew (promotion failed): 59007K->59007K(59008K), 0.1716470 secs]9717.776: [CMS: 708500K->334835K(983040K), 3.9617842 secs] 755796K->334835K(1042048K), 4.1336188 secs]
11033.636: [GC 11033.636: [ParNew: 56766K->56766K(59008K), 0.0000312 secs]11033.636: [CMS11033.637: [CMS-concurrent-abortable-preclean: 0.034/0.384 secs]
(concurrent mode failure): 964112K->316828K(983040K), 3.9151547 secs] 1020879K->316828K(1042048K), 3.9153244 secs]

The GarbageCollectorMBean is reporting the stop-the-world collection. For CMS collector, it only reports the foreground collection but not the background collection which is running in the background with other mutator threads. I believe the difference you observed is due to the background collector activity.
There is a RFE filed to report the statistic for the background collector as well.
http://bugs.sun.com/view_bug.do?bug_id=4975677
Regarding the notification API, can you elaborate more what functionality you are looking for?
We're working on providing a GChisto tool for viewing and analysing a GC log which should help in your analysis. Stay tuned for the news about it.

Default event in classical reports

what is the default event in classical reports?
Regards,
pandu.

hi,
Let us take you developed a program then LOAD-OF-PROGRAM and INITIALIZATION these will be fired first when running the program, before the selection screen, if there is one, is fired.
If there is a selection screen, AT SELECTION-SCREEN OUTPUT event will be fired automatically before the screen is shown.
Also, if there is a selection screen, the START-OF-SELECTION event will only be fired when the user clicks the "Execute" button on the selection screen.
TOP-OF-PAGE will automically be fired when you use the first WRITE statement as well as anytime the line count is reached.

Detect 'Print state' within report?

Hi,
Our main business app uses an embedded CR 8.5 engine, (and will stay that way for the foreseeable future).
Is there any way to detect from within the report when it runs if this is a 'print preview' or a real 'print'?
Any way even if it is complex & requires external programming - such as Windows Emulation & custom written DLL functions added into the report. I have VB .NET skills & we have developed some DLL's in the past.
It would be extremly useful for us...
Thanks in adavnce for any advice or pointers...
regards
Paul Adams

Hi,
It's not my app - it's a third party app. I have no access to the internal code of the app.
The app uses reports we create & supply to produce all it's documents (invoices, statements, etc...).
Why do I want to detect this? The app is 'real-time' - everything happens right now, no delays or batch processing. Therefore - when you print a customers invoice at 10am - then reprint the same invoice at 3pm - there might be extra items added to the invoice - and there is no way of seeing what the invoice was like at 10am. We have issues with customers losing thier invoices & then claiming certain items were not on the invoice & the total is wrong - but we cannot reprint an accurate invoice from that time to prove it.
I would like to create PDF copies of invoices when they print & store them away. I have created a Visual Basic DLL that can be added to the Crystal Reports as an add-in when you make the report - and when referenced in a running report automatically creates an identical second copy of the report exported as a PDF.
The problem is this referenced DLL always runs whenever the report runs (refreshed). So - if you print preview - the pdf is created & stored away. If you print - the PDF is created & stored away.
If I could detect if the report was print previewed or printed - I could control when the PDF export is triggered & stored away.
I have been working on a 'print queue monitor' which detects the name of print jobs - and if it matches the name of the invoice report - copy the print job, convert to PDF & store it away - and this is working. However - if people print locally (not to the server) they can bypass the print monitor.
If there is no way to do it - then I shall have to 'detect' in Windows if a print preview screen is present or not - but it's messy & not a professional solution.
Any advice welcome...
Regards
Paul

What are events in ALV report and explain how sorting is done alv report

events in alv report and sorting in alv report
Moderator Message: Search before posting.
Edited by: kishan P on Dec 21, 2011 11:13 AM

Hi Raja,
<<content and links removed by moderator>>
PavanKumar.G
Edited by: kishan P on Dec 21, 2011 11:12 AM

How to create the event in the report for jobs scheduling.

Hi Experts,
i have a requirement like as follows:
The following triggers for Batch Jobs in the SCM system will be created.i.
Background Processing Event = u201CAPO Background Processing Eventu201D. After sending the Event, write a Log Report line u201CEvent u201CAPO Background Processing Eventu201D sentu201D.
Could you please suggest me how we create the Event or which transaction ?
Please give me a steps for creating events so that based on these events we use
CALL METHOD cl_batch_event=>raise
    EXPORTING
      i_eventid                      = p_bpeve
      i_server                       = p_server
      i_ignore_incorrect_server      = p_ignore
    EXCEPTIONS
      excpt_raise_failed             = 1
      excpt_server_accepts_no_events = 2
      excpt_raise_forbidden          = 3
      excpt_unknown_event            = 4
      excpt_no_authority             = 5
      OTHERS                         = 6.
Right now i received message "APO Background Processing Event" is doesn't exists.
Thanks in Advance.
Puneet.

Hi Puneet,
Goto transaction SM62 and in there to BckProcEvents tab. There you can create the events.
You just need to specify the name and Description of an event.
Hope this serves your purpose.
Thanks

Detecting Events in a report

Similar Messages

Maybe you are looking for