Search Results fa_balances_rep_itf




Overview
Explore in AI Chat

Overview

The FA_BALANCES_REP_ITF table is a report interface (staging) table owned by the FA schema within the Oracle Assets (OFA) module of Oracle E-Business Suite. Its documented description — "Interface table for Report eXchange reports" — identifies it as a transient data repository that holds pre-computed asset balance information in a flattened structure suitable for consumption by Oracle Report eXchange (RX) reporting extracts. Rather than serving as a transactional base table like FA_ADDITIONS_B or FA_BOOKS, this object is populated and subsequently read by reporting programs, then typically purged or reused between runs.

Under a heuristic Data Vault classification mined from its foreign-key structure, the table is assessed as satellite-leaning. This is a modeling suggestion: the table stores descriptive and quantitative attributes that describe asset balances at a point in time, with a single foreign-key relationship anchoring it to a parent hub. It does not function as a link table resolving many-to-many relationships, nor does it own independently-tracked business keys across multiple hubs.

Key Information Stored

The table exposes 42 documented columns in the 12.2.2 schema. The most operationally significant are:

  • REQUEST_ID — Concatenated request identifier that ties a row to a specific concurrent program run, enabling per-run partitioning and cleanup.
  • COMPANY, COST_CENTER, ACCOUNT, COST_ACCOUNT — Accounting flexfield segments used to group asset balance roll-ups by organization and cost centre.
  • ASSET_NUMBER, TAG_NUMBER, ASSET_KEY, SERIAL_NUMBER — Asset identification attributes, with ASSET_KEY acting as the natural business key linking back to the asset definition.
  • BOOK_TYPE_CODE — The depreciation book under which the balances are reported.
  • BEGIN_BALANCE, ADDITIONS, ADJUSTMENTS, RETIREMENTS, REVALUATIONS, RECLASSES, CAPITALIZATIONS, TRANSFERS, DEPRECIATION, AMORTIZATION, END_BALANCE — The full movement schedule reconciling opening to closing cost balances.
  • OUT_OF_BALANCE_FLAG — A control flag indicating rows where BEGIN_BALANCE plus movements does not equal END_BALANCE.
  • GROUP_ASSET_NUMBER — The foreign-key column referencing FA_ADDITIONS_B.

The table does not expose a documented surrogate single-column primary key; REQUEST_ID combined with asset and book identifiers forms the practical business-key candidate for row uniqueness within a run.

Common Use Cases and Queries

The principal use case is delivering reconciled asset movement reports through Report eXchange. A typical extract filters by concurrent request:

  • SELECT asset_number, book_type_code, begin_balance, additions, retirements, depreciation, end_balance FROM fa_balances_rep_itf WHERE request_id = :p_request_id;
  • Balance integrity checks: SELECT * FROM fa_balances_rep_itf WHERE out_of_balance_flag = 'Y';
  • Cost-centre roll-ups for management reporting: SELECT cost_center, SUM(begin_balance), SUM(end_balance) FROM fa_balances_rep_itf WHERE request_id = :p_request_id GROUP BY cost_center;
  • Reconciliation against the asset master using the FK join: ... FROM fa_balances_rep_itf i, fa_additions_b a WHERE i.group_asset_number = a.asset_number;

Because rows are request-scoped, queries should always constrain on REQUEST_ID to avoid returning data from prior runs.

Related Objects

The documented foreign-key relationship anchors this table to the asset master, and several surrounding objects participate in the same reporting flow:

  • FA_ADDITIONS_B — joined via FA_BALANCES_REP_ITF.GROUP_ASSET_NUMBER = FA_ADDITIONS_B.ASSET_NUMBER; the parent hub for asset identification.
  • FA_BOOKS — source of depreciation and book-type balance movements.
  • FA_BALANCES — the underlying balance table from which interface rows are derived.
  • FA_ASSET_HISTORY — transaction detail supporting the movement columns.
  • FA_DEPRN_SUMMARY — depreciation figures feeding the DEPRECIATION and AMORTIZATION columns.
  • FND_CONCURRENT_REQUESTS — correlates REQUEST_ID with the invoking program.