_SAP_WFSYST_RC_DONT_CARE

[Bijay Shrestha]

Hi Sue,
 
Then let me suggest one another thing. I have one another situation
similar to yours e.g. there are about 30 people process certain step in
our workflow. There are about 3000 times workflow a day. Once in a while
I see this type of error from certain user. I looked into workflow,
workflow log nothing unusual thing was happening. I did not design this
workflow but I'm supporting now.
 
Then to narrow down the problem, I called that user and ask her to walk
me through every detail that she went through to perform the process.
And since it doesn't happen all the time it's important to call
immediately so that user still remembers what he/she did. Finally I was
able to figure out what was happening. In one decision step she had
couple option to click on e.g. "Ok" or "change". What I found was most
of the time she was doing as she is supposed to do but once in a while
she accidentally hit another button and she did not know what to do. So
some how she manages to get out from there but that task hung up.
 
So that helped me to fix the technical bug.
 
This is just my two cents from my past experience. Wish you good luck.
 
 
Bijay Shrestha=20
Ph: (763) 764-2201=20
Pager: (612) 661-2772=20
Email: Bijay.Shrestha at genmills.com=20
"WebFlow gets the right information to the right people at the right
time!"
 
 
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Susan R. Keohan
Sent: Friday, March 12, 2004 1:25 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: _SAP_WFSYST_RC_DONT_CARE
 
 
Hi Bijay,
 
I thought this might be the case (did find references to WL411 in OSS
after all, but not that specific event) but the error occurred three
times in a workflow (calling a subworkflow 90 times) in varying steps of
the subworkflow.  There was no one specific method I could point out as
being the culprit.
 
Thanks for the suggestion,
Sue
 
 
Bijay Shrestha wrote:
 
> Sue,
>
> I had this issue before. Normally, this error (WL411) happens when you
 
> have some custom ABAP program/ Function Module call from one of your=20
> method in that specific task but does not trigger the termination=20
> event. If that is the case please define a terminating event and=20
> triger that event at the end of your function Module call or ABAP=20
> Program so that it can complete the step.
>
> Bijay Shrestha
> Ph: (763) 764-2201
> Pager: (612) 661-2772
> Email: Bijay.Shrestha at genmills.com
> "WebFlow gets the right information to the right people at the right=20
> time!"
>
>
>
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of=20
> Susan R. Keohan
> Sent: Friday, March 12, 2004 8:23 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: _SAP_WFSYST_RC_DONT_CARE
>
>
> Hi all,
>
> I hope some of you are just as excited to see the above error message=20
> as I was...
>
> I am on 4.6c, and a workflow went into error (WL 411) yesterday with=20
> the following message.
>
>
>>Workflow '611122' work item : No successor defined
>>for event '_SAP_WFSYST_RC_DONT_CARE'
>
>
> So, my workflow does not wait for this event, and I cannot find any=20
> reference to it in OSS.
>
> Any insights would be greatly appreciated!
> Thanks
> Sue
> --
> Susan R. Keohan
> SAP Workflow Developer
> MIT Lincoln Laboratory
> 244 Wood Street
> LI-200
> Lexington, MA. 02420
> 781-981-3561
> keohan at ll.mit.edu
>
 
--
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu