Back ground job got strucked ,( WF-batch has SAP_ALL)

Kesari Katakam kesari.katakam at gmail.com
Fri Jul 22 11:27:35 EDT 2005


Manual Intervention...i meant was me going to Swi1 transaction , and 
selecting it and executing from the menu option " Execute Back Ground Work 
Item ".

the work flow step / task is perfectly alright in our case, it is a back 
ground task by denition...
 with best regards
Kesari
 On 22 Jul 2005 12:33:53 -0000, Raja Sekhar <rajakmca at rediffmail.com> wrote: 
> 
>  Hello ,
> Am sorry, I still didnt understand the problem.
> Does a work Item getting created for the task which u r saying as 
> BACKGROUND TASK. If so, just check ur Task Definition whethear u make the 
> task as an BACKGROUND TASK or not? 
> 
> Please make the problem clear.
> 
> What do u mean by MANUAL INTERVENTION...Am sorry...Am not able to 
> understand this sentence clearly..
> 
> Regards,
> Raja Sekhar
> 
> 
> On Fri, 22 Jul 2005 Kesari Katakam wrote : 
> >the problem is... the work flow should not get struck... the back ground
> >task should get executed automatically.. without manual intevention....
> >Hope i am clear..
> > could you please send me the solution..if you had faced the same
> >problem..!
> > with best regards
> >Kesari.
> >
> > On 7/22/05, Kjetil Kilhavn <KJETILK at statoil.com> wrote:
> > >
> > > And the problem is?
> > > I am asking because it sounds as if you were able to execute the stuck
> > > work item. Thus your last sentence doesn't really make sense because 
> you
> > > have already solved the problem. There doesn't seem to be a problem, 
> unless
> > > all work items of this type gets stuck.
> > > --
> > > Kjetil Kilhavn, Statoil KTJ IT BKS
> > >
> > > ------------------------------
> > > *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> > > Behalf Of *Kesari Katakam
> > > *Sent:* 21. juli 2005 20:53
> > > *To:* SAP Workflow Users' Group
> > > *Subject:* Back ground job got strucked ,( WF-batch has SAP_ALL)
> > >
> > > Hello all,
> > > In our work flow , a back ground job got struck ( Not in error ) , and
> > > the user WF-BATCH is having SAP_ALL .
> > > When we tried executing it by saying "Execute the Background work item 
> "
> > > it continues to next step.
> > > Could you please help me in solving this, what are the other 
> paramaters
> > > to be considered in this case.
> > > With best regards
> > > Kesari
> > >
> > > -------------------------------------------------------------------
> > > 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.
> > >
> > > _______________________________________________
> > > 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
> 
> 
> 
> <http://clients.rediff.com/signature/track_sig.asp> 
> _______________________________________________
> 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/20050722/c29f238d/attachment.htm


More information about the SAP-WUG mailing list