[LIKELY JUNK]RE: Infeasible State Transition WL 802 -> ABAP ClassMethod CL_SWF_RUN_WIM_STATE->EXECUTE_STATE_TRANSITION

[Dart, Jocelyn]

Hi Mike GT - you should also look at the SAP_WAPI function modules -
there's a RESUME WAPI that may help or at least show you "safe" code for
creating your own program to fix the problem. 
I'd also suggest you stop the illegal behaviours if you can - obviously
there are some people out there with more access than they need. 
Regards,
Jocelyn 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Pokraka
Sent: Saturday, 7 February 2009 8:42 AM
To: 'SAP Workflow Users' Group'
Subject: [LIKELY JUNK]RE: Infeasible State Transition WL 802 -> ABAP
ClassMethod CL_SWF_RUN_WIM_STATE->EXECUTE_STATE_TRANSITION



Hi Mike, 

 

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.

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 :-)

 

Cheers, 

Mike

 

 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Gambier
Sent: 26 January 2009 16:39
To: sap-wug at mit.edu
Subject: Infeasible State Transition WL 802 -> ABAP Class Method
CL_SWF_RUN_WIM_STATE->EXECUTE_STATE_TRANSITION

 

Hi fellow WUGgers,
 
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.
 
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.
 
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 en
masse reprocessing of 'stuck' work legitimately. And when I say stuck I
mean
'cancelled-because-someone-was-stupid-and-killed-a-lot-of-steps-they-sho
uldn't-have-but-the-workflow-is-still-there' kinda thing.
 
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.
 
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?
 
Regards,
 
Mike GT
 

 

________________________________

Share your photos with Windows Live Photos - Free Try it Now!
<http://www.microsoft.com/uk/windows/windowslive/products/messenger.aspx
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090212/d6c17a72/attachment.htm