Search Results gl_iea_transaction_types_u1

Overview

GL.GL_IEA_TRANSACTION_TYPES is a General Ledger reference table that defines the transaction types used by the Oracle E-Business Suite Intercompany and Enterprise Application (IEA) accounting engine. Each row describes a classification of intercompany or intracompany transaction — for example, a journal that must be balanced and posted between two balancing segments, an intercompany invoice, or an interest accrual entry. The table acts as the master control point that determines whether a given transaction type permits automatic approval, interest accrual, or invoicing, and whether it is taxable for VAT purposes.

The IEA subsystem uses this table to drive processing rules at posting time, so its rows behave as configurable metadata rather than transactional data. Under a heuristic Data Vault classification, the table is best modeled as a hub: it carries a durable business key (the transaction type) and is referenced by many dependent transactional tables through a foreign key. This classification is a modeling suggestion only and should be validated against the full IEA data model.

Key Information Stored

The primary key is TRANSACTION_TYPE_ID, a NUMBER(15) surrogate key. Two unique indexes are documented: GL_IEA_TRANSACTION_TYPES_U1 on TRANSACTION_TYPE_ID (the primary key) and GL_IEA_TRANSACTION_TYPES_U2 on NAME. The U2 index confirms NAME, a VARCHAR2(25) transaction type name, as the natural business-key candidate.

• TRANSACTION_TYPE_ID — surrogate primary key, the column referenced by all child tables.
• NAME — the business key, a short unique label for the transaction type.
• DESCRIPTION — VARCHAR2(240) descriptive text.
• ENABLED_FLAG — controls whether the type is available for use.
• AUTO_APPROVE_FLAG — determines whether transactions of this type are approved automatically.
• VAT_TAXABLE_FLAG — indicates whether the type is subject to VAT.
• ALLOW_INTEREST_ACCRUAL_FLAG — permits interest accrual processing.
• ALLOW_INVOICING_FLAG — permits generation of intercompany invoices.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Who columns for audit and concurrency.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield storage for customer-defined extensions.

Common Use Cases and Queries

The most frequent requirement is to resolve a transaction type name to its surrogate identifier, or to list the behavioral flags that govern processing. A typical query joins the type to its transaction table:

• List all enabled types: SELECT transaction_type_id, name, description FROM gl_iea_transaction_types WHERE enabled_flag = 'Y';
• Resolve behavior: SELECT name, auto_approve_flag, vat_taxable_flag, allow_invoicing_flag FROM gl_iea_transaction_types WHERE name = :name;
• Reporting volume by type: SELECT t.name, COUNT(*) FROM gl_iea_transactions x, gl_iea_transaction_types t WHERE x.transaction_type_id = t.transaction_type_id GROUP BY t.name;
• Finding types that still permit invoicing for audit or close purposes.

Because Oracle supports access to applications data only through standard programs, these queries should be used for reporting and reference rather than direct DML. Descriptive flexfield columns (CONTEXT, ATTRIBUTE1–15) may carry site-specific classifications and should be inspected before writing joins.

Related Objects

documented foreign keys establish GL_IEA_TRANSACTION_TYPES as a parent of the primary IEA transactional and staging tables. The significant dependents include:

• GL_IEA_TRANSACTIONS — the main transaction table, joined on TRANSACTION_TYPE_ID.
• GL_IEA_RECUR_TRANSACTIONS — recurring transaction definitions, joined on TRANSACTION_TYPE_ID.
• GL_IEA_INTERFACE — the inbound interface, joined on TRANSACTION_TYPE_ID.
• GL_IEA_IMPORT_REGISTRY — import control registry, joined on TRANSACTION_TYPE_ID.

These child relationships confirm the hub role of the table: all transactional activity references a single, shared catalog of transaction type definitions maintained in GL.