Search Results xla_ae_lines

Overview

The XLA_AE_LINES table is a core data structure within the Oracle E-Business Suite Subledger Accounting (XLA) module. It serves as the definitive repository for all subledger journal entry line details. In the Subledger Accounting architecture, transactional data from source subledgers (like Payables, Receivables, Assets) is processed by accounting programs to create journal entries. Each entry consists of a header and corresponding lines. This table stores those individual accounting lines, maintaining a critical one-to-many relationship with the journal entry headers stored in the XLA_AE_HEADERS table. It is fundamental to the generation of detailed, auditable accounting records that are ultimately transferred to the General Ledger (GL).

Key Information Stored

The table's primary key is a composite of AE_HEADER_ID and AE_LINE_NUM, uniquely identifying each line within its parent journal entry. While the provided ETRM metadata does not list all columns, based on its central role, the table typically stores essential accounting attributes for each line. These include the accounted amounts (both entered and functional currency), the accounting date, the code combination ID (CCID) linking to the GL chart of accounts, and the accounting event class and type that drove the line's creation. It also holds descriptive flexfield data for detailed tracking and references to the original source transaction identifiers, providing a complete audit trail from subledger transaction to general ledger journal entry.

Common Use Cases and Queries

This table is central for troubleshooting accounting issues, performing reconciliations, and building custom subledger accounting reports. A common use case is tracing the detailed accounting for a specific subledger transaction. For example, to retrieve all accounting lines for a particular invoice, one would join XLA_AE_LINES to XLA_AE_HEADERS and XLA_TRANSACTION_ENTITIES using the AE_HEADER_ID and ENTITY_ID. Another critical scenario is reconciling subledger journals to GL by querying lines before they are transferred. A sample query pattern to examine accounting lines for a specific event would be:

• SELECT ae_header_id, ae_line_num, accounted_dr, accounted_cr, code_combination_id
• FROM xla.xla_ae_lines
• WHERE ae_header_id IN (SELECT ae_header_id FROM xla_ae_headers WHERE event_id = :p_event_id);

Related Objects

The XLA_AE_LINES table has intrinsic relationships with several key Subledger Accounting objects. Its most direct relationship is with XLA_AE_HEADERS, as defined by the AE_HEADER_ID foreign key. It is also closely linked to XLA_TRANSACTION_ENTITIES (via the header) and XLA_EVENTS, which represent the accounting occurrences. For reporting and simplified access, Oracle provides the XLA_AE_LINES view, which often includes additional descriptive information. The table is the primary source for the subledger accounting entries that are ultimately transferred to the GL via the GL_INTERFACE or GL_JE_LINES tables, completing the financial posting flow.