Search Results aeh_accounting_error_code




Overview
Explore in AI Chat

Overview

XLA_OKL_AEL_GL_CTR_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, categorized under the XLA (Subledger Accounting) product family. It functions as a presentation and compatibility layer that exposes Oracle Lease Management (OKL) accounting event line data in the column layout expected by the Subledger Accounting (XLA) and General Ledger (GL) transfer engine. The view name itself encodes its purpose: OKL identifies the source application (Lease Management), AEL denotes Accounting Event Lines, and GL_CTR reflects the GL transfer control context. In ETRM 12.2.2 the object is documented as VALID, meaning it is compiled and usable at runtime.

The primary role of this view is to normalize the join between an accounting header (AEH) and its accounting lines (AEL) so that downstream XLA components, particularly the Create Accounting and Transfer to GL processes, can consume lease-related distribution lines uniformly. Because the ETRM metadata references an underlying OKL_AEL_GL_CTR_V, XLA_OKL_AEL_GL_CTR_V acts as the XLA-facing counterpart of the OKL-specific view, mirroring column names such as JE_HEADER_ID, AEL_TABLE, and GL_TRANSFER_STATUS.

Underlying Base Objects

The documented base objects referenced by this view are:

  • OKL_AEL_GL_CTR_V (VIEW) — the principal data source; the XLA view projects its rows and columns.
  • OKL_ACCOUNTING_UTIL (PACKAGE) — supplies accounting utility logic used in the definition for deriving account and event attributes.
  • OKC_UTIL (PACKAGE) — provides general contract/lease utility functions supporting value derivation.
  • ARP_ADDR_LABEL_PKG (PACKAGE) — a Receivables address label package, included for third-party or party-label resolution.

Only the package references are explicitly listed as base objects; the effective row source is the OKL_AEL_GL_CTR_V view, which in turn joins OKL accounting event headers and lines. The XLA view does not itself own tables — it is a derived, non-updatable projection.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling lease accounting distributions, auditing GL transfer completeness, and diagnosing which AEL_TABLE sourced a given accounting line.

SELECT je_header_id, je_line_num, ael_id, ael_table,
       code_combination_id, accounted_dr, accounted_cred,
       gl_transfer_status
FROM   apps.xla_okl_ael_gl_ctr_v
WHERE  set_of_books_id = :p_sob_id
AND    accounting_date BETWEEN :p_from AND :p_to;

A second common pattern audits unposted lease lines:

SELECT trx_number_displayed, trx_class_name, count(*)
FROM   apps.xla_okl_ael_gl_ctr_v
WHERE  gl_transfer_status != 'Y'
GROUP  BY trx_number_displayed, trx_class_name;

Because many descriptive columns are NULL placeholders, queries should restrict output to the populated accounting and identifier columns.