<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1491" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 70.85pt 70.85pt 70.85pt 70.85pt; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: blue; TEXT-DECORATION: underline
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: "Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.E-mailStijl18 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=NL vLink=blue link=blue>
<DIV><SPAN class=349082711-06062005><FONT face=Arial color=#0000ff size=2>and to
add to Jocelyn's last thougths... </FONT></SPAN></DIV>
<DIV><SPAN class=349082711-06062005><FONT face=Arial color=#0000ff size=2>I
prefer creating a virtual attribute to coding a method when it fits in
the OO scheme of things. Virtual attributes are much easier to
test (SWO1), the result is available directly in texts and workflow forks and
conditions (and of course start conditions) without passing through container
variables, and the coding is centralized around the business object and not in
umpteen other workbench objects. Its just good OO
design.</FONT></SPAN></DIV>
<DIV><SPAN class=349082711-06062005><FONT face=Arial color=#0000ff
size=2>Regards</FONT></SPAN></DIV>
<DIV><SPAN class=349082711-06062005><FONT face=Arial color=#0000ff
size=2>Nate</FONT></SPAN></DIV>
<DIV><SPAN class=349082711-06062005></SPAN><SPAN
class=349082711-06062005></SPAN><FONT face=Tahoma size=2>-----Ursprüngliche
Nachricht-----<BR><B>Von:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu]<B>Im Auftrag von </B>Dart,
Jocelyn<BR><B>Gesendet:</B> Montag, 6. Juni 2005 10:00<BR><B>An:</B> SAP
Workflow Users' Group<BR><B>Betreff:</B> RE: Cancelling the previous
workitem<BR><BR></DIV></FONT>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV dir=ltr align=left><SPAN class=844425007-06062005><FONT face=Arial
color=#0000ff size=2>Hi Kjetil, </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=844425007-06062005><FONT face=Arial
color=#0000ff size=2>I would always extend a standard object by delegation in
such a case, rather can create a check function module. Like I said it's
easier to test whether your object will meet the condition or not this
way. If you had to set up an attribute per workflow that might be a pain
- but I would have thought in most cases you are just looking for any active
workflows for that object. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=844425007-06062005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=844425007-06062005><FONT face=Arial
color=#0000ff size=2>The benefits of using a start condition I stated
previously - it's not simply that they are all in the one place, it's because
any other *NON-WORKFLOW* business analyst can read, understand, and even
maintain the start condition quickly and easily without bugging yours truly
all over again. Plus you can turn them on and off at the flick of a
button. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=844425007-06062005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=844425007-06062005><FONT face=Arial
color=#0000ff size=2>We've been using start conditions in EBP for a while now
and they just save heaps of time, a lot of code rewrites on
changing business requirements, and many many otherwise very tedious
explanations. <SPAN class=844425007-06062005><FONT face=Arial
color=#0000ff size=2>They handle currency-specific amounts without drama
and t</FONT></SPAN>hey even have their own test mechanism in situ for the
pedantic. </FONT></SPAN></DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><FONT face=Arial size=1>Regards,</FONT></SPAN> <BR><SPAN
lang=en-us><B><FONT face=Arial color=#000080 size=1>Jocelyn
Dart</FONT></B></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>Senior Consultant</FONT></SPAN> <BR><SPAN lang=en-us><B><FONT
face=Arial color=#808080 size=1>SAP Australia Pty Ltd.</FONT></B></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial color=#808080 size=1>Level 1/168 Walker
St.</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>North Sydney </FONT></SPAN><BR><SPAN lang=en-us><FONT face=Arial
color=#808080 size=1>NSW, 2060</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>Australia</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>T +61 412 390
267</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>M + 61 412 390 267</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>E
jocelyn.dart@sap.com</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial
color=#808080 size=1><A
href="http://www.sap.com/">http://www.sap.com</A></FONT></SPAN> </P>
<P><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>*****************************************************************************************</FONT></SPAN>
<BR><SPAN lang=en-au><FONT face="Times New Roman" color=#800000 size=2>The
information contained in or attached to this electronic transmission is
confidential and may be legally privileged. It is intended only for the person
or entity to which it is addressed. If you are not the intended recipient, you
are hereby notified that any distribution, copying, review, retransmission,
dissemination or other use of this electronic transmission or the information
contained in it is strictly prohibited. If you have received this electronic
transmission in error, please immediately contact the sender to arrange for
the return of the original documents.</FONT> </SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#800000
size=2>Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.</FONT></SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#800000 size=2>Any
views expressed in this electronic transmission are those of the individual
sender, except where the message states otherwise and the sender is authorized
to state them to be the views of SAP AG or any of its subsidiaries. SAP AG,
its subsidiaries, and their directors, officers and employees make no
representation nor accept any liability for the accuracy or completeness of
the views or information contained herein. Please be aware that the furnishing
of any pricing information/ business proposal herein is indicative only, is
subject to change and shall not be construed as an offer or as constituting a
binding agreement on the part of SAP AG or any of its subsidiaries to enter
into any relationship, unless otherwise expressly stated. </FONT></SPAN></P>
<P><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>*****************************************************************************************</FONT></SPAN><SPAN
lang=en-au></SPAN> </P>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Kjetil
Kilhavn<BR><B>Sent:</B> Monday, 06 June 2005 3:24 PM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> RE: Cancelling the previous
workitem<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=174541605-06062005><FONT face=Arial
color=#0000ff size=2>Ahh, yes of course. I have added such a virtual
attribute myself but didn't use it in a start condition. It is very easy using
the WAPI functions). But since that is the answer I assume it isn't possible
with a standard object.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=174541605-06062005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=174541605-06062005><FONT face=Arial
color=#0000ff size=2>There is of course a value in seeing all the start
conditions in one place, but otherwise I don't see any particular advantage
compared to a check function - in particular if you haven't already delegated
your object type, and you would have to create one attribute per workflow
or task you need to distinguish between.</FONT></SPAN></DIV>
<DIV align=left><FONT face=Arial size=2>-- </FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Kjetil Kilhavn, Statoil KTJ IT
BKS</FONT></DIV>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Dart,
Jocelyn<BR><B>Sent:</B> 6. juni 2005 02:33<BR><B>To:</B> SAP Workflow Users'
Group<BR><B>Subject:</B> RE: Cancelling the previous
workitem<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=045412700-06062005><FONT face=Arial
color=#0000ff size=2>Hi Kjetil, </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=045412700-06062005><FONT face=Arial
color=#0000ff size=2>Sure you can - all you need to do is create a virtual
attribute that returns the number of currently active workflow instances for
your object - an easy find with the WAPIs - and then your condition is "number
of active instances" must be 0 - i.e. don't start if anything else is already
out there.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=045412700-06062005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=045412700-06062005><FONT face=Arial
color=#0000ff size=2>Ok so you need to add a virtual attribute, but that's not
difficult, and it makes it easier for testing as you can see the current value
in swo1 test or in the container in the workflow logs. </FONT></SPAN></DIV>
<DIV> </DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><FONT face=Arial size=1>Regards,</FONT></SPAN> <BR><SPAN
lang=en-us><B><FONT face=Arial color=#000080 size=1>Jocelyn
Dart</FONT></B></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>Senior Consultant</FONT></SPAN> <BR><SPAN lang=en-us><B><FONT
face=Arial color=#808080 size=1>SAP Australia Pty Ltd.</FONT></B></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial color=#808080 size=1>Level 1/168 Walker
St.</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>North Sydney </FONT></SPAN><BR><SPAN lang=en-us><FONT face=Arial
color=#808080 size=1>NSW, 2060</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>Australia</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>T +61 412 390
267</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>M + 61 412 390 267</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>E
jocelyn.dart@sap.com</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial
color=#808080 size=1><A
href="http://www.sap.com/">http://www.sap.com</A></FONT></SPAN> </P>
<P><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>*****************************************************************************************</FONT></SPAN>
<BR><SPAN lang=en-au><FONT face="Times New Roman" color=#800000 size=2>The
information contained in or attached to this electronic transmission is
confidential and may be legally privileged. It is intended only for the person
or entity to which it is addressed. If you are not the intended recipient, you
are hereby notified that any distribution, copying, review, retransmission,
dissemination or other use of this electronic transmission or the information
contained in it is strictly prohibited. If you have received this electronic
transmission in error, please immediately contact the sender to arrange for
the return of the original documents.</FONT> </SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#800000
size=2>Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.</FONT></SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#800000 size=2>Any
views expressed in this electronic transmission are those of the individual
sender, except where the message states otherwise and the sender is authorized
to state them to be the views of SAP AG or any of its subsidiaries. SAP AG,
its subsidiaries, and their directors, officers and employees make no
representation nor accept any liability for the accuracy or completeness of
the views or information contained herein. Please be aware that the furnishing
of any pricing information/ business proposal herein is indicative only, is
subject to change and shall not be construed as an offer or as constituting a
binding agreement on the part of SAP AG or any of its subsidiaries to enter
into any relationship, unless otherwise expressly stated. </FONT></SPAN></P>
<P><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>*****************************************************************************************</FONT></SPAN><SPAN
lang=en-au></SPAN> </P>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Kjetil
Kilhavn<BR><B>Sent:</B> Friday, 03 June 2005 3:29 PM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> RE: Cancelling the previous
workitem<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=562012405-03062005><FONT face=Arial
color=#0000ff size=2>Can you really set up a start condition which checks for
already existing instances of the same workflow for the current object?
Admittedly I haven't looked much into start conditions, but from what I have
seen they are meant for much simpler checks.</FONT></SPAN></DIV>
<DIV align=left><FONT face=Arial size=2>-- </FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Kjetil Kilhavn, Statoil KTJ IT
BKS</FONT></DIV>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Dart,
Jocelyn<BR><B>Sent:</B> 3. juni 2005 01:46<BR><B>To:</B> SAP Workflow Users'
Group<BR><B>Subject:</B> RE: Cancelling the previous
workitem<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=202293723-02062005><FONT face=Arial
color=#0000ff size=2>Folks, </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=202293723-02062005><FONT face=Arial
color=#0000ff size=2>Really - if you are 4.6C or above it's better (clarity
for developers and business analysts) and considerably quicker (initial
development and on-going maintenance, switch on/switch off, etc.) to use a
start condition (transaction SWB_COND) which utilises a standard check
function module than build your own custom check function module. Custom
check function module these days I treat as a last resort, card up my sleeve
if all else fails type of approach. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=202293723-02062005><FONT face=Arial
color=#0000ff size=2>Jocleyn </FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Maes
Steven<BR><B>Sent:</B> Thursday,2 June 2005 9:22 PM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> RE: Cancelling the previous
workitem<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Hi
Amit,<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">You can do this in
the event linkage. This is where you link the event to a workflow. Here you
can enter a check function to decide if you would like to start the WF or
not. <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Transaction
SWETYPV.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Good
luck,<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Steven
Maes<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=3>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">Van:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> Amit
Moghe [mailto:amitpmoghe@rediffmail.com] <BR><B><SPAN
style="FONT-WEIGHT: bold">Verzonden:</SPAN></B> donderdag 2 juni 2005
13:07<BR><B><SPAN style="FONT-WEIGHT: bold">Aan:</SPAN></B>
sap-wug@mit.edu<BR><B><SPAN style="FONT-WEIGHT: bold">Onderwerp:</SPAN></B>
Cancelling the previous workitem</SPAN></FONT><o:p></o:p></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">Hi
Kjetil,<BR><BR>Do you want me to call this function module before the
triggering event is published? <BR><BR>If yes, then, I am afraid
whether I can do that since the event is published by the standard program.
Also for a moment even if I have control over publishing the event, how can
I restart the same workitem?<BR><BR>If no, then, will you please a bit more
elaborate?<BR><BR>I would definitely like to trigger as few workflows as
possible since that would reduce my work :))<BR><BR>Thanks &
Regards,<BR>Amit<BR><BR><BR>-------------------<BR>It's a bit late I guess,
but I would recommend using a check function instead. Then you prevent
starting the second instance by looking for existing workflows related to
your purchase order (function SAP_WAPI_WORKITEMS_TO_OBJECT). <BR><BR>The
fewer workflows started, the better - unless your salary depends on the
number of started workflows.<BR>-- <BR>Kjetil Kilhavn, Statoil KTJ IT
BKS<BR><BR><BR><BR>________________________________<BR><BR>From:
sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Amit Moghe<BR>Sent: 2. juni 2005 10:32<BR>To: sap-wug at mit.edu<BR>Subject:
AW: Cancelling the previous workitem<BR><BR><BR><BR>Hi
Michael,<BR><BR> Thanks a lot for the help. It works
perfectly... <BR><BR>Regards,<BR>Amit<BR><BR>--------<BR> Hi
Amit,<BR><BR> You can built a parallel processing in Your workflow,
which ends, <BR> if one of the both branches is completed. One
branch includes Your <BR> current workflow and the other consits of a
Wait Step , which waits <BR> for the event 'CHANGED' of
BUS2012.<BR><BR><BR> Best regards<BR> Michael Ludwig<BR>
rku.it GmbH<BR><BR> -----Ursprüngliche Nachricht-----<BR>
Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]
Im Auftrag von Amit Moghe<BR> Gesendet: Donnerstag, 2. Juni
2005 08:34<BR> An: sap-wug at mit.edu<BR> Cc:
amitpmoghe at rediffmail.com<BR> Betreff: Cancelling the
previous workitem<BR> <BR> <BR><BR>
Hi Workflow Gurus,<BR> <BR> I am new to workflow
and need some help.<BR> <BR> I have a workflow for
which I am using 'CHANGED' event of the business object BUS2012 (Purchase
Order) as the triggering event. When a user changes a particular PO, this
workflow starts. But before it is completed if there is another change to
the same PO, then, one more workitem is started.<BR> <BR>
My requirement is that if there is change to the PO, then, it should
delete the previous workitem and start a new workitem. Can you please advise
me as to how this can be achieved?<BR> <BR> Thanks
in advance.<BR> <BR> Regards,<BR>
Amit<BR><BR> <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><BR><BR><A
href="http://clients.rediff.com/signature/track_sig.asp" target=_blank><SPAN
style="TEXT-DECORATION: none"><IMG id=_x0000_i1025 height=38
src="http://ads.rediff.com/RealMedia/ads/adstream_nx.cgi/www.rediffmail.com/inbox.htm@Bottom"
width=578 border=0
NOSEND="1"></SPAN></A><o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE>
<P></P>
<P><FONT
size=1>-------------------------------------------------------------------<BR>The
information contained in this message may be CONFIDENTIAL and is<BR>intended
for the addressee only. Any unauthorised use, dissemination of
the<BR>information or copying of this message is prohibited. If you are not
the<BR>addressee, please notify the sender immediately by return e-mail and
delete<BR>this message.<BR>Thank you.</FONT> </P>
<P></P>
<P><FONT
size=1>-------------------------------------------------------------------<BR>The
information contained in this message may be CONFIDENTIAL and is<BR>intended
for the addressee only. Any unauthorised use, dissemination of
the<BR>information or copying of this message is prohibited. If you are not
the<BR>addressee, please notify the sender immediately by return e-mail and
delete<BR>this message.<BR>Thank you.</FONT> </P></BLOCKQUOTE></BODY></HTML>