Search Results read_module




Overview

PA_PAXAUGLT_XMLP_PKG is a public PL/SQL package owned by APPS in the Oracle E-Business Suite environment. Its name follows the Oracle Reports XML Publisher (XMLP) generated-package convention: the _XMLP_PKG suffix indicates that the package accompanies the database-side logic of a concurrent report, in this case the "PAXAUGLT" report associated with Oracle Projects (PA). The package was last committed under the file PAXAUGLTS.pls (version 120.1, dated 2008/01/03), and it declares AUTHID CURRENT_USER, meaning that all statements execute with the privileges of the invoking schema rather than the definer.

Functionally, the package acts as the PL/SQL back end for a Projects subledger-to-General Ledger audit report. It exposes the report's parameter values (account ranges, period ranges, interface dates, chart of accounts, set of books), resolves report formulas, and manages session context. The presence of GET_COVER_PAGE_VALUES and GET_COMPANY_NAME confirms it supports cover-page rendering, while the CP_-prefixed variables (CP_USR_JE_SNAME, CP_GL_START, CP_GL_END) and GL_JE_SOURCES access indicate that the report reconciles journal sources against General Ledger period close data.

Key Procedures and Functions

The READ_MODULE procedure, which the user searched for, is the documented counterpart to SET_MODULE: it returns the module name and action name currently set in DBMS_APPLICATION_INFO, and is declared with OUT NOCOPY parameters for efficiency.

Tables Accessed

  • GL_JE_SOURCES — Used to resolve journal source names (correlated with CP_USR_JE_SNAME) so that the report can identify source-originated transactions.
  • GL_PERIODS — Supplies period name and date boundaries for the from/to period and interface-date parameters.
  • DBMS_APPLICATION_INFO — A database-supplied package, not an application table; it backs the module/action/client-info session-tracking procedures.

Usage Notes

The package is invoked indirectly by the Oracle Reports concurrent program that carries the same XMLP-generated name. It is not a general-purpose API and is not referenced by any other package (referenced by 0 other packages), so its call sites are confined to the associated report definition and any custom concurrent request that runs it. The documented variables P_CONC_REQUEST_ID, P_COA_ID, and P_CA_SET_OF_BOOKS_ID confirm that it is driven by a concurrent request with the standard Oracle Projects chart-of-accounts and set-of-books parameters. Customizations should avoid modifying this package directly; extending report behavior is better achieved through the underlying report definition or by wrapping calls to its public getters.