Search Results set_of_books_name_p

Overview

IGC_IGCCYRPR_XMLP_PKG is an Oracle E-Business Suite (EBS) PL/SQL package body owned by the APPS schema. Its name follows the standard Oracle Reports XML Publisher (XMLP) generated-package naming convention, where the trailing _XMLP_PKG suffix identifies a wrapper package produced automatically for a Report Builder report that has been published as a BI Publisher / XML Publisher concurrent program. In this case the report is IGC_IGCCYRPR, which belongs to the Oracle iGrants (IGC) product family and, based on the use of ledger, currency, and operating unit terminology, is a financial reporting listing that prints values in the context of a specific ledger (formerly termed a "Set of Books") and a specific operating unit.

The package encapsulates the report trigger logic and the data items that a report template exposes as bind parameters. It is the bridge between the concurrent program's parameter form and the underlying General Ledger and HR foundation data: at run time it translates the user's ledger selection into a ledger name and functional currency, derives the operating unit name, and surfaces those values through accessor functions so the report layout can render them in headers and page frames. The package body is a straightforward XMLP wrapper with no business-critical procedural logic of its own beyond the before-report initialization.

Key Procedures and Functions

The package exposes eight documented procedures and functions, all of which conform to the XMLP wrapper contract (BOOLEAN return triggers plus VARCHAR2 accessor functions):

• BEFOREREPORT — The principal initialization routine. It stores the concurrent request identifier in P_CONC_REQUEST_ID via FND_GLOBAL.CONC_REQUEST_ID, calls GL_INFO.GL_GET_LEDGER_INFO to resolve the ledger/Set of Books ID supplied through P_SET_OF_BOOKS_ID into a chart of accounts ID, a ledger (set of books) name and a functional currency, then retrieves the operating unit name from HR_OPERATING_UNITS for P_ORG_ID. Error conditions are detected through the GL error buffer and reported via GL_MESSAGE.GET_MESSAGE before raising a generic application error.
• AFTERREPORT — Post-report trigger. Contains no processing and simply returns TRUE.
• AFTERPFORM — After-parameter-form trigger. Returns TRUE.
• BEFOREPFORM — Before-parameter-form trigger. Returns TRUE.
• BETWEENPAGE — Between-page trigger. Returns TRUE.
• SET_OF_BOOKS_NAME_P — Accessor function returning SET_OF_BOOKS_NAME, the ledger name assigned during BEFOREREPORT. This is the function surfaced to the report for the user's "set_of_books_name_p" search term.
• CURRENCY_CODE_P — Accessor function returning CURRENCY_CODE, the ledger's functional currency.
• ORG_NAME_P — Accessor function returning ORG_NAME, the operating unit name.

Tables Accessed

The only table explicitly referenced in the documented source is HR_OPERATING_UNITS, a standard HR foundation table, read to obtain the operating unit NAME for the organization identified by P_ORG_ID. Ledger information is not fetched directly by this package; it is retrieved indirectly through the GL API GL_INFO.GL_GET_LEDGER_INFO, which resolves the ledger name, chart of accounts, and functional currency from the General Ledger configuration. The ARGUMENTS and standard concurrent program views are accessed implicitly by the XMLP wrapper infrastructure but are not named in the package body.

Usage Notes

IGC_IGCCYRPR_XMLP_PKG is not intended to be called from custom code. It is invoked automatically by the Oracle Reports XML Publisher runtime when the IGC_IGCCYRPR concurrent program is executed. The runtime calls BEFOREPFORM, BEFOREREPORT, BETWEENPAGE, and AFTERREPORT in the standard report trigger sequence, then calls the three accessor functions to supply values to the report template. The package therefore only functions correctly when registered as the pl/sql package for the report in the concurrent program definition, and when valid ledger and operating unit values are passed through the report parameters. Because it is a generated wrapper, it should not be recompiled or patched independently of the report definition; regeneration through the Report Builder XML Publisher publishing process is the supported maintenance path.