Validation by LOV

One of the edit boxes in my page takes the value from a LOV. After the user selects the value from the LOV, it automatically validates it and if the value selected forms the combination already existing for the primary key, it automatically gives a Oracle.jbo.TooManyObjectsException.
I have provided the check of the primary key violation in my Save button handler, but this exception is thrown just when the user selects a value from the LOV.
kindly let me know how to stop this from happening.
Regards

Hi,
LOV fires some events we select new value from LOV and at tht time you can handle your Primary Key validation.
I will update the thread with LOV events so that you can proceed.
The error is coming because whenever page gets submitted it posts data from VO to EO, and LOV submits the page partially and I think because of that it is throwing error.
Regards,
Reetesh Sharma

Similar Messages

Validation of LOVs in Timecard while update/while trying to view details

Dear gurus of OTL,
I have followed this forum a lot while implementing OTL for a project and gained lots of interesting things.I have come across another interesting scenario .I have 3 LOVs in my timecard which are based on 3 xml queries.I fill out a timecard with 3 values in these lovs,i submit it and get it approved.After few days for audit purpose we check the approved timecards by clicking on the details of a timecard.Amazingly the 3 values i have entered once again get validated against the 3 xml queries and if it doesn't meet the criteria i see null there.How reasonable is this validation?
Another observation is when we enter a timecard and save it and defer submission to a later time seeing more changes.we then try to update them and it does it again the previoulsy entered lines in the timesheet get validated against the xml queries which is a Performance issue in this case.Let me know your insights on this.
Thanks & Regards,
Sameer.T

It might be something to do with the way the field is defined in the LDT file which defines the timecard layout.
On a data entry timecard, the LOV is based on a ViewObject which in turn is a view which retireves the data from its source (a value set or some other table(s) on the database). The VO usualy returns two columns, the display value and the id of the record. The user selects the value from the display list, and then OTL stores the id of the record on the datbase.
When the system retrieves the data to display, for example in your details page, it must read the id of the stored record and convert it back to the display value. Perhaps the VO associated to this process is not accounting for end dated projects?
Regards
Tim

Key exists validation and LOV

Hi, I'm using JDev 11.1.1.2
I have a key-exists validation on 2 attributes (to prevent user from entering two records with the same pair of those attributes)
One of the attributes is rendered as <af:inputListOfValues>
This component behaves odd ... I enter the first field , then I enter the LOV field so that the pair matches another record and it gets cleared without no warning message.
If I enter first the LOV , and then the other inputText field I got validation Error (which is what I expect).
But on LOV components it returns the previous value in the LOV without displaying any error/warning message.
I think that this is a bug, and if so ... is there another good solution for such validation.
A. Gruev

Hi John
The table has already unique index. And if I remove the validation from entity, I got the error from the database which is not a good scenario... even if I intercept the error and display a nice translated one ... there is the problem when adding several rows and when I press commit It will give the error but the user will not know for which row exactly ... for me the entity validation works OK (it wont let you change the current row or do any other action unless you fix the error) , only the LOV components make the problem.

Validation of LOV

I'm trying to validate three values that are as type LOV in a form. I need to check for STATE, and COMPANY_ID. Since they're LOV, I don't have any way of checking if they are null from the portal submit side. I decided to create a javascript from the onClick of Insert. However, it's still doing the insert even thought I put false. I then realize that my script is not been validated as a "onSubmit()" rather it's just checking if the value is not null, but it is still submits the form.
I even tried to "hacked" the submit command using the form.onSubmit() but this didn't work either.
I'm putting the javascript in the "Additional PL/SQL" and in the "Formating and Validation" option in the "insert top" I clicked on the "onClick" and I put the following script:
isItemValueNull(this.form, 'STATE', 'State');
The javascript that I put on the "addtional pl/sql" is the following:
htp.p('<script language="JavaScript1.3">
function isItemValueNull(form, target, fieldName){
alert("isItemValueNull");
var objname;
var validateForm = true;
//Loop through all elements in the form
for(var j = 0; j < form.length; j++)
objname = form.elements[j].name.split(".");
//Compare the third section of the name with the target
if (objname[2] == target){
//Check if item is null or empty
//isNull(form.elements[j].value, target);
if (form.elements[j].value == null || form.elements[j].value == ""){
alert( fieldName + " cannot be null");
form.elements[j].focus();
form.elements[j].select();
validateForm = false;
if(!validateForm){ alert("validate is false");}
form.onSubmit = "return validateForm";
</script>');
Please help,
Marcelo

Additional information:
================
The order of LOV's is not relevant!
The problem also occures if ANY input field in the form is in error state (I mean at least one field raises a validation error).
regards
Peter

Not validating against LOV if the field is not null

hi all,
i am using form6i.
i have two fields called p_code,p_doc.
p_code is optional and p_doc is mandatory. Both the fields is having LOV. Based on the p_code, p_doc should be filtered.
both fileds i have given validate_from_list true.
if user entered some values and processed after that without clearing the fields(p_doc) if user enters the data p_code the values in the LOV for p_doc is filtering(refreshing) but the value is not validate against the LOV.
that means
p_code p_doc
aa 123
bb 456
first time for the code 'aa' the p_doc value was 123. now again user entered bb so that in the lov p_doc 456 is present but in the item still 123 is there. If user press the ENTER or TAB the cursor is going to next field with out valudating the value in the p_doc(old value is 123 but it should replace by 456) but is not showing any error also.
if my requirement is not clear.please let me know.
Thanks..

Because the value in P_DOC is not getting validate. How about trying the below code in WHEN-VALIDATE-ITEM trigger of P_CODE
:P_DOC:=:P_DOC;-Ammad

Validation for Lov's

Hi,
I have 5 messageLovInput items on my page. I want to ensure that the user first enters value in the first Lov item(as in user queries the first Lov item) before proceeding to the remaning Lov's.
How do I check whether the user has first entered data in the first Lov item?
Please help me in solving this problem.

Why don't you use the "Dependent Text Field LOV" as mentioned in the Dev Guide. I guess that will be able to handle your scenario. If that doesn't suit you, you can put your own logic to maintain the state of 1st LOV through a variable and handle/ disable the other LOVs accordingly.
--Shiv

VALIDATION USING LOV

HI
i have created a text field and aside it is an LOV.say ti_emp_id is my text field and emp_lov is LOV.
now i have set the property of text item as validate from LOVi.e. list=YES.So now if i enter a wrong emp id the lov gets displayed and if i press cancel i.e. doestnt choose any emp_id than i get an error displyiing 'INVALID VALUE FOR FIELD TI_EMP_ID'.
i dont want this error message to display ,wat i want is that if i dont select any value from LOV than the field shd be cleard.
plzz help me out ASAP.

Check required property for your item. It should be 'NO'

Trigger events are notvalidated the lov form personalization or custom.pll

Hi all,
The trigger events are not validated the LOV in forms personalization or custom.pll
any one help me
Regards,
M.Soundrapandian
Edited by: user588510 on Dec 15, 2008 9:27 PM

i have checked with the new item instance and now i have given
In the message text when i have given this query it is displaying me with blank message box when there are no records which i dont want.and also saving it when i click ok .where should i modify my query so it displays message only when there are more than 3 records but should not save
trigger event : when new item instance
trigger object :repairs.lot_number
condition : :SR.ACCOUNT_NUMBER IS NOT NULL
AND :REPAIRS.SERIAL_NUMBER IS NOT NULL
Message text :
=SELECT 'There are a total of '||COUNT (*)||' Previously Repaired Records' "A" FROM CSD_REPAIRS CR, CS_INCIDENTS_ALL_B CS, CSD_PRODUCT_TRANSACTIONS CP
WHERE (
SELECT COUNT(*)
FROM CSD_REPAIRS CR, CS_INCIDENTS_ALL_B CS, CSD_PRODUCT_TRANSACTIONS CP
WHERE CR.REPAIR_LINE_ID = CP.REPAIR_LINE_ID
AND CR.INCIDENT_ID = CS.INCIDENT_ID
AND CS.ACCOUNT_ID = :SR.ACCOUNT_NUMBER
AND CP.prod_txn_status = 'RECEIVED'
AND CR.STATUS = 'Closed'
AND CP.SOURCE_SERIAL_NUMBER = :REPAIRS.SERIAL_NUMBER)>=3
Edited by: user10755387 on Aug 5, 2009 11:31 PM

Problem in LOV event

we are doing some customization to perform validations on LOV event.
First we are calling the SuperForm request , then we are checking for the LOV event and calling one package for the validations.
In first instance it works fine like: we opn the LOV and then select any value, it works fineas expected.
The problem comes : when we are tring to again open the LOV by clicking on the LOV icon , the LOV region window is not opening.
It is taking the previous value and calling the package again.
Please suggest any solution for the same.

I am performing the validation for 2 LOV`s Supplier and SupplierSite.
SupplierSite LOV is dependent on supplier.
//Call processFormRequest method of base class
super.processFormRequest(pageContext, webBean);
//declaring the lov object
String strLovItemName1 = pageContext.getLovInputSourceId();
//check for LOV click event
if (strLovItemName1 != null && !strLovItemName1.equals("")) {
//checking the Supplier Site LOV for any event
if (strLovItemName1.equals("Supplier")) {
//call the base class
super.processFormRequest(pageContext, webBean);
System.out.println("Supplier lov clicked ");
// check if supplier id and org id is not null
if (strSuppId != null && !("").equals(strSuppId) &&
intOrgId != null && !intOrgId.equals("")) {
//supplier site id is not null then convert it into integer
///****callin the package*****//////
// call for the supplier site iD LOV
else if (strLovItemName1.equals("SupplierSite")) {
if (strSuppSiteId != null && !("").equals(strSuppSiteId) &&
suppWebBean != null && !("").equals(suppWebBean) &&
intOrgId != null && !intOrgId.equals("")) {
/////**** calling the package***/////
Please guide me .

OTL Timcard Configuration - lov effective dates

I have configured the Payroll layouts for custom choice lists, e.g. cost centre, project code etc. The view has been created to reference a value set with the start date active and end date active on the flex values checked against sysdate. However, this causes prior weeks timecards to not display an end dated value as it is no longer effective at sysdate. Is there any way to validate the values against timecard date (e.g. timecard start/end date) so a prior week timecard will display the original value as it was still active as at the timecard date.
Thanks
Allan

Thanks for the response.
I have used the custom view to create the choice list and for time entry and review etc it is fine. But the lov is restricted to effective values from the value set as at sysdate. So if we review a timecard from the past the value may not be effective as at sysdate any longer so displays null in the review page. Timekeeper uses the timecard date for the valid list of values so is there a customisation that can cause self sevice to do the same. Effectively, its as though instead of validating the lov by sysdate the list is validated by a variable 'timecard date'. How can this be achieved?

How to set default value for drop down box in jsf

Hi,
Can anyone help me to set the default value in drop down box using <af:selectManyChoice> ?
As I know there is an unselectedLabel attribute in <af:selectOneChoice> but not valid attribute for <af:selectManyChoice>.
Any help must be appreciated.
Regards,
AK

Hi Frank
My entity type is a List in managed bean. I have set the entityType in the constructor of the managed bean. I have attached my code here.
TPSearchCriteriaBean.java****************************************
/** Constructor */
public TPSearchCriteriaBean() {
super();
entityType=new ArrayList<String>();
entityType.add(UIConstants.LIST_ITEM_ALL);
authorizationType=new ArrayList<String>();
authorizationType.add(UIConstants.LIST_ITEM_ALL);
companyType=new ArrayList<String>();
companyType.add(UIConstants.LIST_ITEM_ALL);
mrgStatus=new ArrayList<String>();
mrgStatus.add(UIConstants.LIST_ITEM_ALL);
legalStatus=new ArrayList<String>();
setEntityType(entityType);
setAuthorizationType(authorizationType);
setCompanyType(companyType);
setMrgStatus(mrgStatus);
country = "0";
//address = new AddressBean();
UIConstants.java***********************************************************
public static final String LIST_ITEM_DEFAULT = "select";
public static final String LIST_ITEM_ALL = "0";
LOVManager.java*****************************************************************
public List<SelectItem> getLovList(String lovType, boolean requiredOption_SELECT, boolean requiredOption_ALL)
log.debug("LOV loading for " + lovType + ": START");
List<SelectItem> lovList = new ArrayList<SelectItem>();
//check validity of lov loading request
validLov:
for (int i = 0; i < lovTypeArray.length; i++)
if (lovTypeArray.equals(lovType))
break validLov;
log.debug("ERROR: LOV Type not valid.");
return lovList;
//First select is replaced by ALL here
//<-- Select --> should be an option
if (requiredOption_SELECT)
lovList.add(new SelectItem(UIConstants.LIST_ITEM_DEFAULT, "--Select--"));
LOVDao dao = new LOVDao();
dao.loadLOVValues(lovType, lovList);
log.debug("LOV Loading successful!");
//<ALL> should be an option
if (requiredOption_ALL)
lovList.add(new SelectItem( UIConstants.LIST_ITEM_ALL, "ALL"));
return lovList;
Kindly help me.
Regards,
AK

How to include a DFF in search

My requirement is,
I have a DFF. I want to make the DFF fields searchable in OA framework. How can i achieve it?. Please advice by steps. Thanks

In OA developer guide, for DFF they have mentioned as follows
+++
Descriptive Flexfield in a Search Region Currently if a Search region includes a descriptive flexfield that has a segment of type LOV, any search criteria that you specify in that flexfield LOV will be auto-validated. LOVs, however, should not be validated in a search criteria region. To turn validation off, use the following API in OADescriptiveFlexBean:
public void setUnvalidated(boolean unvalidated);
If the unvalidated value for this method is true, OA Framework will disable LOV validation and disable server-side validation for the descriptive flexfield. See Flexfield Validation for more details.
+++
Does it mean, DFF can be implemented in Search Region. If Yes, how?. Any idea.
Regards,
Soorya

Oracle AP: No invoice is selected in Payment

Hi,
I have input an invoice with payment method = CHECK and already made it validated and accounted.
When, I tried to make a Payment, after enter the Supplier and click the button "Enter/Adjust Invoice". I can't have any valid invoice (LOV) in Select Invoices form.
How come it happens?
Is there any procedures I have missing?
B. Rgds,
Sunny Yip

Sunny,
What is the application release?
Please see if (Note: 947862.1 - Invoice Number is Not in the List of Values LOV in the Payment Workbench) is applicable.
Thanks,
Hussein

Reg bind variable error in OTL extension.

We have done extension to OTL standard screen where we customised three LOVVO's.These are working fine in most scenario's but soemtimes for specific test cases the query TaskLOV query seems to fail.
Error seen when we try to select the time card/click details of time card:
SELECT * FROM (SELECT DISTINCT task.task_number tasknumber, task.task_name taskname,
task.task_id taskid,task.billable_flag BillableFlag,task.project_id ,
task.start_date StartDate, task.completion_date CompletionDate,
task.scheduled_start_date ScheduledStartDate,task.scheduled_finish_date ScheduledFinishDate,
task.chargeable_flag,
NULL project_number, task.workplan -- count(1)
FROM pac_online_task_v task
WHERE TRUNC(TASK.COMPLETION_DATE) >= TRUNC(FND_DATE.CANONICAL_TO_DATE(:1))
AND TRUNC(TASK.START_DATE) <= TRUNC(FND_DATE.CANONICAL_TO_DATE(:2))
and TRUNC(fnd_date.canonical_to_date (:3)) between to_date('01-mar-1900') and to_date('01-mar-4020')
and nvl(task.chargeable_flag,'N')='Y') QRSLT WHERE (TaskId = :1) ORDER BY TaskNumber
"Not All variables Bound."
Th LDT file for bind pramas is as follows.
BEGIN HXC_LAYOUT_COMP_QUALIFIERS "Projects Timecard Layout - Task"
OWNER = "ORACLE"
QUALIFIER_ATTRIBUTE_CATEGORY = "LOV"
QUALIFIER_ATTRIBUTE1 = "XXTaskLOVVO"
QUALIFIER_ATTRIBUTE2 = "N"
QUALIFIER_ATTRIBUTE3 = "XXHXC_CUI_TASK_LOV"
QUALIFIER_ATTRIBUTE4 = "809"
QUALIFIER_ATTRIBUTE5 = "12"
QUALIFIER_ATTRIBUTE6 =
"Xxtaskname|TASK-DISPLAY|CRITERIA|N|Xxtaskprojid|PROJECT|PASSIVE_CRITERIA|Y|Xxtaskid|TASK|RESULT|N|Xxtaskname|TASK-DISPLAY|RESULT|N"
QUALIFIER_ATTRIBUTE8 = "TaskName"
QUALIFIER_ATTRIBUTE9 = "TaskId#NUMBER"
QUALIFIER_ATTRIBUTE10 = "custom.XXTaskLOVVO"
QUALIFIER_ATTRIBUTE11= "TIMECARD_BIND_START_DATE|TIMECARD_BIND_END_DATE|TIMECARD_BIND_END_DATE"
QUALIFIER_ATTRIBUTE14 =
"Xxtaskprojid|PROJECT|Y#Xxtaskprojnum|PROJECT-DISPLAY|Y"
QUALIFIER_ATTRIBUTE15 =
"project_id = ::Xxtaskprojid#upper(project_number) = upper(::Xxtaskprojnum)"
QUALIFIER_ATTRIBUTE17 = "OraTableCellText"
QUALIFIER_ATTRIBUTE20 = "N"
QUALIFIER_ATTRIBUTE21 = "Y"
QUALIFIER_ATTRIBUTE22 = "L"
QUALIFIER_ATTRIBUTE25 = "FLEX"
QUALIFIER_ATTRIBUTE26 = "PROJECTS"
QUALIFIER_ATTRIBUTE27 = "Attribute2"
QUALIFIER_ATTRIBUTE28 = "TASK"
LAST_UPDATE_DATE = "2004/05/24"
END HXC_LAYOUT_COMP_QUALIFIERS
I try to auto populate some values in screen and this error occurs....even without clicking on the lov. I am not sure how the task_id is getting appended at run time when we have different passive criteria's here.Am not aware if some internal validation of LOV's is getting fired when some values are autopopulated in the lov field of base page..Let me know if any bind params are incorrect in the ldt file.
Inputs on this would be really helpful.
Thanks,
Swarna

WHERE TRUNC(TASK.COMPLETION_DATE) >= TRUNC(FND_DATE.CANONICAL_TO_DATE(:1))
AND TRUNC(TASK.START_DATE) <= TRUNC(FND_DATE.CANONICAL_TO_DATE(:2))
and TRUNC(fnd_date.canonical_to_date (:3)) between to_date('01-mar-1900') and to_date('01-mar-4020')
and nvl(task.chargeable_flag,'N')='Y') QRSLT WHERE (TaskId = :1) ORDER BY TaskNumberBind parameter mis match is there.
:1 is used in TRUNC(FND_DATE.CANONICAL_TO_DATE(:1)
and QRSLT WHERE (TaskId = :1)
-Anand

ODI Integration with Siebel

We are from Siebel Marketing team and are evaluating if we can use ODI to move the data from staging tables to Siebel Base tables including Party tables like Contacts/Prospects/Accounts etc.
In order to do that, we need answers of the following basic questions.
1) How does ODI take care of Validations like LOV etc at the table level?
2) Are user key validations configurable?
3) Are Parent Child validations possible like one address (child) mandatory for a contact (parent) to exist?
4) Can an external web Service be called to do the dedup matching? Will that perform? We want to use this essentially for Dedupe logic when moving the data into Party tables.
5) In that case how do we specify the matching guideline like Reject/Update/Insert the record if a match is found?
6) Is there any Siebel team which integrates with ODI currently?
Any inputs would be really helpful.
Varun

Hi User;
For your issue i suggest close your thread here as changing thread status to answered and move it to Forum Home » System Management and Integration » Data Integrator which you can get more quick response
Regard
Helios

Validation by LOV

Similar Messages

Maybe you are looking for