Search Results ael_table




Overview
Explore in AI Chat

Overview

AR_AEL_GL_REC_ALL_V is a Receivables subledger accounting view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It exposes the accounted journal lines created by the Subledger Accounting (SLA) engine for Receivables transactions, alongside the corresponding General Ledger transfer status information. The suffix "REC" indicates that the view is restricted to Receivables accounting event lines, while "ALL" denotes that it is the superset variant — it presents both the standard accounted line set and the cross-business-unit or "CB" (cross-business) accounting lines, layered alongside one another through a UNION ALL construct.

The view is the primary reporting and reconciliation interface between Receivables subledger data and the GL interface. It enables functional and technical users to trace an accounting entry from its originating transaction (invoice, credit memo, debit memo, receipt, adjustment, or chargeback) through to its accounting event, journal header, and journal line, and to determine whether that line has been transferred, posted, or remains pending in the GL interface. The AEL_ID column, which the user searched for, is the unique identifier of the subledger accounting entry line and serves as the principal join key to the XML accounting and error tables.

Underlying Base Objects

The view is defined over two principal accounting views and several supporting PL/SQL packages:

  • AR_AEL_GL_REC_V — the standard Receivables accounted journal lines view (single business unit).
  • AR_AEL_GL_CB_REC_V — the cross-business accounting lines view, providing the "ALL" scope.
  • ARPT_SQL_FUNC_UTIL — provides SQL functions used to derive descriptive names such as transaction class name, line type name, and third-party name.
  • FND_GLOBAL, FND_PROFILE, FND_ACCESS_CONTROL_UTIL — supply runtime context: user ID, responsibility, org context, and security/multi-org access predicates.
  • MO_GLOBAL — provides multi-org (operating unit) security filtering.
  • XTR_USER_ACCESS — supplies user-level access restrictions where applicable.

The view resolves org and security predicates dynamically at query time, which means it is not a simple join against static base tables; its output is filtered by the session's profile and access-control settings.

Key Columns

Several placeholder columns (TRX_NUMBER_N, TRX_TYPE_C, REQUEST_ID, INVENTORY_ITEM_ID) are populated with NULL casts to preserve a uniform column signature across the "ALL" union.

Common Use Cases and Queries

Because AEL_ID is the searched key, the most frequent query is a direct lookup of an accounting entry and its GL transfer state:

  • Retrieving the accounting detail for a specific entry: SELECT ael_id, je_header_id, je_line_num, gl_transfer_status_name, accounted_dr, accounted_cr FROM ar_ael_gl_rec_all_v WHERE ael_id = :ael_id;
  • Reconciling Receivables to GL for a period: filter on ACCOUNTING_DATE and SET_OF_BOOKS_ID, and group by GL_TRANSFER_STATUS_NAME to identify lines not yet transferred.
  • Auditing a customer's account activity by joining THIRD_PARTY_NAME or TRX_NUMBER_DISPLAYED to transaction data.
  • Investigating SLA posting errors by joining AEL_ID back to the SLA event and error tables.

In all cases, results are automatically filtered by the operating unit and access-control context of the querying session, so callers must ensure the correct org context is initialised before relying on row counts or totals.