Search Results igi_igirtaud_xmlp_pkg

Overview

IGI_IGIRTAUD_XMLP_PKG is an Oracle Application Object Library (AOL) report helper package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its name follows the standard <report_short_name>_XMLP_PKG convention used by the Oracle Reports-to-XML Publisher migration infrastructure, in which a small wrapper package is generated to hold the bind parameters, session-level globals, and pre/post processing hooks required by an XML Publisher (BI Publisher) report definition.

The prefix "IGI" identifies the object as part of the IGI product family, which provides Oracle's public-sector and internal-control reporting components (IGI refers to the Grants Accounting / IGIRTA-family reporting suite deployed against the ETRM reporting framework). The report short name embedded in the package name is "IGIRTAUD", corresponding to an audit-oriented report template whose data is typically retrieved through a separate XML data definition or SQL query underlying the concurrent program. The package itself is therefore a coordination shell rather than a business-logic engine: it exposes the runtime variables that the report template references and the two AOL lifecycle callbacks that bracket report execution.

The header comment records a single version, 120.0.12010000.1, dated 2008/07/29, indicating that the package has been carried forward unchanged through the 12.1.1 and 12.2.2 code lines. It is classified in the ETRM metadata as API classification OTHER, meaning it is not part of Oracle's published PL/SQL API surface and should not be called directly by customer extensions.

Key Procedures and Functions

Two functions are documented, both conforming to the AOL report callback signature that returns BOOLEAN and is invoked automatically by the Oracle Reports / XML Publisher runtime rather than by application code.

• BEFOREREPORT — The pre-report initialization hook. It executes once at the start of report execution to populate the package-level globals declared in the specification, most notably the SOB (set of books) identifier, the low and high date bounds, the concurrent request ID, and the customer identifier, and to validate or default those values before the report query is fired. It is the standard location for converting the character date parameters into the canonical DATE forms used internally, which is why the specification declares both the VARCHAR2 parameter variables and the corresponding DATE conversion variables.
• AFTERREPORT — The post-report cleanup hook, executed once after the report output has been produced. It is used to release or reset any session state established by BEFOREREPORT and to return control to the concurrent manager with the appropriate completion status.

Tables Accessed

The ETRM metadata records no directly referenced tables for this package through APPS synonyms. This is consistent with the design pattern: the package contains no SQL DML of its own. All database access for the report is performed by the underlying XML Publisher data template or the generated report query, which reads the audit-related source tables using the bind values (SOB ID, date range, customer ID) exposed by this package. The absence of table references also means the package cannot be used as a data source in its own right.

Usage Notes

IGI_IGIRTAUD_XMLP_PKG is invoked indirectly. It is bound to the concurrent program definition registered for the IGIRTAUD report, and the Oracle Reports server or XML Publisher engine calls BEFOREREPORT and AFTERREPORT automatically as part of the submission lifecycle. Developers will encounter the package primarily when troubleshooting report parameter handling — in particular the cp_date_low and cp_date_high canonical date globals, which are the internal DATE counterparts of the user-entered p_date_low and p_date_high character values.

Because it is classified as OTHER and is not a published API, direct invocation from custom code is not supported. The package is also not referenced by any other package in the ETRM inventory (zero inbound references), confirming that its only consumer is the report runtime. Any modification must be performed through the supported patching mechanism, and the header version marker should be preserved for patch lineage tracking. When diagnosing date-range errors on this report, the values of CP_DATE_LOW and CP_DATE_HIGH after BEFOREREPORT has executed are the authoritative indicator of what the report query actually received, independent of what the user typed into the concurrent program parameter form.