Value Set Windows

The value sets you define using these windows appear in lists of values you see when you define flexfield segments using the Key Flexfield Segments window or the Descriptive Flexfield Segments window. If you are defining reports that your users run from the Submit Re uests window! use this window to define value sets for your report arguments. The value sets you define using this window also appear when you define report parameters using the "oncurrent #rograms window.

$ou can share value sets among segments in different flexfields! segments in different structures of the same flexfield! and even segments within the same flexfield structure. $ou can share value sets across %ey and descriptive flexfields. $ou can also share value sets with parameters for your concurrent programs that use the Standard Re uest Submission feature. &any 'racle (pplications reports use predefined value sets that you may also use with your flexfield segments. )owever! any changes you ma%e to a value set also affect all re uests and segments that use the same value set. This window prevents you from changing the validation type or format type of an existing value set because your changes affect other flexfields that use the same value set. In addition! other changes may affect the values in your value set in ways other than you expect. $ou cannot delete a value set that a flexfield or parameter currently uses. If you ma%e any changes to your value set after you have used your flexfield or concurrent program that uses this value set! you must either change responsibilities or exit to the operating system and log bac% in before you can see your changes ta%e effect.

1. List Type "hoose *ist of +alues if your value set should not provide the *ong*ist feature in 'racle Forms applications. ( user will not see a poplist in 'racle Self,Service applications. "hoose *ong *ist of +alues if your value set should provide the *ong*ist feature in 'racle Forms (pplications. The *ong*ist feature re uires a user to enter a partial segment value before the list of values retrieves all available values. $ou may not enable *ong*ist for a value set that has a validation type of -one. ( user will not see a poplist in 'racle Self,Service applications. "hoose #oplist if your value set should not provide the *ong*ist feature in 'racle Forms applications! but should provide a poplist in 'racle Self,Service applications. )ere are guidelines for the *ist Type field.

#oplist , fewer than /0 values expected *ist of +alues , between /0 and 100 values expected *ong *ist of +alues , more than 100 values expected

2. Security Type 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 -one! Special! or #air. -ote. Flexfield value security is not available for Translatable Independent and Translatable Dependent value sets. The possible security types are.

-o Security , (ll security is disabled for this value set. )ierarchical Security , )ierarchical security is enabled. 2ith hierarchical security! the features of value security and value hierarchies are combined. 2ith this feature any security rule that applies to a parent value also applies to its child values.2arning. 2ithin a hierarchical tree of values! a value is sub3ect to a security rule if any parent above it is sub3ect to that security rule. -on4)ierarchical 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 5cascade down5 to its child values.

3. Format Type 6nter the type of format you want to use for your segment values. +alid choices include. "har! Date! DateTime! -umber! Standard Date! Standard DateTime! and Time. -ote. Translatable Independent and Translatable Dependent value sets must have the "har format 4. Validation types

There are several validation types that affect the way users enter and use segment or parameter values. 7 -one 8not validated at all9 7 Independent 7 Dependent 7 Table 7 Special 8advanced9 7 #air 8advanced9 7 Translatable Independent 7 Translatable Dependent None $ou use a -one type value set when you want to allow users to enter any value so long as that value meets the value set formatting rules. That is! the value must not exceed the maximum length you define for your value set! and it must meet any format re uirements for that value set. For example! if the value set does not allow alphabetic characters! your user could not enter the value (:"! but could enter the value ;<= 8for a value set with maximum length of three9. The values of the segment using this value set are not otherwise validated! and they do not have descriptions. :ecause a -one value set is not validated! a segment that uses this value set does not provide a list of values for your users. ( segment that uses this value set 8that is! a non,validated segment9 cannot use flexfield value security rules to restrict the values a user can enter.

Independent (n Independent value set provides a predefined list of values for a segment. These values can have an associated description. For example! the value 0/ could have a description of 5"ompany 0/5. The meaning of a value in this value set does not depend on the value of any other segment. Independent values are stored in an 'racle (pplication 'b3ect *ibrary table. $ou define independent values using an 'racle (pplications window! Segment +alues.

Table ( table,validated value set provides a predefined list of values li%e an independent set! but its values are stored in an application table. $ou define which table you want to use! along with a 2)6R6 cause to limit the values you want to use for your set. Typically! you use a table, validated set when you have a table whose values are already maintained in an application table

8for example! a table of vendor names maintained by a Define +endors form9. Table validation also provides some advanced features such as allowing a segment to depend upon multiple prior segments in the same structure. ependent ( dependent value set is similar to an independent value set! except that the available values in the list and the meaning of a given value depend on which independent value was selected in a prior segment of the flexfield structure. $ou can thin% of a dependent value set as a collection of little value sets! with one little set for each independent value in the corresponding independent value set. $ou must define your independent value set before you define the dependent value set that depends on it. $ou define dependent values in the Segment +alues windows! and your values are stored in an 'racle (pplication 'b3ect *ibrary table Special and !air Value Sets Special and pair value sets provide a mechanism to allow a 5flexfield,within,a,flexfield5. These value sets are primarily used for Standard Re uest Submission parameters. $ou do not generally use these value sets for normal flexfield segments. Special and #air value sets use special validation routines you define. For example! you can define validation routines to provide another flexfield as a value set for a single segment or to provide a range flexfield as a value set for a pair of segments. Translatable Independent and Translatable ependent ( Translatable Independent value set is similar to Independent value set in that it provides a predefined list of values for a segment. )owever! a translated value can be used. ( Translatable Dependent value set is similar to Dependent value set in that the available values in the list and the meaning of a given value depend on which independent value was selected in a prior segment of the flexfield structure. )owever! a translated value can be used.