Search Results gl_iea_interface




Overview
Explore in AI Chat

Overview

GL_IEA_INTERFACE is a General Ledger staging table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It holds transactional data intended for import into the Global Intercompany System (GIS), the framework that governs intercompany transactions between subsidiaries and legal entities within a multi-organization accounting structure. Rows written to this table are processed by the GIS import concurrent program, which validates, balances, and ultimately transfers the data into the permanent intercompany tables used for intercompany reconciliation and elimination.

Because the table is a staging structure whose rows are consumed, validated, and then typically purged or archived, its heuristic Data Vault classification is a link — it captures associations between sender and receiver subsidiaries, transaction types, currencies, and accounting flexfield combinations. This classification is a modeling suggestion rather than a native EBS concept; Oracle does not implement Data Vault natively.

Key Information Stored

GL_IEA_INTERFACE is documented with 81 columns in the 12.2.2 physical schema. Its most operationally significant columns include:

The SENDER_SEGMENT1 through SENDER_SEGMENT30 and RECEIVER_SEGMENT1 through RECEIVER_SEGMENT30 columns provide the denormalized key flexfield segments that ultimately resolve into the code combination identifiers. The surrogate/functional key for a row is not exposed as a single documented primary key column; GROUP_ID combined with TRANSACTION_NUMBER and LINE_TYPE functions as the practical business-key candidate.

Common Use Cases and Queries

Typical usage centers on loading intercompany data from external systems, monitoring import results, and diagnosing failed rows. A common pattern is to review unprocessed transactions by status:

  • Querying all rows for a given batch: SELECT TRANSACTION_NUMBER, LINE_TYPE, LINE_DEBIT, LINE_CREDIT FROM GL.GL_IEA_INTERFACE WHERE GROUP_ID = :group_id;
  • Identifying failures: SELECT TRANSACTION_NUMBER, TRANSACTION_STATUS_CODE, COMPLETION_STATUS_CODE FROM GL.GL_IEA_INTERFACE WHERE TRANSACTION_STATUS_CODE = 'ERROR';
  • Joining to subsidiary names for reporting: SELECT i.TRANSACTION_NUMBER, s.SUBSIDIARY_NAME FROM GL.GL_IEA_INTERFACE i, GL.GL_IEA_SUBSIDIARIES s WHERE i.SENDER_SUBSIDIARY_ID = s.SUBSIDIARY_ID;
  • Correlating to the loading process via GL_IEA_INTERFACE.REQUEST_ID = FND_CONCURRENT_REQUESTS.REQUEST_ID.

Reporting use cases include intercompany balance summaries, unmatched sender/receiver pairs, and pre-import validation extracts.

Related Objects

  • GL_IEA_SUBSIDIARIES — joined on SENDER_SUBSIDIARY_ID and RECEIVER_SUBSIDIARY_ID.
  • GL_IEA_TRANSACTION_TYPES — joined on TRANSACTION_TYPE_ID.
  • GL_CODE_COMBINATIONS — joined on SENDER_CODE_COMBINATION_ID and RECEIVER_CODE_COMBINATION_ID.
  • FND_CURRENCIES — joined on CURRENCY_CODE.
  • FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to trace the concurrent program execution.
  • GL_IEA_INTERFACE_CONTROLS and the GIS import programs — which read and validate rows from this interface table before posting to the permanent intercompany transaction tables.