<html><body>
<p>Hi Zsolt,<br>
<br>
We also had the same problem the standard "Created" and Changed" events some how get triggered twice.<br>
What we did here was to create our own "Created" and Changed" events.<br>
We added these event to the change docuemtn transaction (SWEC)<br>
<br>
<img src="cid:10__=CDBBFBC8DF8B92E88f9e8a93df9@toyota.co.za" width="911" height="41" alt=""><br>
<br>
<br>
<img src="cid:20__=CDBBFBC8DF8B92E88f9e8a93df9@toyota.co.za" width="567" height="225" alt=""><br>
<br>
<img src="cid:30__=CDBBFBC8DF8B92E88f9e8a93df9@toyota.co.za" width="580" height="213" alt=""><br>
<br>
Regards<br>
<br>
Nat Govender<br>
Toyota South Africa<br>
IT - SAP Workflow Specialist<br>
Internal Ext. : 32645<br>
Direct Line : +27 031 910 2645<br>
Fax : +27 031 902 9633<br>
E-mail : ngovender4@toyota.co.za<br>
==================================================================<br>
Forgiveness is when one relinquishes the option to hurt the person that hurt you.<br>
Remember not to forget that which you do not need to know.<br>
==================================================================<br>
<img src="cid:40__=CDBBFBC8DF8B92E88f9e8a93df9@toyota.co.za" width="16" height="16" alt="Inactive hide details for "Partha Chatterjee" <pchatterjee@gmail.com>">"Partha Chatterjee" <pchatterjee@gmail.com><br>
<br>
<br>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td style="background-image:url(cid:50__=CDBBFBC8DF8B92E88f9e8a93df9@toyota.co.za); background-repeat: no-repeat; " width="40%">
<ul>
<ul>
<ul>
<ul><b><font size="2">"Partha Chatterjee" <pchatterjee@gmail.com></font></b><font size="2"> </font><br>
<font size="2">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size="2">2006/04/24 07:05 PM</font>
<table border="1">
<tr valign="top"><td width="168" bgcolor="#FFFFFF"><div align="center"><font size="2">Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></td></tr>
</table>
</ul>
</ul>
</ul>
</ul>
</td><td width="60%">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="1%"><img src="cid:60__=CDBBFBC8DF8B92E88f9e8a93df9@toyota.co.za" border="0" height="1" width="58" alt=""><br>
<div align="right"><font size="2">To</font></div></td><td width="100%"><img src="cid:60__=CDBBFBC8DF8B92E88f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""><br>
<font size="2">"SAP Workflow Users' Group" <sap-wug@mit.edu></font></td></tr>
<tr valign="top"><td width="1%"><img src="cid:60__=CDBBFBC8DF8B92E88f9e8a93df9@toyota.co.za" border="0" height="1" width="58" alt=""><br>
<div align="right"><font size="2">cc</font></div></td><td width="100%"><img src="cid:60__=CDBBFBC8DF8B92E88f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""><br>
</td></tr>
<tr valign="top"><td width="1%"><img src="cid:60__=CDBBFBC8DF8B92E88f9e8a93df9@toyota.co.za" border="0" height="1" width="58" alt=""><br>
<div align="right"><font size="2">Subject</font></div></td><td width="100%"><img src="cid:60__=CDBBFBC8DF8B92E88f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""><br>
<font size="2">Re: DMS - DRAW business object</font></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="58"><img src="cid:60__=CDBBFBC8DF8B92E88f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""></td><td width="336"><img src="cid:60__=CDBBFBC8DF8B92E88f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""></td></tr>
</table>
</td></tr>
</table>
<br>
<font size="4">Hi Zsolt,</font><br>
<font size="4"> </font><br>
<font size="4">Just curious -- did you check the workflow log check if there were different keys for each of the different events? or different workflows (sometimes regular workflows get kicked off with custom ones).</font><br>
<font size="4"> </font><br>
<font size="4">Regards,</font><br>
<font size="4">Partha<br>
<br>
</font><br>
<font size="4">On 4/24/06, </font><b><font size="4">Márton Zsolt</font></b><font size="4"> <</font><a href="mailto:Zsolt.Marton@t-systems.co.hu"><u><font size="4" color="#0000FF">Zsolt.Marton@t-systems.co.hu</font></u></a><font size="4">> wrote: </font>
<ul><font color="#0000FF" face="Arial">Hi all, </font><br>
<font color="#0000FF" face="Arial">We are in 4.7c. I've created an YDRAW subtype for my workflow, which is triggered when the document is changed with certain status. My problem is: the event is triggered twice in the same time and I couldnt find the reason. :( </font><br>
<font color="#0000FF" face="Arial">There is no mystery in my workflow: a simple document changed event with start condition.</font><br>
<font color="#0000FF" face="Arial">Does anybody met such a problem?</font><br>
<font color="#0000FF" face="Arial">thanks</font><br>
<font color="#0000FF" face="Arial">zsolt</font><br>
<font size="4"><br>
_______________________________________________<br>
SAP-WUG mailing list</font><u><font size="4" color="#0000FF"><br>
</font></u><a href="mailto:SAP-WUG@mit.edu"><u><font size="4" color="#0000FF">SAP-WUG@mit.edu</font></u></a><u><font size="4" color="#0000FF"><br>
</font></u><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank"><u><font size="4" color="#0000FF">http://mailman.mit.edu/mailman/listinfo/sap-wug</font></u></a><font size="4"><br>
<br>
</font></ul>
<tt>_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
</tt><tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a></tt><tt><br>
</tt><br>
</body></html>
<table><tr><td bgcolor=#ffffff><font color=#000000>This message is a privileged and private communication and may be read, copied and used only by <br>
the intended recipient(s). If you are not an intended recipient, please let us know by return email. <br>
Please then delete the message and do not disclose its contents to any person. Neither the sender nor <br>
Toyota South Africa Motors accepts any liability whatsoever as a result of the further dissemination <br>
of this message. Whilst all reasonable steps are taken to avoid corruption of data or information, <br>
we do not accept any liability should such corruption occur.<br>
</font></td></tr></table>