Search Results c_per_item_varformula




Overview

PO_POXSERPR_XMLP_PKG is an Oracle Applications (APPS) PL/SQL package that supports the XML Publisher (BI Publisher) concurrent program associated with the Purchasing Supplier Delivery Performance report — the report commonly referenced by the search term po_received. Authored with AUTHID CURRENT_USER and bearing a header version of 120.1 dated 2007, the package encapsulates the runtime parameters, report-level triggers, and formula functions that the XML Publisher template engine invokes during report execution. Its purpose is to compute delivery performance metrics — on-time, early, late, rejected, and open quantities — relative to ordered quantities captured in the po_received data set, and to format the result set for rendering by the report layout.

The package follows the standard _XMLP_PKG naming convention used throughout EBS 12.1.1 and 12.2.2, where the database package holds the logic that would once have been embedded in a classic Oracle Reports PL/SQL library. The report output is driven by the concurrent request identifier P_CONC_REQUEST_ID, which the package stores to correlate the session with the submitted request.

Key Procedures and Functions

The package exposes report lifecycle triggers and a set of calculation formulas. Documented procedures and functions include:

Tables Accessed

The package references two documented tables through APPS synonyms:

  • FINANCIALS_SYSTEM_PARAMETERS — Read to obtain operating unit and system-level defaults, including precision and currency context required for report formatting.
  • PER_ALL_PEOPLE_F — Read to resolve buyer names and person details associated with purchasing activity, supporting the buyer parameter and grouping logic.

The core po_received transactional data is supplied through the report's XML data definition query rather than being queried directly inside the package, which explains why transactional receiving tables do not appear in the documented table list.

Usage Notes

This package is invoked exclusively by the XML Publisher concurrent program for the Supplier Delivery Performance report. It is not designed for direct call by custom code, and the metadata confirms it is referenced by zero other packages. Parameters such as P_VENDOR_FROM, P_VENDOR_TO, P_BUYER, P_CREATION_DATE_FROM, and P_CREATION_DATE_TO are populated from the concurrent program parameter form at submission time. In both 12.1.1 and 12.2.2 the package behaves identically, as it resides in the APPS schema and is dependent only on the two documented synonyms; customisations should therefore be applied with care, as altering formula behaviour affects every submitted run of the report.