Search Results po_chvprsch_xmlp_pkg




Overview

APPS.PO_CHVPRSCH_XMLP_PKG is a PL/SQL package body in the Oracle E-Business Suite APPS schema classified as an XML Publisher (BI Publisher) report package. It supports the Purchasing schedule report, whose internal name is CHVPRSCH, a concurrent program that produces a printed or published listing of supplier scheduling headers drawn from the Oracle Supplier Scheduling module. In the EBS architecture, report packages named with the _XMLP_PKG suffix are generated to wrap a report's data model: they expose the lexical parameters and group filters that the XML Publisher engine binds at runtime, and they contain the PL/SQL that executes the report's query and formats derived values before the XML output is rendered.

The package is documented as VALID in ETRM for both release 12.1.1 and 12.2.2 and is classified as API OTHER, which indicates that Oracle does not publish it as a supported extension point. It is referenced by no other database object, confirming its role as a leaf-level report artifact consumed only by the concurrent program that invokes it. It is a wrapper rather than a business API, and its logic is tightly coupled to the column layout of the underlying report.

Key Procedures and Functions

Five program units are documented.

  • BEFOREREPORT — The standard XML Publisher report initializer. It runs before the data model executes and is used to derive report context values, such as effective date and organizational parameters, and to initialize package-level state used by the remaining units.
  • AFTERREPORT — The complementary teardown routine, invoked after the data model has completed. It resets package globals so that successive runs of the concurrent program in the same session do not leak state between executions.
  • G_HEADERSGROUPFILTER — A group filter function associated with the report's headers group. In XML Publisher data models a group filter restricts the rows returned for a repeating group; here it constrains the schedule header set according to the report parameters supplied at submission.
  • GET_PRECISION — Returns the numeric precision used when formatting quantity or currency columns in the report output, ensuring consistent decimal presentation.
  • ADDRESSFORMULA — A formula column that assembles a printable address string from the location and organization attributes retrieved by the query, producing the formatted supplier or ship-to address block printed on the schedule report.

Tables Accessed

The package reads two documented tables through APPS synonyms.

  • CHV_SCHEDULE_HEADERS — The primary source of report content. This is the Supplier Scheduling header table, holding the schedule number, supplier, item, dates, and status information that the report lists and filters.
  • HR_LOCATIONS_ALL — Supplies location details, including address lines, city, and postal attributes, that feed the ADDRESSFORMULA calculation. Organization unit data is also resolved through HR_ORGANIZATION_UNITS as part of the same lookup chain.

Only the CHV_SCHEDULE_HEADERS and HR_LOCATIONS_ALL tables are enumerated in the dependency list; no inserts, updates, or deletes are documented, consistent with a read-only reporting package.

Usage Notes

PO_CHVPRSCH_XMLP_PKG is never invoked directly by application forms or by customer-written code. It is called by the XML Publisher engine when the Supplier Scheduling report concurrent program is submitted from the Purchasing responsibility. The report template and data model definitions are registered against this package, and the BEFOREREPORT and AFTERREPORT hooks fire automatically around each execution.

Because the package is an internal, unsupported artifact, customizations should be confined to a copied concurrent program definition and a cloned data model rather than editing APPS.PO_CHVPRSCH_XMLP_PKG. Any in-place modification risks being overwritten by patching or by the AD utilities that regenerate report packages, and it may invalidate dependent objects. Where additional columns or filters are required, the supported approach is to create a custom XML Publisher report that reuses the same base tables.