<BODY><P></P>
<P><B>Hi,</B></P>
<P><B>We've just gone through either a similar or the same problem. We're running ERP2005, NW2004S with CUA.</B></P>
<P><STRONG>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.</STRONG></P>
<P><STRONG>Jerry</STRONG> </P>
<P><B>----- Original Message -----</B></P>
<P></P><B>From</B>: "NICKLAS, Christian" <christian.nicklas@ser.de>
<P></P><B>Date</B>: Wednesday, March 8, 2006 8:12 am
<P></P><B>Subject</B>: AW: Workflow Stops without error in background task statusready
<P></P>
<P></P>> 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: SAP Workflow Users' Group <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: SAP Workflow Users' Group <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: SAP Workflow Users' Group <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: SAP Workflow Users' Group <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>> </BODY>