Search Results where_flex_range

Overview

GL_GLXAVADT_XMLP_PKG is the Oracle E-Business Suite PL/SQL package associated with the GLXAVADT XML Publisher concurrent program, the Daily Activity report for General Ledger. Its primary business function is to prepare the run-time parameters, derived date and period context, and dynamically constructed SQL fragments that the report's data model and template require before, during, and after execution. The package specification exposes a large number of package-level variables that mirror the report's concurrent program parameters, such as P_REPORTING_DATE, P_BALANCE_TYPE, P_LEDGER_ID, P_CONC_REQUEST_ID, P_ENTERED_CURRENCY, P_ACCESS_SET_ID, and P_CURRENCY_TYPE, together with derived values including START_DATE, START_PERIOD_NAME, QUARTER_NUM, PERIOD_NUM, REPORTING_CURR, LEDGER_NAME, and the period set and period year identifiers. It also defines the SELECT_BAL, SELECT_ALL, and WHERE_FLEX_RANGE variables, which hold dynamically assembled account flexfield concatenation strings and range predicates used to select balances by account segment criteria.

The package belongs to the APPS schema (owner APPS), is classified as OTHER rather than as a published API, and is not referenced by any other packages, which confirms that it is a report-support package consumed only by the GLXAVADT report itself.

Key Procedures and Functions

The ETRM metadata documents twenty-nine procedures and functions. The package exposes the following actual names:

• BEFOREREPORT / AFTERREPORT — XML Publisher before-report and after-report triggers that initialize the package's parameter and derived-date variables, and perform cleanup after the report completes.
• OPENING_BALFORMULA, LAST_CCIDFORMULA, DAILY_ACTIVITYFORMULA — formula columns or group filters that compute opening balances, the last CCID value, and daily activity amounts used in the report's balance lines.
• GL_GET_PERIOD_INFO, GL_GET_FIRST_DATE — utility routines that resolve period and date information, notably deriving the first date associated with the reporting period.
• G_BALANCING_SEGGROUPFILTER, G_OPENING_BALGROUPFILTER — group filter functions that restrict the balancing segment and opening balance data sets according to the package's ledger and access set context.
• 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, SELECT_BAL_P — the documented accessor functions corresponding to the package's public variables. These "_P" functions are the mechanism by which the XML Publisher report's data model retrieves values such as the ledger name, period set name, period year, quarter number, period number, reporting currency, start date, start period name, and the balance selection string.

The user's search term start_date_p corresponds to the START_DATE_P accessor function, which returns the package-level START_DATE variable — the derived starting date of the current period used by the report's calculations. No parameter signatures are supplied in the metadata and none are asserted here.

Tables Accessed

The package reads from several General Ledger tables through APPS synonyms:

• GL_LEDGERS — to obtain the ledger name and accounting setup used by the report.
• GL_ACCESS_SETS — to enforce data access security when resolving ledgers and balances.
• GL_PERIOD_STATUSES — to determine period status, period name, quarter, and period year context.
• GL_DATE_PERIOD_MAP — to map the reporting date to the correct accounting period and its first date.
• GL_BALANCES — the primary balance source, filtered by ledger, balance type, currency, and the dynamically constructed flexfield range predicates.

Usage Notes

The package is invoked indirectly through the GLXAVADT XML Publisher concurrent program in General Ledger. Oracle Reports and XML Publisher call its BEFOREREPORT and AFTERREPORT procedures at the appropriate trigger points during execution, and the report's SQL queries call the accessor functions and formula functions to obtain the derived parameters and computed balance values. It is not an API package and is not designed to be called from custom PL/SQL outside the report context. Customizations that require access to the same reporting context should query the underlying GL tables directly or use documented GL APIs, rather than invoking these internal routines, whose signatures and behavior are subject to change across releases.