Search Results g_invoicegroupfilter




Overview

APPS.AP_APXPPHIS_XMLP_PKG is a PL/SQL package that supports the Oracle Payables historical payments report, internally associated with the APXPPHIS XML Publisher (BI Publisher) concurrent program. The package encapsulates the report-level logic required to prepare runtime data, resolve user-entered report parameters, derive language-dependent (NLS) strings, and return control values to the report layout engine before and after report execution. It forms the technical backbone behind the "Payments History" style output that lists payment records for a given set of books, vendor, and payment date range, with optional detail printing.

The package is owned by APPS and is classified under the OTHER API classification, indicating it is an internal implementation object rather than a supported public API. It is not referenced by any other package, confirming its role as a leaf-level report support unit invoked directly by the Oracle Reports / XML Publisher runtime rather than by application code.

Key Procedures and Functions

The documented surface of the package consists of 24 procedures and functions. The principal logic is contained in the following:

Tables Accessed

The package reads AP_SYSTEM_PARAMETERS through the APPS synonym. This table supplies system-level Payables configuration, most notably the Set of Books (ledger) identifier and associated currency and precision defaults that the report requires to derive base currency context and to constrain payment data to the correct accounting books. No other tables are documented as being directly accessed by the package; the primary payment data is retrieved by the underlying report query rather than by package code.

Usage Notes

AP_APXPPHIS_XMLP_PKG is invoked automatically when the APXPPHIS concurrent program (Payments History report) is submitted from the Payables responsibility or scheduled through the concurrent manager. The BeforeReport trigger calls the initialization, cover-page, NLS, flexfield, and run-time functions, while the C_*_P getter functions are called from the report template to render values. Because the package is classified OTHER and exposes no documented public API, custom code should not call it directly; the supported extension approach is to modify or wrap the concurrent program definition and report template, or to use supported Payables APIs and views for custom reporting. Any customization should account for the base-currency and set-of-books dependencies resolved from AP_SYSTEM_PARAMETERS, since these determine precision and formatting in the output.