Search Results dist_currency_code

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:

• ARP_XLA_EXTRACT_MAIN_PKG (PACKAGE) — the main accounting-extract procedure set that drives creation and population of extract lines.
• AR_DISTRIBUTIONS_ALL (SYNONYM) — the primary source of AR accounting distribution lines, aliased DAT in the view text.
• AR_XLA_LINES_EXTRACT (SYNONYM) — provides the SLA extract line context including EVENT_ID, LINE_NUMBER, LANGUAGE and LEDGER_ID, aliased L; a hint forces use of AR_XLA_LINES_EXTRACT_N1.
• AR_CASH_RECEIPTS_ALL, AR_RECEIVABLE_APPLICATIONS_ALL — receipt and application context for cash-based and application-driven distributions.
• AR_CASH_BASIS_DISTS_ALL — cash-basis distribution rows.
• RA_CUSTOMER_TRX_ALL and RA_CUST_TRX_TYPES_ALL — transaction header and transaction-type context.

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

• EVENT_ID — SLA accounting event identifier, the join key to XLA_EVENTS and journal headers.
• DIST_LINE_ID, DISTRIBUTION_TYPE — the distribution line identifier and a literal identifying the source table (for example 'AR_DISTRIBUTIONS_ALL').
• DIST_CODE_COMBINATION_ID — the accounting flexfield combination for the entered distribution.
• DIST_SOURCE_ID / DIST_SOURCE_ID_SECONDARY, DIST_SOURCE_TABLE / DIST_SOURCE_TABLE_SECONDARY, DIST_SOURCE_TYPE / DIST_SOURCE_TYPE_SECONDARY — identify the originating transaction or application and its table, allowing reconciliation back to RA_CUSTOMER_TRX_ALL or AR_RECEIVABLE_APPLICATIONS_ALL.
• DIST_ENT_AMT_FROM and DIST_ENT_AMT — entered amounts computed as NVL(AMOUNT_CR,0) − NVL(AMOUNT_DR,0), with the accompanying DIST_CURRENCY_CODE_FROM and DIST_CURRENCY_CODE.
• DIST_TAX_LINK_ID — link to tax distribution detail.
• LINE_NUMBER, LANGUAGE, LEDGER_ID — extract line sequencing, reporting language and ledger context carried from AR_XLA_LINES_EXTRACT.
• DIST_PAIRED_CCID and DIST_PAIRED_SOURCE_TYPE — paired cost combination and a literal 'REC', supporting pairing between receivables and revenue lines.
• DIST_PARTY_TYPE, DIST_PARTY_ID, DIST_PARTY_SITE_ID — customer party attributes derived from THIRD_PARTY_ID and THIRD_PARTY_SUB_ID, with DIST_PARTY_TYPE resolved to 'C' when a third party exists.
• DIST_REF_DIST_CCID — reference distribution combination.

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.