Results for “old_asset_quantity”

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

Overview

CSI_I_ASSETS_H is the history (audit) table for the CSI_I_ASSETS entity within the Oracle E-Business Suite Install Base module (CSI). In Oracle EBS 12.1.1 and 12.2.2, the CSI schema maintains the customer product and asset install base — the repository of items, instances, and their relationships as delivered to and maintained at a customer site. CSI_I_ASSETS records the association between an instance and an asset. CSI_I_ASSETS_H preserves the before-and-after image of every change applied to such an association, keyed by a transaction that caused the change.

Under a heuristic Data Vault classification mined from the foreign-key structure, this object is best modeled as a link. It sits between the CSI_I_ASSETS association entity and CSI_TRANSACTIONS, capturing the transactional linkage and the state transition of each association record. This classification is a modeling suggestion derived from FK topology rather than a declarative Oracle attribute.

Key Information Stored

The table contains 34 documented columns. The most significant are:

• INSTANCE_ASSET_HISTORY_ID — the surrogate primary key (CSI_I_ASSETS_H_PK), uniquely identifying each historical revision row.
• INSTANCE_ASSET_ID — foreign key to CSI_I_ASSETS; identifies the association record being versioned. Together with TRANSACTION_ID it forms unique index CSI_I_ASSETS_H_U02, a strong business-key candidate.
• TRANSACTION_ID — foreign key to CSI_TRANSACTIONS, tying each history row to the originating install base transaction.
• OLD_INSTANCE_ID / NEW_INSTANCE_ID — the instance identifier before and after the change.
• OLD_FA_ASSET_ID / NEW_FA_ASSET_ID — linked Fixed Assets asset identifiers, before and after.
• OLD_ASSET_QUANTITY / NEW_ASSET_QUANTITY — quantities associated with the instance, before and after.
• OLD_ACTIVE_START_DATE / NEW_ACTIVE_START_DATE and OLD_ACTIVE_END_DATE / NEW_ACTIVE_END_DATE — effective-dating of the association.
• OLD_UPDATE_STATUS / NEW_UPDATE_STATUS — status of the Fixed Assets synchronization before and after.
• FULL_DUMP_FLAG — indicates whether the row records a complete snapshot rather than a delta.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org / security-group data segregation.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER for optimistic locking.

The unique index CSI_I_ASSETS_H_U01 covers INSTANCE_ASSET_HISTORY_ID (the surrogate), while CSI_I_ASSETS_H_U02 on (TRANSACTION_ID, INSTANCE_ASSET_ID) is the meaningful business-key candidate.

Common Use Cases and Queries

Because it is a history table, CSI_I_ASSETS_H supports audit reporting, reconciliation of Fixed Assets synchronization, and investigation into why an install base association changed.

Reconstruct the full change history of one association:

SELECT h.INSTANCE_ASSET_HISTORY_ID,
       h.TRANSACTION_ID,
       h.OLD_INSTANCE_ID, h.NEW_INSTANCE_ID,
       h.OLD_FA_ASSET_ID, h.NEW_FA_ASSET_ID,
       h.LAST_UPDATE_DATE
FROM   CSI.CSI_I_ASSETS_H h
WHERE  h.INSTANCE_ASSET_ID = :p_association_id
ORDER  BY h.INSTANCE_ASSET_HISTORY_ID;

Trace all associations touched by a given transaction:

SELECT a.INSTANCE_ASSET_ID,
       h.OLD_ASSET_QUANTITY, h.NEW_ASSET_QUANTITY,
       h.OLD_UPDATE_STATUS,   h.NEW_UPDATE_STATUS
FROM   CSI.CSI_I_ASSETS_H h,
       CSI.CSI_TRANSACTIONS t
WHERE  t.TRANSACTION_ID  = h.TRANSACTION_ID
AND    t.TRANSACTION_ID  = :p_transaction_id;

Report rows still pending Fixed Assets sync (NEW_FA_SYNC_FLAG or NEW_UPDATE_STATUS set to the unresolved value) or examine rows flagged MIGRATED_FLAG for data-conversion validation. Analytical queries commonly compare OLD_ versus NEW_ values to quantify how often instance, quantity, or effective dates were amended per transaction type.

Related Objects

• CSI_I_ASSETS — the parent association table; joined via INSTANCE_ASSET_ID. The history table exists to preserve its prior states.
• CSI_TRANSACTIONS — joined via TRANSACTION_ID; identifies the install base transaction that produced each history row.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID to enforce and report on data security partitions.
• CSI_I_ASSETS_H_PK / CSI_I_ASSETS_H_U01 / CSI_I_ASSETS_H_U02 — the primary and unique indexes that guarantee row identity and the (transaction, association) business key.
• Install Base APIs that insert or update CSI_I_ASSETS — for example the public Install Base / CSI instance-asset interfaces — implicitly generate rows in CSI_I_ASSETS_H as the accompanying audit trail.