Quality notification workflow not starting

[TMNielsen]

Hi

We have an old workflow with workflow start using a triggering event BUS2078 event CREATED.

The trigger has a condition that the notification type must be different from ZL:

However the situation is that the workflow is started with a notification type Z4 or Z5 or Z6, but not if the type is Y1, Y2, etc. We actually doesn't use type ZL.

Earlier we wanted this behavior, but now we want to also start the workflow for Y1 and Y2, but I can't find where this "filter" is.

Any suggestions?

[TMNielsen · Accepted solution]

Hi all,

thanks for any input.

It turned out that the problem had nothing to do with start conditions in SWB_COND. The business object events in BUS2078 is raised via status changes on the quality notification object. This is configured in transaction BSVW, and it turns out, that the status that raise the Created event is not always created when the quality notification object is created.

Maybe this is ok or maybe not - but anyway, now that I know the problem, I can figure out how to work around it.

Best regards

Thomas

[former_member185167]

Hello,

"Earlier we wanted this behavior, but now we want to also start the workflow for Y1 and Y2, but I can't find where this "filter" is."

Go to PFTC of WS90000016 (and 19) and look for the Triggering Events tab. There you can see and change the condition. It's also in SWB_COND, as stated above.

regards

Rick

[former_member16044]

Hello Thomas,

Check whether there are any other conditions below "EVENT_OBJECT_TYPE". Use the downward arrow to scroll down. And if not any, and there's an issue with workflow trigger then make the workflow template as 'General Task' (if not any assigned possible agents).

PFTC -> WF no without WS -> F6-> Additional Data ->  agent assignment ->Maintain

Regards,

Rahul Kulkarni

[anjan_paul]

Hi,

  check in SWE2 for your workflow event linkage, is there any check Function Module used or not.

Also check in SWB_COND any condition maintained or not

[TMNielsen]

Hi

Thanks Anjan

There was an event linkage check function module:

If I test the event with SWUE the workflow is started. I tried to make event trace of the two scenarios

1. Event test from SWUE has the result Handler/Action SWW_WI_CREATE_VIA_EVENT

2. From the business transaction QM01 the result is No receiver entered

but actually I don't know how this knowledge can help me. Do you still think it is related to the check Function Module?

[suresh_subramanian2]

Hello Thomas !

              According to the screen shot taken from SWEL transaction, when the event CREATED is fired from SWUE transaction, two workflows are triggered.

              The workflow WS90000016 triggered successfully. The other workflow WS90000019 is not triggered. I suppose the first screen shot you've pasted in the beginning of the thread is related to WS90000019.

              What is the notification type of the notification number entered in business object key at SWUE transaction ? If the notification type of notification number entered as business object key at SWUE is not ZL , deactivate the workflow WS90000016 as it gets triggered even if the notification type is ZL.

Regards,

S.Suresh.

[anjan_paul]

Hi,

  I am seeing the event name you share usin SWEL are not same. One is Created , another is Inprocess.  So in your workflow what event is used as start event. Then check it usin SWUE

[TMNielsen]

Hi Anjan

Thaks for your help. My eyes didn't notice "In Process" event, so the "Created" event was never created from QM01.

I guess this is because of the SWB_2_CHECK_FB_START_COND_EVAL check function module.

I will now close this thread and try to figure what is the purpose of function module SWB_2_CHECK_FB_START_COND_EVAL.

Message was edited by: Thomas Madsen Nielsen I found other threads explaining that SWB_2_CHECK_FB_START_COND_EVAL is automatic insterted when a start condition is created in transaction SWB_COND.

[Jocelyn_Dart]

Correct - that is the standard check function module used to check the Start Condition.  In which case you might want to go and check the Start Conditions of that event in transaction SWB_COND to see what they are ... or indeed to see if they have been set up at all...