Search Results xla_req_enc_ael_gl_v




Overview
Explore in AI Chat

Overview

XLA_REQ_ENC_AEL_GL_V is a Subledger Accounting (XLA) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is one of the family of "AEL_GL" interface views used by the Create Accounting process and by the Subledger Accounting reporting layer. The view exposes accounting event line (AEL) data structured to resemble the columns of the General Ledger interface and the XLA_AE_LINES/GL_JE_LINES repositories, allowing subledger accounting entries to be consumed by downstream programs such as the Journal Import, GL transfer, and reconciliation reports without the caller needing to know the physical storage layout. The view is documented as VALID and is intended primarily for internal EBS use; Oracle does not publish a supported public API around it, so queries should be treated as read-only diagnostic or reporting access. Because the view carries the TRX_NUMBER_N column, applications and custom reports frequently join to it to display or filter by a transaction number, which is the attribute most often associated with searches against this object.

Underlying Base Objects

The documented metadata identifies the view as defined over REQ_ENC_AEL_GL_V, itself a subledger accounting view, together with the standard SYSADMIN support packages FND_GLOBAL, HR_GENERAL and HR_SECURITY. FND_GLOBAL supplies session context functions such as USER_ID, RESP_ID and ORG_ID; HR_GENERAL and HR_SECURITY supply organization-level security predicates. The view therefore inherits the row-level security behavior applied to REQ_ENC_AEL_GL_V, meaning that visible rows are restricted by the operating unit and responsibility under which the query is executed. The union-style projection in the view text maps AEL attributes onto GL-style column names and pads unsupported XLA columns with NULLs (for example ACCT_LINE_TYPE, AEH_ID, AEL_ID, DOC_SEQUENCE_ID, GL_TRANSFER_STATUS, SOURCE_ID, TAXABLE_* and THIRD_PARTY_* are hard-coded NULL). This design preserves column-count compatibility with other members of the XLA AEL_GL view family while indicating which attributes are not applicable to this particular encoding.

Key Columns

Common Use Cases and Queries

The view is typically queried to reconcile subledger accounting output to GL, to trace a transaction number back to its journal entry, or to inspect amounts and conversion details for a given ledger and period. A typical lookup by transaction number follows:

  • Transaction lookup: SELECT trx_number_n, je_header_id, je_line_num, accounted_dr, accounted_cred FROM xla_req_enc_ael_gl_v WHERE trx_number_n = :trx_number_n;
  • GL reconciliation: SELECT je_header_id, SUM(accounted_dr), SUM(accounted_cr) FROM xla_req_enc_ael_gl_v WHERE set_of_books_id = :ledger_id AND accounting_date BETWEEN :start_date AND :end_date GROUP BY je_header_id;
  • Multi-currency review: SELECT trx_number_n, currency_code, currency_conversion_rate, currency_conversion_type FROM xla_req_enc_ael_gl_v WHERE trx_number_n = :trx_number_n;

Because the view is secured through HR_SECURITY and FND_GLOBAL, results depend on the responsibility and operating unit of the session, and columns documented as NULL (for example GL_TRANSFER_STATUS and ACCT_LINE_TYPE) should not be relied upon for status reporting; query XLA_AE_HEADERS and XLA_AE_LINES directly when full subledger accounting detail is required.