Search Results fun_interface_batches




Overview
Explore in AI Chat

Overview

The FUN_INTERFACE_BATCHES table is the open interface table for Intercompany Batches within the Financials Common Modules (FUN) product of Oracle E-Business Suite. It serves as the staging area into which external sources, feeder systems, or custom processes insert batch header records prior to validation and import into the Intercompany application tables. Records written to FUN_INTERFACE_BATCHES carry the descriptive and control attributes of an intercompany batch—originating ledger, initiator, transaction type, currency, control totals, and general ledger date—and are subsequently consumed by the Intercompany batch import program, which validates each row, accepts or rejects it, and migrates accepted rows into the permanent Intercompany batch schema.

The table is classified public and active, positioned within the FUN_INTERFACE_BATCHES business entity (FUN_INTERCOMPANY_BATCH). Based on the foreign key structure, the ETRM heuristic Data Vault classification for this object is standalone; from a modeling perspective it may reasonably be treated as a hub-like staging entity, since it holds the business identity of a batch (batch number and source) without resolving upstream or downstream links within the modeled relationship graph. Independent of the Data Vault lens, its functional role is that of an inbound integration surface, and its definition is version-stable across the 12.1.1 and 12.2.2 releases.

Key Information Stored

The documented physical schema comprises 45 columns owned by the FUN schema. The most significant columns are:

The surrogate identity is BATCH_ID; the principal business-key candidates are SOURCE and BATCH_NUMBER. A foreign key exists from TRX_TYPE_ID to IGI_EXP_TRX_TYPE, linking the batch to the governing transaction type definition.

Common Use Cases and Queries

Typical use cases include populating the interface from external ERP systems, monitoring import status, reconciling control totals before submission, and purging processed staging rows. A common monitoring query filters rows that have not been imported:

  • SELECT batch_id, batch_number, source, import_status_code, control_total FROM fun_interface_batches WHERE import_status_code = 'PENDING';
  • Balancing check: compare CONTROL_TOTAL against RUNNING_TOTAL_DR and RUNNING_TOTAL_CR to detect unbalanced batches prior to import.
  • Group-based cleanup: DELETE FROM fun_interface_batches WHERE group_id = :p_group_id AND import_status_code = 'PROCESSED';
  • Join to the transaction type definition: SELECT b.batch_number, t.trx_type_code FROM fun_interface_batches b, igi_exp_trx_type t WHERE b.trx_type_id = t.trx_type_id;

Because the table is an interface, it is not intended for long-term retention; reporting should generally rely on the destination Intercompany tables once import completes.

Related Objects

  • IGI_EXP_TRX_TYPE — referenced via TRX_TYPE_ID; provides transaction type code and name context.
  • FUN_INTERFACE_DISTRIBUTIONS — companion interface table holding distribution lines associated with each interface batch.
  • The Intercompany batch import concurrent program — consumes FUN_INTERFACE_BATCHES and its companion distribution interface rows.
  • Permanent Intercompany batch header and distribution tables in the FUN schema — the import destination.
  • GL_JE_BATCHES / GL_JE_HEADERS and GL_LEDGERS — referenced conceptually through FROM_LEDGER_ID and GL_DATE for accounting context.
  • FND_USER — supplies INITIATOR_ID and the CREATED_BY / LAST_UPDATED_BY audit references.