Search Results gl_glxavtrb_xmlp_pkg




Overview
Explore in AI Chat

Overview

GL_GLXAVTRB_XMLP_PKG is an Oracle Applications (APPS) package body that supports the XML Publisher (BI Publisher) concurrent program known internally as GLXAVTRB. The suffix convention _XMLP_PKG is used throughout Oracle E-Business Suite 12.1.1 and 12.2.2 for the PL/SQL packages that back XML Publisher-based reports, and this package follows that convention. Its business purpose is to assemble and return runtime parameter values and balance figures for the report commonly identified as "Access Set Trial Balance" — a General Ledger trial balance report that restricts the data returned to a user-defined GL Access Set, combines period and quarter-to-date balances, and supports both functional and foreign (resulting) currency reporting.

The package is registered in the database as VALID and is owned by APPS. It is a reporting-support package rather than an application programming interface: it exposes no documented interface for third-party callers, and the ETRM metadata records it as referencing no downstream database objects that in turn reference it (referenced by 0 other packages).

Key Procedures and Functions

The metadata documents 33 procedures and functions. The most significant are:

  • BEFOREREPORT — the Before Report trigger, executed by the report engine prior to data retrieval; it initialises package-level globals and derives values that the report queries depend upon.
  • AFTERREPORTTRIGGER — the After Report trigger, used for post-report cleanup and finalisation logic.
  • PATD, QATD, YATD — period-to-date, quarter-to-date, and year-to-date balance helpers, providing the three cumulative-balance bases the trial balance can display.
  • END_BAL — returns the ending balance for the selected range of accounts and periods.
  • G_HEADERGROUPFILTER and G_DETAILGROUPFILTER — the XML Publisher group filters, validated by the data model engine to suppress header or detail group rows that should not be rendered.
  • Parameter accessors — WHERE_P, CURR_TYPE_P, WHERE_DAS_P, ACCESS_SET_NAME_P, STRUCT_NUM_P, RESULTING_CURRENCY_P, SELECT_BAL_P, SELECT_FLEXDATA_P, ORDERBY_P, PERIOD_NAME_P, PERIOD_START_DATE_P, QUARTER_START_DATE_P. Each of these is a standard Oracle XML Publisher "data source" function that surfaces a report parameter (or a value derived from one) to the report definition, controlling row filtering, currency type, account structure, drill-down access set, flexfield selection, ordering, and the period/quarter boundary dates.

Tables Accessed

The package reads from four documented tables (via APPS synonyms):

  • FND_CURRENCIES — currency validation and currency-type resolution for the resulting-currency parameter.
  • GL_ACCESS_SETS — the access set definition used to scope the accounts and balances returned to the user.
  • GL_DATE_PERIOD_MAP — maps accounting dates to periods, supporting the period-to-date and quarter-to-date computations in PATD, QATD, and YATD.
  • GL_PERIODS — the period calendar, supplying period names, period numbers, and start/end dates used by PERIOD_START_DATE_P, QUARTER_START_DATE_P, and the date-based balance logic.

Security enforcement is delegated to GL_ACCESS_SET_SECURITY_PKG, and user-facing messages are resolved through GL_MESSAGE. Standard and DBMS_STANDARD supply the PL/SQL environment.

Usage Notes

GL_GLXAVTRB_XMLP_PKG is invoked indirectly. In Oracle EBS release 12.1.1 and 12.2.2 the report is submitted as an XML Publisher concurrent program; the Oracle Reports/BI Publisher runtime executes the Before Report trigger (BEFOREREPORT) and the After Report trigger (AFTERREPORTTRIGGER), calls the parameter accessor functions to populate the XML data template, and calls the group filters while formatting output. Because the package is not referenced by any other database object, it should not be treated as a callable API for custom code; customisation should be limited to configuring the concurrent program definition, its parameters, and the associated XML Publisher template. Changes to the package body itself require the standard APPS customisation and patching discipline, and any modification risks conflicting with Oracle-supplied patches to GLXAVTRB.