Search Results okl_ael_sl_v




Overview
Explore in AI Chat

Overview

OKL_AEL_SL_V is a sub-ledger accounting (SLA) view owned by the APPS schema within the Oracle Lease and Finance Management (OKL) module. It exposes the accounting entries generated for all contract, asset, and quote transactions processed by ETRM, presenting them in a flattened, report-friendly structure for the Sub-ledger Accounting architecture. Its principal role is to allow the accounting entries associated with each Lease transaction to be displayed and reconciled, particularly during the Create Accounting process and subsequent transfer to the General Ledger. The view carries a fixed APPLICATION_ID of 540, identifying the OKL application to downstream consumers such as SLA reports, diagnostics, and custom inquiries aimed at validating the accounting impact of lease events.

Because the view consolidates header and line information, it is the natural starting point for any investigation into how a lease transaction was accounted — including the accounting line type driving each journal line — in both EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over the following documented base objects and synonyms: OKL_AE_HEADERS, OKL_AE_LINES_ALL, OKL_AE_TEMPLATES_ALL, OKL_ACC_EVENTS_ALL, OKL_TRX_CONTRACTS_ALL, OKL_TXL_CNTRCT_LNS_ALL, OKL_TRX_ASSETS, OKL_TXL_ASSETS_B, OKL_TRX_TYPES_B, OKL_STRM_TYPE_V, and OKL_ACCOUNTING_UTIL (a package). It also references GL_JE_CATEGORIES, GL_JE_CATEGORIES_VL, and GL_DAILY_CONVERSION_TYPES for journal category and currency conversion descriptions.

The accounting event header (OKL_AE_HEADERS) supplies the set of books, org, accounting date, GL transfer flag, and journal category; the event lines (OKL_AE_LINES_ALL) supply the accounted and entered debit/credit amounts, code combination, and the critical AE_LINE_TYPE_CODE. Transaction contracts, contract lines, assets, and transaction types enrich each row with lease-specific context such as the transaction line number, currency, and asset description.

Key Columns

Common Use Cases and Queries

A frequent requirement is to review the accounting line types generated for a specific lease transaction prior to GL transfer:

SELECT accounting_event_number, accounting_line_number,
       acct_line_type, acct_line_type_name,
       accounted_dr, accounted_created_cr, code_combination_id
FROM   apps.okl_ael_sl_v
WHERE  trx_line_number = :p_line
AND    gl_transfer_status = 'N';

Reconciliation queries group by ACCT_LINE_TYPE_NAME to confirm that every expected accounting line was produced and is balanced. Auditors frequently filter on GL_TRANSFER_STATUS_NAME to isolate entries not yet transferred, or join the view to GL_JE_CATEGORIES_VL via JE_CATEGORY to validate journal category mapping. Because the view resolves both line types and event types through OKL_ACCOUNTING_UTIL, it is well suited to diagnostics when accounting creation errors appear, enabling the AEH_ACCOUNTING_ERROR_CODE and AEL_ACCOUNTING_ERROR_CODE columns to be surfaced alongside each line.