Job triggered by event created with BP_EVENT_RAISE

[fernando_martin]

Hello,

in the exit for sales orders we trigger one event to call one program using FM BP_EVENT_RAISE. We have one job that starts after this event is created and looking with SM37 the job is still released under this condition (as is also in table BTCEVTJOB). The event is created correctly and the process has been working fine until a couple of days ago. I create new sales orders and see that this FM is still called, but the job does not start.

I am trying to track the created events with transaction SWEL, but it does not work. How can I check that the event is being created and processed? any other transactions or programs to check this?

Thanks.

[Former Member]

hi,

as per my experience, in some user-exit you cannot call the BP_RAISE_EVENT ( or the method of the static class CL_BATCH_EVENT->RAISE ) . Even if the event is define correctly and the job is scheduled correctly the bapi call has no effect on event rasing and job is still in released status.

You can try to create a job having the needed steps and directly executed .( JOB_OPEN, submit 'your_program', JOB_CLOSED ).... .. so i suggest to create a custom FM that execute this work .( JOB_OPEN, submit 'your_program', JOB_CLOSED ) and call it into the user exit..

Hope this can be a good input for you.

Best regards luigi.

Edited by: luigi la motta on Jun 14, 2010 4:14 PM

[ThomasZloch]

In newer releases, SM62 shows you the history of batch events (it's different from the workflow events that SWEL shows you), check there if the event was triggered at all.

Thomas

[fernando_martin]

Thanks.

Unfortunately, I am working with version 4.6C, so with SM62 I can only see when the action log over the user event. We mantain other system with ECC60 and there SM62 looks different with more functionalities, but our problem is with the system 4.6C.

I wonder if there is another way to check if the events are really being triggered, as when we use SM64 to trigger manually (then the job starts).

[SuhaSaha]

If i am not wrong till ECC5.0 there was no way we could trace the event history. Check this thread: .

@Thomas: Thanks for sharing the info.

[fernando_martin]

The problem was that with a client copy they have changed some parameters of server destinations, etc, so once this has been fixed the problem has dissapeared. We can look at this with RZ12.

Thanks for your support.