<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1528" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=993470818-08032006>Jerry,</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=993470818-08032006></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=993470818-08032006>In this case I cannot tell if the WF is locked or
not. In SM58 I get the message "The current application triggered a
termination with a short dump". The thing is, this is going on (WF is in
"process" status) since Feb. 17.</SPAN> <SPAN class=993470818-08032006>
SWWERRE should have given up on this one a long time ago and the WF should've
gone in error. </SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=993470818-08032006></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=993470818-08032006></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=993470818-08032006></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=993470818-08032006></SPAN></FONT></FONT></FONT><B><I><FONT face=Arial
color=#000080>Dan Stoicof</FONT></I></B><I></I> <BR><FONT face=Arial
color=#000080 size=2>SAP Workflow/ABAP Team</FONT> <BR><FONT face=Arial
color=#000080 size=2>GREAT-WEST LIFE and ANNUITY</FONT> <SPAN
class=993470818-08032006><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV><SPAN class=993470818-08032006></SPAN> </DIV>
<DIV><SPAN class=993470818-08032006> </SPAN><FONT face=Tahoma><FONT
size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu]<B>On Behalf Of </B>jerry
martinek<BR><B>Sent:</B> Wednesday, March 08, 2006 9:56 AM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> Re: RE: AW: Workflow Stops without
error in background taskstatusready<BR><BR></DIV></FONT></FONT>
<BLOCKQUOTE>
<P>Hi Dan,</P>
<P>In our case SCUM is appropriate because we're using CUA and that is where
the password is set for the ids. Have you checked to see if wf-batch is
locked? If the id is locked, wf-batch can't logon on to execute the background
workitems. In our case each time the work item error job ran the items
were processed. </P>
<P>Jerry</P>
<P> </P>Content-class: urn:content-classes:message Content-Type:
multipart/alternative; boundary="----_=_NextPart_001_01C642CF.2B80D0C2"
------_=_NextPart_001_01C642CF.2B80D0C2 Content-Type: text/plain;
charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hey Jerry,
=20 Note 862937 talks about transcation SCUM and the issue is that a column =
in not available . . . Are you sure this is the note that can help with = the
WF-BATCH contention? =20 Dan Stoicof=20 SAP Workflow/ABAP Team=20 GREAT-WEST
LIFE and ANNUITY=20 -----Original Message----- From: sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu]On Behalf = Of jerry martinek Sent: Wednesday,
March 08, 2006 9:21 AM To: SAP Workflow Users' Group Subject: Re: AW: Workflow
Stops without error in background task = statusready 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_01C642CF.2B80D0C2 Content-Type: text/html;
charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
<META http-equiv='3D"Content-Type"' content='3D"text/html;'
='charset=3Diso-8859-1"'>
<META content='3D"MSHTML' name=3DGENERATOR 6.00.2800.1528?>
<DIV><SPAN class=3D955563916-08032006><FONT face=3DArial color=#3d000f
="size=3D2">Hey=20 Jerry,</FONT></SPAN></DIV>
<DIV><SPAN class=3D955563916-08032006><FONT face=3DArial color=#3d000f
="size=3D2"></FONT></SPAN> </DIV>
<DIV><SPAN class=3D955563916-08032006><FONT face=3DArial color=#3d000f
="size=3D2">Note=20 862937 talks about transcation SCUM and the issue is that
a column in = not=20 available . . . Are you sure this is the note that
can help with = the=20 WF-BATCH contention?</FONT></SPAN></DIV>
<DIV> </DIV>
<P><B><I><FONT face=3DArial color=#3d0008>Dan =
Stoicof</FONT></I></B><I></I>=20 <BR><FONT face=3DArial color=#3d0008
size=3>SAP Workflow/ABAP = Team</FONT>=20 <BR><FONT face=3DArial color=#3d0008
size=3>GREAT-WEST LIFE and = ANNUITY</FONT>=20 <BR></P><BR><BR>
<BLOCKQUOTE>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT size=3
="face=3DTahoma=20">-----Original Message-----<BR><B>From:</B> =
sap-wug-bounces@mit.edu=20 [mailto:sap-wug-bounces@mit.edu]<B>On Behalf Of
</B>jerry=20 martinek<BR><B>Sent:</B> Wednesday, March 08, 2006 9:21 =
AM<BR><B>To:</B> SAP=20 Workflow Users' Group<BR><B>Subject:</B> Re: AW:
Workflow Stops = without error=20 in background task
statusready<BR><BR></FONT></DIV>
<P></P>
<P><B>Hi,</B></P>
<P><B>We've just gone through either a similar or the same=20
problem. We're running ERP2005, NW2004S with CUA.</B></P>
<P><STRONG>In our case the problem turned out to be a workflow =
runtime=20 problem. The wf-batch id kept getting locked. SAP
provided=20 an OSS note for it that we haven't applied yet because
we're = applying the=20 latest support packs plus we figured out a
manuall work around. = The note=20 is 862937. If that doesn't help, I can
also send you the work around=20 instructions.</STRONG></P>
<P><STRONG>Jerry</STRONG> </P>
<P><B>----- Original Message -----</B></P>
<P></P><B>From</B>: "NICKLAS, Christian" =
<christian.nicklas@ser.de>=20
<P></P><B>Date</B>: Wednesday, March 8, 2006 8:12 am=20
<P></P><B>Subject</B>: AW: Workflow Stops without error in background =
task=20 statusready=20
<P></P>
<P></P>> HI Mike, <BR>> Hi All <BR>> <BR>> yes there are =
some=20 simultaneous forks in Definition. One in the <BR>> main flow, and
= two in=20 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=20 make at the end <BR>> an update on a czustom-table. In
the next = task a=20 background step <BR>> updates the same database.
<BR>> Can this = be the=20 program? Commit work is not set in the dialog
or <BR>> background = task=20 <BR>> <BR>> Regards <BR>> <BR>>
Christian Nicklas <BR>> = <BR>> <BR>> -----Urspr=FCngliche
Nachricht----- <BR>> Von:=20 sap-wug-bounces@mit.edu
[sap-wug-bounces@mit.edu] Im Auftrag <BR>> = von Mike=20 Pokraka <BR>>
Gesendet: Mittwoch, 8. M=E4rz 2006 14:45 <BR>> An: = SAP=20 Workflow
Users' Group <BR>> Betreff: Re: Workflow Stops without = error in=20
background task <BR>> statusready <BR>> Uh, hold on. You say =
RSWERRE=20 restarts it. So in other words they <BR>> SHOULDall restart =
themselves=20 after a while (20 minutes)... yes? <BR>> <BR>> In that
case = might it be=20 some kind of locking conflict? - pick your <BR>>
process apart for=20 simultaneous forks or DB updates which might <BR>>
still be = <BR>> active=20 or other similar things. <BR>> How is
RSWERRE scheduled (SWWD)? = <BR>>=20 <BR>> Failing that, OSS. <BR>>
<BR>> Cheers, <BR>> Mike = <BR>>=20 <BR>> NICKLAS, Christian
wrote: <BR>> > Hi all <BR>> > = Hi Mike,=20 <BR>> >
<BR>> > that would be to easy ;-). <BR>> > = It is a=20
background task and background method - in SWI2_ADM1 <BR>> there is =
not=20 <BR>> > entry. But ii SWIA it can be processed! <BR>> > =
<BR>>=20 > So it is becoming more and more strange and that is the
reason = <BR>>=20 why I <BR>> > cannot find a solution? <BR>>
> <BR>> = > But=20 maybe I am on the correct way with report
RSWWERRE? When I <BR>> = start the=20 <BR>> > report manually after
10 minutes when the workitem was = created,=20 <BR>> the flow <BR>>
> continues. <BR>> > <BR>> > = Anybody=20 any ideas what the
problem could be? <BR>> > <BR>> > = Regards=20 <BR>> >
<BR>> > <BR>> > Christian Nicklas | Prof. = Services=20 SAP
Workflow <BR>> > SER Solutions Deutschland GmbH <BR>> = >=20
<BR>> > <BR>> > -----Urspr=FCngliche Nachricht----- = <BR>>
>=20 Von: sap-wug-bounces@mit.edu [sap-wug-bounces@mit.edu] Im Auftrag =
<BR>>=20 > von Mike Pokraka <BR>> > Gesendet: Mittwoch, 8.
M=E4rz 2006 = 13:32=20 <BR>> > An: SAP Workflow Users' Group <BR>>
> Betreff: Re: = AW: AW:=20 Workflow Stops without error in background
task <BR>> > status = ready=20 <BR>> > <BR>> > Duh, must
read posts more carefully. You = mentioned=20 SWIA before. <BR>> That
makes <BR>> > the answer simple: it's = not a=20 background task.
<BR>> > <BR>> > A task in READY status = won't show=20 an agent,
as it can be with <BR>> many people. <BR>> > Once = someone=20
executes it and changes status to STARTED, it will <BR>> show an =
<BR>>=20 > agent. <BR>> > <BR>> > Check your agent
assignments = on the=20 task. Check if they show up in <BR>> >
SWI2_ADM1 (tasks without = agents),=20 would indicate it's being <BR>>
routed to the <BR>> > wrong = people /=20 not a possible agent of the
task. <BR>> > <BR>> > Note, a=20 background task can be 'dialog'
even though there isn't <BR>> any = user=20 <BR>> > interaction.
What it means is that - with 'advance in = dialog'=20 <BR>> set - it
<BR>> > executes under the userID of the = previous task=20 as opposed
to WF- <BR>> BATCH.> This can be for authorization = reasons or=20
simply that you <BR>> want the 'last <BR>> > changed by' to =
reflect=20 the user who made a decision. <BR>> > <BR>> > Cheers,
= <BR>>=20 > Mike <BR>> > <BR>> > NICKLAS, Christian
wrote: = <BR>>=20 >> Hi Mike, <BR>> >> <BR>> >>
In SM13 and SM21 = no=20 entries are available. <BR>> >> After
setting the WI into = status=20 error I get no hits in <BR>> SWI2_DIAG to
<BR>> >> restart = the=20 process (when I set the whole WF into
error I get a <BR>> hit but = <BR>>=20 >> not possible to
restart the flow) <BR>> >> Only = thing what=20 works is in
transaction SWIA to execute without <BR>> agent>> = check=20 (also
here no agent is displayed in the column!) <BR>> >> = <BR>>=20
>> Regards <BR>> >> Christian <BR>> >> = <BR>>=20
>> Christian Nicklas | Prof. Services SAP Workflow <BR>> = >>
SER=20 Solutions Deutschland GmbH <BR>> >> <BR>> >> =
<BR>>=20 >> -----Urspr=FCngliche Nachricht----- <BR>> >>
Von:=20 sap-wug-bounces@mit.edu [sap-wug-bounces@mit.edu] Im Auftrag
<BR>> = >>=20 von Mike Pokraka <BR>> >> Gesendet:
Mittwoch, 8. M=E4rz 2006 = 12:31=20 <BR>> >> An: SAP Workflow
Users' Group <BR>> >> = Betreff: Re:=20 AW: Workflow Stops without
error in background <BR>> task status = <BR>>=20 >> ready
<BR>> >> <BR>> >> Duh, ignore me, = must read=20 posts
more carefully. You said there <BR>> aren't>> any = <BR>>=20
>> conditions. <BR>> >> Can you restart them as = described?
If=20 so it would point towards <BR>> a basisy <BR>> >> problem.
= Else=20 you can also check for update failures - SM13. <BR>> System log
= <BR>>=20 >> SM21 may also reveal some hints. Check around the
time the = task is=20 <BR>> >> created. <BR>> >> <BR>>
>> Cheers, = <BR>> >> Mike <BR>> >> <BR>>
>> Mike = Pokraka wrote:=20 <BR>> >>> What about the
conditions? SWI1_COND implies you = have a=20 <BR>> condition on <BR>>
>>> the <BR>> >>> = task.=20 That does exactly what you
describe - task won't start <BR>> until = the=20 <BR>> >>>
condition is met. <BR>> >>> <BR>> = >>> NICKLAS,
Christian wrote: <BR>> >>>> Hi = Mike=20 <BR>>
>>>> <BR>> >>>> thanks fort he = hint. In=20 SM58
everything is fine. For this <BR>> background>>>> = tasks=20
<BR>> >>>> no conditions are maintained. The SWU3 looks =
good=20 for the <BR>> >>>> runtime-environment. <BR>>=20
>>>> But for me it seems that something is wrong with the =
runtime,=20 <BR>> because>>>> it <BR>> >>>>
happens = very=20 often that the Background-WI's stop in status ready.
<BR>> = >>>>=20 <BR>> >>>> Regards <BR>>
>>>> Christian = <BR>>=20 >>>> <BR>>
>>>> <BR>> >>>> = <BR>>=20 >>>>
-----Urspr=FCngliche Nachricht----- <BR>> = >>>>=20 Von:
sap-wug-bounces@mit.edu [sap-wug-bounces@mit.edu] Im <BR>>=20
>>>> Auftrag <BR>> >>>> von Mike Pokraka =
<BR>>=20 >>>> Gesendet: Mittwoch, 8. M=E4rz 2006 11:23
<BR>>=20 >>>> An: SAP Workflow Users' Group <BR>> =
>>>>=20 Betreff: Re: Workflow Stops without error in background
task <BR>>=20 status>>>> ready <BR>> >>>>
<BR>>=20 >>>> Hallo Christian, <BR>> >>>>
Background = tasks=20 do not have agents, so what you are seeing in <BR>>
= >>>>=20 SWI1_COND <BR>> >>>> is correct.
Interesting you = mention=20 SWI1_COND - have you set a <BR>>
>>>> condition = <BR>>=20 >>>> for the task? Is
it fulfilled? <BR>> = >>>>=20 Conditional tasks are
evaluated/executed by a background job, <BR>> = make>>>> sure
<BR>> >>>> it's scheduled and = running. <BR>>
>>>> <BR>> >>>> Also, = have a look=20 in SM58
for any problems. <BR>> >>>> Something else to = try is=20
set the task to error using SE37, FM <BR>> >>>>=20
SWW_WI_STATUS_CHANGE_NEW (I think... something like that), <BR>> = and
try=20 <BR>> >>>> restart <BR>> >>>> with =
SWI2_DIAG.=20 <BR>> >>>> <BR>> >>>> MfG,
<BR>>=20 >>>> Mike <BR>> >>>> <BR>> =
>>>>=20 NICKLAS, Christian wrote: <BR>> >>>>>
Hi all, = <BR>>=20 >>>>> <BR>> >>>>>
<BR>>=20 >>>>> <BR>> >>>>> I have
implemented = a=20 workflow running on ERP-Release ECC 5.0 <BR>>
>>>>>=20 (SAP_BASIS <BR>> >>>>> 640; Patch
Level 0009; = SAPKB64009;=20 SAP Basis Component). <BR>>
>>>>> <BR>>=20 >>>>> When testing the
solution sometimes the workflow = stops=20 <BR>> without any <BR>>
>>>>> error <BR>>=20 >>>>> in background
tasks. This happens in different = background=20 <BR>> tasks from
<BR>> >>>>> time to time and in = other=20 runs it works.
<BR>> >>>>> <BR>> = >>>>> At=20 the
workflow log the status of the background task is in <BR>>=20
status>>>>> ready. The information at the task says =
"Execution=20 <BR>> will continue in <BR>> >>>>>
background" = (Message=20 no. SWF_RUN609). <BR>> >>>>>
<BR>> = >>>>>=20 There is no error in the log. In ST22 no
dump exists. Also the = <BR>>=20 >>>>> administrative
tasks (SWPR - Restart after error = / SWPC -=20 <BR>>
Restart>>>>> after <BR>> = >>>>>=20
SystemCrash) are not possible. SWU_OBUF also does not work. <BR>>=20
>>>>> <BR>> >>>>> <BR>>=20
>>>>> <BR>> >>>>> The only thing = which
I=20 found was in transaction SWI1_COND. <BR>> For the <BR>>=20
>>>>> task <BR>> >>>>> there is no =
agent=20 available in the agent column (should be <BR>>
>>>>> = workflow-system)? <BR>> >>>>>
<BR>> = >>>>>=20 When I process and reactivate the
workitem in transaction <BR>> = SWIA the=20 <BR>> >>>>>
flow <BR>> >>>>> goes = on.=20 (WF_BATCH has SAP_ALL /
SAP_NEW) <BR>> >>>>> = <BR>>=20 >>>>>
<BR>> >>>>> <BR>>=20 >>>>> Any ideas and
help are appreciated. <BR>>=20 >>>>> <BR>>
>>>>> <BR>>=20 >>>>> <BR>>
>>>>> Christian Nicklas | = Prof.=20 Services SAP Workflow
<BR>> >>>>> SER Solutions = Deutschland=20 GmbH <BR>>
>>>>> <BR>> >>>>> = <BR>>=20
>>>>> <BR>> >>>>>=20
_______________________________________________ <BR>> =
>>>>>=20 SAP-WUG mailing list <BR>> >>>>>
SAP-WUG@mit.edu = <BR>>=20 >>>>>
http://mailman.mit.edu/mailman/listinfo/sap-wug = <BR>>=20
>>>>> <BR>> >>>> <BR>> =
>>>>=20 _______________________________________________ <BR>>
= >>>>=20 SAP-WUG mailing list <BR>> >>>>
SAP-WUG@mit.edu = <BR>>=20 >>>>
http://mailman.mit.edu/mailman/listinfo/sap-wug = <BR>>=20
>>>> <BR>> >>>>=20
_______________________________________________ <BR>> =
>>>>=20 SAP-WUG mailing list <BR>> >>>>
SAP-WUG@mit.edu = <BR>>=20 >>>>
http://mailman.mit.edu/mailman/listinfo/sap-wug = <BR>>=20
>>>> <BR>> >>> <BR>> >>>=20
_______________________________________________ <BR>> >>> =
SAP-WUG=20 mailing list <BR>> >>> SAP-WUG@mit.edu <BR>> =
>>>=20 http://mailman.mit.edu/mailman/listinfo/sap-wug <BR>>
>>> = <BR>>=20 >> <BR>> >> =
_______________________________________________=20 <BR>> >> SAP-WUG
mailing list <BR>> >> = SAP-WUG@mit.edu=20 <BR>> >>
http://mailman.mit.edu/mailman/listinfo/sap-wug = <BR>>=20 >>
<BR>> >> = _______________________________________________=20
<BR>> >> SAP-WUG mailing list <BR>> >> =
SAP-WUG@mit.edu=20 <BR>> >>
http://mailman.mit.edu/mailman/listinfo/sap-wug = <BR>>=20 >>
<BR>> > <BR>> >=20
_______________________________________________ <BR>> > SAP-WUG =
mailing=20 list <BR>> > SAP-WUG@mit.edu <BR>> >=20
http://mailman.mit.edu/mailman/listinfo/sap-wug <BR>> > <BR>> =
>=20 _______________________________________________ <BR>> >
SAP-WUG = mailing=20 list <BR>> > SAP-WUG@mit.edu <BR>> >=20
http://mailman.mit.edu/mailman/listinfo/sap-wug <BR>> > <BR>> =
<BR>> _______________________________________________ <BR>> =
SAP-WUG=20 mailing list <BR>> SAP-WUG@mit.edu <BR>>=20
http://mailman.mit.edu/mailman/listinfo/sap-wug <BR>> <BR>>=20
_______________________________________________ <BR>> SAP-WUG = mailing
list=20 <BR>> SAP-WUG@mit.edu <BR>>=20
http://mailman.mit.edu/mailman/listinfo/sap-wug <BR>>=20
</BLOCKQUOTE>------_=_NextPart_001_01C642CF.2B80D0C2--
</BLOCKQUOTE></BODY></HTML>