Search Results pay_pyaufbr_xmlp_pkg




Overview
Explore in AI Chat

Overview

APPS.PAY_PYAUFBR_XMLP_PKG is a PL/SQL package that supports the Oracle Payroll concurrent program associated with the PYAUFBR (Australian Payroll) XML Publisher (BI Publisher) report. Within Oracle E-Business Suite 12.1.1 and 12.2.2, packages bearing the _XMLP_PKG suffix are generated to accompany XML Publisher–based concurrent programs: they encapsulate the report logic, data formulas, and formatting hooks that the XML Publisher engine calls at execution time. This package follows that pattern, providing the server-side PL/SQL that produces and formats the data set consumed by the underlying report template.

The package is owned by the APPS schema and is documented as VALID, with an API classification of OTHER — indicating it is an internal support package rather than a public or certified API. Its dependency footprint is minimal, referencing only the SYS.STANDARD package, which confirms it is a leaf-level report package not intended for broad reuse. The metadata records a single self-referential dependency (the package referencing itself), which is typical of XML Publisher wrapper packages whose specification and body are listed together.

Key Procedures and Functions

The ETRM documentation records seven documented procedures and functions within this package:

  • BEFOREREPORT — The pre-execution hook invoked by the XML Publisher engine immediately before the report data is generated. It is used to initialize session-level and package-level context, such as defaulting values and setting up the runtime environment for the report.
  • AFTERREPORT — The post-execution hook invoked after report generation completes. It performs cleanup or finalization logic at the end of the report run.
  • CF_BUSINESS_GROUPFORMULA — A report formula (CF_ prefix denoting a "column formula" or computed formula) that resolves the business group context for the report, ensuring the output is scoped to the correct HR business group.
  • CF_LEGISLATION_CODEFORMULA — A formula that returns the legislation code, identifying the payroll legislative context (Australia, given the PYAUFBR program) under which the report executes.
  • CF_CURRENCY_FORMAT_MASKFORMULA — A formula that supplies the currency format mask, governing how monetary amounts are displayed in the report output.
  • CF_EXISTSFORMULA — A conditional formula used to determine whether a given value or record exists, typically to drive conditional display logic in the report template.
  • CP_CURRENCY_CODE_P — A concurrent program parameter or column property (CP_ prefix) associated with the currency code, providing the currency code value used throughout the report.

Parameter lists are not documented in the available metadata and are deliberately not enumerated here.

Tables Accessed

The package reads from three tables through APPS synonyms:

  • FND_CURRENCIES — The Oracle Application Object Library currency definition table. It is queried to resolve currency codes and their associated format masks, directly supporting CP_CURRENCY_CODE_P and CF_CURRENCY_FORMAT_MASKFORMULA.
  • HR_ALL_ORGANIZATION_UNITS — The core HR organization definition table. It supplies the organization/business group data used by CF_BUSINESS_GROUPFORMULA to scope report output to the correct organizational unit.
  • HR_ORGANIZATION_INFORMATION — The flexible attribute table holding additional organization-level details (such as legislation information). It supplements HR_ALL_ORGANIZATION_UNITS in resolving business group and legislative context.

Usage Notes

This package is invoked indirectly rather than directly. It is called by the XML Publisher runtime when the associated Payroll concurrent program (PYAUFBR) is submitted, with BEFOREREPORT and AFTERREPORT bracketing report execution and the CF_/CP_ components supplying runtime values to the report template. The package is referenced by no other packages per the documented metadata, confirming that it is not a shared utility. Because it is classified as OTHER and is not a public API, customizations should not call it directly; instead, report changes should be made through supported XML Publisher template and concurrent program configuration mechanisms. It remains VALID in both 12.1.1 and 12.2.2, and its dependency isolation on SYS.STANDARD makes it low-risk with respect to recompilation during patching or upgrades.