Long Parameter In Discoverer?

Hi All ,
Is it possible to create long parameter in discoverer Plus.
Regards
mani

Hi,
If the column is a LONG data type then using this column in a condition is not supported by SQL and therefore your only alternative is to implement your own INSTR function in a PLSQL package.
Rod West

Similar Messages

How can I pass dynamic value as a user input parameter in discoverer?

Hi,
I have a requirement for a discoverer report like this: The report will display only details for Suppliers that have expired (or soon to be) Insurance details. That is the Expiration Date is less than or equal to the day the report is being run plus any days specified in the Number of Days in the Future Parameter.
The sample code as:
SELECT s.segment1 vendor_number
,s.vendor_name
,flv1.meaning classification
,pca.certificate_number
,pca.certifying_agency
,pca.expiration_date
,flv2.meaning status
FROM ap_suppliers s
,pos_bus_class_attr pca
,fnd_lookup_values flv1
,fnd_lookup_values flv2
WHERE pca.vendor_id = s.vendor_id
AND flv1.lookup_code = pca.lookup_code
AND flv1.lookup_type = pca.lookup_type
AND flv2.lookup_code = pca.class_status
AND flv2.lookup_type = 'POS_BUS_CLASS_STATUSES'
AND pca.expiration_date <= trunc(sysdate) + <No. of Days in the Future>
order by pca.expiration_date asc
Now the parameter is Number of Days in the Future (Enter the number days in the future to extract the data. This will default to 0).
Is it possible in discoverer to do so as in query i do that like a condition as pca.expiration_date <= trunc(sysdate) + <No. of Days in the Future>.
How can I pass <No. of Days in the Future> as a user input parameter in discoverer?
Please help.

Hi,
All you need to do is to create the condition in the discoverer instead of in the query.
Create a custom folder containing the following sq (note that i removed the condition)l:
SELECT s.segment1 vendor_number
,s.vendor_name
,flv1.meaning classification
,pca.certificate_number
,pca.certifying_agency
,pca.expiration_date
,flv2.meaning status
FROM ap_suppliers s
,pos_bus_class_attr pca
,fnd_lookup_values flv1
,fnd_lookup_values flv2
WHERE pca.vendor_id = s.vendor_id
AND flv1.lookup_code = pca.lookup_code
AND flv1.lookup_type = pca.lookup_type
AND flv2.lookup_code = pca.class_status
AND flv2.lookup_type = 'POS_BUS_CLASS_STATUSES'
Then create a discoverer report using this folder using all fields.
Create a new calculation as (use this exact syntax):
Sysdate + :No_of_Days_in_the_Future
Create a new condition:
pca.expiration_date <= <your calculation>
To complete it add a sort as you did in the SQL.
That's it.
Tamir

Validating Date parameter in discoverer

Hi
In the discoverer is it possible to validate or restrict the users to enter the wrong format of the date e.g. if the date format to be entered is dd-mm-yyyy, the system should not allow the users to enter mm-dd-yy,
Is it possible to put any validation?
As of now what is happening is discoverer is not telling me any thing after running for few minutes i am not getting any result, after that if i check i found that the date is in the wrong format
Regards
Ramesh Kumar S

Hi
If I may throw an aside in here. If your users are using 10.1.2 Plus there should be no need for users to key anything into any date parameter because Discoverer now has a calendar for this use. I find it much easier to teach my users to use a calendar than to try and teach them how to key dates in correctly.
One other thing you might want to consider if you have not already done so is to standardize a date format across your entire Discoverer installation. Then the date format will be obvious because its the same one they see all of the time.
Nevertheless, if you still want a mechanism to trap what users are keying it is possible to create functions that trap formats displaying appropriate error messages.
Best wishes
Michael

Alternatives to long parameter lists when calling methods

I've heard you shouldn't have more than 3 parameters when calling methods. What are the alternatives to long parameter lists when calling methods? Compounding parameters into new inner classes, declaring them as member fields? Which one is preferable?

Okay, I get it. But since it's late in the day, I'll share my additional wandering thoughts. And I'll just go ahead and preemptively slap myself for doing so. Ouch! There. So the rules are more like this:
1) Only use setters if the values in question are meant to be part of the state of an object.
2) In general, don't let external entities directly set the state of an object.
Which can be combined into:
1) In general, never use setters.
Which could be reworded to:
1) Only use setters in non-general situations.
Or:
1) Only use setters when setters are a good solution...which isn't very often...generally speaking...
Or if I were to infer when it's a good solution:
1) Only use a setter when it is useful to the caller and has no significant negative effects on the operation of the object nor the maintainability, size, or performance of the class...generally speaking...
Actually, you might just infer from here forward that the "generally speaking" is implicit to every rule, and is essentially the "There is an exception to every rule" rule. Which is an interesting rule because it can be applied to itself, resulting in a paradox...generally speaking...but I digress.
And then translated back to the original topic:
1) You can use a setter instead of a constructor argument so long as the value isn't needed at time of construction (or a default value will suffice) and it is useful for the caller to be able to use the setter and using the setter has no significant negative effects on the operation of the object nor the maintainability, size, or performance of the class.
But this won't quite cut it either. With the input of others, we could eventually devise a very concise rule, but it will end up being so long that on one will ever read it...making it an ideal candidate to be included in a legal document. Which will eventually find it's way into a very long scroll pane with a check box at the end exclaiming that you read the document, at which you will not be able to continue unless you check the check box...at which point, what do you do? After all, you are not a liar...generally speaking...
In summary, you could potentially use setters in some limited cases, but in the general sense, that's more of an option than a recommendation. :-)

ORA-06502: Long parameter

Hi all,
we´re using Oracle 9.2.0.4. We have a procedure with a long parameter.
When I execute this procedure with more than 32400 characters, the I got the following error:
ORA-06502: PL/SQL: numeric or value error: character string buffer too smallWha can I do to solve this?
thank you very much!!!!
[]´s

Hi,
I did this, but...
I got the error before the execute the first query.
When a decrease the size of string to 30000
characters I don't get any error.I don't know why it fails with the LONG datatype, but it is recommended to use CLOB instead of LONG.
Plus, the procedure call works, as expected, with CLOBs.
test@ora>
test@ora>
test@ora> --
test@ora> drop table tab_test;
Table dropped.
test@ora> drop procedure p_ins_tab_test;
Procedure dropped.
test@ora> drop sequence sq_tab_test;
Sequence dropped.
test@ora>
test@ora> --
test@ora> create sequence sq_tab_test;
Sequence created.
test@ora> create table tab_test (
2         id      number(9) not null,
3         id_2    number(9) not null,
4         dt      date not null,
5         data    clob);
Table created.
test@ora>
test@ora> --
test@ora> create or replace
2 procedure   p_ins_tab_test(
3     p_id_2                  in       tab_test.id_2%type,
4     p_data                  in       tab_test.data%type)
5 is
6 begin
7    insert into tab_test (id,id_2,dt,data)
8    values (sq_tab_test.nextval, p_id_2, sysdate, p_data);
9    commit;
10 end p_ins_tab_test;
11 /
Procedure created.
test@ora>
test@ora> --
test@ora> declare
2    v_data clob;
3    n_len   number;
4 begin
5    for i in 1..10 loop
6      v_data := v_data || dbms_random.string(1,4000);
7    end loop;
8    n_len := dbms_lob.getlength(v_data);
9    dbms_output.put_line('n_len = '||n_len);
10    --
11    p_ins_tab_test(100, v_data);
12 end;
13 /
n_len = 40000
PL/SQL procedure successfully completed.
test@ora>
test@ora> --
test@ora> select dbms_lob.getlength(data)
2    from tab_test
3   where id_2 = 100;
DBMS_LOB.GETLENGTH(DATA)
                   40000
test@ora>
test@ora>
test@ora>See the recommendation by Oracle, here -
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/datatype.htm#sthref3806
HTH
isotope

How to passing multiple values for a parameter of discoverer(url parameters

Hi All,
I am trying to pass multiple values for a parameter of disco report. I am trying to include my url for discoverer viewer report. the values has the following
'jeff,mark'
'sfophiee,angela'
Thanks and Regards
Venkat

Hello Venkat,
I know there are some problems with 10.1.2.0.2, maybe if you haven't done yet you can try with 10.1.2.2, assuming this version should be working for multiple parameter values :
OracleAS Discoverer 10.1.2.2 is installed with the following patch :
Patch 4960210 PLACEHOLDER BUG FOR AS/DS 10G R2 PATCH SET 2 10.1.2.2
So, once installed you can try adding your parameter as param_<parameter_name>='sfophiee,angela'
Hope this helps, otherwise feel free to log a Service Request to Support.
Best Regards,
Gianluca

How to pass parameter in Discoverer inner query PLZ give solution-URGENT

Hi All,
My need is I have a query in Disco Admin which has inner query as mention below:
select Net_Drawn_Amount,Undrawn_Amount,Business_Date from
(select * from t_FacilityExtract) A,
We are creating a workbook using Diso Plus and creating a parameter on Business_date which is date partitioned, but issue is in inner query(select * from t_FacilityExtract) is picking whole data which has millions of rows.
Plz help me how to filter inner query.
It is just a sample query.
Plz help me as soon as possible.
Thanks in advance
Amit

Hi,
Generally, using database contexts is the best way to pass parameters to folders defined in Disco Admin. You can look at this posts or download a article on using contexts with Discoverer from my website (www.cabotconsulting.co.uk).
Re: Implementing HR report in Discoverer
Re: Passing multiple parameters into Custom Folder...
Re: Parameters in SubQuery
Re: Passing Parameters to a discoverer folder using Note 282249.1
Rod West

Pass page parameter to discoverer portlet

Hi All,
iAS Version 10g(9.0.4)
I created worksheet(graph) using Discoverer plus having 4 parameters. I published the
discoverer graphs as discoverer portlet in Oracle portal. However for this worksheet it shows
(No parameters) in Page --> Properties --> parameter. I created simple parameter portlet with
4 items, this entry I need to pass to this discoverer portlet/Worksheet.
Any suggestion would help.
Thanks

Hi,
Thank for your reply.
We are using discoverer plus for relational data (Oracle 10g (Ias 9.0.4)).
Appreciate your feedback.
Raj
Hi, are you using discoverer plus for relational/OLAP
data?

Have such a long parameter value how do I pass it?

hi
I'm using 10g report. I have a MFC module that calls this oracle report using the link.
I can create a URL and pass the parameters, it works fine, but some occasions, I have to pass down very long (more than 10,000 characters) parameter value to the report. I know there is a limit on URL length.
In this case, what do i have to do?
I heard there is a way to use a parameter file instead.
This file doesn't have a size limit?
where can I find the document regarding this matter?
thanks

You need to contact Apple. Click here, phone them, and ask for the Account Security team, or fill out and submit this form.
(91888)

Wildcard parameter in Discoverer

Hello -
I have set up several parameters in a Discoverer 4i report. For some of the parameters I have set a condition of "LIKE" for the user input. For these parameters I would like the users to have the option of putting in a wildcard value (%) if they want to receive all values for the parameter. Is this possible?

Hi,
Database contexts may be able to help you here. Search this site for SYS_CONTEXT or check Re: Passing multiple parameters into Custom Folder...
Rod West

Parameter in Discoverer Administartor

Hi
In order to develop the output, i have created a view based on the base tables, there a about 2 millions records, the input parameter is a date, the output of the workbook is very slow, can i do the following..
1. Since the workbook is having date parameter , can the date parameter be directly refer to the column in the discoverer administrator... so that the performance can be reduced...
if possible let me know the steps to do this...
if there is any other method to increase the performance, do let me know...
Regards
Yram

Hi,
Database contexts may be able to help you here. Search this site for SYS_CONTEXT or check Re: Passing multiple parameters into Custom Folder...
Rod West

Discoverer Parameter : ICX: Discoverer Parameters

Hi Experts,
ICX: Discoverer Parameters profile option : is pointing to the EBS URL and is set as exitURL : *****
In the MOS : its is gives as : ICX: DISCOVERER PARAMETERS (ICX_DISCOVERER_PARAMETERS)
at the site, user or responsibility level and it will be added automatically to
the URL when an E-Business Intelligence (BIS/EDW) analysis workbook is called .
But i did not understand that ,
And i open the URL gives under this profile option and it is directing to Oracle apps Homepage but it saying as Discoverer Parameter.
Can someone please give me some more information on it why this profile option is pointing to EBS URL.
I am using EBS : 11510
Thanks In Advance

Please see these docs.
Using Discoverer 11.1.1 with Oracle E-Business Suite Release 11i [ID 1073963.1]
Using Discoverer 10.1.2 with Oracle E-Business Suite 11i [ID 313418.1]
How To Redirect Exit Button On Discoverer Pages To The Home Page Instead Of Login Page? [ID 1129933.1]
How To Redirect From Exit Link Of Discoverer Plus Or Viewer To EBS Home Page [ID 1458342.1]
Thanks,
Hussein

How to Pass Multiple Parameter to Discoverer Custom Folder Created in Admin

Hi,
I have done as describe in doc id (metalink) note 304192.1 and it's ok.
Now, my scope is to use the parameter declared in SETPARAMS not with the "=" condition but with "IN CLAUSE" (multipe values).
for example (SQL Inspector):
SELECT i106116 as E106116,i106117 as E106117,SUM(i106118) as E106118_SUM
FROM ( SELECT DS_COMMESSA AS i106116, DS_SCENARIO AS i106117, DS_VALUE AS i106118 FROM (select ds_commessa, ds_scenario, DS_VALUE
from dw_ods.ods_mbo_commessa
where DS_TIPO_COSTO='COSTI MEDI'
and ds_label='DIR'
and cd_scenario in (1,2)
and ds_commessa IN DW_ODS.SETPARAM.GET_PARAM1
union all
select 'Totale' as ds_commessa, ds_scenario, sum(DS_VALUE)
from dw_ods.ods_mbo_commessa
where DS_TIPO_COSTO='COSTI MEDI'
and ds_label='DIR'
and cd_scenario in (1)
and ds_commessa IN DW_ODS.SETPARAM.GET_PARAM1
group by ds_scenario
) CUO106102 ) o106102
WHERE (1 IN (DW_ODS.SETPARAM.SET_PARAM1(:"Commessa")))
GROUP BY i106116, i106117;
where the parameter "commessa" is used with "IN" operator.
Also tried to modifiy the SET_PARAM1 and GET_PARAM1 in order to use a "table of varchar2" ... but with no succes.
Help please

Rod,
for the first "problem" I find the solution on metalink (note 304192.1) and works fine (also combining SET and GET together)... otherwise I don't know how use this "workaround"...
for the multiple values on a single parameter (for example: Month='Jan,'Feb') I have tried to understand how DISCO pass these values to the SET function (I suppose like an array of varchar2) but don't work. After the first values (Jan) the reports stop... The problem in not how stored the values but understan how DISCO "pass/manage" these values (Jan,Feb)... Can u help me?
my actual SETPARAMS package body is (like metalink):
CREATE OR REPLACE PACKAGE BODY SETPARAM AS
FUNCTION SET_PARAM1(P1 IN VARCHAR2) RETURN NUMBER IS
BEGIN
param1 := P1;
return 1;
END;
FUNCTION GET_PARAM1 RETURN VARCHAR2 AS
BEGIN
return param1;
END;
FUNCTION SET_PARAM_MBO(p_anno IN VARCHAR2) RETURN NUMBER IS
BEGIN
anno := p_anno;
return 1;
END;
FUNCTION GET_PARAM_MBO RETURN VARCHAR2 AS
BEGIN
return anno;
END;
END SETPARAM;
----------------------------------------------------------------------

Date Parameter in Discoverer Custom Folder

Hi All,
We have a requirement where i need to filter sql query data in the where condition as below.
WHERE 1=1
AND TRANSACTION_DATE BETWEEN :PARAMETER_DATE-90 AND :PARAMETER_DATE-9
Can anyone of you help me on achieving that in discoverer.
Thank You
gt0990

Hi,
to do that inside the custom folder you can use DB contexts, read the following :
http://learndiscoverer.blogspot.com/2008/11/metalink-note-304192.html
Re: Passing multiple parameters into Custom Folder...
Tamir

Long parameter list in report call crashes forms

Hi,
I'm using Forms6i (client server) to call a report. The report has 15 parameters. I concat all the parameter into a string l_parameter_string, then call SET_REPORT_OBJECT_PROPERTY(l_report_object, REPORT_OTHER,l_other_parameters);
The report runs successfully, but when I close the report,forms crashes. This error seems to occur when the lenght of l_parameter_string > 160 chars, if the length of l_parameter_string < 160, the problem does not occur.
Has anyone come across a limitation on the length of a parameter string for calling a report,
thanks in advance

Parameter List pl_id cannot be sent in url as you are saying,
rather
you have to sent each parameter separately, with parameter name that must be defined at report.
e.g.
http://testserver:9002/reports/rwservlet?destype=cache&desformat=html&paramform=yes&report=\\testserver\forms\L00000001.rdf&userid=globe/oracle@globe&repserver=RptSvr_globe_asinst_1&p_val1=1243&p_val2=8987
In above url
p_val1 and p_val2 must be defined in your report to capture the data coming from Calling Form or Report.
Hope this will resolve your problem.

Long Parameter In Discoverer?

Similar Messages

Maybe you are looking for