Issue in Dependant LOV

Hi ,
I have two lovs in a table region
Say Department and Employee, Employee LOV is dependant on department lov ( normal depndant lov's). While I am creating the records it is working fine. But i have another option to update. If I click on that button records became updatable state, issue is But if i want to change the employee without changing the department, it is showing the complete employee list, if i go to department field and do some operations there and come to employee it is working fine. How can i solvethis issue?

Its weird!! Did you try raising an exception in the LOV window when there is no value found in the LOV?? Moreover, give a try resetting VO and clearing cache before executing the VO relating to the LOV
VO.reset();
VO.clearcache()
Regards
Pavan, K

Similar Messages

Dependent LOVs not populated properly

Hi,
I have an issue regarding dependent LOVs in one of our pages.
1. Child Lov is unable to fetch the results depending on Parent Lov value. Parent Value is not added to the where clause in the query while getting results for child lov.
This is happening only when the user enters some value like (%) in child text box and tab out.
2. If the user directly clicks on child lookup and then enter some search criteria and Click Enter. It works as expected. In this case it is taking the parent lov value and giving the results properly.
I think we may be missing some property to be set in case1. If anyone aware of this issue please help me out with a solution.
It is related to banks and branches in banks... Due to this issue when I search for branches after selecting a bank.... all the branches are shown in the results.
Regards,
Pavani
Thanks in Advance,
Pavani

MY pg.xml with bank and branch LOVs :
<oa:rowLayout id="BankBranchRowRN" width="100%">
<ui:contents>
<oa:cellFormat id="BankBranchCellFormatRN">
<ui:contents>
<oa:tableLayout id="BankBranchTblLayoutRN" hAlign="center" width="100%">
<ui:contents>
<oa:rowLayout id="BankBranchRow1RN">
<ui:contents>
<oa:cellFormat id="BankRN" hAlign="start" vAlign="top">
<ui:contents>
<oa:header id="BankHeaderRN" text="Bank">
<ui:contents>
<oa:messageRadioGroup id="BankSelectChoice" pickListViewDef="" pickListDispAttr="Name" pickListValAttr="Code" defaultValue="OLD" viewName="SuppNwActPVO" viewAttr="BankSelectFlag" serverUnvalidated="true" pickListViewName="IbyBankSelectVO" shortDesc="Select Bank" rendered="${oa.SuppNwActPVO.ShowChoiceList}">
<ui:primaryClientAction>
<ui:firePartialAction event="BankSelect" unvalidated="true">
<ui:parameters>
<ui:parameter key="Selected" value="${oa.current.BankSelectFlag}"/>
</ui:parameters>
</ui:firePartialAction>
</ui:primaryClientAction>
</oa:messageRadioGroup>
<oa:messageComponentLayout id="BankMasterRN">
<ui:contents>
<oa:messageTextInput id="BankNameInput" maximumLength="360" viewName="SuppNwActVO" viewAttr="BankName" prompt="Bank Name" rendered="${oa.SuppNwActPVO.BankNewFlag}"/>
<oa:messageLovInput id="BankNameSelect" prompt="Bank Name" viewName="SuppNwActVO" viewAttr="BankName" maximumLength="360" rendered="${oa.SuppNwActPVO.BankOldFlag}" externalListOfValues="/oracle/apps/pos/lov/webui/ExtBanksLovRN">
<lovMappings>
<lovMap id="lovMap2" lovItem="BankName" resultTo="BankNameSelect" criteriaFrom="BankNameSelect"/>
<lovMap id="lovMap3" lovItem="BankNumber" resultTo="BankNumber"/>
<lovMap id="lovMap7" lovItem="AddressLine1" resultTo="BankAddress1"/>
<lovMap id="lovMap8" lovItem="AddressLine2" resultTo="BankAddress2"/>
<lovMap id="lovMap9" lovItem="AddressLine3" resultTo="BankAddress3"/>
<lovMap id="lovMap10" lovItem="City" resultTo="BankCity"/>
<lovMap id="lovMap11" lovItem="State" resultTo="BankState"/>
<lovMap id="lovMap12" lovItem="AltBankName" resultTo="AltBankName"/>
<lovMap id="lovMap13" lovItem="ZipCode" resultTo="BankZipCode"/>
<lovMap id="lovMap14" lovItem="Country" resultTo="BankCountry"/>
<lovMap id="lovMap28" lovItem="BankPartyId" resultTo="BankId"/>
<lovMap id="lovMap31" lovItem="AddressLine4" resultTo="BankAddress4"/>
<lovMap id="lovMap32" lovItem="HomeCountry" resultTo="Country" criteriaFrom="Country"/>
</lovMappings>
</oa:messageLovInput>
<oa:messageTextInput id="BankNumber" prompt="Bank Number" viewName="SuppNwActVO" viewAttr="BankNumber" maximumLength="30" disabled="${oa.SuppNwActPVO.BankNoUpdateFlag}"/>
<oa:messageLayout id="bankHiddenFieldRN">
<ui:contents>
<oa:formValue id="BankId" viewName="SuppNwActVO" viewAttr="BankId" dataType="NUMBER"/>
</ui:contents>
</oa:messageLayout>
</ui:contents>
</oa:messageComponentLayout>
<oa:hideShow id="BankDetailHideShowRN" disclosedText="Hide Bank Details" undisclosedText="Show Bank Details" serverUnvalidated="true" unvalidated="true" viewName="SuppNwActVO" viewAttr="BANKHIDESHOW">
<ui:contents>
<oa:header id="BankDetailsHdrRN" text="Details">
<ui:contents>
<oa:messageComponentLayout id="BankDetailsRN">
<ui:contents>
<oa:messageTextInput id="AltBankName" prompt="Alternate Bank Name" viewName="SuppNwActVO" viewAttr="BankNameAlt" maximumLength="320" disabled="${oa.SuppNwActPVO.BankNoUpdateFlag}"/>
</ui:contents>
</oa:messageComponentLayout>
</ui:contents>
</oa:header>
<oa:header id="BankAddressHdrRN" text="Address">
<ui:contents>
<oa:messageComponentLayout id="BankAddressRN">
<ui:contents>
<oa:messageTextInput id="BankAddress1" prompt="Address Line 1" viewName="SuppNwActVO" viewAttr="BankAddressLine1" maximumLength="240" disabled="${oa.SuppNwActPVO.BankNoUpdateFlag}"/>
<oa:messageTextInput id="BankAddress2" prompt="Address Line 2" viewName="SuppNwActVO" viewAttr="BankAddressLine2" maximumLength="240" disabled="${oa.SuppNwActPVO.BankNoUpdateFlag}"/>
<oa:messageTextInput id="BankAddress3" prompt="Address Line 3" viewName="SuppNwActVO" viewAttr="BankAddressLine3" maximumLength="240" disabled="${oa.SuppNwActPVO.BankNoUpdateFlag}"/>
<oa:messageTextInput id="BankAddress4" disabled="${oa.SuppNwActPVO.BankNoUpdateFlag}" maximumLength="240" viewName="SuppNwActVO" viewAttr="BankAddressLine4" prompt="Address Line 4"/>
<oa:messageTextInput id="BankCity" prompt="City" viewName="SuppNwActVO" viewAttr="BankCity" maximumLength="60" disabled="${oa.SuppNwActPVO.BankNoUpdateFlag}"/>
<oa:messageTextInput id="BankState" prompt="State" viewName="SuppNwActVO" viewAttr="BankState" maximumLength="60" disabled="${oa.SuppNwActPVO.BankNoUpdateFlag}"/>
<oa:messageTextInput id="BankZipCode" prompt="Zip Code" viewName="SuppNwActVO" viewAttr="BankZip" maximumLength="60" disabled="${oa.SuppNwActPVO.BankNoUpdateFlag}"/>
<oa:messageLovChoice id="BankCountry" prompt="Country" viewName="SuppNwActVO" viewAttr="BankCountry" disabled="${oa.SuppNwActPVO.BankNoUpdateFlag}" externalListOfValues="/oracle/apps/pos/lov/webui/CountryLovRN" pickListDispAttr="TerritoryShortName" pickListValAttr="TerritoryCode" rendered="false">
<lovMappings>
<lovMap id="lovMap4" lovItem="TerritoryCode" resultTo="BankCountry"/>
</lovMappings>
</oa:messageLovChoice>
</ui:contents>
</oa:messageComponentLayout>
</ui:contents>
</oa:header>
</ui:contents>
</oa:hideShow>
</ui:contents>
</oa:header>
</ui:contents>
</oa:cellFormat>
<oa:cellFormat id="BranchRN" hAlign="start" vAlign="top">
<ui:contents>
<oa:header id="BranchHeaderRN" text="Branch">
<ui:contents>
<oa:messageRadioGroup id="BankBranchSelectChoice" pickListViewDef="" pickListDispAttr="Name" pickListValAttr="Code" defaultValue="OLD" viewName="SuppNwActPVO" viewAttr="BranchSelectFlag" serverUnvalidated="true" pickListViewName="IbyBankBranchSelectVO" shortDesc="Select Branch" rendered="${oa.SuppNwActPVO.ShowChoiceList}">
<ui:primaryClientAction>
<ui:firePartialAction event="BankBranchSelect" unvalidated="true"/>
</ui:primaryClientAction>
</oa:messageRadioGroup>
<oa:messageComponentLayout id="BranchMasterRN">
<ui:contents>
<oa:messageTextInput id="BranchNameInput" viewName="SuppNwActVO" viewAttr="BranchName" prompt="Branch Name" maximumLength="360" rendered="${oa.SuppNwActPVO.BranchNewFlag}"/>
<oa:messageLovInput id="BranchNameSelect" prompt="Branch Name" viewName="SuppNwActVO" viewAttr="BranchName" maximumLength="360" rendered="${oa.SuppNwActPVO.BranchOldFlag}" externalListOfValues="/oracle/apps/pos/lov/webui/ExtBankBranchesLovRN">
<lovMappings>
<lovMap id="lovMap15" lovItem="BankBranchName" resultTo="BranchNameSelect" criteriaFrom="BranchNameSelect"/>
<lovMap id="lovMap16" lovItem="Address1" resultTo="Address11"/>
<lovMap id="lovMap17" lovItem="Address2" resultTo="Address21"/>
<lovMap id="lovMap18" lovItem="Address3" resultTo="Address31"/>
<lovMap id="lovMap19" lovItem="City" resultTo="City1"/>
<lovMap id="lovMap20" lovItem="State" resultTo="State1"/>
<lovMap id="lovMap21" lovItem="ZipCode" resultTo="ZipCode1"/>
<lovMap id="lovMap22" lovItem="Country" resultTo="Country11"/>
<lovMap id="lovMap23" lovItem="BranchNumber" resultTo="BranchNumber"/>
<lovMap id="lovMap24" lovItem="AltBranchName" resultTo="AltBranchName"/>
<lovMap id="lovMap25" lovItem="EftSwiftCode" resultTo="BIC"/>
<lovMap id="lovMap26" lovItem="BankBranchType" resultTo="BranchType"/>
<lovMap id="lovMap27" lovItem="RFCIdentifier" resultTo="RFCIdentifier"/>
<lovMap id="lovMap29" lovItem="BankBranchPartyId" resultTo="BranchId"/>
<lovMap id="lovMap30" lovItem="Address4" resultTo="Address41"/>
<lovMap id="lovMap42" lovItem="BankName" resultTo="BankNameSelect"/>
<lovMap id="lovMap43" lovItem="BankNumber" resultTo="BankNumber"/>
<lovMap id="lovMap47" lovItem="BankAddressLine1" resultTo="BankAddress1"/>
<lovMap id="lovMap48" lovItem="BankAddressLine2" resultTo="BankAddress2"/>
<lovMap id="lovMap49" lovItem="BankAddressLine3" resultTo="BankAddress3"/>
<lovMap id="lovMap410" lovItem="BankCity" resultTo="BankCity"/>
<lovMap id="lovMap411" lovItem="BankState" resultTo="BankState"/>
<lovMap id="lovMap412" lovItem="AltBankName" resultTo="AltBankName"/>
<lovMap id="lovMap413" lovItem="BankZipCode" resultTo="BankZipCode"/>
<lovMap id="lovMap414" lovItem="BankCountry" resultTo="BankCountry"/>
<lovMap id="lovMap428" lovItem="BankPartyId" resultTo="BankId" criteriaFrom="BankId"/>
<lovMap id="lovMap431" lovItem="BankAddressLine4" resultTo="BankAddress4"/>
<lovMap id="lovMap432" lovItem="HomeCountry" resultTo="Country" criteriaFrom="Country"/>
</lovMappings>
</oa:messageLovInput>
<oa:messageTextInput id="BranchNumber" prompt="Branch Number" viewName="SuppNwActVO" viewAttr="BranchNumber" maximumLength="30" disabled="${oa.SuppNwActPVO.BranchNoUpdateFlag}"/>
<oa:messageTextInput id="BIC" prompt="BIC" viewName="SuppNwActVO" viewAttr="Bic" maximumLength="30" disabled="${oa.SuppNwActPVO.BranchNoUpdateFlag}"/>
<oa:messageChoice id="BranchType" prompt="Branch Type" viewName="SuppNwActVO" viewAttr="BranchType" disabled="${oa.SuppNwActPVO.BranchNoUpdateFlag}" pickListDispAttr="DisplayedField" pickListValAttr="LookupCode" pickListViewName="BankBranchTypeVO" allowBlankValue="false"/>
<oa:messageLayout id="branchHiddenFieldRN">
<ui:contents>
<oa:formValue id="BranchId" viewName="SuppNwActVO" viewAttr="BranchId" dataType="NUMBER"/>
</ui:contents>
</oa:messageLayout>
</ui:contents>
</oa:messageComponentLayout>
<oa:hideShow id="BranchDetailHideShowRN" disclosedText="Hide Branch Details" undisclosedText="Show Branch Details" serverUnvalidated="true" unvalidated="true" viewName="SuppNwActVO" viewAttr="BRANCHHIDESHOW">
<ui:contents>
<oa:header id="BranchDetailsHdrRN" text="Details">
<ui:contents>
<oa:messageComponentLayout id="BranchDetailsRN">
<ui:contents>
<oa:messageTextInput id="AltBranchName" prompt="Alternate Branch Name" viewName="SuppNwActVO" viewAttr="BranchNameAlt" maximumLength="320" disabled="${oa.SuppNwActPVO.BranchNoUpdateFlag}"/>
<oa:messageTextInput id="RFCIdentifier" prompt="RFC Identifier" viewName="SuppNwActVO" viewAttr="RfcIdentifier" maximumLength="30" disabled="${oa.SuppNwActPVO.BranchNoUpdateFlag}"/>
</ui:contents>
</oa:messageComponentLayout>
</ui:contents>
</oa:header>

Issue in creating dependent LOV

Hi,
I am creating a dependentLOV Items.
1) Selecting Project Number.
2) List of Tasks in the selected Projects.
when ever user selects particular project number in 1st LOV item the list of tasks assossiated to that project should be
populated in 2 nd LOV.
Can any one suggest.
Regards,
Krishna

Hi Reetesh,
I am unable to create dependency.
VO Querys of Projects and Tasks
Projects VO
select a.SEGMENT1,a.NAME,a.PROJECT_ID
from pa_projects_all a
TasksVO
select a.TASK_NUMBER,a.TASK_NAME,a.PROJECT_ID
from pa_tasks a
I am explaing the steps I have done just show where I met error.
1) Create ProjectsLOVRN (projectno,name,projectId) TasksLOVRN (TaskNumber,Name,ProjectId)
2) Create 2 LOV Items Projects and Tasks
3)In Projects LOV I created 2 LOV Maps which returns Project No and Project Id
4)In Tasks LOV created 2 LOV Maps as you suggested
in first map LOV Region Item TasksLOVRN(TaskNumber)
Criteria Item returned ProjectId from ProjectsLOVRN
Required and Programatic Query is set to true
for crieteria item will be the Project LOv Item how can I select an ProjectsLOV Item in TasksLOV
in second map
LOV Region Item TasksLOVRN(TaskNumber)
return Item LOV ItemTask
While running page At header I am getting an error
Error
Developer Mode Exception : Lov Input should by default be the queryable criteria and Result.
Please suggest where exactly Iam making mistake to create Dependent LOV
Regards,
Krishna

Getting error in dependent LOV

jdev version: 10.1.3.3
I have a dependent LOV in a page. It works fine except in one scenario. When I enter partial value in dependent LOV field and click torch icon, it gives following error:
Exception Details.
oracle.apps.fnd.framework.OAException: oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation. Statement: SELECT * FROM (SELECT org.organization_id, org.name org_name, org.attribute1 product_group, decode(org.attribute6, 'Y', 'Union', 'Non-Union') union_indicator, org.attribute7 union_name, bg.name bg_name
FROM hr_all_organization_units org
, hr_all_organization_units bg
WHERE SYSDATE BETWEEN NVL(org.date_from, SYSDATE) AND NVL(org.date_to, SYSDATE)
AND bg.organization_id = org.business_group_id
AND bg.name = 'Test BG'
AND SYSDATE BETWEEN NVL(bg.date_from, SYSDATE) AND NVL(bg.date_to, SYSDATE)
ORDER BY org.name) QRSLT WHERE (product_group = :1 AND ( UPPER(ORG_NAME) like UPPER(:2) AND (ORG_NAME like :3 OR ORG_NAME like :4 OR ORG_NAME like :5 OR ORG_NAME like :6)))
## Detail 0 ##
java.sql.SQLException: Invalid column type
In order to populate dependent LOV based on independent LOV value, in LOV region CO.processRequest(), I am executing following am method:
public void executeOrgLov(String criteria)
OAViewObjectImpl vo = getLegalChgOrganizationsVO1();
vo.setWhereClause("product_group = :1");
vo.setWhereClauseParams(null);
vo.setWhereClauseParam(0,criteria);
vo.executeQuery();
Any suggestion/help in this regard is highly appreciated.
Thanks

Hi,
modify your code as follow,
public void executeOrgLov(String criteria)
OAViewObjectImpl vo = getLegalChgOrganizationsVO1();
//vo.setWhereClause("product_group = :1");
//vo.setWhereClauseParams(null);
//vo.setWhereClauseParam(0,criteria);
// I assume criterian is a string variable.
if (criteria!=null) {
vo.setWhereClause("product_group = "+criteria);
vo.executeQuery();
I hope it will solve your issue.
Haroon.

How to incorporate dependent LOV in an Advanced Table

Hi,
I have an "Advanced Table". Two columns are LOV columns.
Eg.
In the first column I have an DeptLOV and second column has EmployeenameLOV.
In first Column DeptLOV I choose say Deptno 10 and it should filter and list only the names of the employees in the second column EmployeenameLOV it should list only the employees of Departnumber 10 and I should be able to pick one employeename from EmployeeNameLOV.
I should be able to choose different Dept number and corresponding employee name in LOV different in each row.
Thanks in advance.
Lacman

Thanks for you reply.
But the issue is the dependent LOV inside an advanced table as described in my earlier post.
Advanced table with dependent LOVs
. c1 c2
r1
r2
r3
If an end user clicks on r1c1 LOV. He should be allowed only to click on r1c2. If clicks on r1c1 and directly clicks r2c2 he should not be allowed.
How to accomplish this in an Advanced table in which the second column LOV is dependent on the first LOV.
Regards,
Laxman
Edited by: lacman on Nov 18, 2009 7:19 PM

Can't create multiple dependent LOVs from the same bind variable

Hi all,
I'm having difficulty creating multiple dependent LOVs from queries based on the same bind variable in my JSF application (JDev 10.1.3.1). Basically I have a static LOV in a af:selectOneChoice component from which users select a value which then becomes the bind variable value for two separate queries that generate two different dependent LOV. Having developed the code along the lines of Steve Muench 's blog (http://radio.weblogs.com/0118231/2006/04/03.html#a685), the first dependent LOV works really well. The first dynamic LOV gets refreshed whenever the list from the static LOV changes, and I can execute other queries based on the values selected.
The problem arises when I want to create the second dynamic/dependent LOV that has the same bind variable based on the same selected value from the static LOV. Here I would also like the functionality whereby the second dynamic LOV is also refreshed after the selected value in the static LOV changes. Thinking that all I had to do was replicate the methodology used in creating the first dependent LOV, I created the second iterator, invokeAction and other binding components in the PageDef. The executable section now looks like the following:
<iterator id="SelectStaticQueryViewObjIterator"
 Binds="SelectStaticQueryViewObj" RangeSize="-1"
 DataControl="DMSApplicationModule1DataControl"/>
<invokeAction id="refreshDynamicQuery1BindParameter"
 Binds="ExecuteWithParams1" Refresh="prepareModel"
 RefreshCondition="#{empty requestScope.VariableChanged}"/>
<iterator id="SelectDynamicQuery1ViewObjIterator"
 Binds="SelectDynamicQuery1ViewObj" RangeSize="-1"
 DataControl="DMSApplicationModule1DataControl"/>
<invokeAction id="refreshDynamicQuery2BindParameter"
 Binds="ExecuteWithParams2" Refresh="prepareModel"
 RefreshCondition="#{empty requestScope.VariableChanged}"/>
<iterator id="SelectDynamicQuery2ViewObjIterator"
 Binds="SelectDynamicQuery2ViewObj" RangeSize="-1"
 DataControl="DMSApplicationModule1DataControl"/>I now have a problem whereby everytime I change the value of the static LOV, multiple HTML components for the same ADF component are being generated (the LOVs are refreshed via PPR). The surprising thing is that this duplicating behaviour applies to all ADF components listed after the first dynamic LOV in the *.jspx source. For example, I have a <af:outputText="Test Text"/> component created after the first dynamic LOV. Each time the value in the static LOV changes, a duplicate HTML component is created. This also applies to the 'related' second dynamic LOV which is bound to a af:selectOneChoice component - multiple dropdown lists are created. I've checked with the browser's Page Source and there are actually multiple html components being generated with their own unique ADF-generated IDs. I've tried all different options for the Referesh and RefreshCondition attibutes in the second invokeAction element but nothing seems to eliminate this issue.
Any suggestions about how I might create multiple dependent LOVs from the same bind variable that get refreshed when the selected value changes would be greatly appreciated.
Thanks
George

Hi all,
Just updating the thread on how I've overcome this issue. As it stood the manner in which I was trying to solve my use case, as described above, was creating an absolute mess. Then with a blank sheet of paper I quickly realised that a much simpler solution would be to create a whole series of master-detail VOs and build my components around them. Thankfully I haven't had any issues going down this path as yet.
Cheers
George

Dependent LOV not Working

Hi ,
iam creating a page where there is a dependent LOV's
DJLov,SEQLov are the Lovinput items
Djid is common field between the 2 Lov queries ,WipEntityid is formValue
when i click on second lov iam getting error as "You must enter a value for WipEntityId as criteria for LOV."
LOV1:
LovregionItem:Djnumber
Return Item:DJLov
Criteria Item:DJLov
LovregionItem:Djid
Return Item:WipEntityid
LOV2:
LovregionItem:OperSeqnum
Return Item:SEQLov
Criteria Item:SEQLov
LovregionItem:Djid_SeQ
Criteria Item:WipEntityid
Required: True
can anybody help me regarding this.
if the above data is not suffcient to understand the issue please ask me i will provide some more.
one more thing i want to mention is:
i took an advanced table ,then created columns and added LOv items to the columns. i got the error
"You must enter a value for WipEntityId as criteria for LOV."
but i created another page with tablelayout-->rowlayout-->cellformat-->lov input items
the same Lov mappings were done ,the page got saved without any issue.
can anybody figure out the what is the issue.
Thanks in Advance

Hi guys,
this issue is fixed.i created formvalues under advancedtable region and it worked.
dont keep formvalues to Pagelayout RN.
hopes this info will help OAF starters like me. :)

Dependant LOV is not working sometimes???

Hi Everyone,
i have created one dependant LOV. Lov1(Dept) and Lov2(Eno).
When i select any dept from first LOV it will trigger one OnChange() Event and there i am taking the dept name passing to the Employee table to filter corresponding ENOs in Lov2.
It works sometimes fine but sometimes it shows blank records in Lov2 but in backed Lov2 is having records.
what can be the issue?
Thanks.

Kumar,
mention your jdev version and teck stack always before asking any query.
what do you mean by 'sometimes' it is not working? in which case it's not working? when you are getting blank values in you dependent lov, have you checked that the query (for the dependent lov) is returning any record?
~Abhijit

Dependant LOV

Greetings !!!
I have a requirement like this
There are 2 fields with LOVs as type and GO button.
1 . Customer Number
2 . Invoice Number
a) Suppose if user selected Customer Number from its LOV, then all invoice number related to that customer should be available in the "Invoice Number" LOV.
b) Suppose if user directly selects Invoice Number from its LOV... this LOV should contains all the invoice numbers. now the customer number field will be empty.
I thought of doing Dependant LOV for this scenario but could not proper logic for this case.
Any suggestions please ?????
Thanks

Guys,
First of all I want to thank to all for your valuable suggestions but the unfortunate thing is still I am facing the issue.
I have made the following combinations:
1) vo Query is "select distinct a.trx_number InvoiceNumber
     from ra_customer_trx_all a, hz_cust_accounts b where a.bill_to_customer_id = b.cust_account_id"
Code in Controller
vo.setWhereClause("and b.account_number = " +Acc_Num);
Error:
Exception Details.
oracle.apps.fnd.framework.OAException: oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation. Statement: SELECT * FROM (select distinct a.trx_number InvoiceNumber
from ra_customer_trx_all a, hz_cust_accounts b where a.bill_to_customer_id = b.cust_account_id) QRSLT WHERE (and b.account_number = 104333109 AND ( UPPER(INVOICENUMBER) like :1 ))
     at oracle.apps.fnd.framework.OAException.wrapperException(Unknown Source)
## Detail 0 ##
java.sql.SQLException: ORA-00936: missing expression
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)
2) Vo Query is "select distinct a.trx_number InvoiceNumber
from ra_customer_trx_all a, hz_cust_accounts b where a.bill_to_customer_id = b.cust_account_id and"
Code in Controller
vo.setWhereClause("b.account_number = " +Acc_Num);
Error:
Exception Details.
oracle.apps.fnd.framework.OAException: oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation. Statement: SELECT * FROM (select distinct a.trx_number InvoiceNumber
from ra_customer_trx_all a, hz_cust_accounts b where a.bill_to_customer_id = b.cust_account_id and) QRSLT WHERE (b.account_number = 104333109 AND ( UPPER(INVOICENUMBER) like :1 ))
     at oracle.apps.fnd.framework.OAException.wrapperException(Unknown Source)
## Detail 0 ##
java.sql.SQLException: ORA-00936: missing expression
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)
3) Vo Query is "select distinct a.trx_number InvoiceNumber
from ra_customer_trx_all a, hz_cust_accounts b where a.bill_to_customer_id = b.cust_account_id and b.account_number = :1"
Code in Controller
vo.setWhereClauseParam(0,Acc_Num);
For this option it is executing perfectly for the first time. I mean when we search by putting "%" in LOv is is retrieving proper values based on Account Number. When you re-query again it is giving the following error.
Error:
Exception Details.
oracle.apps.fnd.framework.OAException: oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation. Statement: SELECT * FROM (select distinct a.trx_number InvoiceNumber
from ra_customer_trx_all a, hz_cust_accounts b where a.bill_to_customer_id = b.cust_account_id and b.account_number = :1) QRSLT WHERE (( UPPER(INVOICENUMBER) like :2 AND (INVOICENUMBER like :3 OR INVOICENUMBER like :4 OR INVOICENUMBER like :5 OR INVOICENUMBER like :6)))
     at oracle.apps.fnd.framework.OAException.wrapperException(Unknown Source)
## Detail 0 ##
java.sql.SQLException: Invalid column type
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:175)
Any more suggestions please.......

ADF Desktop Integration: How do I use dependent LOVs in Table Components?

Hi,
I have a table component that has a series of dependent LOVs. Now, while I understand that ADFdi allows for LOVs to be chained together by dependency, what I don't understand is how to get the child values to change based on a selection of a parent value. Is there a method binding I missed? Or is there some other mechanism I'm not seeing in the documentations? Hope someone can help shed some light on it - Google is darkness. Thanks.
Cheers,
Benjamin

Repost

Dependent LOVs in form

Guys,
I do have two fields of LOV types on my form
LOV attached to first field should display all the department. And second field should display all the employees assigned to the department selected in first field. Thats how I need dependent LOVs.. can you please guide me how it can be achieved.
Thanks
Sunil

Hi Sunil
second field should display all the employees assigned to the department selected in first field. Thats how I need dependent LOVs.Here is an example...
Let's Suppose u have a rel between dept & emp table related with a FK called DEPT_NO that's what it should be
Now when u select the 1st Lov it will disploay the DEPT_NO of the dept u selected this DEPT_NO will be displayed on ur form or will be hidden it doesn't matter.
Now in the second LOV Record group u should write a similar select statment as follow...
SELECT EMP_NAME,... etc.
FROM EMP
WHERE DEPT_NO = :DEPT_NO ; Pls note that :DEPT_NO is the number of the department selected form the first lov in ur form, then all emp data will be displayed according to this DEPT_NO as ependent LOVs.
Another approach u should be aware and think about it...
u could u a drop down list dependent on one another specially if u don't have large number of departments in ur company.
Hope this helps...
Regards,
Amatu Allah.

Dependent LOVs in Discoverer Admin

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

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

Mandatory fields on the same page with dependent LOVs

Hi,
I am working on an ADF-BC application using JDeveloper 10.1.3.4
I have an ADF Creation form with dependent LOVs and while implementing dependent LOVs we set the autoSubmit property of the selectOneChoiceListBox as true.
If I have some mandatory fields on the same page then because of the autoSubmit property set as true whenever I select a value in the list the page gets submitted and the mandatory fields give an error that the values are required therefore I had to remove the mandatory fields.
I tried using f:subview but even that dint serve the purpose because what I want is something like partialSubmit so that my mandatory fields do no give an error when I select a value in the list.
Can somebody help me on this, how to have a dependent list and mandatory fields on the same page.
P.S: It is very crucial for my application
Thanks,
Raksha

Hello,
This bug has been around since 10.1.3, its even still present in Trinidad and now in 11.
One of the ways to avoid is to make your fields use:
showRequired="true"instead of
required="true"I have not found a decent way to avoid this in general.
My idea was that this shiould be possible with a phaselistener and determine if this is a partial page event instead of a normal submit, but this didnt work.
-Anton

How to create dependent LOV in Advanced Table.

Hi,
How to create dependent LOV in Advanced Table. Pls help send me the steps.
Thanks in Advance,
Hanimi....

Hi,
Not sure whether you need dependent LOV or dependent poplist. But anyways, you can refer the below link for Dependent LOV
http://oraclearea51.com/component/content/article/98-oa-framework/372-dependent-lov-in-oaf.html
and for Dependent Poplist refer the below link:
http://oraclearea51.com/component/content/article/98-oa-framework/370-dependent-poplist-in-an-advanced-table-in-oaf.html
Regards,
Sudhakar Mani
http://oraclearea51.com/sudhakarmani

Dependent LOV throws Exception

Hello,
I want to implement a dependent LOV:
I have a LOV Competency and a dependent Proficiency LOV.
e.g. in Competence LOV I search for Oracle DBA then I only want the Proficiency level concering to Oracle DBA
e.g. certified, not certified.
The leading Competence LOV I have, does have the following select:
SELECT COMPETENCE_ID,
SEGMENT1
FROM PER_COMPETENCES_V
ORDER BY COMPETENCY
The dependent Proficiency LOV
SELECT cpl.COMPETENCE_ID,
cpl.NAME COMPETENCY,
cmp.RATING_SCALE_ID,
rsl.NAME RATING_SCALE_NAME,
rtl.RATING_LEVEL_ID,
rtx.NAME RATING_SCALE_LEVEL_NAME
FROM PER_COMPETENCES cmp,
PER_COMPETENCES_TL cpl,
PER_RATING_SCALES rsc,
PER_RATING_SCALES_TL rsl,
PER_RATING_LEVELS rtl,
PER_RATING_LEVELS_TL rtx
WHERE 1=1
AND cpl.COMPETENCE_ID = cmp.COMPETENCE_ID
AND cpl.LANGUAGE = USERENV ('LANG')
AND cmp.RATING_SCALE_ID =rsc.RATING_SCALE_ID(+)
AND cmp.RATING_SCALE_ID = rsl.RATING_SCALE_ID(+)
AND rsl.LANGUAGE(+) = USERENV ('LANG')
AND rtl.RATING_SCALE_ID IS NOT NULL
AND rtl.RATING_LEVEL_ID = rtx.RATING_LEVEL_ID
AND rtx.LANGUAGE = USERENV ('LANG')
AND rtl.RATING_SCALE_ID = rsc.RATING_SCALE_ID
AND rsc.TYPE='PROFICIENCY'
ORDER BY cmp.COMPETENCE_ID, rtx.RATING_LEVEL_ID
In both LOV Regions I use form values as NUMBER fields.
form values:
Competency LOV =>Competence_ID (Number)
Proficiency LOV =>Competence_ID (Number),Rating_Level_ID (Number)
Then I did the mappings for both LOVs. Additionally to Proficiency LOV mapping
I add a mapping to get a conjunction between from Proficiency Level to Competence LOV
The necessary mapping within Proficiency Level Region is as follows.
LOV Region Item =>xxmiProfCompetenceID
Criteria Item => CompLOV
Everything renders fine, I can choose a comptency with a return value but when I search for a dependent Proficiency level
I got the following error message =>
The value Oracle DBA specified for the item xxmiProfCompetenceID
oracle.apps.fnd.framework.OAException: The value Oracle DBA specified for the item xxmiProfCompetenceID is an invalid number.
I have checked the column xxmiProfCompetenceID also in view object and there the value is also a number field.
Can someone help me, please.
Thanks
Robert

Hi Robert,
The error suggest that value "Oracle DBA" is getting assigned for the item xxmiProfCompetenceId, please check.
Regards,
Reetesh Sharma

Issue in Dependant LOV

Similar Messages

Maybe you are looking for