Search Results fa_additions_b_u1




Overview

FA.FA_ADDITIONS_B is the master (header) table for asset additions in the Oracle E-Business Suite Fixed Assets module. It holds one row per asset master record created through the Additions form, mass additions interface, or external interfaces. Every downstream transaction — depreciation, adjustments, retirements, transfers, revaluations, and tax book processing — anchors to the surrogate asset identifier defined here. Under the Data Vault classification heuristic mined from its foreign-key topology, FA_ADDITIONS_B behaves as a hub: it captures the durable business key (the asset) and serves as the central integration point for satellites such as FA_BOOKS, FA_DEPRN_DETAIL, and FA_ASSET_HISTORY, which record descriptive and transactional context keyed to the asset.

The table resides in the APPS_TS_TX_DATA tablespace and is registered as FND Design Data object OFA.FA_ADDITIONS_B with STATUS VALID. It carries the standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus DFF-style columns (ATTRIBUTE_CATEGORY_CODE, CONTEXT, ATTRIBUTE1–30, GLOBAL_ATTRIBUTE_CATEGORY, GLOBAL_ATTRIBUTE1–20).

Key Information Stored

The table defines three unique indexes: FA_ADDITIONS_B_U1 (ASSET_ID), FA_ADDITIONS_B_U2 (ASSET_NUMBER), and FA_ADDITIONS_B_U3 (TAG_NUMBER). ASSET_ID is the declared primary key (FA_ADDITIONS_B_PK) and is the surrogate identifier used throughout the FA schema. ASSET_NUMBER is the natural business key users recognize; queries issued against fa_additions_b_u2 target this unique index when looking up an asset by its user-facing number. TAG_NUMBER is a third unique business key, typically the physical or regulatory tag.

Common Use Cases and Queries

The most frequent access pattern is asset lookup by number, which exploits the unique index FA_ADDITIONS_B_U2:

  • SELECT asset_id, asset_number, tag_number, asset_category_id FROM fa_additions_b WHERE asset_number = :asset_number;
  • Join to FA_BOOKS for cost and depreciation: SELECT a.asset_number, b.book_type_code, b.cost FROM fa_additions_b a, fa_books b WHERE a.asset_id = b.asset_id;
  • Join to FA_CATEGORIES_B to resolve category descriptions: ... WHERE a.asset_category_id = c.category_id;
  • Locate child assets of a parent: SELECT * FROM fa_additions_b WHERE parent_asset_id = :asset_id;
  • Reconcile CIP, tax, and corporate book balances by driving reports from this hub and joining satellites FA_BOOKS, FA_DEPRN_SUMMARY, FA_ADJUSTMENTS, and FA_RETIREMENTS.
  • Audit additions posted in a period using CREATION_DATE or LAST_UPDATE_DATE for change tracking.

Reporting solutions (BI Publisher, Discoverer, or custom PL/SQL) generally treat FA_ADDITIONS_B as the driving table for asset master extracts, then left-join the appropriate book and depreciation satellites.

Related Objects

The FK topology of FA_ADDITIONS_B is dense; the most significant dependents and parents include:

  • FA_BOOKS (ASSET_ID → FA_ADDITIONS_B) — Book cost, depreciation method, and life per asset per book.
  • FA_CATEGORIES_B (via ASSET_CATEGORY_ID) — Category defaults referenced by each asset.
  • FA_ASSET_KEYWORDS (via ASSET_KEY_CCID) — Key flexfield combinations.
  • FA_LEASES (via LEASE_ID) — Lease terms for leased assets.
  • FA_ASSET_HISTORY (ASSET_ID) — Audit trail of changes to the asset master.
  • FA_DEPRN_DETAIL and FA_DEPRN_SUMMARY (ASSET_ID) — Period depreciation results.
  • FA_ADJUSTMENTS and FA_RETIREMENTS (ASSET_ID) — Cost and retirement transactions.
  • FA_MASS_ADDITIONS (ASSET_NUMBER, PARENT_ASSET_ID, ADD_TO_ASSET_ID) — Interface feeding New Assets.
  • FA_TRANSACTION_HEADERS (ASSET_ID) — Transaction wrapper for adjustments, transfers, and retirements.
  • PA_PROJECT_ASSETS_ALL (FA_ASSET_ID) — Project-to-asset linkage for capitalized CIP.

Self-referencing via PARENT_ASSET_ID supports composite and grouped asset reporting, and the table is referenced by interfaces including FA_TAX_INTERFACE, FA_MASS_RECLASS_ITF, and CSI_I_ASSETS.