Workflow Triggered Even Start Condition not satisfied

[former_member1193316]

Dear SDNers,

I am facing a serious issue in PRD System.

My workflow has start events condition like Order Type = 'ZAB' and Profit_Block = 'B'. If this condition satisfies,then only my wokrflow has to be triggered.

But its not happened. For one SO, Order Type is 'ZAB' and Profit_block = ''. Even though my wokrflow triggered.

I checked at SWB_COND. Its perfect. Even at SWE2 also I checked.

I have seen the trace(SWEL). Here FM SWB_2_CHECK_FB_START_COND_EVAL didnt not throw any error and reported "Receiver started correctly".

Then how come my workflow triggered even condition not satisfied.

Please help me to solve this issue.

Thanks in advance,

Regards,

Venkat

[former_member185167 · Accepted solution]

Hello,

If it only happened once then I wouldn't worry too much about it. It is annoying though.

"Order Type is 'ZAB' and Profit_block = '' "

Can you be sure that one or both didn't change after the workflow was triggered?

Try to replicate in Test with the exact same data. If you can't replicate it then it's very difficult to fix.

Some people even say that if a problem can't be replicated then it's not a problem!

regards

Rick Bakker

hanabi technology

[suresh_subramanian2 · Accepted solution]

Hello !

What is the value stored for Profit_block in workflow log ?

Is it 'B' or '' or some other value ?

When it is not 'B', still workflow triggers, use check function module as Sanju suggested.

Regards,

S.Suresh.

[Former Member]

Hi,

If the issue still exists then you can use the check function module. This will always work.

For more details please see below link.

http://www.genipole.com/tutorials/2-using-check-function-module-in-workflow/

Thanks and regards,

SNJY

[former_member1193316]

Dear Sanju,

Thanks for the function module. Byt what might be the reason for the exiting error?

What I suppose to give explanation to my client?

Thanks,

Venkat

[Former Member]

In that case please refresh the buffer with transaction SWU_OBUF and test it again.

[Former Member]

Hi venkat,

I too faced this kind of issue in PO related workflows in my system.

You have to convince your client by informing them like, "we are quite unsure of how it has happened. We have replicated in our test system and there is no issue over there.

We will monitor it in future and try to trace the issue if we get it again".

If you get it again(hopefully not), compare this order with the one you will get.

This is the only way to do in production system.

Cheers,

Raja.D

[former_member1193316]

Dear Rick,

I have checked it,at SWB_COND its correctly configured. I have tested it in QAS and DEV Systems also. Its working fine over there.

Even in PRD also, other SO were not triggered if the condition not satisfied. But only why one workflow failed to check the condition.

Thanks,

Venkat

[former_member185167]

Hello,

I would check SWB_COND again to make sure the condition hasn't been deactivated. Does it work in the Test system? Look for any differences.

Another possibility is that these values aren't available when the workflow starts. It's hard to tell if that is the case in the workflow log after the fact. If it is the case then you could have the same test at the start of the workflow as well or instead.

First see if you can replicate this problem in Test.

regards

Rick Bakker

hanabi technology