LOV query in BOBJ

hi every one, i'm getting problem in LOV .. please any one tell me how to use LOV by applying particular condition ?
Activity: Using LOV Instructions
1. Edit the Maker object so that it only lists cars bought by clients from the UK.
2. Save and export the universe and then build a query in Web Intelligence using the Maker object.
3. Run the query to verify that only data from cars bought in the UK is displayed in the report.
i'm not getting the same as per the activity in the rich client.

when you display the LOV from object properties in the universe, can you see the desired result ?
did you try refreshing the LOV in the prompt screen?

Similar Messages

How to accessing current row report column value in Lov Query?

Hi,
which access methods (eg. bind variables, substitutions, ...) for getting the current row report column value can be used in the "Lov Query" property of a report column?
As what I know of and what I have read on the forum there are no bind variables for the report columns. For the "Link Text" property it seems that the column values exist as substitution strings (#COLUMN_NAME#). But they don't work in the Lov Query. => And would be good because of a hard parse each time the Lov query is executed.
The following post (Re: Simulating a correlated sub query in lov
is showing a solution to use package variables for temporary storage of the referenced value, but the only problem with that solution is that if a new record is added with the "Add rows to tabular form" process the package variable still contains the value from the last queried row! Is there a way (variable, APEX package, ...) to determine if the lov query is executed for a new record so that the package can return null?
I know that I could write the package in a way that the value is immediately cleared when lov_pkg.keyval is called (one time read), but then I would have to create several variables if I'm accessing the value multiple times in the query or in another query => I think an one time read solution would be very obscurely.
Thanks for your help
Patrick
http://inside-apex.blogspot.com

Hi Patrick,
I agree that it's a waste to continually use Ajax to go back to the server to get the contents of a dynamic select list.
There are no bind variables for any row item - but what you do have, as per my previous post, is the value of the data entered by the user in the first row. You can pass this into your application process (using get.add("VARIABLENAME", value)), which can use it to retrieve the correct LOV in your Ajax code - this will give you a "bind variable" that your process can use.
What you could do, however, is generate hidden select lists on your page - one for each possible LOV list and replace the contents of the new row's select list with the contents of the appropriate hidden select list. This is easy to do with javascript (using innerHTML functions). Obviously, though, the usefulness of this depends on the number and size of the select lists.
Even if you don't generate them to start with, you can keep a copy of any select lists returned by Ajax in the DOM for use on new rows. So, if you have retrieved a select list, you will have a copy of it in DOM which you can then copy into the new row. If you don't have the list in DOM, use Ajax to get it, store a copy of it and copy it into the new row.
Which method you use will depend on the number/size of select lists needed. If they are few in number and/or size, I would suggest generating hidden lists. If they are large, use Ajax to get them once, store them and then retrieve them from the DOM when needed.
There is another thread here where Arie recommends going to the server every time to make sure you get the most up-to-date data for the lists. If you want to follow this advice, for this reason, use get.add("VARIABLENAME", value) to pass the value to your process. If this is not an issue, you can use one of the other methods I outlined above.
Regards
Andy

Invalid LOV query error

I am trying to modify a query for LOV page item but get an Invalid LOV query error when trying to Apply Changes to my page(query however works in SQL*Plus)
I am trying to change the date format of query result to MON YYYY.
Original query that works:
select distinct bill.BILLED_DATE display_value, bill.BILL_ID return_value
from BILL;
New Query that fails in APEX (but works in SQL*Plus)
select distinct to_char(bill.BILLED_DATE, 'MON YYYY') display_value,
bill.BILL_ID return_value from BILL;
Anyone have any idea what I need to do to make this work?
"1 error has occurred
LOV query is invalid, a display and a return value are needed, the column names need to be different. If your query contains an in-line query, the first FROM clause in the SQL statement must not belong to the in-line query"

Strange, this lov does work and is no different than yours:
select distinct to_char(sysdate,'MON YYYY') disp, 1 retval from dual
What are the results from the query? Can there be something wrong with that?
Regards Guido

1.6 LOV query invalid, was working in 1.5

The following LOV query was valid in 1.5:
select rd.name, rd.refdata_id from refdata rd, refdata_meta meta where meta.name = 'Title' and rd.refdata_meta_id = meta.refdata_meta_id and (:20_PATIENT_ID IS NOT NULL OR visible = 'Y') order by rank
This query is being flagged as invalid in 1.6. The problem appears to be the parenthetical OR clause, since taking it out passes validation. The error message is:
"LOV query is invalid, a display and a return value are needed, the column names need to be different. If your query contains an in-line query, the first FROM clause in the SQL statement must not belong to the in-line query."
Seems to me that the validator is equating the existence of a left parenthesis with an inline query, which of course is incorrect as the above perfectly valid SQL demonstrates.
The query with the OR clause operates to populate the LOVs just fine in my existing app migrated from 1.5, so this is a maintenance and new app creation issue.
I can of course work around it by views as needed to support a simplified LOV query, but I would much rather just get the former level of functionality back. Any prospect of fixing what appears to me to be a bug in the LOV query validator for the 1.6 platform?
thanks,
susan weber

Susan,
In 1.6, we introduced LOV query validations, to help head off problems before runtime. Looks like in this case, the check has a bug. It's trying to parse your SQL as if it were a query in a region and it fails because of the item name you are using that begins with a numeric digit and is followed by non-numeric characters. Such a query fails to parse with DBMS_SQL.PARSE. But the query does work, as you know, in an LOV, where EXECUTE IMMEDIATE with a USING clause handles it okay.
So we have three bugs, the LOV query validation algorithm, the misleading validation failure message, and the bug that allows users to create and use items with names that are not valid Oracle identifiers. Thanks for pointing this out.
Your workaround is to use v('20_PATIENT_ID') instead of using bind variable notation.
Scott

SAP BW QUERY AND BOBJ , QUERY VARIABLES

I have a SAP BW QUERY which Iu2019m trying to get through to BOBJ 4.0 AND CONTINUE TO GET THIS error "getDocumentInformation exception Error WRE 99998.........database error The MDX QUERY SELECT {...} ON CLOUMNS, NON EMPTY UNORDER, DIMESION PROPERTIES ON ROWS from SAP VARIABLES FAILED TO EXECUTE WITH ERROR for characteristic 0FISCYEAR, enter year in specified format(IES10901)
We using BOBJ 4.0 AND IDT TO CREATE connections to query...
In SAP BEX ANALYZER the query runs and returns results without any issues, but in u201CQUERY AS A WEB SERVICEu201D and u201CWEB SERVICEu201D we get THE above error ....
so i removed the variables from the row section and included it in the filter section of query and still i get errors in bobj (This is after going to Transaction RSRT checking the properties TAB and selecting "Use Selection of Structure Elements" and then generating query in SAP BW,
SOME queries you need to assign variable inputs for certain characteristics to restrict specific data ACCORDINGLY...
is there a way to come around this?
are there some docs available that simply describes the method of using a variable input/prompt in a SAP BW QUERY and how to use it in BOBJ?
Any help would be greatly appreciated
Thanks in Advance

personal experience the variables doesnt work properly from query to bobj, remove any calculations in yoru query and variables, you could only use filters in query.. when you bring them in webi then brring the values to the report then create vraibles in it there.
i keep my query from filtering as well then do everything in webi or xcelsius ..

Problem in Dynamic LOV query

Hi,
I have a LOV in my page its query should be based on item condition.
So I tried using Apex provided Dynamic LOV Query with IF.. ELSE.. END IF condition.. But when I use this and run the page it is giving error "URL NOT FOUND".
My query is
   IF :MY_ITEM is not null THEN
   RETURN 'select ename ,eno
                from emp
                where eno = '''||:MY_ITEM||''' ';
   ELSE
    RETURN 'select ename ,eno
                from emp
                where ename = ''ALAKA'' ';
   END IF;But it is not working for me.
Please anyone help me to solve this.
Thanks
Alaka

Hi All,
It worked for me. Just I modified my code a bit. Thanks to all for help.
Just I did ,
   DECLARE
   BEGIN
         IF :MY_ITEM IS NOT NULL THEN
            RETURN 'SELECT ENAME,ENO
                        FROM EMP
                        WHERE ENAME = '''||:MY_ITEM||''' ';
       ELSE
           RETURN 'SELECT ENAME,ENO
                        FROM EMP
                        WHERE ENAME = ''ALAKA'' ';
      END IF;
      EXCEPTION
        WHEN OTHERS THEN
            HTP.PRN('ERROR'||SQLERRM);
   END;
Thanks
Alaka

Select list and subquery: "LOV query is invalid"

Hi all,
I want to create a select list with the following format:
"name1 (count of another table)"
"name2 (count of another table)"
I've boiled it down to a simple query with a non-correlated subquery that works fine in SQL*Plus but not as an LOV:
select table1.field1 || (select count(*) from table2) d,
table1.field2 r
from table1
I get this (Apex 3.2.1):
1 error has occurred
* LOV query is invalid, a display and a return value are needed, the column names need to be different. If your query contains an in-line query, the first FROM clause in the SQL statement must not belong to the in-line query.
Even this doesn't work:
select table1.field1 || (select 'a' from dual) d,
table1.field2 r
from table1
I've tried it with an inline view, joining table1 to a select from table2 that returns the count, but I get the same result. Any ideas?
Edited by: MalcA on Jan 22, 2010 12:14 PM

I don't know, but the difference is that the count(*) code goes from the select clause to the from clause.
Other times I had the same problem and always did it and it was the solution.

Need help how to change LOV query

Hi All,
Can some one help me how to use the LOV Query based on responsibility (I am using form personalization)
When the user logs in with XX_Payables Super user with say (Responsibility id =500) then the LOV should be
Select BA.bank_account_name,
BA.bank_account_num,
BA.bank_Account_id,
BA.currency_code bank_currency_code,
from CE_BANK_ACCOUNTS ba
but if the user logs in with any other responsibilits then the lov should be
Select BA.bank_account_name,
BA.bank_account_num,
BA.bank_Account_id,
BA.currency_code bank_currency_code,
from CE_BANK_ACCOUNTS ba
where BA.multi_currency_allowed_flag = 'Y'
step 1
I have created a built in builtin type : Create Record group from query
Arugument : Select statement
Group name : XX_Group
step 2
Property
Object type : LOV
target object : PAY_ACTIVE_BANK_ACCOUNTS
property name : Group name
value XX_GROUP
Using this method i am able to select only one query
How can i control this based on responsibility.
Appreciate if some one can help me to resolve this issue.
Regards,
Rajini

Thanks for your reply, I tried to use this query but i am getting error as FRM-41076 Error populating group and FRM-41072 Cannot create group
but if i use any one of the query or either of the query it works fine. but i dont see any issues when i run only any one of the query in argument in form personalization. Union all is returing rows in database.
SELECT BA.bank_account_name,
BA.bank_account_num,
BA.bank_Account_id,
BA.currency_code bank_currency_code,
CBAU.bank_acct_use_id ,
BA.multi_currency_allowed_flag bank_multi_currency_flag,
BA.zero_amount_allowed bank_zero_amounts_allowed,
BA.account_owner_org_id legal_entity_id,
CBB.bank_name,
CBB.bank_branch_name
FROM
CE_BANK_ACCOUNTS BA,
CE_BANK_BRANCHES_V CBB,
CE_BANK_ACCT_USES_OU_V CBAU
WHERE ((BA.multi_currency_allowed_flag = 'Y' AND
(BA.currency_code = :pay_sum_folder.functional_currency_code or
BA.currency_code = :parameter.pay_in_full_currency_code )) or
BA.currency_code = nvl( :parameter.pay_in_full_currency_code, BA.currency_code))
AND CBAU.BANK_ACCOUNT_ID = BA.BANK_ACCOUNT_ID
AND sysdate between TRUNC(CBB.start_date) and nvl(TRUNC(CBB.end_date), sysdate + 1)
AND CBB.branch_party_id = BA.bank_branch_id
AND SYSDATE < NVL(BA.END_DATE,SYSDATE+1)
AND BA.ACCOUNT_CLASSIFICATION = 'INTERNAL'
AND CBAU.ap_use_enable_flag = 'Y'
AND CBAU.org_id = :pay_sum_folder.org_id
AND NVL(BA.netting_acct_flag, 'N') <> 'Y'
AND fnd_global.resp_name = 'XX PAYABLES SUPER USER'
AND CBB.bank_name_alt = 'Head office bank'
UNION ALL
SELECT BA.bank_account_name,
BA.bank_account_num,
BA.bank_Account_id,
BA.currency_code bank_currency_code,
CBAU.bank_acct_use_id ,
BA.multi_currency_allowed_flag bank_multi_currency_flag,
BA.zero_amount_allowed bank_zero_amounts_allowed,
BA.account_owner_org_id legal_entity_id,
CBB.bank_name,
CBB.bank_branch_name
FROM
CE_BANK_ACCOUNTS BA,
CE_BANK_BRANCHES_V CBB,
CE_BANK_ACCT_USES_OU_V CBAU
WHERE ((BA.multi_currency_allowed_flag = 'Y' AND
(BA.currency_code = :pay_sum_folder.functional_currency_code or
BA.currency_code = :parameter.pay_in_full_currency_code )) or
BA.currency_code = nvl( :parameter.pay_in_full_currency_code, BA.currency_code))
AND CBAU.BANK_ACCOUNT_ID = BA.BANK_ACCOUNT_ID
AND sysdate between TRUNC(CBB.start_date) and nvl(TRUNC(CBB.end_date), sysdate + 1)
AND CBB.branch_party_id = BA.bank_branch_id
AND SYSDATE < NVL(BA.END_DATE,SYSDATE+1)
AND BA.ACCOUNT_CLASSIFICATION = 'INTERNAL'
AND CBAU.ap_use_enable_flag = 'Y'
AND CBAU.org_id = :pay_sum_folder.org_id
AND NVL(BA.netting_acct_flag, 'N') <> 'Y'
AND fnd_global.resp_name != 'XX PAYABLES SUPER USER'

Designing LOV Query Problem

Hello APEX people,
I posted my problem here:
Designing LOV Query Problem
What I have is a sequence like this:
CREATE SEQUENCE
DR_SEQ_FIRST_SCHEDULE_GROUP
MINVALUE 1 MAXVALUE 7 INCREMENT BY 1 START WITH 1
CACHE 6 ORDER CYCLE ;
What I need would be a SQL query returning all possible values oft my sequence like:
1
2
3
4
5
6
7
I want to use it as a source for a LOV...
The reason why I use the cycling sequence is: My app uses it to cycle scheduling priorities every month to groups identified by this number (1-7).
In the Admin Form, I want to restrict the assignment in a user friendly way - a LOV.
Thanks
Johann

Here ist the solution (posted by michales in the PL/SQL forum):
SQL> CREATE SEQUENCE
dr_seq_first_schedule_group
MINVALUE 1 MAXVALUE 7 INCREMENT BY 1 START WITH 1
CACHE 6 ORDER CYCLE
Sequence created.
SQL> SELECT LEVEL sn
FROM DUAL
CONNECT BY LEVEL <= (SELECT max_value
FROM user_sequences
WHERE sequence_name = 'DR_SEQ_FIRST_SCHEDULE_GROUP')
SN
1
2
3
4
5
6
7
7 rows selected.

LOV Query problem

I have a very huge and a lenghty LOV Query . I am using 6i builder and when i save the module and try to reopen it , Only 3/4th of the LOV query is available and the remaining disappears . I can compile this in 6i by copying the query again but it creates a problem in 10g . ie. The Fmx file is not generating in 10g.
Firstly ,
I haven no idea as to why the code disappears for no reason ? IS it because its too lenghty. I am sure there are no errors because it wouldn't have compiled if there were any .
Anybody who has come across such problems , kindly advice!
Thank you .

hii,
Create a VIEW of your query in database level and then create LOV based on that VIEW.
Regards
PS

URGENT - Form with LOV - Query Fails

Hi All,
I've a portal form, with about 10 fields and about 06 of them are combo boxes (attached to dynamic LOVs).
I'm trying to perform a query using the ID and leaving all other fields blank, but no result is displayed. I am sure that the record for that ID exist in the database table.
Can someone please suggest what should I do to be able to perform query in form with LOVs.
Thanks in advance.

Hi Jatinder
I'm happy because you are apparently on the right way with 'your duplicate form'!
"adjust the empty values" means to make sure, that the value of the simple empty field (in the duplicate form) is the same as the value of the corresponding LOV based combo box field (in the original form).
Maybe this sounds easy, but in the matter of fact it isn't. Why?
Look carefully at the following sample:
You have a dynamic LOV based on the number column 'category' in your 'table_1'.
So the basic part of the LOVs query looks like this:
select distinct category from table_1;
Now you still have to add the 'empty value' to your LOV to complete your request to find any value of 'category'. But if you add '0' or ' ' (blank) it wouldn't work. So you have to add NULL but this still doesn't work because you have to adjust NULL to the corresponding data type.
Furthermore you have to be sure that the default LOV's value is the 'any value' one.
Your complete LOVs query then looks like this:
select distinct category from table_1
union
select to_number(null) from dual
order by category desc;
/* 'desc' for 'descending' ensures the NULL value to be on the top of the combo box */
Now as you know how it works for number columns simply use the analog logic for character columns with to_char(null) and for date columns with to_date(null).
That's it.
Thanks
Peter

Binding a variable to an LOV query, not working... Urgent!

Hi,
Based on a column value(which gets populated at runtime), in a table, the LOV query for another column in the same table, should be restricted with this value.
1. My LOV is based on a VO.
Lov query is
SELECT ped.full_name as employee_name,
ped.employee_number as employee_number
FROM p_employee_details ped
WHERE ped.value = 'Y' and ped.work in (:1, 'Both')
2. For binding the variable, I have a method in VOImpl of the LOV.
public void initQuery(String p_param)
setWhereClauseParams(null);
setWhereClauseParam(0,p_param);
3. This method is called in the LOVAMImpl
public void initializeVO(String p_param)
LovVOImpl lovVO = (LovVOImpl)getLovVO1();
lovVO.initQuery(p_param);
4. In the CO for the LOV RN, the LOVAMimpl Method defined in step 3 is called.
public void processRequest(OAPageContext pageContext, OAWebBean webBean)
super.processRequest(pageContext, webBean);
OAApplicationModule lov_am = (OAApplicationModule) pageContext.getApplicationModule(webBean);
Dictionary lov_dict = pageContext.getLovCriteriaItems();
String lov_criteria = (String) lov_dict.get("work");
Serializable lov_params[] = {lov_criteria};
lov_am.invokeMethod("initializeVO",lov_params);
Here "work" is the column in the table whose value is needed for binding the lov query
But i am still getting an error saying not all variables bound.:
Developer Mode Exception : Lov Input should by default be the queryable criteria and Result.
I don't know what else to do.
Thanks in advance

HI,
Here the code giving on starting of the thread will work,only problem is lov mapping over here which was same as mine , u have to create one more lov mapping which will have criterial item same as the field on which lov is based.
Thanks

LOV query is invalid, a display and a return value are needed

hello - i am having this issue and can't get around this when creating a popup LOV based on sql.
below is LOV query. as you see the view has only two columns. I tried various ways by giving alias to columns in query but nothing works. What did I miss here?
select description,inventory_item_id from xx_apex_inv_v
1 error has occurred
LOV query is invalid, a display and a return value are needed, the column names need to be different. If your query contains an in-line query, the first FROM clause in the SQL statement must not belong to the in-line query.

Did you try it like this?
select description d, inventory_item_id v from xx_apex_inv_v

How to edit custom integrator/layout to change LOV query

Hi,
We have a custom integrator to populate data in to a custom table, in one of the columns in Header, we have simple list of values setup.
i want to update the list of values query to fetch from a different source and different condition.
i am not able to do that through "Create Document" or "Define Layout" etc., any idea how to change the LoV query or is it possible to do it through front-end pages?
Rgds,
-Kamal

if you are using 12.1.3/4 then you can do using "Define Parameter" screen to create LOV and attach to integrator.

Can someone tell me what's wrong with this LOV query please?

This query works fine..
select FILTER_NAME display_value, FILTER_ID return_value
from OTMGUI_FILTER where username = 'ADAM'
But this one..
select FILTER_NAME display_value, FILTER_ID return_value
from OTMGUI_FILTER where username = apex_application.g_user
Gives the following error.
1 error has occurred
* LOV query is invalid, a display and a return value are needed, the column names need to be different. If your query contains an in-line query, the first FROM clause in the SQL statement must not belong to the in-line query.
Thanks very much,
-Adam vonNieda

Ya know, I still don't know what's wrong with this.
declare
l_val varchar2(100) := nvl(apex_application.g_user,'ADAM');
begin
return 'select filter_name display_value, filter_id return_value
from otmgui_filter where username = '''|| l_val || '''';
end;
Gets the same error as above. All I'm trying to do is create a dropdown LOV which selects based on the apex_application.g_user.
What am I missing here?
Thanks,
-Adam

LOV query in BOBJ

Similar Messages

Maybe you are looking for