Are cascading LOVs possible in af:query?

Is it possible to have two or more cascading LOVs in an af:query area based on a view criteria?
I'm having some trouble with dependant (child) LOVs: they filter correctly but return nothing to the field from which were launched.
I can attach a code snippet if necessary
Thanks
JDeveloper 11.1.1.3.0 with ADF BC
Anybody has ever tried it?
Edited by: Marge on 02-sep-2010 23:17

Is it possible to have two or more cascading LOVs in an af:query area based on a view criteria?Yes, it is possible
There might be something wrong in the configuration, Can you upload the sample app so that it will be easy to figure out the issue.
Sireesha

Similar Messages

Cascading LOV in a Query panel (af:query)

Hi
I have a requirement to implement few Cascading LOV's in a Query panel. I have created the VO's for the LOV's with bind variable and view criteria and linked them. It works for the BC viewer. But to enable in the ADF UI, the partial trigger needs to be enabled on individual field. And the af:query encapsulates the fields and they are not exposed. Can someone help me with a solution or a pointer
Many thanks

Thanks for the pointer
Well I followed the the steps, and implemented the same for two LOV's. I'm getting "Server Exception during PPR, #1". Would be able to identify where I'm going wrong please.
FYI: I'm using a UI template that is stripped won from Oracles Dynamic tab template
1. parent LOV
<?xml version="1.0" encoding="windows-1252" ?>
<!DOCTYPE ViewObject SYSTEM "jbo_03_01.dtd">

<ViewObject
xmlns="http://xmlns.oracle.com/bc4j"
Name="QcChiptypeVViewRO"
Version="11.1.1.56.60"
BindingStyle="OracleName"
CustomQuery="true"
RowClass="com.qualcomm.qdt.fwk.model.QdtViewRowImpl"
ComponentClass="com.qualcomm.qdt.fwk.model.QdtViewObjectImpl"
DefClass="com.qualcomm.qdt.fwk.model.QdtViewDefImpl"
PageIterMode="Full"
UseGlueCode="false">
<DesignTime>
<Attr Name="_codeGenFlag2" Value="Access|VarAccess"/>
<Attr Name="_isExpertMode" Value="true"/>
</DesignTime>
<SQLQuery>
<![CDATA[SELECT QcChiptypeV.CHIPTYPE
FROM QC_CHIPTYPE_V QcChiptypeV]]>
</SQLQuery>
<ViewAttribute
Name="Chiptype"
IsUpdateable="false"
IsPersistent="false"
PrecisionRule="true"
Precision="42"
Type="java.lang.String"
ColumnType="VARCHAR2"
AliasName="CHIPTYPE"
Expression="CHIPTYPE"
SQLType="VARCHAR">
<DesignTime>
<Attr Name="_DisplaySize" Value="42"/>
</DesignTime>
</ViewAttribute>
</ViewObject>
2. Child LOV
<?xml version="1.0" encoding="windows-1252" ?>
<!DOCTYPE ViewObject SYSTEM "jbo_03_01.dtd">

<ViewObject
xmlns="http://xmlns.oracle.com/bc4j"
Name="QcMcnVViewRO"
Version="11.1.1.56.60"
BindingStyle="OracleName"
CustomQuery="true"
RowClass="com.qualcomm.qdt.fwk.model.QdtViewRowImpl"
ComponentClass="com.qualcomm.qdt.fwk.model.QdtViewObjectImpl"
DefClass="com.qualcomm.qdt.fwk.model.QdtViewDefImpl"
PageIterMode="Full"
UseGlueCode="false">
<DesignTime>
<Attr Name="_codeGenFlag2" Value="Access|VarAccess"/>
<Attr Name="_isExpertMode" Value="true"/>
</DesignTime>
<Variable
Name="chiptype"
Kind="viewcriteria"
Type="java.lang.String"/>
<ViewAccessor
Name="QcChiptypeVViewRO1"
ViewObjectName="com.qualcomm.qdt.model.lov.QcChiptypeVViewRO"
RowLevelBinds="true"/>
<SQLQuery>
<![CDATA[SELECT QcMcnV.MCN,
QcMcnV.CHIPTYPE
FROM QC_MCN_V QcMcnV]]>
</SQLQuery>
<ViewAttribute
Name="Mcn"
IsUpdateable="false"
IsPersistent="false"
PrecisionRule="true"
Precision="20"
Type="java.lang.String"
ColumnType="VARCHAR2"
AliasName="MCN"
Expression="MCN"
SQLType="VARCHAR">
<DesignTime>
<Attr Name="_DisplaySize" Value="20"/>
</DesignTime>
<Dependencies>
<Item
Value="Chiptype"/>
</Dependencies>
</ViewAttribute>
<ViewAttribute
Name="Chiptype"
IsUpdateable="false"
IsPersistent="false"
PrecisionRule="true"
Precision="42"
Type="java.lang.String"
ColumnType="VARCHAR2"
AliasName="CHIPTYPE"
Expression="CHIPTYPE"
SQLType="VARCHAR">
<DesignTime>
<Attr Name="_DisplaySize" Value="42"/>
</DesignTime>
</ViewAttribute>
<ViewCriteria
Name="QcMcnVViewROCriteriaChiptype"
ViewObjectName="com.qualcomm.qdt.model.lov.QcMcnVViewRO"
Conjunction="AND">
<Properties>
<CustomProperties>
<Property
Name="displayOperators"
Value="InAdvancedMode"/>
<Property
Name="autoExecute"
Value="true"/>
<Property
Name="allowConjunctionOverride"
Value="true"/>
<Property
Name="showInList"
Value="true"/>
<Property
Name="mode"
Value="Basic"/>
</CustomProperties>
</Properties>
<ViewCriteriaRow
Name="vcrow5"
UpperColumns="1">
<ViewCriteriaItem
Name="QcMcnVViewROCriteria_vcrow5_Chiptype"
ViewAttribute="Chiptype"
Operator="="
Conjunction="AND"
Value=":chiptype"
IsBindVarValue="true"
Required="Optional"/>
</ViewCriteriaRow>
</ViewCriteria>
</ViewObject>
3. JSF page
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<jsp:directive.page contentType="text/html;charset=UTF-8"/>
<f:view>
<af:document id="d1">
<af:messages id="m1"/>
<af:form id="f1">
<af:pageTemplate viewId="/oracle/ui/pattern/dynamicShell/dynamicTabShell.jspx"
value="#{bindings.pageTemplateBinding}" id="pt1">
<f:facet name="copyright">
<af:outputText value="2010 Qualcomm Inc. All Rights Reserved."
id="ot10"/>
</f:facet>
<f:facet name="about">
<af:navigationPane id="np3" hint="buttons">
<af:commandNavigationItem text="About" id="cni5"/>
<af:commandNavigationItem text="Privacy" id="cni6"/>
</af:navigationPane>
</f:facet>
<f:facet name="navigation">
<af:panelAccordion id="pa1">
<af:showDetailItem text=" Asset Details" id="sdi1">
<af:panelGroupLayout layout="vertical" id="pgl1">
<af:panelHeader text=" " id="ph1">
<af:query id="qryId1"
headerText="Search Criteria (Use % as wildcard)" disclosed="true"
value="#{bindings.ImplicitViewCriteriaQuery.queryDescriptor}"
model="#{bindings.ImplicitViewCriteriaQuery.queryModel}"
queryListener="#{bindings.ImplicitViewCriteriaQuery.processQuery}"
queryOperationListener="#{bindings.ImplicitViewCriteriaQuery.processQueryOperation}"
saveQueryMode="hidden"/>
</af:panelHeader>
</af:panelGroupLayout>
</af:showDetailItem>
<af:showDetailItem text="More Info" id="sdi2"/>
</af:panelAccordion>
</f:facet>
<f:facet name="globalLinks">
<af:navigationPane id="np2" hint="buttons"
inlineStyle="text-align:right;">
<af:commandNavigationItem text="Help" id="cni4" action="noop"/>
<af:commandNavigationItem text="Sign out"
id="commandNavigationItem1"
action="noop"/>
</af:navigationPane>
</f:facet>
<f:facet name="status"/>
<f:facet name="globalToolbar"/>
<f:facet name="globalSearch"/>
<f:facet name="globalTabs">
<af:navigationPane id="np1">
<af:commandNavigationItem text="Device Query/Update" id="cni1"
selected="true" partialSubmit="false"/>
<af:commandNavigationItem text="Asset Return" id="cni3"
action="dummy" rendered="false"/>
</af:navigationPane>
</f:facet>
<f:facet name="welcome">
<af:panelSplitter id="ps1" orientation="vertical">
<f:facet name="first">
<af:panelCollection id="pc1" defaultToolbarItemDisplay="icon">
<f:facet name="menus">
<af:menu text="Options" id="m2" rendered="false">
<af:commandMenuItem text="Printable Page" id="cmi2">
<af:showPrintablePageBehavior/>
</af:commandMenuItem>
<af:commandMenuItem text="Download" id="commandMenuItem1">
<af:exportCollectionActionListener exportedId="t2"
type="excelHTML"
title="Asset Details"/>
</af:commandMenuItem>
</af:menu>
</f:facet>
<f:facet name="toolbar">
<af:toolbar id="t1">
<af:commandToolbarButton id="ctb1"
hoverIcon="/images/view_image.gif"
text="Export to Excel">
<af:exportCollectionActionListener exportedId="t2"
type="excelHTML"
title="Asset Details"/>
</af:commandToolbarButton>
</af:toolbar>
</f:facet>
<f:facet name="statusbar"/>
<af:table value="#{bindings.QcDeviceTrackingVO1.collectionModel}"
var="row"
rows="#{bindings.QcDeviceTrackingVO1.rangeSize}"
emptyText="#{bindings.QcDeviceTrackingVO1.viewable ? 'No data to display.' : 'Access Denied.'}"
fetchSize="#{bindings.QcDeviceTrackingVO1.rangeSize}"
rowBandingInterval="0"
filterModel="#{bindings.ImplicitViewCriteriaQuery.queryDescriptor}"
queryListener="#{bindings.ImplicitViewCriteriaQuery.processQuery}"
filterVisible="true" varStatus="vs"
selectedRowKeys="#{bindings.QcDeviceTrackingVO1.collectionModel.selectedRow}"
selectionListener="#{bindings.QcDeviceTrackingVO1.collectionModel.makeCurrent}"
rowSelection="single" id="t2"
columnSelection="single"
partialTriggers=":::ph1 :::qryId1">
<af:column sortProperty="Serialnum" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Serialnum.label}"
id="c28" width="103">
<af:outputText value="#{row.Serialnum}" id="ot17"/>
</af:column>
<af:column sortProperty="Assettag" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Assettag.label}"
id="c7" width="107">
<af:outputText value="#{row.Assettag}" id="ot24"/>
</af:column>
<af:column sortProperty="Chiptype" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Chiptype.label}"
id="c18" width="26">
<af:outputText value="#{row.Chiptype}" id="ot27"/>
</af:column>
<af:column sortProperty="Mcn" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Mcn.label}"
id="c11">
<af:outputText value="#{row.Mcn}" id="ot13"/>
</af:column>
<af:column sortProperty="Mcnrev" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Mcnrev.label}"
id="c8">
<af:outputText value="#{row.Mcnrev}" id="ot3"/>
</af:column>
<af:column sortProperty="Assignedto" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Assignedto.label}"
id="c15">
<af:outputText value="#{row.Assignedto}" id="ot32"/>
</af:column>
<af:column sortProperty="Location" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Location.label}"
id="c24">
<af:outputText value="#{row.Location}" id="ot19"/>
</af:column>
<af:column sortProperty="Locationfullname" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Locationfullname.label}"
id="c14">
<af:outputText value="#{row.Locationfullname}" id="ot26"/>
</af:column>
<af:column sortProperty="Locationtype" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Locationtype.label}"
id="c13">
<af:outputText value="#{row.Locationtype}" id="ot28"/>
</af:column>
<af:column sortProperty="Description" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Description.label}"
id="c21">
<af:outputText value="#{row.Description}" id="ot22"/>
</af:column>
<af:column sortProperty="Assignment" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Assignment.label}"
id="c30">
<af:outputText value="#{row.Assignment}" id="ot34">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Assignment.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Createddate" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Createddate.label}"
id="c1">
<af:outputText value="#{row.Createddate}" id="ot15">
<af:convertDateTime pattern="#{bindings.QcDeviceTrackingVO1.hints.Createddate.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Lastid" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Lastid.label}"
id="c33">
<af:outputText value="#{row.Lastid}" id="ot9">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Lastid.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Lportfolioitemid" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Lportfolioitemid.label}"
id="c23">
<af:outputText value="#{row.Lportfolioitemid}" id="ot23">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Lportfolioitemid.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Lkeycontactid" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Lkeycontactid.label}"
id="c4">
<af:outputText value="#{row.Lkeycontactid}" id="ot11">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Lkeycontactid.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Fullname" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Fullname.label}"
id="c22">
<af:outputText value="#{row.Fullname}" id="ot6"/>
</af:column>
<af:column sortProperty="Status" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Status.label}"
id="c16">
<af:outputText value="#{row.Status}" id="ot21"/>
</af:column>
<af:column sortProperty="Qcemployeenumber" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Qcemployeenumber.label}"
id="c6">
<af:outputText value="#{row.Qcemployeenumber}" id="ot33">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Qcemployeenumber.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Field3" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Field3.label}"
id="c12">
<af:outputText value="#{row.Field3}" id="ot18"/>
</af:column>
<af:column sortProperty="Empdeptfullname" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Empdeptfullname.label}"
id="c27">
<af:outputText value="#{row.Empdeptfullname}" id="ot4"/>
</af:column>
<af:column sortProperty="Comments" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Comments.label}"
id="c10">
<af:outputText value="#{row.Comments}" id="ot16"/>
</af:column>
<af:column sortProperty="Builtby" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Builtby.label}"
id="c19">
<af:outputText value="#{row.Builtby}" id="ot20"/>
</af:column>
<af:column sortProperty="Mesbuild" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Mesbuild.label}"
id="c31">
<af:outputText value="#{row.Mesbuild}" id="ot2"/>
</af:column>
<af:column sortProperty="Esn" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Esn.label}"
id="c26">
<af:outputText value="#{row.Esn}" id="ot31"/>
</af:column>
<af:column sortProperty="Imei" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Imei.label}"
id="c17">
<af:outputText value="#{row.Imei}" id="ot29"/>
</af:column>
<af:column sortProperty="Macaddress" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Macaddress.label}"
id="c32">
<af:outputText value="#{row.Macaddress}" id="ot1"/>
</af:column>
<af:column sortProperty="Brf" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Brf.label}"
id="c25">
<af:outputText value="#{row.Brf}" id="ot8"/>
</af:column>
<af:column sortProperty="Brfrev" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Brfrev.label}"
id="c3">
<af:outputText value="#{row.Brfrev}" id="ot25"/>
</af:column>
<af:column sortProperty="Dacquisition" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Dacquisition.label}"
id="c29">
<af:outputText value="#{row.Dacquisition}" id="ot7">
<af:convertDateTime pattern="#{bindings.QcDeviceTrackingVO1.hints.Dacquisition.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Datqcmainttermdate" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Datqcmainttermdate.label}"
id="c2">
<af:outputText value="#{row.Datqcmainttermdate}"
id="ot30">
<af:convertDateTime pattern="#{bindings.QcDeviceTrackingVO1.hints.Datqcmainttermdate.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Datqcissueddate" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Datqcissueddate.label}"
id="c5">
<af:outputText value="#{row.Datqcissueddate}" id="ot5">
<af:convertDateTime pattern="#{bindings.QcDeviceTrackingVO1.hints.Datqcissueddate.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Itlqciteclass" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Itlqciteclass.label}"
id="c20">
<af:outputText value="#{row.Itlqciteclass}" id="ot14"/>
</af:column>
<af:column sortProperty="RowID" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.RowID.label}"
id="c9">
<af:outputText value="#{row.RowID}" id="ot12"/>
</af:column>
</af:table>
</af:panelCollection>
</f:facet>
<f:facet name="second">
<af:panelTabbed id="pt2">
<af:showDetailItem text="Update Attributes" id="sdi3"
stretchChildren="first"/>
</af:panelTabbed>
</f:facet>
</af:panelSplitter>
</f:facet>
<f:facet name="innerToolbar"/>
<f:attribute name="brandingTitle" value="ITE Device Tracking System"/>
<f:attribute name="navSplitterPosition" value="450"/>
</af:pageTemplate>
</af:form>
</af:document>
</f:view>
</jsp:root>

Cascading LOV in BEx Query OLAP Universe + BEx variable

Hi gurus,
we have an universe where a Cascading LOV has been defined based on a BO Hierarchy ( based on a BW hierarchy), the OLAP universe is based on a BEx query.
Now, when the users create a WebI report selecting a value from the value list, the Cascading LOV appears and the user selects the value, descending by the nodes.
We are analyzing the universe performance and we are testing to add some time BEx variables in the query ( in the current version no variables are used).
Everything works properly but when we try to select a value from the Cascading LOV and try to select a lower level the webI returns a mdx error indicanting that the time variable is not informed. (WIS 10901: A database error ocurred; MDX query can not be executed: specify a value for the variable Z... )
We thought that the mdx for the LOV get values from the MD table because in the infoobject definition, it has the Business Explorer Settings:
Query Def. Filter Value Selection = Value in Master Data Table
Query Execution Filter Val. Selectn = Value in Master Data Table
The Query Execution Filter Val. Selectn can be defined at the infoprovider also (with the provider specific Properties of the infoobject) and also at the query, whe have not modify none of them.
My first question is which settings has efect at OLAP Universes, the infoobject settings; the infocube settings or the query settings ?
Are the Cascading LOV integrated with BEx Query OLAP Universe?
Is it an application error?
Many Thanks in advanced.
Best Regards,
Nuria

Hi Ingo,
many thanks for your quick answer.
That was one of the possibilities we have analized but the problem is that the user has to inform the hierarchy level for all the reports, that kind of variables is translated in the universe as a prompt
Now we have only one universe and some business analists users create reports themselves for the business area based on that universe.
The users create WebI filters without prompts,just filtering the hierarchy node. If we add the BEx variable then the user sould inform the prompt for all the reports based on that universe.
We want to avoid that prompt, we have several hierarchies in the query for different infoobjects.
Thanks again.
Best Regards,
Nuria

Set Cascading LOV Item using Dynamic Action

Hi all,
I have the following page item:
P1_USERNAME
P1_COMPANY (LOV)
P1_DIVISION (LOV)
P1_DEPT (LOV)
Item P1_COMPANY, P1_DIVISION, and P1_DEPT are cascading LOV on my page.
I also have a table that contains the user and his/her company, division, and department.
So I have a dynamic action that when P1_USERNAME is entered. The dynamic action will pull the COMPANY, DIVISION, and DEPT information from the table and populate the page item accordingly.
I got the dynamic action working, I can confirm this by checking the Session State of the items.
BUT I cannot get the LOVs to display the selected value from the session state. They always reset back to "- Please Select -", which is my display value when NULL.
For example:
I have a record like in the table:
Username :alex
Company : Finance Inc.
Division : Admin
Dept : HR
When I entered the username into P1_USERNAME, this is what I see in the screen.
Username :alex
Company : - Please Select -
Division : - Please Select -
Dept : - Please Select -
While the session states of the items have been set correctly as per the record in the database.
Has anyone experienced this before?
I think it's because the parent LOV (company), reset the child LOVs (division and dept), when the dynamic action kicks in.
Thanks.

I've just taken a look at your sample page and don't think this issue is actually too complicated to solve. (Actually, it was I who was mucking around in page 1, sorry for that. I was looking at it and then had to go. Picked it up again later on and just made a copy this time)
You change the employee. The dynamic action fires, executes plsql and sets the values in the company2/division2/dept2 fields
Company 1 is a cascading lov. Empo has changed? Company refreshes. Cascading for division and dept as well.
You can see this happening in sequence as well when looking at the page. Select emp, it'll hang for a second. You then get the select list refresh icons.
The sequence in which this happens is of course a bit wrong. You set the values for the items on the client side first, but then their refresh is kicked in, and so the value setting is simply lost again.
What makes this annoying is how P1_EMPNO is a cascading lov parent of P1_COMPANY. Changing P1_EMPNO will refresh the lovs beneath it. However, you can't simply set their values after you've retrieved the user's company/division/dept, because each lov is dependent on the one above it. Eg you change the employee. The company lov is refreshed. Because the it is refreshed, the division lov will refresh. Now you can set the value of the company lov, but not that of the division one. Why is this? The lov for division requires the value of company in the session state. If you'd set the value for company after it has finished refreshing, it will already be too late for division to pick up the value set. .
I made a copy of your page to page 5, “tom”.
The first I did was removing the cascade from the company lov. You don’t need this. There are simply no parent lovs for this lov, as is evident from the sql for it. The companies always remain the same companies even when you select another person; it is not dependent on another item for its values.
Then the timing issues come in play, and with them there is also the issue of the session state.
So now companies always show. You pick a user, it runs the PLSQL block and put values in the P5_xxx2 items. P5_COMPANY can be set now, and this is in the set value of the dynamic action. By not suppressing the change event, a refresh will be triggered on its cascading lov, P5_DIVISION.
Refreshing P5_DIVISION will only get the new lov values (constrained within the chosen company) for this item though, and not set the value. We already have the values in P5_DIVISION2 however, and thus can use the “After Refresh” dynamic action on P5_DIVISION to do this. In short: company gets set, divisions refresh to show the correct divisions, and then the selected value is set. Again, by not suppressing the change event on this item the depending lov on DEPT will be refreshed.
Then by using another “After Refresh” dynamic action on P5_DEPT we can set the selected value once more.
Also important is that I changed P5_DIVISION to submit P5_COMPANY when it is refreshed, and P5_DIVISION when P5_DEPT is refreshed. This makes sure that the correct set of values is retrieved and probably why you were struggling aswell. After company has changed and division has refreshed, the value on division is set. But the correct divisions are shown only because the chosen company has been set in the session state.
The same for division - dept. After the refresh of division, the chosen value for division is set. This change will trigger the refresh on dept, and because dept has the division in its page items to submit list, the correct values will be retrieved.
Take note that the “debug items” are required in this solution though. Just set them as hidden and unprotect their value. Your goal should be to reduce the amount of roundtrips to the server. Why do a plsql (ajax) call just to retrieve a session state, when the value is already on the page and all in one action? Three hidden items is just so much easier than 3 extra ajax calls, the tradeoff is plenty.
There is one more noteworthy point, and that is the fact that dept is being retrieved twice. That makes sense because of the cascading lovs. Initially company is changed, and this will refresh division and this in turn will trigger a refresh on dept. At this point the lov for dept will be empty, because division will be empty. Because we set the value of division again after it has refreshed, this will trigger a second refresh on dept, though now the correct list of values is retrieved because division has a value set. Not that big an issue, but good to point out. If you’d have another cascading lov beneath dept, it would refresh three times.

JDev: af:query cascade LOVs

Hi,
I have question about cascade LOVs inside af:query component (generated automatically via viewCriteria).
Is it possible to have two LOVs (master slave relation), in first user selects department, and then he gets all employees which are
in selected department in second ? (search must be possible only by department)
Regards, Rok Kogovšek

Hi,
I managed to made LOV behavior in cascading fashion but i have another problem, form is refreshed when user click on search button.
Is it possible to set partial trigger of first LOV to refresh second one or to refresh complete form on value change.
Regards Rok Kogovšek

Af:query component with cascading Lov's

Hi All,
I have Cascading LOV's model setup in Business Components and they work fine in a form or table
but they are not working inside af:query component as there is no autoSubmit attribute on the query component itself
can someone help me to resolve this
Thanks in Advance

I have found a way
using bindings attribute of the query component it was able to go to backing bean on any LOV change in there we need to manually refresh the bindings then it works

Cascading LOV always returns first row in af:query

HI
JDEV 11.1.1.3.0
A strange thing is happening with my cascading LOV which is input text with LOV.
I have a read only table with a query section. I then also bring up any of the tables rows in a popup with single record view where the row is then in an af:form for inserting and updating.
Both the af:query and af:form have the cascaing LOV in them.
When testing the cascading LOV in the BC Browser it works fine. When I use it in the popup in the af:form record it works fine. But in the af:query section, no matter which row I choose in the LOV, it always returns the 1st row of the LOV back to my input text component.
Has anyone experienced this...any ideas?
Thanks,
Mario

Aha...and the above log message lead me to the solution!! :-)
The VO is based on an Oracle data dictionary view, DBA_TAB_COLUMNS. When you create the read only VO, by default it does not create any of the attributes as "key" attributes, because the oracle view has no primary key.
Setting owner, tableName and columnName as key attributes solved this issue, now my cascading LOV works in the BC Tester, af:query component and my af:form component.
Regards,
Mario

Cascading LOVs with the ability to create a new record. Is this possible?

Hi,
I'm trying to create a couple of LOVs. The first is a list of manufacturers, the second a list of items. Essentially, when you select a manufacturer in the first LOV you will only see their items in the second LOV.
I've had a look through the forum and I think I've got a handle on how to do a cascading LOV... except...
I'd like the users to have the ability to type in a NEW manufacturer and NEW item if necessary and have that combination then saved into the source table.
Is that possible?
Thanks,
Joseph

Hi,
Browsers don't have the combo-box functionality that you would find in something like MS Access. You could try autocomplete - see [http://apex.oracle.com/pls/otn/f?p=31517:53] - but you would then have to look up every entry (the field would only relate to the display text and not the ID for the item, so that would have to be looked up every time).
I'd like to say that you should be able to trust your users not to create duplicate entries. I'd like to say that, but.... ;)
Andy

4.2.1 Bug: Current values of child cascading LOVs are LOST.

Hello, ApEx Team!
This bug affected 4.1.1 and 4.2.1 but with different behavior. It seems that someone was trying to fix it.
According to docs "whats new in 4.1" a value of refreshed child cascading lov is derived from default value settings of select list.
Please follow these steps to see the bug.l builder-work done for you here http://apex.oracle.com/pls/apex/f?p=14110:1
1.Create primary select list P1_SEL1.
Display null value: Yes
LOV definition:
    select 'aaa' name,'a' id
      from dual
     union all
    select 'bbb' name,'b' id
      from dual
     union all
    select 'ccc' name,'c' id
      from dual2.Create child select list P1_SEL2.
Cascading LOV Parent Item: P1_SEL1
Page Items to Submit: P1_SEL2 (I strongly believe that this item should be submitted automatically along with Parent Item)
Display Null Value: Yes
LOV definition:
    select 'aaa' name,'a' id
      from dual
     union all
    select 'bbb' name,'b' id
      from dual
     where :P1_SEL1 in ('b','c')
     union all
    select 'ccc' name,'c' id
      from dual
     where :P1_SEL1 in ('c')
Default: return :P1_SEL2;
Default Value Type: PL/SQL Function Body3.Run app. and manually change P1_SEL1 and P1_SEL2 to 'bbb'.
4.Manually change P1_SEL1 to 'ccc'.
h2.
In apex 4.1.1..
you see that P1_SEL2 is resetted to NULL automatically. The value of P1_SEL2 is LOST. Although I tell apex to submit P1_SEl2 value to set its session state, but the session state still remains NULL.
The session state of P1_SEL2 is always NULL and I have no idea how to set it as it is set in a browser at the moment of changing parent LOV P1_SEL1.
h2.
Now apex 4.2.1.
It seems this bug is fixed. Indeed it is NOT fixed.
To see this bug in 4.2.1 just...
5.Create a third child select list P1_SEL3 which depends on P1_SEL2.
Cascading LOV Parent Item: P1_SEL2
Page Items to Submit: P1_SEL3 (Again, I hope you will always submit current item automatically as you do for the parent item)
Display Null Value: Yes
LOV definition:
    select 'aaa' name,'a' id
      from dual
     union all
    select 'bbb' name,'b' id
      from dual
     where :P1_SEL2 in ('b','c')
     union all
    select 'ccc' name,'c' id
      from dual
     where :P1_SEL2 in ('c')
    Default: return :P1_SEL3;
    Default Value Type: PL/SQL Function Body6.Run app. again. Manually set P1_SEL1, P1_SEL2 and P1_SEL3 to 'bbb'.
7.Change P1_SEL1 to 'ccc' and see the bug:
1) P1_SEL2 is reset to NULL for just a short time and than restored to 'bbb'.
2) P2_SEL3 is reset to NULL. So the session state was NULL for this item at the moment of calculating default value. As a result the value of child cascading lov is LOST.
So this bug is still present in 4.2.1.
Can I hope to get workaround for this problem in 4.1 and 4.2?
Thank you,
Vladimir
Edited by: vgoncharov on 17.12.2012 19:37
Edited by: vgoncharov on 17.12.2012 22:45

Good to hear this is already being worked on.
When we tried to work around the "Automatic detection" bug - changing the "Application Language Derived From" to "Application Preference" or "Session" - we hit issue that some page processes were not firing in translated application.
See Page processes not firing in Translated applications
Jan

Cascading LOVs (APEX 4.1) problem, using in report does not set values

Hi,
i am using APEX 4.1.0.00.32 and i have a simple report as
SQL:*
SELECT * from region
WHERE region like '%'||P3_REGION||'%'
and country like '%'||P3_COUNTRY||'%'
and city like '%'||P3_CITY||'%'
Items:*
P3_REGION:
select distinct region as d, region as r from region
Display Null value: YES
Null display value: - select -
Null return value: +0+
P3_COUNTRY:
select distinct country as d, country as r from region where region = :P3_REGION
Display Null value: YES
Null display value: - select -
Null return value: +0+
Cascading LOV Parent Item(s): P3_REGION
P3_CITY:
+select distinct city as d, city as r from region where country = :P3_COUNTRY
Display Null value: YES
Null display value: - select -
Null return value: +0+
Cascading LOV Parent Item(s): P3_COUNTRY
The LOVs work fine and the correct values are displayed if cascading through them
So in the last step i want to filter the report with the values that were selected in the lovs. And this i get not working.
I tried to add a button with SUBMIT of the page. After choosing values in all LOVs and clicking the SUBMIT button the page submits, alle LOVs are cleared (with value - select -) and the report shows all rows.
I tried to change the button to "redirect to Page 3" and setting the values P3_REGION, P3_COUNTRY, P3_CITY to &P3_REGION., &P3_COUNTRY., &P3_CITY. but without success.
I tried to use the setting "Page Action when Value Changed" to "Submit" and/or "Redirect and set value" for all Item LOVs and/or only the last item LOV, but then the cascade of the LOVs does not work properly and the report does not change too.
I am confused as i don´t know what i can do until now. I think this should be an easy requirement to limit/filter the report with values in the LOVs.
Furthermore it should be possible to choose only the region LOV and then limit the report with that region (without choosing country and city)
Thanks in advance!

Hi Dan,
thank you for your answer. I have the solution now from Kleber_M, this works.
Dan McGhan wrote:
1. Use bind variables in my query. It would look something like:
SELECT *
FROM region
WHERE region LIKE '%'|| :P3_REGION ||'%'
AND country LIKE '%'|| :P3_COUNTRY ||'%'
AND city LIKE '%'|| :P3_CITY ||'%'
This was only a mistake when writing the post, i forgot the colon. I use bind variables of course.
2. Make sure you have a comma separated list of item names that the report depends on beneath the SQL Query where it says Page Items to Submit. This will make sure that the value of those items on the page are bound into session state prior to the query executing.I tried this, too, but without success...
3. Use Dynamic Actions to perform the refresh action when any of the three items changes. This would be both more performant and a better experience for the end user than a full page refresh.How can i do this. This sounds good, because when refreshing the page often some items oder actions are done that i don´t want to.
Regards,
Matze

Get('XML') doesn't work, but get() does in javascript - CASCADING LOVs

I'm trying to get cascading LOVs working in Apex 3.1.0 in Oracle 11g. When I call get.get('XML') it returns null in firefox and empty string in IE6. If I change it to call get.get() then it returns the XML as a string into Javascript.
The Application process is getting called in both scenarios as i've put PL/SQL logging to disk in order to prove it. The XML being returned is very basic so i'm sure it's not a problem with formatting. I'm not getting any exceptions thrown in javascript either.
Is it possible to use get.get() and then convert the text into an XML object which is returned as per get.get('XML') which at least will allow me to get something working ?
thanks
<script language="JavaScript" type="text/javascript">
function getBusinessFieldJS(pThis, pSelect)
alert('getBusinessFieldJS');
try
var l_Return = null;
var l_Select = html_GetElement(pSelect);
var get = new htmldb_Get(null, html_GetElement('pFlowId').value, 'APPLICATION_PROCESS=GET_DATA_FIELDS_XML', 0);
/*get.add('F120_GETBUSINESSFIELD_ITEM',pThis.value);*/
gReturn = get.get('XML');
alert('gReturn=' + gReturn);
alert('gReturn.value=' + gReturn.value);
if (gReturn == null)
alert('gReturn is null');
if(gReturn && l_Select)
var l_Count = gReturn.getElementsByTagName("option").length;
alert('l_count='+l_Count);
l_Select.length = 0;
for(var i=0;i<l_Count;i++)
var l_Opt_Xml = gReturn.getElementsByTagName("option")+;+
+ appendToSelect(l_Select, l_Opt_Xml.getAttribute('value'),+
+ l_Opt_Xml.firstChild.nodeValue)+
+ }+
+ }+
+
get = null;+
+ }+
+ catch (e)+
+ {+
+ alert('Exception : ' + e);+
+
}+
+}+

Hi,
I've been trying to replicate your problem here: [http://apex.oracle.com/pls/otn/f?p=37055:1]
My application process is:
BEGIN
OWA_UTIL.mime_header ('text/xml', FALSE);
HTP.p('Cache-Control: no-cache');
HTP.p('Pragma: no-cache');
OWA_UTIL.http_header_close;
HTP.prn('<select>');
HTP.prn('<option value="-1">Please Select</option>');
HTP.prn('</select>');
END;(Just copied from your post and XML changed to xml, otherwise untouched)
And my page has a simple HTML region with the source of:
<div id="XMLOUTPUT" style="border:1px solid blue; width:200px; height:200px;"></div>
<div id="XMLOUTPUT2" style="border:1px solid blue; width:200px; height:200px;"></div>
<script type="text/javascript">
function getMyXML()
var l_Return = null;
var get = new htmldb_Get(null, html_GetElement('pFlowId').value, 'APPLICATION_PROCESS=RETURN_XML', 0);
gReturn = get.get('XML');
var d = html_GetElement('XMLOUTPUT');
d.innerHTML = gReturn;
var d2 = html_GetElement('XMLOUTPUT2');
d2.innerHTML = get.get();
var s = gReturn.getElementsByTagName("select");
alert(s.length);
</script>
<a href="javascript:getMyXML();">Click</a>Click on Click at the bottom of the page. The first DIV gets the get.get('XML') object and the second one the get.get() and a popup message tells you how many "select" items are in the XML version.
As far as I can see, this works fine.
Andy

How to use a cascading LOV as a Web Services Consumer?

How to use a cascading LOV as a Web Services Consumer?
We are trying to populate a prompt programmatically.
Our program is a Web Services Consumer.
As an example we use Island Resorts Marketing
The cascading LOV for City is
Country -> Region -> City
The City object is key-aware to the customer table
The query is
Customer | Revenue
(where) City = [prompt]
In order to make the key-awareness work, we must select the value (rowIndex) from the LOV
When we run our program below, the LOV for City is not populated, as expected since we must first select the Country, then the Region.
The code snippet below shows that the LOV for Country is populated. We have no idea how to go from there.
Any hint will be immensely appreciated.
Let us know if anything is unclear in the code.
Source
RetrieveMustFillInfo retrieveMustFillInfo = RetrieveMustFillInfo.Factory.newInstance();
        RetrievePromptsInfo retrievePromptInfo = RetrievePromptsInfo.Factory.newInstance();
        retrievePromptInfo.setPromptLOVRetrievalMode(PromptLOVRetrievalMode.ALL);
        retrievePromptInfo.setRefreshReturnedLOVs(true);
        retrievePromptInfo.setReturnLOVOnMustFillPrompts(true);
        retrieveMustFillInfo.setRetrievePromptsInfo(retrievePromptInfo);
        // *-- need the "Refresh" action to get the .promptToBeFilled
        Action[] boActions = new Action[1];
        boActions[0] = Refresh.Factory.newInstance();
        try {
            documentInformation = reportEngine.getDocumentInformation(Integer.toString(infoObject.getID()), retrieveMustFillInfo, boActions, null, null);
            m_Token = documentInformation.getDocumentReference();
        } catch (Exception ex) {
            System.out.println(GetWSError(ex));
            return;
        if (documentInformation.getMustFillPrompts()) {
            PromptInfo[] promptInfoS = documentInformation.getPromptInfoArray();
            for (PromptInfo promptInfo : promptInfoS) {
                System.out.println(String.format("Prompt '%1$s', hasLOV=%2$s", promptInfo.getName(), (promptInfo.getHasLOV() ? "Yes" : "No")));
                if (promptInfo.getHasLOV()) {
                    LOV boLOV = promptInfo.getLOV();
                    for (Value boLOVValue : boLOV.getValuesArray()) {
                        System.out.println(String.format(" LOV item '%1$s' RowIndex=%2$s", boLOVValue.getColumnsArray(0), (boLOV.getRowIndexed() ? boLOVValue.getRowIndex() : "")));
                System.out.println("--End LOV");
                PromptInfo[] promptInfoS2 = promptInfo.getPromptToBeFilledArray();
                if (promptInfoS2.length > 0) {
                    PromptInfo promptInfo2 = promptInfoS2[0];
                    System.out.println(String.format(" linked to %1$s", promptInfo2.getName()));
                    if (promptInfo2.getHasLOV()) {
                        LOV boLOV2 = promptInfo2.getLOV();
                        for (Value boLOVValue : boLOV2.getValuesArray()) {
                            System.out.println(String.format(" LOV item '%1$s' RowIndex=%2$s", boLOVValue.getColumnsArray(0), (boLOV2.getRowIndexed() ? boLOVValue.getRowIndex() : "")));
                        System.out.println("--End LOV");
Result
Prompt 'Enter value(s) for City:', hasLOV=Yes
--End LOV
linked to Enter value for Country of origin
LOV item 'Australia' RowIndex=6
LOV item 'France' RowIndex=2
LOV item 'Germany' RowIndex=4
LOV item 'Holland' RowIndex=7
LOV item 'Japan' RowIndex=5
LOV item 'UK' RowIndex=3
LOV item 'US' RowIndex=1
--End LOV

Hi,
Refer SAP Note 1278947. You would require a Service Market Place logon to access this article.
Let me know if this helps.
Regards,
Shreyans Surana

Apex 4.2.1 - mobile theme display bugs and Cascading LOV bug

I've setup a test at http://apex.oracle.com/pls/apex/f?p=35331 - username/password is test/test
Simple page to show some issues I'm running into. Wondering if work-arounds exist or if a patch would be available before we'd go live.
First and second issue are the same I believe. So - a normal text box (label1) looks fine. But, Label2 is a Display only item and Label3 is a read-only select list item. As you can see - both of the values appear smack dab right beside the label and not in line with the other fields. It's totally ugly and not usable as is. I've tried to move this over, but the label goes with it. I can see no way of doing it, but wondering if there's some hack I can put in to solve it...
The last issues is with a cascading LOV. Simple table setup. Static on the first, the second a simple query that filters on the first. If you set the select list to Value Required and not to display null values - then when you click on the Second List button - it just hangs. The page is unusable. I suspect this has to do with the null or something. But - doesn't appear to matter if anything is chosen. Note - if the list is large - which I think then uses a different UI control, this is fine. Only when one of the lists is small does the issue reproduce.
Any workarounds or fixes? Any ideas?
Thanks

Hi,
I would suggest to not mix different questions and a thread for each of them. Makes it easier for others to follow.
About your problem with the cascading LOVs, it appears that this is/was a bug in jQuery Mobile which we use under the hood. I was able to reproduce the problem with APEX 4.2.1 using jQM 1.2.0, but was not able to reproduce it with APEX 5.0 which will use jQM 1.3.0RC1 or higher. The problem occurs if a select list is empty.
There are different workarounds available:
1) set the attribute "HTML Form Element Attributes" of P1_CLOV_2 to data-native-menu="false"or
2) set the attribute "Display Null Value" of P1_CLOV_2 to Yes and "Null Display Value" to - select - (or something similar). The "Value Required" = Yes will still guarantee that a value has to be picked. Having the extra null entry will guarantee that the select list always contains an entry, that seems to workaround the bug in jQuery Mobile.
I have filed bug 16355963 - jquery mobile: empty select list causes javascript error
to track that this is definitely fixed in APEX 5.0.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

APEX 4: Cascading LOV generic?

Is it possible to have a "generic" cascading LOV?
I prefer to have my LOV as shared components (reuse and such) but with a cascading LOV the detail list refers to the Parent item within the query. This makes for a not very reusable LOV in my opinion.
Is it possible to use a more generic bind?
select description d, id r
from table
where parent = :B --<--- Not refering to any particular Page Item
order by 1... and specify the actual item which is to be used in the detail query? (Page Items to Submit)

Hi Learco,
I doubt that this will work, because the "Cascading LOV Parent Item" has to be a page item which is actually rendered into the HTML page. The reason is that for those page items we register a "change" event to trigger the refresh of the childs. If it's an application item it would not exist on the page.
I would also question if dealing with additional application items and additional dynamic actions would make the code better maintainable. If the LOV query is really that complicated that it would be beneficial to re-use it, I would suggest to define a database view for it and then again use a very simple LOV statement to access it. I think that would make it much more transparent and maintainable then trying some generic bind variables and placeholders.
Just my 2 cents
Patrick
PS: yes, nice colors ;-)
My Blog: http://www.inside-oracle-apex.com
APEX 4.0 Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Problems with 4.1.1.00.23 Cascading LOVs

I have a pages with 4 levels of cascading LOVs. These are:
MEMBER_ID => ACCOUNT => COMMODITY => EXPIRY
The issue I am running into is that these work fine up through the first three and then fails (or rather simply doesn't do anything) on EXPIRY. I have no idea what or what to do to get this last level to populate. I have confirmed, using the values present in the session that the query for EXPIRY should return data.
The top level is a simply Select List Control using a Named LOV with this query:
select
case organization_type
when 'Member' then NAME || Chr(32) || LEGAL_NAME
when 'Bank' then LEGAL_NAME
end d,
ID r
from mbrdata.ORGANIZATION
order by name, legal_nameThe next level, ACCOUNT, is set up as a cascading LOV. The parent is the MEMBER_ID.
Named LOV
Display Extra Values
Display Null Value
Cascading LOV Parent Item(s)     P15_MEMBERID
Page Items to Submit
Optimize Refresh     YES
List of values definition
SELECT DISTINCT MARGINING_ACCOUNT d, MARGINING_ACCOUNT r
FROM MBRDATA.INTRADAY_MARGIN_MONITOR
WHERE ORG_ID = :P15_MEMBERID
ORDER BY 1The next level, COMMODITY, is set up as a cascading LOV. The parent is the ACCOUNT.
Named LOV
Display Extra Values
Display Null Value
Cascading LOV Parent Item(s)     P15_MEMBERID,P15_ACCOUNTID
Page Items to Submit
Optimize Refresh     YES
List of values definition
SELECT DISTINCT PHYSICAL_COMMODITY D, PHYSICAL_COMMODITY R
FROM
    SELECT PHYSICAL_COMMODITY,
           DENSE_RANK() OVER
            ( PARTITION BY ORIG_CLEARER_NAME, MARGINING_ACCOUNT
              ORDER BY RUNTIME DESC ) AS RUNTIME_RANK
    FROM RISKDM2.INTRADAY_POSITION
    JOIN MBRDATA.ORGANIZATION
        ON ( INTRADAY_POSITION.ORIG_CLEARER_NAME = ORGANIZATION.NAME )
    WHERE ORGANIZATION.ID = :P15_MEMBER_OR_TRADER AND
          MARGINING_ACCOUNT = :P15_MARGINING_ACCOUNT
WHERE RUNTIME_RANK = 1The next level, EXPIRY, is set up as a cascading LOV. The parent is the COMMODITY.
Named LOV
Display Extra Values
Display Null Value
Cascading LOV Parent Item(s)     P15_MEMBERID,P15_ACCOUNTID,P15_COMMODITYID
Page Items to Submit
Optimize Refresh     YES
List of values definition
SELECT DISTINCT EXPIRY_DATE AS D, EXPIRY_DATE AS R
FROM
    SELECT EXPIRY_DATE,
           DENSE_RANK() OVER
            ( PARTITION BY ORIG_CLEARER_NAME, MARGINING_ACCOUNT
              ORDER BY RUNTIME DESC ) AS RUNTIME_RANK
    FROM RISKDM2.INTRADAY_POSITION
    JOIN MBRDATA.ORGANIZATION
        ON ( INTRADAY_POSITION.ORIG_CLEARER_NAME = ORGANIZATION.NAME )
    WHERE ORGANIZATION.ID = :P15_MEMBER_OR_TRADER AND
          MARGINING_ACCOUNT = :P15_MARGINING_ACCOUNT AND
          PHYSICAL_COMMODITY = :P15_PHYSICAL_COMMODITY
WHERE RUNTIME_RANK = 1Any ideas? I know I am just doing something dumb but, with me, I require and more specific example of my dumbness.
Thanks,
-Joe

Hi Joe,
looks like you don't reference the parent lov's items in the sql queries for ACCOUNT, COMMODITY and EXPIRY.
Are there any processes (DA, Ajax etc.) that you use to populate the items :P15_MEMBER_OR_TRADER, :P15_MARGINING_ACCOUNT and :P15_PHYSICAL_COMMODITY in those queries?
regards,
Erik-jan

Are cascading LOVs possible in af:query?

Similar Messages

Maybe you are looking for