Search Results g_sub_classgroupfilter




Overview

APPS.GL_GLYRLBGE_XMLP_PKG is a generated PL/SQL package that supports the Oracle General Ledger "Year-End Closing Balances" style XML Publisher report. In Oracle EBS 12.1.1 and 12.2.2, Oracle Reports and XML Publisher concurrent programs are implemented as PL/SQL packages that begin with a _XMLP_PKG or report-package suffix. The package encapsulates the report's parameters, session-level globals, data-fetch logic, and formula columns that the report layout invokes at runtime.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling APPS schema rather than the package owner. Its header exposes numerous public variables (for example P_LEDGER_ID, P_PERIOD_NAME, P_START_ACCOUNT, P_END_ACCOUNT, P_COMPANY, P_CURRENCY_CODE, P_CONC_REQUEST_ID) that hold concurrent-program parameters and derived report values. Several of these globals, including BEGIN_DR_SELECT, END_DR_SELECT, PER_DR_SELECT, BEGIN_CR_SELECT, END_CR_SELECT, PER_CR_SELECT, ACCOUNTING_SEGMENT_WHERE, and BALANCING_SEGMENT_WHERE, are initialized to the neutral predicate '1' or '1 = 1' and are later rewritten by the BeforeReport trigger to build dynamic WHERE clauses.

Key Procedures and Functions

The documented 42 routines fall into several categories:

Tables Accessed

According to the ETRM metadata, the package references the following APPS synonyms:

  • GL_LEDGERS — Source of ledger name, chart of accounts, and currency attributes used by GL_GET_LEDGER_INFO and BeforeReport.
  • GL_PERIOD_STATUSES — Provides period status and first-period information used by GL_GET_FIRST_PERIOD and the report query.
  • GL_ACCESS_SETS — Enables access-set security filtering so users see only authorized ledgers and balancing segments.

Usage Notes

This package is not called directly by end users or custom code; it is invoked implicitly when the associated XML Publisher/Reports concurrent program is submitted from the General Ledger responsibility or from the Submit Request form. The concurrent manager passes the request ID and parameters, then Oracle Reports or XML Publisher instantiates the package and invokes BEFOREREPORT followed by the formula functions during layout rendering. Because the package is generated by Oracle Reports, customizations should be limited to the report definition rather than the package body; modifying it directly risks being overwritten during patching. The use of AUTHID CURRENT_USER means the package relies on the APPS schema synonyms and the caller's access privileges, reinforcing the importance of correct responsibility and access-set configuration.