Results for “compound_relation_id”

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

Overview

IBC_COMPOUND_RELATIONS is a transactional definition table owned by the IBC schema within the Oracle E-Business Suite Content Manager module. It records the association between a compound content item and the individual component content items that satisfy each component-typed attribute of that compound. In other words, when a content type is defined as a "compound" — meaning one or more of its attributes is itself of a component data type — this table persists the resolved component content item and its version for every such attribute instance.

The table is populated at runtime as compound content items are created, versioned, or reconfigured. Each row captures the pairing of a parent compound item's version, the attribute that consumes a component, and the concrete content item that fulfills it. The Data Vault classification heuristic, derived from its foreign key structure, suggests a link model: it sits between hubs (content items, attribute types, content item versions) and functions primarily as an associative relationship carrier rather than a descriptive satellite, though it retains some descriptive columns such as SORT_ORDER.

Key Information Stored

Documented metadata records 15 columns. The most significant include:

• COMPOUND_RELATION_ID — surrogate primary key defined by IBC_COMPOUND_RELATIONS_PK; uniquely identifies each compound-to-component association. It is also the leading column of unique index IBC_COMPOUND_RELATIONS_U1.
• CONTENT_ITEM_ID — the component content item referenced; foreign key to IBC_CONTENT_ITEMS.
• CITEM_VERSION_ID — the specific version of the content item involved, foreign key to IBC_CITEM_VERSIONS_B.
• ATTRIBUTE_TYPE_CODE — identifies which component-typed attribute of the compound item the row fulfills; foreign key to IBC_ATTRIBUTE_TYPES_B.
• CONTENT_TYPE_CODE — the content type context for the relationship.
• SORT_ORDER — controls ordering of components where the attribute allows multiple values.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enabling multi-org / row-level data segregation.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit and optimistic-locking columns.
• SUBITEM_VERSION_ID — version pointer for the subordinate/subitem component context.
• ZD_EDITION_NAME — edition marker used by the Content Manager's editioning scheme; appears in both unique indexes U1 and U2.

Business-key candidates: unique index IBC_COMPOUND_RELATIONS_U2 spans (ATTRIBUTE_TYPE_CODE, CITEM_VERSION_ID, CONTENT_ITEM_ID, CONTENT_TYPE_CODE, ZD_EDITION_NAME), representing the natural uniqueness of a component binding for a given attribute and version. IBC_COMPOUND_RELATIONS_U1 (COMPOUND_RELATION_ID, ZD_EDITION_NAME) reinforces the surrogate/edition combination.

Common Use Cases and Queries

Typical usage centers on resolving which components compose a versioned compound item, and on rendering or validating compound content structures.

• Resolve components for a compound version:

  SELECT cr.COMPOUND_RELATION_ID, cr.ATTRIBUTE_TYPE_CODE,
         cr.CONTENT_ITEM_ID, cr.CITEM_VERSION_ID, cr.SORT_ORDER
  FROM   IBC.IBC_COMPOUND_RELATIONS cr
  WHERE  cr.CITEM_VERSION_ID = :version_id
  AND    cr.SECURITY_GROUP_ID = :sg_id
  ORDER  BY cr.SORT_ORDER;

• Find all compounds that reference a given component item: filter CONTENT_ITEM_ID to identify reverse dependencies — useful before deleting or re-versioning a reused component.
• Attribute coverage reporting: join to IBC_ATTRIBUTE_TYPES_B to confirm that every component-typed attribute of a content type has a corresponding row, detecting incomplete compound definitions.
• Versioned lineage/audit: combine CITEM_VERSION_ID and ZD_EDITION_NAME to trace how component bindings changed across editions and versions.

Related Objects

• IBC_CONTENT_ITEMS — referenced via CONTENT_ITEM_ID; the master content item for the component.
• IBC_ATTRIBUTE_TYPES_B — referenced via ATTRIBUTE_TYPE_CODE; defines the component-typed attribute.
• IBC_CITEM_VERSIONS_B — referenced via CITEM_VERSION_ID; the versioned definition of the content item.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs visibility and multi-org isolation.
• IBC_COMPOUND_RELATIONS_PK / _U1 / _U2 — primary and unique indexes enforcing entity and business-key integrity.

Because it bridges content items, attribute types, and versions, IBC_COMPOUND_RELATIONS is central to any query that assembles or reports on compound content structures in Oracle EBS 12.1.1 and 12.2.2.