Search Results gl_glxlslst_xmlp_pkg

Overview

APPS.GL_GLXLSLST_XMLP_PKG is the generated PL/SQL package that backs the Oracle General Ledger concurrent program "GLXLSLST" — the XML Publisher (BI Publisher) version of the GL Ledger/Structure Listing report. The package's role is standard for Oracle Reports and XML Publisher concurrent program wrappers: it declares the report's bind and lexical parameters as package-level variables, provides getter functions that expose those values to the report layout and to SQL queries embedded in the report definition, and supplies the BeforeReport and AfterReport triggers that initialize and clean up the reporting context. The program is used by GL administrators and implementation teams to list the chart of accounts structures (accounting key flexfield structures) associated with a ledger, together with identifying attributes such as the calendar, period type, structure number, description, chart of accounts name, ledger set name, and session language. In EBS 12.1.1 and 12.2.2 the object resides in the APPS schema and is classified as OTHER (a report-support package, not a public API). The header comment shows version 120.0, dated 2007/12/27, indicating the package has been stable across releases and ships with the standard XML Publisher report set rather than changing with each point release.

Key Procedures and Functions

The package exposes nine documented program units. Two are report triggers: BeforeReport returns BOOLEAN and executes before the report query is fired, and AfterReport returns BOOLEAN and executes after report output is produced. These are the standard XML Publisher report-level triggers used to set up and tear down the reporting environment. The remaining seven are the parameter getter functions, each returning the current value of a package variable: C_CALENDAR_p returns the accounting calendar name, C_PERIOD_TYPE_p returns the period type, C_STRUCT_NUM_p returns the accounting flexfield structure number, C_DESCRIPTION_p returns the structure description, C_COA_NAME_p returns the chart of accounts name, C_LEDGER_SET_NAME_p returns the ledger set name, and C_LANGUAGE_p returns the language used for the output. These getters are referenced from the report's data model and layout templates so that the same value captured at report startup is used consistently. The variables themselves — P_CONC_REQUEST_ID, P_LEDGER_ID, C_CALENDAR, C_PERIOD_TYPE, C_STRUCT_NUM, C_DESCRIPTION, C_COA_NAME, C_LEDGER_SET_NAME, and C_LANGUAGE — are declared at the top of the package specification and hold the runtime parameter context, including the concurrent request ID that identifies the specific submission.

Tables Accessed

According to the documented metadata, the package reads three tables through APPS synonyms. FND_ID_FLEX_STRUCTURES_TL is the translated table of key flexfield structure definitions; it supplies the structure number, the description, and the chart of accounts name displayed on the report. GL_LEDGERS supplies ledger attributes, including the association between the ledger and its chart of accounts and calendar, and is used to resolve the ledger specified at submission time. GL_PERIOD_TYPES supplies the accounting period type used by the ledger, which the report prints alongside the calendar. No table is written by this package; it is a read-only reporting component.

Usage Notes

This package is not a public API and should not be called directly from custom code. It is invoked automatically by the Oracle Reports runtime or by the XML Publisher concurrent program infrastructure when the GLXLSLST concurrent program is submitted. In 12.1.1 and 12.2.2 the program can be run from the Standard Request Submission window, from the Submit Requests form, or scheduled as a recurring request in the GL responsibility. The P_CONC_REQUEST_ID parameter is populated by the concurrent manager to link report output to the request record in FND_CONCURRENT_REQUESTS. The documented metadata shows the package is referenced by zero other packages, confirming its role as a leaf-level report-support component. Customization should be limited to the underlying report definition or a copied report, not to this generated package body.