Duplicate Workflows when a PO is changed.

[Catherine Schumann]

Hi Michael,
 
We have recently solved this issue at our site.  At first we had a check st=
ep, which looked to see whether another workflow had started in the last 30=
 seconds, with the same PO number, and if so, to terminate, but this just l=
ed to some pretty unpredictable behaviour - it would work most of the time =
but then occasionally both workflows would die.  Not good - so we have drop=
ped that check.
 
What I have done now is to work with the Event function module that you can=
 attach to a change doc/object/event combination in SWEC.  (needs OSS note =
576834 to get it working) Basically, I do a check in the function to see wh=
ether any of the fields that are relevant to ReleaseStepCreated (FRGXX) are=
 passed in the change documents, and if so, don't call the Changed event. (=
ReleaseStepCreated and Changed are both triggering events, so need to make =
sure that exactly one of them is called.) And, for when the PO gets created=
 and you also get 2 events, just exclude the key ekko field as well.
 
It has gone through some good testing and is 100% consistent now, so that i=
s what we are sticking with.  Hope that this might help your problem.
 
Catherine
 
-----Original Message-----
From: Michael Payoe [mailto:Michael.Payoe at health.gov.au]
Sent: 30 May 2003 05:11
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Duplicate Workflows when a PO is changed.
 
 
Hi all,
 
I have a situation where duplicate workflow are created when the PO is chan=
ged.
This happens when the change causes the release strategy to change or a new=
 line
item is added to the workflow after it has been approved.
 
I have checked the Event Linkage which shows 2 entries for Object type BUS2=
012
for 'CHANGE' with the 2 receiver types being EVENTITEM and the WF Id.
 
I have looked at Tcode SWI1 and it shows that the WF is kicked off for both
trigger events, ie Changed and the ReleasestepCreated.
 
Any assistance as to where I could go from this point will be appreciated.
 
Many Thanks
 
Michael Payoe
 
 
***************************************************************************=
*****
"Important: This transmission is intended only for the use of the addressee=
 and
may contain confidential or legally privileged information.
 
If you are not the intended recipient, you are notified that any use or
dissemination of this communication is strictly prohibited.  If you receive=
 this
transmission in error please notify the author immediately and delete all c=
opies
of this transmission."
***************************************************************************=
*****
 
 
BBCi at http://www.bbc.co.uk/
 
This e-mail (and any attachments) is confidential and may contain=20
personal views which are not the views of the BBC unless specifically=20
stated.
If you have received it in error, please delete it from your system, do=20
not use, copy or disclose the information in any way nor act in=20
reliance on it and notify the sender immediately. Please note that the=20
BBC monitors e-mails sent or received. Further communication will=20
signify your consent to this.