Search Results adj_drs




Overview
Explore in AI Chat

Overview

APPS.GL_MC_INQUIRY_PKG is a PL/SQL package body in the Oracle E-Business Suite General Ledger module. Its name and procedure inventory indicate that it belongs to the Multi-Currency (MC) inquiry layer, providing the query and balance-retrieval logic used by inquiry screens and programs that present primary and reporting set of books information side by side. Unlike the core accounting engine, this package is an inquiry-oriented container: it exposes functions and procedures that assemble depreciation, period, adjustment, and associated set of books data for display rather than to post or validate journal entries.

The header comment embedded in the body ($Header: glmcinqb.pls 120.5 2006/01/13) shows the source is an older-generation file that has been retained across the 11i to 12.1.1 and 12.2.2 releases without functional enrichment. Several routines in the current body are stubs that return NULL or FALSE, indicating that parts of the original design were superseded, most notably by the Rel11 note stating that adjustment handling would move into the depreciation rows themselves. Consumers should therefore treat this package as an integration and compatibility surface rather than as a source of authoritative accounting logic.

Key Procedures and Functions

  • MRC_ENABLED — Determines whether multi-reporting-currency functionality applies for a given application, primary set of books, and organization. In the documented source it is a stub returning FALSE.
  • GET_ASSOCIATED_SOBS — Populates a set-of-books array (r_sob_list_type) with the reporting set of books associated with a primary set of books, application, organization, and fixed asset book. The comment acknowledges a known defect regarding the asset book type code.
  • QUERY_BALANCES — Top-level balance inquiry routine that accepts an asset identifier, book, period counter, distribution identifier, and run mode to retrieve balance information.
  • QUERY_BALANCES_INT — Internal counterpart to QUERY_BALANCES, operating on a depreciation row structure and returning original cost, salvage value, revaluation ceiling, revaluation reserve, and cost values.
  • ADD_ADJ_TO_DEPRN — Adds the current period's adjustments (ADJ_DRS) into the most recent depreciation row (DEST_DRS), called immediately after adjustment retrieval.
  • GET_PERIOD_INFO — Returns period-level context used when presenting balances and depreciation across set of books.
  • QUERY_DEPRN_SUMMARY — Retrieves summarized depreciation data for inquiry display.
  • GET_ADJUSTMENTS_INFO — Supplies adjustment information consumed by ADD_ADJ_TO_DEPRN.
  • AR_INIT_CASH_RECEIPTS — Initialization routine related to Receivables cash receipts within the multi-currency inquiry flow.
  • INIT_INVOICE and INIT_PAYMENT — Initialization routines for invoice and payment data used by the same inquiry process.
  • TRANSACTION_BALANCES — Returns transaction-level balance information; this is the routine most directly associated with the "transaction_balances" search term and is the primary entry point for callers seeking per-transaction balances in a multi-currency inquiry context.

Tables Accessed

The documented metadata does not enumerate base tables, only APPS synonyms indirectly. The parameter signatures reference FA_STD_TYPES structures (fa_deprn_row_struct), confirming that the package operates over Fixed Assets depreciation rows, and the naming of AR_INIT_CASH_RECEIPTS, INIT_INVOICE, and INIT_PAYMENT indicates access to Receivables transaction data through the standard AR inquiry views. Balance-oriented routines imply reads against GL and FA balances, but no direct table list is asserted in the source excerpt.

Usage Notes

GL_MC_INQUIRY_PKG is referenced by one other package, so it should be regarded as an internal inquiry dependency rather than a public API. It is typically invoked from inquiry forms, multi-currency inquiry concurrent programs, or custom code that reproduces the standard set of books comparison screens. Because multiple routines are stubs and the body carries an explicit "should go away in Rel11" note, customizations should avoid extending this package for new logic and should instead query the underlying FA and GL tables directly. Any upgrade from 12.1.1 to 12.2.2 should be preceded by a review of these routines to confirm that the stubbed behavior remains acceptable for the calling forms and reports.