How User Variables and Contract Expert Rules Uses Value Sets
You can use value sets to determine what entries contract authors can make in user variables and in Contract Expert feature questions.
You can use them either to specify the format an entry must take, or to create a list of values contract authors must choose from.
Value sets are a common application component which you can set up by navigating to the Setup and Maintenance work area and searching for the Manage Contract Terms Value Sets task. This topic highlights value sets nonprogrammers can set up for Oracle Fusion Enterprise Contracts.
This topic covers:
-
Using value sets for creating user variables
-
Restrictions for values sets used in Contract Expert feature rules
Using Value Sets for User Variables
You use value sets in the setup of user variables for one of the two following purposes:
-
To set up the list of values the contract author must choose from to enter the value
-
To specify only the length and format of the information the author must enter manually
Suppose, for example, that you need to create a user variable contract authors can use to enter the name of one of your warehouses into a clause during contract authoring. Without any knowledge of programming, you can:
-
Create the list of values the contract author will use to select one of the warehouses.
You create the values first and then enter them into an independent value set.
-
Create a format only value set that restricts the entry to a specified number of characters.
Other value set features are also available for use by nonprogrammers. If you want to restrict the entry of the available warehouses by country, then you can make the above value set dependent on a second value set of countries, for instance.
Restrictions for Using Value Sets in Contract Expert Rules
If you are using the value set for a variable that will be used in Contract Expert rules or to specify the values used in responses to a question used in such a rule, then you only use a subset of the value set features as described in the following table.
Value Set Format Type |
Value Set Validation Type |
Supported? |
---|---|---|
Char |
Independent |
Yes Valid operators are: Is, Is Not, In, and Not In |
Char |
Table |
No |
Char |
Translatable Independent |
Yes Valid operators are: Is, Is Not, In, and Not In |
Char |
None |
No |
Char |
Pair |
No |
Char |
Special |
No |
Char |
Dependent |
No |
Number |
None |
Yes Numeric operators. |
Standard Date / Standard Date Time |
Not Applicable |
No |
Date / Date Time |
Not Applicable |
No |