Search Results ar_distributions_l_v




Overview
Explore in AI Chat

Overview

The AR_DISTRIBUTIONS_L_V view is an Oracle Receivables (AR) dictionary object owned by the APPS schema and marked VALID in the E-Business Suite 12.1.1 and 12.2.2 environments. ETRM documents its description as "distribution line extract." Functionally, the view is not a general-purpose ledger inquiry object; it is a purpose-built extraction source that feeds Subledger Accounting (SLA/XLA) processing and downstream reporting by presenting AR distribution lines in the exact columnar shape required by the accounting extract engine. It reconciles three streams that must be combined before a subledger journal can be created: the accounting distributions themselves, the SLA line-extract row that carries event and ledger context, and the associated receipt/application or transaction source identifiers.

Because the view carries a DISTRIBUTION_TYPE literal, party attributes, tax link references, and paired cost-combination (CCID) information, it occupies the boundary between the raw transactional data in AR and the generalized extract format consumed by the XLA framework. In this sense it behaves as the bridge that allows AR distributions to be turned into journal entries and to be surfaced to reporting tools without the caller needing to join AR and XLA tables manually.

Underlying Base Objects

The documented 12.2.2 metadata lists the following referenced base objects:

Structurally, the view is a UNION over AR distribution sources. The visible predicate set restricts to POSTING_ENTITY = 'ADJ', matching SOURCE_ID and SOURCE_TABLE between the extract line and the distribution, LEVEL_FLAG = 'L' (line level only) and MFAR_ADDITIONAL_ENTRY = 'N' (excludes multi-fund additional entries).

Key Columns

Common Use Cases and Queries

Typical uses include SLA journal reconciliation, distribution-level reporting and debugging of accounting extract generation, and data verification prior to posting. A representative query retrieves entered amounts by ledger and event:

SELECT event_id, dist_line_id, dist_code_combination_id,
       dist_ent_amt, dist_currency_code, dist_party_id
  FROM ar_distributions_l_v
 WHERE ledger_id = :p_ledger_id;

Another common pattern traces a distribution to its originating transaction or receipt through the SOURCE columns, or reconciles the extract back to AR_DISTRIBUTIONS_ALL on DIST_LINE_ID and SOURCE_ID. Because the view is defined in APPS and restricted to POSTING_ENTITY = 'ADJ' at line level, callers should not treat it as a complete ledger of all AR accounting entries; it is specifically the adjustment-oriented distribution line extract supplied for the subledger accounting pipeline.