Search Results reporting_curr

Overview

APPS.GL_GLXAVADT_XMLP_PKG is the supporting PL/SQL package body for an Oracle General Ledger XML Publisher (BI Publisher) concurrent program report. The package name follows the EBS XML Publisher convention where the suffix "XMLP_PKG" identifies the server-side package that supplies runtime data, parameters, and formulas to a report definition registered against an XML template. In this case the "GLXAVADT" report belongs to the General Ledger product and is associated with an account analysis or daily activity style inquiry that resolves balances for a specific ledger, access set, and period context.

Its central business purpose is parameter resolution and report initialization. The package reads ledger and access set definitions, derives the accounting period, quarter, and year that correspond to a user-supplied reporting date, and then computes derived report values such as the opening balance, activity amounts, and last end-of-day figures that the XML template renders. It is an "OTHER" classification package, meaning it is not a published public API but an internal, report-specific implementation owned by APPS.

Key Procedures and Functions

The documented package exposes 29 procedures and functions. The most significant include:

• BEFOREREPORT — the report initialization routine. It validates the access set, populates global package variables including ACCESS_SET_NAME, STRUCT_NUM, PERIOD_SET_NAME_1, and PERIOD_TYPE_1, and invokes period derivation logic. The source excerpt confirms it calls GL_GET_PERIOD_INFO and validates the returned error buffer.
• GL_GET_PERIOD_INFO — resolves the dollar period year, quarter number, and period number for a given ledger and reporting date.
• GL_GET_FIRST_DATE — returns the start date and start period name for the calculated period, using the ledger, balance type, year, quarter, and period number as inputs. This is the routine most closely associated with the user's search term.
• OPENING_BALFORMULA, LAST_CCIDFORMULA, DAILY_ACTIVITYFORMULA — XML Publisher formula columns that compute opening balance, last CCID, and daily activity amounts for display in the template.
• AFTERREPORT — the closure routine for the report run.
• Structed filter and parameter accessors such as G_BALANCING_SEGGROUPFILTER, G_OPENING_BALGROUPFILTER, LAST_EOD_P, STRUCT_NUM_P, LEDGER_NAME_P, PERIOD_SET_NAME_P, PERIOD_YEAR_P, QUARTER_NUM_P, PERIOD_NUM_P, REPORTING_CURR_P, START_DATE_P, START_PERIOD_NAME_P, and SELECT_BAL_P — these provide read access to report parameters and computed globals for the template and for the SELECT_BAL cursor logic.

Tables Accessed

The package reads from the following tables through APPS synonyms, all within the GL schema:

• GL_ACCESS_SETS — retrieves the access set name, chart of accounts ID, period set name, and accounted period type used to seed the report context.
• GL_PERIOD_STATUSES — used for period and quarter derivation in conjunction with GL_GET_PERIOD_INFO.
• GL_DATE_PERIOD_MAP — maps reporting dates to accounting periods, supporting the first-date and period-info calculations.
• GL_LEDGERS — supplies ledger name and currency context.
• GL_BALANCES — provides actual and budget balance amounts rendered by the opening balance, activity, and end-of-day formulas.

Usage Notes

This package is invoked exclusively by the XML Publisher concurrent program that owns the GL_GLXAVADT report definition. It is not intended for direct calls from forms or custom code, and the metadata records zero packages referencing it. Oracle EBS 12.1.1 and 12.2.2 deployments rely on the XML Publisher engine to call BEFOREREPORT and AFTERREPORT automatically, while formula columns invoke the *_FORMULA routines during template rendering.

The GL_GET_FIRST_DATE routine, which prompted the search, is a private helper rather than a documented public API. Its signature is derived from the commented call in BEFOREREPORT and takes ledger ID, balance type, period year, quarter number, and period number as inputs to return the first date and period name. Because it is an internal routine, it should not be referenced from external code; behavior and signature are subject to change with patches and are not part of Oracle's supported API surface.