Search Results gl_glyrljge_xmlp_pkg




Overview
Explore in AI Chat

Overview

APPS.GL_GLYRLJGE_XMLP_PKG is the package body that backs the Oracle EBS General Ledger "Journal Entries Report" (report short name GLYRLJGE), a concurrent report that lists detailed journal entry lines for a selected ledger, period range, and data access set. The package is generated in the standard Oracle Reports XML Publisher (XMLP) pattern, where the report's PL/SQL library is built as a package body containing the report's BeforeReport and AfterReport triggers, group filters, and formula columns. Its principal business purpose in both 12.1.1 and 12.2.2 is to resolve the runtime reporting context — ledger, period range, chart of accounts, and data access security — and to hand that context to the report query at execution time.

The user's search term "c_access_where" refers directly to the package-level variable C_ACCESS_WHERE, which is central to this package's function. It is not a procedure or function; it is a package variable that holds the SQL predicate fragment generated by GL_ACCESS_SET_SECURITY_PKG.GET_SECURITY_CLAUSE and then prefixed with " AND " before being concatenated into the report's WHERE clause.

Key Procedures and Functions

The documented interface includes 36 procedures and functions. The most significant are:

Tables Accessed

The package reads from the following APPS synonyms:

  • GL_ACCESS_SETS — to validate P_ACCESS_SET_ID and obtain the access set name and chart of accounts ID.
  • GL_LEDGERS — to resolve ledger name, currency code, object type, consolidation flag, period set name, and accounted period type.
  • GL_PERIODS — to derive period start/end dates for the fiscal year and period-type resolution.
  • GL_SYSTEM_USAGES — to confirm the General Ledger application is enabled for the target ledger.
  • DUAL — for scalar evaluations in formula columns.

No writes are performed; the package is strictly read-only against reference data.

Usage Notes

GL_GLYRLJGE_XMLP_PKG is invoked exclusively through the Journal Entries Report concurrent program and the Oracle Reports runtime. Parameters typically include P_ACCESS_SET_ID, P_LEDGER_ID, P_START_PERIOD, P_END_PERIOD, and P_STRUCT_NUM. In 12.1.1 the report relies on the same access-set security package as in 12.2.2, so C_ACCESS_WHERE behaves consistently across releases. The package is referenced by zero other PL/SQL packages, meaning it is not exposed as a shared API and should not be called directly from custom code. Customizations must be applied through the underlying report definition (GLYRLJGE.rdf/.xml) rather than by modifying this generated package body, as it is regenerated whenever the report is recompiled or patched. The " AND " concatenation pattern on C_ACCESS_WHERE requires that the host query already contain at least one WHERE predicate; report query changes must preserve that assumption.