Task Stuck In Process

[Tom Olaf @ Spring]

Hi.
 
It seems the update task for the invoice transaction has not finished
(program RSM13000 is related to the update). This update is performed
asynchron to perform the actual update of the tables and locks the object.
When facing such a problem I have used the requested start option of the
activity definitions to delay the start of the background task for a few
minutes so that the update has finished. You can in addition or instead try
to lock the object in your method and create an exception that will lead to
reprocessing based on the error-monitoring job interval.
 
Regards
Tom
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Bibby, David
Sent: 4. februar 2004 12:57
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Task Stuck In Process
 
 
Michael
Thanks for your advice.
If I run it again, it runs and completes.
However, looking in SM58 there are entries in here for the workflows that
are stuck in process.
It says  "Object is blocked....<billing document no.>" Trans VF01 Prog
RSM13000.
Maybe the data the RSNAST00 needs is locked and a return code is not being
returned.
 
Many Thanks
David
 
 
-----Original Message-----
From: Michael Pokraka [mailto:workflow at quirky.me.uk]
Sent: 04 February 2004 11:16
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Task Stuck In Process
 
 
Hi David,
Can you reproduce it - i.e. if you reexecute the same task with the same
data
does it still get stuck? If so it's likely something with your report.
Otherwise check for short dumps or stuck TRFC's (SM58).
Cheers
Mike
 
--- "Bibby, David" <david.bibby at Linklaters.com> wrote:
> I have a single step task that intermittently gets stuck In Process.
> This step calls our own copy of report RSNAST00 and takes input
parameters.
> Has anyone had a similar problem calling a report in background and the
task
> getting stuck in process and if so, what did you do to solve the problem ?
>
> This one is difficult to debug as the problem only occurs a small
percentage
> of the time.
>
> Thanks
> David
>
>
> ________________________________________________
> This message is confidential. It may also be privileged or
> otherwise protected by work product immunity or other legal
> rules. If you have received it by mistake please let us know
> by reply and then delete it from your system; you should not
> copy the message or disclose its contents to anyone. All
> messages sent to and from Linklaters may be monitored to
> ensure compliance with internal policies and to protect  our
> business.
>
> Please refer to http://www.linklaters.com/regulation for
> important information on the regulatory position of the firm.
>
>