Search Results fun_bal_headers_gt




Overview
Explore in AI Chat

Overview

FUN_BAL_HEADERS_GT is a global temporary table (GTT) owned by the FUN (Financials Common Modules) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the transient staging and control structure for the Intercompany Balancing API, which is invoked during journal processing to create the intercompany balancing lines required when a journal spans multiple legal entities or balancing segment values. Calling modules such as Subledger Accounting (SLA) and General Ledger (GL) populate this table with the header-level details of journals that require balancing, then invoke the Intercompany Balancing API to process them. Because it is a GTT, data is visible only within the session and is scoped to the transaction lifecycle, making it unsuitable for permanent reporting without interception at runtime.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is standalone. This suggests treating the object not as a conformed hub, link, or satellite, but as a session-scoped work table whose rows represent an in-flight balancing request rather than a persistent business entity.

Key Information Stored

The table is defined with 20 documented columns. Its surrogate/business grouping key is exposed through the unique index FUN_BAL_HEADERS_GT_U1 on GROUP_ID, which ties each balancing request together and acts as the primary correlation point within a session. The remaining columns carry journal and balancing metadata:

Common Use Cases and Queries

The table is rarely queried directly in production because its contents are session-bound and short-lived. Its principal uses are debugging intercompany balancing failures, tracing why journals were rejected, and confirming which legal entities drove balancing. A typical diagnostic query would join the GTT to ledger and legal entity reference tables:

SELECT h.group_id, h.ledger_id, h.je_source_name,
       h.je_category_name, h.gl_date, h.status, h.error_code,
       h.driving_dr_le_id, h.driving_cr_le_id
FROM   fun_bal_headers_gt h
WHERE  h.status = 'ERROR';

Support and implementation teams also use it to validate that the calling module populated the expected driving legal entities and currencies before API invocation. Because rows are visible only to the creating session, queries must be run from the same session that populated the table, or during a debug/trace-enabled run.

Related Objects

The most significant related objects are the Intercompany Balancing API routines that consume this table and the reference tables from which its values are derived:

  • GL_MGT_SEG_UPGRADE_H – Referenced by CHART_OF_ACCOUNTS_ID; supplies chart of accounts context.
  • Intercompany Balancing API (FUN) – The primary consumer that reads this GTT and generates balancing lines.
  • SLA (Subledger Accounting) journal posting programs – Population source for awaiting-balancing journals.
  • GL journal import and posting programs – Additional callers that stage journals for balancing.
  • GL_LEDGERS / ledger reference tables – Supply LEDGER_ID context.
  • Legal entity (LE) reference tables – Resolve DRIVING_DR_LE_ID, DRIVING_CR_LE_ID, and LE_ID.

Together these objects form the intercompany balancing workflow in which FUN_BAL_HEADERS_GT functions as the transient request and control surface.