Search Results pay_reverse_payroll_pkg




Overview

PAY_REVERSE_PAYROLL_PKG is an Oracle Payroll package owned by the APPS schema and classified in the ETRM repository as an "OTHER" API. Its responsibility centres on the reversal of payroll processing — the controlled rollback of a payroll run and the assignment-level actions that payroll processing generated. In Oracle EBS 12.1.1 and 12.2.2, payroll runs create rows in PAY_PAYROLL_ACTIONS (a run header) and corresponding assignment-level entries in PAY_ASSIGNMENT_ACTIONS. When a payroll run must be undone — because it was submitted in error, contained incorrect data, or needs to be reprocessed — the reversal logic must remove or invalidate those generated records in a consistent manner. This package provides the data-manipulation layer that supports that operation.

The package is a supporting, low-level component rather than an end-user API. Its status is VALID, and it depends only on the SYS.STANDARD package, indicating it does not itself call further application APIs. The ETRM record shows a reciprocal self-reference in the "referenced by" list, which is typical of packages whose specification and body are catalogued together. The documented interface is deliberately narrow, exposing a single procedure.

Key Procedures and Functions

The documented ETRM metadata lists two procedures or functions in total, with the procedure INSERT_ROW identified by name. Consistent with its classification and its limited dependency footprint, the package is a data-level insert helper rather than a business-rule engine.

  • INSERT_ROW — Inserts a row into the target payroll action table, providing the low-level record creation used during reversal processing. The ETRM record does not publish a parameter list, and none is asserted here.
  • Second documented subprogram — The metadata records two subprograms in total but names only INSERT_ROW. The remaining entry is not named in the available documentation and is therefore not described further.

Because the published interface is minimal, custom code should not assume additional public entry points. Any extension of reversal behaviour should be implemented through supported Oracle Payroll APIs rather than by calling internal helpers directly.

Tables Accessed

The ETRM metadata documents three tables referenced through APPS synonyms:

  • PAY_ASSIGNMENT_ACTIONS — Holds the assignment-level action records created when payroll processes an assignment. Reversal must reconcile or remove these entries so the assignment returns to its pre-run state.
  • PAY_PAYROLL_ACTIONS — The payroll action header, representing the payroll run or action being reversed. The package writes the action record that documents the reversal.
  • PAY_PAYROLL_ACTIONS_S — The translation or secondary table associated with PAY_PAYROLL_ACTIONS, holding the action's descriptive text. Inserts into the action are accompanied by the corresponding localized row.

The presence of PAY_PAYROLL_ACTIONS_S indicates the package maintains the paired row required for the action's display text, which is essential for the reversal to appear correctly in payroll inquiry and reporting.

Usage Notes

PAY_REVERSE_PAYROLL_PKG is invoked indirectly through the standard Oracle Payroll reversal flows rather than being called directly by end users. Reversal is normally initiated from the Payroll window on the Submit Requests or Reverse Payroll form, or through the concurrent program that processes the reversal request. The package's procedures then execute within that server-side flow to write the reversal action records.

Its dependency profile — referencing only SYS.STANDARD and being referenced by no other documented packages — confirms that it is a leaf component in the dependency chain and does not participate in broader API orchestration. Custom development should treat it as internal to Oracle Payroll. Where additional reversal logic is required, the supported approach is to use Oracle's public payroll APIs and concurrent programs, leaving this package untouched to preserve upgrade safety across 12.1.1 and 12.2.2.