Results for “xla_ap_pay_ael_sl_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XLA_AP_PAY_AEL_SL_V is a Subledger Accounting (XLA) view exposed within Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the accounting event lines (AEL) generated for Oracle Payables payment transactions, combined with the corresponding subledger (SL) accounting detail. The view is used primarily as a reporting and integration surface for payment-related journal entries produced by the Create Accounting process, allowing cleared, accounted payment activity to be retrieved in a form similar to a general ledger journal line collection.

The view name reflects its lineage: the XLA_AP_PAY_AEL_SL_V convention denotes an XLA-owned object, sourced from the AP (Payables) application, scoped to the PAY (payment) event class, drawing from AEL and SL tables. Users commonly search for the alias ap_ael_sl_pay_v, which refers to this same object. ETRM documentation records it as "Not implemented in this database" for the documented instance, so availability depends on whether Subledger Accounting has been configured and whether accounting has been created for the relevant payment events.

Underlying Base Objects

The documented view text is a union-style projection over the XLA accounting line tables—principally XLA_AE_HEADERS (AEH), XLA_AE_LINES (AEL), and the associated accounting event structure. The column set confirms this lineage: AEH_ID and AEL_ID are the account entry header and line identifiers, while AE_LINE_REFERENCE appears both as a public column and as AE_LINE_REFERENCE_INTERNAL, characteristic of subledger accounting line joins. Because the ETRM metadata lists no separately documented base objects, the view should be treated as an XLA-owned reporting layer whose physical tables are the standard Subledger Accounting schema objects. For the Payables context specifically, it is associated with the payment event class and links to AP payment transactions through SOURCE_ID and SOURCE_TABLE.

Key Columns

The view exposes a broad set of accounting, currency, and party attributes:

• ACCOUNTED_DR / ACCOUNTED_CR and ENTERED_DR / ENTERED_CR — journal amounts in ledger (accounted) and entered currency terms.
• ACCOUNTING_DATE, CURRENCY_CODE, and the conversion columns (CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_TYPE) — control the posting date and currency translation of each line.
• AEH_ID / AEL_ID / AE_LINE_REFERENCE — internal identifiers linking back to the accounting event headers and lines.
• CODE_COMBINATION_ID — the accounting flexfield combination used for the journal line.
• GL_TRANSFER_STATUS / GL_TRANSFER_STATUS_NAME / TRANSFER_STATUS_DETAIL_NAME — indicate whether the line has been transferred and posted to General Ledger.
• TRX_CLASS_NAME, TRX_TYPE_NAME, TRX_DATE, TRX_NUMBER_DISPLAYED, and TRX_HDR_ID — identify the transaction class, type, and displayed document number of the underlying payment.
• THIRD_PARTY_NAME / THIRD_PARTY_NUMBER and their subtype columns — identify the supplier or other party associated with the line.
• ORG_ID, SET_OF_BOOKS_ID, SOURCE_ID, and SOURCE_TABLE — provide organizational and source context, with ACCT_LINE_TYPE_NAME describing the accounting line type.

Common Use Cases and Queries

Typical uses include reconciling payment accounting entries to General Ledger, validating that payment events were accounted and transferred, and extracting supplier-level journal detail for audit or reporting. A representative query returns accounted payment lines by transaction number and period:

SELECT trx_number_displayed, accounting_date,
       accounted_dr, accounted_cr, currency_code,
       third_party_name, gl_transfer_status_name
FROM   xla_ap_pay_ael_sl_v
WHERE  trx_date BETWEEN :start_date AND :end_date
AND    org_id = :org_id
ORDER BY trx_number_displayed, accounting_date;

A second common pattern checks transfer status for posted payments:

SELECT ael_id, gl_transfer_status_name,
       transfer_status_detail_name, code_combination_id
FROM   xla_ap_pay_ael_sl_v
WHERE  gl_transfer_status_name <> 'Yes';

Because the view is not implemented in every database, queries should be preceded by a check against ALL_VIEWS to confirm availability before use in packaged reporting or integrations.