Search Results end_bal

Overview

APPS.GL_GLXBTB_XMLP_PKG is the generated PL/SQL package body that supports the Oracle E-Business Suite General Ledger XML Publisher (BI Publisher) report GLXBTB, generally known as the "Trial Balance" or "Trial Balance - Detail" report. In Releases 12.1.1 and 12.2.2 the Report Manager architecture converts the classic Reports Builder (.rdf) program into a package specification and a package body whose procedures and functions supply the data model, formula columns, and report-level triggers that the XML Publisher template consumes. The package is classified as API classification OTHER, meaning Oracle does not publish it as a supported public API; it is a runtime artifact that should be modified only through Oracle-supplied patches.

The business purpose of GLXBTB is to present account balances for a chosen ledger, access set, and accounting period, comparing beginning balances with ending balances. Within this package the token END_BAL is directly relevant: it is the input parameter of the formula function PERIOD_ACT_BALFORMULA, which computes period activity as ending balance less beginning balance. The report therefore enables controllers and accounting staff to review opening balances, period movement, and closing balances at the account and balancing-segment level.

Key Procedures and Functions

The package exposes 21 documented program units. The principal formula and trigger functions are described below; parameters are named only where the source excerpt documents them.

• PERIOD_ACT_BALFORMULA — Accepts END_BAL and BEGIN_BAL and returns their difference, producing the period activity amount displayed on the report. This is the function most closely associated with the user's "end_bal" search.
• BUDGET_NAMEFORMULA — Calls GL_INFO.GL_GET_BUD_OR_ENC_NAME to translate the budget version identifier into a printable budget name, raising an application error if the lookup fails.
• DISP_BAL_LPROMPT_W_COLONFORMUL — Appends a colon to the balance prompt label for display formatting.
• BEFOREREPORT — Report trigger executed before output; validates the supplied access set against GL_ACCESS_SETS and populates ACCESS_SET_NAME and STRUCT_NUM, raising GL_PLL_INVALID_DATA_ACCESS_SET when the identifier is invalid.
• AFTERREPORT — Post-report cleanup trigger; returns TRUE.
• Group filter functions — G_BALANCESGROUPFILTER, G_PAGE_BREAKGROUPFILTER, and G_ACCT_DATAGROUPFILTER control which rows are emitted for the balances, page-break, and account data groups.
• Parameter and lookup formulas — LEDGER_NAMEFORMULA, STRUCT_NUM_P, and ACCESS_SET_NAME_P expose the ledger name, chart of accounts structure number, and access set name to the report layout.
• Query construction functions — SELECT_BAL_P, SELECT_ALL_P, SELECT_ACCT_P, ORDERBY_BAL_P, ORDERBY_ACCT_P, ORDERBY_ALL_P, WHERE_DAS_P, TRANS_CHECK_BB_P, and TRANS_CHECK_BE_P assemble the SELECT, WHERE, and ORDER BY clauses, apply data access security (DAS), and determine whether beginning- or ending-balance translation logic applies.

Tables Accessed

The documented data dictionary references are GL_ACCESS_SETS, read in BEFOREREPORT to resolve the access set name and chart of accounts identifier used for data access security, and GL_LEDGER_RELATIONSHIPS, used to determine the ledger hierarchy and related ledgers included in the report output. Balance figures themselves are obtained from the GL temporary balance and period-balance tables populated by the report's underlying query logic rather than from base transaction tables.

Usage Notes

GL_GLXBTB_XMLP_PKG is invoked implicitly when the GLXBTB concurrent program is submitted from the General Ledger responsibility or from the standard Submit Request form. Users supply the ledger, access set, budget version, period, and balance options; the package then resolves the access set, builds the query, and returns rows to the XML Publisher template. Because it is referenced by zero other packages, it has no dependent PL/SQL callers in the ETRM inventory.

Custom implementations should not call these functions directly. Any modification, such as changing the period activity calculation in PERIOD_ACT_BALFORMULA, must be applied through the Oracle patching mechanism, since the package is regenerated whenever the underlying report definition is recompiled. Environments upgraded from 12.1.1 to 12.2.2 retain the same internal logic, although the online accounting model in 12.2.x means balances are frequently derived from the GL_SUMMARY and GL_PERIOD_BALANCES_INTERIM structures rather than the older consolidated tables.