Results for “ibc_citem_version_labels”

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

Overview

IBC_CITEM_VERSION_LABELS is a table owned by the IBC schema within the Oracle E-Business Suite Content Manager (IBC) product module. As its documented description states, the table "stores the association between a label and the version of any content item." In practical terms, it acts as a junction table that links a reusable label definition to a specific version of a content item, enabling label-driven classification, tagging, and retrieval of versioned content across the Content Manager repository.

Content Manager is the repository layer used by Oracle iLearning and related content delivery applications, where content items are authored, versioned, and published. Because a single content item may have many versions over its lifecycle, and because labels are commonly reused across many items, the relationship between labels and versions is inherently many-to-many. This table resolves that relationship. Its documented unique index, IBC_CITEM_VERSION_LABELS_U1 on (CONTENT_ITEM_ID, LABEL_CODE, ZD_EDITION_NAME), enforces that a given label is applied only once per content item within an edition.

Regarding Data Vault modeling, the mined heuristic classification for this object is link. This is consistent with its structure: it carries no descriptive attributes of its own beyond audit and key columns, and it exists primarily to associate the hub-like entities IBC_CONTENT_ITEMS, IBC_LABELS_B, and IBC_CITEM_VERSIONS_B. Treat this classification as a modeling suggestion rather than a formally documented fact.

Key Information Stored

The documented physical schema lists 11 columns. The most significant are:

• CONTENT_ITEM_ID — Identifier of the content item to which the label association applies; foreign key to IBC_CONTENT_ITEMS.
• LABEL_CODE — The label being associated; foreign key to IBC_LABELS_B, which holds label definitions.
• CITEM_VERSION_ID — The specific content item version being labeled; foreign key to IBC_CITEM_VERSIONS_B.
• SECURITY_GROUP_ID — Multi-tenant / organization security partition; foreign key to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications framework to detect concurrent updates.
• ZD_EDITION_NAME — Edition identifier supporting edition-based redefinition (EBR), present in 12.2.x schemas and integral to the unique index.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording who created and last modified each row and when.

The documented primary key is IBC_CITEM_VERSION_LABELS_PK on (LABEL_CODE, CONTENT_ITEM_ID). A separate unique index, IBC_CITEM_VERSION_LABELS_U1, serves as the business-key candidate across (CONTENT_ITEM_ID, LABEL_CODE, ZD_EDITION_NAME). Note that while the PK uses LABEL_CODE and CONTENT_ITEM_ID, the version-level granularity is carried through CITEM_VERSION_ID and the edition column.

Common Use Cases and Queries

Typical usage centers on answering which labels apply to a given content item or version, and which content items carry a particular label—useful for catalog browsing, compliance tagging, and content reuse reporting.

• Retrieve all labels for a content item:
  SELECT v.LABEL_CODE FROM IBC.IBC_CITEM_VERSION_LABELS v WHERE v.CONTENT_ITEM_ID = :item_id;
• Find all content items carrying a specific label:
  SELECT CONTENT_ITEM_ID, CITEM_VERSION_ID FROM IBC.IBC_CITEM_VERSION_LABELS WHERE LABEL_CODE = :code;
• Join to label definitions to resolve descriptive label text:
  SELECT l.NAME, v.CONTENT_ITEM_ID FROM IBC.IBC_CITEM_VERSION_LABELS v JOIN IBC.IBC_LABELS_B l ON l.LABEL_CODE = v.LABEL_CODE;
• Reporting on published versus draft versions by restricting CITEM_VERSION_ID against IBC_CITEM_VERSIONS_B.

Reports should always filter or group by SECURITY_GROUP_ID to respect multi-org data partitioning, and should consider ZD_EDITION_NAME when querying 12.2.x data to avoid crossing edition boundaries.

Related Objects

The following tables are directly referenced or dependent through the documented foreign keys:

• IBC_CONTENT_ITEMS — parent of CONTENT_ITEM_ID; defines the content item itself.
• IBC_LABELS_B — parent of LABEL_CODE; stores label definitions and metadata.
• IBC_CITEM_VERSIONS_B — parent of CITEM_VERSION_ID; holds the individual version records of content items.
• FND_SECURITY_GROUPS — parent of SECURITY_GROUP_ID; governs organization-level access partitioning.

Together these objects form the labeling and versioning subsystem of the Content Manager repository, and this table is the associative link that binds them.