Search Results ar_arxaprcb_xmlp_pkg




Overview
Explore in AI Chat

Overview

APPS.AR_ARXAPRCB_XMLP_PKG is the generated PL/SQL package body that supports the Oracle Receivables "Automatic Receipt Batch Management Report" (ARXAPRCB), an XML Publisher–enabled concurrent program. In Oracle EBS 12.1.1 and 12.2.2, report logic for XML Publisher reports is encapsulated in packages whose names carry the _XMLP_PKG suffix. This package supplies the formula functions and parameter-handling logic consumed by the report template and by the Oracle Reports runtime bridge (SRW). It is classified as OTHER in ETRM and is referenced by no other packages, confirming its role as a leaf-level, report-specific artifact.

Key Procedures and Functions

The package exposes eleven documented program units. The following are the report formula functions:

The lifecycle and parameter functions are:

  • BEFOREREPORT — Initializes the runtime by capturing P_CONC_REQUEST_ID via FND_GLOBAL.CONC_REQUEST_ID. The FND SRWINIT user exit is present but commented out, consistent with the XML Publisher conversion.
  • AFTERREPORT — Companion teardown function; the FND SRWEXIT call is likewise commented out. Returns TRUE.
  • RP_COMPANY_NAME_P, RP_REPORT_NAME_P, RP_SUB_TITLE_P, RP_DATA_FOUND_P — Accessor/return functions for the package globals holding company name, report name, subtitle, and a data-found flag used by the report layout.

Tables Accessed

Three tables are documented, all read through APPS synonyms:

  • FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS_VL — joined in REPORT_NAMEFORMULA to translate the concurrent request into its program name for the report header.
  • AR_LOOKUPS — read by RP_DSP_STATUSFORMULA to convert the BATCH_APPLIED_STATUS lookup code into its display meaning.
  • AR_CASH_RECEIPT_HISTORY and AR_PAYMENT_SCHEDULES — underlying Receivables tables supplying receipt batch history and payment schedule detail for the report's amount and status calculations.

Usage Notes

This package is invoked indirectly, not by application forms or custom code. It executes when the Automatic Receipt Batch Management Report concurrent program is submitted, with Oracle Reports or the XML Publisher engine calling BEFOREREPORT at runtime start, the *_FORMULA functions as each layout field is evaluated, and AFTERREPORT at termination. Because it is generated and shipped with the report definition, it should not be modified directly; customizations belong in the report template or in a copy of the concurrent program. The absence of reverse dependencies means changes here carry localized impact only.