Search Results select_detail_budget




Overview
Explore in AI Chat

Overview

APPS.GL_GLXRBCR_XMLP_PKG is the generated Oracle Reports PL/SQL package body that supports the Oracle General Ledger "Budget vs. Actual" style report, associated with the report definition GLXRBCR (Budget and Encumbrance Comparison / Budget vs. Actual inquiry report). In Oracle EBS 12.1.1 and 12.2.2, XML Publisher (BI Publisher)-converted concurrent reports embed a compiled PL/SQL package whose name follows the GL_<report>_XMLP_PKG pattern. This package provides the report-specific logic that the report's data model and layout call: token substitution for report parameters, formula columns, anchoring of the report context (ledger, access set, chart of accounts), and cursor-bind logic for the master and detail budget selections.

Its business purpose is to present a comparison of a master (primary) budget balance against aggregated detail budget balances for a given ledger and chart of accounts, resolving the correct budget version names, access-set-driven data access security, and PTD/YTD display conventions. The recorded API classification is OTHER, meaning it is not a published, formally supported public API; it exists to service the report executable only.

Key Procedures and Functions

  • AFTERREPORT — Report-level trigger invoked after the report output completes; historically issued the SRW exit call (FND SRWEXIT) and simply returns TRUE.
  • BEFOREREPORT — Report-level trigger invoked before report execution; initializes the report context and issues the FND SRWINIT exit. It also resolves the access set name/chart of accounts and the ledger name for the selected parameters.
  • MASTER_BUDGET_NAMEFORMULA — Formula column returning the display name of the master budget version, resolved via GL_INFO.GL_GET_BUD_OR_ENC_NAME using the budget version ID parameter.
  • AVAILABLE_BUDGETFORMULA — Formula column computing the available budget amount as the difference between the master budget balance and the total detail budget balance.
  • SELECT_MASTER_BUDGET_P — Returns the value/identifier for the master budget selection used by the report's master budget bind; this is the object surfaced by the "select_master_budget" search term.
  • SELECT_DETAIL_BUDGET_P — Returns the value/identifier for the detail budget selection compared against the master budget.
  • SELECT_FLEX_P — Selects the accounting flexfield (chart of accounts) context for the report.
  • ORDERBY_FLEX_P — Supplies the ORDER BY clause fragment for the flexfield, controlling the sort order of report rows.
  • WHERE_DAS_P — Provides the WHERE clause fragment enforcing Data Access Set security so users only see permitted ledger/balancing segment data.
  • CHART_OF_ACCOUNTS_ID_P, LEDGER_NAME_P, ACCESS_SET_NAME_P — Parameter/context accessors returning the chart of accounts ID, ledger name, and access set name respectively.
  • PTD_YTD_DSP_P — Controls whether amounts are displayed on a period-to-date (PTD) or year-to-date (YTD) basis.

Tables Accessed

  • GL_ACCESS_SETS — Queried in BEFOREREPORT to resolve the access set name and chart of accounts ID from P_ACCESS_SET_ID; supports the data-access-security filter built by WHERE_DAS_P.
  • GL_LEDGERS — Queried in BEFOREREPORT to resolve the ledger name from P_LEDGER_ID.
  • Budget balances are not read directly by the package body but are passed in through formula columns and bind variables derived from the report's underlying queries.

Usage Notes

GL_GLXRBCR_XMLP_PKG is not invoked by other PL/SQL packages; the metadata records zero referencing packages. It is executed exclusively by the concurrent program/report executable that it was generated for — typically launched as a concurrent request from General Ledger inquiry forms such as the Budget Inquiry or from the Submit Requests window. Because it is a report-private XMLP package, Oracle does not document or guarantee its internal signatures for external callers. Custom code should not call these functions directly; any extension should rely on the report's parameters (LEG parameter, P_LEDGER_ID, P_ACCESS_SET_ID, P_BUDGET_VERSION_ID) rather than the package internals. On upgrades between 12.1.1 and 12.2.2 the body is regenerated and may change without notice.