Search Results crh_prv_status




Overview
Explore in AI Chat

Overview

AR.AR_XLA_HEADERS_EXTRACT is a global temporary table (GTT) in the Oracle E-Business Suite Receivables (AR) schema. It functions as a staging structure within the Subledger Accounting (SLA / XLA) architecture, holding the header-level attribute set passed to the accounting engine during the creation of subledger journal entries. Rows are populated at runtime by the Receivables accounting program (Create Accounting), consumed by the XLA event model, and then discarded. As a global temporary table, data is visible only to the session that inserted it, and the documented data duration is SYS$TRANSACTION, meaning rows are purged at transaction commit or rollback. The table carries 46 documented columns and a single non-unique index, AR_XLA_HEADERS_EXTRACT_N1, on EVENT_ID. Storage attributes are PCT Free 10 and PCT Used 40, which is typical for a short-lived, high-churn staging object. Based on a heuristic Data Vault classification (standalone, with no functional foreign keys to other hubs), this object is best modeled as a temporary satellite attached to the accounting event hub, carrying descriptive attributes for a single extraction cycle rather than persisting business history.

Key Information Stored

The table’s grain is one row per accounting event header. It has no surrogate primary key; EVENT_ID is the dominant business-key candidate and the only indexed column, linking the extract to the XLA events and journal header lines created downstream. CUSTOMER_TRX_ID identifies the originating transaction in RA_CUSTOMER_TRX_ALL, while AGREEMENT_ID, PAYMENT_SCHEDULE_ID, and DISTRIBUTION_SET_ID tie the event to Receivables agreements and scheduling structures.

The strongest candidates for extraction and reporting are the party and site identifiers. SHIP_CUSTOMER_ID, BILL_CUSTOMER_ID, DRAWEE_CUSTOMER_ID, PAYING_CUSTOMER_ID, and SOLD_CUSTOMER_ID represent the respective customer roles, complemented by SHIP_SITE_USE_ID, BILL_SITE_USE_ID, DRAWEE_SITE_USE_ID, PAYING_SITE_USE_ID, and SOLD_SITE_USE_ID for the associated site uses, plus BILL_CUST_ROLE_ID, SHIP_CUST_ROLE_ID, DRAWEE_CUST_ROLE_ID, and SOLD_CUST_ROLE_ID for role definitions. Bank and remittance data is captured through CUSTOMER_BANK_ACCT_ID, DRAWEE_BANK_ACCOUNT_ID, REMITTANCE_BANK_ACCT_ID, CUSTOMER_BANK_BRANCH_ID, ISSUER_BANK_BRANCH_ID, and REMIT_ADDRESS_ID. Accounting context is supplied by ORG_ID, SET_OF_BOOKS_ID, BASE_CURRENCY_CODE, EXCHANGE_RATE_TYPE, EXCHANGE_RATE, and EXCHANGE_DATE. Receipt-related columns include CASH_RECEIPT_ID, RECEIPT_BATCH_ID, RECEIPT_METHOD_ID, RECEIVABLE_APPLICATION_ID, and RECEIVABLES_TRX_ID (with ED_ADJ_ and UNED_ variants).

Common Use Cases and Queries

Typical usage is diagnostic and reconciliation-oriented. Because the table is populated only during a concurrent Create Accounting run, queries must be executed from the same session or while the run is active.

  • Verifying which ship-to customer was passed into accounting for a transaction: SELECT event_id, customer_trx_id, ship_customer_id, ship_site_use_id FROM ar.ar_xla_headers_extract WHERE customer_trx_id = :trx_id;
  • Reconciling SLA headers to source transactions by joining on CUSTOMER_TRX_ID to RA_CUSTOMER_TRX_ALL and returning BALANCING_SEGMENT or TRX_NUMBER.
  • Confirming the Receivables transaction type and receipt method routed into the event: join RECEIVABLES_TRX_ID to AR_RECEIVABLES_TRX_ALL.
  • Validating exchange rate details for foreign-currency events via EXCHANGE_RATE_TYPE, EXCHANGE_RATE, and EXCHANGE_DATE.
  • Supporting custom SLA rules or diagnostics that reference attribute values such as SHIP_CUSTOMER_ID or SALESREP_ID at header level.

Related Objects