Search Results version_label_id

Overview

The CSI_I_VERSION_LABELS table is a core Install Base (CSI) data object in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores instance version labels associated with customer product instances. In the Oracle EBS Install Base model, item instances represent tracked customer assets, and the version label captures the specific revision, software release, or configuration version that applies to an instance at a given point in time. The table is owned by the CSI schema and is documented as VALID in the ETRM repository.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this table as satellite-leaning. The descriptive attributes (version label text, timestamps, active date ranges, descriptive flexfields, and audit columns) cluster around a parent instance key, which is typical of a satellite attached to an instance-level hub. This classification is a heuristic suggestion derived from FK topology rather than a prescriptive design statement; the table remains a standard relational EBS entity with a surrogate primary key and unique index.

Key Information Stored

The documented physical schema contains 31 columns. The most significant are:

• VERSION_LABEL_ID — surrogate primary key, enforced by CSI_I_VERSION_LABELS_PK and also by unique index CSI_I_VERSION_LABELS_U01. It uniquely identifies each version-label record.
• INSTANCE_ID — foreign key to CSI_ITEM_INSTANCES, tying the version label to a specific tracked item instance. This is the primary business relationship in the table.
• VERSION_LABEL — the descriptive version or release identifier applied to the instance.
• DATE_TIME_STAMP — the effective timestamp associated with the version label record.
• DESCRIPTION — free-text explanation of the version label.
• ACTIVE_START_DATE and ACTIVE_END_DATE — date-effective range controlling when the label is considered active for the instance.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group access control at row level.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework for concurrent update control.
• MIGRATED_FLAG — indicates whether the row originated from a data migration rather than normal application entry.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield segment set, allowing customer-specific extension of the version-label record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard "who did what when" audit columns.

The surrogate key (VERSION_LABEL_ID) should be distinguished from the business relationship expressed by INSTANCE_ID, which is the meaningful join path to the instance hub. No composite business-key unique index is documented beyond the single-column unique index on VERSION_LABEL_ID.

Common Use Cases and Queries

The table is most commonly queried to report the version history of tracked instances, to determine which version was active on a given date, and to feed configuration or entitlement reporting. Typical patterns include:

• Version history for an instance: SELECT VERSION_LABEL, DATE_TIME_STAMP FROM CSI_I_VERSION_LABELS WHERE INSTANCE_ID = :instance_id ORDER BY DATE_TIME_STAMP;
• Currently active label: filter with ACTIVE_END_DATE IS NULL OR ACTIVE_END_DATE > SYSDATE combined with ACTIVE_START_DATE <= SYSDATE.
• Instance-to-version join for reporting: join to CSI_ITEM_INSTANCES on INSTANCE_ID to combine version data with instance name, serial number, and owner.
• Migration analysis: aggregate by MIGRATED_FLAG to confirm which version labels were loaded via conversion.
• Security-filtered extracts: always constrain by SECURITY_GROUP_ID or rely on the EBS security view layer when extracting across organizations.

Related Objects

The following objects are documented as directly related through PK/FK relationships:

• CSI_ITEM_INSTANCES — parent instance table; joined via CSI_I_VERSION_LABELS.INSTANCE_ID.
• CSI_I_VERSION_LABELS_H — history/audit shadow table; its VERSION_LABEL_ID references this table, capturing prior versions of each row.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for row-level access control.
• CSI_I_VERSION_LABELS_PK / CSI_I_VERSION_LABELS_U01 — the primary key constraint and unique index that enforce the surrogate key.

Together these objects form the version-tracking sub-model of the Install Base, where CSI_ITEM_INSTANCES anchors the instance hub and CSI_I_VERSION_LABELS provides the date-effective version detail.