Results for “new_active_end_date”

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

Overview

CSI_IEA_VALUES_H is the Instance Extended Attribute Values History table in the CSI (Install Base) product module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the audit trace of changes made to instance extended attribute values (CSI_IEA_VALUES) that are linked to install base transactions. Every time an instance's extended attribute value is inserted, updated, or otherwise modified through a transaction, this history table preserves both the prior state and the resulting state of the record, enabling full temporal reconstruction of attribute value data for installed assets, configurations, and customer products.

Within Oracle Install Base, extended attributes capture customer-defined or seeded descriptive flexfield-style data attached to an instance (item instance, configuration, or component). The history table acts as the transactional counterpart that logs deltas against those values. From a Data Vault modeling perspective, the mined foreign key structure suggests classifying CSI_IEA_VALUES_H as a link entity — it connects a transaction event (CSI_TRANSACTIONS) to a base attribute value (CSI_IEA_VALUES) while carrying descriptive change payload. This classification is heuristic and offered as a modeling suggestion rather than an EBS-imposed constraint.

Key Information Stored

The table contains 50 documented columns. The most significant include:

• ATTRIBUTE_VALUE_HISTORY_ID — the surrogate primary key, enforced by CSI_IEA_VALUES_H_PK and also covered by unique index CSI_IEA_VALUES_H_U01. This is the identifier users typically search for when tracing a specific change event.
• ATTRIBUTE_VALUE_ID — the foreign key to CSI_IEA_VALUES, identifying which base attribute value row was altered.
• TRANSACTION_ID — the foreign key to CSI_TRANSACTIONS, tying the history record to the originating install base transaction.
• OLD_ATTRIBUTE_VALUE / NEW_ATTRIBUTE_VALUE — the pre- and post-change values of the extended attribute.
• OLD_ACTIVE_START_DATE / NEW_ACTIVE_START_DATE and OLD_ACTIVE_END_DATE / NEW_ACTIVE_END_DATE — effective-dating pairs establishing the validity window before and after the change.
• OLD_CONTEXT / NEW_CONTEXT — the descriptive flexfield context code before and after modification.
• OLD_ATTRIBUTE1 … NEW_ATTRIBUTE15 — fifteen paired descriptive flexfield segments capturing detailed pre/post values.
• FULL_DUMP_FLAG — indicates whether the history row represents a complete snapshot rather than a delta.
• MIGRATED_FLAG — flags records brought forward by migration or upgrade processes.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS supporting multi-organization data security.
• Standard WHO/audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.

The second unique index, CSI_IEA_VALUES_H_U02 (TRANSACTION_ID, ATTRIBUTE_VALUE_ID), represents the documented business-key candidate and guarantees a single history row per transaction-attribute combination.

Common Use Cases and Queries

Typical uses include audit reporting on attribute changes for an installed asset, reconstructing the value of an extended attribute as of a prior date, and diagnosing transaction-driven updates. A representative query retrieves change history for one attribute value:

• SELECT attribute_value_history_id, transaction_id, old_attribute_value, new_attribute_value, old_active_start_date, new_active_start_date FROM csi.csi_iea_values_h WHERE attribute_value_id = :attribute_value_id ORDER BY creation_date;

To trace which transaction changed a value, join to CSI_TRANSACTIONS on TRANSACTION_ID. To find history tied to a specific instance, join CSI_IEA_VALUES on ATTRIBUTE_VALUE_ID and then to the instance tables. Reporting teams frequently use FULL_DUMP_FLAG to separate snapshot rows from delta rows and MIGRATED_FLAG to isolate upgrade-generated history.

Related Objects

• CSI_IEA_VALUES — the base attribute value table; joined on CSI_IEA_VALUES_H.ATTRIBUTE_VALUE_ID = CSI_IEA_VALUES.ATTRIBUTE_VALUE_ID.
• CSI_TRANSACTIONS — the originating transaction; joined on CSI_IEA_VALUES_H.TRANSACTION_ID = CSI_TRANSACTIONS.TRANSACTION_ID.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data security partitioning.
• CSI_ITEM_INSTANCES — reached indirectly through CSI_IEA_VALUES to identify the affected instance.
• CSI_IEA_VALUES_H_PK / CSI_IEA_VALUES_H_U01 / CSI_IEA_VALUES_H_U02 — the primary and unique indexes governing row identity and uniqueness.
• Install Base audit and reporting views built over CSI_IEA_VALUES_H for attribute change tracking.