Poplists are used for two distinct purposes in Oracle Applications: to hold data in a small list of possible values, and to set the displayed region for a set of alternative regions (for backwards compatibility only).
For information about the look and feel of poplists, see the Oracle Applications User Interface Standards for Forms-Based Products.
Poplists holding data use the LIST property class. Poplists that serve as control elements for alternative regions use the LIST_REGION_CONTROL property class (for backwards compatibility only).
Coding Alternative Region Behavior
The maximum width of a list element is 30 characters. Your longest value in English for a 30-character-wide poplist should be no longer than 23 characters to account for expansion of values for some languages.
You may need to populate a list at runtime. If so, be aware of the following issues:
Never use a list item if you expect more than fifteen elements
Do not change a list on a per-record basis
Make sure each populated list has a value that matches the default value. You can dynamically change the default by specifying it as a reference to another field, as opposed to a hardcoded value.
Always set a poplist based on its value, not its label. The value never gets translated, but the label may. When you set the Default Value property, Oracle Forms will actually accept the label value (for example, Good), but you should always use the hidden value (for example, G) instead.