What is a good practice to handle LOV in jdev apps?

Question

Hi, experts,
In jdev 11.1.2.3,
In our projects, there are many LOVs which the value are stored in a common dictionary table, for example in table refcode:
refcode(id, low_value,high_value,meaning,domain_no),
Different LOVs will retrieve value pairs(low_value,meaning) , or (high_value,meaning) from refcode table by using domain_no as the filtering criteria.
In the end user's UI, the code/number field values should be displayed by a meaning word from refcode,
To accomplish this goal, I will create numberous associations between different tables with refcode,
and create VOs to have refcode entity view as a secondary entity view.
I feel some odd in doing so(because so many associations with the same refcode table),
Is that a good practice to handle LOV this way ?
Thanks.

Answer 1

On Fusion Developer's Guide for Oracle Application Development Framework
10.3 Defining a Base View Object for Use with Lookup Tables
(http://docs.oracle.com/cd/E37975_01/web.111240/e16182/bclookups.htm#BABIBHIJ)
10.3.3 How to Define the WHERE Clause of the Lookup View Object Using View Criteria
There are valuable information and suggestions on implement lookup features, especially by using view criteria
(the View Criteria and View accessor is one of important and great idea in ADF)
I think, by using of view criteria, the derivative attribute to display fk information can be implemented in a convinent way without FK associations definition.