Results for “fa_asset_history”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FA_ASSET_HISTORY is a transactional history table in the Oracle E-Business Suite Fixed Assets (OFA) module, owned by the FA schema. It records the historical chronology of asset reclassifications and unit adjustments, capturing the state of an asset — its category, asset type, and unit count — as it existed during the effective date ranges spanning each change. Rather than storing only the current attribute values found in FA_ADDITIONS_B, this table preserves the temporal progression of those attributes so that period-by-period reporting, retrospective queries, and audit reconciliation can reflect what the asset looked like at any given point in time.

From a Data Vault modeling perspective, the mined relationship structure classifies FA_ASSET_HISTORY as a link table. This is a heuristic suggestion: the table carries two foreign keys to FA_TRANSACTION_HEADERS (TRANSACTION_HEADER_ID_IN and TRANSACTION_HEADER_ID_OUT) plus keys to FA_ADDITIONS_B and FA_CATEGORIES_B, and its composite key (ASSET_ID, DATE_EFFECTIVE) reflects the intersection of an asset, a category, and its bounded transaction windows. In practice it behaves as a dated satellite-and-link hybrid, tracking attribute validity over time while associating each interval with the transactions that opened and closed it.

Key Information Stored

The primary key FA_ASSET_HISTORY_PK is a composite surrogate formed from ASSET_ID and DATE_EFFECTIVE; the two together uniquely identify each historical row. ASSET_ID is a foreign key to FA_ADDITIONS_B and establishes the asset whose history is tracked. DATE_EFFECTIVE and DATE_INEFFECTIVE define the validity interval for each recorded state, with DATE_EFFECTIVE delimiting the start of the segment and DATE_INEFFECTIVE marking its close, thereby enabling as-of and between-date queries.

The three principal business attributes subject to change are CATEGORY_ID (foreign key to FA_CATEGORIES_B, denoting the asset's category during the interval), ASSET_TYPE (the descriptive classification used for cost and depreciation processing), and UNITS (the number of units assigned to the asset, relevant to unit-of-production or quantity-based adjustments). Two foreign keys to FA_TRANSACTION_HEADERS, TRANSACTION_HEADER_ID_IN and TRANSACTION_HEADER_ID_OUT, identify the transactions that brought the interval into and out of effect — the incoming reclassification or adjustment and the subsequent superseding event. Standard audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture row maintenance metadata. Together these eleven columns preserve the full attribute history without duplicating the complete asset master record.

Common Use Cases and Queries

Typical usage centers on point-in-time reporting, reclassification audits, and unit-change analysis. Determining the attribute state of an asset on a specific date requires selecting the interval that contains that date:

• SELECT asset_id, category_id, asset_type, units FROM fa_asset_history WHERE asset_id = :asset_id AND :as_of_date BETWEEN date_effective AND NVL(date_ineffective, :as_of_date);
• Reclassification tracing: join TRANSACTION_HEADER_ID_IN and TRANSACTION_HEADER_ID_OUT to FA_TRANSACTION_HEADERS to identify which transactions changed an asset's category or units, supporting audit trails and period close reconciliation.
• Category migration reporting: aggregate rows by CATEGORY_ID and DATE_EFFECTIVE to measure how assets shifted between categories over a fiscal period.
• Unit adjustment analysis: compare UNITS across consecutive intervals for a given ASSET_ID to quantify unit increases or decreases tied to specific transactions.

Related Objects

The following are the most significant objects directly related through documented foreign key or dependency paths:

• FA_ADDITIONS_B — joined on FA_ASSET_HISTORY.ASSET_ID = FA_ADDITIONS_B.ASSET_ID; the asset master providing current values.
• FA_CATEGORIES_B — joined on FA_ASSET_HISTORY.CATEGORY_ID; supplies category code and description.
• FA_TRANSACTION_HEADERS — referenced twice, via TRANSACTION_HEADER_ID_IN and TRANSACTION_HEADER_ID_OUT; identifies the transactions bounding each interval.
• FA_TRANSACTION_LINES — commonly joined through the transaction headers to obtain line-level detail of the reclassification or adjustment.
• FA_DEPRN_SUMMARY and FA_DEPRN_DETAIL — depreciation records frequently reconciled against historical category and unit states.

These relationships make FA_ASSET_HISTORY an essential bridge between asset master data, category definitions, and the transaction stream that drives asset changes.