Search Results p_invoice_type_low

Overview

AR_ARXPDI_XMLP_PKG is the generated report package body behind the Oracle Receivables "Past Due Invoice" XML Publisher report (short name ARXPDI). It is an internal support package that the Oracle Reports XML Publisher engine invokes at runtime through the standard SRW-style entry points, rather than an API intended for direct application calls. Its responsibilities span three areas: initializing global and profile-driven state, resolving sort and label lookups, and dynamically assembling SQL fragments (the show billing number column, table and WHERE clause text) that the report's data model consumes. Because the report allows the user to filter by invoice type, the package exposes parameters such as p_invoice_type_low, used to constrain which invoice types are included in the extract.

The package header carries a nonship source header ($Header: ARXPDIB.pls 120.1), confirming it is part of the sealed Oracle EBS 12.1.1 / 12.2.2 code line. Business users trigger it only implicitly by running the Past Due Invoice report; developers interact with it solely when debugging or extending that report.

Key Procedures and Functions

• BEFOREREPORT — The principal initialization routine. It captures the concurrent request ID (P_CONC_REQUEST_ID), reads the AR_SHOW_BILLING_NUMBER profile option via AR_SETUP.value, calls GET_BOILER_PLATES, resolves the "As Of" message text and lookup meanings, and, depending on the profile value, either supplies literal NULL placeholders or joins the ar_cons_inv table so the consolidated billing number appears. It returns TRUE.
• AFTERREPORT — The symmetric teardown hook; returns TRUE after the report completes.
• REPORT_NAMEFORMULA — Builds the report title from the company name and the parameter values (including invoice type and amount ranges), substituting blanks for NULL bounds and populating the rp_past_days_from / rp_past_days_to globals. Related formula functions include AFTERPFORM, C_TEMP_SALFORMULA, C_DATA_FOUNDFORMULA, C_CUSTOM_CHECKFORMULA, INVOICE_NUMBER_CONSFORMULA, CF_ORDER_BYFORMULA, and CF_SALESPERSONFORMULA, which control dynamic sort order, the consolidated invoice number display, and conditional row visibility.
• GET_BOILER_PLATES — Loads boilerplate text used by the layout.
• GET_LOOKUP_MEANING — Wrapper that returns the meaning for a given lookup code, used to label the Balance Due, Customer, and Salesperson sort options.
• SET_DISPLAY_FOR_CORE / SET_DISPLAY_FOR_GOV — Toggle display behavior for core and government (federal) variants of the report.
• ACCT_BAL_APROMPT_P, RP_OLD_CURR_P, RP_CURR_CHECK_P, RP_OLD_CUSTOMER_P, RP_CUST_CHECK_P, RP_COMPANY_NAME_P — Anchor and validation procedures for the runtime parameters (account balance prompt, old and current currency checks, old customer and customer validation, company name), which enforce the entered values before the query executes.

Tables Accessed

The only table documented as a direct dependency through APPS synonyms is FND_CONCURRENT_REQUESTS, read to retrieve concurrent program context information during initialization. All other data, such as the consolidated invoice attributes and the profile option AR_SHOW_BILLING_NUMBER, is obtained through supporting APIs (AR_SETUP, ARPT_SQL_FUNC_UTIL, FND_GLOBAL, FND_MESSAGE) and through the report's own SQL query against the Receivables transaction tables, which are defined in the report data model rather than referenced by name inside this package body.

Usage Notes

The package is invoked automatically whenever the ARXPDI report is submitted, either from the Receivables responsibility's standard report menu or as part of an accounting/reporting cycle. It is not called by any other PL/SQL package, and the metadata records zero inbound package dependencies, confirming its role as a leaf, report-bound unit.

Parameters such as p_invoice_type_low are supplied by the report's parameter form and are consumed by the generated WHERE-clause logic and by REPORT_NAMEFORMULA and the parameter-validation procedures. Customizations should not modify the package directly; instead they should be layered through Oracle Reports/XML Publisher template or query changes, since direct edits are overwritten by patching. The AR_SHOW_BILLING_NUMBER profile option at site or responsibility level is the documented mechanism for controlling whether the consolidated billing number column is rendered.