<div>G'day Vijay,</div>
<div> </div>
<div>You could try a few different things.</div>
<div> </div>
<div>An oldy and not necessarily a goody is a 1 minute delay via the requested start option on your background check.</div>
<div> </div>
<div>Depending on your release you could consider using the 'complete work item condition' on the first step.</div>
<div> </div>
<div>Have fun,</div>
<div>Mark<br><br> </div>
<div><span class="gmail_quote">On 12/20/05, <b class="gmail_sendername">vijay srikanth</b> <<a href="mailto:vijay_d15@hotmail.com">vijay_d15@hotmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>I am developing a workflow to ensure sales order completion. There is a step<br>that takes the user to the sales order incompletion log. Then there is
<br>background method to check if he has completed the sales order fully. If he<br>does not complete it then the work item is recalled in his inbox. However if<br>he completes it, then the work item should not appear again. But the
<br>background job I think occurs before the changes to the sales order is<br>committed. It again returns a container value saying that the sales order is<br>incomplete, even though It is not. How do I avoid this problem.
<br><br>Regards,<br>Vijay<br><br><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br></blockquote></div><br>