Search Results fun_trx_batches
Overview
FUN_TRX_BATCHES is a Financials Common Modules (FUN) table that stores information about Intercompany transaction batches in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents a batch header that groups one or more intercompany transactions destined for one or more recipients. The table acts as the central control record for a batch, capturing its identifier, initiator, source ledger, transaction type, control totals, and lifecycle status.
The ETRM metadata describes FUN_TRX_BATCHES as having a standalone Data Vault classification, mined heuristically from its foreign key structure. In Data Vault modeling terms, the table can therefore be treated as a hub-like or self-contained entity rather than a link that resolves two or more business hubs. Its unique business key, formed by BATCH_NUMBER and INITIATOR_ID, supports that interpretation.
Key Information Stored
The table contains 44 documented columns. The most operationally significant are:
- BATCH_ID — the surrogate primary key, enforced by unique index FUN_TRX_BATCHES_U1.
- BATCH_NUMBER and INITIATOR_ID — together they form the business unique key. BATCH_NUMBER identifies the batch to users; INITIATOR_ID identifies the user or process that created it.
- FROM_LEDGER_ID and FROM_LE_ID — the source ledger and legal entity from which intercompany transactions originate.
- CONTROL_TOTAL, RUNNING_TOTAL_DR, and RUNNING_TOTAL_CR — the batch control amount and the accumulated debit and credit totals used for balancing and reconciliation.
- CURRENCY_CODE and EXCHANGE_RATE_TYPE — the currency of the batch and the rate type applied to conversions.
- STATUS — the batch lifecycle state (for example, unposted, posted, or reversed).
- TRX_TYPE_ID and TRX_TYPE_CODE — the intercompany transaction type; TRX_TYPE_ID has a documented foreign key to IGI_EXP_TRX_TYPE.
- GL_DATE and BATCH_DATE — the accounting date and the batch creation date.
- REJECT_ALLOW_FLAG and AUTO_PRORATION_FLAG — control flags governing rejection handling and automatic proration.
- DESCRIPTION and NOTE — free-text commentary; DESCRIPTION participates in unique index FUN_TRX_BATCHES_U2 (FROM_LEDGER_ID, BATCH_ID, FROM_LE_ID, DESCRIPTION).
- ORIGINAL_BATCH_ID, REVERSED_BATCH_ID, and FROM_RECURRING_BATCH_ID — self-referencing identifiers linking reversal, original, and recurring batch relationships.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard audit columns.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield columns.
Common Use Cases and Queries
Typical reporting scenarios include batch status monitoring, control-total reconciliation, and audit of intercompany activity by initiator or ledger. A common query joins the batch header to its transaction lines and filters by status:
SELECT b.batch_number, b.initiator_id, b.status, b.control_total, b.running_total_dr, b.running_total_cr FROM fun_trx_batches b WHERE b.from_ledger_id = :ledger_id AND b.status = 'UNPOSTED';
Control-check queries compare CONTROL_TOTAL against the sum of the running totals to detect batches that failed to balance. Reversal analysis uses the ORIGINAL_BATCH_ID and REVERSED_BATCH_ID columns to trace a batch to its counterpart. Aging and period-close reports filter on GL_DATE and BATCH_DATE, while initiator-based reporting groups by INITIATOR_ID to measure batch volumes per user or process.
Related Objects
- IGI_EXP_TRX_TYPE — referenced by FUN_TRX_BATCHES.TRX_TYPE_ID; provides the transaction type definition for each batch.
- FUN_TRX_HEADERS — the transaction header table whose rows belong to a batch through BATCH_ID, forming the batch-to-transaction relationship.
- FUN_TRX_LINES — transaction line detail associated with the headers and ultimately with the batch.
- IGI_EXP_TRX_TYPES_B / IGI_EXP_TRX_TYPES_TL — the base and translated tables that back the transaction type reference.
- GL_LEDGERS / GL_LEDGER_LE_BSV — source of FROM_LEDGER_ID and FROM_LE_ID values.
- FND_USER — resolves INITIATOR_ID and the audit user columns to application users.
- XLA_EVENTS / GL_JE_HEADERS — downstream accounting objects populated when an intercompany batch is accounted and posted.
These relationships make FUN_TRX_BATCHES the entry point for intercompany batch inquiry, reconciliation, and audit reporting in Oracle EBS Financials Common Modules.
-
Table: FUN_TRX_BATCHES
12.2.2
owner:FUN, object_type:TABLE, fnd_design_data:FUN.FUN_TRX_BATCHES, object_name:FUN_TRX_BATCHES, status:VALID, product: FUN - Financials Common Modules , description: FUN_TRX_BATCHES stores information about the Intercompany transaction batches. The BATCH_NUMBER and INITIATOR_ID together form a unique key. An Intercompany transaction batch can contain many transactions for multiple recipients. , implementation_dba_data: FUN.FUN_TRX_BATCHES ,
-
Table: FUN_TRX_BATCHES
12.1.1
owner:FUN, object_type:TABLE, fnd_design_data:FUN.FUN_TRX_BATCHES, object_name:FUN_TRX_BATCHES, status:VALID, product: FUN - Financials Common Modules , description: FUN_TRX_BATCHES stores information about the Intercompany transaction batches. The BATCH_NUMBER and INITIATOR_ID together form a unique key. An Intercompany transaction batch can contain many transactions for multiple recipients. , implementation_dba_data: FUN.FUN_TRX_BATCHES ,
-
APPS.FUN_PARTY_MERGE_PUB SQL Statements
12.1.1
-
APPS.FUN_PARTY_MERGE_PUB SQL Statements
12.2.2
-
VIEW: APPS.FUN_TRX_BATCHES_DFV
12.2.2
-
VIEW: APPS.FUN_TRX_BATCHES_DFV
12.1.1
-
APPS.FUN_IC_AME_WF_PKG SQL Statements
12.1.1
-
APPS.FUN_IC_AME_WF_PKG SQL Statements
12.2.2
-
APPS.FUN_RECIPIENT_WF SQL Statements
12.1.1
-
APPS.FUN_GLINT_WF SQL Statements
12.1.1
-
APPS.FUN_GLINT_WF SQL Statements
12.2.2
-
APPS.FUN_GL_BATCH_TRANSFER SQL Statements
12.2.2
-
APPS.FUN_GL_BATCH_TRANSFER SQL Statements
12.1.1
-
APPS.FUN_RECIPIENT_WF SQL Statements
12.2.2
-
SYNONYM: APPS.FUN_TRX_BATCHES
12.1.1
owner:APPS, object_type:SYNONYM, object_name:FUN_TRX_BATCHES, status:VALID,
-
SYNONYM: APPS.FUN_TRX_BATCHES
12.2.2
owner:APPS, object_type:SYNONYM, object_name:FUN_TRX_BATCHES, status:VALID,
-
VIEW: FUN.FUN_TRX_BATCHES#
12.2.2
owner:FUN, object_type:VIEW, object_name:FUN_TRX_BATCHES#, status:VALID,
-
APPS.FUN_REPORT_PVT SQL Statements
12.1.1
-
APPS.FUN_REPORT_PVT SQL Statements
12.2.2
-
APPS.FUN_TRX_PVT SQL Statements
12.2.2
-
APPS.FUN_PERIOD_STATUS_PKG SQL Statements
12.1.1
-
VIEW: FUN.FUN_TRX_BATCHES#
12.2.2
-
APPS.FUN_TRX_PVT SQL Statements
12.1.1
-
PACKAGE BODY: APPS.FUN_UPDATE_UPGRADED_TRX_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_UPDATE_UPGRADED_TRX_PKG, status:VALID,
-
APPS.FUN_UPDATE_UPGRADED_TRX_PKG SQL Statements
12.2.2
-
APPS.FUN_UPDATE_UPGRADED_TRX_PKG SQL Statements
12.1.1
-
PACKAGE: APPS.FUN_REPORT_PVT
12.1.1
owner:APPS, object_type:PACKAGE, object_name:FUN_REPORT_PVT, status:VALID,
-
PACKAGE: APPS.FUN_REPORT_PVT
12.2.2
owner:APPS, object_type:PACKAGE, object_name:FUN_REPORT_PVT, status:VALID,
-
APPS.FUN_PERIOD_STATUS_PKG SQL Statements
12.2.2
-
VIEW: APPS.FUN_TRX_BATCHES_DFV
12.1.1
owner:APPS, object_type:VIEW, object_name:FUN_TRX_BATCHES_DFV, status:VALID,
-
PACKAGE BODY: APPS.FUN_IC_AME_WF_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_IC_AME_WF_PKG, status:VALID,
-
PACKAGE BODY: APPS.FUN_UPDATE_UPGRADED_TRX_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_UPDATE_UPGRADED_TRX_PKG, status:VALID,
-
PACKAGE BODY: APPS.FUN_IC_AME_WF_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_IC_AME_WF_PKG, status:VALID,
-
VIEW: APPS.FUN_TRX_BATCHES_DFV
12.2.2
owner:APPS, object_type:VIEW, object_name:FUN_TRX_BATCHES_DFV, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.FUN_WF_AUTHORIZATION_LIMIT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_WF_AUTHORIZATION_LIMIT, status:VALID,
-
PACKAGE BODY: APPS.FUN_IC_AME_WF_PKG
12.1.1
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.FUN_IC_AME_WF_PKG
12.2.2
-
PACKAGE BODY: APPS.FUN_SEQ_UTILS
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_SEQ_UTILS, status:VALID,
-
PACKAGE BODY: APPS.FUN_PARTY_MERGE_PUB
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_PARTY_MERGE_PUB, status:VALID,
-
PACKAGE BODY: APPS.FUN_PARTY_MERGE_PUB
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_PARTY_MERGE_PUB, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
PACKAGE BODY: APPS.FUN_SEQ_UTILS
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_SEQ_UTILS, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.FUN_GLINT_WF
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_GLINT_WF, status:VALID,
-
12.1.1 FND Design Data
12.1.1
-
PACKAGE BODY: APPS.FUN_GL_TRANSFER
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_GL_TRANSFER, status:VALID,
-
PACKAGE BODY: APPS.FUN_GL_TRANSFER
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_GL_TRANSFER, status:VALID,