Search Results ibc_compound_relations




Overview
Explore in AI Chat

Overview

The IBC_COMPOUND_RELATIONS table is a core data structure within the Oracle E-Business Suite Content Manager module (IBC). It functions as a relational mapping table that defines the internal composition of compound content items. In the IBC data model, a compound item is a complex content object constructed from multiple component items, each potentially representing a distinct attribute or piece of the whole. This table specifically stores the relationships that link a parent compound item to its individual component content items, based on attributes defined as having a component data type. Its role is essential for maintaining the integrity and structure of compound documents, enabling the system to assemble and manage these composite entities accurately across versions and deployments in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's primary purpose is to associate a component content item with a specific attribute of a compound item. Key columns include COMPOUND_RELATION_ID, which serves as the unique primary key for each relationship record. The CONTENT_ITEM_ID column references the parent compound content item from the IBC_CONTENT_ITEMS table. The ATTRIBUTE_TYPE_CODE and CONTENT_TYPE_CODE together identify the specific attribute of the compound item that is of component type, linking to the IBC_ATTRIBUTE_TYPES_B table. Crucially, the CITEM_VERSION_ID column stores the identifier for the specific version of the component content item being used, referencing the IBC_CITEM_VERSIONS_B table. This version-specific linkage ensures that the composition of a compound item is preserved and consistent for a given state of its components.

Common Use Cases and Queries

A primary use case is the retrieval of all components for a given compound item, often for rendering, validation, or lifecycle management. For instance, an application may need to list all component items that make up a specific marketing brochure (compound item). A typical query would join IBC_COMPOUND_RELATIONS to IBC_CONTENT_ITEMS and IBC_CITEM_VERSIONS_B to fetch component details. Another common scenario is impact analysis: determining which compound items are affected if a particular component item is updated or made obsolete. Developers might also query this table when building custom reports on content structure or when debugging issues related to compound item assembly. Sample SQL to find components for a compound item would be:

  • SELECT comp_rel.*, comp_ver.version_number
  • FROM ibc_compound_relations comp_rel,
  • ibc_citem_versions_b comp_ver
  • WHERE comp_rel.content_item_id = :p_compound_item_id
  • AND comp_rel.citem_version_id = comp_ver.citem_version_id;

Related Objects

The IBC_COMPOUND_RELATIONS table is centrally connected to other fundamental Content Manager tables via foreign key constraints. Its primary relationship is with IBC_CONTENT_ITEMS, which stores the master definition of all content items, including the parent compound. It links to IBC_ATTRIBUTE_TYPES_B to validate the attribute type code and content type code for the component attribute. Most significantly, it references IBC_CITEM_VERSIONS_B to pinpoint the exact version of a component item used in the relationship. The table's primary key constraint is IBC_COMPOUND_RELATIONS_PK. Any processes, APIs, or user interfaces that create, update, or dismantle compound content items will inherently interact with this table to manage its compositional data.