Results for “gl_iea_recur_transactions”

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

Overview

GL_IEA_RECUR_TRANSACTIONS is a General Ledger (GL) table that stores the header-level definitions of recurring intercompany transactions within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is part of the Intercompany Accounting (IEA) subsystem, which automates the creation and balancing of intercompany journal entries between sender and receiver subsidiaries. A recurring transaction definition captures the template attributes — such as transaction type, currency, receiving subsidiary, and clearing account assignments — that are reused on a scheduled basis to generate actual GL intercompany transactions.

Each record in this table represents a single recurring template belonging to a recurring batch. The parent batch provides the scheduling frequency and control parameters, while this table supplies the transactional specifics applied to each generated entry. The generated output is written to GL_IEA_TRANSACTIONS, which records the message that was processed by the Intercompany functionality. From a dimensional modeling perspective, the metadata's heuristic classification is satellite-leaning. This table carries descriptive and status attributes keyed to a transaction identifier, while its relationships are largely outbound lookups to reference and code combination tables. The recurrence is therefore best modeled as a satellite attached to a recurring transaction or batch key, with outbound links to currency, subsidiary, transaction type, and account dimensions.

Key Information Stored

The table contains 40 documented columns. The most significant include:

• RECURRING_TRANSACTION_ID — Surrogate primary key, enforced by GL_IEA_RECUR_TRANSACTIONS_PK and also the unique index GL_IEA_RECUR_TRANSACTIONS_U1.
• RECURRING_BATCH_ID — Foreign key to GL_IEA_RECUR_BATCHES, grouping the transaction under its recurring batch definition. Combined with NAME, it forms the second unique business key, GL_IEA_RECUR_TRANSACTIONS_U2.
• NAME — Business identifier for the recurring transaction, unique within its batch.
• TRANSACTION_TYPE_ID — Foreign key to GL_IEA_TRANSACTION_TYPES, defining the intercompany transaction type.
• CURRENCY_CODE — Foreign key to FND_CURRENCIES, specifying the transaction currency.
• RECEIVING_SUBSIDIARY_ID — Foreign key to GL_IEA_SUBSIDIARIES, identifying the receiver of the intercompany entry.
• SENDER_CLEARING_CCID and RECEIVER_CLEARING_CCID — Foreign keys to GL_CODE_COMBINATIONS, defining the clearing accounts for each side.
• SENDER_CLEARING_ACCOUNT and RECEIVER_CLEARING_ACCOUNT — Denormalized account identifiers retained alongside the CCID references.
• STATUS — Indicates whether the recurring transaction is active or otherwise.
• SENDER_RUNNING_TOTAL_DR, SENDER_RUNNING_TOTAL_CR, RECEIVER_RUNNING_TOTAL_DR, RECEIVER_RUNNING_TOTAL_CR, and CONTROL_TOTAL — Accumulated debit and credit balances used to monitor activity against the template.
• DESCRIPTION and NOTE — Free-form text.

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), fifteen descriptive ATTRIBUTE columns, and a CONTEXT column are also present.

Common Use Cases and Queries

Recurring intercompany templates are typically inspected when validating automated intercompany activity, reconciling clearing accounts, or auditing transferred balances. A common query joins transactions to their batch, transaction type, and receiving subsidiary to list all templates in an active state:

• Listing recurring transactions in a batch: SELECT t.NAME, t.STATUS, t.CONTROL_TOTAL FROM gl_iea_recur_transactions t WHERE t.RECURRING_BATCH_ID = :batch_id;
• Joining to the transaction type and receiving subsidiary to report template composition.
• Comparing running totals (SENDER_RUNNING_TOTAL_DR against CONTROL_TOTAL) to identify unposted or misbalanced recurring activity.
• Resolving clearing accounts by joining SENDER_CLEARING_CCID and RECEIVER_CLEARING_CCID to GL_CODE_COMBINATIONS.
• Audit tracing from generated entries back to the template: SELECT * FROM gl_iea_transactions WHERE FROM_RECURRING_TRANSACTION_ID = :id;

Related Objects

• GL_IEA_RECUR_BATCHES — Parent batch; joined on RECURRING_BATCH_ID.
• GL_IEA_RECUR_LINES — Child line details; joined on GL_IEA_RECUR_LINES.RECURRING_TRANSACTION_ID = this table's RECURRING_TRANSACTION_ID.
• GL_IEA_TRANSACTIONS — Generated transactions; joined on FROM_RECURRING_TRANSACTION_ID.
• GL_IEA_TRANSACTION_TYPES — Joined on TRANSACTION_TYPE_ID.
• GL_IEA_SUBSIDIARIES — Joined on RECEIVING_SUBSIDIARY_ID.
• FND_CURRENCIES — Joined on CURRENCY_CODE.
• GL_CODE_COMBINATIONS — Joined on SENDER_CLEARING_CCID and RECEIVER_CLEARING_CCID.