Results for “xla_distribution_links”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The XLA.XLA_DISTRIBUTION_LINKS table is a core Subledger Accounting (XLA) repository in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the association between a source subledger transaction and the subledger journal entry lines that were generated from it by the accounting program. Each row represents a single distribution line item — an accounting line, tax line, gain/loss line, or allocation line — and captures the reference back to the transaction as well as the applied-to and allocated-to references used in multi-line accounting relationships. Because Subledger Accounting sits between the subledgers (Payables, Receivables, Assets, Cost Management, etc.) and the General Ledger, this table is central to drill-down, traceability, and reconciliation between transactional data and journal entries. The table resides in the XLA schema, is marked VALID, and contains 85 documented columns in the 12.2.2 physical schema. From a Data Vault modeling perspective, the metadata heuristic classifies this object as standalone, though its composite primary key and reference columns exhibit link-like behavior, suggesting it could also be modeled as a link between transaction events and journal entry lines.

Key Information Stored

The documented primary key is XLA_DISTRIBUTION_LINKS_PK, composed of EVENT_ID, AE_HEADER_ID, AE_LINE_NUM, and APPLICATION_ID. Together these columns uniquely identify the link between an accounting event and a specific subledger journal entry line.

• EVENT_ID — the accounting event identifier from XLA_EVENTS, tying the row to the source transaction event.
• AE_HEADER_ID and AE_LINE_NUM — the subledger journal entry header and line number identifying the generated accounting entry.
• APPLICATION_ID — the owning subledger application, distinguishing the source product.
• REF_EVENT_ID, REF_AE_HEADER_ID, and REF_TEMP_LINE_NUM — reference pointers to related events and entries, including references to temporary line numbers used during accounting generation.
• TEMP_LINE_NUM — the temporary line number during construction; the unique index XLA_DISTRIBUTION_LINKS_U1 on (APPLICATION_ID, REF_AE_HEADER_ID, TEMP_LINE_NUM, AE_HEADER_ID) serves as a documented business-key candidate.
• SOURCE_DISTRIBUTION_TYPE along with SOURCE_DISTRIBUTION_ID_CHAR_1..5 and SOURCE_DISTRIBUTION_ID_NUM_1..5 — the source-side distribution identity, capturing the transaction distribution that generated the line.
• ACCOUNTING_LINE_CODE, ACCOUNTING_LINE_TYPE_CODE, and ACCOUNTING_LINE_TYPE_CODE-related flags (CALCULATE_ACCTD_AMTS_FLAG, CALCULATE_G_L_AMTS_FLAG) — describe the nature of the accounting line.
• UNROUNDED_ENTERED_DR, UNROUNDED_ENTERED_CR, UNROUNDED_ACCOUNTED_DR, UNROUNDED_ACCOUNTED_CR, DOC_ROUNDING_ENTERED_AMT, and DOC_ROUNDING_ACCTD_AMT — the pre-rounding and rounding amounts applied at document level, governed by ROUNDING_CLASS_CODE and DOCUMENT_ROUNDING_LEVEL.
• STATISTICAL_AMOUNT — any statistical quantity associated with the line.
• APPLIED_TO_* and ALLOC_TO_* column families — capture cross-line relationships, such as the distribution to which an amount was applied (cash application, discounts) or allocated (cost allocations).
• GAIN_OR_LOSS_REF — identifies gain or loss reference lines arising from foreign currency or revaluation events.
• UPG_BATCH_ID — a foreign key to XLA_UPG_BATCHES, used during upgrade processing.

Common Use Cases and Queries

This table is primarily queried for drill-down and reconciliation reporting. Typical scenarios include tracing a subledger journal entry line back to its originating transaction, reconciling source transaction amounts to accounted amounts, and investigating rounding or gain/loss differences.

A sample join to find the journal entry lines for a given event:

• Query: SELECT ae_header_id, ae_line_num, accounting_line_code FROM xla_distribution_links WHERE event_id = :event_id AND application_id = :app_id;

Reconciliation of accounted versus entered amounts uses the rounding columns:

• Query: SELECT event_id, ae_header_id, ae_line_num, unrounded_entered_dr, unrounded_accounted_dr, doc_rounding_acctd_amt FROM xla_distribution_links WHERE rounding_class_code IS NOT NULL;

Reporting use cases include subledger-to-GL reconciliation extracts, tax line traceability (via TAX_LINE_REF_ID and TAX_SUMMARY_LINE_REF_ID), and analysis of applied-to versus allocated-to chains to understand cash application or cost allocation flows.

Related Objects

Significant objects that reference or are referenced by this table include:

• XLA_UPG_BATCHES — referenced by XLA_DISTRIBUTION_LINKS.UPG_BATCH_ID (documented foreign key), used during upgrade batch processing.
• XLA_EVENTS — joined via EVENT_ID to retrieve source event details.
• XLA_AE_HEADERS — joined via AE_HEADER_ID for journal entry header information.
• XLA_AE_LINES — joined via AE_HEADER_ID and AE_LINE_NUM for journal entry line detail.
• XLA_TRANSACTION_ENTITIES — provides the transaction entity context linked through the event.
• GL_JE_LINES and GL_JE_HEADERS — the eventual General Ledger destination for posted entries.
• Subledger-specific source tables (e.g., AP_INVOICE_DISTRIBUTIONS_ALL, AR_CASH_RECEIPT_HISTORY_ALL) — referenced through SOURCE_DISTRIBUTION_TYPE and the SOURCE_DISTRIBUTION_ID_* columns.

These relationships make XLA_DISTRIBUTION_LINKS the connective tissue for subledger accounting traceability, enabling end-to-end reporting from source transaction to General Ledger entry.