Search Results ar_xla_lines_extract

Overview

AR_XLA_LINES_EXTRACT is a Receivables (AR) staging table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schemas. It is the line-level counterpart to the Receivables extract structures used by the Subledger Accounting (XLA) and Create Accounting engine. The table holds flattened, transaction-grain accounting attribute data for Receivables source transactions — invoices, credit memos, debit memos, receipts, applications, adjustments, and tax lines — which the XLA engine consumes to generate subledger journal entries in the SLA data model.

The "EXTRACT" suffix is significant: rather than representing permanent transactional state, the table functions as a working/staging area populated during the Create Accounting and Transfer to GL processes. Rows are written by the Receivables accounting program, read by the XLA accounting engine, and typically purged or reused after the accounting event completes. The 110 documented columns confirm this is a wide, denormalized structure optimized for rapid consumption by the accounting engine rather than normalized transactional storage.

The heuristic Data Vault classification provided in the metadata is standalone. As a modeling suggestion, this indicates the table has no foreign key relationships that would place it as a traditional hub or link. However, the presence of EVENT_ID, LINE_ID, ENTITY_CODE, and EVENT_TYPE_CODE columns strongly suggests the table behaves as a satellite-like staging object keyed to an XLA accounting event. Practitioners modeling this data for a warehouse should treat it as an event-scoped satellite anchored on EVENT_ID and LINE_ID rather than a free-standing hub.

Key Information Stored

The table's surrogate primary key is LINE_ID, with EVENT_ID as the foreign reference back to the parent accounting event in XLA_EVENTS. The combination of EVENT_ID and LINE_NUMBER forms the natural business key for a distinct accounting line.

• EVENT_ID — Reference to the parent XLA accounting event header.
• LINE_ID / LINE_NUMBER — Surrogate and sequential identifier for each extracted accounting line.
• EVENT_TYPE_CODE / EVENT_CLASS_CODE / ENTITY_CODE — XLA accounting event classification used to determine which Journal Line Type rules apply.
• SOURCE_ID / SOURCE_TABLE — Polymorphic reference back to the originating Receivables transaction.
• CUSTOMER_TRX_ID / CUSTOMER_TRX_LINE_ID — The invoice header and line generating the entry.
• CASH_RECEIPT_ID / RECEIVABLE_APPLICATION_ID — Receipt and cash application context for receipt-based events.
• AMOUNT / ACCTD_AMOUNT / TAXABLE_ACCTD_AMOUNT — Entered and accounted monetary values used for journal amounts.
• CURRENCY_CODE / EXCHANGE_RATE / EXCHANGE_RATE_TYPE / EXCHANGE_DATE — Foreign currency conversion attributes.
• LEDGER_ID / SET_OF_BOOKS_ID — Target ledger for the resultant journal entry.
• DIST_CCID / PAIRED_CCID / REF_DIST_CCID — Accounting flexfield code combinations for the debit, credit, and reference distributions.
• POSTING_ENTITY / BUSINESS_FLOW_CODE / REVERSAL_CODE — Posting control and flow metadata.
• TAX_LINE_ID — Foreign key to ZX_LINES, linking to the tax detail line.
• ORG_ID — Multi-org operating unit discriminator.
• ADDITIONAL_CHAR1–5 / ADDITIONAL_ID1–5 — Extensible attribute columns available for custom accounting rule derivation.

Documented foreign keys reference RA_CUST_TRX_LINE_SALESREPS_ALL (CUST_TRX_LINE_SALESREP_ID), AR_RECEIPT_METHODS (RECEIPT_METHOD_ID), AR_RECEIVABLES_TRX_ALL (RECEIVABLES_TRX_ID), and ZX_LINES (TAX_LINE_ID), confirming both transaction and tax lineage.

Common Use Cases and Queries

Primary use cases include: diagnosing why a specific invoice or receipt generated (or failed to generate) a journal entry; extracting accounting attribute values for reconciliation to the General Ledger; auditing the tax line linkage for receivable tax rules; and building custom subledger reporting where standard XLA views are insufficient.

A representative diagnostic query traces an invoice to its extracted lines:

• Join AR_XLA_LINES_EXTRACT to XLA_EVENTS on EVENT_ID, filtering CUSTOMER_TRX_ID to inspect every accounting line candidate.
• Join to ZX_LINES on TAX_LINE_ID = ZX_LINES.TAX_LINE_ID to trace tax amounts.
• Join RA_CUST_TRX_LINE_SALESREPS_ALL on CUST_TRX_LINE_SALESREP_ID for sales credit allocation detail.
• Aggregate ACCTD_AMOUNT by EVENT_TYPE_CODE and LEDGER_ID to summarize extract totals against GL balances.

Because the table is staging in nature, reporting against it is best performed in the context of a specific accounting batch run or after a Create Accounting execution, rather than as a historical data source.

Related Objects

Significant related objects, drawn from the documented relationships and the Receivables/XLA architecture, include the following:

• XLA_EVENTS — Parent accounting event header; joined on EVENT_ID.
• XLA_AE_HEADERS / XLA_AE_LINES — Downstream generated journal entries derived from this extract.
• ZX_LINES — Tax detail lines; joined on TAX_LINE_ID.
• RA_CUST_TRX_LINE_SALESREPS_ALL — Sales credit allocation; joined on CUST_TRX_LINE_SALESREP_ID.
• AR_RECEIPT_METHODS — Receipt method reference for receipt events; joined on RECEIPT_METHOD_ID.
• AR_RECEIVABLES_TRX_ALL — Receivables transaction type set; joined on RECEIVABLES_TRX_ID.
• RA_CUSTOMER_TRX_ALL / RA_CUSTOMER_TRX_LINES_ALL — Invoice header and line sources referenced by CUSTOMER_TRX_ID and CUSTOMER_TRX_LINE_ID.
• AR_CASH_RECEIPTS_ALL — Receipt source for cash events; joined on CASH_RECEIPT_ID.
• AR_XLA_HEADERS_EXTRACT — The companion header-grain extract table.