AW: Workflow Stops without error in background task statusready

Stoicof, Dan dan.stoicof at gwl.com
Wed Mar 8 11:41:38 EST 2006 

Hey Jerry,
 
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?
 

Dan Stoicof 
SAP Workflow/ABAP Team 
GREAT-WEST LIFE and ANNUITY 




-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at 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  

----- Original Message -----



From: "NICKLAS, Christian" <christian.nicklas at ser.de> 



Date: Wednesday, March 8, 2006 8:12 am 



Subject: AW: Workflow Stops without error in background task statusready 





> HI Mike, 
> Hi All 
> 
> yes there are some simultaneous forks in Definition. One in the 
> main flow, and two in each subflows. After the deletion of the 
> forks still the same problem. 
> 
> But the lock can be the reason. In a dialog task I make at the end 
> an update on a czustom-table. In the next task a background step 
> updates the same database. 
> Can this be the program? Commit work is not set in the dialog or 
> background task 
> 
> Regards 
> 
> Christian Nicklas 
> 
> 
> -----Ursprüngliche Nachricht----- 
> Von: sap-wug-bounces at mit.edu [sap-wug-bounces at mit.edu] Im Auftrag 
> von Mike Pokraka 
> Gesendet: Mittwoch, 8. März 2006 14:45 
> An: SAP Workflow Users' Group 
> Betreff: Re: Workflow Stops without error in background task 
> statusready 
> Uh, hold on. You say RSWERRE restarts it. So in other words they 
> SHOULDall restart themselves after a while (20 minutes)... yes? 
> 
> In that case might it be some kind of locking conflict? - pick your 
> process apart for simultaneous forks or DB updates which might 
> still be 
> active or other similar things. 
> How is RSWERRE scheduled (SWWD)? 
> 
> Failing that, OSS. 
> 
> Cheers, 
> Mike 
> 
> NICKLAS, Christian wrote: 
> > Hi all 
> > Hi Mike, 
> > 
> > that would be to easy ;-). 
> > It is a background task and background method - in SWI2_ADM1 
> there is not 
> > entry. But ii SWIA it can be processed! 
> > 
> > So it is becoming more and more strange and that is the reason 
> why I 
> > cannot find a solution? 
> > 
> > But maybe I am on the correct way with report RSWWERRE? When I 
> start the 
> > report manually after 10 minutes when the workitem was created, 
> the flow 
> > continues. 
> > 
> > Anybody any ideas what the problem could be? 
> > 
> > Regards 
> > 
> > 
> > Christian Nicklas | Prof. Services SAP Workflow 
> > SER Solutions Deutschland GmbH 
> > 
> > 
> > -----Ursprüngliche Nachricht----- 
> > Von: sap-wug-bounces at mit.edu [sap-wug-bounces at mit.edu] Im Auftrag 
> > von Mike Pokraka 
> > Gesendet: Mittwoch, 8. März 2006 13:32 
> > An: SAP Workflow Users' Group 
> > Betreff: Re: AW: AW: Workflow Stops without error in background task 
> > status ready 
> > 
> > Duh, must read posts more carefully. You mentioned SWIA before. 
> That makes 
> > the answer simple: it's not a background task. 
> > 
> > A task in READY status won't show an agent, as it can be with 
> many people. 
> > Once someone executes it and changes status to STARTED, it will 
> show an 
> > agent. 
> > 
> > Check your agent assignments on the task. Check if they show up in 
> > SWI2_ADM1 (tasks without agents), would indicate it's being 
> routed to the 
> > wrong people / not a possible agent of the task. 
> > 
> > Note, a background task can be 'dialog' even though there isn't 
> any user 
> > interaction. What it means is that - with 'advance in dialog' 
> set - it 
> > executes under the userID of the previous task as opposed to WF- 
> BATCH.> This can be for authorization reasons or simply that you 
> want the 'last 
> > changed by' to reflect the user who made a decision. 
> > 
> > Cheers, 
> > Mike 
> > 
> > NICKLAS, Christian wrote: 
> >> Hi Mike, 
> >> 
> >> In SM13 and SM21 no entries are available. 
> >> After setting the WI into status error I get no hits in 
> SWI2_DIAG to 
> >> restart the process (when I set the whole WF into error I get a 
> hit but 
> >> not possible to restart the flow) 
> >> Only thing what works is in transaction SWIA to execute without 
> agent>> check (also here no agent is displayed in the column!) 
> >> 
> >> Regards 
> >> Christian 
> >> 
> >> Christian Nicklas | Prof. Services SAP Workflow 
> >> SER Solutions Deutschland GmbH 
> >> 
> >> 
> >> -----Ursprüngliche Nachricht----- 
> >> Von: sap-wug-bounces at mit.edu [sap-wug-bounces at mit.edu] Im Auftrag 
> >> von Mike Pokraka 
> >> Gesendet: Mittwoch, 8. März 2006 12:31 
> >> An: SAP Workflow Users' Group 
> >> Betreff: Re: AW: Workflow Stops without error in background 
> task status 
> >> ready 
> >> 
> >> Duh, ignore me, must read posts more carefully. You said there 
> aren't>> any 
> >> conditions. 
> >> Can you restart them as described? If so it would point towards 
> a basisy 
> >> problem. Else you can also check for update failures - SM13. 
> System log 
> >> SM21 may also reveal some hints. Check around the time the task is 
> >> created. 
> >> 
> >> Cheers, 
> >> Mike 
> >> 
> >> Mike Pokraka wrote: 
> >>> What about the conditions? SWI1_COND implies you have a 
> condition on 
> >>> the 
> >>> task. That does exactly what you describe - task won't start 
> until the 
> >>> condition is met. 
> >>> 
> >>> NICKLAS, Christian wrote: 
> >>>> Hi Mike 
> >>>> 
> >>>> thanks fort he hint. In SM58 everything is fine. For this 
> background>>>> tasks 
> >>>> no conditions are maintained. The SWU3 looks good for the 
> >>>> runtime-environment. 
> >>>> But for me it seems that something is wrong with the runtime, 
> because>>>> it 
> >>>> happens very often that the Background-WI's stop in status ready. 
> >>>> 
> >>>> Regards 
> >>>> Christian 
> >>>> 
> >>>> 
> >>>> 
> >>>> -----Ursprüngliche Nachricht----- 
> >>>> Von: sap-wug-bounces at mit.edu [sap-wug-bounces at mit.edu] Im 
> >>>> Auftrag 
> >>>> von Mike Pokraka 
> >>>> Gesendet: Mittwoch, 8. März 2006 11:23 
> >>>> An: SAP Workflow Users' Group 
> >>>> Betreff: Re: Workflow Stops without error in background task 
> status>>>> ready 
> >>>> 
> >>>> Hallo Christian, 
> >>>> Background tasks do not have agents, so what you are seeing in 
> >>>> SWI1_COND 
> >>>> is correct. Interesting you mention SWI1_COND - have you set a 
> >>>> condition 
> >>>> for the task? Is it fulfilled? 
> >>>> Conditional tasks are evaluated/executed by a background job, 
> make>>>> sure 
> >>>> it's scheduled and running. 
> >>>> 
> >>>> Also, have a look in SM58 for any problems. 
> >>>> Something else to try is set the task to error using SE37, FM 
> >>>> SWW_WI_STATUS_CHANGE_NEW (I think... something like that), 
> and try 
> >>>> restart 
> >>>> with SWI2_DIAG. 
> >>>> 
> >>>> MfG, 
> >>>> Mike 
> >>>> 
> >>>> NICKLAS, Christian wrote: 
> >>>>> Hi all, 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> I have implemented a workflow running on ERP-Release ECC 5.0 
> >>>>> (SAP_BASIS 
> >>>>> 640; Patch Level 0009; SAPKB64009; SAP Basis Component). 
> >>>>> 
> >>>>> When testing the solution sometimes the workflow stops 
> without any 
> >>>>> error 
> >>>>> in background tasks. This happens in different background 
> tasks from 
> >>>>> time to time and in other runs it works. 
> >>>>> 
> >>>>> At the workflow log the status of the background task is in 
> status>>>>> ready. The information at the task says "Execution 
> will continue in 
> >>>>> background" (Message no. SWF_RUN609). 
> >>>>> 
> >>>>> There is no error in the log. In ST22 no dump exists. Also the 
> >>>>> administrative tasks (SWPR - Restart after error / SWPC - 
> Restart>>>>> after 
> >>>>> SystemCrash) are not possible. SWU_OBUF also does not work. 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> The only thing which I found was in transaction SWI1_COND. 
> For the 
> >>>>> task 
> >>>>> there is no agent available in the agent column (should be 
> >>>>> workflow-system)? 
> >>>>> 
> >>>>> When I process and reactivate the workitem in transaction 
> SWIA the 
> >>>>> flow 
> >>>>> goes on. (WF_BATCH has SAP_ALL / SAP_NEW) 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> Any ideas and help are appreciated. 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> Christian Nicklas | Prof. Services SAP Workflow 
> >>>>> SER Solutions Deutschland GmbH 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> _______________________________________________ 
> >>>>> SAP-WUG mailing list 
> >>>>> SAP-WUG at mit.edu 
> >>>>> http://mailman.mit.edu/mailman/listinfo/sap-wug 
> >>>>> 
> >>>> 
> >>>> _______________________________________________ 
> >>>> SAP-WUG mailing list 
> >>>> SAP-WUG at mit.edu 
> >>>> http://mailman.mit.edu/mailman/listinfo/sap-wug 
> >>>> 
> >>>> _______________________________________________ 
> >>>> SAP-WUG mailing list 
> >>>> SAP-WUG at mit.edu 
> >>>> http://mailman.mit.edu/mailman/listinfo/sap-wug 
> >>>> 
> >>> 
> >>> _______________________________________________ 
> >>> SAP-WUG mailing list 
> >>> SAP-WUG at mit.edu 
> >>> http://mailman.mit.edu/mailman/listinfo/sap-wug 
> >>> 
> >> 
> >> _______________________________________________ 
> >> SAP-WUG mailing list 
> >> SAP-WUG at mit.edu 
> >> http://mailman.mit.edu/mailman/listinfo/sap-wug 
> >> 
> >> _______________________________________________ 
> >> SAP-WUG mailing list 
> >> SAP-WUG at mit.edu 
> >> http://mailman.mit.edu/mailman/listinfo/sap-wug 
> >> 
> > 
> > _______________________________________________ 
> > SAP-WUG mailing list 
> > SAP-WUG at mit.edu 
> > http://mailman.mit.edu/mailman/listinfo/sap-wug 
> > 
> > _______________________________________________ 
> > SAP-WUG mailing list 
> > SAP-WUG at mit.edu 
> > http://mailman.mit.edu/mailman/listinfo/sap-wug 
> > 
> 
> _______________________________________________ 
> SAP-WUG mailing list 
> SAP-WUG at mit.edu 
> http://mailman.mit.edu/mailman/listinfo/sap-wug 
> 
> _______________________________________________ 
> SAP-WUG mailing list 
> SAP-WUG at mit.edu 
> http://mailman.mit.edu/mailman/listinfo/sap-wug 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060308/e47f80f3/attachment.htm

More information about the SAP-WUG mailing list