Event triggering sources

[devrajsinghr]

Hi Friends,

Is there any way to check the sources of event triggering? event trace is not thr..

Regards

Dev

[Former Member · Accepted solution]

Also remember to then activate the Event Queue using SWEQADM. There you will need to activate the Background Job and switch on the Event Queue.

Use transaction SWEQBROWSER to see info relating to each triggered event including the program source.

[Former Member]

Enable the Event Queue on the Event Linkage. There's also sorts of info captured.

[Former Member]

3 Transactions are enough:

SWEL - To Check the trace of events happened

SWELS - to start the Trace (do not do it in Prod environment for long time)

SWE2 - To define the event linkage

Check if FM SWE_CREATE_EVENT is used somewhere this cal also trigger event.

Regards

Shital

[Former Member]

Apart from tcode SWEL, Event trace is available in Goto Menu of "create event" Tcode SWUE .

Also, you can simulate an event in Tcode SWU0 which will give status of all wokflows using this event.

Regards,

Archana

[bpawanchand]

Check execute the Txn SWEL and check this txn updates the table SWFREVTLOG

[surjith_kumar]

Hi,

You want to see the whether any event trigger for a transaction right.

check the Table: SWFREVTLOG

Regards,

Surjith

[devrajsinghr]

Hi Surjit,

Thanks 4 replying.

But this table contain the data regarding the event triggering only when event trace is on, The problem is I need to check the data of the event which triggered when event trace was off. So is there any way which can tell the source of event triggering?

Regards

Dev

Edited by: Dev on Mar 19, 2009 12:32 PM

[Former Member]

hi,

From your post what i understood is, you don't have a event being triggered or captured even though you ran the event trace during your transaction.

If you are trying to initiate a work flow with respect to triggering of events and if you don't have any events you need to either of two ways.

1) Message control--> whenever your transaction you can assign the work flow for every success or failure message

2) Change pointers or change document objects:

trigger the work flow whenever there's a update in the tables CDHDR and CDPOS.

Regards

Sharath