Search Results ae_line_reference




Overview
Explore in AI Chat

Overview

AP_AEL_SL_V is a reporting view in the Oracle E-Business Suite Payables module (AP) that consolidates Subledger Accounting (SLA) event and journal line data for Payables transactions. The "AEL" and "AEH" tokens in the name refer to the Accounting Event Lines and Accounting Event Headers underlying tables, while the "_SL_" prefix indicates the Subledger accounting context and the trailing "_V" confirms it is a view rather than a stored table. In Oracle EBS 12.1.1 and 12.2.2, this view functions as a unified presentation layer over the accounting event model, exposing accounting lines together with their transaction context so that reporting tools, reconciliations, and drill-down inquiries can retrieve debits, credits, currency conversion details, third-party information, and posting status from a single source.

The view is documented in ETRM as "Not implemented in this database," meaning it exists only as a definition (metadata) rather than installed data. It is widely used by Oracle's own Payables pages and by custom reports built on top of the SLA schema.

Underlying Base Objects

The view is defined as a UNION of at least two component views. The visible portion of the view text shows the final SELECT of the union drawing from AP_AEL_SL_INV_V, which supplies the invoice-related accounting lines. The remaining union members (typically AP_AEL_SL_PAY_V for payments and AP_AEL_SL_ADJ_V for adjustments in standard Oracle definitions) inherit the same column list. These component views in turn resolve to the Subledger Accounting tables XLA_AE_HEADERS and XLA_AE_LINES, joined to Payables transaction tables such as AP_INVOICES_ALL, AP_PAYMENT_HISTORY_ALL, and AP_ADJUSTMENTS.

The documented metadata notes "Referenced base objects: none documented," which reflects the fact that the dependency is mediated through the intermediate component views rather than being declared directly on AP_AEL_SL_V itself.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling Payables to the General Ledger, auditing accounting entries by transaction type, and building custom reports that surface invoice and payment accounting lines side by side.

Retrieve all invoice accounting lines for a transaction type:

SELECT h.trx_number_displayed, h.trx_type_c, h.trx_type_name,
       h.accounting_date, h.accounted_dr, h.accounted_cr,
       h.gl_transfer_status_name
FROM   ap_ael_sl_v h
WHERE  h.trx_type_c = 'STANDARD'
AND    h.accounting_date BETWEEN :p_from AND :p_to;

Summarize activity by transaction type and class for a period:

SELECT trx_class_name, trx_type_name,
       SUM(accounted_dr) dr_total, SUM(accounted_cr) cr_total
FROM   ap_ael_sl_v
WHERE  set_of_books_id = :p_sob
AND    accounting_date BETWEEN :p_from AND :p_to
GROUP  BY trx_class_name, trx_type_name;

Link accounting lines back to the source event for drill-down:

SELECT aeh_id, ael_id, accounting_event_number,
       accounting_event_type_name, acct_line_type_name
FROM   ap_ael_sl_v
WHERE  trx_number_c = :p_invoice_num;

Because the view is not physically materialized, queries should be filtered tightly by date, ledger, and transaction class to maintain acceptable performance in both 12.1.1 and 12.2.2 environments.