Dependent Parameters in Discoverer Desktop

Hi All,
I am using discoverer 10g. i dont know how to filter the second parameter based on the first parameter selection in the Discoverer Desktop.
Regards,
Vishwanath

Hi,
It only exists in the Plus.
There are some differences between the plus and desktop for ex sub queries that can be done in desktop and not plus.
Any way if you'll create it in plus you will be able to use it in desktop but you cannot create it using the desktop edition.
Regards,
Tamir

Similar Messages

Is it possible to use dependent parameters in discoverer

Dear All,
Is it possible to use dependent parameters in discoverer... Like in RDF's(concurrent program)
Reddy.

Hi Hussain,
I think In Discoverer 4i there is no optional parameters Option.I wrote in condition(Desktop addition) like Org = :Org_param or org = DECODE(:"Org Parameter 1",'All',Org) .
At the time of running work book I am passing 'All' in parameter it's taking all orgs and giving org's data.
But in application i am not able give 'All' in parameters.
how to do optional parameters in 4i.
In 10G Optional parametes are there.
Regards,
Reddy
Edited by: Hanimi on Apr 15, 2009 5:39 AM

Cascading LOVs in discoverer desktop 10

Hi
Is it possible to create Cascading parameters in Discoverer Desktop 10?
i know the possibility in discoverer plus but didn't find the "filter the lov based on the selected condition" radio button while creating the paramenter in Desktop10.
Thanks

Hi,
You do not have to upgrade the desktop or administrator (you can if you like to).
can i install Plus as client?No, the plus is installed on IAS or weblogic
you can search this forum for links to download, and it will need installation and configuration.
the same schema, reports, configuration will work on Plus?Yes it will as long as the configuration is right.
Tamir

How to create optional parameters in discoverer 10.1.2

I am new to discoverer, Can any one tell me how to create optional parameters in Discoverer desktop edition in 10.1.2
I looked at the following thread which says optional parameters can be created in 10.1.2 but doesn't tell how tro create it
How to create optional parameters in Discoverer
Thanks in Advance

Hi.
In the thread you quoted Michael Armstrong-Smith says that optional parameters can be created in Plus but not in Desktop and that's true.
So your question "how to create optional parameters in Discoverer desktop" is already answered in that thread.
Assume that it is a typo and you wanted to ask how to create optional parameters in Plus.
Then the answer is simple: Just uncheck the "Require users to enter a value" checkbox when creating new parameter.
Regards Jakub

Discoverer Desktop Parameters

please help in how to change the parameter requiered or not in Discoverer Desktop, and if can't is applicable to do it through DB and how?
I have Discoverer Desktop 11g.
please your help?

Hello
To back up what the others have said, Desktop can only create mandatory parameters whereas Plus can create both optional and mandatory parameters. Interestingly, if you create an optional parameter in Plus and run the worksheet in Desktop the parameter remains optional and Desktop can handle it. However, you should not edit the parameter in Desktop.
Michael

Scheduling workbooks in discoverer desktop

I'm trying to figure out how to schedule workbooks to run and export the output to a folder in Discoverer Desktop, I see in many posts that it can be done easily, I just can't figure it out, can anyone help?
I did confirm with my DBA that we do have the DBMS_Job package installed.
When I click on schedule as a user I get the following message:
A workbook cannot be scheduled for the following reason(s) - summary refresh 'job_queue_processes' parameter is 0
I would appreciate any help you can offer.
Thanks,
Janet
email: [email protected]

Hi Janet
You do not need to have DBA privilegs to schedule workbooks and any user should be able to do this. Here is an article from my notes:
Setting up Workbook Scheduling
The workbook scheduling feature in Discoverer uses native features in the Oracle DBMS, and is therefore only available when running against the Oracle database. This feature uses the same highly scalable and reliable processing procedures ithin the kernel, since the summary management capability and the setup for both features is similar. These procedures use standard packages in the DBMS called DBMS_JOB.
To enable the processing procedures for workbook scheduling in Discoverer, follow these steps:
A. Grant Schedule Workbook Privilege to the user.
B. Confirm that DBMS_JOBS has been installed.
C. Specify result set storage.
D. Set the time period at which the process kicks in.
These procedures are described in the following sections:
A. Grant Schedule Workbook Privilege to the User
The user must be granted the Schedule Workbooks privilege in the Privileges dialog. Connect to the Administration Edition, and grant the Schedule Workbooks privilege in Tools->Privileges dialog.
B. Confirming that DBMS_JOBS is Installed
1. Log onto SQL*Plus as the Administrator, and execute the following SQL statement:
SQL> select * from all_objects where object_name='DBMS_JOB' and
object_type = 'PACKAGE';
If the statement returns no rows, use SVRMGRL to create the necessary packages.
2. From Windows XP or NT, select Start->Run.
3. Type in one of the following:
SVRMGRL
4. When in the DBA facility, type CONNECT INTERNAL.
5. Execute the following SQL statement:
SQL> start <ORACLE_HOME>/rdbms/admin/dbmsjob.sql;
SQL> start <ORACLE_HOME>/rdbms/admin/prvtjob.plb;
C. Specifying Result Set Storage
When a scheduled workbook is run, the results are stored in database tables
within the database. Result set data created as part of the workbook
scheduling process may be stored in one of two areas:
the user's own schema or a centralized schema.
User's Schema
In order to enable workbook scheduling in the user's own database schema,
the user requires the following database privileges:
Create Procedure
Create Table
Create View
To grant these privileges, do the following:
1. Log onto SQL*Plus or SQLDBA as the Database Administrator.
2. Type the following:
SQL> Grant CREATE PROCEDURE to <USER>;
SQL> Grant CREATE TABLE to <USER>;
SQL> Grant CREATE VIEW to <USER>;
SQL> Grant EXECUTE ANY PROCEDURE to <USER>;
SQL> Grant SELECT on SYS.DBMS_JOB to <USER>;
SQL> Grant EXECUTE on SYS.V$_PARAMETER to <USER>;
where <USER> is the userid of the person who is to be allowed to schedule
workbooks.
These privileges must be granted directly to the user and not to a database
role.
Advantages: A database limit can be specified on the maximum amount of data a
user can store in the database. If the result set is stored under the user's
schema, then you keep control over the maximum amount of space one individual
user can fill with result sets. If the user creates a scheduled workbook that
fills that space, it affects only his/her own scheduled workbook.
Disadvantage: The user is required to have the above privileges in the database.
Repository User's Schema
In order to enable workbook scheduling using a centralized repository user's
schema, the SQL script batchusr.sql must be run in SQL*Plus or SQLDBA as a
database administrator (such as, SYSTEM). This script creates a new user that
is granted the above privileges.
In addition, the administrator of the EUL must change the user so that the
Repository User property is pointing to the repository user's schema just
created. The centralized repository user's schema may be customized by the
database administrator for space management purposes and underlying data access.
NOTE: SELECT ANY TABLE access is given by the script batchusr.sql,
but this may be limited provided the repository user's schema is
granted access to the underlying data that will be accessed for
workbook scheduling.
The repository user created will not be able to directly schedule a workbook
through the User Edition.
Advantages: Each user does not need DML procedures to run scheduled workbooks.
Disadvantages: One user can potentially run a scheduled workbook that fills the
available result set space, preventing other scheduled workbooks from running
until it is cleared.
D. Setting the Start Time for Workbook Processing
The workbook processes run within the database on the server, and are
controlled by parameters in the initialization file of the Oracle DBMS
- the INIT<SID>.ORA file.
To limit the number of processing requests that can run simultaneously:
The parameter job_queue_processes specifies the number of concurrent processes to use to process DBMS_JOB. It controls the number of processing requests that can be handled simultaneously. The default value is zero, which means processing requests will not be created. You should set it to a minimum of 2 or more if you have any other applications that use DBMS_JOB.
You need more than one job queue process, because if one job fails for any reason, it may keep getting re-submitted, and thus, prevent everything else in the queue from being completed. If you want to have 10 simultaneous processing requests handled, then you will need to set this to 10.
The INIT<SID>.ORA parameter job_queue_interval is the time in seconds that controls how often the job processes wake up to process pending jobs. The default is 60, which is quite frequent. What you set this to depends on how frequently you want the process to wake up and serve the requests that have been made. Oracle recommends that you update the 60 seconds default to at least 10 minutes (a value of 600).
NOTE: This parameter also affects summary management.
To enable these parameters:
1. Locate the INIT<SID>.ORA file.
For example, on Personal Oracle7 the INIT<SID>.ORA file is held in
<ORACLE_HOME>\database. Its default name is INITORCL.ORA where ORCL is
the <SID> name.
2. Enter 2 lines into the file. For example:
job_queue_processes = 2
job_queue_interval = 600 (equivalent to 10 minutes)
NOTE: The summary management and workbook scheduling features both use this scheduling capability within the Oracle DBMS. The interval you specify and the number of concurrent requests affect both features.

Discoverer Desktop crash

When trying to open a report created by a colleague, Discoverer immediately throws a Windows (Vista 32Bit) error that "Oracle Discoverer Desktop has stopped working". I click close program, and Discoverer closes. It's a very simple report so I recreated it yesterday, ran it fine, could change parameters for different outputs, no problems. This morning I log in and when trying to open the newly created report from yesterday, same error. No exception, no memory pointers, nothing, just the Win error that it has stopped working.
Anyone seen this before? Running Discoverer Desktop v 10.1.2.3 Client v 10.1.2.55.26.

My colleague was able to open and modify the report that I created without issue so I suspect the report is alright, perhaps my installation? Odd that I can run many other reports just fine in the same environment and that this one ran fine from development, but as soon as I closed it to reopen, no luck.

How to use Oracle OAB Fast Formulas in Discoverer-desktop [ for reporting]

Hi,
Can anyone tell me how to use a fast formula in discoverer-desktop [for reporting]. Currently, we have a disco-report that calcuates the 'monthly salary', but we don't want to use that. Instead, we have a custom fast-formula [xx_oab_monthly_salary] which has the conditions and calculations that we need.
I want to use that formula in discoverer-desktop directly and get the monthly-salary.. i.e., someone needs to create a folder under the business area and add it i believe.. the formula internally calls a function.
when i checked about this with my dba - he said, he can add the 'function', but not the formula. and i need to write the calculation part...
does anyone know how to add it...there shud a way right...
i do not have access to the technical-stuff here..
someone said ["you can wrap the FF_EXEC.run_formula call into your own pl/sql function and map this function into the EUL so that the formula can be called from a workbook.", but this talks about pl/sql-do we need pl/sql
for this].
also, someone else said [ some fast formulas need specific contexts to be set. Depending on whether the fast formula below the only fast formula that you want to recreate in Discoverer.
For a single formula, in general my recommendation is to recreate the fast formula instead of using the ff_exec call].
any quick answers greatly appreciate..
thx,

Hi,
That's right you need to develop the pl/sql function outside of Discoverer using a pl/sql tool or just SQL*plus. I haven't an example to hand, but can dig one up if you need it. Once you have the function developed you can map it into the EUL using Discoverer Administrator. It will then be available to Discoverer Desktop/Plus as a database function when creating calculations. So you can then just add the calculation to an existing or new report.
Alternatively, you can build the pl/sql function into a view and load the view into a new folder using Discoverer Admin.
Rod West

Dependent LOVs in Discoverer Admin

Hi All,
Can we create dependent LOVs in Discoverer. If yes can anyone throw some light that.
regards,
gt1982

Well, let me try to clarify what Tamir said. I think you probably will need to do some setup work in Administrator. I am assuming that you want to do something like this in a worksheet - The user first clicks the LOV indicator on the Region parameter and picks a region from the Region LOV (say they pick the East region value), and then based on that region value, when they click on the City parameter LOV icon, the list of cities they see is filtered so that they only see cities in the East region (say New York City and Boston). To do this correctly in a worksheet, you need to define an Item Hierarchary in Discoverer Administrator. The two parameters must have some kind of relationship in the database to make this work.
Then once you have the item hierarchy defined, the rest of your work is in Discoverer Plus. You create the first parameter in the worksheet. In my example, you would create the Region parameter first. Next you would create your second parameter (in my example, that would be the City parameter). When creating the second parameter, that is when that section on the parameter window ("Do you want to filter the list of values for this parameter") comes into play. You will want to select the "Filter the list of values based on the selected conditions" option, and then find the condition name (for the Region parameter created condition) and select that condition. The term Oracle uses for this is "Cascading Parameters". So if you search on that term in the Discoverer Plus user guide, that will give you more information on this process.
Now, you do have to be careful. Ideally the folder with the relationship between the two parameters is based on a master table, not a detail table. If based on a detail table, you can run into performance problems when clicking on the LOV icon for the second parameter. The system may take forever to try to build that second LOV.
But the process does work. I have used it a couple of times.
Hope this helps a bit. Good luck.
John Dickey

USE OF PARAMETERS IN DISCOVERER

Hi, from El Salvador my question is? in a query that have parameters, when customize the parameters, how can put TO_DATE(SYSDATE)-1 in default value ?

Hi,
You cannot more a worksheet, only a workbook. To move a workbook between instances you have to either use Discoverer Desktop and save the workbook to the desktop, or you can use the Discoverer Admin 4i command line and export the workbook to a .eex file then import the workbook into the new instance.
Rod West

Error in Inserting data in GTT in Discoverer Desktop

Hi,
I wanted to pass a user entered parameter in Discoverer Desktop as a parameters to the custome SQL query.
I came across a solution where in they are asking to create a separate sheet to take in input parameters from the user and create a condition where in you store the value enterd in a GTT. When i am using this approach i am getting an error message. You cannot perform DML operation in the function. I cam across thread in the forum wherein people are also discussing about the same approach. Can anyone help.
lnk: Passing multiple parameters into Custom Folder...
Thanks
Ashwini

Hi,
It is true that you cannot perform DML operations inside SQL (that is what discoverer do).
The way to work around it is to define the function that perform the insert as AUTONOMOUS_TRANSACTION
You should add the syntax to your function, for example:
CREATE OR REPLACE FUNCTION test1 RETURN INTEGER IS
i INTEGER;
PRAGMA AUTONOMOUS_TRANSACTION;
BEGIN
i := 1:
insert into t
select i from dual;
COMMIT;
RETURN i;
END test1 ;
BTW don't forget the commit although it's GTT and make sure you preserve rows on commit;
Tamir

Discoverer desktop aborts when passing parameter

Hi All,
I'm trying to pass parameters to a discoverer desktop workbook, using the following command:
C:\oracle\product\BIToolsHome_1\bin\dis51usr.exe /connect discover/discover@fincon_d10 /opendb FCONR09615 /parameter p_user 'FCON' /parameter session_id '26240255' /parameter p_dt_final '31/01/2008'
where FCONR09615 is my workbook. But when I execute this command discoverer desktop aborts!
When I manually open the wokbook and fill the parameters, it works just fine.
Any Ideas?
Thanks in advance,
Valentim

Hi Valentim
You don't seem to be telling Discoverer which worksheet to open. You need to use the sheet command.
Let me look at the rest of your command.
1. You appear to be calling Discoverer Desktop correct
2. The command /connect is correct with username/password@database
3. The /opendb command is correct so long as you have a workbook called FCONR09615 owned by the user discover
4. You seem to have 2 parameters: one called p_user and one called p_dt_final. I can't comment as to whether you are passing the correct string values as I don't know how you have defined the objects that the parameters are feeding. I can tell you that your parameters need to be called p_user and p_dt_final
Best wishes
Michael

Boolean Parameters in Discoverer

Hi,
I am doing parameters in discoverer with True/False values. Those values are not from database. It's just values for users to choose, and after that, it deals with select statement. How can I do it? Do you have any ideas to use thing like checkbox as the input parameter of discoverer?
Thanks,

Hi Michael,
Well, yes there is a way to automate the initialization. You can use a database or EUL post-login trigger to set the contexts to a default value. In fact, it is useful to have 'session initialised' context, initially, set to FALSE. Then in your parameter initialization sheet you set the context to TRUE using a hidden calculation. Then in your report you can check when the parameters have been initialized and raise a custom exception to prompt the user to run the parameter initialization sheet if the parameters have not been set.
This approach works well, but some care is needed. Discoverer plus caches SQL query results and when a workbook is opened and exactly the same SQL has been run before it will use the results from the cache without realising that the context and changed and the query needs to be rerun. A refresh of the workbook usually fixes the problem.
Also if you are using this approach to generate context sensitive LOVs, you will find that Discoverer Desktop usually caches the LOVs and therefore the LOV does not change when the context is changed.
Another useful technique is to initialise a context to different values for different users. You can then use this context in the report to reduce the complexity of the SQL and improve performance.
Best wishes,
Rod

Discoverer report - Output from Discoverer plus is not the same as Discoverer desktop

As a part of Upgrade project we are migrating the discoverer reports from 11i (11.5.10.2) to R12 (12.1.3) .After migrating to R12, for a custom discoverer report the output given by discoverer desktop is correct (24 rows for a scenario). But the report output from Discoverer plus does not show the credit transactions (2 rows). The output from Discoverer plus shows only 22 rows (24 - 2), which is incorrect. The query is the same in Discoverer desktop and Discoverer plus.
Please let me know why these transactions that are appearing when the report is run from discoverer desktop are not appearing in discoverer plus. Is there any setup in discoverer plus for this?
Regards,
Brajesh

Pretty hard to answer a question like this. Best bet would be to copy the existing discoverer plus book and start removing conditions, fields, etc until those two rows from desktop show up and see if you can work it out.

Checkbox in discoverer desktop edition

Hi,
The query we are executing created for cross tab report have plenty of views and is returning null data which needs apps intialization which cannot be done from discoverer.
I think loging into Discoverer desktop edition with oracle applications user would resolve the same.
I have checked the checkbox in desktop edition and logged in as operations/welcome. but it is showing as invalid user name /password.
please help in setup that must required to check and login to oracle applications user. Also Provide if there is any alternative.
I would be very much thankful if you could help me on this.
Best Regards,
Katty.
Edited by: karthik.thadakamalla on May 10, 2009 11:49 PM

Hi,
The apps initialization can be done by Discoverer provided that you are connecting to an Apps mode EUL with an applications username and password.
You must specify that you want an Apps mode EUL when the EUL is created. Then when you connect to Disco Admin as the owner of the EUL you will be able to grant access privs and security to the Application users and responsbilities.
If you have an apps mode EUL and still get an invalid username/password then this could be because the application is running in secure mode. Then you need to copy the .dbc file to a local directory. Search this forum for details on how to do this.
Rod West

Dependent Parameters in Discoverer Desktop

Similar Messages

Maybe you are looking for