Search Results p_where_cat

Overview

APPS.PO_POXRFRAR_XMLP_PKG is the generated PL/SQL package specification that supports the Oracle Purchasing XML Publisher concurrent program POXRFRAR — commonly identified as the "Purchase Order Detail" or related purchasing report driven by a BI Publisher (XML Publisher) template. Like other _XMLP_PKG packages in Oracle E-Business Suite, it is not hand-written application logic; it is produced automatically when a report is registered as an XML Publisher (BI Publisher) program. Oracle EBS uses this package to expose report parameters as package-level variables and to host the BeforeReport and AfterReport trigger functions that the concurrent manager invokes at defined points in the report life cycle.

The package is declared with AUTHID CURRENT_USER, meaning its SQL and PL/SQL execute under the privileges of the invoking session rather than the definer, consistent with standard APPS-level security. Its header carries the revision marker $Header: POXRFRARS.pls 120.2 2008/01/05 17:09:33 dwkrishn noship $, indicating it has been part of the Oracle Purchasing code line since the 12.x releases and is "noship," i.e., internal/unpublished. All of the fields declared in the specification are report parameters.

Key Procedures and Functions

The specification documents three program units, all implemented in the package body:

• BeforeReport — Returns a boolean. It is executed by the report engine before the main query fires. This is the standard hook used to derive or validate runtime parameters and to set up session state needed by the report.
• AfterReport — Returns a boolean. It runs after the report body completes and is the conventional place to release resources, reset package state, or perform cleanup.
• get_p_struct_num — Returns a boolean. This helper supports resolution of the P_STRUCT_NUM parameter, which controls the key flexfield structure used for the category segment in the report. It is typical of generated XMLP packages in which a look-up function drives dependent parameters.

No parameter lists are documented for these units, and none should be assumed beyond the generated report-trigger conventions. All report parameters — P_title, P_CONC_REQUEST_ID, P_DATE_FROM, P_DATE_TO, P_VENDOR_FROM, P_VENDOR_TO, P_BUYER, P_FLEX_CAT, P_WHERE_CAT, P_STRUCT_NUM, P_category_from, P_category_to, P_ORDERBY, and P_ORDERBY_DISP — are declared as package-level variables and populated by the concurrent manager before the triggers fire.

Tables Accessed

The ETRM metadata for this package lists no tables directly referenced through APPS synonyms. This is expected: the base tables backing the report are accessed by the report SQL query itself, while the generated XMLP package typically only reads parameter values and, where used, performs look-ups against flexfield or value-set views to validate P_FLEX_CAT, P_STRUCT_NUM, and the category range parameters (P_category_from / P_category_to). Users searching for "p_category_to" are searching within this package because that variable appears in the specification at line 14; it is the upper bound of the category key flexfield range entered on the report parameter form.

Usage Notes

This package is not intended for direct invocation by custom code. It is called by the Oracle Concurrent Manager and the XML Publisher report engine when the associated concurrent program is submitted from the Submit Requests form or scheduled as a request set. In Oracle EBS 12.1.1 it is registered as a Java/XML Publisher concurrent program with format templates; in 12.2.2 it retains the same role, with the report definition managed under the XML Publisher Administrator or the 12.2 BI Publisher integration. Customization is not supported on the generated package; instead, users customize the report by copying and editing the data model and template. The presence of P_CONC_REQUEST_ID confirms standard concurrent-program context passing, used for log and output handling during execution.