Search Results gl_glxrbdhr_xmlp_pkg




Overview
Explore in AI Chat

Overview

APPS.GL_GLXRBDHR_XMLP_PKG is the Oracle Reports 6i PL/SQL library package body that supports the General Ledger multi-currency / revaluation-style report executable GLXRBDHR, distributed within the Oracle E-Business Suite General Ledger (GL) module. In EBS 12.1.1 and 12.2.2, report-specific XML publisher (XMLP) packages of this naming convention are auto-generated stubs that wrap the report's anchor logic: they hold the "before report" and "after report" triggers, receive the report parameters entered by the user, resolve those parameters into descriptive database values, and expose the resolved values back to the report layout as placeholders.

The package belongs to the family of standard GL report DBI packages owned by APPS and is classified as OTHER in the ETRM repository. Its principal business responsibility is validation and enrichment of two mandatory runtime parameters supplied by the user when the report is submitted: the access set identifier (P_ACCESS_SET_ID) and the ledger identifier (P_LEDGER_ID). If either parameter cannot be resolved against the GL setup tables, the report is deliberately aborted rather than executed against an invalid or unauthorized data context.

Key Procedures and Functions

  • BEFOREREPORT — The report-level Before Report trigger. It performs the substantive work of the package: it queries GL_ACCESS_SETS to derive the access set name (ACCESS_SET_NAME) and the associated chart of accounts structure number (STRUCT_NUM) for the supplied P_ACCESS_SET_ID, and it queries GL_LEDGERS to obtain the ledger name (LEDGER_NAME) for the supplied P_LEDGER_ID. When the access set lookup returns no rows, it retrieves the seeded message GL_PLL_INVALID_DATA_ACCESS_SET and raises a controlled application error (-20101), terminating the report; any other lookup failure is converted into the same abort with SQLERRM as the diagnostic.
  • AFTERREPORT — The report-level After Report trigger. In the documented source it is an empty stub returning TRUE, retained for symmetry with the Oracle Reports execution model and, historically, for the SRW cleanup user exit that is now commented out.
  • LEDGER_NAME_P — Placeholder accessor that returns the resolved LEDGER_NAME to the report layout.
  • STRUCT_NUM_P — Placeholder accessor that returns the resolved chart of accounts structure number (STRUCT_NUM) to the report layout.
  • ACCESS_SET_NAME_P — Placeholder accessor that returns the resolved ACCESS_SET_NAME to the report layout.

Tables Accessed

  • GL_ACCESS_SETS — Read in BEFOREREPORT to validate P_ACCESS_SET_ID and to fetch the access set name and chart of accounts ID. This is the control that enforces data access set security; a missing or invalid ID triggers the GL_PLL_INVALID_DATA_ACCESS_SET message.
  • GL_LEDGERS — Read in BEFOREREPORT to translate P_LEDGER_ID into the ledger name used as report heading information. Failure to find the ledger aborts the report with the raw SQL error message.

Usage Notes

The package is invoked implicitly by the Oracle Reports runtime whenever the GLXRBDHR report is executed; it is not called directly by application forms or custom code. In a standard EBS deployment the report is launched from the General Ledger responsibility's standard request submission, or from a form that submits the concurrent request with the access set and ledger parameters populated. The package is referenced by zero other PL/SQL packages, so its scope is confined to the single report executable. The GL_PLL_INVALID_DATA_ACCESS_SET message string, visible in the user search that surfaced this object, is the runtime error returned to the concurrent manager log and to the request submitter when the supplied access set does not exist or is not accessible. Because the original SRW message and abort calls are commented out in the source, error surfacing relies entirely on RAISE_APPLICATION_ERROR, producing a generic error-20101 in the request log rather than a friendly concurrent-manager message.