<!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" xmlns:st1 =
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Event Triggering Twice</TITLE>
<META content="MSHTML 6.00.2800.1480" 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]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PostalCode"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="country-region"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"></o:SmartTagType><!--[if !mso]>
<STYLE>st1\:* {
BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Trebuchet MS;
}
@page Section1 {size: 612.1pt 792.1pt; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><SPAN class=312232911-31012005><FONT face="Trebuchet MS" color=#0000ff
size=2>Richard, Dan,</FONT></SPAN></DIV>
<DIV><SPAN class=312232911-31012005><FONT face="Trebuchet MS" color=#0000ff
size=2>I forgot to mention in my original message that I had checked
SWETYPV and there is only one entry in there.</FONT></SPAN></DIV>
<DIV><SPAN class=312232911-31012005><FONT face="Trebuchet MS" color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=312232911-31012005><FONT face="Trebuchet MS" color=#0000ff
size=2>However I've now have checked SWEC and found an entry in there for
BUPA_BUP BUS1006 CHANGED.</FONT></SPAN></DIV>
<DIV><SPAN class=312232911-31012005><FONT face="Trebuchet MS" color=#0000ff
size=2>In our other two systems where this problem isn't happening there is no
SWEC entry.</FONT></SPAN></DIV>
<DIV><SPAN class=312232911-31012005><FONT face="Trebuchet MS" color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=312232911-31012005><FONT face=
"Trebuchet MS" color=#0000ff
size=2>I think it might be possible that our 4.0 upgrade to this system added
this SWEC entry. The other two systems are still on 3.1</FONT></SPAN></DIV>
<DIV><SPAN class=312232911-31012005><FONT face="Trebuchet MS" color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=312232911-31012005><FONT face="Trebuchet MS" color=#0000ff
size=2>Many Thanks</FONT></SPAN></DIV>
<DIV><SPAN class=312232911-31012005><FONT face="Trebuchet MS" color=#0000ff
size=2>David</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu]<B>On Behalf Of </B>Getliffe,
Dan<BR><B>Sent:</B> 31 January 2005 04:45<BR><B>To:</B> SAP Workflow Users'
Group<BR><B>Subject:</B> RE: Event Triggering Twice<BR><BR></FONT></DIV>
<DIV dir=ltr align=left><SPAN class=549353704-31012005><FONT face=Arial
color=#0000ff size=2>Hi David,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=549353704-31012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=549353704-31012005><FONT face=Arial
color=#0000ff size=2>As Richard has said the first thing to do is to determine
how the 2 events are being raised e.g. change documents, through the
application etc.. and then determine if both event linkages are required
to be active in the system. I recently had the situation with the
standard PO release workflow where one event was being raised by the
application and another event was being raised via an entry in SWEC (change
documents) which appeared following the application of a support package
- for this particular problem there was an OSS note that recommended
deactivating the event raised via change documents. It is worth
having a check on OSS and determining if any support packages have been
recently applied.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=549353704-31012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=549353704-31012005><FONT face=Arial
color=#0000ff size=2>Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=549353704-31012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=549353704-31012005><FONT face=Arial
color=#0000ff size=2>Dan. </FONT></SPAN></DIV>
<DIV> </DIV><!-- Converted from text/rtf format -->
<P><B><SPAN lang=en-us><FONT face=Arial color=#000080 size=1>Dan
Getliffe</FONT></SPAN></B><SPAN lang=en-us></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>NetWeaver 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 2, 441 St Kilda Road</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>Melbourne VIC 3004</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>T +61 3 9862
7144</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>F +61 3 9862 7244</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>M +61 438 234 533</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial color=#808080 size=1>E </FONT>
</SPAN><A href="mailto:dan.getliffe@sap.com"><SPAN lang=en-us><U><FONT
face=Arial color=#808080
size=1>dan.getliffe@sap.com</FONT></U></SPAN></A><SPAN
lang=en-us><U></U><U></U><U></U></SPAN> <BR><SPAN lang=en-us><FONT face=Arial
size=1><A
href="http://www.sap.com/australia">http://www.sap.com/australia</A></FONT></SPAN>
</P><BR><BR><BR>
<DIV> </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>Richard
Marut<BR><B>Sent:</B> Monday, 31 January 2005 3:05 PM<BR><B>To:</B> 'SAP
Workflow Users' Group'<BR><B>Subject:</B> RE: Event Triggering
Twice<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">David,<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
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">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 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
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Richard…<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>
<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=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; 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 face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P><FONT face="Trebuchet MS" size=2><SPAN
style="FONT-SIZE: 10pt; 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 face="Trebuchet MS" size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Trebuchet MS'">The Business Object is
BUS1006 and the event is CHANGED.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face="Trebuchet MS" size=2><SPAN
style="FONT-SIZE: 10pt; 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 face="Trebuchet MS" size=2><SPAN
style="FONT-SIZE: 10pt; 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 face="Trebuchet MS" size=2><SPAN
style="FONT-SIZE: 10pt; 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 face="Trebuchet MS" size=2><SPAN
style="FONT-SIZE: 10pt; 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 face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Many Thanks</SPAN></FONT>
<BR><FONT face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">David</SPAN></FONT><SPAN
lang=EN-GB> </SPAN><o:p></o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">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
style="BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"
tabIndex=0 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:P
ostalCode></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></BLOCKQUOTE></BLOCKQUOTE><HR><P>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 UK partnership of Linklaters is One <BR>Silk Street, London, EC2Y 8HQ. Please refer to <BR>http://www.linklaters.com/regulation for important information on<BR>the regulatory position of the firm.<BR></P></BODY></HTML>