Invoking discoverer from OA framework page

Question

When i try to invoke the disoverer link from the home page via RUNDISCOVERER function, it works. But if we try the some from OA framwork page, it gave error (page cannot be displayed).
Is there any other function for this ?

Answer 1

Is this what counts as "support" for the OA framework?
I haven't been able to get my report to work properly, but at least I get a different error. In my case, the OA framework is truncating part of the parameter list. But since it looks like I may have gotten one step further, maybe what I did will help you:
1. Create a the pl/sql function per oracle's note (check metalink)
2. Create a "link" item in the OA Fwk "page" that calls a function.
3. For the "destination function" property of the "link" I used the name of the function I defined in the Oracle application.
NOTE, make sure when you save the Discoverer report in the DB, you use the name in File > Manage Workbooks > Properties for the report name. You also need to run the report in viewer to get the "workbook/wbk" number.
4. Write code in the page controller to add any parameters to your report. Here's a partial example:
public void processRequest(OAPageContext pageContext, OAWebBean webBean)
paramStringBuffer.append("parameters=wsk~28*qp_Project_Number_Parameter~");
OALinkBean linkDJ =
(OALinkBean)webBean.findIndexedChildRecursive("LinkToDJReport"); //Name of the link on whateverPG.xml
if (linkDJ != null)
linkDJ.setInvokeFunctionParams(paramStringBuffer.toString());
}//if
Note the parameters for the actual report should be written with "*" for "&" and "~" for equals.
5. Make sure the discoverer profile options are set up properly. It sounds like you already did that, but I changed ICX: Discoverer Default End User Layer Schema Prefix and ICX: Discoverer Parameters. The parameters I have are: po=10011110101101111111000&act=Apply Parameters&anlsdf=DD-MON-RRRR&pg=1
Of course this works fine for everywhere OTHER than the OA framework.
My issue is that from the OA framework page, when it's run from the server the link apparently only sends one parameter as part of the URL. I'm really disappointed to see you don't appear to have gotten any help for the relatively simple problem you're having. Maybe it's not too late for me to consider another product for my project.