Search Results rp_number_p

Overview

AR_RAXSOL_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. It supports the Oracle Receivables sales order detail or statement-style XML Publisher (XMLP) report, whose concurrent execution logic is encapsulated within this generated package. The package follows the standard Oracle Reports-to-XML-Publisher conversion pattern: Oracle Reports initially generated a library of summary and formula functions, and the converted XML Publisher concurrent program continues to use the same package shell. The package encapsulates report-level bind variables, formatted display strings, and helper functions that shape the data returned by the underlying SQL query before it is rendered by the XML template.

The package is classified as OTHER in the ETRM metadata, indicating it is not a public API and is intended strictly for internal use by the concurrent program that owns it. The naming convention RAXSOL reflects the Receivables "sales order" family of reports. References to the user search term "rp_yes_p" correspond to the getter function RP_YES_P, which returns the localized value of the "Yes" label used in the report layout for indicator columns.

Key Procedures and Functions

• BEFOREREPORT / AFTERREPORT — Standard XML Publisher report-level triggers. BEFORE establishes session context; AFTER performs cleanup.
• REPORT_NAMEFORMULA — Derives the printed report title, optionally incorporating the operating unit or company name.
• C_GET_MEANINGFORMULA — Resolves a lookup meaning for a code, used to render descriptive text in the report.
• C_LAST_INVOICE_NUMBERFORMULA — Retrieves the last invoice number for a given transaction numbering scheme and batch source.
• RP_SYSDATEFORMULA — Returns the current system date formatted for display.
• C_DATA_NOT_FOUNDFORMULA — Evaluates whether the data set is empty so that the appropriate "no data" message can be printed.
• GET_LOOKUP_MEANING — Procedure that wraps FND_LOOKUPS lookup-code translation.
• GET_BOILER_PLATES — Populates boilerplate text and static label variables used by the report template.
• SET_DISPLAY_FOR_CORE / SET_DISPLAY_FOR_GOV — Conditionally control visibility of fields depending on whether the deployment is Core or Government (public sector) reporting.
• RP_*_P getters — Accessor 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, RP_YES_P, and related) return the corresponding package variables to the XML template. RP_YES_P specifically supplies the localized "Yes" string for boolean indicator columns.

Tables Accessed

• FND_CONCURRENT_REQUESTS — Read to seed P_CONC_REQUEST_ID, allowing the report to identify the current concurrent request and its parameters.
• RA_CUSTOMER_TRX — The primary transactional source supplying invoice and transaction data rendered by the report.
• DUAL — Used for scalar expressions such as the system date.

Usage Notes

AR_RAXSOL_XMLP_PKG is invoked exclusively by its owning concurrent program; the ETRM metadata records zero inbound references from other packages. It is not a callable public API and must not be invoked directly from custom code. Customizations should be limited to the XML template or the underlying SQL, preserving the getter contract (RP_YES_P, RP_REPORT_NAME_P, and similar) that the template references. Because field visibility differs between Core and Government deployments via SET_DISPLAY_FOR_CORE and SET_DISPLAY_FOR_GOV, template changes should account for both modes. Access to the package is restricted to APPS; any extension should be implemented in a custom package shadowing the same signature rather than modifying the delivered source.