Search Results last_period_year

Overview

APPS.GL_GLRGNL_XMLP_PKG is the generated PL/SQL package body that implements the report logic behind the Oracle General Ledger "General Ledger Report" (short name GLRGNL), delivered in Oracle E-Business Suite 12.1.1 and 12.2.2. The package is classified as OTHER within ETRM and is owned by the APPS schema, one of the 51 documented procedures and functions that Oracle Reports automatically derives from the underlying XML Publisher/RDF report definition. Its primary business purpose is to support the rendering of journal line details for a specified ledger or ledger set, resolving the Data Access Set, the chart of accounts structure, the dispatch of reference columns, the actual/budget/encumbrance predicate, and the currency balancing logic used by the report query.

Unlike a conventional PL/SQL API, the package is not designed to be called directly by business users. The executable statements contained inside BEFOREREPORT, AFTERREPORT, and the numerous format trigger functions are invoked internally by the Oracle Reports runtime as the report executes. The trigger functions primarily perform conditional formatting and display decisions for individual columns and cells displayed on the printed output.

Key Procedures and Functions

The package exposes the following documented routines. Their names indicate their responsibilities within the report execution cycle.

• BEFOREREPORT / AFTERREPORT – Report-level triggers executed before and after the report body. BEFOREREPORT initializes the access set by selecting the access set name and chart of accounts ID and sets up the SELECT_REFERENCE and WHERE clauses according to the P_KIND, P_ACTUAL_FLAG, and P_CURRENCY_TYPE parameters.
• GL_GET_PERIOD_DATES – Function that resolves the start and end dates of a given accounting period, used to bracket the reporting range.
• GL_GET_EFF_PERIOD_NUM – Function that returns the effective period number for a given ledger and period, commonly used for period-to-date calculations.
• START_DATEFORMULA / END_DATEFORMULA, LAST_PERIOD_YEARFORMULA, START_EFF_PERIOD_NUMFORMULA – Format triggers that display the period start date, period end date, the ending period of the prior year, and the effective period number.
• DISP_ACTUAL_FLAGFORMULA / BUD_ENC_TYPE_NAMEFORMULA – Format triggers that display the actual/budget/encumbrance indicator and the corresponding budget or encumbrance type name.
• OLD_CCIDFORMULA, OLD_END_DRFORMULA, OLD_END_CRFORMULA, NEW_RECORDFORMULA, BAD_STARTFORMULA, BAD_ENDFORMULA, DISP_CRFORMULA – Format triggers that control printing of account code combinations, debit and credit running balances, and credit-only display logic, and flag malformed begin/end balance conditions.
• BEGIN_BALFORMULA, END_BALFORMULA, ACCOUNTED_BALFORMULA – Format triggers that display the beginning balance, ending balance, and accounted balance for each account.

Tables Accessed

The package reads from the following application tables via APPS synonyms:

• GL_ACCESS_SETS – Queried in BEFOREREPORT to retrieve the access set name and chart of accounts ID (STRUCT_NUM) for the requested P_ACCESS_SET_ID; invalid IDs raise application error -20101 with message GL_PLL_INVALID_DATA_ACCESS_SET.
• GL_LEDGERS – Used to resolve ledger attributes such as currency and chart of accounts.
• GL_LEDGER_SET_ASSIGNMENTS – Resolves the ledgers that belong to a ledger set when the report is run across multiple ledgers.
• GL_PERIOD_STATUSES – Provides period status and effective period information used by GL_GET_PERIOD_DATES and GL_GET_EFF_PERIOD_NUM.

Usage Notes

GL_GLRGNL_XMLP_PKG is not a public API and should not be invoked from custom code. It is executed automatically by the Oracle Reports engine when the GLRGNL report is submitted, either from the General Ledger responsibility or through concurrent program submission. Because the package body carries Oracle's standard "$Header: GLRGNLB.pls" identifier and the report runtime references srw built-ins, customers should treat it as a seeded, non-modifiable object. Customizations should instead be applied through the report definition, value sets, or by copying the report into a custom concurrent program. Note also that the package is referenced by no other packages, confirming its tightly scoped purpose within the GL reporting framework.