Search Results po_poxcorsl_xmlp_pkg

Overview

The PL/SQL package body APPS.PO_POXCORSL_XMLP_PKG is the compiled implementation of the package specification bearing the same name. It belongs to the Oracle Purchasing (PO) module and is registered in the APPS schema with a status of VALID. The object is classified as OTHER in the Oracle E-Business Suite API taxonomy, which indicates that it is not a published, callable open interface or business API but rather an internal helper unit.

Its business purpose is associated with the Purchasing ordering and receiving report family. The name segment "POXCO" relates to Purchasing core functionality, "RSL" suggests a results or résumé listing, and the "XMLP_PKG" suffix confirms that the package exists to support an Oracle XML Publisher (BI Publisher) concurrent report definition. In Oracle EBS 12.1.1 and 12.2.2, XML Publisher reports are typically implemented as concurrent programs driven by a report-specific PL/SQL package that supplies data and format triggers. The package body therefore contains the logic required to execute and format one such report rather than transactional business logic.

Key Procedures and Functions

The ETRM documentation records exactly two package-level procedures: BEFOREREPORT and AFTERREPORT. These are the standard Oracle Reports / XML Publisher report trigger hooks generated by the Oracle report conversion tools.

• BEFOREREPORT — Executed before the report data is fetched. In generated XMLP packages this procedure initializes the reporting context, assigns values to package-level variables derived from the concurrent program parameter list, and performs any pre-query setup required so that the subsequent data model query runs with the correct parameters.
• AFTERREPORT — Executed once the report data model has completed. It is used for post-processing, resetting or releasing package-level state, and any final formatting housekeeping.

The names follow the Oracle Reports trigger convention that the XML Publisher report generation utility preserves, and no additional parameters or overloads are documented in the ETRM metadata. Consistent with standard generated report packages, both are called implicitly by the report runtime rather than directly by users.

Tables Accessed

The documented dependency list identifies APPS.ORG_ORGANIZATION_DEFINITIONS as the sole referenced table (resolved through the APPS synonym). This view supplies organization-level information — legal entity, operating unit, and inventory organization attributes — that the report needs to filter and present data correctly for the selected operating unit. The remaining dependency entries, notably SYS.STANDARD and a self-reference to PO_POXCORSL_XMLP_PKG, are compiler artifacts rather than data sources. Because this is a report-support package, it is expected to read from the view only and not to perform DML.

Usage Notes

PO_POXCORSL_XMLP_PKG is not referenced by any other database object, as confirmed by the ETRM report. It is invoked exclusively by the Oracle EBS report runtime when the corresponding XML Publisher concurrent program is submitted. Typical invocation points are:

• The Purchasing responsibility concurrent program tied to the report, where the request is submitted and BEFOREREPORT and AFTERREPORT are fired automatically.
• Scheduled or request-set-based runs in which the same report is executed repeatedly with varying parameters.
• Diagnostic execution, where a developer submits the concurrent request directly to validate output templates, data model SQL, or parameter handling.

Because the package is an internal, non-API object, customization should avoid modifying the seed package body in place. Any extension should be applied through a supported template or a copy of the concurrent program definition, so that Oracle patching in 12.1.1 or 12.2.2 does not overwrite the change.