Search Results p_flex_item




Overview

APPS.PO_POXRQEXP_XMLP_PKG is the generated PL/SQL package that supports the Oracle Purchasing requisition export concurrent program (short name POXRQEXP), an XML Publisher (BI Publisher) based report. The package encapsulates the global variables, the data selection logic, and the report trigger entry points required by the Oracle Reports/XML Publisher runtime to render the purchase requisition export output. Its header identifies it as a source-controlled package with the revision string $Header: POXRQEXPS.pls 120.1 2007/12/25 11:51:40 krreddy noship $, indicating it belongs to the Purchasing (PO) product family and has been maintained under the standard EBS naming convention for XML Publisher report packages.

The package spec declares several global variables that are populated by the concurrent program parameters and consumed by the underlying query and report layout. These include P_CONC_REQUEST_ID, P_TITLE, P_EXPRESS_NAME, and the Flexfield-related variables P_FLEX_ITEM, P_FLEX_CAT, P_STRUCT_NUM, and P_ITEM_STRUCT_NUM. The variable P_FLEX_CAT, which is the term searched for (p_flex_cat), is declared as varchar2(31000) and holds the concatenated key flexfield segment values for the Category Flexfield used to filter or display the requisition export.

Key Procedures and Functions

  • BeforeReport — Standard Oracle Reports/XML Publisher format trigger that executes prior to the main query and report body generation. It is the point at which the package prepares global state, typically calling the structure-number resolution logic so that the correct key flexfield structure and segment information are available to the report query.
  • get_p_struct_num — A helper function responsible for resolving and returning the key flexfield structure number(s) used by the report. This drives the interpretation of the Flexfield variables, including the item and category structures referenced by P_ITEM_STRUCT_NUM and P_STRUCT_NUM. By separating this lookup into a dedicated function, the package allows the report to adapt to the applicable chart of accounts or item/category flexfield configuration in the current operating unit.
  • AfterReport — Post-report format trigger invoked after the report output has been produced. It performs any necessary cleanup or finalization logic required by the XML Publisher runtime.

No parameter lists are exposed in the documented specification, and the ETRM metadata records no additional procedures beyond these three entry points.

Tables Accessed

The provided ETRM metadata does not enumerate any tables referenced through APPS synonyms for this package. In practice, the underlying report query associated with PO_POXRQEXP_XMLP_PKG draws on Purchasing requisition data, including PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL, together with flexfield definition views used to resolve structure numbers. Because the documented metadata lists no referenced tables and no downstream packages, consumers should treat the table access as indirect — through the report's SQL rather than through explicit DML in the package body.

Usage Notes

This package is invoked by the Oracle Purchasing requisition export concurrent program rather than by forms or ad hoc custom code. It is not designed as a general-purpose API, and the ETRM metadata confirms it is referenced by no other packages. The p_flex_cat / P_FLEX_CAT variable is populated from the concurrent program parameter that captures the Category Flexfield value; because the variable is sized at 31,000 characters, it accommodates fully concatenated multi-segment category flexfield values and is used to constrain or label the export output. Technical consultants customizing the report should modify the underlying XML Publisher data template and query rather than editing the package, since the package is generated. For diagnostics, checking the value of P_FLEX_CAT and the structure numbers returned by get_p_struct_num is the standard approach when a requisition export returns no rows or incorrect category filtering under EBS 12.1.1 or 12.2.2.