RSWWCOND

[yves.lebacq@skynet.be]

Hi Andy,

I confirm from Mike (is really necessary...). We got some experience from this batch.
It spends around 2 or 3 seconds of runtime but sometime (really rarely) it take more than one half hour.... We have not yet identified why and checked in the Oss note without real success (four our system 4.7).
This job sound like handling the conditions rules, but not the case, it is checking the rule that you can set in the step of workflow.

Hope this help you.

Yves.






------=_Part_11997_5657537.1166633687227Can anyone explain what exactly RSWWCOND does? I don't see it but does ithave anything to do with EVENTS?Anyone had issues with it taking 6hrs to run? We have a high volumeenvironment (380,000 WI's in 1.5 months). and SWWCOND is taking 6hrs torun.It appears to select all none complete status WI's from SWWWIHEAD whichreturns 45,000 WI's here and then takes a long time to process each one.Andy------=_Part_11997_5657537.1166633687227
Can anyone explain what exactly RSWWCOND does?  I don't see it but does it have anything to do with EVENTS?

Anyone had issues with it taking 6hrs to run?  We have a high volume environment (380,000 WI's in 1.5 months).  and SWWCOND is taking 6hrs to run.

It appears to select all none complete status WI's from SWWWIHEAD which returns 45,000 WI's here and then takes a long time to process each one.

Andy
------=_Part_11997_5657537.1166633687227----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061220/1e29e419/attachment.htm