Event is triggered again and again after error

[tobias_setzekorn]

I have started the event BUS2081-POSTED manually via SWUE with an invalid object key. Unfortunately the receiving function module is now producing a short dump due to the invalid object key. Due to the dump the event is now triggered hourly and running each time on the same dump.

Does anybody have an idea how to get rid of that event? I had a look in SWEQDEL, but this is empty.

I know that the best solution would be to change the receiving function module to have a better exception handling, but this is currently not possible.

Thanks a lot for your help...

[tobias_setzekorn]

This is very easy. I started in transaction SWUE the event BUS2081-POSTED with any object key which is not a MM invoice. In our solution we have a self-made workflow for that event with a self-made receiver function module. That function module expected a valid MM invoice document number. Due to the lack of a good exception handling, the function module produced a short dump because of the invalid MM document number. SAP now tries to execute this again each hour.

[former_member185167]

Hello,

"SAP now tries to execute this again each hour"

Is that how you have temporary error handling set up??

regards

Rick Bakker

hanabi technology

[tobias_setzekorn]

I just found the solution. I can delete it in transaction SM58.

[former_member185167]

Can you explain how SWUE can lead to an event being created again and again?

[tobias_setzekorn]

There is a workflow assigned to the event. But not started because the receiver function module goes on a dump. This is just because of an invalid object type assigned with SWUE, normally this is working perfectly.

Unfortunately we currently cannot change the function module to resolve the dump in the coding. I just want to get rid of this single event which is triggered hourly now because it runs on the dump. There are no new events created, it is just the old one which SAP wants to start again until the error is resolved.

[suresh_subramanian2]

Hello !

If no workflows are associated with the business object BUS2081 and the event POSTED, deactivate it at SWE2.

Otherwise, you should resolve the cause for dump.To know the reason for dump, following transactions would be helpful : ST22,ST01,ST05 and ST12.

Instead of checking at SWEQDEL transaction, check at SWEQADM transaction.

Regards,

S.Suresh.