Work Items in are 'In Process'

Tue May 23 11:06:53 EDT 2006

Hi Alon,
You are correct, it should pick up background steps that are still in
status STARTED after a hardcoded 30 minutes.

However it doesn't change the status, but it will send a mail to the WF
administrator informing them of an item remaining in process. Presumably
this was designed so it won't abort items that take longer -
particularly with RFC-type WIs, they can be delayed in a TRFC queue or
whatever - in which case you don't want them to error.

For this reason I recommend a WF admin to also run a SWI1 to look for
incomplete BG tasks over a day old maybe once a week to make sure they
haven't missed any mails.

Cheers,
Mike

Alon Raskin wrote:
> Hi Miguel,
> 
> Thank you for the response. Yes my task is a background synchronous one
> so I think it should error. I will log an OSS.
>  
> Regards,
>  
> *
> *Alon Raskin*
> *e: **araskin at 3i-consulting.com* <mailto:araskin at 3i-consulting.com>
> *p: +1 207 409 4983*
> *
>  
> 
> ------------------------------------------------------------------------
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *Adao-Cruz, Miguel
> *Sent:* Tuesday, May 23, 2006 9:27 AM
> *To:* SAP Workflow Users' Group
> *Subject:* RE: Work Items in are 'In Process'
> 
> Hello Aron,
>  
> SWWERRE title is "Report for Restarting Work Items with Temporary
> Errors". So it main purpose is for restarting items with temporary
> erros. If it fales after X number of times (setting for entire system or
> at workflow level) then the temporary error becomes an Application error.
> The exception to this, is that the report also checks some workitems not
> with temporary erros but hanging. But, it only does it for background
> items (batch, flow, remote). Is your item a background one? Sync or not ?
>  
> Cheers.
>  
> ___________________________________________________________________________
> Miguel Adao-Cruz | *Capgemini* | London
> Technology Services
> SAP Application Architect
> 
> T.+44-870-238-2927 | Int.700 2927 | www.capgemini.com
> <file:///C:\Documents%20and%20Settings\madaocru\Application%20Data\Microsoft\Signatures\www.capgemini.com,DanaInfo=OWA.UKI.CAPGEMINI.COM+>
> 
> Join the Collaborative Business Experience
> ___________________________________________________________________________
> 
> ------------------------------------------------------------------------
> *From:* sap-wug-bounces at mit.edu on behalf of Alon Raskin
> *Sent:* Tue 23/05/2006 12:55
> *To:* 'SAP Workflow Users' Group'
> *Subject:* RE: Work Items in are 'In Process'
> 
> Hi Sherie,
>  
> Thanks for the response. Unfortunately, our work items are not suck for
> 'no reason'. I know exactly why they are stuck.
>  
> My problem is *that I expect the work item to go to ERROR status after a
> while and not remain 'In Process' for 4 days (5 now). *Am I wrong here
> or isn't SWWERRE supposed to change the status of a work item to ERROR
> if it has been 'In Process' for a certain amount of time?
>  
> Regards,
>  
> *
> *Alon Raskin*
> *e: **araskin at 3i-consulting.com* <mailto:araskin at 3i-consulting.com>
> *p: +1 207 409 4983 (please note new number)*
> *f:  +61 3 8610 1239 *
> ** 
> *The easiest way to integrate SAP with any mobile device*
> *http://www.themobileworkplace.com <http://www.themobileworkplace.com/>*
>  
> *
>  
> 
> ------------------------------------------------------------------------
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *Munday,Sherie J.
> *Sent:* Monday, May 22, 2006 10:55 AM
> *To:* SAP Workflow Users' Group
> *Subject:* RE: Work Items in are 'In Process'
> 
> Alon,
> We have had similar experiences with workitems getting "stuck" for no
> apparent reason since our upgrade to ECC 5.0.  We opened an OSS note,
> and were told to apply Note 924388.  Unfortunately our client was
> refreshed and I cannot recreate the problem, so I have to wait to be
> able to test to see if applying the note will work.  Maybe it will work
> for you.
> Best of Luck,
> Sherie
>  
> Sherie Munday
> Workflow Developer/Analyst
> Air Products & Chemicals, Inc.
> 
> ------------------------------------------------------------------------
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *Alon Raskin
> *Sent:* Monday, May 22, 2006 8:45 AM
> *To:* SAP Workflow Users' Group
> *Subject:* RE: Work Items in are 'In Process'
> 
> Hi Hans,
> 
> Thank you for the response.
>  
> I know why the work item is 'stuck'. That is not my question.
> What I was wondering about is why the work item status is still 'In
> Process'? I would have expect SWWERRE to change it to ERROR by now.
> 
> Regards,
>  
> *
> *
> *Alon Raskin*
> *e: **araskin at 3i-consulting.com* <mailto:araskin at 3i-consulting.com>
> *p: +1 207 409 4983*
>  
> *
> *
> 
> ------------------------------------------------------------------------
> *From:* sap-wug-bounces at mit.edu on behalf of Brilleman JOHANNES
> *Sent:* Mon 5/22/2006 08:45
> *To:* SAP Workflow Users' Group
> *Subject:* RE: Work Items in are 'In Process'
> 
> ------------------------------------------------------------------------
> Notice of Disclaimer: Please note that this e-mail, and the contents
> thereof, is subject to the Standard PetroSA e-mail Disclaimer which is
> located at http://www.petrosa.com/Content/380.html
> ------------------------------------------------------------------------
> Hi Alon,
>  
> please have a look on the dump log (ST22) of 4 days ago and check if
> that workitem did not produce a short dump.
>  
> Regards,
>  
> Hans
> 
>     -----Original Message-----
>     *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]*On
>     Behalf Of *Alon Raskin
>     *Sent:* Monday, May 22, 2006 2:22 PM
>     *To:* sap-wug at mit.edu
>     *Subject:* Work Items in are 'In Process'
> 
>     We have some work item in Production that have been 'In Process' for
>     about 4 days now. I expected that they would have gone into ERROR
>     status by now. Batch job SWWERRE is scheduled and running periodically.
>      
>     Is this an OSS or are we missing some configuration somewhere?
> 
>     Regards,
>      
>     * *
>     ** **
>     ***Alon Raskin***
>     ** **
>     ***e: **araskin at 3i-consulting.com* <mailto:araskin at 3i-consulting.com>**
>     ** **
>     ***p: +1 207 409 4983***
> 
>     The information contained in this electronic message and any
>     attachments to this message are intended for the exclusive use of
>     the addressee(s) and may contain proprietary, confidential or
>     privileged information. If you are not the intended recipient, you
>     should not disseminate, distribute or copy this e-mail. Please
>     notify the sender immediately and destroy all copies of this message
>     and any attachments.
> 
>     WARNING: Computer viruses can be transmitted via email. The
>     recipient should check this email and any attachments for the
>     presence of viruses. The company accepts no liability for any damage
>     caused by any virus transmitted by this email.
> 
>     www.wipro.com
> 
> ------------------------------------------------------------------------
> *The Petroleum Oil & Gas Corporation of South Africa (Pty) Ltd*
> trading as "*PetroSA*" Reg. No. 1970/008130/07.
>  
> *Directors:*
>  
> Dr P S Molefe (Chairman)
>  
> Mr S Mkhize (President and Chief Executive Officer),
>  
> Mr N G Nika (Executive), Mr A R Nkuhlu, Ms R J Huntley, Ms T C P Chikane,
>  
> Mr N H Gumede, Prof B Figaji, Mr A W Mjekula, Mr T O Mokwena,
>  
> Mr M B Damane, Ms P S V Ngaba (Company Secretary)
>  
>  
> ------------------------------------------------------------------------
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug