Search Results ibc_citem_versions_b




Overview
Explore in AI Chat

Overview

The IBC_CITEM_VERSIONS_B table is a core data object within the Oracle E-Business Suite Content Manager (IBC) module. It serves as the central repository for storing all historical and current versions of content items managed by the system. Every time a content item, such as a marketing document, legal clause, or product description, is created or modified, a new version record is inserted into this table. This design enables robust version control, audit trails, and content lifecycle management, allowing users to track changes, revert to previous versions, and maintain a definitive version history for each piece of content. Its role is foundational to the content management capabilities across EBS applications.

Key Information Stored

While the provided metadata does not list specific columns, the primary and foreign key relationships define its critical structure. The primary key, CITEM_VERSION_ID, uniquely identifies each version record. The essential foreign key, CONTENT_ITEM_ID, links the version to its master definition in the IBC_CONTENT_ITEMS table. Other inferred columns typically include version-specific metadata such as a version number, the effective start and end dates for the version's validity, the status (e.g., Draft, Approved, Live), and creation details (created by, creation date). The table's relationship with IBC_CONTENT_ITEMS.LIVE_CITEM_VERSION_ID indicates it stores the pointer to identify which version is currently active or published.

Common Use Cases and Queries

A primary use case is retrieving the complete version history for a specific content item for audit or review purposes. Another is identifying the currently live version of an item for display or processing in other modules. The user's search for "prp_proposal_ctntvers" directly relates to a common integration: the Proposals (PRP) module references specific content item versions within proposals via the PRP_PROPOSAL_CTNTVERS table. A typical query would join these tables to fetch proposal content.

  • Sample Query: To find all content item versions used in a specific proposal:
    SELECT p.proposal_id, c.content_item_id, c.version_number, cv.*
    FROM prp_proposal_ctntvers p,
        ibc_citem_versions_b cv,
        ibc_content_items c
    WHERE p.citem_version_id = cv.citem_version_id
    AND cv.content_item_id = c.content_item_id
    AND p.proposal_id = :p_proposal_id;

Related Objects

The table maintains extensive relationships within the IBC module and integrates with other EBS products. Key related objects include:

  • IBC_CONTENT_ITEMS: The parent table containing the core definition of the content item.
  • IBC_CITEM_VERSIONS_TL: The translated descriptions and titles for each content item version.
  • PRP_PROPOSAL_CTNTVERS: Links specific content versions to proposals in the Proposals module, as indicated by the user's search term.
  • PRP_PERZ_FILES: Associates personalized files with content versions in Proposals.
  • PV_PARTNER_PROGRAM_B: Links content versions to partner programs in the Partner Management (PV) module.
  • IBC_COMPOUND_RELATIONS & IBC_CITEM_VERSION_LABELS: Support advanced content management features like compound documents and version tagging.