Search Results msg_tkn_expand

Overview

APPS.GL_GLXRLTCL_XMLP_PKG is a General Ledger report package in Oracle EBS Release 12.1.1 and 12.2.2. It is a generated XML Publisher (BI Publisher) report package bound to a concurrent program—identified internally by the P_CONC_REQUEST_ID parameter—that produces a General Ledger listing report. The package encapsulates the PL/SQL logic executed before and after the report data model runs, exposes report-level parameters and lexical bindings, and supplies a family of helper routines that retrieve ledger, period, consolidation, and lookup information required by the report's query and layout. Its structure is characteristic of XML Publisher report wrappers: a set of package globals and accessor functions (the "_P" functions that return derived values to the template), a BEFOREREPORT/AFTERREPORT pair that brackets execution, and reusable GL data retrieval procedures. The package is declared with AUTHID CURRENT_USER and runs under APPS, so it executes with the privileges of the invoking schema, and its source header indicates a last revision from 2007 (GLXRLTCLS.pls 120.0).

Key Procedures and Functions

The documented API surface comprises roughly 20 procedures and functions:

• BEFOREREPORT and AFTERREPORT — the standard pre-report and post-report entry points invoked by the XML Publisher concurrent program infrastructure to initialize and finalize report execution.
• SET_OF_BOOKS_NAME_P, STRUCT_NUM_P, VALUE_SET_ID_P, and PAGENO_P — accessor functions that return report global values to the template: the ledger (set of books) name, the account structure number, the value set identifier, and the current page number.
• GL_GET_PERIOD_DATES — returns the start and end dates for a given set of books and period name.
• GL_GET_LEDGER_INFO — returns chart of accounts ID, ledger name, and functional currency for a given set of books ID.
• GL_GET_BUD_OR_ENC_NAME — resolves the name of a budget or encumbrance type from its actual type and type ID.
• GL_GET_LOOKUP_VALUE — retrieves a lookup value by mode, code, and type; the searched term "set_language" aligns with this package's localization support.
• GL_GET_FIRST_PERIOD and GL_GET_FIRST_PERIOD_OF_QUARTER — return the first period, respectively the first period of the quarter, for a period and set of books.
• GL_GET_CONSOLIDATION_INFO — returns consolidation name, method, currency, from/to set of books IDs, description, and date range for a consolidation.
• SET_LANGUAGE — sets the language context, typically to force the report and its concurrent program to render messages and output in a specified language ID.
• GET_MESSAGE and MSG_TKN_EXPAND — retrieve and expand message text, supporting the token substitution used in report headers and boilerplate.

Tables Accessed

The package reads two documented tables through APPS synonyms:

• FND_ID_FLEX_SEGMENTS — the application object library table defining key flexfield segments; used to resolve structure and segment information for the ledger's chart of accounts referenced in the report.
• FND_SEGMENT_ATTRIBUTE_VALUES — holds segment attribute values, including the value set and segment qualifier metadata the report uses when reporting on the accounting flexfield.

These are Foundation (FND) dictionary tables, confirming the package's role in resolving flexfield structure and value set information rather than storing transactional GL data.

Usage Notes

GL_GLXRLTCL_XMLP_PKG is invoked indirectly through its parent XML Publisher concurrent program, not called by application forms. The concurrent manager passes the request ID, and the framework calls BEFOREREPORT, then executes the report query, then calls AFTERREPORT. The accessor functions and GL_GET_* helpers are called from within the report's data model or template bindings, not externally. SET_LANGUAGE is used to switch the report output language based on the user or request language. The package is referenced by zero other packages, indicating it is a leaf-level report wrapper with no dependents. Custom integrators should avoid calling it directly; instead, they should run the associated GL report concurrent program or reuse the individual GL_GET_* helper procedures where documented. Changes to the underlying flexfield structure tables used here will affect segment and value set resolution in the report output.