Search Results ledger_name_p

Overview

APPS.GL_GLXRBDHR_XMLP_PKG is a generated PL/SQL package that serves as the report logic container for an Oracle General Ledger XML Publisher (BI Publisher) concurrent program. The internal naming convention (GL_GLXRBDHR_XMLP_PKG) indicates that the package backs an XMLP-based report whose source file is GLXRBDHRS.pls, as confirmed by the header comment in the specification. Its role is to hold the bind variables, global state, and report-level trigger functions that Oracle Reports and the XML Publisher engine call during execution of the associated concurrent program.

The package maintains two categories of package-level globals. The first are the concurrent request and parameter inputs: P_CONC_REQUEST_ID, P_LEDGER_ID, and P_ACCESS_SET_ID. The second are derived display values that are resolved at run time and exposed to the report layout: LEDGER_NAME, STRUCT_NUM, and ACCESS_SET_NAME. This structure is characteristic of Oracle EBS XMLP report packages, where parameters are accepted, contextual attributes are resolved against the ledger and access set definitions, and the results are published as XML tags for the template.

Key Procedures and Functions

• BeforeReport — The report trigger function executed prior to the main report query. It performs setup work such as resolving the ledger and access set names from the parameter identifiers and populating the package globals used later by the data model and layout.
• AfterReport — The report trigger function executed after the report completes. It is used for cleanup and resetting of package state at the end of a run.
• LEDGER_NAME_p — A getter function that returns the resolved ledger name (LEDGER_NAME) for the report.
• STRUCT_NUM_p — A getter function that returns the structure number (STRUCT_NUM) associated with the ledger.
• ACCESS_SET_NAME_p — A getter function that returns the resolved access set name (ACCESS_SET_NAME) for the report.

The three _p functions follow the standard Oracle Reports/XMLP accessor naming pattern; they expose internal globals to the report data model so that values can be referenced as XML elements in the output.

Tables Accessed

• GL_LEDGERS — Referenced through the APPS synonym to retrieve ledger attributes, principally the ledger name and the associated chart of accounts structure number, based on P_LEDGER_ID.
• GL_ACCESS_SETS — Referenced to resolve the access set name from P_ACCESS_SET_ID, which governs the data access privileges applicable to the report run.

Both tables are core General Ledger configuration entities. Access is read-only, consistent with a reporting package that resolves descriptive context rather than maintaining transactional data.

Usage Notes

This package is invoked automatically by the Oracle Reports/XML Publisher run-time engine when the associated GL concurrent program is submitted. It is not intended for direct invocation from forms or custom code. The concurrent request identifier is passed in through P_CONC_REQUEST_ID, and the ledger and access set parameters are supplied from the concurrent program parameter window. The resolved LEDGER_NAME, STRUCT_NUM, and ACCESS_SET_NAME values are consumed by the report template, typically displayed in the report heading to identify the ledger and access set context of the output.

Because it is a report-specific package generated against a specific source version (RDBMS header 120.0, dated 2007/12/27), it should be treated as internal and non-extensible. Customizations should be applied to a copy of the report definition rather than to this package. The package is self-contained: it is not referenced by any other package in the ETRM inventory, and its documented interface consists solely of the five functions listed above. The convention of returning a Boolean from the trigger functions matches Oracle Reports expectations, where a FALSE return can abort report execution under error conditions.