Search Results fun_bal_headers_gt_u1

Overview

FUN.FUN_BAL_HEADERS_GT is a global temporary table in the Oracle E-Business Suite Financials (FUN) schema, documented as a valid object in both EBS 12.1.1 and 12.2.2. It is the primary staging structure consumed by the Intercompany Balancing API. Calling modules such as Subledger Accounting (SLA) and General Ledger (GL) insert the header-level attributes of journals requiring intercompany balancing into this table, then invoke the API, which reads the staged rows, resolves driving legal entity attributes, and writes balancing lines back to the calling product.

The table is defined with a data duration of SYS$TRANSACTION, meaning rows persist only for the duration of the transaction that inserted them and other sessions cannot see them. This makes the table a session-scoped, transaction-scoped scratch area rather than a persistent data store. Storage defaults are PCTFREE 10 and PCTUSED 40, typical of Oracle EBS temporary staging tables where inserts and deletes are frequent within short-lived transactions.

From a heuristic Data Vault modeling perspective, this table is classified as standalone. It exhibits no foreign keys in the reference model; the documented relationship to GL_MGT_SEG_UPGRADE_H is informational rather than a declared constraint. The GROUP_ID unique index acts as a surrogate business key, scoping a set of journal headers passed in a single API call.

Key Information Stored

Each row represents one journal header awaiting intercompany balancing. The most significant columns are:

• GROUP_ID — surrogate key and the sole unique index (FUN_BAL_HEADERS_GT_U1). Groups the headers submitted in a single balancing invocation.
• LEDGER_ID — identifies the ledger owning the journal; indexed non-uniquely (FUN_BAL_HEADERS_GT_N3).
• JE_SOURCE_NAME and JE_CATEGORY_NAME — classify the journal for accounting rule resolution.
• GL_DATE — accounting date used to determine the applicable balancing rules.
• STATUS — processing state of the header; indexed non-uniquely (FUN_BAL_HEADERS_GT_N1).
• INTERCOMPANY_MODE — controls balancing behavior (for example, whether to balance, or to process due-to/due-from); indexed non-uniquely (FUN_BAL_HEADERS_GT_N2).
• DRIVING_DR_LE_ID / DRIVING_CR_LE_ID — driving debit and credit legal entities that determine intercompany relationships.
• DRIVING_DR_LE_CURR_CODE / DRIVING_CR_LE_CURR_CODE — currency codes associated with the driving entities.
• LE_ID and LE_COUNT — the balancing legal entity and number of legal entities involved.
• CHART_OF_ACCOUNTS_ID, BAL_SEG_COLUMN_NAME, BAL_SEG_COLUMN_NUMBER, INTERCOMPANY_COLUMN_NUMBER — chart of accounts structure metadata used to locate the balancing segment and intercompany segment.
• CLEARING_BSV and UNMAPPED_BSV_LE_ID — clearing balancing segment value and unmatched legal entity references.
• ERROR_CODE — captures failure diagnostics returned to the calling module.

Common Use Cases and Queries

The table is primarily interrogated during debugging of intercompany balancing failures. A typical diagnostic query inspects headers for a specific GROUP_ID:

• SELECT group_id, ledger_id, status, intercompany_mode, error_code FROM fun.fun_bal_headers_gt WHERE group_id = :p_group_id;
• Identify unbalanced headers by status: SELECT * FROM fun.fun_bal_headers_gt WHERE status = :p_status AND ledger_id = :p_ledger_id;
• Locate journals processed with a specific intercompany mode: SELECT group_id, je_source_name, je_category_name FROM fun.fun_bal_headers_gt WHERE intercompany_mode = :p_mode;

Because the table is transaction-scoped, querying after the originating transaction commits yields no rows; diagnostics must run within the same session or transaction. Reporting on historical balancing activity should target the persistent SLA and GL journal tables instead.

Related Objects

• Intercompany Balancing API (FUN_BALANCING_PUB or successor package) — the primary consumer that reads staged headers and generates balancing lines.
• GL_MGT_SEG_UPGRADE_H — referenced relationship on CHART_OF_ACCOUNTS_ID in the reference model.
• SLA (XLA) journal entities — SLA tables and entry APIs populate this table before invoking the API for subledger balancing.
• GL_JE_HEADERS and GL_JE_LINES — persistent GL journals populated after balancing completes.
• GL_LEDGERS — source of LEDGER_ID and chart of accounts context.
• FUN_BAL_HEADERS_GT indexes (U1, N1, N2, N3) — supporting access paths for status, ledger, and intercompany mode lookups.