<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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 12 (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]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-AU link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Patil – System Defaults means it uses the Behaviour on Error
Feedback specified on the Basic Data tab of SWEQADM. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>That should also be mark linkage as having errors – in which
case linkages deactivated due to errors can be reactivate on the linkages in
error tab….<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>You should of course also investigate the cause of the problem
and redeliver the failed events from the Linkages in Error tab also. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>By the way, the ability to be able to deactivate a workflow in
production without transport is deliberate – to allow for emergency stop of a
workflow as per SWEQADM. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Jocelyn<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Patil, Priyank<br>
<b>Sent:</b> Thursday, 1 July 2010 10:21 PM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> RE: Activating workflow without using SWDD tcode<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoPlainText><span lang=EN-US>Some workflows its ‘MARK LINKAGE AS
HAVING ERRORS’ and for some others its SYSTEM DEFAULTS.I guess this should not
be a problem.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Thanks<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>PD<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Rick Bakker<br>
<b>Sent:</b> Thursday, July 01, 2010 5:46 PM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> Re: Activating workflow without using SWDD tcode<o:p></o:p></span></p>
</div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US>What's the
setting in SWEQADM?<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span lang=EN-US>On Thu, Jul 1, 2010 at 8:08 PM, Patil,
Priyank <<a href="mailto:Priyank.Patil@keane.com">Priyank.Patil@keane.com</a>>
wrote:<o:p></o:p></span></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'>No, it was set to ‘Mark
linkage as having errors’.</span><span lang=EN-US><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'> </span><span
lang=EN-US><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'>Thanks,</span><span
lang=EN-US><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'>PD</span><span lang=EN-US><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'> </span><span
lang=EN-US><o:p></o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
lang=EN-US style='font-size:10.0pt'>From:</span></b><span lang=EN-US
style='font-size:10.0pt'> <a href="mailto:sap-wug-bounces@mit.edu"
target="_blank">sap-wug-bounces@mit.edu</a> [mailto:<a
href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a>]
<b>On Behalf Of </b>Neumann, Marcia<br>
<b>Sent:</b> Thursday, July 01, 2010 5:33 PM <o:p></o:p></span></p>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt'><br>
<b>To:</b> SAP Workflow Users' Group<o:p></o:p></span></p>
</div>
<div>
<div>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt'>Subject:</span></b><span
lang=EN-US style='font-size:10.0pt'> RE: Activating workflow without using SWDD
tcode<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US> <o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:10.0pt;color:navy'>We have ‘Behavior Upon Error
Feedback’ set to ‘Do not change linkage’ in event linkage SWETYPV for all our
workflows. Is your set to ‘Deactivation on linkage’?</span><span
lang=EN-US><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:10.0pt;color:navy'><img border=0 width=590
height=120 id="_x0000_i1025" src="cid:image001.jpg@01CB19EA.CE452230"></span><span
lang=EN-US><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:10.0pt;color:navy'> </span><span lang=EN-US><o:p></o:p></span></p>
<div>
<p><span lang=EN-US style='font-size:10.0pt;color:navy'>Marcia Neumann</span><span
lang=EN-US style='color:navy'> <br>
</span><span lang=EN-US style='font-size:10.0pt;color:gray'>I</span><span
lang=EN-US style='font-size:7.5pt;color:gray'>T Claims/CSU Development &
Support</span><span lang=EN-US style='color:navy'> <br>
</span><span lang=EN-US style='font-size:7.5pt;color:gray'>Ext 4461</span><span
lang=EN-US style='color:navy'> </span><span lang=EN-US><o:p></o:p></span></p>
<p><b><span lang=EN-US style='font-size:7.5pt;color:gray'>Confidentiality
notice:</span></b><span lang=EN-US style='font-size:7.5pt;color:gray'> The
information included in this e-mail,<i> including any attachments,</i> is for
the sole use of the intended recipient and may contain information that is
confidential and protected. Any unauthorized review, use, disclosure,
distribution or similar action is prohibited. If you are not the intended
recipient, please contact the sender and delete all copies of the original
message immediately.</span><span lang=EN-US><o:p></o:p></span></p>
</div>
<div>
<div class=MsoNormal align=center style='text-align:center'><span lang=EN-US>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
lang=EN-US style='font-size:10.0pt'>From:</span></b><span lang=EN-US
style='font-size:10.0pt'> <a href="mailto:sap-wug-bounces@mit.edu"
target="_blank">sap-wug-bounces@mit.edu</a> [mailto:<a
href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a>]
<b>On Behalf Of </b>Patil, Priyank<br>
<b>Sent:</b> Thursday, July 01, 2010 7:57 AM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> RE: Activating workflow without using SWDD tcode</span><span
lang=EN-US><o:p></o:p></span></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US> <o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US>The triggering event attached to WF is getting deactivated all the
time. Its creating a huge problem to us. And it’s a customized workflow not a
standard one.<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US> <o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US>Thanks<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US>Priyank<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'> </span><span
lang=EN-US><o:p></o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
lang=EN-US style='font-size:10.0pt'>From:</span></b><span lang=EN-US
style='font-size:10.0pt'> <a href="mailto:sap-wug-bounces@MIT.EDU"
target="_blank">sap-wug-bounces@MIT.EDU</a> [mailto:<a
href="mailto:sap-wug-bounces@MIT.EDU" target="_blank">sap-wug-bounces@MIT.EDU</a>]
<b>On Behalf Of </b>Bhupinder<br>
<b>Sent:</b> Thursday, July 01, 2010 5:18 PM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> Re: Activating workflow without using SWDD tcode</span><span
lang=EN-US><o:p></o:p></span></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US> <o:p></o:p></span></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US>Hi Priyank,<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US>Normally at production system, we are simply activating the
triggering event attached to WF which sometimes deactivated.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US>Is this the case in your scenario or WF definition itself gets
deactivated?<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US>To activate the event, you can either use OOCU tcode or using PFTC.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US>Best Regards,<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
lang=EN-US>Bhupinder<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US>On Thu, Jul 1, 2010 at 5:03 PM, Patil, Priyank <<a
href="mailto:Priyank.Patil@keane.com" target="_blank">Priyank.Patil@keane.com</a>>
wrote:<o:p></o:p></span></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US>Wuggers,<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US>
Can we activate our workflow without going into SWDD.Suppose I have
created one workflow for PO approval.Actuallly we don’t have access to
SWDD tcode in production and often the WF is getting inactive once its activated.
Now is there any way to activate workflow using any tcodes or standard
program.<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US> <o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:10.0pt;color:#1F497D'>______________________</span><span
lang=EN-US><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:10.0pt;color:#4F81BD'>Thanks and Regards,</span><span
lang=EN-US><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
lang=EN-US style='font-size:10.0pt;color:#4F81BD'>Priyank Dev Patil</span></b><span
lang=EN-US><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US> <o:p></o:p></span></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US><br>
______________________________________________________________________<br>
Disclaimer: This email message and any attachments are for the sole use of the
intended recipient(s) and may contain information that is confidential, legally
privileged or otherwise exempt from disclosure under applicable law. If you are
not the intended recipient(s) or have received this message in error, you are
instructed to immediately notify the sender by return email and required to
delete this message from your computer system. This communication does not form
any contractual obligation on behalf of the sender, the sender's employer or
such employer's parent company, affiliates or subsidiaries.<o:p></o:p></span></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
lang=EN-US><br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><o:p></o:p></span></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US> <o:p></o:p></span></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US><br>
______________________________________________________________________<br>
Disclaimer: This email message and any attachments are for the sole use of the intended
recipient(s) and may contain information that is confidential, legally
privileged or otherwise exempt from disclosure under applicable law. If you are
not the intended recipient(s) or have received this message in error, you are
instructed to immediately notify the sender by return email and required to
delete this message from your computer system. This communication does not form
any contractual obligation on behalf of the sender, the sender's employer or
such employer's parent company, affiliates or subsidiaries.<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span lang=EN-US><br>
______________________________________________________________________<br>
Disclaimer: This email message and any attachments are for the sole use of the
intended recipient(s) and may contain information that is confidential, legally
privileged or otherwise exempt from disclosure under applicable law. If you are
not the intended recipient(s) or have received this message in error, you are
instructed to immediately notify the sender by return email and required to
delete this message from your computer system. This communication does not form
any contractual obligation on behalf of the sender, the sender's employer or
such employer's parent company, affiliates or subsidiaries.<o:p></o:p></span></p>
</div>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US><br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US><br>
______________________________________________________________________<br>
Disclaimer: This email message and any attachments are for the sole use of the
intended recipient(s) and may contain information that is confidential, legally
privileged or otherwise exempt from disclosure under applicable law. If you are
not the intended recipient(s) or have received this message in error, you are
instructed to immediately notify the sender by return email and required to
delete this message from your computer system. This communication does not form
any contractual obligation on behalf of the sender, the sender's employer or
such employer's parent company, affiliates or subsidiaries.<o:p></o:p></span></p>
</div>
</body>
</html>