cancel
Showing results for 
Search instead for 
Did you mean: 

Correlations in Workflow - wait for Delete event problem

Former Member
0 Kudos

Hi All,

I am working on version ECC5.

I have a workflow that needs to wait for any changes to i0008, i0007, i0509 and i2001 for the person who is the subject of the workflow. I have used correlations to do this and it is all working fine except for the Delete event.

For each infotype I wait for each event ie. Approved, Changed, Created, ApprovedCancelled and Delete. When the events are published the wait event is triggered and the workflow goes to the next steps where it does a recalculation, fires off a new workflow and ends the current one. This is working for all of the events except Delete. The Delete event is set up exactly the same as the rest, but somehow the workflow wait event is not triggered. It is happening with the Delete event for all the Infotypes I am waiting for.

Does anybody have any suggestions as to what may be the problem.

Thanks

Sandra

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Is the event getting triggered at the point when the Workflow is stuck in the Wait for event step. Please check. Also make sure you are waiting for the correct event of the correct Business Object i.e use the standard Business object instead of delegated one.

<b>Reward points if useful</b>

Former Member
0 Kudos

Arghadip/Martin thanks for your replies.

Yes, the delete event is being published. I am using the same object e.g BasicPay for the delete event that I am using for the other events - Approved, Created etc. that are working. The correlation and the wait for event steps are set up exactly the same way as they are for the events that are working. I find it curious that the delete event doesn't work for any of the infotypes. Why? Could it be that when a record is deleted the object no longer exists?

Any suggestions?

Thanks

Sandra

martin_nooteboom
Active Contributor
0 Kudos

Hi Sandra,

It could be like you say, but I agree it is strange. What you could try is create you own events in a delegated subtype of your standard BOR. You could raise these events in a FM like SAP does in FM /ISDFPS/FORCE_WF_T779W_SUP which you can check in SWEHR2.

Regards,

Martin

martin_nooteboom
Active Contributor
0 Kudos

Hi Sandra,

Are you sure the deleted event is triggered? Did you check this in the event trace?

Regards,

Martin