Search Results c_postable_summary_labelformul

Overview

IGI_IGIRRTRH_XMLP_PKG is an Oracle Application Object Library (AOL) report package that supports the XML Publisher (BI Publisher) concurrent program associated with the IGI Receiving Reporting Transaction History report in Oracle E-Business Suite. The package is owned by APPS and classified as OTHER within the ETRM metadata for releases 12.1.1 and 12.2.2. Its primary function is to encapsulate the runtime parameters, bind variables, and calculated values required by the underlying SQL query and the corresponding XML report template. The package defines a set of public constants, date and character substitution variables, and lookup-derived values that allow the concurrent program to render a transactional history report with flexible filtering on general ledger dates, transaction dates, currencies, company segments, invoice types, and transaction types.

The package source header, dated 2008/07/29 under version 120.0.12010000.1, indicates a long-standing Oracle internal component. It contains 79 documented procedures and functions in total, reflecting the typical structure of an Oracle Reports or XML Publisher integration package where every formula column and user parameter is represented as a coded unit.

Key Procedures and Functions

The documented procedures and functions include the standard report lifecycle callbacks BEFOREREPORT, AFTERREPORT, and AFTERPFORM. BEFOREREPORT and AFTERPFORM are invoked by the Oracle Reports engine to initialize variables and prepare the data model before the main query executes, while AFTERREPORT performs post-query cleanup and final formatting.

A large group of functions represents XML template formula columns: REPORT_NAMEFORMULA, C_COMPANY_SUMMARY_LABELFORMULA, C_POSTABLE_SUMMARY_LABELFORMUL, C_CURRENCY_SUMMARY_LABELFORMUL, C_CLASS_SUMMARY_LABELFORMULA, and C_DATA_NOT_FOUNDFORMULA. These return display strings used as labels, section headers, and conditional "no data found" messages in the XML output. D_COMPANYFORMULA and INVOICE_CONSFORMULA similarly derive calculated company and invoice consolidation values.

The lookup and display helpers include AR_LOOKUP, GET_LOOKUP_MEANING, GET_BOILER_PLATES, SET_DISPLAY_FOR_CORE, and SET_DISPLAY_FOR_GOV. AR_LOOKUP and GET_LOOKUP_MEANING resolve Oracle Receivables and FND lookup codes into their user-facing meanings, which is directly relevant to the "fnd_message" search context because FND message and lookup retrieval mechanisms are commonly used to present translated or descriptive text. GET_BOILER_PLATES retrieves standard report boilerplate text, while SET_DISPLAY_FOR_CORE and SET_DISPLAY_FOR_GOV adapt report display behavior for the core industry versus public sector (government) variants of the report.

The remaining documented units include parameter accessor functions such as RP_COMPANY_NAME_P, RP_REPORT_NAME_P, RP_DATA_FOUND_P, and RP_YES_P, which expose internal report values to the XML template.

Tables Accessed

The package references three tables through APPS synonyms: FND_CONCURRENT_PROGRAMS_TL, FND_CONCURRENT_REQUESTS, and RA_CUSTOMER_TRX. FND_CONCURRENT_PROGRAMS_TL supplies the translated concurrent program and report name, supporting REPORT_NAMEFORMULA and RP_REPORT_NAME_P. FND_CONCURRENT_REQUESTS is queried for the concurrent request identifier and its associated execution metadata, which is used to associate the report run with its parameters. RA_CUSTOMER_TRX is the primary transactional source, providing invoice, transaction number, currency, and date columns that underlie the reporting query and the various currency, date, and class summary calculations.

Usage Notes

IGI_IGIRRTRH_XMLP_PKG is not intended to be called directly by custom applications. It is invoked by the Oracle Reports/BI Publisher runtime host when the corresponding concurrent program is submitted from the Submit Requests form or the relevant Receiving or Payables responsibility. The package is not referenced by any other database package, as confirmed by the "Referenced by 0 other packages" metadata. Developers extending the report should create their own wrapper packages rather than modifying this AOL-owned object, and should use the FND_MESSAGE and FND lookup APIs when adding message or lookup handling consistent with the standard implementation.