Your customer has implemented Fusion Payroll and defined a set of elements and CIRs (Calculation Information Repository) with restricted element…

Oracle Time and Labor can filter the list of Payroll Time Type values that workers see only when every element to be offered is included in a single multiple-attribute time-card field that belongs to the worker’s layout set. When that layout set is connected to the worker through the Time Entry Profile, the application evaluates each element’s eligibility rules (defined in Payroll’s Calculation Information Repository) at run time and hides any time-type value whose element isn’t eligible for the person’s assignment. Splitting the elements across several fields or relying on the Enabled flag does not invoke element-eligibility processing, and the product never auto-populates the filter by itself.

B. The Enabled flag only determines if a field itself is shown, not which element rows inside the field appear; eligibility is therefore not enforced.

C. Element eligibility isn’t consulted automatically; it is evaluated only when elements are grouped as described and tied to the profile.

D. If elements are spread over several multiple-attribute fields, the eligibility engine can’t run across them, so ineligible time types still display.

1. Oracle Fusion Cloud Time and Labor 24A – Implementing Time and Labor Guide, section “Multiple-Attribute Time Card Fields: Restrict Payroll Elements”, pp. 146–147.

2. Oracle Fusion Cloud Global Payroll 24A – Implementing Payroll, chapter “Element Eligibility”, pp. 105–107 (explains how eligibility rules are invoked by consuming applications).

3. Oracle Fusion Cloud Time and Labor 24A – chapter “Configure Time Entry Profiles”, p. 212 (linking layout sets to workers through the Time Entry Profile).