Search Results fa_balances_report

Overview

FA_BALANCES_REPORT is a table owned by the FA schema within the Oracle E-Business Suite (EBS) Assets module (OFA). It is not a master data table in the conventional sense; rather, it functions as a temporary storage area for the balance reports generated by the Assets application. During balance report processing, Oracle Assets extracts and assembles the relevant balances into this table, which then serves as the data source for report output. As a result, the contents are transient, populated and consumed within a reporting run, and should not be treated as a durable transaction ledger or a system of record.

Because of its staging nature, the table is typically truncated or refreshed between report executions. This behavior has important implications for query design, since historical values are not retained once a subsequent report run overwrites or clears the prior contents. In the ETRM 12.2.2 documented schema, the table contains nine columns. The heuristic Data Vault classification derived from the foreign key structure is standalone. Following standard Data Vault modeling guidance, a standalone table of this kind would most naturally be represented as a satellite, since it records descriptive attributes tied to assets and group assets rather than defining a business hub in its own right; the group asset reference can be modeled as a link to the corresponding hub.

Key Information Stored

The documented columns capture the accounting and grouping dimensions required for balance reporting. The most significant columns include:

• ASSET_ID — identifies the asset whose balance is being reported; this is the principal business key used to join back to asset-level data.
• GROUP_ASSET_ID — the foreign key column referencing FA_GROUP_ASSETS, used when balances are reported at the group asset level.
• DISTRIBUTION_CCID — the distribution account code combination, tying the reported balance to a General Ledger account.
• ADJUSTMENT_CCID — the account code combination used for adjustment-related balances.
• COST_ACCOUNT — the cost account associated with the reported amount.
• CATEGORY_BOOKS_ACCOUNT — the account derived from the asset category and depreciation book combination.
• SOURCE_TYPE_CODE — indicates the source or transaction type that generated the balance line.
• AMOUNT — the monetary value of the reported balance.
• COST_BEGIN_BALANCE — the opening cost balance carried into the reporting period.

No surrogate primary key is documented for this table in the ETRM metadata, consistent with its role as a transient staging object. ASSET_ID and GROUP_ASSET_ID function as business-key candidates, with GROUP_ASSET_ID formally enforced through the foreign key to FA_GROUP_ASSETS.

Common Use Cases and Queries

The primary use case is diagnostic and reporting support: inspecting the intermediate result set that Oracle Assets produces during balance report execution. A typical query joins the staging rows to group asset definitions to validate grouping:

• Confirming that all expected assets and group assets are represented: SELECT asset_id, group_asset_id, amount FROM fa_balances_report;
• Reconciling reported amounts against account combinations: SELECT distribution_ccid, SUM(amount) FROM fa_balances_report GROUP BY distribution_ccid;
• Verifying the link to group assets: SELECT b.asset_id, b.group_asset_id, g.group_asset_name FROM fa_balances_report b, fa_group_assets g WHERE b.group_asset_id = g.group_asset_id;
• Reviewing source-type composition: SELECT source_type_code, COUNT(*), SUM(amount) FROM fa_balances_report GROUP BY source_type_code;

Because data is overwritten with each run, these queries are best executed immediately after the report is generated and before the next execution.

Related Objects

The most significant related object is FA_GROUP_ASSETS, referenced through GROUP_ASSET_ID. Balance rows also relate logically to asset master data in FA_ADDITIONS and its asset-level children, to depreciation book accounts in FA_CATEGORY_BOOKS_DEFAULTS, and to the chart of accounts combinations referenced by DISTRIBUTION_CCID, ADJUSTMENT_CCID, and COST_ACCOUNT. The balance report itself is driven by the Oracle Assets balance report concurrent programs, which populate and consume this table. Analysts should rely on the formal GL and asset tables for permanent reporting and treat FA_BALANCES_REPORT strictly as a transient vehicle.