Search Results ar_xla_lines_extract_n1




Overview
Explore in AI Chat

Overview

APPS.AR_RECEIPT_HISTORY_H_V is a reporting and integration view within the Oracle E-Business Suite Receivables (AR) module, documented under ETRM 12.2.2 and equally applicable to 12.1.1. The view presents receipt history information at the header level, drawing together cash receipt history records and their associated Subledger Accounting (SLA) extract event data. It is primarily intended for consumption by Oracle Subledger Accounting and by the XLA (eXtended Ledger Architecture) extraction processes that feed accounting event models. Because the view is header-level (the level_flag = 'H' predicate is used throughout the defining query), it returns one logical row per receipt history event rather than per distribution line.

A distinguishing characteristic of this view is that it carries an explicit optimizer hint, /*+INDEX(HE AR_XLA_LINES_EXTRACT_N1)*/, on the driving table. This directly references the AR_XLA_LINES_EXTRACT_N1 index — the exact term the user searched for — indicating that the index is used to drive extraction of SLA line records efficiently during receipt accounting processing.

Underlying Base Objects

The documented base objects referenced by the view are:

  • AR_CASH_RECEIPT_HISTORY_ALL — the primary source of receipt history rows, including GL dates, statuses, reversal references, and descriptive flexfield attributes.
  • AR_RECEIVABLE_APPLICATIONS_ALL — used to associate receipt history records with application events, joined outer-style on event_id and cash_receipt_history_id.
  • AR_XLA_LINES_EXTRACT — the SLA extract table that supplies the accounting event identifiers; the driving table in the inline view, aliased l and he.

The view joins the extract table to a derived aggregate set (ev) that resolves, per event, the appropriate "original" event ID using MAX(DECODE(l.crh_status,'', c.event_id, l.event_id)). This handles receipt reversals by mapping to either the original or reversal event depending on the CRH status. The view then self-joins AR_CASH_RECEIPT_HISTORY_ALL as crh and crh1 to surface both current and reversal GL dates and statuses.

Key Columns

Common Use Cases and Queries

This view is typically queried to reconcile receipt activity with SLA events, to investigate reversal behavior, or to retrieve receipt descriptive attributes during subledger accounting diagnostics.

  • Identifying receipts whose SLA events did not resolve to a current history record.
  • Reporting reversals by comparing CRH_REVERSAL_GL_DATE against CRH_GL_DATE.
  • Diagnosing performance of extraction by verifying the use of AR_XLA_LINES_EXTRACT_N1 in an execution plan.

A representative query follows:

SELECT crh_cash_receipt_history_id, eb.event_id, crh_gl_date, crh_status, crh_reversal_gl_date
FROM apps.ar_receipt_history_h_v
WHERE crh_status = 'REVERSED';