LOV query issue

HI, I know some of you will find this incredibly easy but I cannot work out the logic here...
I am trying to draw LOV on all projects on one client that user selects.
- I have a master-detail relationship all setup (orders block is master and project block is detail).
- The orders and project block are on same canvas.
- In properties of the project block i put: clientid = orders.clientid
My sql query looks like this but this displays ALL OF projects:
SELECT ALL PROJECT.PROJECTID, PROJECT.CLIENTID, PROJECT.PROJECTNAME, PROJECT.DATESTART,
PROJECT.DATEEND, PROJECT.DESCRIPTION, PROJECT.CONTRACT
FROM PROJECT
**// project is the table which contains all the details on the projects...
**// orderline is the table which contains details on orders
**// client is the table which contains details on all the clients
Thank you

ahhhhhhhhhhhhhhhhhhhhh thank you thank you thank you thank you
you have made my day !!!

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

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

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'

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

LOV Query Invalid

Hello.
I am uisng Apex 4.1 on Oracle 10.2.0.5 and Oracle App Server.
Would someone please tell me why the following LOV query is causing the dreaded error:
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.
select d, r
from
select
'(select)' as d,
'javascript:void(0)' as r
from dual
union
select
initcap(INFO_NAME) as d,
'javascript:popUp2(''' || INFO_LINK || ''', 1000, 800);' as r
from INFO_LINKS
order by 1Running this query in the SQL Commands section returns the result set without problem.
Related to this, I've noticed that I am getting this same error for many similar LOV "complex" queries that involve things like UNIONs or sub-queries. In fact, when I bring up an already working LOV query in the LOV editor and then simply click the "OK" button without modifying the query, I get this same error. WHY?
Thanks in advance for any help on this.
Elie

Hello Everyone.
I just realized what my mistake is.
Many of the individual lines in my LOV query are ending with a carriage-return character. And so, the following code line is literally concantonated with the previous line.
Once I added one or more space characters to the end of each code line, Apex accepted the query without problem.
Whew! That was tricky, indeed.
And this is why many of my other already working queries suddenly caused the error when I clcik the OK button in the LOV editor. For some reason, bringing up these already existing, working queries stripped awawy any space characters from the very end of the code codes.
I hope this helps others facing the same issue.
Elie

Dataset query issues twice if the dataset is connected to matrix and used in multilookup function

hello everybody.
could not find any information if this is an intended behavior:
dataset query issues twice if the dataset is connected to matrix and used in multilookup function
parameters in both queries are the same
ssrs: 2008 r2, sharepoint 2010 integrated
sharepoint 2010: september 2014 cu
thanks in advance
Sergey Vdovin

Hello, Wendy.
I prepared a very empty sample report for you to demonstrate the problem - with this report, i hope, there is no place to discuss the shrinking of time data retrieval.
There is one dataset, one parameter and one lookup function. The query is executed twice.
<?xml version="1.0" encoding="utf-8"?>
<Report xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner" xmlns:cl="http://schemas.microsoft.com/sqlserver/reporting/2010/01/componentdefinition" xmlns="http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition">
<AutoRefresh>0</AutoRefresh>
<DataSources>
<DataSource Name="DataSource1">
<DataSourceReference>http://t005/ProjectBICenter/DocLib/IntegrationDBVdovin.rsds</DataSourceReference>
<rd:SecurityType>None</rd:SecurityType>
<rd:DataSourceID>7e554344-d6c2-48a5-a7f4-1d24608cb4b5</rd:DataSourceID>
</DataSource>
</DataSources>
<DataSets>
<DataSet Name="DataSet1">
<Query>
<DataSourceName>DataSource1</DataSourceName>
<CommandText>select 1 as temp, '$' as tempname</CommandText>
<rd:UseGenericDesigner>true</rd:UseGenericDesigner>
</Query>
<Fields>
<Field Name="temp">
<DataField>temp</DataField>
<rd:TypeName>System.Int32</rd:TypeName>
</Field>
<Field Name="tempname">
<DataField>tempname</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
</Fields>
</DataSet>
</DataSets>
<ReportSections>
<ReportSection>
<Body>
<ReportItems>
<Textbox Name="ReportTitle">
<CanGrow>true</CanGrow>
<KeepTogether>true</KeepTogether>
<Paragraphs>
<Paragraph>
<TextRuns>
<TextRun>
<Value>=Lookup(1,Fields!temp.Value,Fields!tempname.Value,"DataSet1")</Value>
<Style>
<FontFamily>Verdana</FontFamily>
<FontSize>20pt</FontSize>
</Style>
</TextRun>
</TextRuns>
<Style />
</Paragraph>
</Paragraphs>
<rd:WatermarkTextbox>Title</rd:WatermarkTextbox>
<rd:DefaultName>ReportTitle</rd:DefaultName>
<Top>0mm</Top>
<Height>10.16mm</Height>
<Width>139.7mm</Width>
<Style>
<Border>
<Style>None</Style>
</Border>
<PaddingLeft>2pt</PaddingLeft>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
<PaddingBottom>2pt</PaddingBottom>
</Style>
</Textbox>
</ReportItems>
<Height>57.15mm</Height>
<Style>
<Border>
<Style>None</Style>
</Border>
</Style>
</Body>
<Width>152.4mm</Width>
<Page>
<PageFooter>
<Height>11.43mm</Height>
<PrintOnFirstPage>true</PrintOnFirstPage>
<PrintOnLastPage>true</PrintOnLastPage>
<Style>
<Border>
<Style>None</Style>
</Border>
</Style>
</PageFooter>
<PageHeight>29.7cm</PageHeight>
<PageWidth>21cm</PageWidth>
<LeftMargin>2cm</LeftMargin>
<RightMargin>2cm</RightMargin>
<TopMargin>2cm</TopMargin>
<BottomMargin>2cm</BottomMargin>
<ColumnSpacing>0.13cm</ColumnSpacing>
<Style />
</Page>
</ReportSection>
</ReportSections>
<ReportParameters>
<ReportParameter Name="ReportParameter1">
<DataType>String</DataType>
<DefaultValue>
<Values>
<Value>1</Value>
</Values>
</DefaultValue>
<Prompt>ReportParameter1</Prompt>
<ValidValues>
<DataSetReference>
<DataSetName>DataSet1</DataSetName>
<ValueField>temp</ValueField>
<LabelField>tempname</LabelField>
</DataSetReference>
</ValidValues>
</ReportParameter>
</ReportParameters>
<rd:ReportUnitType>Mm</rd:ReportUnitType>
<rd:ReportServerUrl>http://t005/ProjectBICenter</rd:ReportServerUrl>
<rd:ReportID>cd1262ef-eca7-4739-a2ce-d3ca832d5cd6</rd:ReportID>
</Report>
Sergey Vdovin

3.1 Page 0 LOV APP_ITEM issues

Hello,
I recently upgraded from 3.0.1 to 3.1 and my application appears to have broken.
I have a select list on page 0. The LOV query references an application item using the bind syntax. similar to
select col1 d, col2 r
from my_table
where col3 = :MY_APP_ITEM
order by 1
Since upgrading to 3.1, the select lists are empty after submitting the page, even when the session shows a value in my application item.
This problem only manifests in the select list LOV. If i create a display only item with MY_APP_ITEM as the source, it displays fine.
It almost seems like the page 0 LOV queries are parsed before the session is populated on page load.
Has anybody seen this? Any advice?
Thanks in advance
Matt Cox

Hi Guys,
I am encountering a similar problem to the one mentioned here. I've tried to create a dynamic LOV as below:-
select state_name AS Display_val, state_abbrev as Return_Val
from Pay_US_States@&DB_LINK_APP_ITEM.
order by 1
but I get the following error message...
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.
When I change the query to reference the db link directly, it works fine.
select state_name AS Display_val, state_abbrev as Return_Val
from Pay_US_States@dbname_link
order by 1
I am using version 3.1.0.00.32 of APEX and the db link refers to a remote database. APEX itself is installed on a local XE database.
I have other page references to the application item which work fine but using it in LOVs does not seem possible.
The application item is set on my login page (page 211) in the login process as follows...
:DB_LINK_APP_ITEM := :P211_DB_NAME||'_LINK';
wwv_flow_custom_auth_std.login(
P_UNAME => :P211_USERNAME,
P_PASSWORD => :P211_PASSWORD,
P_SESSION_ID => v('APP_SESSION'),
P_FLOW_PAGE => :APP_ID||':2'
Any help would be great!
Thanks,
Donal

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

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

Web Query issues

Hi All,
I have created a web query and assigned it to a role. I have moved the role, web templete and the query from dev to QA was able run the query fine without issues.
The problem I am having is when I make changes to the query and transport it to QA...when I run the query from the role menu it still shows the old query instead of the changed query.
Can someone please explain what are the steps I need to take when I make changes to exsisting web query in dev and move to QA and be able to see the changes. What are all the objects I need to collect. Also would like to know if there are any settings on the role menu or web templete that need to be changed and also any buffers that I need to cleared??
Any help is appriciated and will give max points.
Thanks

BWdesi,
please avoid reposts - it could be that due to network issues the post got posted twice... close one of them as answered and then proceed with the other one...
Web Query issues
Arun

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.

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.

Query issue

I had query issue on planning layout
Sold    mat   price   qty   amount
100      3        5        5          25    layout 1
100      4       10       5          50    layout2
when I should removed material cal has to come like this
100             15        10          75
but I getting value like
100        15       10       150
can u plz tell me how to slove this
regards
raju

Dear Raju,
In the query, for the Calculated Key Figure (Amount)
   Select properties, enhanced and change to:
                      "BEFORE AGGREGATION"
It seems to be doing after aggregation, which is default.
it is aggregating:
    price = 5+10 = 15
    qty   = 5+5 = 10
    Amount = 15 * 10 = 150
Good luck, BB

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

LOV query issue

Similar Messages

Maybe you are looking for