Independent and dependent value sets have a special relationship. While you can have the same dependent values for any of your independent values, the meanings (or descriptions) - as well as any segment qualifier values, enabled/activation information and descriptive flexfield data for that value - of the dependent values depend on which of the independent values you choose in the prior independent segment. For example, you could have value sets with the values (dependent default value of 0) as described in the following table:
| Independent Value Set (Account Segment) Value | Independent Value Set (Account Segment) Description | Dependent Value Set (Sub-Account Segment) Value | Dependent Value Set (Sub-Account Segment) Description |
|---|---|---|---|
| 01 | Cash accounts | 0 | Default Value |
| 01 | Cash accounts | 1 | Bank of California |
| 01 | Cash accounts | 2 | Bank of Denver |
| 01 | Cash accounts | 3 | First Federal Bank |
| 02 | Equipment accounts | 0 | Misc equipment |
| 02 | Equipment accounts | 1 | Computers |
| 02 | Equipment accounts | 2 | Printers |
| 02 | Equipment accounts | 3 | Delivery Vehicles |
| 03 | Other asset accounts | 0 | Default value |
You must set up your independent-dependent value sets carefully using the following sequence:
Create your independent value set first
Create your dependent value set, specifying a default value
Define your independent values
Define your dependent values
When you define each of your independent values, Oracle E-Business Suite automatically creates a default dependent value that goes with your independent value. For example, the previous diagram shows a default value of zero (0). If for some reason you create a dependent value set after your independent value set has values, you must manually create a default value in your dependent set for each of your independent values, since each independent value must have a default dependent value. If necessary, create your default dependent values manually using the Segment Values form (you also use this form to create all dependent values other than the default value). You must create at least one dependent value for each independent value, or else your user will be unable to enter segment value combinations in the flexfield. However, we recommend that you carefully follow the above order for creating your value sets so that you never have to create default dependent values manually, since manually creating default dependent values is both tedious and error-prone.
Attention: For independent-dependent value sets, the size of a value entered for the independent value set must not exceed 60 characters. Failure to adhere to this limit may result in unexpected behavior.
Flexfields uses a special mechanism to support table-validated segments whose values depend on the value in a prior segment (a different mechanism from that used for independent value sets with dependent value sets). You can use flexfield validation tables with a special WHERE clause (and the $FLEX$ argument) to create value sets where your segments depend on prior segments. You can make your segments depend on more than one segment (cascading dependencies). However, you cannot use parent value/child value features with these value sets, nor can you use this mechanism with the Accounting Flexfield.