Results for “igi_igirrtrh_xmlp_pkg”

32 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.IGI_IGIRRTRH_XMLP_PKG package body is the server-side PL/SQL component associated with an Oracle EBS XML Publisher (BI Publisher) concurrent report in the IGI (Oracle Financials Intelligence / Public Sector) application family. The suffix _XMLP_PKG identifies it as the packaged logic generated for a report definition registered in the XML Publisher data model. Its principal role is to prepare report-level parameters, derive boilerplate and summary text, and compute dynamic SQL fragments before the report data source executes.

The package is classified as an OTHER API in the ETRM repository, meaning it is not a formally published integration API. It is intended for internal use by the report itself rather than by external callers. Its functions are strongly tied to runtime parameter values entered by the user at the concurrent program submission screen — for example ordering options, company segment ranges, and GL/transaction date ranges — which are translated into internal variables used by the underlying query.

Key Procedures and Functions

The package exposes 79 documented procedures and functions. The most significant include:

Tables Accessed

The package reads from the following tables via APPS synonyms:

  • RA_CUSTOMER_TRX — Transaction header data used to source invoice and credit memo information displayed on the report.
  • FND_CONCURRENT_REQUESTS — Retrieves current request identifiers and runtime context for the concurrent program executing the report.
  • FND_CONCURRENT_PROGRAMS_TL — Provides the translated name of the concurrent program for use in the report header.

Additional joins to AR payment schedules and consolidated invoice tables are constructed dynamically in BEFOREREPORT when the billing-number profile is enabled.

Usage Notes

This package is invoked automatically by the XML Publisher engine when the corresponding concurrent program is run. It is not intended to be called from forms or custom PL/SQL; doing so would bypass the report framework and could produce inconsistent results. It is referenced by zero other packages, confirming its role as a self-contained report support unit. Because it manipulates profile options and message lookups, its behavior may vary by instance configuration (for example, the AR_SHOW_BILLING_NUMBER profile or the Government versus core edition setting). It should not be modified without equivalent functional testing, since the report layout expects the specific parameters, summary labels, and boilerplate text it produces.