Comprehensive and Detailed in Depth Explanation:
To transfer absence information from HCM Cloud Absence Management to Cloud Global Payroll, two key steps in Payroll are required: (1) "Create your absence elements" (D) to define the payroll elements linked to absence types, and (2) "Create element eligibility for each absence element" (B) to specify which employees qualify for these elements. Option A (Absence Calculation Card) is not a payroll component, and Option C (manual entry) is unnecessary as the integration automates data transfer via input values. This is detailed in the "Absence Integration with Payroll" section.

Comprehensive and Detailed in Depth Explanation:
In Oracle Payroll Cloud, when a task on a checklist is "On Hold," the available actions are "Skip" (bypass the task), "Retry" (attempt reprocessing), and "Submit" (move forward with the flow). This status typically indicates a pause awaiting manual intervention or correction, and these actions allow flexibility in resolving it. Options A and B include "Resubmit" or "Rollback," which apply to broader flow actions, not a single "On Hold" task, and Option D ("Mark for Retry") is a preparatory step, not a direct action. This is covered in the "Payroll Checklist Management" section.

In Oracle Payroll Cloud, a tax reporting unit (TRU) is created as part of the payroll statutory unit (PSU) setup. When a legal entity is identified as a PSU, the application automatically transfers its associated legal reporting units (LRUs) to HCM as TRUs (Option A). This ensures tax reporting aligns with the legislative requirements of the PSU. Option B is incorrect, as there's no optional step to designate the PSU as a TRU-it's automatic. Option C (directly identifying a legal entity as a TRU) bypasses the PSU linkage, which is not supported. Option D (legal employer) is inaccurate, as TRUs are tied to PSUs, not legal employers. Oracle documentation confirms this automatic transfer process.

Comprehensive and Detailed in Depth Explanation:
When a payroll run results in errors for a subset of workers (e.g., five out of 10,000), the most efficient action in Oracle Payroll Cloud is to "Mark errored workers for retry" and then retry the payroll process for those specific workers. This action targets only the errored records, reprocesses them after corrections, and integrates the results with the successful runs, avoiding a full rollback. Rolling back the entire payroll (A) is unnecessary and disruptive to the 10,000 successful records. Manually updating statuses (B) is not a supported or recommended practice, and "Process Payroll" (D) is too vague and not a specific action for this scenario. This is detailed in the "Correcting Payroll Errors" section.