Search Results thousands_separator




Overview

APPS.GL_GLXETB_XMLP_PKG is the database-side PL/SQL package body that backs the Oracle General Ledger XML Publisher report GLXETB. Its name follows the standard EBS concurrent program/XML Publisher naming convention, in which a report definition (for example GLXETB) is bound to a generated package (GL_GLXETB_XMLP_PKG) that supplies report-level formulas, grouping filters, column formatting logic, lexical parameters, and pre/post-processing hooks. The package is classified as OTHER in the ETRM repository, meaning it is a supporting report component rather than a public-API package. Its principal business function is to produce an enhanced trial balance or account balances style ledger report scoped by an access set, resolving the access set name and chart of accounts identifier, applying data access security to the ledger dimension, and computing derived balances and currency display values for the XML template.

Key Procedures and Functions

The documented interface comprises 26 procedures and functions, most of which exist to satisfy XML Publisher report triggers or to return SQL fragments and grouping values to the report definition.

Tables Accessed

The package references three objects through APPS synonyms. GL_ACCESS_SETS is read in BeforeReport to translate the access set identifier parameter into the access set name and the associated chart of accounts identifier, and it underpins the security clause used to restrict report rows. GL_LEDGERS is referenced to support ledger and ledger currency parameter resolution, notably through PARAM_LEDGER_CURR_P. DUAL is used for scalar evaluations and parameter defaults. All access is read-only; the package does not write application data.

Usage Notes

GL_GLXETB_XMLP_PKG is invoked implicitly by the XML Publisher engine whenever the GLXETB concurrent program or its report definition is run from the Submit Requests form or the standard concurrent manager. It is not referenced by any other package, so it has no programmatic dependents and should not be treated as a callable API. Customizations should be limited to the XML template or to a cloned package, because the body is a generated report component shipped under the APPS schema. The header comment indicates a 2007 revision, so behavior is consistent across EBS 12.1.1 and 12.2.2, with any differences attributable to the online patching editioning applied to APPS objects in 12.2.