Search Results old_active_start_date




Overview
Explore in AI Chat

Overview

CSI_IAH_DETAILS_V is a reporting view in the Oracle E-Business Suite Install Base (CSI) module, owned by the APPS schema. Its name reflects its purpose: the Instance Asset History Details View. It presents a consolidated, denormalized picture of changes recorded against instance assets as transactions move assets through their lifecycle, contrasting the "old" state of an asset with the "new" state produced by each transaction. The view joins the Install Base instance asset history table to the current instance asset record and, critically, resolves both the prior and resulting fixed asset records along with their asset categories.

Because it exposes descriptive attributes that are otherwise distributed across multi-organization and reference tables, CSI_IAH_DETAILS_V is principally used for audit, reconciliation, and reporting. Personnel investigating why an asset's fixed asset linkage, category, or identifying attributes changed can query a single view rather than reconstruct the history manually. The column NEW_SERIAL_NUMBER, frequently sought by users, is one such resolved descriptor; it surfaces the serial number of the fixed asset after the transaction, while OLD_SERIAL_NUMBER gives the pre-transaction value, enabling direct comparison of serial number changes.

Underlying Base Objects

The ETRM metadata documents four referenced base objects, all exposed through synonyms:

  • CSI_I_ASSETS_H — the instance asset history table, aliased CIAH; the primary driving table supplying transaction identifiers and the old/new paired columns.
  • CSI_I_ASSETS — the current instance asset table, aliased CIA; joined on INSTANCE_ASSET_ID purely to return INSTANCE_ID.
  • FA_ADDITIONS — the Oracle Assets addition table, joined twice under the aliases OAD (old) and NAD (new) to resolve asset number, tag number, and serial number.
  • FA_CATEGORIES_B — the Assets category table, also joined twice (OCA and NCA) to resolve major and sub category segments.

Notably, every join to FA_ADDITIONS and FA_CATEGORIES_B is an outer join, so history rows are preserved even when the old or new fixed asset cannot be resolved, which is important when assets are pending or were never fully transferred to Oracle Assets.

Key Columns

The view returns three groups of columns. The history keys and quantities include INSTANCE_ASSET_HISTORY_ID, INSTANCE_ASSET_ID, TRANSACTION_ID, OLD/NEW_INSTANCE_ID, OLD/NEW_FA_ASSET_ID, and OLD/NEW_ASSET_QUANTITY. The dating and status columns include OLD/NEW_ACTIVE_START_DATE, OLD/NEW_ACTIVE_END_DATE, OLD/NEW_UPDATE_STATUS, and OLD/NEW_FA_BOOK_TYPE_CODE, which capture book type context for the fixed asset linkage. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER provide audit and concurrency information. The resolved descriptive columns derived from the outer joins are OLD_ASSET_NUMBER, OLD_TAG_NUMBER, OLD_SERIAL_NUMBER, OLD_MAJOR_CATEGORY, OLD_SUB_CATEGORY and their NEW_ counterparts.

Common Use Cases and Queries

Typical uses include auditing serial number or asset number changes, verifying category movements, and reconciling Install Base history against Oracle Assets. A search for NEW_SERIAL_NUMBER corresponds to finding transactions in which the resulting fixed asset serial number differs from OLD_SERIAL_NUMBER. For example:

  • Locating transactions where the serial number changed: SELECT INSTANCE_ASSET_ID, TRANSACTION_ID, OLD_SERIAL_NUMBER, NEW_SERIAL_NUMBER FROM CSI_IAH_DETAILS_V WHERE OLD_SERIAL_NUMBER <> NEW_SERIAL_NUMBER.
  • Reviewing the full history of one asset: SELECT * FROM CSI_IAH_DETAILS_V WHERE INSTANCE_ASSET_ID = :instance_asset_id ORDER BY CREATION_DATE.
  • Confirming category shifts: SELECT TRANSACTION_ID, OLD_MAJOR_CATEGORY, NEW_MAJOR_CATEGORY FROM CSI_IAH_DETAILS_V.

Because all fixed asset joins are outer, queries should tolerate null descriptors for unresolved old or new asset rows.