<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">The triggering is absolutely standard
( with OAWD transaction )</font>
<br><font size=2 face="sans-serif">My suggestion is same as you have, </font>
<br><font size=2 face="sans-serif">but the early archiving and the workflow
start is controlled by OAWD ...</font>
<br>
<br><font size=2 face="sans-serif">Regards:</font>
<br>
<br><font size=2 face="sans-serif"> Árpád</font>
<br>
<br>
<br><font size=2 face="sans-serif">Vincze Árpád<br>
itelligence Hungary Kft.<br>
Váci út 141<br>
H-1138 Budapest<br>
<br>
Tel: (+36) 1 / 452 38-22<br>
Mob: (+36) 20 / 9533-578<br>
Fax: (+36) 1 / 452 38-39<br>
Arpad.Vincze@itelligence.hu<br>
http://www.itelligence.hu</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Michael Pokraka <workflow@quirky.me.uk></b>
</font>
<br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">2005.02.09 11:38</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">"SAP Workflow Users'
Group" <sap-wug@mit.edu></font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">Re: Very first batch step
with ERROR state</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Hi, <br>
Sounds like a system update issue - the WF starts before the DB update
is<br>
complete. How are you triggering the flow? <br>
Cheers<br>
Mike<br>
<br>
--- Arpad.Vincze@itelligence.hu wrote:<br>
<br>
> Hello,<br>
> <br>
> (Vers. 6.2) <br>
> I have an own developed SAP ArchiveLink workflow having storing with
<br>
> subsequent entry <br>
> (or formerly called early archiving ) attribute.<br>
> <br>
> This workflow very first step is a batch one which assigns to the
document <br>
> the next free number from a SAP standard number range.<br>
> <br>
> Sometimes this batch step goes to error (approx.1 %) with <br>
> OA12 (SAP ArchiveLink: No stored document found ) . <br>
> <br>
> If this erroneous workflow is restarted, it runs without any problem.<br>
> <br>
> Have you ever such kind of problem?<br>
> Waiting for your answer:<br>
> <br>
> Árpád<br>
> <br>
> Vincze Árpád<br>
> itelligence Hungary Kft.<br>
> Váci út 141<br>
> H-1138 Budapest<br>
> <br>
> Tel: (+36) 1 / 452 38-22<br>
> Mob: (+36) 20 / 9533-578<br>
> Fax: (+36) 1 / 452 38-39<br>
> Arpad.Vincze@itelligence.hu<br>
> http://www.itelligence.hu> _______________________________________________<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>
</tt></font>
<br>