Search Results csi_i_version_labels_h_u02

Overview

The CSI.CSI_I_VERSION_LABELS_H table is an audit history table within the Oracle E-Business Suite Install Base (CSI) module. It stores the complete change history of Instance Version Label records maintained in the base table CSI.CSI_I_VERSION_LABELS. In Oracle EBS 12.1.1 and 12.2.2, the CSI schema manages installed base instances and their version tracking. This table captures every insert, update, and delete operation performed against version labels, preserving both the prior state (OLD_ columns) and the resulting state (NEW_ columns) of each changed attribute.

Because the table records the before-and-after image of each version label change alongside the transaction that produced it, it functions as an audit trail and supports historical reporting, reconciliation, and troubleshooting of version label data. Under Data Vault modeling heuristics, this object is best classified as a link table: it associates a version label (VERSION_LABEL_ID → CSI_I_VERSION_LABELS), the transaction that changed it (TRANSACTION_ID → CSI_TRANSACTIONS), and the security group that owns it (SECURITY_GROUP_ID → FND_SECURITY_GROUPS). It is a transactional association rather than a pure descriptive satellite.

Key Information Stored

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

• VERSION_LABEL_HISTORY_ID — Surrogate primary key (CSI_I_VERSION_LABELS_H_PK) identifying each history record; defined by unique index U01.
• VERSION_LABEL_ID — Foreign key to the base table CSI_I_VERSION_LABELS; identifies which version label was changed.
• TRANSACTION_ID — Foreign key to CSI_TRANSACTIONS; identifies the transaction responsible for the change. Together with VERSION_LABEL_ID it forms the business-key unique index U02.
• OLD_VERSION_LABEL / NEW_VERSION_LABEL — Prior and current version label values (VARCHAR2(30)).
• OLD_DESCRIPTION / NEW_DESCRIPTION — Prior and current descriptive text (VARCHAR2(240)).
• OLD_DATE_TIME_STAMP / NEW_DATE_TIME_STAMP — Timestamps before and after modification.
• OLD_ACTIVE_START_DATE / NEW_ACTIVE_START_DATE and OLD_ACTIVE_END_DATE / NEW_ACTIVE_END_DATE — Effective date range changes for the label.
• OLD_CONTEXT / NEW_CONTEXT and OLD_ATTRIBUTE1 through OLD/NEW_ATTRIBUTE15 — Descriptive Flexfield (DFF) context and attribute history, captured as paired OLD/NEW columns.
• SECURITY_GROUP_ID — Multi-org/security grouping reference to FND_SECURITY_GROUPS.
• FULL_DUMP_FLAG and MIGRATED_FLAG — Flags indicating full-record capture or migration origin.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns and optimistic locking support.

The unique index U01 enforces uniqueness on the surrogate key, while U02 enforces uniqueness per transaction and version label. Nonunique index N01 accelerates lookups by VERSION_LABEL_ID. The table resides in APPS_TS_TX_DATA with indexes in APPS_TS_TX_IDX.

Common Use Cases and Queries

Typical uses include auditing who changed a version label, when, and through which transaction; reconstructing the state of a label at a point in time; and diagnosing discrepancies between base and history data during support investigations.

Sample query returning the change history for a specific version label:

• SELECT h.version_label_id, h.transaction_id, h.old_version_label, h.new_version_label, h.old_active_end_date, h.new_active_end_date, h.last_updated_by, h.last_update_date FROM csi.csi_i_version_labels_h h WHERE h.version_label_id = :label_id ORDER BY h.version_label_history_id DESC;

To correlate changes with their originating transaction:

• SELECT h.version_label_id, t.transaction_id, t.transaction_date FROM csi.csi_i_version_labels_h h JOIN csi.csi_transactions t ON t.transaction_id = h.transaction_id WHERE h.new_version_label = :value;

Reporting use cases include version-label change volume by period, DFF attribute change tracking (OLD_ATTRIBUTEn versus NEW_ATTRIBUTEn), and audit extracts for compliance. Because the DFF columns are stored as paired OLD/NEW pairs, comparisons are straightforward using column-to-column predicates.

Related Objects

• CSI.CSI_I_VERSION_LABELS — Base table; joined on VERSION_LABEL_ID.
• CSI.CSI_TRANSACTIONS — Transaction master; joined on TRANSACTION_ID.
• FND_SECURITY_GROUPS — Security grouping reference; joined on SECURITY_GROUP_ID.
• CSI.CSI_I_OBJECTS_H — Parallel history table for instance objects, useful for correlated audit reporting.
• CSI.CSI_ITEM_INSTANCES — Installed base instance records that reference version labels.
• CSI_INSTANCE_VERSION_LABEL_PUB / CSI APIs — Public APIs that manipulate version labels and therefore populate this history table indirectly.

The table is not directly maintained by users; it is populated programmatically as changes flow through the CSI version label APIs.