Search Results ibc_content_items_uk

Overview

The IBC_CONTENT_ITEMS table is a core data object within the Oracle E-Business Suite Content Manager (IBC) module. It serves as the master repository for high-level, invariant metadata about content items. As indicated in the ETRM documentation, its primary role is to store non-version and non-language specific information. This establishes it as the central parent entity for all content managed within the system. Every piece of content, such as a document, image, or template, is first defined as a record in this table. The table holds the persistent identity of a content item, while its specific versions, translations, and binary data are managed in related child tables.

Key Information Stored

The table's structure is designed to manage content identity, classification, and lifecycle. The primary key is CONTENT_ITEM_ID, a unique system-generated identifier. A critical business key is the ITEM_REFERENCE_CODE, which also has a unique constraint (IBC_CONTENT_ITEMS_UK), often used for programmatic referencing. Other essential foreign key columns define the item's context and status: CONTENT_TYPE_CODE (links to IBC_CONTENT_TYPES_B for categorization), DIRECTORY_NODE_ID (links to IBC_DIRECTORY_NODES_B for folder-like organization), and LIVE_CITEM_VERSION_ID (points to IBC_CITEM_VERSIONS_B to identify the currently active version). Additional columns, inferred from standard IBC patterns, typically track creation and update dates, owner, security attributes, and system-level status flags.

Common Use Cases and Queries

This table is central to content discovery, administration, and integration reporting. Common operational queries involve listing content items by type, directory, or status. For instance, to find all active content items of a specific type with their live version details, a join to IBC_CITEM_VERSIONS_B is required. Administrators may query for orphaned items or items not assigned to a directory. The table is also frequently referenced in data fixes or audits to trace content lineage. A typical reporting pattern is:

• SELECT ci.item_reference_code, ci.content_item_id, ct.name content_type, cv.version_number
  FROM ibc_content_items ci,
  ibc_content_types_b ct,
  ibc_citem_versions_b cv
  WHERE ci.content_type_code = ct.content_type_code
  AND ci.live_citem_version_id = cv.citem_version_id
  AND ci.directory_node_id = :p_directory_id;

Related Objects

As the foundational table, IBC_CONTENT_ITEMS has extensive relationships. The ETRM metadata shows it is referenced by numerous key tables. IBC_CITEM_VERSIONS_B is the primary child table, storing each version of a content item. IBC_CONTENT_ITEM_NODES links items to multiple directories. IBC_ASSOCIATIONS and IBC_COMPOUND_RELATIONS manage relationships between items. For styling, IBC_STYLESHEETS and PRP_COMPONENT_STYLES_B reference it. Crucially, it integrates with other EBS modules, as shown by foreign keys from AMS_CONTENT_RULES_B (Marketing) and PRP_PROPOSALS (Proposals), demonstrating its role as a shared content service across the application suite.