<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:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 11 (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]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@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";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
p
        {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";}
span.E-MailFormatvorlage18
        {mso-style-type:personal;
        font-family:Arial;
        color:navy;}
span.E-MailFormatvorlage20
        {mso-style-type:personal-reply;
        font-family:Arial;
        color:navy;}
@page Section1
        {size:595.3pt 841.9pt;
        margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.Section1
        {page:Section1;}
-->
</style>
</head>
<body lang=DE link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Hi Jerry,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'>maybe you can send me the
work around instructions. The note you mentioned was without any sucsess.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'>Thanks in advance<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'>Chris<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=3 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>Von:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <b><span
style='font-weight:bold'>Im Auftrag von </span></b>jerry martinek<br>
<b><span style='font-weight:bold'>Gesendet:</span></b> Mittwoch, 8. März 2006
17:21<br>
<b><span style='font-weight:bold'>An:</span></b> <st1:PersonName w:st="on">SAP
Workflow Users' Group</st1:PersonName><br>
<b><span style='font-weight:bold'>Betreff:</span></b> Re: AW: Workflow Stops
without error in background task statusready</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p><b><font size=3 face="Times New Roman"><span style='font-size:12.0pt;
font-weight:bold'>Hi,</span></font></b><o:p></o:p></p>
<p><b><font size=3 face="Times New Roman"><span style='font-size:12.0pt;
font-weight:bold'>We've just gone through either a similar or the
same problem. We're running ERP2005, NW2004S with CUA.</span></font></b><o:p></o:p></p>
<p><strong><b><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>In
our case the problem turned out to be a workflow runtime problem. The
wf-batch id kept getting locked. SAP provided an OSS note for it
that we haven't applied yet because we're applying the latest support packs
plus we figured out a manuall work around. The note is 862937. If that
doesn't help, I can also send you the work around instructions.</span></font></b></strong><o:p></o:p></p>
<p><strong><b><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>Jerry</span></font></b></strong> <o:p></o:p></p>
<p><b><font size=3 face="Times New Roman"><span style='font-size:12.0pt;
font-weight:bold'>----- Original Message -----</span></font></b><o:p></o:p></p>
<p class=MsoNormal><b><font size=3 face="Times New Roman"><span
style='font-size:12.0pt;font-weight:bold'>From</span></font></b>:
"NICKLAS, Christian" <christian.nicklas@ser.de> <o:p></o:p></p>
<p class=MsoNormal><b><font size=3 face="Times New Roman"><span
style='font-size:12.0pt;font-weight:bold'>Date</span></font></b>: Wednesday,
March 8, 2006 8:12 am <o:p></o:p></p>
<p class=MsoNormal><b><font size=3 face="Times New Roman"><span
style='font-size:12.0pt;font-weight:bold'>Subject</span></font></b>: AW:
Workflow Stops without error in background task statusready <o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>> HI Mike, <br>
> Hi All <br>
> <br>
> yes there are some simultaneous forks in Definition. One in the <br>
> main flow, and two in each subflows. After the deletion of the <br>
> forks still the same problem. <br>
> <br>
> But the lock can be the reason. In a dialog task I make at the end <br>
> an update on a czustom-table. In the next task a background step <br>
> updates the same database. <br>
> Can this be the program? Commit work is not set in the dialog or <br>
> background task <br>
> <br>
> Regards <br>
> <br>
> Christian Nicklas <br>
> <br>
> <br>
> -----Ursprüngliche Nachricht----- <br>
> Von: sap-wug-bounces@mit.edu [sap-wug-bounces@mit.edu] Im Auftrag <br>
> von Mike Pokraka <br>
> Gesendet: Mittwoch, 8. März 2006 14:45 <br>
> An: <st1:PersonName w:st="on">SAP Workflow Users' Group</st1:PersonName> <br>
> Betreff: Re: Workflow Stops without error in background task <br>
> statusready <br>
> Uh, hold on. You say RSWERRE restarts it. So in other words they <br>
> SHOULDall restart themselves after a while (20 minutes)... yes? <br>
> <br>
> In that case might it be some kind of locking conflict? - pick your <br>
> process apart for simultaneous forks or DB updates which might <br>
> still be <br>
> active or other similar things. <br>
> How is RSWERRE scheduled (SWWD)? <br>
> <br>
> Failing that, OSS. <br>
> <br>
> Cheers, <br>
> Mike <br>
> <br>
> NICKLAS, Christian wrote: <br>
> > Hi all <br>
> > Hi Mike, <br>
> > <br>
> > that would be to easy ;-). <br>
> > It is a background task and background method - in SWI2_ADM1 <br>
> there is not <br>
> > entry. But ii SWIA it can be processed! <br>
> > <br>
> > So it is becoming more and more strange and that is the reason <br>
> why I <br>
> > cannot find a solution? <br>
> > <br>
> > But maybe I am on the correct way with report RSWWERRE? When I <br>
> start the <br>
> > report manually after 10 minutes when the workitem was created, <br>
> the flow <br>
> > continues. <br>
> > <br>
> > Anybody any ideas what the problem could be? <br>
> > <br>
> > Regards <br>
> > <br>
> > <br>
> > Christian Nicklas | Prof. Services SAP Workflow <br>
> > SER Solutions Deutschland GmbH <br>
> > <br>
> > <br>
> > -----Ursprüngliche Nachricht----- <br>
> > Von: sap-wug-bounces@mit.edu [sap-wug-bounces@mit.edu] Im Auftrag <br>
> > von Mike Pokraka <br>
> > Gesendet: Mittwoch, 8. März 2006 13:32 <br>
> > An: <st1:PersonName w:st="on">SAP Workflow Users' Group</st1:PersonName>
<br>
> > Betreff: Re: AW: AW: Workflow Stops without error in background task <br>
> > status ready <br>
> > <br>
> > Duh, must read posts more carefully. You mentioned SWIA before. <br>
> That makes <br>
> > the answer simple: it's not a background task. <br>
> > <br>
> > A task in READY status won't show an agent, as it can be with <br>
> many people. <br>
> > Once someone executes it and changes status to STARTED, it will <br>
> show an <br>
> > agent. <br>
> > <br>
> > Check your agent assignments on the task. Check if they show up in <br>
> > SWI2_ADM1 (tasks without agents), would indicate it's being <br>
> routed to the <br>
> > wrong people / not a possible agent of the task. <br>
> > <br>
> > Note, a background task can be 'dialog' even though there isn't <br>
> any user <br>
> > interaction. What it means is that - with 'advance in dialog' <br>
> set - it <br>
> > executes under the userID of the previous task as opposed to WF- <br>
> BATCH.> This can be for authorization reasons or simply that you <br>
> want the 'last <br>
> > changed by' to reflect the user who made a decision. <br>
> > <br>
> > Cheers, <br>
> > Mike <br>
> > <br>
> > NICKLAS, Christian wrote: <br>
> >> Hi Mike, <br>
> >> <br>
> >> In SM13 and SM21 no entries are available. <br>
> >> After setting the WI into status error I get no hits in <br>
> SWI2_DIAG to <br>
> >> restart the process (when I set the whole WF into error I get a <br>
> hit but <br>
> >> not possible to restart the flow) <br>
> >> Only thing what works is in transaction SWIA to execute without <br>
> agent>> check (also here no agent is displayed in the column!) <br>
> >> <br>
> >> Regards <br>
> >> Christian <br>
> >> <br>
> >> Christian Nicklas | Prof. Services SAP Workflow <br>
> >> SER Solutions Deutschland GmbH <br>
> >> <br>
> >> <br>
> >> -----Ursprüngliche Nachricht----- <br>
> >> Von: sap-wug-bounces@mit.edu [sap-wug-bounces@mit.edu] Im Auftrag
<br>
> >> von Mike Pokraka <br>
> >> Gesendet: Mittwoch, 8. März 2006 12:31 <br>
> >> An: <st1:PersonName w:st="on">SAP Workflow Users' Group</st1:PersonName>
<br>
> >> Betreff: Re: AW: Workflow Stops without error in background <br>
> task status <br>
> >> ready <br>
> >> <br>
> >> Duh, ignore me, must read posts more carefully. You said there <br>
> aren't>> any <br>
> >> conditions. <br>
> >> Can you restart them as described? If so it would point towards <br>
> a basisy <br>
> >> problem. Else you can also check for update failures - SM13. <br>
> System log <br>
> >> SM21 may also reveal some hints. Check around the time the task
is <br>
> >> created. <br>
> >> <br>
> >> Cheers, <br>
> >> Mike <br>
> >> <br>
> >> Mike Pokraka wrote: <br>
> >>> What about the conditions? SWI1_COND implies you have a <br>
> condition on <br>
> >>> the <br>
> >>> task. That does exactly what you describe - task won't start <br>
> until the <br>
> >>> condition is met. <br>
> >>> <br>
> >>> NICKLAS, Christian wrote: <br>
> >>>> Hi Mike <br>
> >>>> <br>
> >>>> thanks fort he hint. In SM58 everything is fine. For this
<br>
> background>>>> tasks <br>
> >>>> no conditions are maintained. The SWU3 looks good for the
<br>
> >>>> runtime-environment. <br>
> >>>> But for me it seems that something is wrong with the
runtime, <br>
> because>>>> it <br>
> >>>> happens very often that the Background-WI's stop in
status ready. <br>
> >>>> <br>
> >>>> Regards <br>
> >>>> Christian <br>
> >>>> <br>
> >>>> <br>
> >>>> <br>
> >>>> -----Ursprüngliche Nachricht----- <br>
> >>>> Von: sap-wug-bounces@mit.edu [sap-wug-bounces@mit.edu] Im
<br>
> >>>> Auftrag <br>
> >>>> von Mike Pokraka <br>
> >>>> Gesendet: Mittwoch, 8. März 2006 11:23 <br>
> >>>> An: <st1:PersonName w:st="on">SAP Workflow Users' Group</st1:PersonName>
<br>
> >>>> Betreff: Re: Workflow Stops without error in background
task <br>
> status>>>> ready <br>
> >>>> <br>
> >>>> Hallo Christian, <br>
> >>>> Background tasks do not have agents, so what you are
seeing in <br>
> >>>> SWI1_COND <br>
> >>>> is correct. Interesting you mention SWI1_COND - have you
set a <br>
> >>>> condition <br>
> >>>> for the task? Is it fulfilled? <br>
> >>>> Conditional tasks are evaluated/executed by a background job,
<br>
> make>>>> sure <br>
> >>>> it's scheduled and running. <br>
> >>>> <br>
> >>>> Also, have a look in SM58 for any problems. <br>
> >>>> Something else to try is set the task to error using
SE37, FM <br>
> >>>> SWW_WI_STATUS_CHANGE_NEW (I think... something like
that), <br>
> and try <br>
> >>>> restart <br>
> >>>> with SWI2_DIAG. <br>
> >>>> <br>
> >>>> MfG, <br>
> >>>> Mike <br>
> >>>> <br>
> >>>> NICKLAS, Christian wrote: <br>
> >>>>> Hi all, <br>
> >>>>> <br>
> >>>>> <br>
> >>>>> <br>
> >>>>> I have implemented a workflow running on ERP-Release
ECC 5.0 <br>
> >>>>> (SAP_BASIS <br>
> >>>>> 640; Patch Level 0009; SAPKB64009; SAP Basis
Component). <br>
> >>>>> <br>
> >>>>> When testing the solution sometimes the workflow
stops <br>
> without any <br>
> >>>>> error <br>
> >>>>> in background tasks. This happens in different
background <br>
> tasks from <br>
> >>>>> time to time and in other runs it works. <br>
> >>>>> <br>
> >>>>> At the workflow log the status of the background task
is in <br>
> status>>>>> ready. The information at the task says
"Execution <br>
> will continue in <br>
> >>>>> background" (Message no. SWF_RUN609). <br>
> >>>>> <br>
> >>>>> There is no error in the log. In ST22 no dump exists.
Also the <br>
> >>>>> administrative tasks (SWPR - Restart after error /
SWPC - <br>
> Restart>>>>> after <br>
> >>>>> SystemCrash) are not possible. SWU_OBUF also does not
work. <br>
> >>>>> <br>
> >>>>> <br>
> >>>>> <br>
> >>>>> The only thing which I found was in transaction
SWI1_COND. <br>
> For the <br>
> >>>>> task <br>
> >>>>> there is no agent available in the agent column
(should be <br>
> >>>>> workflow-system)? <br>
> >>>>> <br>
> >>>>> When I process and reactivate the workitem in
transaction <br>
> SWIA the <br>
> >>>>> flow <br>
> >>>>> goes on. (WF_BATCH has SAP_ALL / SAP_NEW) <br>
> >>>>> <br>
> >>>>> <br>
> >>>>> <br>
> >>>>> Any ideas and help are appreciated. <br>
> >>>>> <br>
> >>>>> <br>
> >>>>> <br>
> >>>>> Christian Nicklas | Prof. Services SAP Workflow <br>
> >>>>> SER Solutions Deutschland GmbH <br>
> >>>>> <br>
> >>>>> <br>
> >>>>> <br>
> >>>>> _______________________________________________ <br>
> >>>>> SAP-WUG mailing list <br>
> >>>>> SAP-WUG@mit.edu <br>
> >>>>> http://mailman.mit.edu/mailman/listinfo/sap-wug <br>
> >>>>> <br>
> >>>> <br>
> >>>> _______________________________________________ <br>
> >>>> SAP-WUG mailing list <br>
> >>>> SAP-WUG@mit.edu <br>
> >>>> http://mailman.mit.edu/mailman/listinfo/sap-wug <br>
> >>>> <br>
> >>>> _______________________________________________ <br>
> >>>> SAP-WUG mailing list <br>
> >>>> SAP-WUG@mit.edu <br>
> >>>> http://mailman.mit.edu/mailman/listinfo/sap-wug <br>
> >>>> <br>
> >>> <br>
> >>> _______________________________________________ <br>
> >>> SAP-WUG mailing list <br>
> >>> SAP-WUG@mit.edu <br>
> >>> http://mailman.mit.edu/mailman/listinfo/sap-wug <br>
> >>> <br>
> >> <br>
> >> _______________________________________________ <br>
> >> SAP-WUG mailing list <br>
> >> SAP-WUG@mit.edu <br>
> >> http://mailman.mit.edu/mailman/listinfo/sap-wug <br>
> >> <br>
> >> _______________________________________________ <br>
> >> SAP-WUG mailing list <br>
> >> SAP-WUG@mit.edu <br>
> >> http://mailman.mit.edu/mailman/listinfo/sap-wug <br>
> >> <br>
> > <br>
> > _______________________________________________ <br>
> > SAP-WUG mailing list <br>
> > SAP-WUG@mit.edu <br>
> > http://mailman.mit.edu/mailman/listinfo/sap-wug <br>
> > <br>
> > _______________________________________________ <br>
> > SAP-WUG mailing list <br>
> > SAP-WUG@mit.edu <br>
> > http://mailman.mit.edu/mailman/listinfo/sap-wug <br>
> > <br>
> <br>
> _______________________________________________ <br>
> SAP-WUG mailing list <br>
> SAP-WUG@mit.edu <br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug <br>
> <br>
> _______________________________________________ <br>
> SAP-WUG mailing list <br>
> SAP-WUG@mit.edu <br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug <br>
> <o:p></o:p></span></font></p>
</div>
</body>
</html>