<div>Does SWI1_COND do exactly the same thing as RSWWCOND but on-line instead of in batch? Our problem appears to be that there are 67,000+ Wait Events (Conditions) waiting and SWWCOND picks all of these up, tries to process each one uses more and more memory, until after about 6 hrs runtime it ends in error.
</div>
<div> </div>
<div>If I could use SWI1_COND to process them in smaller groups, maybe I could get the number outstanding down from 67,000+ to a managable amount. If only there were more Selections on RSWWCOND!</div>
<div> </div>
<div>BTW, this is the SAP Wait Event in the Leave Approval Wf thats causing all this. So beware anyone in a HR environment with 120,000 employees requesting Leave likes theres no tomorrow!</div>
<div> </div>
<div>Any help gratefully received as I will return to this issue after Christmas.</div>
<div> </div>
<div>Andy</div>