<br><font size=2 face="sans-serif">Wuggers,</font><br><br><font size=2 face="sans-serif">I have set up a new workflow for the
approval of parked invoices. Only invoices for specific types of
purchase orders (service) get parked for approval. It seems I have
a race condition that was not detected during user testing. The race
is between the start of the approval workflow and the scanned document
association with the SAP invoice. Some more details...</font><br><br><font size=2 face="sans-serif">1. When an invoice for a service PO
arrives, 2 processes are kicked off simultaneously:</font><br><font size=2 face="sans-serif">a) the invoice approval workflow</font><br><font size=2 face="sans-serif">b) the association of the scanned document
(archivelink) with the SAP invoice object.</font><br><font size=2 face="sans-serif">2. Sometimes the scanned document association
completes first, in which case an entry in the AdHoc objects container
item is made, and a hyperlink to the scanned document appears in the subesquent
work items in the invoice approval workflow. </font><br><font size=2 face="sans-serif">3. Other times the approval workflow
starts before the association completes and no scanned documents are found
-> no hyperlink in the work items.</font><br><font size=2 face="sans-serif">4. The approvers require the link to
the scanned document so they can review the vendor invoice before approval.</font><br><br><font size=2 face="sans-serif">I was wondering if anyone else has seen
a similar problem and what was done to correct. Some things I thought
about:</font><br><font size=2 face="sans-serif">1. Triggering the workflow off the BUS2089.ASSIGNED
event (this event is generated when an association is made between the
archivelink document and the SAP object) - this probably is not a good
idea as all invoices generate this event, but not all invoices go thru
the approval workflow.</font><br><font size=2 face="sans-serif">2. Including a wait step for the BUS2089.ASSIGNED
event - probably not a good idea as the workflow could hang in those cases
where this event is already generated when the approval workflow starts</font><br><font size=2 face="sans-serif">3. Create a loop to test the adhoc objects
container element for entries and loop until there is one - this would
probably work, but it seems a little, well..., kludgey.</font><br><br><font size=2 face="sans-serif">Can anyone give me some advice on correcting
this issue? Your help is appreciated.</font><br><br><font size=2 face="sans-serif"><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><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>