Search Results rollback_batch

Overview

The concurrent program ROLLBACK_BATCH is an Oracle E-Business Suite (EBS) executable that belongs to the PAY – Payroll product module. It presents to end users under the friendly name Rollback – Batch, reflecting its function as a batch program for roll back operations. Within the Payroll processing model, a rollback reverses a payroll run action—removing calculated results, reversing payments, or backing out a completed run—so that corrections can be applied and the process re-executed cleanly. The program is documented as enabled (Enabled: Yes) across the ETRM 12.2.2 metadata set and applies equally to the 12.1.1 and 12.2.2 release families.

The "Batch" designation indicates that the program is designed to process multiple payroll actions or assignments within a single submission rather than acting on a single record at a time. This is consistent with the broader Oracle Payroll approach to lifecycle management, where bulk rollback is required before a payroll run can be retried after validation failures, data corrections, or backpay adjustments.

Execution Details

The documented execution metadata for this program is as follows:

• User-facing name: Rollback – Batch
• Product / Module: PAY – Payroll
• Enabled: Yes
• Execution Method: PL/SQL Stored Procedure
• Argument Method: Standard
• Executable: ROLLBACK_BATCH
• Execution File: PAY_GB_MULTI_PAYROLL_RUN.RUN_ROLLBACK_ALL_UK

The execution file naming convention (PAY_GB_MULTI_PAYROLL_RUN with the subroutine RUN_ROLLBACK_ALL_UK) indicates a UK (GB) localization origin. The RUN_ROLLBACK_ALL_UK routine suggests that the program is designed to roll back all eligible payroll actions governed by a specified scope, rather than a single discrete action. Because the execution method is a PL/SQL stored procedure with a Standard argument method, the program accepts arguments through the standard concurrent program parameter framework rather than a token-based or custom interface.

How to Run

Users typically submit this program from the Submit Requests (SRS) window, or via the Oracle Payroll responsibility through the concurrent manager. Because the Argument Method is Standard, the program exposes one or more standard parameters—commonly a payroll identifier, consolidation set, payroll period, or effective date range—that define the scope of the rollback. Guidance for users includes:

• Ensure no active payroll processes are in conflict with the target scope before submission.
• Submit with a defined payroll and period to limit the rollback to the intended batch.
• Review the concurrent request log and output file to confirm which actions were reversed.
• Re-run the failed or corrected payroll process only after the rollback completes successfully.

Because the program is enabled and exposed under the Rollback – Batch name, it may be added to a request group and scheduled or submitted on demand.

Related Objects

Rollback activity in Oracle Payroll interacts with the core payroll run data structures and their associated diagnostic and reporting objects. Commonly associated objects include:

• The payroll run and assignment action result tables that store calculated run results (for example, PAY_RUN_RESULTS and related action/assignment records) that are reversed by the rollback.
• The companion single-record or alternate rollback executables used in the same product area (for example, rollback of an individual assignment).
• Payroll run concurrent programs, such as the payroll run and prepayments processes that are retried following a rollback.
• Payroll reports and reconciliation output that verify exclusions, reversals, and net pay impacts after rollback.

Because the ETRM metadata provides only the program definition and executable mapping, administrators should confirm parameter specifics and associated table names in the Oracle Payroll documentation for the exact patch level in use.