cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Workflow - Start Condition Failure

Former Member
0 Likes
2,497

Hi All,

I am trying to put a start condition on a workflow of mine. I just want to check if an order type = PM01 or PM03 and not 0010.

I have my start condition set-up but every time I run it I get this error in my event log:

Operator 'EQ': The value of the left operand cannot be determined


  (  " PM01 or PM03 
     &Maintenance order.Order type& = PM01 
     or    &Maintenance order.Order type& = PM03 
  ) " PM01 or PM03 
  and    &Maintenance order.Plant& u2260 0010 

The funny thing is if I go to SWUE and kick off the even it passes the start condition fine. So therefore I think there is an issue with my container being passed to the start condition.

Is there anyway I can fix this?

Many Thanks For Any Help Provided,

Colm

View Entire Topic
Former Member
0 Likes

I have been doing extensive debugging and it looks like the problem is the way this event is kicked off. The event is being triggered by config set up in the BSVW transaction.

Has anyone experience in calling events from this config?

surjith_kumar
Active Contributor
0 Likes

Hi,

In the BSVW, the mapping of the event is not correct. Check the setting once again.

Refer the 5 in this [blog|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/7219] [original link is broken] [original link is broken] [original link is broken];.

Also Refer the [Link|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e038cc2d-0cde-2a10-e28e-f50025578112].

Regards,

Surjith

Former Member
0 Likes

Surjith,

I found your documentation very useful although there didn't seem to be any information in it regarding why a container might not be populated when calling these events using BSVW?

Does anyone know if it is possible to debug a BSVW event trigger to make sure that the container is populated correctly when triggering the event?

Many Thanks for all your help,

Colm