[LIKELY JUNK]Re: [LIKELY JUNK]Task TS10007991 in Ready status on an around 30 minutes

[chandrasekhar valluri]

Hi,

This problem only occurs when SC has approvers. If there are no approvers
then the status is immediately changing to 'Approved' from 'Awaiting
approval'. But in both the cases(Without approvers & with approvers) the
task TS10007991 is same in sub-workflow WS10400051. This sub-workflow is
using in With approvers main workflow and without approvers main workflow.


Kindly suggest me this.


On Fri, Aug 14, 2009 at 4:49 AM, Dart, Jocelyn <jocelyn.dart at sap.com> wrote:

>  Hi Chandra,  The job variant is not relevant.  This is generated
> automatically.  You need to look for another cause as to why there is a
> delay - as you mentioned a difference in support packages I'd suggest you
> look at the notes relating to that task/workflow and generally SRM approvals
> between the two support packages.  Other than than you may need to debug to
> see  what is going on.
> Regards,
> Jocelyn
>
> P.S. Just a little cultural aside for your future information .... In most
> western societies it is usual to address people by their given name - i.e.
> Jocelyn - not by their family name - Dart - unless you are going to prefix
> it with their title e.g. Ms. Dart. To address someone by their family name
> without a title they should be male and preferably a close friend, never
> with females, otherwise it can be a little offensive.  And apologies for not
> spelling out your full name... I was assuming that the short form is Chandra
> as seems to be usual...
>
>  ------------------------------
>  *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *chandrasekhar valluri
> *Sent:* Friday, 14 August 2009 12:52 AM
> *To:* SAP Workflow Users' Group
> *Subject:* [LIKELY JUNK]Re: [LIKELY JUNK]Task TS10007991 in Ready status
> on an around 30 minutes
>
>   Hi Dart,
>
> Thanks for your reply.
> I have checked the job which you said. It was scheduled for every 20 mins.
> But the variant is &0000000000002. I have compared this server
> with Quality, here variant for this is &0000000000000. and status was
> also changing immediately from Awaiting approval to Approved. In Quality
> support package is SAPKIBKT11.
>
> This problem occurs recently after support pack "SAPKIBKT14"
> implementation.
> Previously working fine.
>
> Kindly suggest me how to overcome this.
>
> On Thu, Aug 13, 2009 at 4:53 AM, Dart, Jocelyn <jocelyn.dart at sap.com>wrote:
>
>>  Hi Chandra,
>> Standard behaviour if a background task does not complete successfully is
>> to recheck it using the SWWERRE job run - which occurs every 20 mins or so.
>> So really your problem is that the background update is taking a
>> looooooooong time.  I'd suggest you check your BADIs and make sure your
>> coding is performance efficient and not breaking any logical units of work.
>> Regards,
>> Jocelyn
>>
>>  ------------------------------
>> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
>> Behalf Of *chandrasekhar valluri
>> *Sent:* Wednesday, 12 August 2009 10:12 PM
>> *To:* SAP Workflow Users' Group
>> *Subject:* [LIKELY JUNK]Task TS10007991 in Ready status on an around 30
>> minutes
>>
>>   We are working on SRM 5.0
>>
>> We have a problem while updating the status TS10007991.
>> Once after completion of all the SC approvals the status of above task is
>> still in "Ready" status. It is taking around 30 minutes to update the
>> status.
>>
>> Is this issue with our workflow or with Basis problem?
>>
>> Kindly suggest me to solve this.
>>
>> --
>> Thanks & Regards,
>> Chandrasekhar V
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>
>
> --
> Thanks & Regards,
> Chandrasekhar V
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>


-- 
Thanks & Regards,
Chandrasekhar V
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090820/c6576c90/attachment.htm