AW: AW: Workflow Stops without error in background task status ready

[Kjetil Kilhavn (KJETILK)]

It can still be background (type B) tasks, even if it is executable in SWIA, at least in R/3 46C.

When we had these problems the best thing to do proved to be to never change status. I simply executed the work items in SWIA (search for all type B items in status started without any date/time constraint). That worked just fine.
-- 
Kjetil Kilhavn, Statoil ØFT KTJ BAS DEV SAP
 

> -----Original Message-----
> From: sap-wug-bounces at mit.edu 
> [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mike Pokraka
> Sent: 8. mars 2006 13:32
> To: SAP Workflow Users' Group
> Subject: 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 [mailto: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 [mailto: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


-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.