Search Results gl_iea_transaction_lines_u1

Overview

The GL.GL_IEA_TRANSACTION_LINES table stores the individual debit, credit, and offset account lines that make up an Intercompany Engine Accounting (IEA) transaction within Oracle General Ledger. It is the line-level counterpart to the transaction header record, capturing the accounting distributions generated by the Intercompany balancing and accounting processes in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents one side of an intercompany entry — either the sender or the receiver — together with the key flexfield account segments that will ultimately be posted to the GL_BALANCES and GL_JE_LINES structures.

The object resides in the GL schema in the APPS_TS_TX_DATA tablespace with FND Design Data reference SQLGL.GL_IEA_TRANSACTION_LINES. Both 12.1.1 and 12.2.2 maintain the same logical structure; the 12.2.2 documented physical schema exposes 62 columns. From a Data Vault modeling perspective, this object classifies heuristically as a link, since it associates a transaction header with code combinations and carries descriptive attributes rather than identifying a standalone business entity.

Key Information Stored

The table is anchored by a composite primary key and a matching unique index, GL_IEA_TRANSACTION_LINES_U1, created on the columns TRANSACTION_ID, SENDER_RECEIVER_CODE, and LINE_NUMBER. This triple is the business-key candidate; no separate single-column surrogate key is used, and TRANSACTION_ID doubles as both a foreign key to the transaction header and a component of the primary key.

• TRANSACTION_ID — the intercompany transaction defining column, joining to GL_IEA_TRANSACTIONS.
• SENDER_RECEIVER_CODE — identifies whether the line is the sender or receiver side of the transaction.
• LINE_NUMBER — sequences the lines within each sender/receiver grouping.
• OFFSET_CCID — the offset account key flexfield defining column, referencing GL_CODE_COMBINATIONS.
• ENTERED_DR and ENTERED_CR — the entered debit and credit amounts for the line.
• GENERATION_CODE — indicates whether the account segments were generated, updated, or newly created.
• SEGMENT1 … SEGMENTn — the key flexfield segment columns storing the accounting flexfield components (up to 30 segments in the documented 12.2.2 schema).
• CONTEXT, ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield context and attribute columns.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Who columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — request and concurrent program tracking columns.

Common Use Cases and Queries

Typical usage centers on intercompany reconciliation, balancing reports, and audit of generated offset accounts. Analysts join header and line data to reconstruct full transactions, or join to GL_CODE_COMBINATIONS to resolve the offset account description.

SELECT l.transaction_id, l.sender_receiver_code, l.line_number,
       l.entered_dr, l.entered_credit, l.offset_ccid
FROM   gl_iea_transaction_lines l
WHERE  l.transaction_id = :p_transaction_id
ORDER  BY l.sender_receiver_code, l.line_number;

Reconciliation queries aggregate debits and credits per transaction to verify balancing, while reporting extracts use the SEGMENT columns when a decodes-based view of the accounting flexfield is preferred over the OFFSET_CCID. Auditing queries filter on GENERATION_CODE to isolate lines whose segments were regenerated by a rerun.

Related Objects

• GL.GL_IEA_TRANSACTIONS — the transaction header; join on TRANSACTION_ID (foreign key).
• GL.GL_CODE_COMBINATIONS — the account key flexfield; join on OFFSET_CCID (foreign key).
• GL.GL_JE_LINES — downstream journal lines populated from IEA accounting.
• GL.GL_JE_HEADERS — journal headers corresponding to posted intercompany entries.
• GL.GL_BALANCES — account balances affected by postings derived from these lines.
• GL.GL_IEA_TRANSACTION_LINES_U1 — the unique index enforcing the business key.

Access to this object outside standard Oracle Applications programs is documented as Oracle Internal Use Only and is not supported by Oracle Corporation.