Results for “gl_period_name”

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:

• BEFOREREPORT — Runs prior to report execution. It initializes the summary label message via FND_MESSAGE, resolves the ordering parameter (P_ORDER_BY), builds company segment filter strings, conditionally appends billing-number columns based on the AR_SHOW_BILLING_NUMBER profile option, and calls GET_BOILER_PLATES to populate standardized header text.
• AFTERREPORT — Performs post-processing cleanup, historically invoking the FND SRWEXIT user exit in the Oracle Reports variant.
• REPORT_NAMEFORMULA — Builds the report title from functional currency, company name, and start/end date parameters.
• GET_BOILER_PLATES — Retrieves reusable boilerplate/minimal text used across the report layout.
• AR_LOOKUP, GET_LOOKUP_MEANING — Resolve Oracle Receivables lookup codes to their display meanings.
• SET_DISPLAY_FOR_CORE, SET_DISPLAY_FOR_GOV — Toggle display behavior depending on whether the instance is running core commercial or Government/Public Sector configuration.
• Summary-label and status formula functions (C_COMPANY_SUMMARY_LABELFORMULA, C_POSTABLE_SUMMARY_LABELFORMUL, C_CURRENCY_SUMMARY_LABELFORMUL, C_CLASS_SUMMARY_LABELFORMULA, C_DATA_NOT_FOUNDFORMULA) — return localized column headers and conditional text for report sections.
• Column formula functions (INVOICE_CONSFORMULA, D_COMPANYFORMULA) — format individual report columns.
• Runtime parameter holders (RP_COMPANY_NAME_P, RP_REPORT_NAME_P, RP_DATA_FOUND_P, RP_YES_P) — capture parameter and status values during execution.

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.