Search Results ibc_citem_version_labels




Overview
Explore in AI Chat

Overview

The IBC_CITEM_VERSION_LABELS table is a core data object within the Oracle E-Business Suite Content Manager (IBC) module. It functions as a junction table that manages the many-to-many relationship between content item versions and labels. Its primary role is to store the explicit association between a specific version of a content item and one or more labels, enabling sophisticated content categorization, organization, and retrieval. This table is critical for implementing a flexible labeling taxonomy, allowing administrators and users to tag content versions with descriptive codes for filtering, reporting, and access control purposes across the application.

Key Information Stored

The table's structure is defined by a composite primary key and several foreign key relationships, ensuring referential integrity. The key columns are:

  • LABEL_CODE: A foreign key referencing IBC_LABELS_B.LABEL_CODE. This column stores the unique identifier for a specific label within the system's taxonomy.
  • CONTENT_ITEM_ID: A foreign key referencing IBC_CONTENT_ITEMS.CONTENT_ITEM_ID. This identifies the master content item to which the version belongs.
  • CITEM_VERSION_ID: A foreign key referencing IBC_CITEM_VERSIONS_B.CITEM_VERSION_ID. This column is crucial as it pinpoints the exact version of the content item to which the label is attached, allowing labels to be applied with version-level granularity.

Together, the LABEL_CODE and CONTENT_ITEM_ID form the table's primary key (IBC_CITEM_VERSION_LABELS_PK), preventing duplicate label assignments for the same content item at the database level.

Common Use Cases and Queries

A primary use case is generating reports of all content item versions tagged with a particular label, such as "CONFIDENTIAL" or "MARKETING_2024". This supports compliance audits and content lifecycle management. Another common scenario is querying to find all labels applied to a specific published version of a document for display or validation. Sample SQL to retrieve labeled content versions would typically join this table with the content items and labels master tables:

  • Find all versions with a specific label:
    SELECT civl.content_item_id, civl.citem_version_id, civl.label_code
    FROM ibc_citem_version_labels civl
    WHERE civl.label_code = '&LABEL_CODE';
  • List all labels for a content item version:
    SELECT lb.label_code, lb.name
    FROM ibc_citem_version_labels civl, ibc_labels_b lb
    WHERE civl.label_code = lb.label_code
    AND civl.content_item_id = &CONTENT_ITEM_ID
    AND civl.citem_version_id = &VERSION_ID;

Related Objects

This table sits at the intersection of three key Content Manager entities, as defined by its foreign key constraints:

  • IBC_CONTENT_ITEMS: The master table for content items, referenced via CONTENT_ITEM_ID.
  • IBC_LABELS_B: The base table defining the label taxonomy, referenced via LABEL_CODE.
  • IBC_CITEM_VERSIONS_B: The base table storing all versions of content items, referenced via CITEM_VERSION_ID. This is the most direct relationship, anchoring the label to a specific version.

Development or integration work involving content labeling must interact with this table, often through the standard IBC public APIs, which ensure business logic and security are maintained when creating or modifying these associations.