ECC 6.0: Issues With Header Event to cancel Workflow

[Morris, Eddie]

Hi Ramki,

Do you raise the RELEASED event via custom code? Do you use
SWE_EVENT_CREATE?

If you raise the event via SWE_EVENT_CREATE please make note that the
Function module SWE_EVENT_CREATE should not be called with flag
START_RECFB_SYNCHRON = 'X'.


Regards,
Eddie








-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Ramki Maley
Sent: 20 February 20, 2009 3:04
To: SAP Workflow Users' Group
Subject: ECC 6.0: Issues With Header Event to cancel Workflow

System ECC 6.0 SAPKA70015 / SAPKB70015

This is a new implementation that recently went live. I have a PO 
approval Workflow in which the last step is a Synchronous Background 
Task that releases the PO after the necessary approval steps. Please 
note that the approval step is not in any Fork and is the very last 
step. I have defined the 'Released' event to cancel the WF at the header

level in the WF Builder (SWDD) in order to cater to approval outside 
workflow. When the Released event is created by WF-BATCH in the BG step,

the WF is complete by the time the system tries to process the 
terminating event,. However I noticed that the Released event in some 
cases is being flagged as in error and put in event queue. I switched on

the trace for the event and monitored it. The event trace sometimes 
shows 'No Receiver Entered' for some instances (which is perfectly fine)

and Error for the rest. The message does not show any locking conflicts.

  Redelivering the event creates the same error message (No 
configuration for workflow WS900XXX version n). Please see the attached 
picture for example entries from WF Log and Event Log.

Any pointers in stopping the Events being written to the queue would be 
greatly apreciated.

Regards,
Ramki.