How to customize JSP page in iSupport

Question

Hi,
I have worked on OA framework. But I have got a requirement to customize iSupport page in oracle apps. There is a Next button on page, I want to call one DB function by passing 2 parameters to this function. Get the result from that function and show the error message to user based in result of function.
This page is JSP page. I got the JSP page name from URL in browser. I view the source of that page and found following statement..
onclick="javascript:document.identifyproblem.JTFValidateFlag.value='Yes';*next*('identifyproblem', 'NEXTFROMIP'); return false " type="button">Next</button><img src="/OA_HTML/cabo/images/swan/t.gif" width="10" height="10"></td></tr></table>
"next" function is available in one .js file which is imported in above file.
function next(form, opcode)
if (opcode =='NEXTFROMCI' || opcode =='NEXTFROMIP') {
if (!checkContactPoint(form)) return;
if (checkRequiredField(form)) {
document.forms[form].IBU_CF_SR_OPCODE.value=opcode;
document.forms[form].submit();
else {
return;
If I want to change the functionality can I add my code in above "next" function?
Or I will have to change something in controller file of that page??

Answer 1

Hi Paraq,
if you want to extend a seeded Oracle E-Business suite page you should use the personalization framework combined with a custom controller. Personalisations are done via the ebusiness suite user interface and involve no coding and allow you to intergate custom components into the app.
Controller extensions are not recomended in E-Business suite however they are commonly implemented. You can personalise the page/region/table controller etc... to call your custom controller when they are invoked. See the OAF Personalization/Development guide for details on how to do this.
One problem you will have here is that if you want to modify an existing controller you will need the source code which would probably mean getting an Oracle consultant or you could decompile the class files, failing that if you can bypass the existing controller by personalizing a different aspect of the page i.e. a region or table that doesnt already have a controller then you might get away with it.
Keith