Search Results gl_iea_transaction_lines




Overview
Explore in AI Chat

Overview

The GL_IEA_TRANSACTION_LINES table, owned by the GL schema, stores the individual line details of intercompany transactions processed by Oracle General Ledger's Intercompany and Intracompany Balancing (IEA) engine. It is the line-level companion to GL_IEA_TRANSACTIONS (the header), capturing the debit and credit amounts, the balancing account assignments, and the descriptive flexfield segments required to record and post intercompany journal entries. The table resides in the GL product/module and is defined as VALID in ETRM 12.1.1 and 12.2.2.

From a dimensional modeling perspective, the documented foreign key structure (TRANSACTION_ID → GL_IEA_TRANSACTIONS, OFFSET_CCID → GL_CODE_COMBINATIONS) suggests a link classification (heuristic, mined from FK structure): this table resolves the many-to-many relationships between intercompany transactions and the balancing code combinations they reference. It is not a hub (no single immutable business key) nor a pure satellite. As a modeling suggestion, treat it as a link table whose grain is one row per transaction, sender/receiver designation, and line number.

Key Information Stored

The physical schema contains 62 documented columns. The most significant are:

The documented primary key is GL_IEA_TRANSACTION_LINES_PK on (TRANSACTION_ID, SENDER_RECEIVER_CODE, LINE_NUMBER). The unique index GL_IEA_TRANSACTION_LINES_U1 mirrors the same column set, making these three columns the business-key candidate, while no separate surrogate key is documented.

Common Use Cases and Queries

Typical scenarios include auditing intercompany balancing output, reconciling sender versus receiver amounts, and reporting on the offset accounts applied during auto-balancing.

Sample query to list all lines for a given transaction:

  • SELECT transaction_id, sender_receiver_code, line_number, offset_ccid, entered_dr, entered_cr
  • FROM gl.gl_iea_transaction_lines
  • WHERE transaction_id = :p_transaction_id
  • ORDER BY sender_receiver_code, line_number;

Joining to code combinations to resolve the balancing account:

  • SELECT l.transaction_id, l.line_number, c.concatenated_segments, l.entered_dr, l.entered_cr
  • FROM gl.gl_iea_transaction_lines l, gl.gl_code_combinations_kfv c
  • WHERE l.offset_ccid = c.code_combination_id;

Related Objects

  • GL_IEA_TRANSACTIONS — Parent header table; joined on TRANSACTION_ID.
  • GL_CODE_COMBINATIONS — Referenced via OFFSET_CCID for the balancing account.
  • GL_JE_HEADERS / GL_JE_LINES — Journal entries ultimately produced from IEA processing.
  • GL_IMPORT_REFERENCES — Links imported intercompany lines back to their source subledger.
  • GL_INTERCOMPANY_ACCOUNTS — Defines the intercompany account rules driving line generation.
  • GL_IEA_TRANSACTIONS header/line APIs (e.g., journal import and balancing concurrent programs) that populate these lines.

Together these objects support end-to-end intercompany balancing, posting, and reconciliation within Oracle General Ledger.