Search Results ap_apxxpxpl_xmlp_pkg




Overview
Explore in AI Chat

Overview

APPS.AP_APXXPXPL_XMLP_PKG is the generated PL/SQL package specification that backs the Oracle E-Business Suite concurrent program associated with the AP_APXXPXPL XML Publisher (BI Publisher) report in Oracle Payables. The package is compiled with AUTHID CURRENT_USER and follows the standard Oracle Reports/XML Publisher integration pattern introduced in Release 12, in which every report template is paired with an automatically generated package (suffix _XMLP_PKG) that encapsulates the report's user parameters, its NLS strings, and the logic executed in the report's BeforeReport and AfterReport triggers. The header comment (APXXPXPLS.pls 120.0, dated 2007) confirms its origin as a seeded, versioned artifact maintained by Oracle development and shipped with the Payables product.

The package's public surface is split into three logical groups: global report parameters bound to the concurrent program's parameter form, cached "C_" global variables populated at runtime, and accessor functions (the _p suffix) that expose those globals. The user's search term, c_report_start_date_p, corresponds to the accessor function returning the value of the global C_REPORT_START_DATE, a DATE variable declared at line 15 of the specification. This value is typically derived from system parameters or the report's effective date range and is consumed by the report query to bound transactions included in the output.

Key Procedures and Functions

Tables Accessed

The only documented table reference is AP_SYSTEM_PARAMETERS, accessed via its APPS synonym. This table supplies the base (functional) currency, precision, minimum accounting unit, chart of accounts identifier, and set of books context required by the report. All other data is supplied through concurrent program parameters (P_CONC_REQUEST_ID, P_SET_OF_BOOKS_ID, P_EFFECTIVE_DATE, P_ACTIVE_TYPE, and related constants) rather than through direct table reads by this package.

Usage Notes

This package is never invoked directly by application code. It is loaded automatically by the Oracle Reports/BI Publisher runtime when the associated Payables concurrent program is submitted, and its BeforeReport/AfterReport functions fire as report lifecycle triggers. Because it is classified as OTHER (not a public API), Oracle does not guarantee its interface across patches; customizations should not call it directly, and any client extension should be limited to wrapping the underlying concurrent program. The package is referenced by zero other packages, reinforcing its role as an internal report-runtime artifact. In 12.2.2 the same generated pattern applies, though customers should rely on the ETRM-documented signature rather than the source header, which reflects the original 12.1.x-era file.