LOV Considerations Print this Page
Description and Purpose

This guideline describes how you should use Oracle Fusion Applications LOV choice lists, LOV text fields, and select-one choice lists.

Types of Lists
Return to Top

Choice lists and lists of values (LOVs) enable users to choose a value from a set or list of values. Application Development Framework (ADF) supports several kinds of lists:

Select-One Choice List

Here is an example of a select-one choice list. This type of list is the standard web widget single-select choice list:

Figure 1. Example of a select-one choice list
LOV Text Field

Here is an example of an LOV text field. Users either type an exact match, type a partial string and activate the search, or leave the field blank and activate the search:

Figure 2. Example of an LOV text field
LOV Choice List

Here is an example of an LOV choice list. Users select from what is currently displayed or select Search to find more values:

Figure 3. Example of an LOV choice list
Comparison of Features

This table compares the features and functions of the lists that are important to the user experience.

Feature Select-One Choice LOV Text
LOV Choice

Set Size

Small to medium (up to 100 values)

Medium to very large

Medium to very large


Fewest http requests and SQL statements

Lighter than the LOV Choice. This does not trigger a blind query.

Most http requests and SQL statements. This always triggers a blind query.


This functionality is not supported. The widget displays the entire list.

This functionality is supported using the icon.

This functionality is supported using the Search link at the bottom of the pane.

Type Ahead


ADF autosuggest

ADF autoSuggest

Type Ahead Performance

Fastest (all values are already loaded)

One round trip to the middle tier and one SQL fires to calculate the suggestions.

One round trip to the middle tier and one SQL fires to calculate the suggestions


Use the multiselect widget.

No. Use a multiselect search results table.

No. Use a multiselect search results table.

Most Recently Used (MRU)

Not supported

Not supported


Smart List

Not supported

Not supported


Multiple Columns

Not supported

Supported. The panel sizes to fit columns.

Supported. The panel sizes to fit columns.

Oracle Fusion Guidance for LOV Choice Lists
Return to Top

Follow these guidelines for different data set sizes:

Small Data Sets

For small data sets use the select one-choice list. Small data sets load quickly in the browser, and the browser type ahead feature is fast. Using about 100 items is the recommended maximum. By using well written SQL, the select one-choice list can perform excellently with up to 300 items. You can simulate a smart list in a select one-choice list by adding some additional code at the view object (VO) level, as has been done for the currency LOV.

Figure 4. Select-one choice list used with a small data set
Medium to Very Large Data Sets

For medium to very large data sets (large tables or multiple joins) use the LOV text field. Enable autoSuggest if you have appropriate performance guarantees. The LOV text field is lighter than the LOV choice list, which always triggers a blind query first. Some possible tables include Person, Party, Supplier, and Customer.
Figure 5. LOV text field for medium to very large data sets
All Others:

Use the LOV choice list. Enable autoSuggest if you have appropriate PSR guarantees. Use the Most Recently Used (MRU) or Smart List features or both if indicated by your use case. An LOV choice list with these features enabled works in the following way:

  • If users click the arrow, the panel drops down to show the MRU, Smart List, or the full list of search options.
  • If users enter data in the field, AutoSuggest opens and the panel displays the results.
  • Note that content from the two panels is never combined.
    Users' action determine which panel is displayed.
  • You can display the full list if you have fewer than about 100 values. Note that you cannot use the full list in combination with the Smart List, but you can use the full list with the MRU.
  • Use of full list only.
    • If you have a short list of values, but you need to display more than one column to enable users to correctly identify the value.
      In this case, you can show the full list without the MRU. Make sure that you enable Auto-Suggest.
    • If users do not reuse a small subset or you are not able to derive a Smart List from the context, you can use the full list only.
      Make sure that you enable Auto Suggest.
LOV Features
Return to Top

The following are descriptions of various features for the LOV Choice List.

Figure 6. Example of elements and their placement within the LOV Choice List.


The MRU has these characteristics:

  • The MRU shows a list of the last five values selected by this user during the current session, in order of most to least recent.
  • The MRU is most useful when users use a small set of values repeatedly during a session.
  • The list is blank when users first use it, so use either the Smart List or a full list as well as the MRU.
    Alternatively, use preseeded values in the MRU if the Smart List or full list are not appropriate.

The Smart List

The Smart List has these characteristics:

  • The Smart List displays a list of values that are most relevant to the context users are in.
  • Application teams add their own logic to create this list.
    It is not user generated.
  • The Smart List cannot be combined with a full list.

Auto Suggest

Auto Suggest has these characteristics:

  • Auto Suggest displays values that match what users are typing in real time.
  • Auto Suggest should be enabled on all LOV choice lists and LOV text lists where performance is reliably good.
  • Auto Suggest requires teams to build VOs that are optimized for the LOV.
  • Auto Suggest improves usability enormously when properly implemented.
    Users expect Auto Suggest based on their internet experience. They do not have to take their hands off the letter keys to activate a list.
Performance and Scalability
Return to Top

Performance and scalability are two key considerations for LOVs. An LOV is frequently the most important element in a task flow in terms of establishing context and loading related data. For example, in a Create Purchase Order transaction, selecting the supplier causes many fields of data to be defaulted and may also set the context for what items users can select for the purchase order.

To make sure that LOVs in Oracle Fusion work as well as possible, follow these guidelines:

  • Select the correct type of list. See the previous Oracle Fusion Guidance section in this guideline.
  • Strive to create a uncomplicated VO:
    • Avoid joins.
    • Avoid generic views.
    • Do not join large tables in a way that requires filtering on a large numbers of rows.
    • Minimize selected columns.
    • Make sure the ORDER BY agrees with the index.
Related Documentation
Return to Top
About Oracle | Legal Notices | Terms of Use | Your Privacy Rights