Search Results balance_totals

Overview

APPS.PAY_AU_REC_PKG is an Oracle Payroll package that supports the Australian localization of Oracle E-Business Suite (12.1.1 and 12.2.2). Its responsibilities are centered on the calculation and reporting of payroll balance information for a given assignment and assignment action. The package header is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking user, relying on APPS synonym grants at run time rather than definer's rights. The package is classified in ETRM as "OTHER" (not a public, certified business API), which indicates it is an internal or supporting routine invoked by payroll processing logic rather than a documented integration entry point. The source header indicates ship level 115.7, dated 2002, confirming that this code is a long-standing component of the Australian payroll engine. The package is referenced by zero other packages, so its callers are external to the PL/SQL package dependency graph — typically forms, concurrent programs, or payroll process drivers.

Key Procedures and Functions

The documented package contains two procedures:

• RUN_BALANCES — Executes a balance calculation for a specified assignment and assignment action at a given effective date, using a named balance type. The procedure accepts a balance name and returns the computed run balance value as an OUT parameter. It is used to derive the value of payroll balances (for example, gross earnings or deductions) as part of payroll run processing for Australian payrolls.
• BALANCE_TOTALS — The procedure matched by the "balance_totals" search term. It aggregates and returns a set of pay-period totals for an assignment and assignment action as of an effective date. The OUT parameters provide gross pay, other deductions, tax deductions, direct payments, and pre-tax deductions for the pay period, each returned through a NOCOPY OUT parameter for efficiency. This procedure therefore supports the assembly of period-to-date or current-pay figures used for reporting, validation, or downstream payment and taxation processing.

Neither procedure returns a status code or raises documented exceptions; callers must manage error handling themselves. The "NOCOPY" hint on all OUT parameters indicates performance-oriented design, common in high-volume payroll loops.

Tables Accessed

The ETRM metadata documents three referenced tables, all accessed via APPS synonyms:

• PER_ALL_ASSIGNMENTS_F — The core HR assignment table. It supplies the assignment context and effective-dated assignment attributes used to identify the employee and period being processed. Both procedures take an assignment ID typed against this table.
• PAY_ASSIGNMENT_ACTIONS — Identifies the specific payroll action (such as a payroll run or reversal) for which balances are calculated. The assignment action ID ties the balance computation to a particular payroll process instance.
• PAY_BALANCE_TYPES — Defines the balance definitions available to the calculation. RUN_BALANCES accepts a balance name typed against this table, ensuring only defined balance types are processed.

Usage Notes

Because PAY_AU_REC_PKG is not a public API, it is not intended for direct customer invocation. It is typically called during Australian payroll run processing and balance reporting, where a payroll process or form needs period totals for an assignment action. The BALANCE_TOTALS procedure in particular is suited to producing a consolidated view of the current pay: gross, deductions, tax, direct payments, and pre-tax deductions, which may then feed reconciliation, payment, or legislative reporting logic. Developers extending Australian payroll should treat this package as an internal dependency: invoke it only from within the payroll processing flow where the required assignment action exists and is current, and supply a valid effective date and assignment context. Callers must also provide their own exception handling, since the documented metadata records no raised exceptions or return status. When migrating from 12.1.1 to 12.2.2, the package remains present in APPS as a shipped object, and customization should avoid modifying it directly in favor of a supported wrapper or extension point.