Search Results ar_raxsol_xmlp_pkg




Overview
Explore in AI Chat

Overview

APPS.AR_RAXSOL_XMLP_PKG is a server-side PL/SQL package body that supports the XML Publisher (BI Publisher) concurrent report known internally as "RAXSOL" in the Oracle Receivables module. In Oracle EBS 12.1.1 and 12.2.2, the "XMLP" suffix identifies a package that is generated by or associated with the XML Publisher report definition, and it encapsulates the report-specific data logic, parameter handling, and output formatting rules that the concurrent program layer invokes at runtime. Its status is recorded as VALID in the ETRM 12.2.2 metadata. Functionally, RAXSOL relates to the Statement of Account / customer invoice statement reporting process in Receivables, where the report assembles customer transaction balances, invoice details, ageing information, and remittance-level boiler plate text for printing or delivery to customers. The package is classified as OTHER rather than as a public or private API, meaning it is an internal implementation object and not part of Oracle's supported extension surface.

Key Procedures and Functions

The package exposes 28 documented procedures and functions, the majority of which are formula functions referenced from the XML Publisher template. Report lifecycle procedures include BEFOREREPORT and AFTERREPORT, which execute before and after the report query to initialize and finalize report state. REPORT_NAMEFORMULA and C_LAST_INVOICE_NUMBERFORMULA return derived values used in the report header and transaction sections. C_GET_MEANINGFORMULA and GET_LOOKUP_MEANING resolve lookup codes into their displayed meanings. C_DATA_NOT_FOUNDFORMULA produces the "no data found" indicator when the query returns no rows. RP_SYSDATEFORMULA supplies the system date to the template. GET_BOILER_PLATES retrieves standard boiler plate text for the statement. SET_DISPLAY_FOR_CORE and SET_DISPLAY_FOR_GOV provide conditional display switches, apparently toggling formatting for commercial versus government customer variants. The remaining RP_* functions — RP_COMPANY_NAME_P, RP_REPORT_NAME_P, RP_DATA_FOUND_P, RP_ID_P, RP_NONE_P, RP_SEGMENT_P, RP_NUMBER_P, RP_VALUE_P, and RP_YES_P — act as parameter and value helpers consumed by the XML template at render time.

Tables Accessed

The metadata documents three table dependencies accessed through APPS synonyms: FND_CONCURRENT_REQUESTS, RA_CUSTOMER_TRX, and DUAL. FND_CONCURRENT_REQUESTS is queried to resolve concurrent request context such as request identifiers and parameter values at execution time. RA_CUSTOMER_TRX is the core Receivables transaction table and is read to supply invoice-level and transaction-level statement data. DUAL is used for single-row expressions. The dependency list additionally names AR_LOOKUPS and FND_LOOKUPS for lookup meaning resolution, AR_RAXSOL_XMLP_PKG itself, FND_CONCURRENT_PROGRAMS_VL, FND_INSTALLATION, and the SYS STANDARD package, indicating standard utility and concurrent program metadata references.

Usage Notes

AR_RAXSOL_XMLP_PKG is not referenced by any other database object, confirming that it is invoked by the concurrent manager and XML Publisher engine rather than by other PL/SQL packages. Typical invocation is through the Receivables concurrent program associated with the statement report; the XML Publisher data template calls the RP_* and formula functions directly within the report definition. Because the package is not a supported API, customizations should not call it directly. Developers extending the report should instead copy the report definition or create a custom XML Publisher template that references supported views such as RA_CUSTOMER_TRX. Behaviour is consistent across 12.1.1 and 12.2.2, though the 12.2.x Online Patching editioning model means the package body resides in the APPS schema and is editioned accordingly.