What are "events"?

This might be a very basic question but I'm having trouble grasping the concept of events in iPhoto '08. I already have my iPhoto library (the previous version) organized into what I'd call "events" -- for example, a recent trip to colorado is called 2007-07-Colorado. This keeps everything sorted by date and then by special, uh, events. Will the new version destroy this architecture I've worked hard to build and maintain?

Events are similar to albums -- but there are some big differences.
Albums aren't automatically created. You have to make the album and drag pictures into it. You could also create 'smart albums', but even then you'd have to make the smart album and then define the rules used to determine which photos belong to it. Either way, the creation of the album hinges on you manually doing something.
Events don't rely on you doing anything special to organize them -- and this is really the biggest difference between events and albums. The assumption is that when you use your digital camera for some real-life activity, you'll probably import the pictures when you're done. This means that all the pictures you imported probably belong together. iPhoto calls this an "event". It makes a new iPhoto event (you get to pick a name for it) each time you import pictures from your camera. As a result, your library automatically has at least some organization to it -- even if you're not the sort of person who is good at organizing information and would never have manually created albums and/or sorted your photos. This makes things easier to find later because the photos aren't all just piled in one really big photo library that gets harder to search as it grows.
Events don't conflict with albums. You can still drag things into albums. Photos can belong to multiple albums at the same time and still also belong to the original event. Events assume that all the pictures in the iPhoto event are somehow related to each other because they were taken at the same real-life activity. Albums don't assume anything about their contents -- other than you decided to put the picture in the album.
If iPhoto is ever wrong about categorizing photo events, you can always correct it. You can split events. Say you took some photos at some real-life activity, then never bothered to use your camera for several weeks, then took more photos at a different real-life activity, THEN decided it was time to import all your photos. iPhoto would believe all the photos were from a single event because they would have been imported at the same time. You can just pick the first picture from the 2nd real-life event and click the 'split' icon -- iPhoto will then break the event into two events at the point you specified. You can also merge separate events back together again.
Another big difference is the way in which pictures in an event can be displayed vs. pictures in an album. iPhoto allows you to go to the 'events' view (at the top left side of the iPhoto window) and it will show all the all the events you have the libary at the same time (you can scroll the list). It only shows the 'Key' photo in each event. By default this is the first photo from the event, but you can set it to any photo in the event. If you slowly pan your mouse across the event, it'll flip through a thumbnail of every photo in that event. It's a great way to scan the event without having to click the event to open it's contents. Instead of viewing your libary as thousands of thumbnails, you just see a few dozen thumbnails -- it just displays the 'key' photo for each event and hides the rest until you mouse-over the event or click it to open it and view all the photos. Albums, in contrast, can only be viewed by clicking the album name at the left side of the iPhoto window to view the individual photos in the album. This makes it a LOT easier to scan photos using the 'Library Events' view than either the 'Libary Photos' view or even the individual Album views.
Events is a way of saving you from frustration as your photo library grows into the thousands of pictures.
Regards,
Tim

Similar Messages

What are events in LBWE for a particular application area

hi ,
I would like to know what are events in LBWE for a particular application area extract structures.
What impact and how does it relate to BW/BI

Hi
There are lot of discusions on EVENT in SDN you can search and kindly look below links:
Events in LO cockpit
LBWE events
events
and so many other discussions
http://forumsa.sdn.sap.com/search.jspa?threadID=&q=LBWE+EVENTS&objID=c4&dateRange=all&numResults=15
Ravi

WHAT ARE EVENTS IN INTERACTIVE LIST ?

WHAT ARE EVENTS IN INTERACTIVE LIST ? IS THERE A DIFFERENCE BETWEEN INTERACTIVE LIST AND INTERACTIVE REPORT ?
BEST REGARDS,
RYAN

Hi
Events in Interactive Report
TOP-OF-PAGE DURING LINE-SELECTION
AT USER-COMMAND.
AT LINE-SELECTION
AT PF-FUNCTION KEY
Report Output is called LIST
Interactive report Output is nothing but Interactive List
<REMOVED BY MODERATOR>
Regards
Anji
Message was edited by:
Alvaro Tejada Galindo

WHAT ARE EVENTS IN A CLASSICAL REPORT ?

WHAT ARE EVENTS IN A CLASSICAL REPORT ? PLEASE EXPLAIN THEM ?
BEST REGARDS
RYAN

When u start the Report:
LOAD-OF-PROGRAM
INITIALIZATION
Before displayins Selection Screen:
AT SELECTION-SCREEN OUTPUT.
Before leaving Selection Screen:
AT SELECTION-SCREEN.
After processing Selection Screen when the List starts:
START-OF-SELECTION.
Before displaying the List .. After completing START-OF-SELECTION.
END-OF-SELECTION.
For Every page:
TOP-OF-PAGE .
END-OF-PAGE.
For more details check this link -
Events in Report

What are events In a screen

What are events In a screen
could u plz explain clearly

Hello
the events of the screen are
Variants:
1.PROCESS BEFORE OUTPUT. Process before output
2.PROCESS AFTER INPUT. Process after user input
3.PROCESS ON HELP-REQUEST. User-programmed F1 help
4.PROCESS ON VALUE-REQUEST. User-programmer F4 help
Variant 1
PROCESS BEFORE OUTPUT.
Effect
Processing before the screen is displayed (PBO).
Examples
Initializing screen fields, inserting default values, positioning the cursor, showing and hiding fields and changing field attributes dynamically.
Variant 2
PROCESS AFTER INPUT.
Effect
Processing after user input.
Examples
Checking values where there is no automatic check, processing the cursor position, processing correct entries or triggering an error dialog.
Variant 3
PROCESS ON HELP-REQUEST.
Effect
POH event for user-programmed help. Modules in this event are processed when the user presses F1 with the cursor positioned on a screen field. In the subsequent FIELD statements, you can specify a data element supplement (or determine one in an application module). The texts are then displayed by the help system.
Examples
FIELD XY WITH '0001'.
Displays data element addition 0001 for field XY.
FIELD XY WITH variable.
Displays the data element supplement with the number contained in variable for the field XY.
FIELD XY MODULE XYZ WITH variable .
The relevant data element supplement is determined in module XYZ, where it is placed in variable. Use this procedure whenever you cannot determine the correct data element supplement until the F1 event.
Variant 4
PROCESS ON VALUE-REQUEST.
Effect
Event in user-programmed help that occurs when the user presses F4 with the cursor positioned on a screen field. The modules specified in the subsequent FIELD statements are called instead of the SAP help system.
Example
FIELD XY MODULE XYZ
Module XYZ determines the value of field XY and places it in the input field on the screen.
Reward the points and close the thread.
Vasanth

WHAT ARE EVENTS IN AN ALV REPORT ?

WHAT ARE EVENTS IN AN ALV REPORT ? PLEASE EXPLAIN HOW TO MAKE AN ALV REPORT AND WHAT THE EVENTS DO ?
BEST REGARDS,
RYAN

Events are driven by user interaction...Like...
DATA_CHANGED
DOUBLE_CLICK
ONF4
Here's a sample code of OO ALV using events...
*& Report ZDUMMY_ATG_2
REPORT zdummy_atg_2.
TYPES: BEGIN OF ty_scarr,
 carrid TYPE scarr-carrid,
 carrname TYPE scarr-carrname,
 currcode TYPE scarr-currcode,
 END OF ty_scarr.
DATA: t_spfli TYPE STANDARD TABLE OF spfli,
 w_spfli LIKE LINE OF t_spfli,
 lt_f4 TYPE lvc_t_f4 WITH HEADER LINE,
 return_tab TYPE STANDARD TABLE OF ddshretval WITH HEADER LINE,
 t_custom_scarr TYPE STANDARD TABLE OF ty_scarr WITH HEADER LINE,
 t_stable TYPE STANDARD TABLE OF lvc_s_stbl WITH HEADER LINE.
FIELD-SYMBOLS: <fs_spfli> LIKE LINE OF t_spfli,
 <fs_scarr> LIKE LINE OF t_custom_scarr.
CLASS cl_gui_object DEFINITION LOAD.
CLASS lcl_event_receiver DEFINITION DEFERRED.
INCLUDE <cl_alv_control>.
DATA: ok_code LIKE sy-ucomm,
 gt_fieldcat TYPE lvc_t_fcat,
 gt_sort TYPE lvc_t_sort,
 event_receiver TYPE REF TO lcl_event_receiver,
 gs_layout TYPE lvc_s_layo,
 mycontainer TYPE scrfname VALUE 'CUSTOM_ALV',
 custom_container TYPE REF TO cl_gui_custom_container,
 grid1 TYPE REF TO cl_gui_alv_grid,
 gs_variant TYPE disvariant,
 x_save,
 w_error TYPE c,
 l_valid(1) TYPE c.
* CLASS LCL_EVENT_RECEIVER DEFINITION
CLASS lcl_event_receiver DEFINITION.
PUBLIC SECTION.
 METHODS: handle_data_changed
 FOR EVENT data_changed OF cl_gui_alv_grid
 IMPORTING er_data_changed,
 handle_f4_help
 FOR EVENT onf4 OF cl_gui_alv_grid
 IMPORTING e_fieldname es_row_no er_event_data.
ENDCLASS. "LCL_EVENT_RECEIVER DEFINITION
* CLASS lcl_event_receiver IMPLEMENTATION
CLASS lcl_event_receiver IMPLEMENTATION.
METHOD handle_data_changed.
 PERFORM data_changed USING er_data_changed.
ENDMETHOD. "HANDLE_DATA_CHANGED
METHOD handle_f4_help.
 PERFORM handle_onf4 USING e_fieldname es_row_no.
 er_event_data->m_event_handled = 'X'.
ENDMETHOD. "HANDLE_F4_HELP
ENDCLASS. "LCL_EVENT_RECEIVER IMPLEMENTATION
*& START-OF-SELECTION *
START-OF-SELECTION.
PERFORM cargar_customs.
PERFORM cargar_datos.
PERFORM fill_layout.
PERFORM fill_catalog.
PERFORM llamar_alv.
CALL SCREEN 0100.
*& Form CARGAR_DATOS *
FORM cargar_datos.
SELECT mandt carrid connid countryfr cityfrom
 airpfrom countryto cityto airpto
 fltime deptime arrtime distance
 distid fltype period
INTO TABLE t_spfli
FROM spfli.
ENDFORM. " CARGAR_DATOS
*& Form CARGAR_CUSTOMS *
FORM cargar_customs.
SELECT carrid carrname currcode
INTO TABLE t_custom_scarr
FROM scarr.
ENDFORM. " CARGAR_DATOS
*& Form FILL_LAYOUT *
FORM fill_layout.
gs_layout-sel_mode = 'A'.
ENDFORM. " FILL_LAYOUT
*& Form FILL_CATALOG *
FORM fill_catalog.
DATA: gs_fieldcat TYPE lvc_s_fcat.
CLEAR gs_fieldcat.
gs_fieldcat-col_pos = 1.
gs_fieldcat-fieldname = 'CARRID'.
gs_fieldcat-reptext = 'Compañia'.
gs_fieldcat-tabname = 'T_SPFLI'.
gs_fieldcat-edit = 'X'.
gs_fieldcat-f4availabl = 'X'.
gs_fieldcat-outputlen = '8'.
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat-col_pos = 2.
gs_fieldcat-fieldname = 'CONNID'.
gs_fieldcat-reptext = 'Conexión'.
gs_fieldcat-tabname = 'T_SPFLI'.
gs_fieldcat-edit = 'X'.
gs_fieldcat-outputlen = '8'.
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat-col_pos = 3.
gs_fieldcat-fieldname = 'COUNTRYFR'.
gs_fieldcat-reptext = 'País'.
gs_fieldcat-tabname = 'T_SPFLI'.
gs_fieldcat-edit = 'X'.
gs_fieldcat-outputlen = '4'.
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat-col_pos = 4.
gs_fieldcat-fieldname = 'CITYFROM'.
gs_fieldcat-reptext = 'Ciudad Salida'.
gs_fieldcat-tabname = 'T_SPFLI'.
gs_fieldcat-edit = space.
gs_fieldcat-outputlen = '20'.
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat-col_pos = 5.
gs_fieldcat-fieldname = 'AIRPFROM'.
gs_fieldcat-reptext = 'Arp. Salida'.
gs_fieldcat-tabname = 'T_SPFLI'.
gs_fieldcat-edit = 'X'.
gs_fieldcat-outputlen = '10'.
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat-col_pos = 6.
gs_fieldcat-fieldname = 'COUNTRYTO'.
gs_fieldcat-reptext = 'País'.
gs_fieldcat-tabname = 'T_SPFLI'.
gs_fieldcat-edit = 'X'.
gs_fieldcat-outputlen = '4'.
APPEND gs_fieldcat TO gt_fieldcat.
CLEAR gs_fieldcat.
gs_fieldcat-col_pos = 7.
gs_fieldcat-fieldname = 'CITYTO'.
gs_fieldcat-reptext = 'Ciudad Llegada'.
gs_fieldcat-tabname = 'T_SPFLI'.
gs_fieldcat-edit = space.
gs_fieldcat-outputlen = '20'.
APPEND gs_fieldcat TO gt_fieldcat.
ENDFORM. " FILL_CATALOG
*& Form LLAMAR_ALV *
FORM llamar_alv.
IF custom_container IS INITIAL.
 CREATE OBJECT custom_container
 EXPORTING
 container_name = mycontainer
 EXCEPTIONS
 cntl_error = 1
 cntl_system_error = 2
 create_error = 3
 lifetime_error = 4
 lifetime_dynpro_dynpro_link = 5.
ENDIF.
CREATE OBJECT grid1
 EXPORTING
 i_parent = custom_container.
CREATE OBJECT event_receiver.
lt_f4-fieldname = 'CARRID'.
lt_f4-register = 'X' .
lt_f4-getbefore = 'X' .
lt_f4-chngeafter = 'X' .
APPEND lt_f4.
SET HANDLER event_receiver->handle_data_changed FOR grid1.
SET HANDLER event_receiver->handle_f4_help FOR grid1.
CALL METHOD grid1->register_f4_for_fields
 EXPORTING
 it_f4 = lt_f4[].
IF sy-batch IS INITIAL.
 CALL METHOD grid1->register_edit_event
 EXPORTING
 i_event_id = cl_gui_alv_grid=>mc_evt_modified.
ENDIF.
CALL METHOD grid1->set_table_for_first_display
 EXPORTING
 is_variant = gs_variant
 i_save = x_save
 i_default = 'X'
 is_layout = gs_layout
 CHANGING
 it_fieldcatalog = gt_fieldcat
 it_sort = gt_sort[]
 it_outtab = t_spfli[].
CALL METHOD grid1->set_ready_for_input
 EXPORTING
 i_ready_for_input = 1.
ENDFORM. " LLAMAR_ALV
*& Form HANDLE_ONF4 *
FORM handle_onf4 USING p_e_fieldname
 p_es_row_no STRUCTURE lvc_s_roid.
CASE p_e_fieldname.
 WHEN 'CARRID'.
 CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 retfield = 'CARRID'
 value_org = 'S'
 TABLES
 value_tab = t_custom_scarr
 return_tab = return_tab
 EXCEPTIONS
 parameter_error = 1
 no_values_found = 2
 OTHERS = 3.
 IF NOT return_tab[] IS INITIAL.
 READ TABLE return_tab INDEX 1.
 READ TABLE t_spfli INDEX p_es_row_no-row_id
 ASSIGNING <fs_spfli>.
 <fs_spfli>-carrid = return_tab-fieldval.
 CALL METHOD grid1->refresh_table_display
 EXPORTING
 is_stable = t_stable.
 ENDIF.
ENDCASE.
ENDFORM. " HANDLE_ONF4
*& Module STATUS_0100 OUTPUT *
MODULE status_0100 OUTPUT.
SET PF-STATUS 'MAIN_STATUS'.
* SET TITLEBAR 'xxx'.
ENDMODULE. " STATUS_0100 OUTPUT
*& Module USER_COMMAND_0100 INPUT *
MODULE user_command_0100 INPUT.
ok_code = sy-ucomm.
CASE ok_code.
 WHEN 'BACK' OR 'STOP' OR 'CANCEL'.
 SET SCREEN 0.
 LEAVE SCREEN.
 WHEN 'SAVE'.
 CALL METHOD grid1->check_changed_data
 IMPORTING
 e_valid = l_valid.
 IF l_valid EQ 'X'.
 PERFORM grabar_datos.
 ENDIF.
ENDCASE.
ENDMODULE. " USER_COMMAND_0100 INPUT
*& Form DATA_CHANGED *
FORM data_changed USING rr_data_changed TYPE REF TO
 cl_alv_changed_data_protocol.
DATA: w_new,
 ls_mod_cells TYPE lvc_s_modi,
 ls_cells TYPE lvc_s_modi.
DATA: l_carrid TYPE spfli-carrid.
CLEAR l_carrid.
LOOP AT rr_data_changed->mt_good_cells INTO ls_mod_cells.
 CASE ls_mod_cells-fieldname.
 WHEN 'CARRID'.
 CALL METHOD rr_data_changed->get_cell_value
 EXPORTING
 i_row_id = ls_mod_cells-row_id
 i_fieldname = ls_mod_cells-fieldname
 IMPORTING
 e_value = l_carrid.
 IF l_carrid IS INITIAL.
 CALL METHOD rr_data_changed->add_protocol_entry
 EXPORTING
 i_msgid = '0K'
 i_msgno = '000'
 i_msgty = 'E'
 i_msgv1 = 'Seleccione algún código'
 i_fieldname = ls_mod_cells-fieldname
 i_row_id = ls_mod_cells-row_id.
 w_error = 'X'.
 ELSE.
 READ TABLE t_custom_scarr WITH KEY carrid = l_carrid
 ASSIGNING <fs_scarr>.
 IF sy-subrc NE 0.
 CALL METHOD rr_data_changed->add_protocol_entry
 EXPORTING
 i_msgid = '0K'
 i_msgno = '000'
 i_msgty = 'E'
 i_msgv1 = 'Código ingresado no existe'
 i_fieldname = ls_mod_cells-fieldname
 i_row_id = ls_mod_cells-row_id.
 w_error = 'X'.
 ENDIF.
 ENDIF.
 ENDCASE.
ENDLOOP.
ENDFORM. " DATA_CHANGED
*& Form GRABAR_DATOS *
FORM grabar_datos.
LOOP AT t_spfli ASSIGNING <fs_spfli>.
 w_spfli = <fs_spfli>.
 MODIFY spfli FROM w_spfli.
 IF sy-subrc EQ 0.
 COMMIT WORK.
 ELSE.
 ROLLBACK WORK.
 ENDIF.
ENDLOOP.
ENDFORM. " GRABAR_DATOS
Greetings,
Blag.

What are Events in NWDS Enterprise Service Repository Perspective?

Hello Experts,
does anyone have further information about the artefact "Events" in the context of the attached picture?
As far as I know is it not the same as the events in process modelling. Furthermore you can't create an object of the type "Events".
When I'm accessing the ESR with the swing client there is no object like an Event (I've checked all subcategories).
Thanks in advance and best Regards
Patrick

Hi Holger,
It is running with PI.
A detailed description of the error as follows:
503 Service not available
Error: -6
Version: 7011
Component: ICM Java
Date/Time: Tue Apr 26 06:19:18 2011
Module: http_j2ee2.c
Line: 769
Server: gblonxi01_XI1_00
Error Tag: {-}
Detail: ICM running but no server with HTTP connected
Thank you.
Regards,
Haridev

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

What are the Dynamic Events avaliable in the LabView 6.1 Event Structure?

I recieved LabView 6.1 recently and I am working with the Event Structure, and I'm trying to figure out what Dynamic Events are avaliable in the event structure, and how to access them. If you don't understand what I'm talking about, open a new VI in LabView 6.1 and drop an event structure on the diagram. Add an event and look at the dialog box that appears on the screen, specifically the Event Sources section. The third option in this area of the screen is "grayed out" but reads "Dynamic". I'm curious what these events are, and how I access them. I'm running WinNT 4 SP6.
Thanks,
Chris Davis

I believe this is part of a feature which is not yet present in LabVIEW 6.1, but may be present in a future release.

How to find what are all the rules and events are monitoring for specific server in SCOM 2007

how to find what are all the rules and events are monitoring for specific server in SCOM 2007.
I need to know what are all the events, services, and rules are monitored for the specific server.
Kindly help me friends.

how to find what are all the rules and events are monitoring for specific server in SCOM 2007.
I need to know what are all the events, services, and rules are monitored for the specific server.
Kindly help me friends.
Thanks for the question Sandoss. This is something that we all come across at sometime.
Thanks & regards, Sumit Agrawal
The lack of this feature is an inexcusable oversight for an enterprise management product. They have some serious lightweights making design decisions on the SCOM team. 5 thumbs down.
BTW the answer is probably LOTS of stuff. Literally 100's of workflows are running on any server.
The following OpsMgr DB query will list all running monitors on a server. Change the name of @srv. I think this works pretty well. I'd like some feedback if something is missing.
DECLARE @srv varchar(30)
SET @srv = 'your name here'
SELECT mon.displayName as monitor, bme.FullName,bme.DisplayName as object,
case
 when s.HealthState = 1 then 'healthy'
 when s.HealthState = 2 then 'Warning'
 when s.HealthState = 3 then 'Critical'
 else 'N/A'
end as Health
FROM state AS s WITH (NOLOCK)
left join BaseManagedEntity as bme WITH (NOLOCK) on s.basemanagedentityid = bme.basemanagedentityid
left join dbo.MonitorView Mon WITH (NOLOCK) on Mon.ID = s.monitorid
where
bme.FullName like '%' + @srv + '%'
and s.HealthState <> 0
and mon.IsInternalRollupMonitor = 0
and mon.IsExternalRollupMonitor = 0
order by bme.DisplayName, mon.displayName

What are main events in that are used in ALV reports

hi gurus
what are main events in that are used in ALV reports....
regards
baskar

hi
i think this will help u.
Events in alv and their FM    The main events in alv and their FM and why we use these:
1. SLIS_PRINT_ALV.
2. SLIS_T_LISTHEADER.
3. SLIS_T_EVENT.
4. SLIS_T_SORTINFO_ALV.
5. SLIS_T_LAYOUT_ALV.
6. SLIS_T_FIELDCAT_ALV.
and in classic reports what is the sequence of events:   === Events are
At selection-screen output.
Initialization.
At selection-screen on field
At selection-screen on end of field
At selection-screen on Radiobutton Group R1. (If you have any radio buttons)
At selection-screen on block b1. (If you have any blocks)
Start-of-selection.
Get node. (if the data is retreived from a logical database)
Get node late. (if the data is retreived from a logical database)
Top-of-page. (if the write statement is in the end-of-selection event or we can say that before the first write statement)
end-of-selection.
and fuction modules are
LISTHEADER - Is used to print the header information in the ALV List. Name, Date, Time, ALV Name and other details are called as Header information.   EVENT - Basically this is the FM to handle Event's. When the user needs to do some event operation like when double clicking the a particular field we need to perform some operation.   These events are captured by this FM.   LAYOUT - This FM is used to define the layout of the List. There are many options available in this FM to define the Layout style.   FIELDCAT - These are used to populate the List header. We can change them according to our req.
User-defined Text Output Event
    Application
      print_end_of_list
    Define output text to be printed at the end of the entire list
      print_top_of_list
    Define output text to be printed at the beginning of the entire list
      print_end_of_page
    Define output text to be printed at the end of each page
      print_top_of_page
    Define output text to be printed at the beginning of each page
      subtotal_text
    Define self-defined subtotals texts
Mouse-controlled Actions in the Grid Control Event
    Application
      button_click
    Query a click on a pushbutton in the ALV Grid Control
      double_click
    Query a double-click on a cell of the ALV Grid control
      hotspot_click
    Query a hotspot click on columns defined for this purpose in advance
      onDrag
    Collect information when elements of the ALV Grid Control are dragged
      onDrop
    Process information when elements of the ALV Grid Control are dropped
      onDropComplete
    Perform final actions after successful Drag&Drop
      onDropGetFlavor
    Distinguish between options for Drag&Drop behavior
Processing of Self-defined and Standard Functions Event
    Application
      before_user_command
    Query self-defined and standard function codes
      user_command
    Query self-defined function codes
      after_user_command
    Query self-defined and standard function codes
Definition of Self-defined Functions Event
    Application
      toolbar
    Change, delete or add GUI elements in the toolbar
      menu_button
    Define menus for menu buttons in the toolbar
      context_menu_request
    Change context menu
      onf1
    Define self-defined F1 help
All of these can be found under type group SLIS.
Events
SLIS_EV_ITEM_DATA_EXPAND        TYPE SLIS_FORMNAME VALUE 'ITEM_DATA_EXPAND',
SLIS_EV_REPREP_SEL_MODIFY       TYPE SLIS_FORMNAME VALUE 'REPREP_SEL_MODIFY', SLIS_EV_CALLER_EXIT_AT_START TYPE SLIS_FORMNAME VALUE 'CALLER_EXIT',
SLIS_EV_USER_COMMAND              TYPE SLIS_FORMNAME VALUE 'USER_COMMAND',
SLIS_EV_TOP_OF_PAGE                     TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE',
SLIS_EV_DATA_CHANGED                TYPE SLIS_FORMNAME VALUE 'DATA_CHANGED',
SLIS_EV_TOP_OF_COVERPAGE       TYPE SLIS_FORMNAME VALUE 'TOP_OF_COVERPAGE',
SLIS_EV_END_OF_COVERPAGE       TYPE SLIS_FORMNAME VALUE 'END_OF_COVERPAGE',
SLIS_EV_FOREIGN_TOP_OF_PAGE TYPE SLIS_FORMNAME
VALUE 'FOREIGN_TOP_OF_PAGE', SLIS_EV_FOREIGN_END_OF_PAGE TYPE SLIS_FORMNAME
VALUE 'FOREIGN_END_OF_PAGE',
SLIS_EV_PF_STATUS_SET                  TYPE SLIS_FORMNAME VALUE 'PF_STATUS_SET',
SLIS_EV_LIST_MODIFY                      TYPE SLIS_FORMNAME VALUE 'LIST_MODIFY',
SLIS_EV_TOP_OF_LIST                       TYPE SLIS_FORMNAME VALUE 'TOP_OF_LIST',
SLIS_EV_END_OF_PAGE                    TYPE SLIS_FORMNAME VALUE 'END_OF_PAGE',
SLIS_EV_END_OF_LIST                      TYPE SLIS_FORMNAME VALUE 'END_OF_LIST',
SLIS_EV_AFTER_LINE_OUTPUT       TYPE SLIS_FORMNAME VALUE 'AFTER_LINE_OUTPUT', SLIS_EV_BEFORE_LINE_OUTPUT     TYPE SLIS_FORMNAME VALUE 'BEFORE_LINE_OUTPUT',
SLIS_EV_SUBTOTAL_TEXT                TYPE SLIS_FORMNAME VALUE 'SUBTOTAL_TEXT'.
with regards
sravani
award points if found useful.

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

WHAT ARE SUBEVENTS OF DIFFERENT EVENTS IN REPORTS ?

WHAT ARE SUBEVENTS OF DIFFERENT EVENTS IN REPORTS ?
BEST REGARDS,
RYAN

hi,
output events are.........
start-of-selection.
using this event we can genarate basic list.
end-of-selection.
we can use this event also for genarating basic list
top-of-page.
this event is related to list, we can use this event to providing list header.
end-of-page.
this event is related to list, we can use this event to providing list footer.
if our program reading data from logical database, in that case GET and
GET LATE events triggered to genarate report.
interactive repotrs.
we use AT LINE -SELECTION and AT USER-COMMAND events to genarate secondary events based on user actions.
TOP-OF-PAGE DURING LINE-SELECTION EVENT, provides page heading to all secondary lists.
PBO and PAI events also used to genarating list.
regards,
AshokReddy.

WHAT ARE SUB EVENTS OF EVENTS IN REPORTS ?

WHAT ARE SUB EVENTS OF EVENTS IN REPORTS I.E INITIALIZATION, AT SELECTION SCREEN, START OF SELECTION, END OF SELECTION. WHAT ALL EVENTS HAVE SUB EVENTS ? PLEASE EXPLAIN IN DETAIL.
REWARD POINTS GUARENTEED FOR ANSWERS!!

hi,
Check out these:
Processing time Meaning Default setting
__BEGIN_OF_PROCESSING__ Before the beginning of
data processing
(blank)
__BEGIN_OF_TRANSACTION__ Before the beginning of
transaction data
processing
(blank)
__BEGIN_OF_RECORD__ Before applying the
conversion rules for a
source structure
Initialize the structure <segment>
(Name of target structure)
Batch Input, Direct Input:
<segment> = init_<segment>.
BAPI, IDoc:
g_edidd_segnam = '...'.
g_edidd_segnum = '....'.
g_edidd_psgnum = '......'.
g_edidd_hlevel = '..'.
Clear <segment>.
__END_OF_RECORD After applying the
conversion rules for a
source structure
Transfer_record.
__END_OF_TRANSACTION__ After finishing transaction
processing
Transfer_transaction.
__END_OF_PROCESSING__ After finishing data
processing
(blank)
transfer_record. Transfers the current record (i.e. for the current target
structure) to the output buffer.
transfer_this_record '...'. Transfers a record of another target structure to the output
buffer. The name of the target structure has to be specified as
argument in single quotes.
at_first_transfer_record. Transfers the current record to the output buffer, if it is the first
transaction.
on_change_transfer_record. Transfers the current record to the output buffer, if it has
changed compared to the last record.
transfer_transaction. Writes the current transaction to an output file. All records of
Legacy System Migration Workbench
38
the output buffer are transferred to the output file.
skip_record. The current record is not transferred to the output buffer.
skip_transaction. The current transaction is not written to the output file.

How to identify what are all the events are created in background jobs?

Hi all,
how to identify what are all the events are created for background jobs. And what events gets triggered for a particular job.
thanxs
haritha

Hi Haritha,
JOB is a program which starts to a determined point of time and executes some standard programs in the system. JOBs can be planed to a determined point of time on the regular basis (every night, for example) or to some discret time moments. So, the JOB can be planed and then will be started automatically without the manual start.
Realtime programs are understood in the most cases as actual program execution which is started by somebody to the actual moment of time.
Typically per JOBs some special processes will be started that should be executed automatically and regularly: for example, IDOC application, some correction reports, statistic updates etc.
Standard jobs are those background jobs that should be run regularly in a production SAP System These jobs are usually jobs that clean up parts of the system, such as by deleting old spool requests.
Use
As of Release 4.6C, the Job Definition transaction ( sm36 ) provides a list of important standard jobs, which you can schedule, monitor, and edit.
Standard jobs are those background jobs that should be run regularly in a production SAP System. These jobs are usually jobs that clean up parts of the system, such as by deleting old spool requests.
for more information you can go thru the following thread:
http://help.sap.com/saphelp_nw70/helpdata/en/24/b884388b81ea55e10000009b38f842/frameset.htm
About Events:
Events have meaning only in the background processing system. You can use events only to start background jobs.
Triggering an event notifies the background processing system that a named condition has been reached. The background processing system reacts by starting any jobs that were waiting for the event.
Types of Events:
There are two types of events:
1.)System events are defined by SAP. These events are triggered automatically when such system changes as the activation of a new operation mode take place.
2.)User events are events that you define yourself. You must trigger these events yourself from ABAP or from external programs. You could, for example, signal the arrival of external data to be read into the SAP system by using an external program to trigger a background processing event.The event scheduler processes an event if the event is defined in the system.
For example, if a system (System 1) receives an event from another system (System 2), the event scheduler of System 1 processes the event only if it is defined in System 1. That event does not need to be defined in System 2 (the sending system).
You define an event by assigning a name (EVENTID) to it. When defining an event, you do not define the event arguments.
for more information you can go thru the following thread:
http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e2a543b11d1898e0000e8322d00/frameset.htm
When you schedule the process chain or infopackages the jobs associated with it run in the background mode. In case you want to create a job for a specific activity you can do so in SM36. You would be creating jobs that would get executed in any one of the options:
1. Immediate
2. Date & Time
3. After event.
4. After job.
5. At Operation mode.
In case you want to view the job logs go to sm37.
Also Pls check DB02 for database performance and ST03 for workload .
Analyse u will have an idea ,
*pls assign points,if info is useful**
Regards
CSM reddy
null

What are "events"?

Similar Messages

Maybe you are looking for