<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=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:Verdana;
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";}
span.EmailStyle19
{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-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Mike, <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'>Thinking outside the box: Perhaps you could duplicate the state
of the workflow. It’s not difficult to create a little report to mirror the
container into a new workflow instance, and in NetWeaver you also have
transaction SWUS_WITH_REFERENCE.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If the cancellation is way down the flow, perhaps you could
create a temporary ‘resume’ template specific to that issue and run your report
to resume all your cancelled ones. Or if you have lots of reporting around
specific templates then you could generate a version with a special ‘skip’ import
flag and appropriate branch, but I guess I don’t need to explain that level of
detail to you :-)<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'>Cheers, <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Mike<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 style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<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>Mike Gambier<br>
<b>Sent:</b> 26 January 2009 16:39<br>
<b>To:</b> sap-wug@mit.edu<br>
<b>Subject:</b> Infeasible State Transition WL 802 -> ABAP Class Method
CL_SWF_RUN_WIM_STATE->EXECUTE_STATE_TRANSITION<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Hi
fellow WUGgers,<br>
<br>
Now that we've had a week to play with the new ECC 6 stuff for real (things are
settling down now), some interesting 'features' have started to become evident.
For us the limitations of the new 'State Transition' approach appear to be the
most painful at the moment.<br>
<br>
I can see why SAP have tightened up this area, after all plenty of people had
worked out that calling some Admin FMs in the past with a few flags set would
allow all sorts of shenanigans to go on when mucking about with errored or
cancelled steps or flows. But now we seem to have swung from one extreme to the
other. There's no 'Admin' privileges to tap into to do something
technially 'illegal' under normal Workflow conditions that may actually
be required to keep the system going.<br>
<br>
Short of mucking around with the CLASS_CONSTRUCTORS and adding spurious 'legal'
states (like CANCELLED->READY) or direct database updates to SWWWIHEAD
*shudder* there's very little that one can do to allow <em><span
style='font-family:"Verdana","sans-serif"'>en masse</span></em> reprocessing of
'stuck' work legitimately. And when I say stuck I mean
'cancelled-because-someone-was-stupid-and-killed-a-lot-of-steps-they-shouldn't-have-but-the-workflow-is-still-there'
kinda thing.<br>
<br>
I've prayed to the Workflow Gods and received, predictably, a rather
polite response, that any such bypass option to enable 'illegal' status changes
would require a CDP.<br>
<br>
The trouble is that I'm pretty sure there are other people out there who
may have assumed they could manipulate steps and flows as they have done in the
past who may now come unstuck. Perhaps someone like that is even reading this
mail right now...? Or maybe, just maybe, someone has found a way around this?<br>
<br>
Regards,<br>
<br>
Mike GT<br>
<o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Share
your photos with Windows Live Photos - Free <a
href="http://www.microsoft.com/uk/windows/windowslive/products/messenger.aspx"
target="_new">Try it Now!</a><o:p></o:p></span></p>
</div>
</div>
</body>
</html>