Adding a  value to an LOV in an Oracle apps form

Hi Guys
Im new to forms and customizations in apps as im sure will be apparent with the questions i have :-)I have a requirement to add a value to an LOV on a field in an oracle apps form.
My question is
1: How do i get the lov query?
2: How do i edit an existing query.
3: How can i solve this problem.
Thanks

Since you are working with the E-Business Suite, most likely the LOV is based on a Value Set. I strongly recommend you confer with a coworker for guidance on how to investigate an Oracle EBS Form. Value Sets are defined within the EBS setup screens and you have to be assigned to a responsibility that will allow you to modify and create Value Sets. I also strongly recommend you visit the Oracle Applications Documentation web site and review the Oracle Applications Developer's Guide and Oracle Applications User Interface Standards for Forms-Based Products for your particular version of the EBS.
Also, the General EBS Discussion is the more appropriate forum to post this type of question.
Hope this helps.
Craig...

Similar Messages

  • Need to restrict KFF values on Charge Account Screen in Oracle Apps 11i

    Hi,
    I have a requirement to restrict KFF values based on certain criteria in the charge account screen in Oracle Apps 11i..
    Could you pls advise on how this can be achieved.
    Thanks,
    Shashank
    Edited by: Shashank Senan on May 23, 2012 2:53 PM

    Can you please mark my answers correct......if they were helpful to you.....
    That would be so nice of you....:-)
    and regarding your next requirement, You should create a new table which will contain Date, Worker Number and any other details that you want.
    In the form, for every date for which you want to enter the data, you will select the max(date) before the current date and maximum worker number for that selected date and then from that number you can select next 15/20 workers or whatever your number is.
    e.g. for the first time if you want to enter data for 01-jul-2010 and you have work for 15 workers, you will select max(date) where date<01-jul-2010, but you will not find any bcoz this is your first entry. So wat you will do is will start popupating your grid from number 1-15.
    Next day you will select max(date) where date<02-jul-2010, you will find 01-jul-2010. Then you will select max(number) for 01-jul-2010, you will find 15. So populate your grid from number 16-30 (whatever your number is). and so on.
    Hope it helps you...
    Please mark my answer Helpful or correct and Please create a new thread for new question
    Thanks
    Nishu

  • Dynamically change LOV in oracle apps forms

    Hi,
    I have one requirement the Item LOV need to change based on the condition. If the condition is X then it use the X record group and attach to the LOV (This record groups is I have already created at design time). I can able to attache the record group to the LOV based on condition but if I click the LOV it not pop up in a window it is simply not working (no error).
    If I enter some text in the Item and press Tab then the LOV window is pop up.
    Can you please post your suggestion or solutions for this issue.
    I am giving my sample code the below code I am using to attache the record group to the LOV.
    Item level KEY-LISTVAL Trigger
         Set_ITEM_Property('XXRULES.P_RULE_VALUE',LOV_NAME,'ZIP_CODE');
         Set_ITEM_Property('XXRULES.P_RULE_VALUE',LOV_VALIDATION,PROPERTY_TRUE);
         Set_LOV_Property('ZIP_CODE',GROUP_NAME,'ZIP_CODE');

    Set_ITEM_Property('XXRULES.P_RULE_VALUE',LOV_NAME,'ZIP_CODE');Set_ITEM_Property('XXRULES.P_RULE_VALUE',LOV_VALIDATION,PROPERTY_TRUE);
    Set_LOV_Property('ZIP_CODE',GROUP_NAME,'ZIP_CODE'); Is this all of your code? If so, you are missing the call to Show_LOV(). Remember, Show_LOV() returns a boolean so you have to catch the return value.
    DECLARE
       b_selected  BOOLEAN := FALSE;
    BEGIN
       Set_ITEM_Property('XXRULES.P_RULE_VALUE',LOV_NAME,'ZIP_CODE');
       Set_ITEM_Property('XXRULES.P_RULE_VALUE',LOV_VALIDATION,PROPERTY_TRUE);
       Set_LOV_Property('ZIP_CODE',GROUP_NAME,'ZIP_CODE');
       b_selected := Show_LOV('ZIP_CODE');
    END;Hope this helps,
    Craig B-)
    If someone's response is helpful or correct, please mark it accordingly.

  • How to find LOV Query in Oracle Web Form

    Hi All,
    I am currently use oracle ebs R12.1.2 and i just want to know the query which is attached in lov for Oracle web pages kindly help.
    Regards

    Hi,
    There is a bug in OAF for this one, upon clicking on About this page on the newly opened LOV page it still shows the Parent Page Details.
    Workaround:
    1. After the LOV window opens, click on about this page [This will still show the parent page properties]
    2. Now click on backspace. [You should be back to the same LOV Page]
    3. Now click on About this page, again, - This should show you the correct details.
    Hope that helps!!!
    Regards,
    Yuvaraj

  • Right side of a shuttle -  Retunr id and not the display value of the LOV.

    Hi all,
    The matter is how to populate/persist right-side of Shuttle in apex 4.0.1 after submit. The only problem I have is that the values
    on the right side of the shuttle are dispayed as (retun value of the LOV) and not as (dislay valueo of the LOV). What I'm missing.
    There is a way to pre-load dynamically, so depending on a query, a set of values on the right of the Shuttle, and then allow end user to change the preselection adding or removing values.?.

    On page load you need to set the page item value to a colon separated list. Basically just reverse what ever processing you are doing on submit.

  • How to add a new value in seeded LOV in I Procurement page

    Hey Guys,
    I am stuck with one problem.
    In the I procurement module , when we make requisitions , we have option to change the requestor name. When i open the form , we can search the requestor only by name. There is a LOV for search criteria which has got only one value - Name.
    I want to add Employee id also as a search option which means adding a value in the seeded LOV. Please help !
    Regards,
    Amit

    Hi,
    user13079404 wrote:
    I want to add Employee id also as a search option which means adding a value in the seeded LOV. Please help !
    ---U want search by employeid also in lov search region
    ---In lov region u need to enable seacrh option for employee id also.
    ---searcby:True
    ---let men know u have the value of emplyeeid in lov RN.
    Regards
    Meher Irk

  • New Blog Post: Saving Current Values with Cascading LOVs

    All,
    Just blogged on Saving Current Values with Cascading LOVs: http://bit.ly/hQPUPi
    Enjoy!
    Regards,
    Dan

    Monty,
    Glad to hear it's working for you.
    Oh, you just had to go there ;) Popup LOVs are a bit more difficult because the values are not automatically brought back to the page for you. I've already worked out how this could be implemented in my head - but writing it up, of course, is more of an effort. I've added it to my list of blog articles to write on. Since it's not a requirement right now, I'll cover another topic first and come back to that one afterward.
    Regards,
    Dan
    Blog: http://DanielMcGhan.us/
    Work: http://SkillBuilders.com/apex/

  • Two values from a LOV to Timecard LDT

    Hi,
    I have a requirement to pull two values from single LOV to Timecard layout page.
    e.g.: Suppose we have a LOV field 'emp_number' on layout and this field is getting value from one LOV. Query in LOV shows emp_number and emp_last_name. I want to put one more field on layout page by the name Last_Name and whenever a emp_number value is selected in LOV, corresponding emp_last_name value should be coming to Last_Name field of layout page. Can somebody please help me on how to do this?
    I have tried to add one similar HXC_LAYOUT_COMPONENTS as of Emp_number LOV field to ldt file with component = 'Text_Field' but it is not working for me :(

    Follow this note 307151.1, this note describes how to populate a Task Name in a different field when Task number is selected in LOV, you have a similar requirement, so you can configure the attributes as described in that note.
    - Ramu

  • [UIX] How To: Return multiple values from a LOV

    Hi gang
    I've been receiving a number of queries via email on how to return multiple items from a LOV using UIX thanks to earlier posts of mine on OTN. I'm unfortunately aware my previous posts on this are not that clear thanks to the nature of the forums Q&A type approach. So I thought I'd write one clear post, and then direct any queries to it from now on to save me time.
    Following is my solution to this problem. Please note it's just one method of many in skinning a cat. It's my understanding via chatting to Oracle employees that LOVs are to be changed in a future release of JDeveloper to be more like Oracle Forms LOVs, so my skinning skills may be rather bloody & crude very soon (already?).
    I'll base my example on the hr schema supplied with the standard RDBMS install.
    Say we have an UIX input-form screen to modify an employees record. The employees record has a department_id field and a fk to the departments table. Our requirement is to build a LOV for the department_id field such that we can link the employees record to any department_id in the database. In turn we want the department_name shown on the employees input form, so this must be returned via the LOV too.
    To meet this requirement follow these steps:
    1) In your ADF BC model project, create 2 EOs for employees and departments.
    2) Also in your model, create 2 VOs for the same EOs.
    3) Open your employees VO and create a new attribute DepartmentName. Check “selected in query”. In expressions type “(SELECT dept.department_name FROM departments dept WHERE dept.department_id = employees.department_id)”. Check Updateable “always”.
    4) Create a new empty UIX page in your ViewController project called editEmployees.uix.
    5) From the data control palette, drag and drop EmployeesView1 as an input-form. Notice that the new field DepartmentName is also included in the input-form.
    6) As the DepartmentName will be populated either from querying existing employees records, or via the LOV, disable the field as the user should not have the ability to edit it.
    7) Select the DepartmentId field and delete it. In the UI Model window delete the DepartmentId binding.
    8) From the data controls palette, drag and drop the DepartmentId field as a messageLovInput onto your page. Note in your application navigator a new UIX page lovWindow0.uix (or similar) has been created for you.
    9) While the lovWindow0.uix is still in italics (before you save it), rename the file to departmentsLov.uix.
    10) Back in your editEmployees.uix page, your messageLovInput source will look like the following:
    <messageLovInput
        model="${bindings.DepartmentId}"
        id="${bindings.DepartmentId.path}"
        destination="lovWindow0.uix"/>Change it to be:
    <messageLovInput
        model="${bindings.DepartmentId}"
        id="DepartmentId"
        destination="departmentsLov.uix"
        partialRenderMode="multiple"
        partialTargets="_uixState DepartmentName"/>11) Also change your DepartmentName source to look like the following:
    <messageTextInput
        id=”DepartmentName”
        model="${bindings.DepartmentName}"
        columns="10"
        disabled="true"/>12) Open your departmentsLov.uix page.
    13) In the data control palette, drag and drop the DepartmentId field of the DepartmentView1 as a LovTable into the Results area on your page.
    14) Notice in the UI Model window that the 3 binding controls have been created for you, an iterator, a range and a binding for DepartmentId.
    15) Right click on the DepartmentsLovUIModel node in the UI Model window, then create binding, display, and finally attribute. The attribute binding editor will pop up. In the select-an-iterator drop down select the DepartmentsView1Iterator. Now select DepartmentName in the attribute list and then the ok button.
    16) Note in the UI Model you now have a new binding called DCDefaultControl. Select this, and in the property palette change the Id to DepartmentName.
    17) View the LOV page’s source, and change the lovUpdate event as follows:
    <event name="lovSelect">
        <compound>
            <set value="${bindings.DepartmentId.inputValue}" target="${sessionScope}" property="MyAppDepartmentId" />
            <set value="${bindings.DepartmentName.inputValue}" target="${sessionScope}" property="MyAppDepartmentName" />
        </compound>
    </event>18) Return to editEmployees.uix source, and modify the lovUpdate event to look as follows:
    <event name="lovUpdate">
        <compound>
            <set value="${sessionScope.MyAppDepartmentId}" target="${bindings.DepartmentId}" property="inputValue"/>
            <set value="${sessionScope.MyAppDepartmentName}" target="${bindings.DepartmentName}" property="inputValue"/>     
        </compound>
    </event>That’s it. Now when you select a value in your LOV, it will return 2 (multiple!) values.
    A couple things to note:
    1) In the messageLovInput id field we don’t use the “.path” notation. This is mechanism for returning 1 value from the LOV and is useless for us.
    2) Again in the messageLovInput we supply “_uixState” as an entry in the partialTargets.
    3) We are relying on partial-page-refresh functionality to update multiple items on the screen.
    I’m not going to take the time out to explain these 3 points, but it’s worthwhile you learning more about them, especially the last 2, as a separate exercise.
    One other useful thing to do is, in your messageLovInput, include as a last entry in the partialTargets list “MessageBox”. In turn locate the messageBox control on your page (if any), and supply an id=”MessageBox”. This will allow the LOV to place any errors raised in the MessageBox and show them to the user.
    I hope this works for you :)
    Cheers,
    CM.

    Thanks Chris,
    It took me some time to find the information I needed, how to use return multiple values from a LOV popup window, then I found your post and all problems were solved. Its working perfectly, well, almost perfectly.
    Im always fighting with ADF-UIX, it never does the thing that I expect it to do, I guess its because I have a hard time letting go of the total control you have as a developer and let the framework take care of a few things.
    Anyway, I'm using your example to fill 5 fields at once, one of the fields being a messageChoice (a list with countries) with a LOV to a lookup table (id , country).
    I return the countryId from the popup LOV window, that works great, but it doesn't set the correct value in my messageChoice . I think its because its using the CountryId for the listbox index.
    So how can I select the correct value inside my messageChoice? Come to think of it, I dont realy think its LOV related...
    Can someone help me out out here?
    Kind regards
    Ido

  • No data found due to cost element adding leading values in report

    Hi Experts,
    I have an issue where when the run the analyser with some values in variable screen it is displaying the output correctly in analyser tool. I am filtering the cost element with a single value for ex 4545000 and I have kept that in rows . Still the report is working fine.  But then when I go back to variable screen and change the input for ex instead of period 3 if I change it to 4 , output is null since the cost element is adding leading values to the existing value in the filter and displaying no result.  for ex 4545000 is getting added with controlling area 0050 and its searching for 00500004545000 and since this is not the cost element value its not displaying output..
    Any ideas how to rectify this or is it a analyser tool issue..
    Thanks in advance
    Kishore

    Hi,
    In my system it looks like this:
    Note that superior infoobject to 0costcenter is 0co_area
    Hope this helps,
    Leszek

  • How to set the default value of a LOV that is found in a view criteria

    HI,
    I need to set the default value of an LOV that is found in a view criteria. I tried to set a groovy expression but unfortunately it wasn't read. i also tried to bind the LOV to a bind variable and set the value of the bind variable in the constructor of my backing bean but unfortunately the default value appeared the second time i entered the screen and not on page load.
    Can anyone advise where can i set the default value,
    Thanks

    if you want some default value in LOV. you go to edit list of value wizard-> UI hint->include no selection Item checkbox -checked.use labeled item first of list- and beside that put the label. but when you try to get value, it will show null.but you can manipulate in ur java , if it default value

  • AJVOAF : How to set a value in one LOV which is coming from another LOV

    Dear Friends,
    I have a issue regarding LOVs. Actually I have 3 LOVs ( Material ,Subinventory ,Locator) in my maintainence user page.
    First Requirement is I have to add subinventory and locator fields to the Material LOV itself (for user no need to go upto Subinventory & Locator LOVs) and WHICH record of Material ,user iis selecting corresponding Subinventory and Locator values should come in Subinventory & Locator boxes ( Second Requirement is i have to make these two Subinventory & Locator LOVs as READ ONLY)
    Third Requirement is I have to bring these Subinventory and Locator values from Material LOV page to Subinventory & Locator boxes.
    I hope iam clear.
    First and Second Requirement s done.
    Iam struggiling for third req.Can any one plz help.
    Thanks
    Aravinda

    hi,
    In your Subinventory LOV add Bin variable using it Query tab. which has Bind VAriable And View Criteria section.use Bind Variable section. those are in the view object level.
    then your all lov include view object select and choose it View Accessors section. it has your lov and Edit your Subinventory LOV and then popup dialog box. Inside it you can make Inside Parametor section select relevant bind variable name and it need value.
    thaks.

  • Maintaining operating concern after adding new value field

    Hello,
    I added a new value field to our live operating concern,maintained the data structure throguh KEA0(Maintain operating concern).The changes are transported from Development to Quality,Changes were reflected in Q system.After testing in Q system transports were pushed to production system.The new value field is added to the operating concern. When i check the log for KEA0 in production system it displayed one message like:
    Field VV088 was added to the reference structure
    Message no. KE782.You probably either  changed the operating concern or SAP-EIS aspect, and added the field VV099 to the definition.
    The added a CO-PA value field:
    In this case, the field is added to the definition or the summarization levels. This invalidates all existing levels. Consequently, you need to activate them again and fill them with data.
    In production system maintaining operating concenr or KEAO is only in display mode.Is it needed to regenerate the operating concern once again in production, how to do it. Is the message talking about the KEDV summarization levels.?
    thanks
    rahul

    Hi,
    No no ....KEDV is nothing to do here....that is creation of summarization in CO-PA.
    Since you added new value field you necessarily have to Regenerate the operating concern...
    Use Tcode KEA0...go to Environment tab...there the status of Cross client part  and client specific part both will be in RED....now just click on the Cross client (candle button)...now the system would regenerate the operating concern...once it is over do the same for the client specific...
    Beware when you do regenerate the operating concern no body can enter any transaction in that server since it is cross client table ...hence better do it after business hours.
    Hope this helps!
    Running KEDU with rebuild is relevant only when you already have created summarization and called up the same in the CO-PA report "options" tab. If you did not created the summarization you are nothing to do with KEDU.
    Next: The new value field has to be transported to PRD and hence even in PRD we have to do the regeneration manually.
    Regards,
    Velumani
    Message was edited by: Velumani Arunachalam
    Message was edited by: Velumani Arunachalam

  • Impact of adding new value fields in ongoing operating concern.

    Hi All,
    Want to know the steps of adding new value fields in the existing operating concern in COPA?
    What is the overall impact of addition of New Value fields in the running Operating Concern?
    How do we test the addition of new value fields?
    Is the addition of New Value fields to the running Operating Concern advisable?
    Your support and advice is highly anticipated and appreciated.
    Thanks & Regards
    9819528669

    HI,
    please search in SCN forum before you post:
    Re: Adding a ValueField to an existing Operating Concern?
    Best regards, Christian

  • Limitation of the number of values in an LOV

    Greetings,
    I have a tabular form with few of the columns as LOVs. One of the LOVs returns close to 1000 records and the form is giving me a "PL/SQL Numeric Value error". If I do a rownum < 450 in the LOV query the form works. But I need all the values in the LOV.
    Any ideas ow to fix this issue. Your help will be greatly appreciated.
    Thanks
    Vatsa

    sr**** wrote:
    I have a tabular form with few of the columns as LOVs. One of the LOVs returns close to 1000 records and the form is giving me a "PL/SQL Numeric Value error". If I do a rownum < 450 in the LOV query the form works. But I need all the values in the LOV.
    Any ideas ow to fix this issue. Your help will be greatly appreciated.The total size of the HTML generated for an LOV-based item in APEX is restricted to 32K&mdash;something that can be discovered by a basic search of the forum.
    You have not provided enough information to enable anyone to "fix this issue" directly. ALWAYS provide the following information in a question:
    <li>Full APEX version
    <li>Full DB version and edition
    <li>Web server architecture (EPG, OHS or APEX listener)
    <li>Browser(s)/version(s) used
    <li>Theme
    <li>Template(s)
    <li>Region type(s)
    When discussing a tabular form, always indicate whether it was created using a wizard with generated column items, validations and MRU processing, or created manually using <tt>apex_item</tt> API items and custom validations and processing (or some other combination of these possibilities).
    LOVs can be used in rendering a number of APEX items: text look-ups, select lists, radio groups and pop-ups. You have not specified which item type(s) are involved. All of these item types except pop-ups are subject to the 32K restriction.
    For text look-ups rendered as Display as Text (based on LOV, does not save state), change the display type to Display as Text (escape special characters, does not save state) and do the the look-up in the query using a join or scalar subquery.
    As pointed out above, even if it was possible to render a select list or radio group with 1000 options in APEX, this is way too many for an effective UI. There's also the effect on the overall size of a page: if the tabular form displays 10 rows, and each select list contains 32K of options, how big is the page? How long does it take to download? The maximum number of options I'd use in a select list is the ~200 used in lists of countries. (For select lists used in tabular forms I'd prefer to limit it to about 6!) The workaround for select lists/radio groups is to change them to Popup Key LOVs.

Maybe you are looking for