The standard payslip availability date is set at the payroll definition level. To override this for a specific subset of employees, the correct method is to group them using a payroll object group (specifically, a Payroll Relationship Group). When submitting the "Generate Payslips" process, you can select this specific object group and enter an earlier date in the "Payslip Availability Date" parameter. This action overrides the default date for only the employees included in that group for that specific run, meeting the requirement without affecting other workers.

A. This is incorrect because Oracle Payroll provides a mechanism to override the payslip availability date for a subset of workers through process parameters.

B. Payroll time definitions are used to define payroll periods and dates for the entire payroll, not to override settings for specific employee subsets.

D. Document of Records (DOR) is a repository for various employee documents; it is not used to control the availability date of payroll-generated payslips.

1. Oracle Cloud HCM

Implementing Payroll for the United States

Release 24B

Document ID F97217-02.

Chapter: Payroll Setup > Payroll Definitions. This chapter explains that the default "Payslip Availability Date" is set on the payroll definition

applying to all employees on that payroll.

Chapter: Payroll Flows > Generate Payslips for the US. This section details the parameters for the "Generate Payslips" process

which include "Payroll Relationship Group" and "Payslip Availability Date

" confirming that an override is possible for a specified group.

2. Oracle Cloud HCM

Using Payroll

Release 24B

Document ID F97221-02.

Chapter: Payroll Processing > Object Groups. This chapter describes the use of object groups

including Payroll Relationship Groups

to "limit the persons you process for a payroll run

or for a report." This supports the creation of a group for the impacted workers.

Chapter: Payroll Processing > How Payroll Process Parameters Work. This section explains that parameters entered during process submission

such as an override date

take precedence over default settings for that specific run.