Making LOV off of an exposed method from second application module

Question

Hello,
I am on JDev 11.1.1.4.0.
My ADF project worked fine until the spec changed on how Lookups are going to be handled. Previuosly, all the lookup tables were in the same database as other tables. Change is that FND Lookups will be created in the "Oracle" and my ADF project should connect to "Oracle" to get appropriate lookup values to build LOVs while maintaining the main database connection intact.
After some research, I now have 2 Application Modules, one my project and the other for Lookups to create LOVs. I went to Application Module configuration wizard to edit JDBC setting to point to "Oracle" database and created a read only view with the following SQL:
SELECT LOOKUP_CODE, MEANING, DESCRIPTION FROM FND_LOOKUP_VALUES  
WHERE LOOKUP_TYPE = 'MY_LOOKUP'
AND ENABLED_FLAG = 'Y'
AND LANGUAGE = 'US'I can run both AMs via "Oracle Business Component Browser" fine. However, I somehow have to set the lookup view object as data source to create LOV on the main updatable view object's attribute. If I set it the way I used to do treating the lookup view as a view object residing in the same AM I am getting "table or view does not exist" error. I guess it is something to do with the lookup view object, but I cannot seem to make any kind of progress on this.
Any help would be greatly appreciated.
Thank you
Bones Jones
Edited by: Bones Jones on May 19, 2011 10:40 AM

Answer 1

Well, I think I have found a solution which I didn't have to write a single line of code. My mistake was to think that I have to write code to achieve this.
Here is what I did:
*I already have the main AM and View Objects created for my project.  The following steps are done on top of that to bring LOV to life
1. Create a new, pretty empty AM, named LovAM.
1.1 Right click on the newly created AM and select 'Configurations'
1.2 Click JDBC Name value and click 'Edit'
1.3 Select the second database source where Lookup is defined. If not listed, go back out and create a new Database connection and come back.
2. Create a View Object with the following SQL:
SELECT
    TO_NUMBER(LOOKUP_CODE) ID,
    MEANING NAME,
    DESCRIPTION
FROM
    FND_LOOKUP_VALUES
WHERE
    LOOKUP_TYPE = 'MY_LOOKUP' AND ENABLED_FLAG = 'Y' AND LANGUAGE = 'US'3. Notice you now have LovAMDataControl
4. Create a jspx page and create a table with the main data control's binding (This was a part of the requirements).
5. I create a read-only table with LovAMDataControl.LovLookUp1 binding (I think this creates/exposes correct binding in the pageDef).
6. Now I drag-and-drop an attribute that I have been wanting to display LOV from the main binding.
7. Selected single select listbox. You will be presented with 'Edit zlist Binding' screen.
8. Base Data Source is the main data control binding.
9. Select Dynamic List
10. Select LovAM data control binding as List Data Source.
11. (optional) Selected 'Name' as Display Attribute.
11.1. (optional) I don't want to see the table created in step 5. On the jspx page, go to Source tab and delete the table from there. I think this keeps binding in pageDef while the UI component is deleted from the page.
12. Save and Run
Now, I didn't have to create Root Application Module in the code, but still achieved what I wanted.
Thanks
Bones Jones