Search Results orderby_clauseformula

Overview

The APPS.PO_POXSURQC_XMLP_PKG package is the PL/SQL specification associated with the Oracle E-Business Suite Oracle Reports executable POXSURQC, the Purchasing "Supplier Quality" report. It belongs to the Oracle Purchasing (PO) module and follows the long-established EBS pattern in which every Oracle Reports-based concurrent program is paired with a generated package specification that declares report-level variables, user-facing display parameters, and a small set of callable formula functions embedded into the report definition. In EBS 12.1.1 and 12.2.2 this package is a file-based library object compiled into the APPS schema and is registered against the report template so that the Reports runtime can resolve the packaged functions and public variables during execution.

In the context of the search term orderby_clauseformula, this package is significant because it is the declaring unit for the packaged function orderby_clauseFormula, which governs the dynamic ordering applied to the report's result set. The package therefore acts as a lightweight configuration surface between the concurrent program's parameters and the SQL driving the underlying report query.

Key Procedures and Functions

The ETRM metadata documents three callable units within the package specification:

• orderby_clauseFormula — Returns a VARCHAR2 value that supplies the ORDER BY clause text used by the report's data model. This is the function referenced by the search term. It is invoked by the Oracle Reports engine when the report's query group is executed, translating the user's chosen sort (captured in the public package variable P_ORDERBY) into a literal SQL sort expression. Its presence explains why the report can offer user-selectable sort ordering without shipping separate report definitions.
• BeforeReport — The standard Oracle Reports before-report trigger function, returning a boolean. It performs pre-execution initialisation such as resolving the active/inactive parameter into a display string, populating P_active_inactive_disp and P_orderby_displayed, and validating the concurrent request context (P_CONC_REQUEST_ID). Returning FALSE suppresses report execution.
• AfterReport — The standard after-report trigger function, returning a boolean. It executes once the report output has been produced and is used for post-processing, cleanup, or signalling completion back to the concurrent manager.

The package specification additionally exposes the public variables P_title, P_ACTIVE_INACTIVE, P_ORDERBY, P_active_inactive_disp, P_orderby_displayed, and P_CONC_REQUEST_ID, which carry values between the concurrent program parameter form and the report layout.

Tables Accessed

The ETRM metadata records no tables referenced through APPS synonyms for this package specification. This is consistent with the nature of a generated report package specification: the specification declares signatures and shared variables only, while the actual DML and query activity is embedded in the Oracle Reports data model queries that reference Purchasing supplier and quality tables directly. Consequently, no direct table access is attributable to this package in the documented metadata.

Usage Notes

The package is invoked indirectly rather than called from custom code. When a user submits the Supplier Quality report concurrent program, the Oracle Reports runtime loads POXSURQC, resolves the packaged triggers and formula columns against PO_POXSURQC_XMLP_PKG, and executes BeforeReport, the query with the sort supplied by orderby_clauseFormula, and finally AfterReport. Because the package is owned by APPS and classified as OTHER, it is not part of a published PL/SQL API, and the metadata records no other packages depending on it. Customisations should be limited to the underlying report definition and its parameter values; direct calls to orderby_clauseFormula from external code are not a supported interface and would not be meaningful outside the Reports execution context.