<br><font size=2 face="sans-serif">Nope, no locking problem....<br>
</font>
<br><font size=2 face="sans-serif">Ah yes.. we have the </font><font size=2 face="Courier New">RSWWERRE</font><font size=2 face="sans-serif"> job running...<br>
<br>
</font><font size=1 face="Comic Sans MS">Met vriendelijke groeten,<br>
Salutations,<br>
Best regards,<br>
Mit freundlichen Grüssen,<br>
Atentos saludos, </font>
<p>
<table border=4>
<tr>
<td><img src=cid:_1_021C000059D80035AD03C1257031>
<td><font size=1 face="Comic Sans MS">Koenraad Janssens<br>
Sidmar N.V. - ISM<br>
Leverage Team - Programmer <br>
Tel: +32 9 347 35 76<br>
email: </font><a href=mailto:koenraad.Janssens@sidmar.arcelor.com><font size=1 color=blue face="Comic Sans MS"><u>koenraad.janssens@sidmar.arcelor.com</u></font></a><font size=1 face="Comic Sans MS"> </font></table>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>wug.replies@workflowconnections.com</b></font>
<br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">01/07/2005 11:09</font>
<br><font size=1 face="sans-serif">Please respond to sap-wug</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To: sap-wug@mit.edu</font>
<br><font size=1 face="sans-serif"> cc: </font>
<br><font size=1 face="sans-serif"> Subject: Re: WF's not totally completed</font></table>
<br>
<br>
<br><font size=2 face="Courier New">That is the type of setup that could produce these orphaned items. Can you<br>
check whether anyone was doing anything to the task at the time the WF<br>
completes?<br>
<br>
Oh, and the error monitor is RSWWERRE, set up via SWWD :)<br>
<br>
Cheers<br>
Mike<br>
<br>
koenraad.janssens@sidmar.arcelor.com wrote:<br>
> Hi<br>
><br>
> Well you could look at it as the wf has two branches.... one completes<br>
> and closes the worklow.. and the other (a kind of monitoring task) just<br>
> remains in the user's inbox. It was like that since april so.... I<br>
> think I'll just have to wait till it happens again and then post a request<br>
> to sap....<br>
><br>
> It isn't a mayor problem at all.. but it's hard to communicate system<br>
> "glitches" like this to your users.<br>
><br>
> Met vriendelijke groeten,<br>
> Salutations,<br>
> Best regards,<br>
> Mit freundlichen Grüssen,<br>
> Atentos saludos,<br>
><br>
><br>
> Koenraad Janssens<br>
> Sidmar N.V. - ISM<br>
> Leverage Team - Programmer<br>
> Tel: +32 9 347 35 76<br>
> email: koenraad.janssens@sidmar.arcelor.com<br>
><br>
><br>
><br>
><br>
><br>
> wug.replies@workflowconnections.com<br>
> Sent by: sap-wug-bounces@mit.edu<br>
> 01/07/2005 09:57<br>
> Please respond to sap-wug<br>
><br>
><br>
> To: sap-wug@mit.edu<br>
> cc:<br>
> Subject: Re: WF's not totally completed<br>
><br>
><br>
> Hi Koenraad,<br>
> How are these stray WF's completed? Certain locking conditions can cause a<br>
> WF to complete but an item still remains in a user's inbox.<br>
><br>
> In those cases the error monitoring job should pick it up and the forlorn<br>
> item eventually gets cancelled within the next 20 minutes or so. I had an<br>
> interesting discussion with OSS about this one, in some scenarios it's a<br>
> bug and in others it's the way you'd expect it to work.<br>
><br>
> Cheers<br>
> Mike<br>
><br>
> koenraad.janssens@sidmar.arcelor.com wrote:<br>
>> Hello all<br>
>><br>
>> We sometimes have workflows whom are completed... but some subsequent<br>
>> tasks stay present in the users inbox.<br>
>> Anyone an idea how to counter this? (so the closing down of the<br>
> workflow<br>
>> isn't 100% foulproof)<br>
>><br>
>> Met vriendelijke groeten,<br>
>> Salutations,<br>
>> Best regards,<br>
>> Mit freundlichen Grüssen,<br>
>> Atentos saludos,<br>
>><br>
>><br>
>> Koenraad Janssens<br>
>> Sidmar N.V. - ISM<br>
>> Leverage Team - Programmer<br>
>> Tel: +32 9 347 35 76<br>
>> email: koenraad.janssens@sidmar.arcelor.com<br>
>><br>
>><br>
>><br>
> ***********************************************************************************<br>
>> This message should only be read by those persons to whom it is<br>
>> addressed, and may contain confidential information, the disclosure<br>
>> of which is prohibited. This message is not intended to create rights<br>
>> or obligations without subsequent written confirmation of its contents.<br>
>> If you have received this message in error, please notify us immediately<br>
>><br>
> ***********************************************************************************<br>
>><br>
>> _______________________________________________<br>
>> SAP-WUG mailing list<br>
>> SAP-WUG@mit.edu<br>
>> http://mailman.mit.edu/mailman/listinfo/sap-wug</font>
<br><font size=2 face="Courier New">>><br>
><br>
><br>
> Mike Pokraka<br>
> Senior Consultant<br>
> Workflow Connections Ltd.<br>
> Mobile: +44 (0)7786 910 855<br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
><br>
><br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
><br>
<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
</font>
<br>
<br>