topic Re: CALL 'RaiseEvent' in Application Development and Automation Discussions

CALL 'RaiseEvent'

Former Member — Mon, 15 Oct 2007 11:56:36 GMT

Hello experts.

I was debugging into FM "BP_EVENT_RAISE" for an issue.

Command comes to following statement gets executed without going into it.

CALL 'RaiseEvent'

ID 'EVTI' FIELD evt_id

ID 'EVTP' FIELD evt_parm

ID 'TSYS' FIELD tgt_srv.

where Field values were

evt_id SAP_START_EHS_RDO_EVENTHANDLER

evt_parm 510-{0-00000000000000000000-00000000000000056540

tgt_srv SPACE

Something is getting executed in this step which is distorting our output.

I want to know where to see what steps are getting executed in this statement.

I tried looking this event in SM64 but its only to trigger.

Pleae help.

Sure reward points for Help...

Re: CALL 'RaiseEvent'

Former Member — Mon, 15 Oct 2007 12:05:44 GMT

go to the source code of this function module.........BP_EVENT_RAISE....

keep the break point over raise event.

reward points if useful

Re: CALL 'RaiseEvent'

marcelo_ramos1 — Mon, 15 Oct 2007 12:25:13 GMT

Hi,

This is a System Function, you can't see or debugging it's source code because it's a C source code.

I think you Could try to find the events that are triggered by this function and then put a break point at it's event handler.

Regards.

Marcelo Ramos

Re: CALL 'RaiseEvent'

Former Member — Mon, 15 Oct 2007 12:58:57 GMT

I have an idea of FM's getting triggered by this Step. Placed a break point on them but debugging not stopping on those break points.

I wanted to know wheather there is any code in the Event like "SAP_START_EHS_RDO_EVENTHANDLER" in my case.

Re: CALL 'RaiseEvent'

marcelo_ramos1 — Mon, 15 Oct 2007 13:47:13 GMT

Hi,

I believe that it is very difficult to predict which routinely this function executes. But as the name suggests (RaiseEvent) i believe that one event of one class is triggered and all event handlers( Methods ) that are listening to this event are triggered.

Unfortunately this System Function can run other System Function, Or anything other than what I said, in these case we can not know what they do.

<b>All these SAP system functions are for internal use only, and don't have any documentation about it. </b>

Regards.

Marcelo Ramos

Re: CALL 'RaiseEvent'

uwe_schieferstein — Mon, 15 Oct 2007 18:56:40 GMT

Hello Dheeraj

Perhaps chapters 3.25 & 3.26 in document

<a href="http://help.sap.com/bestpractices/BBLibrary/documentation/Q50_BB_ConfigGuide_EN_ZH.doc">Q50 EH&S / RM Basics</a>

may be useful to understand what happens after the event has been triggered.

Another useful document may be:

<a href="http://help.sap.com/bestpractices/BBLibrary/documentation/Q51_BB_InstallGuide_EN_US.doc">Q51 Product Safety</a>

Regards

Uwe

Re: CALL 'RaiseEvent'

Former Member — Tue, 16 Oct 2007 05:37:50 GMT

hi,

Hope this will help.

Events let you start background jobs when particular changes in the SAP system take place.

When an event occurs, the background processing system starts all jobs that were scheduled to wait for that event.

http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e2a543b11d1898e0000e8322d00/frameset.htm

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.

http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e37543b11d1898e0000e8322d00/frameset.htm

Use function module BP_EVENT_RAISE to trigger an event from an ABAP program.

Example

Report processing before triggering event...
Trigger event to start background jobs waiting for the event.

DATA: EVENTID LIKE TBTCJOB-EVENTID.

DATA: EVENTPARM LIKE TBTCJOB-EVENTPARM.

EVENTID = 'SP_TEST_EVENT'. " Event name must be defined

" with transaction SM62.

EVENTPARM = 'EVENT1'. " Optional: a job can be

" scheduled to wait for an

" EVENTID or combination of

" EVENTID and EVENTPARM.

CALL FUNCTION 'BP_EVENT_RAISE' " Event is triggered. Jobs

EXPORTING " waiting for event will be

EVENTID = EVENTID " started.

EVENTPARM = EVENTPARM

TARGET_INSTANCE = ‘ ‘ " Instance at which an event

" should be processed. Can

" generally be omitted.

EXCEPTIONS OTHERS = 1. " Exceptions include event not

" defined, no EVENTID

" exported, etc.

<b>Reward if usefull</b>