Search Results ar_xla_headers_extract




Overview
Explore in AI Chat

Overview

The AR_XLA_HEADERS_EXTRACT table resides in the AR (Receivables) schema and forms part of the Oracle Subledger Accounting (XLA) extraction layer in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a transient staging table populated during the Subledger Accounting program run, providing the accounting engine with a denormalized snapshot of Receivables transaction header data required for journal entry creation and transfer to General Ledger. The table carries 46 documented columns and is classified by heuristic Data Vault analysis as standalone, suggesting a modeling approach in which this object behaves as a self-contained structure rather than participating in a traditional hub-and-link topology; it may therefore best be treated as a satellite-style staging entity keyed on the accounting event identifier.

Key Information Stored

The primary correlation key is EVENT_ID, which ties each row to a specific accounting event generated by the XLA framework. CUSTOMER_TRX_ID identifies the originating transaction header and serves as the dominant business-key candidate for joining back to Receivables transaction data. Monetary and currency attributes include BASE_CURRENCY_CODE, EXCHANGE_RATE_TYPE, EXCHANGE_RATE, and EXCHANGE_DATE, which drive conversion of transaction amounts into ledger currency. Organizational context is supplied by ORG_ID and SET_OF_BOOKS_ID, enabling multi-org and multi-ledger reporting. Receipt and payment context columns include CASH_RECEIPT_ID, RECEIPT_BATCH_ID, and RECEIVABLE_APPLICATION_ID, linking the accounting event to cash application activity. Party and site references — BILL_CUSTOMER_ID, SHIP_CUSTOMER_ID, PAYING_CUSTOMER_ID, SOLD_CUSTOMER_ID, and their corresponding site-use identifiers — capture the full customer role model. Two foreign keys are documented: RECEIPT_METHOD_ID references AR_RECEIPT_METHODS, and RECEIVABLES_TRX_ID references AR_RECEIVABLES_TRX_ALL. The columns CRH_STATUS and CRH_PRV_STATUS track processing states.

Common Use Cases and Queries

Typical usage centers on diagnosing and reconciling Subledger Accounting output. Analysts query the table to trace why a given transaction produced a specific journal entry, or to confirm that events were successfully extracted before Create Accounting execution. A representative pattern joins the extract to transaction headers:

  • Reconciliation: SELECT e.EVENT_ID, e.CUSTOMER_TRX_ID, e.EXCHANGE_RATE, e.BASE_CURRENCY_CODE FROM AR.AR_XLA_HEADERS_EXTRACT e WHERE e.CUSTOMER_TRX_ID = :trx_id;
  • Receipt method analysis: join RECEIPT_METHOD_ID to AR_RECEIPT_METHODS to attribute accounting events by payment channel.
  • Multi-org reporting: group by ORG_ID and SET_OF_BOOKS_ID to summarize extraction volumes per ledger.
  • Status monitoring: filter on CRH_STATUS and CRH_PRV_STATUS to detect incomplete or failed extractions.

Related Objects

The most significant related objects, based on documented relationships and accounting flow, include:

  • AR_RECEIPT_METHODS — joined via RECEIPT_METHOD_ID.
  • AR_RECEIVABLES_TRX_ALL — joined via RECEIVABLES_TRX_ID.
  • RA_CUSTOMER_TRX_ALL — parent transaction header, joined via CUSTOMER_TRX_ID.
  • AR_CASH_RECEIPTS_ALL — joined via CASH_RECEIPT_ID.
  • AR_RECEIVABLE_APPLICATIONS_ALL — joined via RECEIVABLE_APPLICATION_ID.
  • XLA_EVENTS and the related XLA extraction/accounting tables — joined via EVENT_ID.

These relationships make AR_XLA_HEADERS_EXTRACT a critical diagnostic link between Receivables transactional data and the Subledger Accounting engine.