Search Results debit_dsp_p




Overview
Explore in AI Chat

Overview

The APPS.GL_GLRFGNJ_XMLP_PKG package is a generated Oracle Reports (XML Publisher) support package that belongs to the Oracle General Ledger application module. Its name follows the standard EBS convention for report packages, where XMLP_PKG identifies a PL/SQL library bound to an XML Publisher data model or an Oracle Reports executable. The GLRFGNJ token corresponds to a General Ledger standard report program — historically a foreign currency or revaluation-related journal listing — that renders output through the XMLP engine. The package holds the report-level trigger logic, formula columns, parameter derivation helpers, and lexical WHERE/SELECT fragment builders required by the concurrent program at runtime.

The object is owned by the APPS schema, carries a VALID status, and is classified under the ETRM API classification OTHER, meaning it is not a supported public API but an internal implementation artifact. It is not referenced by any other package, confirming that its only consumers are the report definition and the Reports/XMLP runtime itself.

Key Procedures and Functions

The ETRM metadata documents 27 procedures and functions. The most significant include:

  • BEFOREREPORT — the standard report entry point invoked before data retrieval; it initializes session state and prepares parameters for the report query.
  • AFTERREPORT — the standard trailing trigger used for cleanup or final formatting after the result set is produced.
  • ENT_X_DRCRFORMULA / ACCT_X_DRCRFORMULA — formula columns that resolve the debit/credit (DR/CR) sign indicator for the Enterprise and Accounting flexfield views respectively.
  • DR_CR_DSPFORMULA — a display formula that presents the DR/CR value in the report layout.
  • G_LINESGROUPFILTER — a report-level group filter applied to the line data block.
  • GL_FORMAT_CURRENCY — formats monetary amounts according to the reporting currency conventions.
  • FLEXDATA_P — retrieves flexfield display data for the accounting key segments.
  • POSTING_STATUS_SELECT_P / POSTING_STATUS_WHERE_P — build the SELECT and WHERE fragments that constrain journal lines by posting status.
  • PERIOD_WHERE_P — constructs the period-range predicate.
  • DAS_WHERE_P — builds the WHERE clause fragment for the detail accounting flexfield (DAS) restriction.
  • STRUCT_NUM_P — resolves the accounting flexfield structure number in use.
  • PARAM_LEDGER_NAME_P / PARAM_LEDGER_TYPE_P / ACCESS_SET_NAME_P — derive the ledger name, ledger type, and access set name from the concurrent program parameters.
  • INV_FLEX_MSG_P — supplies the message returned when the flexfield configuration is invalid or inaccessible.
  • DEBIT_DSP_P / CREDIT_DSP_P — supply the formatted debit and credit display values.
  • WIDTH_P — controls column width sizing in the report output.

Tables Accessed

The package reads Oracle General Ledger base and security tables through APPS synonyms:

  • GL_LEDGERS — source of ledger definition, accounting flexfield, currency, and chart-of-accounts attributes.
  • GL_ACCESS_SETS — resolves the access set controlling which ledgers the user may report on, driving the security WHERE fragments.
  • GL_SYSTEM_USAGES — identifies the General Ledger system usage assigned to the ledger, supporting ledger-type derivation.
  • DUAL — used for scalar parameter evaluations and constant selection.

All reads are consistent with a reporting-only workload; the package does not write to these tables.

Usage Notes

This package is invoked exclusively by its parent XML Publisher / Oracle Reports concurrent program in General Ledger. Users do not call it directly. The BEFOREREPORT and AFTERREPORT triggers fire automatically during report execution, and the WHERE/SELECT builder functions (POSTING_STATUS_WHERE_P, PERIOD_WHERE_P, DAS_WHERE_P) supply the lexical fragments that the report data model concatenates at runtime. Customization should be avoided because the package body is regenerated when the report definition is recompiled in ADOP or adpatch cycles; any site-specific logic belongs in a separate custom package. The presence of ACCESS_SET_NAME_P and PARAM_LEDGER_TYPE_P confirms that data access security and ledger-type filtering are enforced inside the report rather than by the calling form.