<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[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]-->
<title>Event Triggering Twice</title>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PostalCode"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="country-region"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"Trebuchet MS";
        panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
p
        {mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman";}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:Arial;
        color:navy;}
@page Section1
        {size:612.1pt 792.1pt;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>David,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Take a look at transaction SWETYPV for
entry BUS1006.Changed and you will see two entries with active linkages. You
can either disable one entry or look into why there are two active. I once ran
into a situation where two entries were active because someone decided to
experiment with workflow. If both entries are supposed to be active, you may
want use a start condition or check function module to start them only when
needed.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Richard…<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Bibby, David<br>
<b><span style='font-weight:bold'>Sent:</span></b> Friday, January 28, 2005
9:55 AM<br>
<b><span style='font-weight:bold'>To:</span></b> sap-wug@mit.edu<br>
<b><span style='font-weight:bold'>Subject:</span></b> Event Triggering Twice</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p><font size=2 face="Trebuchet MS"><span style='font-size:10.0pt;font-family:
"Trebuchet MS"'>I have a problem with a workflow where the event triggers twice
and the workflow therefore triggers twice.</span></font> <o:p></o:p></p>
<p><font size=2 face="Trebuchet MS"><span style='font-size:10.0pt;font-family:
"Trebuchet MS"'>The Business Object is BUS1006 and the event is CHANGED.</span></font>
<o:p></o:p></p>
<p><font size=2 face="Trebuchet MS"><span style='font-size:10.0pt;font-family:
"Trebuchet MS"'>In CRM 4.0, when a Business Partner is edited in transaction BP
a workflow is supposed to trigger.</span></font> <o:p></o:p></p>
<p><font size=2 face="Trebuchet MS"><span style='font-size:10.0pt;font-family:
"Trebuchet MS"'>The only visible difference I can see in the two event log
entries is the main program.</span></font> <br>
<font size=2 face="Trebuchet MS"><span style='font-size:10.0pt;font-family:
"Trebuchet MS"'>One says the main program is SAPLBUPA_DIALOG_JOEL and the other
event has the main program RSM13000.</span></font> <o:p></o:p></p>
<p><font size=2 face="Trebuchet MS"><span style='font-size:10.0pt;font-family:
"Trebuchet MS"'>I have never seen this before. Has anyone any ideas what could
be causing this ?</span></font> <o:p></o:p></p>
<p><font size=2 face=Arial><span lang=EN-GB style='font-size:10.0pt;font-family:
Arial'>Many Thanks</span></font> <br>
<font size=2 face=Arial><span lang=EN-GB style='font-size:10.0pt;font-family:
Arial'>David</span></font><span lang=EN-GB> </span><o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>This
message is confidential. It may also be privileged or<br>
otherwise protected by work product immunity or other legal<br>
rules. If you have received it by mistake please let us know<br>
by reply and then delete it from your system; you should not<br>
copy it or disclose its contents to anyone. All messages sent<br>
to and from Linklaters may be monitored to ensure compliance<br>
with internal policies and to protect our business. Emails are<br>
not secure and cannot be guaranteed to be error free as they<br>
can be intercepted, amended, lost or destroyed, or contain<br>
viruses. Anyone who communicates with us by email is taken<br>
to accept these risks.<br>
<br>
The contents of any email addressed to our clients are subject<br>
to our usual terms of business; anything which does not relate<br>
to the official business of the firm is neither given nor endorsed by it. <br>
<br>
The registered address of the <st1:country-region w:st="on"><st1:place w:st="on">UK</st1:place></st1:country-region>
partnership of Linklaters is <st1:address w:st="on"><st1:Street w:st="on">One <br>
Silk Street</st1:Street>, <st1:City w:st="on">London</st1:City>, <st1:PostalCode
w:st="on">EC2Y 8HQ</st1:PostalCode></st1:address>. Please refer to <br>
http://www.linklaters.com/regulation for important information on<br>
the regulatory position of the firm.<o:p></o:p></span></font></p>
</div>
</body>
</html>