Race to the Finish Line

[Gunawan_Hasim@app.co.id]

How about put checking of document (in this case Business Partner) locking 
record on each workflow ?
So if a workflow detect the BP is being updated by other workflow then the 
workflow will loop until BP is released.
Be careful on endless loop here.








"Alon Raskin" <araskin at 3i-consulting.com> 
Others, 06/28/2006 11:54 AM AST
Sent by: sap-wug-bounces at mit.edu
 
        To:     "SAP Workflow Users' Group" <sap-wug at mit.edu>
        cc: 
        Subject:        Race to the Finish Line

Hi Everyone,
 
Problem: I have multiple instances of the same workflow that are triggered 
at the same time. Of course, the first thing that happens is that each 
instance tries to update the Business Partner (the same one) and this 
results in a large number of temporary application errors. This is no big 
deal but if I have 50 instances of the WF for the same Business Partner 
then I am going to get a lot of errored workflows.
 
Possible (sucky) solution: One obvious thing I can do to alleviate this 
problem is to put in a random wait step and this will hopefully reduce (or 
remove) the number of errored workflows. I dont like this solution as I 
hate putting in random wait steps unless there is a business need for 
this. 
 
Can anyone can suggest a better solution?
 
Look forward to your input.
 
Alon Raskin
e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com> 
p: +1 207 409 4983
f:  +1 806 403 4983
 
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug



,"
DISCLAIMER :

The information contained in this communication (including any attachments) is privileged and confidential, and may be legally exempt from disclosure under applicable law. It is intended only for the specific purpose of being used by the individual or entity to whom it is addressed. If you are not the addressee indicated in this message (or are responsible for delivery of the message to such person), you must not disclose, disseminate, distribute, deliver, copy, circulate, rely on or use any of the information contained in this transmission.

We apologize if you have received this communication in error; kindly inform the sender accordingly. Please also ensure that this original message and any record of it is permanently deleted from your computer system. We do not give or endorse any opinions, conclusions and other information in this message that do not relate to our official business.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060629/afd527bf/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/octet-stream
Size: 4540 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20060629/afd527bf/attachment.obj