<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<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;}
/* 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
{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";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
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.EmailStyle20
{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;}
/* List Definitions */
@list l0
{mso-list-id:348409283;
mso-list-type:hybrid;
mso-list-template-ids:-1751338226 201916439 201916441 201916443 201916431 201916441 201916443 201916431 201916441 201916443;}
@list l0:level1
{mso-level-number-format:alpha-lower;
mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</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 bgcolor=white 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'>Hi MGT<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Really not trying to have an argument here, but just to clarify the
best practice position further for the sake of everyone else on the list:<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'> …. most of what you are saying is correct but ….<u> BOTH</u> SWETYPV
and SWEQADM look at event linkages … SWEQADM specifically looks at<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:36.0pt;text-indent:-18.0pt;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>a)<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Event
linkages in error<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:36.0pt;text-indent:-18.0pt;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>b)<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Volume
event linkages<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Whereas SWETYPV just contains the transported settings for all
event linkages. You can see if the event linkage has been marked in error but
it’s not exactly obvious. <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'>In a runtime environment any errors in behaviour are therefore far
more evident in SWEQADM which focuses on those errors in the Linkages in Error
tab. It links directly to the event linkage container and event log entries to
help diagnose why the event linkage failed. Plus it has traffic light icons to
highlight events with new and continuing problems. <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'>I agree SWETYPV is useful background information and you might
still need to use SWETYPV to fix the problem of course… but SWEQADM should still
be the starting point for event linkage behavioural problems. <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'>Especially as there are plenty of workflow administrators out
there who are not workflow developers… and SWETYPV wouldn’t help those people
at all. Even for a workflow developer it’s far easier to figure out what’s
going wrong when you can look at a specific instance of the event linkage and
its container. <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'>Also SWEQADM notifies the workflow administrator of any problems
via email (provided you entered a real user id with an email address on the
Basic Data tab) … so the workflow administrator is able to catch any errors
quicker. <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'>Perhaps you haven’t had a chance to play around in SWEQADM a lot
so far? Developers often don’t particularly if they’ve been working with
workflow for some years… but as a workflow administrator it’s an invaluable
tool, and well worth familiarizing yourself with it. <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'>Again not wanting an argument but, given that there are quite a
few workflow administrators on the WUG list, I think it’s important to clarify
the best practice here as using the correct tool goes directly to speed of
problem resolution. <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>
<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>Madgambler<br>
<b>Sent:</b> Thursday, 24 June 2010 5:06 PM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Cc:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> Re: Workflows getting inactive in Prod frequently<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>Hi back Jocelyn,<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>You!re right to point out how essential SWEQADM is of
course. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>In this case the cause for concern seems to be the behaviour
of the event linkages, which is more evident using SWETYPV.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Any self-respecting WF Admin should be watching both or at
least be aware of them.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Like you, though, my instinct here would be to investigate
why errors are causing feedback to trip the linkage rather than rush off to
adjust the setting, which is not what I'd advocate at all. Quite the contrary.
In this case the setting behaviour could well be justified to prevent further
damage.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>And of course SWEQADM would be invaluable to help diagnose
and re-issue 'stuck' events.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>MGT<br>
<br>
Sent from my iPhone<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
On 24 Jun 2010, at 00:38, "Dart, Jocelyn" <<a
href="mailto:jocelyn.dart@sap.com">jocelyn.dart@sap.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi
MGT,</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Sorry
but for the benefit of all I have to disagree with you there… </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>As
the whole point of SWEQADM is </span><o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-18.0pt'><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>a)</span><span
style='font-size:7.0pt;color:#1F497D'> </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>to
manage the event behaviour <u>over and above</u> the settings transported via
SWETYPV</span><o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-18.0pt'><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>b)</span><span
style='font-size:7.0pt;color:#1F497D'> </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>to
help you diagnose what is wrong if an event linkage has failed -
especially an occasional problem such as this which might be data related</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I’m
still seeing too many sites not remembering to set up SWEQADM and suffering as
a result. </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Please
folks you really need to think of activating your workflow environment as at
least a 2 step process these days i.e. SWU3 ***AND*** SWEQADM.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards,</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Jocelyn</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></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;font-family:"Tahoma","sans-serif"'>From:</span></b><span
lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a
href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>
[mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Madgambler<br>
<b>Sent:</b> Wednesday, 23 June 2010 8:05 PM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Cc:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> Re: Workflows getting inactive in Prod frequently</span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>And
SWETYPV is probably more useful for that...<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>But,
rather than changing the settings to prevent the linkage from blowing it would
be a better idea to find a recent instance of your WF (no doubt you have an
errored one lying around) and work out the problem is.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>You
might, for example, have an intermittent issue that is data related, e.g. A
binding error like ObjectA.ObjectB.Attribute where ObjectB is null.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>MGT<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br>
Sent from my iPhone<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><br>
On 23 Jun 2010, at 09:08, "Dart, Jocelyn" <<a
href="mailto:jocelyn.dart@sap.com">jocelyn.dart@sap.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Just check
the settings on the basic data tab. Karl has already indicated that the
critical field is the Behavior on Error Feedback</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></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;font-family:"Tahoma","sans-serif"'>From:</span></b><span
lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a
href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:sap-wug-bounces@mit.edu]
<b>On Behalf Of </b>Patil, Priyank<br>
<b>Sent:</b> Wednesday, 23 June 2010 5:54 PM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> RE: Workflows getting inactive in Prod frequently</span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Could you please explain me in detail regarding the settings in
the </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Queue Administration (SWEQADM) for workflows. As Iam not much
aware in that. Please let me know the settings that should be done.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><o:p></o:p></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;font-family:"Tahoma","sans-serif"'>From:</span></b><span
lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a
href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:sap-wug-bounces@mit.edu]
<b>On Behalf Of </b>Dart, Jocelyn<br>
<b>Sent:</b> Wednesday, June 23, 2010 1:14 PM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> RE: Workflows getting inactive in Prod frequently</span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Yes –
that’s exactly the sort of behaviour that suggests you are getting failed
linkages that are being deactivated by the Event Queue Administration settings.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></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;font-family:"Tahoma","sans-serif"'>From:</span></b><span
lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a
href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>
[mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Patil, Priyank<br>
<b>Sent:</b> Wednesday, 23 June 2010 5:18 PM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> RE: Workflows getting inactive in Prod frequently</span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Once I login into Prod and activate, it starts to work
perfectly. But after some days it will get inactive automatically, even for
standard workflows. Again I need to login and activate it. Its like an extra
rework for us.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><o:p></o:p></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;font-family:"Tahoma","sans-serif"'>From:</span></b><span
lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a
href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>
[mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Karl Nietz<br>
<b>Sent:</b> Wednesday, June 23, 2010 11:57 AM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> Workflows getting inactive in Prod frequently</span><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
lang=EN-US><br>
</span><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>It
is likely that you have the type linkage setting for your triggering event set
to 'Deactivation of Linkage' when an error occurs (parameter 'Behaviour Upon
Error Feedback'). You should change this to something more benign.
Also check the report of workflows in error (SWI2_DIAG) to see if you
have workflows in error, and review and clear them.</span><span lang=EN-US> <br>
<br>
</span><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Karl
Nietz<br>
Senior Consultant<br>
CSC Australia<br>
Ph: 61 3 8695 1157<br>
Mob: 61 434 181303<br>
<br>
Please consider the environment before printing this e-mail. <br>
<br>CSC - This is a private message. If you are not the intended
recipient, please delete without copying and kindly advise us by e-mail of the
mistake in delivery. Note: Regardless of content, this e-mail shall not operate
to bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail for
such purpose • CSC Australia Pty Limited; Registered Office: 5B/26 Talavera
Road, Macquarie Park NSW 2113 Australia; Incorporated in Australia. ACN: 008
476 944</span><span lang=EN-US> </span><o:p></o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>From:</span>
<o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"Patil,
Priyank" <<a href="mailto:Priyank.Patil@keane.com">Priyank.Patil@keane.com</a>></span>
<o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>To:</span>
<o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"SAP Workflow
Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>></span>
<o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>Date:</span>
<o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>23/06/2010 04:08 PM</span>
<o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>Subject:</span>
<o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Workflows getting
inactive in Prod frequently</span><o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US> </span><o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'><span lang=EN-US>
<hr size=2 width="100%" noshade style='color:gray' align=center>
</span></div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US><br>
<br>
<br>
</span><span lang=EN-US style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span><span
lang=EN-US> <br>
</span><span lang=EN-US style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Hi,</span><span
lang=EN-US> <br>
</span><span lang=EN-US style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>
We are facing serious a problem in production. The workflows which
are existing in Prod are automatically getting inactive. The event link in SWDD
are getting inactive frequently and the mail/workitems are not getting
triggered. Since every time we need to login to Prod and activate the event
linkage in the workflow builder. Is there any permanent solution for this??.We
are into Ecc6.</span><span lang=EN-US> <br>
</span><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#004080'>______________________</span><span lang=EN-US> <br>
</span><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#4181C0'>Thanks and Regards,</span><span lang=EN-US> <br>
</span><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#4181C0'>Priyank Dev Patil.</span></b><span lang=EN-US> <br>
</span><span lang=EN-US style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span><span
lang=EN-US> </span><o:p></o:p></p>
<p><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.</span><tt><span
lang=EN-US style='font-size:10.0pt'>_______________________________________________</span></tt><span
lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt>SAP-WUG mailing list</tt><br>
<tt><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a></tt><br>
</span><span lang=EN-US><a
href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><span
style='font-size:10.0pt'>http://mailman.mit.edu/mailman/listinfo/sap-wug</span></tt></a></span><o:p></o:p></p>
<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.</span><o:p></o:p></p>
<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.</span><o:p></o:p></p>
</div>
</div>
</blockquote>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>_______________________________________________<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">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
</blockquote>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<div>
<p class=MsoNormal>_______________________________________________<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">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</body>
</html>