We have had a problem with the conditions via SWB_COND. So we had to change the conditions and remove a parameter. But after that removal the Workflow won't start. We get the error shown below in the message of event trace. But manually triggered event via SWUE workes fine and acts acording to the updated SWB_COND.
I use SWB_COND to set conditons for a WF to start. Parameter VAR must not contain 'X'.
Operator: VAR NE 'X'
When we use FM SWE_EVENT_CREATE_FOR_UPD_TASK (see below) trigger event
(containter totally empty : parameter VAR is not set to anything)
...the event is triggered BUT with:
Action: "Check FM ends with exception"
Message: Operator 'NE': The value of the left operand cannot be determined
CALL FUNCTION 'SWE_EVENT_CREATE_FOR_UPD_TASK' EXPORTING event = gc_ev_pr_created objtype = gc_obj_bkpf objkey = lv_obj_key TABLES event_container = lt_container. COMMIT WORK.
When using SWUE to trigger the event with SAME object key and same parameters (parameter VAR is not filled) - Workflow is triggered OK
So I have a workflow that won't trigger when the Event is triggered via a FM caused by an unfamiliar Operator in the condition. (in Event Trace all is RED)
BUT the same WILL trigger if I call the SWUE and trigger the Event myself. In the Event Trace all is GREEN then...
Anyone have any ideas....
I've checked the OSS / the web / this forum ... but couldn't find anything that lookes the same... Please help
Is there a buffert or something that need to be updated in order for the FM SWE_EVENT_CREATE_FOR_UPD_TASK to be aware of the Conditions...
The event linkage contains:
Receiver FM = SWW_WI_CREATE_VIA_EVENT
Check FM = SWB_2_CHECK_FB_START_COND_EVAL