Search Results action_parameter




Overview

PAY_MIX_ROLLBACK_PKG is an Oracle EBS Payroll (PAY) schema-level PL/SQL package owned by the APPS schema. Its central purpose is to reverse or "roll back" payroll run results for a defined group of assignments — commonly referred to as a "mix" — so that processing can be corrected, re-executed, or purged. In payroll operations, a run may be started, partially completed, or produce incorrect results for a set of assignments. Without a controlled rollback mechanism, the resulting element entries, run results, and batch records would corrupt subsequent payroll processing and costing. This package provides the programmatic interface that allows a payroll administrator or a concurrent process to undo such results cleanly, while logging messages and maintaining the integrity of related payroll tables.

Within the APPS schema, the package is classified as an OTHER API rather than a public or private interface, indicating it is an internal utility used primarily by Oracle Payroll's own processes rather than a documented integration point for third-party callers. Its dependency graph confirms this: it references only SYS.STANDARD at the database level and is referenced by the PAY_ROLLBACK_PKG package, which suggests PAY_MIX_ROLLBACK_PKG is a lower-level component invoked by higher-level rollback orchestration logic.

Key Procedures and Functions

The ETRM documentation lists eight procedures and functions, each serving a distinct role in the rollback lifecycle:

  • UNDO_MIX — The primary routine that performs the actual reversal of payroll mix results, removing or voiding the run results and associated entries for the targeted assignments.
  • UNDO_MIX_ASG — The assignment-level counterpart to UNDO_MIX, applying rollback logic to individual assignments within the mix.
  • RUN_RESULTS_EXIST — A validation function that checks whether run results currently exist for the target set, allowing the caller to decide whether a rollback is required.
  • INSERT_ROLLBACK_MESSAGE — Records a rollback-related message into the payroll message tables, providing an audit trail of the operation.
  • COMMIT_MESSAGES — Commits the accumulated message records generated during the rollback so they persist independently of the main transaction.
  • PURGE_ROLLBACK_MESSAGES — Removes stale or processed rollback messages, maintaining the message tables.
  • ACTION_PARAMETER — Resolves or validates the action parameter that drives the rollback behavior, defining the scope or type of action to be performed.
  • SET_STATUS — Updates the status of the rollback operation, reflecting its progress or completion.

Tables Accessed

The package reads and writes a broad set of Payroll and related tables through APPS synonyms. It accesses PAY_RUN_RESULTS, PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_LINKS_F, and PAY_ELEMENT_TYPES_F to identify and reverse element-level results and their definitions. PAY_ASSIGNMENT_ACTIONS and PAY_PAYROLL_ACTIONS track the assignment and payroll action context. Batch processing data is handled through PAY_BATCH_HEADERS, PAY_BATCH_LINES, and PAY_BATCH_CONTROL_TOTALS. Classification data comes from PAY_ELEMENT_CLASSIFICATIONS. Message logging uses PAY_MESSAGE_LINES and PAY_MESSAGE_LINES_S. Concurrent processing is monitored via FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS, and absence data is referenced through PER_ABSENCE_ATTENDANCES, since absences can affect rollback calculations.

Usage Notes

PAY_MIX_ROLLBACK_PKG is typically invoked indirectly by higher-level payroll rollback processes, particularly PAY_ROLLBACK_PKG, rather than being called directly by end users. It is generally triggered during corrective payroll operations, such as when a payroll run must be undone or re-processed, or when administrative actions require reversal. Because it manipulates core payroll result tables, it should be invoked with caution and only within the context of an authorized rollback flow. Custom code or concurrent programs that need rollback functionality should generally call the higher-level ROLLBACK API rather than this package directly.