Search Results doc_sequence_name




Overview
Explore in AI Chat

Overview

XLA_AR_INV_AEL_GL_V is a Subledger Accounting (XLA) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the accounting event lines generated by the Receivables (AR) invoice process, together with their General Ledger transfer attributes, in a flattened structure suitable for inquiry, reconciliation, and downstream integration. In the EBS architecture, XLA replaces the older AR_AEL and GL_JE staging tables with the unified XLA_AE_HEADERS, XLA_AE_LINES, and XLA_DISTRIBUTION_LINKS model. This view presents those lines in a report-friendly column layout resembling the legacy AEL structure, which is why it is widely used by the standard Subledger Accounting and Receivables accounting reports, as well as custom extracts.

The object is relevant to users searching on "accounting_rule_name" because accounting rule processing on invoices (for example, deferred revenue recognition schedules) determines how distributions are generated and posted. Each row in this view represents an accounted line produced by the application of an accounting rule or standard accounting method, making the view the practical starting point for tracing rule-driven accounting results.

Underlying Base Objects

Per the documented ETRM metadata, XLA_AR_INV_AEL_GL_V is defined over a single referenced base object: AR_AEL_GL_INV_V (VIEW). That intermediate view supplies the AR invoice accounting event lines joined to their General Ledger transfer information. The mapping shows the view is not defined directly over XLA base tables but over the AR-specific AEL/GL view, which itself resolves to the XLA_AE_HEADERS, XLA_AE_LINES, XLA_DISTRIBUTION_LINKS, and XLA_EVENTS entity model together with the GL_JE_HEADERS and GL_JE_LINES tables for posted journals.

Because the lineage passes through AR_AEL_GL_INV_V, the view inherits the Receivables application context (APPLICATION_ID) and the invoice transaction class filters. Several columns in the view text are defined as TO_NUMBER(NULL) or NULL (for example AEH_ID, TAXABLE_ENTERED_DR, TRANSFER_SYSTEM, and ACCOUNTING_COMPLETE). These placeholders preserve positional compatibility with the legacy AR_AEL_GL view structure, but they do not carry data in this version and should not be relied upon in custom queries.

Key Columns

Common Use Cases and Queries

The most frequent uses are invoice-to-GL reconciliation, unposted accounting review, tax and revenue analysis, and feeding external reporting or data warehouses. A typical reconciliation query filters by ledger, accounting period, and transaction class:

  • SELECT TRX_NUMBER_DISPLAYED, ACCT_LINE_TYPE_NAME, ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR, GL_TRANSFER_STATUS_NAME FROM APPS.XLA_AR_INV_AEL_GL_V WHERE SET_OF_BOOKS_ID = :ledger AND TRUNC(ACCOUNTING_DATE) BETWEEN :start_date AND :end_date AND TRX_CLASS = 'INV'
  • To identify lines not yet transferred to GL, add a predicate on the transfer status name, for example WHERE GL_TRANSFER_STATUS_NAME = 'Not Transferred', which isolates accounting awaiting the Create Accounting and Transfer Journal Entries to GL programs.
  • To analyze deferred revenue generated by accounting rules, join to the AR distributions or to RA_CUSTOMER_TRX_LINES and filter on ACCT_LINE_TYPE_NAME to separate revenue and unbilled receivable lines.
  • Because the view shares the column layout of the legacy AR_AEL_GL view, existing custom reports and Discoverer workbooks built on the older structure can be repointed with minimal column changes.

Note that the view is read-only and reflects data at the time of query; the accounting_rule_name attribute frequently sought by users is not exposed as a column here and must be obtained by joining the underlying XLA event/distribution tables (for example XLA_DISTRIBUTION_LINKS and RA_RULES) or the AR transaction line record. Queries should always constrain on a ledger and date range to avoid full scans of the XLA tables.