Results for “gl_iea_transactions_v”

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

Overview

GL_IEA_TRANSACTIONS_V is a General Ledger view that exposes intercompany and intracompany accounting transactions processed through the Intercompany Engine / Intercompany Accounting (IEA) framework in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It presents a denormalized, reporting-friendly projection of the underlying IEA transaction table, joining transaction header attributes with the sender and receiver ledger contexts. The view is primarily consumed by intercompany reconciliation reports, period-close validation queries, and custom integrations that need a single row per intercompany transaction together with both its sending and receiving side attributes.

The view is read-only and is not documented as an implemented object in the reference ETRM database for 12.2.2; the documented base object list is empty, so the view text itself is the authoritative specification. Its column naming reflects the two-sided nature of intercompany accounting: every column that describes a party, clearing account, period, or balancing segment appears in both a SENDER_ and a RECEIVER_ prefixed form.

Underlying Base Objects

The view text selects from a single aliased source, TR, which is the intercompany transaction table (GL_IEA_TRANSACTIONS). It is joined internally — within the view definition or via the source table — to resolve the sender and receiver chart of accounts identifiers used in the CHART_OF_ACCOUNTS_ID and RECEIVER_COA_ID columns (aliased from SEND and RECV respectively).

Because the transaction table stores only accounting flexfield identifiers, the view exposes the raw sender and receiver segments (SENDER_SEGMENT1 through SENDER_SEGMENT30 and RECEIVER_SEGMENT1 through RECEIVER_SEGMENT30) rather than resolved flexfield descriptions. Code combination identifiers for clearing accounts are surfaced directly as SENDER_CLEARING_CCID and RECEIVER_CLEARING_CCID, requiring a join to GL_CODE_COMBINATIONS for descriptive reporting.

Key Columns

• TRANSACTION_ID / TRANSACTION_NUMBER — Primary identifier and user-visible transaction number for each intercompany transaction.
• CHART_OF_ACCOUNTS_ID / RECEIVER_COA_ID — Chart of accounts of the sending and receiving parties.
• SENDING_SUBSIDIARY_ID / RECEIVING_SUBSIDIARY_ID — Subsidiary (legal entity or balancing segment) identifiers for each side of the transaction.
• SENDER_TRANSFER_FLAG / RECEIVER_TRANSFER_FLAG — Flags indicating whether the sender or receiver side of the transaction has been transferred to its respective ledger. These are the columns most commonly queried to determine transfer and posting status per side.
• STATUS — Overall transaction status within the IEA lifecycle.
• SENDER_CLEARING_CCID / RECEIVER_CLEARING_CCID — Clearing account code combinations used to balance the intercompany entries on each side.
• GL_DATE / ENTERED_DATE — Accounting date and entry date of the transaction.
• SENDER_PERIOD_NAME / RECEIVER_PERIOD_NAME — GL period assigned to each side, relevant when sender and receiver ledgers operate on different calendars.
• SENDER_GENERATION_CODE / RECEIVER_GENERATION_CODE — Codes describing how each side's intercompany entries were generated.
• SENDER_SEGMENT1–30 / RECEIVER_SEGMENT1–30 — The accounting flexfield segment values for each side, supporting segment-level reporting without additional joins.
• WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for audit traceability.

Common Use Cases and Queries

A frequent requirement is identifying transactions whose sender side has not yet transferred, which can be expressed as follows:

• SELECT transaction_id, transaction_number, sender_transfer_flag, receiver_transfer_flag, status FROM gl_iea_transactions_v WHERE sender_transfer_flag = 'N';
• SELECT transaction_id, transaction_number, sender_period_name, receiver_period_name, currency_code FROM gl_iea_transactions_v WHERE gl_date BETWEEN :start_date AND :end_date;
• SELECT transaction_number, sender_segment1, receiver_segment1, sender_clearing_ccid, receiver_clearing_ccid FROM gl_iea_transactions_v WHERE sending_subsidiary_id = :subsidiary_id;
• SELECT status, COUNT(*) FROM gl_iea_transactions_v GROUP BY status;

For reconciliation reporting, join SENDER_CLEARING_CCID and RECEIVER_CLEARING_CCID to GL_CODE_COMBINATIONS to obtain concatenated account strings, and combine the view with GL_JE_LINES or GL_JE_HEADERS to tie intercompany transactions to their journal entries. Because the view is not documented as implemented in the reference database, always verify object existence and column availability against the target instance before relying on it in production queries.