Search Results fa_additions_b

Overview

The FA_ADDITIONS_B table is the core master data table for fixed assets within Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2. As the base table for the Multi-Language Support (MLS) architecture, it stores the fundamental descriptive and identifying information for every asset tracked in the Fixed Assets module. Its primary role is to serve as the central repository for asset definitions, from which all transactional, depreciation, and reporting processes flow. The existence of numerous foreign key relationships from critical transactional tables, such as FA_BOOKS and FA_ADJUSTMENTS, underscores its foundational position in the asset lifecycle.

Key Information Stored

The table's structure is designed to capture essential asset metadata. The primary key is the system-generated ASSET_ID, which uniquely identifies each asset record internally. The ASSET_NUMBER serves as a unique business key (enforced by the FA_ADDITIONS_B_UK1 unique key) and is the primary identifier used by end-users. Other critical columns include ASSET_CATEGORY_ID, which links to FA_CATEGORIES_B for classification; PARENT_ASSET_ID, which enables hierarchical asset structures by self-referencing the same table; and LEASE_ID for leased asset tracking. Additional columns typically hold data such as asset description, serial number, model number, and in-service date, forming the complete asset profile.

Common Use Cases and Queries

This table is central to virtually all asset reporting and data validation. Common use cases include generating asset registers, validating asset numbers during mass additions or invoice imports, and tracing the parent-child relationships within grouped assets. A fundamental query to retrieve a basic asset listing would join to the category table for descriptive information:

• Asset Master Listing: SELECT a.asset_number, a.description, c.category_name FROM fa_additions_b a, fa_categories_b c WHERE a.asset_category_id = c.category_id AND a.date_effective <= SYSDATE;
• Hierarchy Analysis: Queries utilizing self-joins on PARENT_ASSET_ID are used to roll up costs for summary reporting or to analyze asset structures.
• Integration Validation: When reconciling assets between FA and other modules like Payables or Projects, queries against FA_ADDITIONS_B using ASSET_NUMBER or ASSET_ID are essential for verifying existence and status.

Related Objects

As indicated by the extensive foreign key metadata, FA_ADDITIONS_B is referenced by a vast network of transactional and supporting tables. Key dependencies include:

• FA_BOOKS / FA_BOOKS_SUMMARY: Store asset financial information and depreciation rules per book.
• FA_ADJUSTMENTS / FA_DEPRN_DETAIL: Record capital adjustments and depreciation transactions.
• FA_ASSET_INVOICES: Links assets to their source invoices from Payables.
• FA_ASSET_HISTORY: Tracks changes to key asset attributes over time.
• CSI_I_ASSETS: Enables integration with the Installed Base module, linking an EBS asset to a serviceable item.

This web of relationships confirms that FA_ADDITIONS_B is the singular source of truth for an asset's existence, with all other tables managing financial, transactional, or integration data associated with that asset record.