cancel
Showing results for 
Search instead for 
Did you mean: 

Program RSM13000 triggers workflow automatically

andrs_sarcevic
Contributor
0 Kudos

Hi all,

I currently have a workflow being triggered automatically by program RSM13000. Anybody can throw some light for me?

Is this a normal behaviour? It had never happened before... I just found this thread on the matter, unanswered sadly to say.

Regards,

Andres.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

This program will pretty much show up for most triggered events in the event log. This is the batch job that actually picks up the event and generates workflow instances. Now, in your case you want to know what is the event being triggered. You want to look at event linkage table (transaction SWETYPV). If you want to find out where the event is being triggered then this is a tricky task. One way to find out is to place a break point in the receiver function module. You can replace it with a custom function module that throws an exception and see where it fails. If you don't want to create a short dump, you can put a "timed" loop that waits for a minute (do not use WAIT statement), but rather use DO WHILE. This way, you can find the process in SM50 and debug it within a minute.

As far as creating events, you should use SAP_WAPI_CREATE_EVENT. Basically, when dealing with workflow programmatically you should always use function modules that start with SAP_WAPI.

anjan_paul
Active Contributor
0 Kudos

Hi,

  Which workflow it is triggering. I saw in this program on FM is called BP_EVENT_RAISE. But it is used for starting background job. May there have any user exit or they may link this event to workflow thats why it is calling. Please check i the workflow basic data start event tabs what event is linked with that workflow.

andrs_sarcevic
Contributor
0 Kudos

Hi Anjan,

It's triggering workflow WS55100587, used in Banking Services for approval process. As this is standard workflow and triggering happens only due to customizing and event linkage, I don't think a user exit is involved, and SWEL states that program in the logging. But it may as well be something else that this report is pushing that triggers the workflow.

I'll double check the basic data as well.
Thank you for your time.

By the way... FM BP_EVENT_RAISE has this comment inside: "This function module is obsolete. Please do not use it. This function module is planned to be deleted. Substitution: CALL METHOD cl_batch_event=>raise"