Cascading Value Sets for Element Input Values in Oracle Fusion Payroll

If you are configuring Element Input Values in Oracle Fusion Payroll and need a parent-child relationship like Bank to Branch, you might reach for an Independent or Dependent value set. However, assigning either of these will throw an error: "You must enter a valid value set. The current value set is <YOUR_VS_NAME>. (XLA-870689)."

Here is why this happens:

• Oracle Fusion Global Payroll has a hard restriction that only Table-based value sets are supported for Element Input Values.

• Independent, Dependent, and Format Only value sets are strictly not supported.

• Even without this restriction, the Input Values UI does not have a mechanism to pass a "parent segment" context.

The Solution: Table Value Sets and Context Parameters

You can still build a cascading experience using Table-type value sets by adding a context parameter to the WHERE clause. Oracle exposes a specific token for this purpose: :{PARAMETER.<InputValueName>}.

• The <InputValueName> must be the exact Name of the parent Input Value on the element.

• It cannot be the value set's code.

• It cannot be the display label.

Step-by-Step Guide: Building a Bank to Branch Setup

Step 1: Create the Banks Value Set (Parent)

Create your parent value set named ATL_BANKS_TBL_VS using the following configuration.

Field	Value
Validation Type	Table
Value Data Type	Character
FROM Clause	ce_index_banks cba
Value Column Name	bank_name
WHERE Clause	cba.BANK_INSTITUTION_TYPE = 'BANK'
ORDER BY Clause	bank_name

Step 2: Create the Bank Branches Value Set (Child)

Next, create the child value set named ATL_BANK_BRANCHES_TBL_VS to reference the parent parameter.

Field	Value
Validation Type	Table
Value Data Type	Character
FROM Clause	ce_index_banks cba, ce_index_bank_branches cbb
Value Column Name	cbb.branch_name
WHERE Clause	cba.bank_party_id = cbb.bank_party_id AND cba.BANK_INSTITUTION_TYPE = 'BANK' AND cba.bank_name = :{PARAMETER.BANK_IP}
ORDER BY Clause	cbb.branch_name

Step 3: Configure the Element

1. Create an Input Value named BANK_IP.

2. Set the UOM to Character and assign the Value Set to ATL_BANKS_TBL_VS.

3. Create a second Input Value named BRANCH_IP.

4. Set the UOM to Character and assign the Value Set to ATL_BANK_BRANCHES_TBL_VS.

5. Sequence the Bank input above the Branch input on the Input Values page.

6. Save and submit your configuration.

Selecting a bank on Element Entries will now automatically scope the Branch list of values (LOV) to that specific bank's branches.

Avoid This Common Mistake

The parameter token only works if its name exactly matches an actual Input Value's Name field.

• Wrong Setup: AND cba.bank_name = :{PARAMETER.ATL_BANKS_TBL_VS}. This incorrectly references the value set name.

• Right Setup: AND cba.bank_name = :{PARAMETER.<InputValueName>}. This correctly references the parent Input Value's Name.

• If you reference the wrong name, the parameter silently resolves to NULL.

• There is no error message; the LOV simply comes back empty, which can look like a data issue rather than a naming mismatch.