The customer wants payroll validations to fire as soon as the worker leaves the Time Entry page and clicks Next (which opens the Review page).

In a Time Consumer Set the only action that invokes validation at that point is “Next”.

Secondly, the transfer must include every payroll time-type entry, which the delivered time category “All Payroll Entries” already contains.

Option A combines exactly these two requirements—time category “All Payroll Entries” and “Validate on Time Card Actions” = Next—so it is the sole configuration that satisfies both parts of the scenario.

B – Adds absences; requirement is limited to payroll time types only, so transfer scope is too broad.

C – Validation fires only at Submit, not when the user clicks Next.

D – Validation fires on Save and Submit, but still not on Next, so Review-page requirement is unmet.

E – Fails both conditions: fires on Submit/Save, not Next, and also adds absences.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 23C, “Manage Time Consumer Sets”, Section ‘Validate on Time Card Actions’, pp. 211-212 — lists action ‘Next’ and its usage for review-page validation.

2. Same guide, Table ‘Delivered Time Categories’, p. 196 — defines “All Payroll Entries” as containing every payroll time-type entry (excludes absences).

3. Oracle Fusion Global Payroll Interface Implementation Guide 23C, “Transferring Time to Payroll”, p. 37 — confirms that “All Payroll Entries” is the recommended category when only payroll time is transferred.