Results for “xla_fa_ael_gl_v”

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

Overview

XLA_FA_AEL_GL_V is an APPS-owned database view in Oracle E-Business Suite that belongs to the XLA (Subledger Accounting) product family. It presents subledger accounting entries originating from Oracle Assets (FA) in a shape compatible with the general ledger account analysis and AEL (Accounting Event Line) reporting model. The view is defined with status VALID and is available in both the 12.1.1 and 12.2.2 releases. It is primarily consumed by account analysis reporting, General Ledger reconciliation tools, and integration routines that expect a GL-facing column layout rather than the raw XLA AEL columns.

The view therefore acts as a compatibility layer: it re-projects the underlying Oracle Assets accounting extract into the standard accounting-entry-line shape used across the EBS financials reporting stack, allowing assets-driven journal activity to be queried alongside GL data with a consistent set of column names.

Underlying Base Objects

The documented referent for XLA_FA_AEL_GL_V is a single base object: the view FA_AEL_GL_V. This means XLA_FA_AEL_GL_V does not select directly from physical tables such as XLA_AE_HEADERS, XLA_AE_LINES, or GL_JE_LINES; it wraps FA_AEL_GL_V, which in turn presents the Assets accounting extract. The view text exposes headers and lines through surrogate identifiers JE_HEADER_ID and JE_LINE_NUM, and also carries AE_LINE_REFERENCE and AE_LINE_REFERENCE_INTERNAL to preserve the linkage back to the subledger accounting entry line.

Notably, several columns are defined as NULL or TO_NUMBER(NULL) casts. Columns such as AEH_ID, AEL_ID, DOC_SEQUENCE_ID, DOC_SEQUENCE_NAME, ORG_ID, TAXABLE_ENTERED_DR, ACCOUNTING_COMPLETE, and TRANSFER_STATUS_DETAIL_NAME are placeholders rather than populated values. This is characteristic of the AEL-to-GL bridge views, where a uniform column set must be produced even when the underlying source does not supply every attribute. Consumers should not rely on these columns containing data when querying XLA_FA_AEL_GL_V.

Key Columns

• JE_HEADER_ID, JE_LINE_NUM — the journal header and line identifiers used to key the accounting entry.
• ACCOUNTED_DR, ACCOUNTED_CR, ENTERED_DR, ENTERED_CR — accounted and entered debit/credit amounts for the line.
• ACCOUNTING_DATE, TRX_DATE — the GL accounting date and the originating transaction date.
• CODE_COMBINATION_ID, SET_OF_BOOKS_ID — the accounting flexfield and ledger identifiers.
• CURRENCY_CODE and conversion columns — CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_TYPE, and CURRENCY_USER_CONVERSION_TYPE support revaluation and audit of translated amounts.
• ACCT_LINE_TYPE, ACCT_LINE_TYPE_NAME — the subledger accounting line type and its descriptive name.
• GL_TRANSFER_STATUS, GL_TRANSFER_STATUS_NAME — indicates whether the line has been transferred to GL.
• SOURCE_ID, SOURCE_TABLE, TRX_HDR_ID, TRX_HDR_TABLE — trace back to the originating Assets transaction.
• AE_LINE_REFERENCE — link to the underlying subledger accounting entry line; mirrored into AE_LINE_REFERENCE_INTERNAL.
• TRX_CLASS, TRX_CLASS_NAME, TRX_TYPE_NAME, TRX_NUMBER_DISPLAYED — transaction classification and display references.
• LAST_UPDATE_DATE — standard audit column for incremental extraction.

Common Use Cases and Queries

Typical uses include reconciling Oracle Assets journal activity to GL, reporting account balances by asset transaction class, and extracting accounting lines for downstream warehouse loads. Because several columns are deliberately null, filters should be applied only to populated attributes.

Extract all posted assets lines for a ledger and period:

• SELECT je_header_id, je_line_num, accounting_date, code_combination_id,
  accounted_dr, accounted_cre, set_of_books_id
  FROM apps.xla_fa_ael_glx_v
  WHERE set_of_books_id = :ledger_id
  AND accounting_date BETWEEN :start_date AND :end_date;

Summarise amounts by transaction class:

• SELECT trx_class_name, SUM(accounted_dr) dr, SUM(accounted_cr) cr
  FROM apps.xla_fa_ael_glx_v
  GROUP BY trx_class_name;

Track transfer to GL:

• SELECT gl_transfer_status, gl_transfer_status_name, COUNT(*)
  FROM apps.xla_fa_ael_glx_v
  GROUP BY gl_transfer_status, gl_transfer_status_name;

Where a line must be traced to its subledger origin, join on AE_LINE_REFERENCE or SOURCE_ID back to the XLA accounting line tables. Standard practice is to restrict by set_of_books_id and accounting_date to keep execution plans efficient.