Search Results po_poxsurqc_xmlp_pkg

Overview

PO_POXSURQC_XMLP_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the generic "OTHER" API category. It supports the concurrent program identified by the short name POXSURQC, a Purchasing-supplier survey or supplier quality questionnaire report built on the Oracle Reports XML Publisher (XMLP) architecture. In the EBS 12.1.1 and 12.2.2 releases, report-based concurrent programs are wrapped in a generated package whose naming convention follows <report_short_name>_XMLP_PKG. The package body encapsulates the PL/SQL logic invoked by the report's Before Report, After Report, and formatted trigger points, allowing the report definition to remain declarative while the runtime behaviour is driven from the database.

Key Procedures and Functions

The ETRM metadata documents three procedures or functions in this package body:

• ORDERBY_CLAUSEFORMULA — A formula/function used to construct or return the ORDER BY clause applied to the report's result set. Oracle Reports XMLP wrapper packages typically expose the dynamic sort clause through this entry point so the report's SQL can be sorted at runtime without hard-coding the ordering in the query definition. It allows the report to present supplier survey records in a user- or profile-determined sequence.
• BEFOREREPORT — The Before Report trigger handler. This procedure executes once at the start of report execution, prior to the main query being run. It is the standard location for initialising package-level variables, resolving session and profile option values, setting up the reporting context, and preparing any parameters or globals required by the data model.
• AFTERREPORT — The After Report trigger handler. This procedure runs after the report's data model has been processed and the output produced. It is used for post-processing, releasing resources, or performing any final bookkeeping required by the concurrent request lifecycle.

No parameter lists are documented in the ETRM record, and none should be assumed; the generated XMLP wrapper convention typically declares these procedures without formal arguments, relying on package globals and Oracle Reports bind/lexical parameters.

Tables Accessed

The documented dependency list shows that the package body references PO_LOOKUP_CODES, the Purchasing lookup codes view (the APPS synonym that resolves to PO_LOOKUP_CODES_V or the underlying PO_LOOKUP_CODES table). This view supplies the seeded and user-defined lookup values used to decode survey question types, response categories, statuses, and similar code columns presented on the report. The dependency record lists no other application tables, and the package is not referenced by any other database object, confirming it is a leaf-level report wrapper rather than a shared utility.

Usage Notes

PO_POXSURQC_XMLP_PKG is not intended for direct invocation from forms, custom APIs, or ad hoc PL/SQL. It is invoked indirectly by the Oracle Reports runtime when the POXSURQC concurrent program is submitted from the Purchasing responsibility, or when the report is executed through the standard concurrent manager. Supporting dependencies include the SYS.STANDARD package and the package itself (recursive reference in the dependency listing). Because the object is not referenced by any other database object, changes to its body have no downstream PL/SQL impact, though any modification affects the output of the associated concurrent program. The package status is VALID in the documented environment, indicating it compiled successfully and is available for report execution.