Search Results pa_paxaarul_xmlp_pkg




Overview
Explore in AI Chat

Overview

PA_PAXAARUL_XMLP_PKG is an Oracle EBS Application Object Library (AOL) XML Publisher (BI Publisher) report package body owned by the APPS schema. It is a generated PL/SQL wrapper that supports an Oracle Projects XML Publisher report. The "PA" prefix identifies the module as Oracle Projects, and the "_XMLP_PKG" suffix confirms that the package is the data-definition and after-report logic container for a concurrent program whose output is rendered through XML Publisher rather than the legacy Report Builder engine. The report governed by this package relates to project rules ("PA_RULES") and produces a listing that includes a company or organization header and a rule name. The package is classified as "OTHER" in the documented API metadata, meaning that Oracle does not publish it as a supported public API; it is intended for internal use by the concurrent program framework. Its dependencies include standard AOL and SQL constructs (FND_PROFILE, DBMS_STANDARD, STANDARD) together with Oracle General Ledger and Oracle Projects lookup and rule tables (GL_SETS_OF_BOOKS, PA_LOOKUPS, PA_RULES). The package body is documented as VALID in ETRM at 12.2.2 and is referenced by no other database object, consistent with the role of a top-level report driver package.

Key Procedures and Functions

Eight procedures and functions are documented on the package. They fall into two categories: report lifecycle hooks and report data helpers.

  • BEFOREREPORT — The standard XML Publisher pre-execution hook. It initializes session state, typically resolving profile option values and report parameters before the data query executes.
  • AFTERREPORT — The post-execution counterpart to BEFOREREPORT. It performs cleanup or finalization after the report data has been fetched and before the XML output is finalized.
  • GET_COVER_PAGE_VALUES — Populates cover-page attributes such as report title, run date, and organizational context used on the report's header page.
  • GET_COMPANY_NAME — Resolves and returns the company or organization name displayed in the report header, typically based on the operating unit or set of books in context.
  • C_COMPANY_NAME_HEADER_P — A package-level constant or getter that supplies the company name header label used in the report's layout.
  • C_RULE_NAME_P — A constant or getter that supplies the rule name label, reflecting the report's focus on Oracle Projects rules.
  • C_NO_DATA_FOUND_P — Supplies the message text displayed when the report query returns no qualifying rows.
  • C_DUMMY_DATA_P — Supplies the dummy or placeholder data string used by the XML Publisher template when the result set is empty, ensuring the layout still renders.

Parameter lists are not published in the ETRM metadata and should not be assumed; callers should treat these as internal report helpers.

Tables Accessed

Documented table access is limited to PA_RULES, read via an APPS synonym. This confirms that the report extracts rule definitions from Oracle Projects and presents them with an organizational header. The dependency list also shows FND_PROFILE, used to resolve profile option values such as operating unit or organization context; GL_SETS_OF_BOOKS, used to derive set-of-books and currency context for the header; and PA_LOOKUPS, used to decode lookup codes into display values. No write operations are documented; the package is a read-only reporting component.

Usage Notes

PA_PAXAARUL_XMLP_PKG is not invoked directly by end users or custom code. It is executed by the Oracle EBS concurrent manager when the associated XML Publisher concurrent program is submitted, either from the Projects responsibility menu or from a scheduled request set. BEFOREREPORT and AFTERREPORT are called automatically by the XML Publisher engine, while the remaining procedures and constants are referenced by the report's data template and RTF layout. Because the package is not referenced by any other database object, it may be regenerated during patching or upgrade without affecting dependent code. Customizations should not modify this package body; instead, the underlying XML Publisher data template or RTF layout should be copied and extended. Integrity of PA_RULES, PA_LOOKUPS, GL_SETS_OF_BOOKS, and FND_PROFILE is therefore a prerequisite for correct report output.