Search Results cp_ot_message




Overview

APPS.PAY_PYAUPYT_XMLP_PKG is the generated PL/SQL package body that supports the Oracle Payroll Australian Payroll Tax report, an XML Publisher (BI Publisher) concurrent program in Oracle E-Business Suite 12.1.1 and 12.2.2. The package follows the standard Oracle Reports-to-XML Publisher conversion pattern, in which Oracle Reports user exits, format triggers, and group filters are re-implemented as PL/SQL functions within a package whose name ends in _XMLP_PKG. The prior report-specific logic executes during the Before Report, After Report, and formula-column phases of the concurrent request lifecycle.

The package achieves two core objectives. First, it derives display values for report parameters and column formulas from Oracle HR and Payroll reference tables, so that the XML output shows lookup meanings, currency formatting masks, legislation codes, and organization names rather than raw identifiers. Second, it purges transient staging data written to PAY_ACTION_INFORMATION by the pre-processor when the concurrent request completes. The $Header value (PYAUPYLB.pls 120.1) indicates this is the XML Publisher label variant distributed with the Australian payroll tax feature.

Key Procedures and Functions

The 14 documented program units divide into three groups:

No public API signature beyond the report parameter set is exposed; the package is invoked exclusively by the XML Publisher engine.

Tables Accessed

Usage Notes

The package is invoked automatically when the Australian Payroll Tax concurrent program (short name PYAUPYT) is submitted from the Submit Requests form or the Australian Payroll Tax report form. It is not referenced by any other PL/SQL package, so custom code should call the concurrent program rather than the package directly.

Because AFTERREPORT deletes rows from PAY_ACTION_INFORMATION, PAY_ASSIGNMENT_ACTIONS, and PAY_PAYROLL_ACTIONS, the report is destructive by design; the affected payroll action should not be reused. The exception handler issues a ROLLBACK, but the COMMIT that follows the exception block is issued unconditionally, so partial processing should be verified when errors occur. In 12.2.2 the package executes under the APPS schema with the standard XML Publisher security model, and the report output is generated as XML data plus an RTF template.