Search Results fun_trx_batches_u2

Overview

FUN.FUN_TRX_BATCHES is the Intercompany transaction batch header table in Oracle E-Business Suite, owned by the FUN (Financials Common) schema. It stores one row for each Intercompany batch created by an initiating organization, and serves as the parent container for the individual Intercompany transactions that a batch distributes to multiple recipients. A batch is uniquely identified by the combination of BATCH_NUMBER and INITIATOR_ID, as documented in the object description; the surrogate row identity is BATCH_ID. The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and is registered in FND Design Data as FUN.FUN_TRX_BATCHES. Under a Data Vault modeling convention, this object is best characterized as a standalone hub-like structure: the metadata classifies it as standalone with a single outbound foreign key, so it acts as a durable business entity anchor rather than a link or satellite, though dependent detail tables effectively act as satellites around it.

Key Information Stored

• BATCH_ID (NUMBER(15), mandatory) — system-generated surrogate primary key, enforced by unique index FUN_TRX_BATCHES_U1. All child transactions reference the batch through this column.
• BATCH_NUMBER (VARCHAR2(15)) — the user-visible batch identifier; together with INITIATOR_ID it forms the documented business key.
• INITIATOR_ID (NUMBER(15)) — party identifier of the initiating Intercompany organization; foreign key to HZ_PARTIES.PARTY_ID.
• FROM_LE_ID (NUMBER(15)) — party identifier of the initiator's legal entity; foreign key to XLE_ENTITY_PROFILES.LEGAL_ENTITY_ID.
• FROM_LEDGER_ID (NUMBER(15)) — primary ledger of the initiating organization; foreign key to GL_LEDGERS.LEDGER_ID.
• CONTROL_TOTAL — user-entered placeholder amount the batch is expected to reconcile against; it is not the sum of transaction amounts.
• RUNNING_TOTAL_CR / RUNNING_TOTAL_DR — the actual sum of INIT_AMOUNT_CR and INIT_AMOUNT_DR from FUN_TRX_HEADERS, providing the live batch balance.
• CURRENCY_CODE (VARCHAR2(15)) — batch currency; all transactions in a batch must share it.
• EXCHANGE_RATE_TYPE (VARCHAR2(30)) — rate type applied when the batch currency differs from the initiator's base currency.
• STATUS (VARCHAR2(30)) — batch lifecycle state.
• GL_DATE, BATCH_DATE — accounting and creation dates used for period and reporting filters.
• TRX_TYPE_ID / TRX_TYPE_CODE — transaction type driving batch behavior; TRX_TYPE_ID references IGI_EXP_TRX_TYPE.
• REJECT_ALLOW_FLAG, AUTO_PRORATION_FLAG — control flags for rejection handling and rounding proration.
• ORIGINAL_BATCH_ID, REVERSED_BATCH_ID, FROM_RECURRING_BATCH_ID — self-referencing links that trace reversal, copy, and recurring batch lineage.

Common Use Cases and Queries

Typical reporting centers on batch completeness (comparing CONTROL_TOTAL to RUNNING_TOTAL_CR and RUNNING_TOTAL_DR), batch aging by GL_DATE, and tracing reversals back to their origin. The unique index FUN_TRX_BATCHES_U2 covers FROM_LEDGER_ID, BATCH_ID, FROM_LE_ID, and DESCRIPTION, while FUN_TRX_BATCHES_N1 and N2 support lookups by BATCH_NUMBER and TRX_TYPE_ID, and FUN_TRX_BATCHES_N20 supports GL_DATE range scans.

• Retrieve a batch by business key: SELECT * FROM fun.fun_trx_batches WHERE batch_number = :num AND initiator_id = :org_id;
• Reconciliation report: SELECT b.batch_id, b.batch_number, b.control_total, b.running_total_dr, b.running_total_cr, (b.control_total - (b.running_total_dr - b.running_total_cr)) variance FROM fun.fun_trx_batches b WHERE b.status = 'UNPROCESSED';
• Ledger-scoped batch listing using the U2 index: SELECT batch_number, description FROM fun.fun_trx_batches WHERE from_ledger_id = :ledger AND from_le_id = :le;
• Period activity by GL date: filter GL_DATE within the accounting period and group by TRX_TYPE_CODE.

Related Objects

• IGI_EXP_TRX_TYPE — referenced via FUN_TRX_BATCHES.TRX_TYPE_ID; supplies transaction type attributes that govern batch processing.
• HZ_PARTIES — source of INITIATOR_ID, resolving the initiating organization party.
• XLE_ENTITY_PROFILES — source of FROM_LE_ID, resolving the legal entity.
• GL_LEDGERS — source of FROM_LEDGER_ID, resolving the initiating primary ledger.
• FUN_TRX_HEADERS — child transaction detail; its INIT_AMOUNT_CR and INIT_AMOUNT_DR roll up into RUNNING_TOTAL_CR and RUNNING_TOTAL_DR, joined on BATCH_ID.
• FUN_TRX_BATCHES (self-join) — via ORIGINAL_BATCH_ID and REVERSED_BATCH_ID for lineage and reversal analysis.
• Intercompany APIs and concurrent programs that create, submit, or reverse batches operate on this table through BATCH_ID.