Search Results property_1245_1250_code




Overview
Explore in AI Chat

Overview

FA_ADDITIONS_B is the base table of the Oracle Assets (OFA) module that stores descriptive, non-financial information about every asset defined in the Fixed Assets application. The "_B" suffix denotes that this is the base table of an MLS (Multi-Lingual Support) pair; translatable columns such as asset descriptions and descriptive flexfield context values are held in the corresponding FA_ADDITIONS_TL table. One row exists per asset, identified by ASSET_ID, making FA_ADDITIONS_B the central descriptive registry for the asset master.

Based on the foreign key structure mined from the ETRM metadata, the heuristic Data Vault classification for this object is a hub. It anchors a natural business key (ASSET_NUMBER) and a surrogate key (ASSET_ID), and is referenced by a large number of satellite and transactional tables. Note that FA_ADDITIONS_B also carries a self-referencing foreign key on PARENT_ASSET_ID, which introduces a hierarchical edge within the hub and supports parent/child (group) asset relationships.

Key Information Stored

The table is documented with 80 columns. The most significant are:

Common Use Cases and Queries

Because ASSET_ID is the hub key, most reporting joins FA_ADDITIONS_B to financial satellites such as FA_BOOKS and FA_DEPRN_SUMMARY. Typical scenarios include asset master extraction, tag verification, category roll-ups, and hierarchy reconciliation.

  • Asset master listing for a given category: 
    SELECT a.asset_number, a.tag_number, a.serial_number,
       c.category_name
FROM   fa_additions_b a, fa_categories_b c
WHERE  a.asset_category_id = c.category_id
AND    a.asset_number = :asset_number;
  • Joining the hub to cost and depreciation satellites: 
    SELECT a.asset_number, b.book_type_code, b.date_placed_in_service,
       d.cost, d.ytd_deprn
FROM   fa_additions_b a, fa_books b, fa_deprn_summary d
WHERE  a.asset_id = b.asset_id
AND    b.book_type_code = d.book_type_code
AND    b.asset_id = d.asset_id;
  • Resolving parent/child hierarchy via the self-join on PARENT_ASSET_ID for group asset roll-ups.
  • Validating descriptive flexfield values through ATTRIBUTE_CATEGORY_CODE and CONTEXT.
  • Reconciling asset numbers against interface staging tables such as FA_MASSADD_REP_ITF and FA_TAX_INTERFACE using GROUP_ASSET_NUMBER / ASSET_NUMBER.

Related Objects

FA_ADDITIONS_B is referenced by a broad set of Fixed Assets tables. The most significant dependencies are:

  • FA_BOOKS — Reference by ASSET_ID; stores book-specific cost and depreciation attributes.
  • FA_DEPRN_SUMMARY — Reference by ASSET_ID; periodic depreciation balances.
  • FA_BOOKS_SUMMARY — Reference by ASSET_ID and GROUP_ASSET_ID.
  • FA_CATEGORIES_B — Referenced via ASSET_CATEGORY_ID (asset default rules).
  • FA_LEASES — Referenced via LEASE_ID.
  • FA_ASSET_KEYWORDS — Referenced via ASSET_KEY_CCID.
  • FA_ASSET_HISTORY — Reference by ASSET_ID; audit trail of asset changes.
  • FA_ADJUSTMENTS — Reference by ASSET_ID; cost and unit adjustments.
  • FA_TRANSACTION_HEADERS — Reference by ASSET_ID; source of posted transactions.
  • PA_PROJECT_ASSETS_ALL — Reference by FA_ASSET_ID, PARENT_ASSET_ID, and RET_TARGET_ASSET_ID, linking project assets to Fixed Assets.

These relationships confirm FA_ADDITIONS_B as the hub from which the majority of Fixed Assets transactional and reporting objects derive their key lineage.