Search Results po_poxpopar_xmlp_pkg




Overview
Explore in AI Chat

Overview

PO_POXPOPAR_XMLP_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. It is the generated runtime implementation behind the Oracle Reports executable associated with the POXPOPAR report, one of the standard purchasing reports in the Oracle Purchasing module. The naming convention follows the Oracle XML Publisher / Oracle Reports integration pattern in which a report definition generates a supporting PL/SQL package containing an AFTERPFORM, BEFOREREPORT, and AFTERREPORT trigger along with a set of data-fetch and formatting helper functions. This package therefore provides the report grouping, lookup decoding, currency rounding, and system-parameter resolution logic that drives the printed output, including corporate identity, cost center labeling, and precision handling for monetary values. In EBS 12.1.1 and 12.2.2 the package is a standard, VALID database object and is classified as OTHER under the API classification scheme, reflecting its status as report infrastructure rather than a published business API.

Key Procedures and Functions

The documented package exposes fourteen procedures and functions:

  • COMPANY — Returns the company or legal entity name used as the report header or organizational identity.
  • COST_CENTER — Resolves and returns the cost center value displayed for the report's operating unit or inventory organization context.
  • GET_PRECISION — Determines the currency precision (decimal places) applied to monetary columns.
  • ORDERBY_CLAUSEFORMULA — Supplies the ordering clause applied to the report's result set, allowing runtime control of sort sequence.
  • BEFOREREPORT — The report-level before-trigger; establishes session context, initializes parameters, and prepares lookups prior to data retrieval.
  • AFTERREPORT — The report-level after-trigger; performs cleanup or final formatting actions once report execution completes.
  • GET_LOOKUP_MEANING — Wraps lookup resolution to translate stored lookup codes into their user-facing meanings.
  • GET_BOILER_PLATES — Retrieves boilerplate text such as standard legal, regulatory, or organizational statements.
  • SET_DISPLAY_FOR_GOV — Toggles display behavior for government-oriented report variants.
  • SET_DISPLAY_FOR_CORE — Toggles display behavior for the core (non-government) report variant.
  • ROUND_AMOUNT_LIST_SUBTOTAL_REP — Applies currency rounding to reported subtotal amounts in the report list section.
  • AFTERPFORM — The parameter form after-trigger; validates or transforms user-entered report parameters.
  • C_INDUSTRY_CODE_P — Package-level constant or function supplying the industry code parameter.
  • C_COMPANY_TITLE_P — Package-level constant or function supplying the company title parameter.

Tables Accessed

Per the recorded metadata, the package reads the following tables through APPS synonyms:

  • FINANCIALS_SYSTEM_PARAMETERS — Used to derive the ledger, currency, and accounting setup governing rounding and precision behavior.
  • FND_SEGMENT_ATTRIBUTE_VALUES — Used to determine which key flexfield segments are enabled and displayed, supporting cost center and company resolution.

Additional dependencies recorded in the object metadata include FINANCIALS_SYSTEM_PARAMETERS, FND_INSTALLATION, FND_LOOKUPS, FND_SEGMENT_ATTRIBUTE_VALUES, GL_SETS_OF_BOOKS, PO_COMMON_XMLP_PKG, and PO_LOOKUP_CODES. PO_COMMON_XMLP_PKG is of particular note as a shared purchasing report utility package from which common report logic is inherited.

Usage Notes

This package is not a callable business API; it is invoked indirectly when the associated Oracle Purchasing report is run from the Submit Requests form or the concurrent manager. It is not referenced by any other database object, so custom code should not depend on it. In 12.1.1 and 12.2.2 the package body is regenerated when the underlying report definition is compiled or re-uploaded, so any direct modification is unsupported and will be overwritten. Organizations customizing purchasing report output should extend via XML Publisher templates or custom concurrent programs rather than editing this generated package. Troubleshooting typically involves confirming the package body is VALID and that dependent objects such as PO_COMMON_XMLP_PKG and the lookup tables remain accessible.