To define a value set:

1. Navigate to the Value Sets window.

2. Enter a unique name for this value set. See: Value Set Naming Conventions.

3. If you are modifying an existing value set, you can, with the proper privileges, view where the value set is used. See: Value Set Usages.

4. Specify the List Type for your value set.

   Choose List of Values if your value set should not provide the LongList feature in Oracle Forms applications. A user will not see a poplist in Oracle Self-Service applications.

   Choose Long List of Values if your value set should provide the LongList feature in Oracle Forms Applications. The LongList feature requires a user to enter a partial segment value before the list of values retrieves all available values. You may not enable LongList for a value set that has a validation type of None. A user will not see a poplist in Oracle Self-Service applications.

   Choose Poplist if your value set should not provide the LongList feature in Oracle Forms applications, but should provide a poplist in Oracle Self-Service applications.

   Here are guidelines for the List Type field:

   • Poplist - fewer than 10 values expected

   • List of Values - between 10 and 200 values expected

   • Long List of Values - more than 200 values expected

5. Specify the Security Type you plan to use with any segments that use this value set. Security does not apply to value sets of validation type None, Special, or Pair. See: Defining Security Rules.

   Note: Flexfield value security is not available for Translatable Independent and Translatable Dependent value sets.

   The possible security types are:

   • No Security - All security is disabled for this value set.

   • Hierarchical Security - Hierarchical security is enabled. With hierarchical security, the features of value security and value hierarchies are combined. With this feature any security rule that applies to a parent value also applies to its child values.

     Warning: Within a hierarchical tree of values, a value is subject to a security rule if any parent above it is subject to that security rule.

   • Non-Hierarchical Security - Security is enabled, but the rules of hierarchical security do not apply. That is, a security rule that applies to a parent value does not "cascade down" to its child values.

6. Enter the type of format you want to use for your segment values. Valid choices include: Char, Date, DateTime, Number, Standard Date, Standard DateTime, and Time.

   Note: Translatable Independent and Translatable Dependent value sets must have the Char format.

7. Enter formatting information appropriate to your format type, including information such as whether your values should include numbers only and whether they must fall within a certain range.

   Note: The maximum size for Translatable Independent and Translatable Dependent value set values is 150. You cannot use the Numbers Only feature or the Right-Justify and Zero-fill feature with translatable value sets.

8. Select your validation type: Independent, Dependent, Table, None (non-validated), Special, Pair, Translatable Independent, or Translatable Dependent. See: Choosing a Validation Type for Your Value Set.

9. If you are creating a Dependent, Translatable Dependent, Table, Special or Pair value set, choose the Edit Information button to open the appropriate window. Enter any further information required for your validation type. See: Dependent Value Set Information Window, Validation Table Information Window, Special Validation Routines Window.

10. Save your changes.