Search Results rollback_ass_action

Overview

PY_ROLLBACK_PKG is an Oracle Payroll utility package owned by the APPS schema. Its principal business function is to reverse, or "roll back," payroll processing actions and assignment-level actions after they have already been committed, restoring the affected data structures to a pre-processing state. This capability is essential in Oracle EBS Payroll because a payroll run, QuickPay, prepayment, or balance adjustment can propagate changes across a large number of dependent tables — assignment actions, action contexts, action information, balances, batch lines, and General Ledger interface records. When a run must be undone due to incorrect inputs, funding errors, or reconciliation failures, this package provides the programmatic mechanism to unwind those effects in a controlled manner. The package is classified as OTHER in the ETRM metadata, meaning it is an internal utility rather than a public business API, and it is registered as VALID in both the 12.1.1 and 12.2.2 releases. It relies on the SYS.STANDARD package and is referenced by twenty-three other Payroll packages, indicating that it occupies a foundational position within the Oracle Payroll processing stack.

Key Procedures and Functions

The ETRM documentation identifies three callable units within the package body:

• INS_ROLLBACK_MESSAGE — Inserts a rollback-related message, typically into the application messaging or log infrastructure, so that the outcome of a rollback attempt is recorded for diagnostics and user notification. It supports the traceability requirements that surround destructive payroll operations.
• ROLLBACK_PAYROLL_ACTION — The primary routine for reversing a payroll action. It removes or restores the records generated when a payroll action executed, including action contexts, action information, interlocks, assignment actions, and associated balance feeds, returning the payroll action to an unprocessed state.
• ROLLBACK_ASS_ACTION — Performs the equivalent reversal at the assignment-action level, allowing a single assignment's payroll action to be unwound independently of the wider payroll action set. This granularity is important when only a subset of assignments produced erroneous results.

No parameter lists are documented in the ETRM metadata, so signatures should be confirmed against the deployed package specification before direct invocation.

Tables Accessed

Through APPS synonyms, the package touches a broad set of Payroll and General Ledger tables. Action-level tables — PAY_ACTION_CLASSIFICATIONS, PAY_ACTION_CONTEXTS, PAY_ACTION_INFORMATION, and PAY_ACTION_INTERLOCKS — are read to resolve the action being reversed and updated to clear processing state. PAY_ASSIGNMENT_ACTIONS, PAY_ASSIGNMENT_LATEST_BALANCES, PAY_BALANCE_CONTEXT_VALUES, and PAY_BALANCE_FEEDS_F are manipulated to remove or back out assignment results and balance contributions. PAY_ALL_PAYROLLS_F, PAY_BATCH_LINES, and PAY_CHUNK_STATUS support payroll-level and batch-level rollback context, while GL_INTERFACE and GL_JE_SOURCES are engaged where the reversal must also undo corresponding General Ledger interface entries. The archive tables FF_ARCHIVE_ITEMS and FF_ARCHIVE_ITEM_CONTEXTS supply the stored definition data needed to identify archived elements referenced during reversal.

Usage Notes

PY_ROLLBACK_PKG is not a user-facing API. It is invoked indirectly by higher-level Payroll processes such as HR_DELETE, PAY_BALANCE_ADJUSTMENT_API, PAY_BALANCE_UPLOAD, PAY_BATCH_BALANCE_ADJ_PKG, PAY_QPA_API, PAY_QPQ_API, PAY_QPU_API, PAY_MAGTAPE_EXTRACT, and various country-specific packages including the Japan and Korea payroll extensions. These callers use it to unwind work during delete processing, balance adjustment reversals, and archive or extract corrections. Custom code should not call ROLLBACK_PAYROLL_ACTION or ROLLBACK_ASS_ACTION directly without careful analysis, because the package assumes a consistent processing context established by the calling concurrent program or API. Where rollback is required, the supported route is to invoke the parent concurrent program or API that internally orchestrates PY_ROLLBACK_PKG, thereby preserving action interlocks, audit records, and balance integrity.