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