Workday-Pro-Absence Exam Questions & Answers

A period schedule establishes the recurring processing periods used by the time off plan and therefore determines its default accrual frequency. For example, a monthly period schedule normally causes Workday to process periodic accruals monthly, while a weekly schedule provides weekly processing periods. This behavior can be modified through an accrual frequency override, custom frequency, or front-loaded configuration, but the period schedule supplies the standard framework.

The schedule also defines period start and end dates used to retrieve and process time off, organize balance reporting, evaluate period-based eligibility criteria, and determine which effective dates are available for time off plan components. Every time off plan must therefore reference a valid period schedule.

Public holidays are defined through holiday calendars rather than period schedules. The maximum number of consecutive absence days is controlled by a Consecutive Day Maximum validation. The types of time off available to workers are determined through time off types, underlying time offs, eligibility, and security configuration. These functions do not belong to the period schedule. Among the available choices, determining the plan's default accrual frequency is the defining period-schedule characteristic.

The time off plan must specify a time off in the Time Off for Termination Adjustment field. This configuration tells Workday which time off component to use when generating the adjustment that removes the worker's entire remaining balance during termination processing.

When the Adjust Time Off Balances service step runs in the Termination business process, Workday evaluates the eligible plan, determines the remaining balance, and creates a termination adjustment using the designated time off. The adjustment reduces the plan balance to zero. Where payroll integration or Workday Payroll calculations are appropriately configured, that adjustment can support payment of the outstanding amount.

A payout accrual is not required because an accrual ordinarily adds units to a time off plan; it does not remove and pay the existing termination balance. Accrual Frequency Method controls whether ordinary accrual processing occurs at the start or end of a processing period and does not establish termination payout behavior. Time Off Forfeiture Adjustment is used when a balance is being forfeited under plan rules, not when the organization intends to pay the balance upon termination.

Study Guide reference: Absence Management Business Processes -- Automating Payout of Plan Balance upon Termination, particularly the time off plan's termination-adjustment configuration.

The Put Override Balance EIB performs mass time off plan balance overrides. It is appropriate because 200 acquired workers require the same type of beginning-balance conversion. Each worker's eligible plan balance can be established at 40 hours as of the applicable period start date, after which Workday uses that amount as the starting point for subsequent accrual and time off calculations.

Import Request Leave of Absence loads leave-of-absence events and does not establish time off plan balances. Adjust Time Off creates mass time off adjustment or correction transactions; it is not the delivered EIB for setting the authoritative opening balance. Enter Time Off loads time off requests through the Request Time Off business process and would reduce balances instead of establishing them.

The effective date must align with the start of a period for which each worker is eligible. Administrators must also understand that an override replaces the calculated balance at that point. Workday does not recalculate the overridden balance for the override date or earlier dates when retroactive activity is subsequently entered. Data validation should therefore confirm worker eligibility, plan, unit of time, effective date, and the 40-hour value before loading.

Study Guide reference: Absence Management Administration -- Maintain Time Off Plan Carryover and Balances for Employees.

Workday makes fields from the Worker, Leave Request Event, Leave Type, and Position business objects available when administrators create leave-of-absence rules. These objects supply the contextual data needed to evaluate eligibility requirements and validate submitted leave requests.

The Worker object supplies employee-level information such as hire date, service dates, and worker attributes. The Position object supports position-specific conditions, which are essential for position-based leave types or workers with multiple jobs. The Leave Request Event contains information generated by the particular request, including dates and event-specific data. The Leave Type object provides information about the leave configuration being requested.

There is an important eligibility restriction: eligibility rules must use fields based on Worker or Position because Workday evaluates eligibility before the leave type and leave event are fully known. Validation rules are evaluated later and can use request-event or leave-type information. Consequently, selecting a technically available field does not automatically make it suitable for every rule.

Time off plans, payroll results, period schedules, and balance periods are not the four business objects identified for constructing leave-of-absence rules.

Workday automatically recalculates the accrual adjustment when the effective date of the underlying job change is corrected. The adjustment is system-generated from the Change Job business process and is dependent on the job-change effective date, the worker's eligibility transition, the applicable accrual period, and the accrual's adjustment configuration. Correcting the source event causes Workday to reevaluate those inputs and update the dependent adjustment.

Manual deletion is neither required nor preferred because it would separate the adjustment from the business event responsible for creating it. The Time Off for Balance Transfer Adjustment field supports balance-transfer scenarios and does not govern recalculation of an accrual adjustment created because the worker lost eligibility. Carryover overrides apply to balances transferred between balance periods and are similarly unrelated to correcting the effective date of a job change.

This automated recalculation prevents an incorrect proration from remaining after the source event changes. For example, moving the job-change date later in the processing period may increase the portion of the period for which the worker was eligible. Workday recalculates the resulting adjustment using the corrected date.

Study Guide reference: Absence Management Administration -- Accrual Adjustment during a Job Change, including automated processing associated with Change Job events.