Search Results g_headergroupfilter

Overview

GL_GLXAVTRB_XMLP_PKG is the generated PL/SQL package that supports the Oracle General Ledger XML Publisher (BI Publisher) report commonly associated with the "GLXAVTRB" concurrent program. In Oracle EBS 12.1.1 and 12.2.2 the XMLP report template is registered against a concurrent program, and the corresponding _XMLP_PKG package is auto-generated to bind the report's data model parameters, build the runtime WHERE clauses, and supply derived values (such as period start/end dates) that the report layout expects. Its business function is therefore to prepare and expose the selection criteria used by an Account Analysis / Trial Balance-style report that reads General Ledger balances and account flexfield segment values, and to format the concatenated account segments for display in the report output.

The package is classified as OTHER (a report support package rather than a public API) and is owned by APPS. It is not referenced by any other package, confirming its role as a leaf-level, report-specific component invoked only through the concurrent program framework.

Key Procedures and Functions

ETRM documents 33 procedures and functions. The principal entries include:

• BEFOREREPORT — the pre-report trigger that initializes the package state and prepares session context before the data query runs.
• AFTERREPORTTRIGGER — the post-report trigger executed after the data model completes.
• G_HEADERGROUPFILTER (and G_DETAILGROUPFILTER) — group filter routines that return the filter expressions applied to the header (and detail) grouping levels of the report, allowing the layout to suppress or restrict repeating groups.
• 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 — accessor functions that expose the package's global variables (heavily used as bind parameters in the XML data template), covering the runtime WHERE clause, currency type, data access set, structure/segment number, resulting currency, balance and flexfield SELECT lists, ORDER BY clause, period name, and the derived period/quarter start dates.
• PATD, QATD, YATD, END_BAL — helper routines that compute period dates and ending balance values used in the report calculations.

The package declares public globals including P_REPORTING_DATE, P_ENTERED_CURRENCY, P_CURRENCY_TYPE, P_CONC_REQUEST_ID, P_MAX_FLEX, P_MIN_FLEX, P_LEDGER_CURRENCY, P_ACCESS_SET_ID and P_LEDGER_ID, along with defaulted lexical variables such as WHERE_lexical, CURR_TYPE ('dbs.currency_type = ''E'''), SELECT_BAL and SELECT_FLEXDATA (which concatenate segment1 through segment30 with newline separators), and ORDERBY ('cc.segment1').

Tables Accessed

The package reads the following tables through APPS synonyms:

• FND_CURRENCIES — currency information to resolve entered and ledger currency definitions.
• GL_ACCESS_SETS — data access set definition, supporting the access set name and ID parameters.
• GL_PERIODS — period definitions used to derive period names and period/quarter start dates.
• GL_DATE_PERIOD_MAP — mapping between accounting dates and periods, used to translate the reporting date into the correct period context.

Balance and flexfield data are read by the report's own data model query rather than directly within the package body.

Usage Notes

This package is invoked indirectly. A user runs the GLXAVTRB concurrent program from the EBS Reports or General Ledger responsibility; the concurrent manager executes the program, which calls the XML Publisher report, which in turn calls the _XMLP_PKG routines to populate bind parameters and prepare the query. The package is specific to a single report and should not be called from custom code as a supported API. Because Oracle regenerates these packages when the corresponding XML Publisher data template is compiled, any direct customizations are overwritten during patching. The "g_headergroupfilter" search term refers to the G_HEADERGROUPFILTER routine, which is used solely within the report's group filtering logic and carries no external dependencies or documented callers.