In Oracle Payroll Cloud, if costing setups (e.g., department costing information) are updated after a payroll run, the original costing results won't reflect the new setup. To apply these retroactive changes without rolling back the entire Calculate Payroll process, you should run the Calculate Retroactive Costing process (Option B). This process recalculates costing based on the updated setups and adjusts the results for affected employees, ensuring the department costing is reflected. Option A (rolling back costing only) is not a standalone option; rollback typically applies to the full payroll process. Option C (General Ledger adjustments) is a manual workaround, not the recommended system approach. Option D is incorrect, as retroactive costing is designed for this purpose. Oracle documentation highlights this process for retroactive cost updates.

Comprehensive and Detailed in Depth Explanation:
When a worker's check is returned due to damage, the correct action in Oracle Payroll Cloud is to update the payment status from "Paid" to "Void." This reflects that the payment was issued but is no longer valid, allowing for reissuance without affecting the payroll run. Deleting the payment result (B) is not a standard option and could disrupt reconciliation. "Cancelled" (C) is not a recognized status for this scenario, and rolling back the prepayment process (D) is unnecessary and impacts more than just the damaged check. This process is outlined in the "Managing Payments" section of the Oracle documentation.