Search Results csi_i_version_labels_h




Overview
Explore in AI Chat

Overview

CSI_I_VERSION_LABELS_H is a table in the CSI (Install Base) product module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. The object is documented as "Instance Version Labels History" and is owned by the CSI schema with a VALID status. Its purpose is to preserve the full historical record of changes made to instance version labels maintained by the Install Base application. Where CSI_I_VERSION_LABELS holds the current definition of a version label, CSI_I_VERSION_LABELS_H captures each prior and subsequent state of that label as it is created, modified, or retired.

From a Data Vault modeling perspective, the FK structure suggests that this table behaves as a link, connecting version label records to the transactions that altered them. Each row represents an auditable event rather than a static attribute set, which is characteristic of a link or transactional history construct.

Key Information Stored

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

Two unique indexes are documented: CSI_I_VERSION_LABELS_H_U01 on VERSION_LABEL_HISTORY_ID and CSI_I_VERSION_LABELS_H_U02 on (TRANSACTION_ID, VERSION_LABEL_ID). The latter is the strongest business-key candidate since it enforces one history entry per label per transaction. Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

Typical usage centers on auditing and reconstructing the evolution of version labels over time. A common pattern retrieves the change history for a specific label:

  • SELECT h.VERSION_LABEL_HISTORY_ID, h.OLD_VERSION_LABEL, h.NEW_VERSION_LABEL, h.OLD_DATE_TIME_STAMP, h.NEW_DATE_TIME_STAMP, t.TRANSACTION_ID FROM csi.csi_i_version_labels_h h JOIN csi.csi_transactions t ON h.TRANSACTION_ID = t.TRANSACTION_ID WHERE h.VERSION_LABEL_ID = :label_id ORDER BY h.CREATION_DATE;
  • Tracing which transaction last changed a label by joining on TRANSACTION_ID and filtering the maximum CREATION_DATE.
  • Reporting on labels active within a period using the OLD/NEW_ACTIVE_START_DATE and OLD/NEW_ACTIVE_END_DATE pairs.
  • Reconciling DFF attribute changes by comparing OLD_ATTRIBUTE[n] against NEW_ATTRIBUTE[n] for n = 1..15.

Related Objects

The following objects are most significant in relation to this table, based on documented FK and PK relationships:

  • CSI_I_VERSION_LABELS — parent label table, joined on CSI_I_VERSION_LABELS_H.VERSION_LABEL_ID = CSI_I_VERSION_LABELS.VERSION_LABEL_ID.
  • CSI_TRANSACTIONS — source of change transactions, joined on TRANSACTION_ID.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data access control.
  • CSI_I_VERSION_LABELS_H_PK — primary key constraint on VERSION_LABEL_HISTORY_ID.
  • CSI_I_VERSION_LABELS_H_U01 and CSI_I_VERSION_LABELS_H_U02 — unique indexes enforcing uniqueness of history rows and label/transaction combinations.

These relationships make the table a central audit reference for any analysis of Install Base version label lifecycle activity.