<br><font size=2 face="sans-serif">Mike,</font><br><br><font size=2 face="sans-serif">Oooh, that sounds like a good idea!
Would you mind elaborating a little more on the "conditions
job" (its name, a program name, something...)? I guess this
is something I should look for in SM37, just not sure what to look for...</font><br><br><font size=2 face="sans-serif">I am using task conditions in this workflow,
but these are "complete work item" conditions that will cause
a step to be bypassed (completed) if that step is not relevant for this
instance of the WF (for example, we don't need higher levels of approval
if the dollar value of the invoice isn't that big...).</font><br><br><font size=2 face="sans-serif">Thanks for your help.<br></font><font size=4 color=#808000><b> </b></font><p><font size=4 color=#808000><b>Michael McLey</b></font><font size=3 color=#808000><b></b><br>MBUSI - IT Parts & Administration </font><font size=2 color=#808000><br>Mercedes-Benz US International, Inc.</font><font size=3 color=#808000></font><font size=2 color=#808000><br>1 Mercedes Drive</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>Vance, AL 35490</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>PHONE: (205) 462 - 5239</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>EMAIL: michael.mcley@daimler.com</font><font size=3 color=#808000>
</font><br><br><br><table width=100%><tr valign=top><td width=40%><font size=1 face="sans-serif"><b>wug@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">11/11/2010 05:18 AM</font><table border><tr valign=top><td bgcolor=white><div align=center><font size=1 face="sans-serif">Please respond to<br>sap-wug@mit.edu</font></div></table><br><td width=59%><table width=100%><tr valign=top><td><div align=right><font size=1 face="sans-serif">To</font></div><td><font size=1 face="sans-serif">sap-wug@mit.edu</font><tr valign=top><td><div align=right><font size=1 face="sans-serif">cc</font></div><td><tr valign=top><td><div align=right><font size=1 face="sans-serif">Subject</font></div><td><font size=1 face="sans-serif">Re: Race condition in a workflow</font></table><br><table><tr valign=top><td><td></table><br></table><br><br><br><tt><font size=2>Joe's suggestion is good, but if your archivelink
WF is too generic then a<br>less kludgey version of your option 3 is to use a step condition to ensure<br>adhoc objects exist.<br>If you haven't used them before: Conditions tab on the first step that<br>uses adhoc objects; and make sure the conditions job is running.<br><br>Cheers,<br>Mike<br><br><br>On Wed, November 10, 2010 2:25 pm, michael.mcley@daimler.com wrote:<br>> Wuggers,<br>><br>> I have set up a new workflow for the approval of parked invoices.
Only<br>> invoices for specific types of purchase orders (service) get parked
for<br>> approval. It seems I have a race condition that was not detected
during<br>> user testing. The race is between the start of the approval
workflow and<br>> the scanned document association with the SAP invoice. Some
more<br>> details...<br>><br>> 1. When an invoice for a service PO arrives, 2 processes are kicked
off<br>> simultaneously:<br>> a) the invoice approval workflow<br>> b) the association of the scanned document (archivelink) with the
SAP<br>> invoice object.<br>> 2. Sometimes the scanned document association completes first, in
which<br>> case an entry in the AdHoc objects container item is made, and a hyperlink<br>> to the scanned document appears in the subesquent work items in the<br>> invoice approval workflow.<br>> 3. Other times the approval workflow starts before the association<br>> completes and no scanned documents are found -> no hyperlink in
the work<br>> items.<br>> 4. The approvers require the link to the scanned document so they
can<br>> review the vendor invoice before approval.<br>><br>> I was wondering if anyone else has seen a similar problem and what
was<br>> done to correct. Some things I thought about:<br>> 1. Triggering the workflow off the BUS2089.ASSIGNED event (this event
is<br>> generated when an association is made between the archivelink document
and<br>> the SAP object) - this probably is not a good idea as all invoices<br>> generate this event, but not all invoices go thru the approval workflow.<br>> 2. Including a wait step for the BUS2089.ASSIGNED event - probably
not a<br>> good idea as the workflow could hang in those cases where this event
is<br>> already generated when the approval workflow starts<br>> 3. Create a loop to test the adhoc objects container element for entries<br>> and loop until there is one - this would probably work, but it seems
a<br>> little, well..., kludgey.<br>><br>> Can anyone give me some advice on correcting this issue? Your
help is<br>> appreciated.<br>><br>><br>><br>> Michael McLey<br>> MBUSI - IT Parts & Administration<br>> Mercedes-Benz US International, Inc.<br>> 1 Mercedes Drive<br>> Vance, AL 35490<br>> PHONE: (205) 462 - 5239<br>> EMAIL: michael.mcley@daimler.com<br>><br>> If you are not the intended addressee, please inform us immediately
that<br>> you have received this e-mail in error, and delete it. We thank you
for<br>> your cooperation. _______________________________________________<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></tt><br><font face="sans-serif"><font face="sans-serif, Arial, Helvetica" size="-1" color="#808080"><br>If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation.
<br></br>
</font></font>