AW: Terminating event changes status to Executed not Completed

[Schmidinger, Heinz (Oerlikon TR)]

Hi David,

 

many months ago I dealed with the same problem. I could discuss it with SAP  Development directly and they told me that they have created a "hierarchy":

If commitment is requested, it has highest priority and the task can not be ended by a receiving event. In words of the development it is not a bug it is a planned feature.

 

For my implementations I have included "by-pass"-forks where an event-receiver-item is waiting in a parallel fork to end the dialog-item.

 

Hope it helps.

 

Greetings

Heinz

_______________________________________

Heinz Schmidinger 
Certified Senior Application Consultant 

Oerlikon Solar AG, Trübbach

Hauptstrasse 1a

9477 Trübbach

Schweiz

P +41 58 356 8626 
F +41 58 356 8826 
heinz.schmidinger at oerlikon.com 

www.oerlikon.com/solar 

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please notify the sender immediately and destroy this e-mail. Unauthorised copying, disclosure and distribution of the material in this e-mail are strictly prohibited.

 

Diese E-Mail enthaelt vertrauliche und/oder geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet.

Please consider our environment before printing this e-mail.

Bitte denken Sie an unsere Umwelt, bevor Sie diese E-Mail ausdrucken.

 

________________________________

Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] Im Auftrag von David Baitman
Gesendet: Freitag, 27. Februar 2009 15:41
An: sap-wug at mit.edu
Betreff: Terminating event changes status to Executed not Completed

 

Any ideas are welcome, otherwise I'll share what I find.

 

ECC 6.0 running HR.  Basis release is 7.0 (SAPKB70014).  

 

I have a workflow template that triggers a dialog synchronous task.  The task has the "confirm end of processing" option selected.  A terminating event is also configured.  However, when the terminating event occurs, the work item changes to status "Executed" instead of "Completed."  (The background status is actually "Committed").

 

I have turned on the event trace, and the correct instance linkage receiver is found.  

 

The interesting part is that I run SWUE to manually create the event and if I choose the "Trigger receiver FM synchr" option, the status correctly changes from Ready to Completed.  However, if I leave that option unchecked the work item changes from Ready to Executed.  The same is true if I execute (via SE37) SAP_WAPI_WORKITEM_COMPLETE...asynchronous (Ready to Executed), synchronous (Ready to Completed).  

 

According to the online help <http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c5/e4b590453d11d189430000e829fbbd/frameset.htm> , the work item should be set to complete regardless of the "confirm end of processing" flag so I can only assume this is a bug...or I've missed something very obvious.

 

It was suggested to me by the same kind soul who told me about this user group that I try putting the terminating event in a parallel branch in the flow.  If that doesn't help, I will create a Z receiver function that calls SAP_WAPI_WORKITEM_COMPLETE and if the NEW_STATUS is COMMITTED, I'll call it again.  Testing has shown this to work.

 

In any case, I'll let the group know what I find.  If you have any other advice...please let me know.  

 

Finally...this is my first posting on this user group.  If I didn't follow proper etiquette please let me know...I tried to follow the advice of the wiki.  

 

Regards,

 

David Baitman

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090302/4b38985a/attachment.htm