Race to the Finish Line

[LENAHAN Kari -TSDC]

Maybe limit trigger event with a check function module; for example
check the tables/logs to see if a workflow was already triggered for the
same object/key within a specific timeframe.
 
Please let me know if this suggestion is way off base.  I am workflow
admin/support only, and do not do any programming.
 
Thanks.

  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Alon Raskin
Sent: Wednesday, June 28, 2006 11:54 AM
To: SAP Workflow Users' Group
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
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060628/0a135cf1/attachment.htm