Results for “xla_pa_ei_ael_gl_v”

20 results




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

Overview

XLA_PA_EI_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 exposes accounting event line (AEL) information originating from the Projects (PA) application and presents that data alongside the General Ledger transfer attributes maintained within the XLA model. The view functions as a unified, security-aware reporting layer that joins Project accounting distributions to their corresponding subledger journal entries, providing consumers with a single query point for account balances, journal headers, and GL transfer status.

Its naming convention reflects this hybrid purpose: the "PA" segment indicates the source application (Projects), "EI" denotes event information, and "AEL" refers to Accounting Event Lines in the XLA data model. The "_GL_" element signals that GL transfer-related columns are surfaced. Because it consolidates multiple accounting sources and enforces operating-unit and person-level security, the view is typically consumed by reports, reconciliations, and diagnostic queries rather than by direct transactional inserts or updates.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, XLA_PA_EI_AEL_GL_V is defined over the following base objects:

  • PA_AEL_GL_EI_V (VIEW) — the primary Project Accounting source view supplying accounting event lines, GL transfer status, and journal header/line attributes.
  • XLA_UTIL (PACKAGE) — provides Subledger Accounting utility functions referenced in the view definition.
  • PA_SECURITY (PACKAGE) — applies Project-level access control filters so users see only authorized projects.
  • HR_SECURITY (PACKAGE) — enforces HR organizational and person-level security on the exposed records.
  • HR_GENERAL (PACKAGE) — supplies general HR lookup utilities.
  • HR_PERSON_NAME (PACKAGE) — resolves person identifiers to displayable names.

The composition demonstrates that the view is not a simple table projection but a security-filtered join. The PA_AEL_GL_EI_V view supplies the bulk of the columns, while the HR and PA security packages constrain the result set. XLA_UTIL augments the output with XLA-specific processing logic. Notably, the select list includes numerous TO_NUMBER(NULL) and NULL placeholders (for example AEH_ID, AEL_ID, DOC_SEQUENCE_ID, TAXABLE_ENTERED_DR, THIRD_PARTY_ID, and TAX_CODE), which indicates that the view conforms to a standard XLA interface column layout while leaving certain XLA-specific attributes intentionally unpopulated for the Projects source.

Key Columns

The view exposes a wide set of columns that can be grouped as follows:

Together these columns allow reconciliation of Projects accounting entries to GL postings without directly navigating the underlying XLA_AE_HEADERS, XLA_AE_LINES, and XLA_DISTRIBUTION_LINKS tables.

Common Use Cases and Queries

Typical uses include GL transfer reconciliation, unposted-and-posted journal diagnostics, and Projects-to-GL audit reporting. The following query returns accounting lines for a given set of books within a date range:

  • SELECT je_header_id, je_line_num, accounting_date, trx_number_displayed, entered_dr, entered_cr, accounted_dr, accounted_cr, gl_transfer_status_name FROM apps.xla_pa_ei_ael_gl_v WHERE set_of_books_id = :p_sob AND accounting_date BETWEEN :p_start AND :p_end ORDER BY je_header_id, je_line_num;
  • To isolate entries that have not yet transferred to GL, apply WHERE gl_transfer_status_name NOT IN ('Yes','Posted') or filter on GL_TRANSFER_STATUS = 1 (Pending/Unposted), depending on the configured lookup meaning.
  • To reconcile by operating unit, constrain with WHERE org_id = :p_org_id; the HR_SECURITY and PA_SECURITY packages will additionally restrict rows to the caller's authorized projects.

Because security packages are embedded, query results vary by responsibility and user. Consumers should therefore avoid using this view for background jobs that require unrestricted global scope unless the executing schema bypasses those filters. For performance, filter on indexed source columns such as JE_HEADER_ID, ACCOUNTING_DATE, and SET_OF_BOOKS_ID.