<div>Thanks Sergey!</div>
<div>That did it. This saved me (and hopefully others as well) quite a lot of time..</div>
<div> </div>
<div>-Mikko</div>
<div><br>Date: Mon, 27 Mar 2006 08:22:00 -0500<br>From: "Breslavets Sergey" <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sergey.breslavets@volvo.com">sergey.breslavets@volvo.com</a>
><br>Subject: RE: CATS rejection notification?<br>To: "SAP Workflow Users' Group" <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>Message-ID:
<br> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:6BB019DC392E364F8768B97BC61DDC880EF1FA31@usgson071.vcn.ds.volvo.net">6BB019DC392E364F8768B97BC61DDC880EF1FA31@usgson071.vcn.ds.volvo.net
</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>Hi Mikko,<br><br>the notification text is hardcoded (surprise!) in the abap code - function 'CATS_APPROVAL' which is being called from the method SET_STATUS of the class CL_GRID_APPROVAL_ACTEXP.
<br><br>I had the similar problem and to get around it i have created subclass of the CL_GRID_APPROVAL_ACTEXP and redefined method SET_STATUS to send my own notification.<br><br>You can also use ABAP event APPROVAL_REJECTED of the superclass to plug in your own handler for some follow-up processing.
<br><span></span><br>Best regards,<br>Sergey</div>