Search Results functional_credit_amount




Overview

APPS.ARBV_ADJ_DISTS_ALT_CRNCY is a Business Intelligence System (BIS) view in the Oracle E-Business Suite Receivables (AR) module. It is registered in FND Design Data under the identifier AR.ARBV_ADJ_DISTS_ALT_CRNCY and holds a VALID status in the APPS schema across Oracle EBS 12.1.1 and 12.2.2. The view exposes Multiple Reporting Currencies (MRC) information regarding adjustment amounts that have been posted to the General Ledger. MRC is an Oracle General Ledger feature that allows an organization to maintain and report accounting data in more than one functional currency simultaneously, translating primary ledger transactions into one or more reporting currencies.

Because the object is a BIS view rather than a transactional entity, it serves a reporting and integration purpose: it presents a denormalized, read-only projection of adjustment distribution data in the reporting (alternate) currency. The "ALT_CRNCY" naming convention signals that the amounts surfaced by this view are expressed in an alternate reporting currency rather than the primary functional currency of the source ledger. This makes the view suitable for cross-currency analysis, reconciliation between primary and reporting ledgers, and downstream extracts feeding financial data warehouses or GL reporting.

Underlying Base Objects

The view is defined over the documented base object AR_MC_ADJUSTMENTS, accessed through a SYNONYM in the APPS schema. AR_MC_ADJUSTMENTS stores Multiple Reporting Currencies adjustment information for Receivables adjustments, that is, the alternate-currency counterparts of the primary adjustment records. The view therefore inherits its source rows from this MRC table and projects a restricted subset of columns into a reporting-oriented shape.

The metadata records that ARBV_ADJ_DISTS_ALT_CRNCY references AR_MC_ADJUSTMENTS, and notably that the view "is not referenced by any database object" within the documented dependency set. It is a leaf object in the dependency graph: consumers are expected to be external queries, reports, or integration programs rather than other database views. There are no further upstream dependencies documented beyond the AR_MC_ADJUSTMENTS synonym, indicating a relatively shallow lineage.

Key Columns

The view exposes a compact column set. The following columns are documented:

  • FUNCTIONAL_DEBIT_AMOUNT (NUMBER) — The debit side of the adjustment distribution amount, expressed in the functional currency of the reporting context derived from the MRC data. This is the counterpart to the credit amount and supports balanced accounting analysis.
  • FUNCTIONAL_CREDIT_AMOUNT (NUMBER) — The credit side of the adjustment distribution amount in functional currency terms. This column is the direct target of the user's search term "functional_credit_amount," and it represents the reporting-currency credit value posted for the adjustment. It is the figure analysts typically aggregate when reconciling GL postings of adjustments by currency.
  • _LA:POSTED_FLAG (CHAR, length 71) — A posting status indicator. The "_LA:" prefix denotes an application-context or descriptive-flexfield-related attribute; the column reflects whether the associated distribution has been posted to the General Ledger.
  • ADJUSTMENT_ID (NUMBER, length 15) — The identifier of the underlying Receivables adjustment. This is the principal join key back to adjustment header and line data and links the MRC row to its primary-currency origin.
  • SET_OF_BOOKS_ID (NUMBER, length 15) — Identifies the ledger (set of books) to which the reporting-currency amounts belong. It is essential for partitioning results by primary versus reporting ledger, especially where MRC is configured with multiple reporting currencies.
  • _LA:POSTED_FLAG also participates in the projection; together with ADJUSTMENT_ID and SET_OF_BOOKS_ID it forms the identity and filtering backbone of the view.

Common Use Cases and Queries

Typical usage centers on reporting adjusted balances in an alternate reporting currency, verifying that adjustment amounts posted to GL are complete and balanced, and extracting data for reconciliation between the primary and reporting ledgers. Because the view is a BIS object, it is safe to query directly without affecting transactional integrity.

The documented query text can be used as a starting point:

  • Full projection: SELECT FUNCTIONAL_DEBIT_AMOUNT, FUNCTIONAL_CREDIT_AMOUNT, ADJUSTMENT_ID, SET_OF_BOOKS_ID FROM APPS.ARBV_ADJ_DISTS_ALT_CRNCY;
  • Filter by ledger: Add WHERE SET_OF_BOOKS_ID = :ledger_id to isolate a specific reporting ledger.
  • Aggregate credit values: SELECT ADJUSTMENT_ID, SUM(FUNCTIONAL_CREDIT_AMOUNT) FROM APPS.ARBV_ADJ_DISTS_ALT_CRNCY GROUP BY ADJUSTMENT_ID to reconcile credit totals per adjustment.
  • Posting verification: Comparing FUNCTIONAL_DEBIT_AMOUNT and FUNCTIONAL_CREDIT_AMOUNT by ADJUSTMENT_ID confirms that debits and credits balance for each MRC adjustment. Joining SET_OF_BOOKS_ID to GL ledger views identifies which reporting currency produced the amounts.

These patterns support MRC reconciliation, GL tie-out, and reporting-currency adjustment analysis, particularly for users searching on the functional_credit_amount attribute.