Search Results new_sub_category

Overview

APPS.CSI_IAH_DETAILS_V is a reporting and inquiry view in the Oracle E-Business Suite Install Base (CSI) module. The acronym "IAH" denotes Instance Asset History, and the view exposes audit-style records that capture changes made to instance-asset relationships and their associated fixed asset attributes. It is registered in FND Design Data as CSI.CSI_IAH_DETAILS_V and is documented as Internal / Oracle Internal Use Only: Oracle Corporation does not support access to application data through this object except from standard Oracle Applications programs. This status means it is intended for use by seeded Install Base forms, concurrent programs, and interfaces rather than for direct customer reporting.

The view presents paired "OLD_" and "NEW_" column sets, reflecting a before-and-after image of each change event. This design makes it valuable for troubleshooting asset lifecycle discrepancies and for reconstructing historical states, but the internal-only designation requires that any custom use be validated carefully against Oracle support policy.

Underlying Base Objects

The documented base objects referenced by the view are CSI_I_ASSETS (synonym), CSI_I_ASSETS_H (synonym), FA_ADDITIONS (synonym), and FA_CATEGORIES_B (synonym).

• CSI_I_ASSETS — the current-state table of instance-asset relationships, providing the present association between an instance and a fixed asset.
• CSI_I_ASSETS_H — the history (audit) table retaining prior versions of those relationships, which is the primary source of the OLD_/NEW_ value pairs.
• FA_ADDITIONS — the Fixed Assets table of asset additions, supplying asset number, tag number, and serial number attributes.
• FA_CATEGORIES_B — the Fixed Assets category definitions, supplying major category and sub-category descriptions.

The view therefore joins Install Base history records to Fixed Assets reference data, enriching the transaction history with descriptive asset attributes.

Key Columns

• INSTANCE_ASSET_HISTORY_ID / INSTANCE_ASSET_ID / TRANSACTION_ID — primary history key, the related instance-asset association, and the transaction that drove the change.
• INSTANCE_ID, OLD_INSTANCE_ID, NEW_INSTANCE_ID — the instance context plus prior and resulting instance identifiers.
• OLD_FA_ASSET_ID / NEW_FA_ASSET_ID — the fixed asset before and after the change.
• OLD_TAG_NUMBER / NEW_TAG_NUMBER — the fixed asset tag number before and after the change, each VARCHAR2(15). This is the column set most relevant to users searching on "old_tag_number," enabling identification of the prior tag number on a re-tagged asset.
• OLD_ASSET_NUMBER / NEW_ASSET_NUMBER, OLD_SERIAL_NUMBER / NEW_SERIAL_NUMBER — prior and resulting asset and serial numbers.
• OLD_MAJOR_CATEGORY / NEW_MAJOR_CATEGORY, OLD_SUB_CATEGORY / NEW_SUB_CATEGORY — category attributes drawn from FA_CATEGORIES_B.
• OLD_ASSET_QUANTITY / NEW_ASSET_QUANTITY, OLD_FA_BOOK_TYPE_CODE / NEW_FA_BOOK_TYPE_CODE, OLD_FA_LOCATION_ID / NEW_FA_LOCATION_ID, OLD_UPDATE_STATUS / NEW_UPDATE_STATUS — quantity, depreciation book, location, and FA update status transitions.
• OLD_ACTIVE_START_DATE / NEW_ACTIVE_START_DATE, OLD_ACTIVE_END_DATE / NEW_ACTIVE_END_DATE — effective date range changes.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, and FULL_DUMP_FLAG.

Common Use Cases and Queries

Typical scenarios include auditing tag number changes, reconciling Install Base history against Fixed Assets, and diagnosing why an asset association changed. Because the view is internal-only, queries should be restricted to diagnostic use.

SELECT instance_asset_history_id
     , old_tag_number
     , new_tag_number
     , old_asset_number
     , new_asset_number
     , creation_date
  FROM apps.csi_iah_details_v
 WHERE old_tag_number = 'ASSET-TAG-001';

A second pattern traces the full history for a given asset:

SELECT instance_asset_id
     , transaction_id
     , old_tag_number
     , new_tag_number
     , old_update_status
     , new_update_status
     , last_update_date
  FROM apps.csi_iah_details_v
 WHERE new_fa_asset_id = :p_fa_asset_id
 ORDER BY last_update_date DESC;

These queries illustrate the view's central purpose: surfacing the prior "old_tag_number" and related attributes so that asset history changes can be examined and reconciled.