Search Results po_poxrvods_xmlp_pkg

Overview

PO_POXRVODS_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. The naming convention identifies it as the generated package body that supports an Oracle Reports executable registered against the Purchasing module — specifically the report POXRVODS, with the _XMLP_PKG suffix indicating that the report is published through the Oracle XML Publisher (BI Publisher) engine introduced in Release 12. In Oracle EBS 12.1.1 and 12.2.2, every XML Publisher–enabled concurrent report is accompanied by a package of this type. Oracle Reports substitutes the packaged functions and procedures into the report's data model at execution time, so the package itself does not implement business logic in the conventional sense; instead it supplies the report's declarative parameters, format masks, and report-level trigger logic.

The package is classified as OTHER in the ETRM API classification and is marked VALID. It does not expose a public API for third-party or custom integration; it is invoked exclusively by the Oracle Reports runtime when the associated concurrent program is submitted. Its sole dependency in the data dictionary is on SYS.STANDARD, and no other APPS packages reference it, which confirms that it is a leaf-level, report-support object rather than a shared library.

Key Procedures and Functions

ETRM documents six procedures and functions within the package. Each corresponds to a standard report-level construct.

• BEFOREREPORT — Executes before the report's data model is processed. It is used to initialize report-level state, such as resolving session or parameter context needed by the query.
• AFTERREPORT — Executes after the report's data has been fetched and formatted. It is typically reserved for cleanup of report-level variables or post-processing hooks.
• AFTERPFORM — Runs after the report's parameter form has been submitted and its values validated. This is the standard entry point for applying user-supplied parameter values before the main query executes.
• GET_PRECISION — Returns a numeric precision value used by the report layout to format quantity or amount columns consistently. This is a generated helper rather than a business rule.
• GET_P_STRUCT_NUM — Returns the value of the structure number parameter, which in Purchasing reports identifies the item or category structure used to drive the flexfield display.
• C_ITEM_FLEXFORMULA — Supplies the flexfield formula used to render the item key flexfield concatenated segment display within the report output.

Tables Accessed

The ETRM dependency extract lists no tables referenced through APPS synonyms for this package. This is consistent with the generated-package model: the report's SQL statements are stored in the Oracle Reports definition file and executed by the Reports server, not embedded as static SQL inside the PL/SQL package. The package therefore reads no application tables directly. Any Purchasing data — purchase orders, releases, suppliers, or item flexfield structures — is retrieved by the report query itself, with the package contributing only parameter values and formatting instructions.

Usage Notes

PO_POXRVODS_XMLP_PKG is never called from Oracle Forms or from custom PL/SQL. It is invoked implicitly and only when the associated POXRVODS concurrent program or report request is run. In 12.1.1 the report is submitted through the standard Concurrent Programs form or the Requests window; in 12.2.2 the same execution path applies, with the report output rendered through the XML Publisher template associated with the program definition.

Because the package is generated and regenerated by Oracle, it should not be modified or extended. Customizations that require additional logic must be implemented through the report definition, an XML Publisher data template, or a separate custom package, leaving PO_POXRVODS_XMLP_PKG untouched so that Oracle patching and upgrades can replace it safely. Organizations troubleshooting report failures should treat anomalies in this package as symptoms of a broader report or template issue rather than as defects in application logic.