Search Results po_poxaglst_xmlp_pkg

Overview

PO_POXAGLST_XMLP_PKG is the generated PL/SQL package body that supports the Oracle Purchasing "POXAGLST" Oracle Reports executable, an XML Publisher (BI Publisher) report used to produce an approved supplier list (ASL) listing. The package encapsulates the report-level logic that Oracle Reports requires: initialization before the report runs, cleanup after it completes, and derived values for the report layout. Its principal role is to translate stored lookup codes into the displayed (translated) descriptions that appear on the report output, to derive the SQL ORDER BY clause for the query, and to resolve the default material structure identifier needed by the report.

The package is a report-support package rather than a business API. It is generated from the report definition and is deployed under the APPS schema; the header comment ($Header: POXAGLSTB.pls 120.2 2008/01/05 ...) identifies it as a standard Oracle EBS source component. It is documented with an API classification of OTHER, consistent with its internal report-support nature.

Key Procedures and Functions

• BeforeReport — Runs once when the report is initiated. It resolves the user-entered sort parameter into a displayed value by querying PO_LOOKUP_CODES, assigns that value to P_orderby_displayed (the value the user searched for), and copies it to the report placeholder LP_ORDERBY_DISPLAYED. It performs the same translation for the active/inactive parameter and calls the internal initialization structure. This is the point at which the search term is populated.
• AfterReport — Performs report teardown. In this package body it is largely a no-op placeholder, returning TRUE after the Oracle Reports exit user-exit call has been reduced to a comment.
• orderby_clauseFormula — A formula function that returns the SQL ORDER BY expression based on the selected P_orderby value. It maps BUYER to the buyer name column, LOCATION to the location code column, and CATEGORY to the report parameter P_ORDERBY_CAT; the default fallback returns the buyer name column.
• get_p_struct_num — Resolves the default material structure identifier by querying MTL_DEFAULT_SETS_VIEW for the functional area (Purchasing) and assigns it to P_STRUCT_NUM. It returns TRUE on success and swallows errors by returning FALSE, allowing the report to continue with a null structure number.

Tables Accessed

• PO_LOOKUP_CODES — Read to convert lookup codes stored in report parameters into their translated display fields. Two lookup types are used: ACTIVE_INACTIVE for the active/inactive parameter and SRS ORDER BY for the sort parameter that drives P_orderby_displayed.
• MTL_DEFAULT_SETS_VIEW — Read to retrieve the structure_id for functional_area_id = 2 (Purchasing), populating P_STRUCT_NUM.

No insert, update, or delete activity is documented; the package is entirely read-only.

Usage Notes

The package is invoked automatically by the Oracle Reports runtime when the POXAGLST report is executed; it is not intended to be called directly by forms or custom code. The BeforeReport and AfterReport functions correspond to the report's Before Report and After Report triggers, and orderby_clauseFormula is referenced by a report query column or formula column. P_orderby_displayed is the package-level variable that exposes the user-friendly sort description to the report layout. Because the package relies on Oracle Reports user exits that have been commented out in favour of XML Publisher integration, it behaves as a thin parameter-resolution layer. In 12.1.1 and 12.2.2 the object remains in the APPS schema with the same signature; the ETRM metadata records no other packages depending on it.