Squence of events triggered in reports

Hi all,
Please specify squence of events trigger. When top-of-page event triggers? When end of selection event triggers
venkraa

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
the top of page can put any where in the program..
end of selection is after selecting data means the population of data is done in the start-of-selection and no data is selected in the end of selection if you write select after the end of selection ...is of no use..
regards,
venkat
regards,
venkat .

Similar Messages

Event Triggered when a Report is generated

Hi ,
When we execute a report is there a trigger which captures this event. I need to execute an APD once the report is executed.
Could you please give me the name of the event when a report is generated?

Thanks for the quick response.
I have tried with POST-FORM event. But it is not working for me.
Ihave defined a seq 10 with
a) Condition
Trigger Event = WHEN-NEW-FORM-INSTANCE
b) Action
Type = Builtin
Builtin Type = Forms_DDL
Argument = Script for creating a trigger
I have created another seq 20 with
a) Condition
Trigger Event = WHEN-FORM-NAVIGATE
b) Action
Type = Builtin
Builtin Type = Forms_DDL
Argument = scritpt to disable the trigger
When form is opened, trigger is getting created.
But when the user closes the form, it is not disabling the trigger. User closes the form by clicking on 'X' on the window.
As per your suggesion , I have changed the trigger event to POST-FORM in seq20. It is not working.
I have tried with WHEN-WINDOW-CLOSED event also.
Please help me in this.

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

Event Triggers not getting executed

I'm having following code in beforeData(PLSQL) event trigger:
ADCPackageName.MethodName
There is no such package in database, even my report works fine and publish data without any error.
Is there any configuration for enabling event triggers.
I didn't sufficient documents on event triggers. I want to use them for returning some values to report variables and validating input parameters.

Hi,
I tried to use "SAP_WAPI_CREATE_EVENT" also but it is also behaving in the same manner.
At first execution event is getting triggered but my workitem is not getting terminated.
But when i am executing the same report second time, again my event is getting triggered, and this time my workitem got terminated, and workflow proceeded furthur.
I checked it from SWEL, i have two entries for my event (i.e; first and second execution of report).
Any idea why it is behaving like this.
Please find below code for reference, apart from below code i have only declarations.
call function 'SWC_ELEMENT_SET'
EXPORTING
    element       = 'ActualState'
    field         = 'A'
TABLES
    container     = it_cont
EXCEPTIONS
    type_conflict = 1
    others        = 2.
CALL FUNCTION 'SWE_EVENT_CREATE'
EXPORTING
    OBJTYPE                       = 'WORKINGWI'
    OBJKEY                        = '000000003061'
    EVENT                         = 'Approve'
IMPORTING
   EVENT_ID                      = it_event_id
RECEIVER_COUNT                =
TABLES
   EVENT_CONTAINER               = it_cont
EXCEPTIONS
   OBJTYPE_NOT_FOUND             = 1
   OTHERS                        = 2
COMMIT WORK.
Regards,
Amar

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

Regarding events in alv reports

Dear Friends,
Sorry for this post, Events not triggering in alv reports. There is no errors and no warnings.I am using interactive reports. Please tell me where could be i went wrong. It is displaying basic list information but with out events triggering.

Hi,
go through the following piece of code..........
*& Form EVENT_CALL
we get all events - TOP OF PAGE or USER COMMAND in table v_events
FORM EVENT_CALL.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
I_LIST_TYPE = 0
IMPORTING
ET_EVENTS = V_EVENTS
EXCEPTIONS
LIST_TYPE_WRONG = 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.
ENDFORM. "EVENT_CALL
*& Form POPULATE_EVENT
Events populated for TOP OF PAGE & USER COMAND
FORM POPULATE_EVENT.
READ TABLE V_EVENTS INTO WA_EVENT WITH KEY NAME = 'TOP_OF_PAGE'.
IF SY-SUBRC EQ 0.
WA_EVENT-FORM = 'TOP_OF_PAGE'.
MODIFY V_EVENTS FROM WA_EVENT TRANSPORTING FORM WHERE NAME =
WA_EVENT-FORM.
ENDIF.
READ TABLE V_EVENTS INTO WA_EVENT WITH KEY NAME = 'USER_COMMAND'.
IF SY-SUBRC EQ 0.
WA_EVENT-FORM = 'USER_COMMAND'.
MODIFY V_EVENTS FROM WA_EVENT TRANSPORTING FORM WHERE NAME =
WA_EVENT-NAME.
ENDIF.
ENDFORM. "POPULATE_EVENT
FORM DISPLAY_ALV_REPORT.
V_REPID = SY-REPID.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_CALLBACK_PROGRAM = V_REPID
I_CALLBACK_PF_STATUS_SET = ' '
I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
I_GRID_TITLE = I_TITLE_EKKO
I_GRID_SETTINGS =
IS_LAYOUT = ALV_LAYOUT
IT_FIELDCAT = I_FIELDCAT[]
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
i_default = 'ZLAY1'
I_SAVE = 'A'
is_variant = i_variant
IT_EVENTS = V_EVENTS
TABLES
T_OUTTAB = IT_EKKO
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.
ENDFORM. "display_alv_report
*& Form TOP_OF_PAGE
text
FORM TOP_OF_PAGE.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
IT_LIST_COMMENTARY = IT_LISTHEADER
i_logo =
I_END_OF_LIST_GRID =
ENDFORM. "TOP_OF_PAGE
*& Form USER_COMMAND
text
-->R_UCOMM text
-->, text
-->RS_SLEFIELDtext
FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM
RS_SELFIELD TYPE SLIS_SELFIELD.
CASE R_UCOMM.
WHEN '&IC1'.
READ TABLE IT_EKKO INTO WA_EKKO INDEX RS_SELFIELD-TABINDEX.
PERFORM BUILD_FIELDCATLOG_EKPO.
PERFORM EVENT_CALL_EKPO.
PERFORM POPULATE_EVENT_EKPO.
PERFORM DATA_RETRIEVAL_EKPO.
PERFORM BUILD_LISTHEADER_EKPO USING IT_LISTHEADER.
PERFORM DISPLAY_ALV_EKPO.
ENDCASE.
ENDFORM. "user_command
*& Form event_call_ekpo
we get all events - TOP OF PAGE or USER COMMAND in table v_events
FORM EVENT_CALL_EKPO.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
I_LIST_TYPE = 0
IMPORTING
ET_EVENTS = V_EVENTS
EXCEPTIONS
LIST_TYPE_WRONG = 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.
ENDFORM. "event_call_ekpo
*& Form POPULATE_EVENT
Events populated for TOP OF PAGE & USER COMAND
FORM POPULATE_EVENT_EKPO.
READ TABLE V_EVENTS INTO WA_EVENT WITH KEY NAME = 'TOP_OF_PAGE'.
IF SY-SUBRC EQ 0.
WA_EVENT-FORM = 'TOP_OF_PAGE'.
MODIFY V_EVENTS FROM WA_EVENT TRANSPORTING FORM WHERE NAME =
WA_EVENT-FORM.
ENDIF.
ENDFORM. "POPULATE_EVENT
*& Form TOP_OF_PAGE
text
FORM F_TOP_OF_PAGE.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
IT_LIST_COMMENTARY = IT_LISTHEADER
i_logo =
I_END_OF_LIST_GRID =
ENDFORM. "TOP_OF_PAGE
Thanks
Ashu

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

File Events Triggering Erroneously

I have been using file events for a few years. The creation of a file from an application triggers a report to run (file event), then I use schedule events to trigger addtional reports for the same application. The file events are getting triggered for no apparent reason. The files did not get updated or created new. The files are in shared folders on filers which are referenced in CMC as File Events using a UNC designation.
When this happens, it usually triggers all file events. This happened a few times in the past, and I would clean up the mess and blame it on sunspots. But it has happened three times in the past month. I'm not sure if it's something on the network that makes these files appear "new" or if there's an issue with BOE File Events. Has anyone else encountered issues with File Events? Is there a fix? Thanks in advance for your response.

Hi Isaac,
You'll probably best off with moving the files away. For some reason, the move caused all files to look like new ones.
If all files are processed one by one anyway, you could have CPS move them using a move directory so they'll never show up again.
Regards,
Anton.

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.

Event triggers from HANA to sharepoint

Hi All,
Is it possible to create a trigger in HANA that on creation of a new row in a particular table, creates an event that goes to a sharepoint portal and triggers a mail and a push notification to MS BI mobile users?
Please let me know how that would work.
Thanks,
Shyam

Hi,
I have the same req, we did like below the problem is resolved.
1. Craete Event in SM62 in BW , Event name = ECCTOBW.
2. Assign that Event in BW and give Parameter name = ECCTOBW_P. (Param is directly give in BW)
(In Case of dataloads, create Process chain and give thios Event and Parameter in Start-->Event) and Activate and Exexute the Processc Chain.
3. Then Run the below program in ECC then check your processc hain, it will trigger.
This is the way how to use the Events triggers in different system.
REPORT ytestrd1tobd1.
CALL FUNCTION 'RSSM_EVENT_RAISE'
DESTINATION 'BWCLNT' ------------> Here give your BW system ID
EXPORTING
 i_eventid = 'ECCTOBW'
 i_eventparm = 'ECCTOBW_P1'
EXCEPTIONS
 bad_eventid = 1
 eventid_does_not_exist = 2
 eventid_missing = 3
 raise_failed = 4
 OTHERS = 5.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Thanks
Reddy

Events Triggered

hi
guys i am not understand why the out put is 1,2,99.
please explain me
Events Triggered in the Order Dictated by the Driver Program
1 report ztx1702.
2 data f1 type i value 1.
3
4 end-of-selection.
5 write: / '3. f1 =', f1.
6
7 start-of-selection.
8 write: / '2. f1 =', f1.
9 f1 = 99.
10
11 initialization.
12 write: / '1. f1 =', f1.
13 add 1 to f1.
output:
1. f1 = 1
2. f1 = 2
3. f1 = 99
thanks

Hi Sanjeev,
Order of events triggered in ABAP programming is..
 INITIALIZATION
 AT SELECTION-SCREEN
 AT SELECTION-SCREEN ON <field>
 START-OF-SELECTION
 TOP-OF-PAGE
 END-OF-PAGE
 END-OF-SELECTION
ABAP program will be executed in the above event order, with out depending on the order you write.
Your program execution will be like this..
1) It declares the f1 as the integer type value and initializes 1 to it.
2) It directly goes to the Intialization part and there you are printing f1 value which is 1.
So there the output will be 1.f1 = 1.
At step 13 It will add 1 to f1. so here your f1 value is 2.
3) It then goes to the Start-of-selection event.
 Here you are again printing f1 value which is 2.
 after printing f1 value you are assigning 99 to f1 so your f1 now becomes to 99.
4) It goes to End-of-selection part and again you are printing f1 value which is 99.
So your report output willbe like this..
1.f1 = 1.
2.f1 = 2.
3.f1 = 99.
Thanks,
Sreekanth.
Message was edited by: Sreekanth G
Message was edited by: Sreekanth G

Event Triggered?

Hi all
Please tell me in the below code i mentioned which is the first event that gets triggered.I think its AT-SELECTION-SCREEn event.
REPORT ZPRE_5 .
tables:s026.
parameters:wrbtr1 type bseg-wrbtr.
at selection-screen .
if wrbtr1 is initial.
MESSAGE 'Please enter a value' TYPE 'E'.
endif.
START-OF-SELECTION.
Write:/ 'Hi1'.
Write:/ 'Hi2'.
END-OF-SELECTION.
With Regards
Vijay G

Hi,
It is At selection screen to be triggered first.
then START-OF-SELECTION
Event related to reports are not triggered based on any statements in ABAP.
The event are triggered depended on the way the output is generated .
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 If Helpful,
Jagadish

How to disable the "turn page" event triggered by the scroll/swipe function?

The problem is as follows.
The default behaviour of Acrobat Reader (both stand alone and browser plug-in) is to allow scrolling/swiping with the mouse wheel/trackpad. This is useful when the pdf's page length is greater than the screen's own length, because you can read the pdf with no need to distract your attention from the text to the scrollbar button. However, the same scroll/swipe function turns into a usability problem when the pdf is embedded in a html page and the pdf's page length is smaller than the browser's length. In this case, the scroll/swipe turns the page, distracting your attention from the text to the unintended behaviour of the browser. What happens is that you are so used to scrolling/swiping that you did it unintentionally in the pdf's caption area. You really did not want to turn pages in the pdf. Furthermore, if the pdf takes the whole html page, being a website, the scroll/swipe function flips the website pages in ways that neither the reader nor the writer had ever intended. Hence the question. How to disable, in this case, the "turn page" event triggered by the scroll/swipe function? A JavaScript should do, but the SDK documents did not help so far...
Message was edited by: 41457173
Message was edited by: 41457173

... or release a patch for the API,
... or suggest an alternative route to achieve the intended result.

Event triggering by abap class & ISR

hi gurus
1 ) can i able to see the event triggering by abap class in SWEL ? ,
2) in custom ISR scenario , new form scenario has been created by our functional consultant , and asking me to trigger a workflow for approval , when employee fills that particular ISR FORM , workflow should start and to go his HR administrator , when HR administrator double click on workitem he should get the ISR form in display mode & also with some descpition text is to be added in the screen (like user decision description ) with approval button ..... my question is how to trigger a event from in form scenario ? , how to bring the FORM screen to display mode to the HR administrator ?
regards
surya

Hi Surya
The BO for ISR forms is BUS7051 - Notification. Turn on the trace via SWELS and create a PCR/ISR form and you should see the events being triggered in SWEL.
Good Luck
Ravi

Event triggered for checkbox in cl_gui_alv_grid

Hi All ,
I have a requirement like ,i give PO number on selection-screen.After execution, the items should be displayed on second screen ,which has some options on the top like before GR or after GR .(custom screen designed with cl_gui_alv_grid for display)
I desgined checkboxes for each row of the line item.user can click on multiple rows and click on EXECUTE button on the screen.After that smartform should trigger and print .
Now my query is how to capture the checkboxes which the user has entered (thru cl_gui_alv_grid) . Is there any event that gets triggered upon clicking the checkboxes?? I need the data of the corresponding row to process further .User can click on multiple items.
Please respond
Thanks

Hi Hemanth
You should have a field in your internal table matching the checkbox column in ALV.
Call method CHECK_CHANGED_DATA of CL_GUI_ALV_GRID on user command for execute button,
it will set the field = 'X' for ticked lines in your internal table.
Then use a loop on your internal table and find selected lines.
You don't need an event triggered when user clicks.
Edited by: Bulent Balci on Aug 3, 2010 4:42 PM

Squence of events triggered in reports

Similar Messages

Maybe you are looking for