Search Results ibc_content_item_nodes




Overview
Explore in AI Chat

Overview

The IBC_CONTENT_ITEM_NODES 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 critical relationship between content items and the directory structure in which they are organized. Its primary role is to store the specific location information, defining under which directory node a given content item resides. This enables the hierarchical categorization and management of digital assets, such as documents, images, and files, within the EBS system. The table is essential for implementing folder-like navigation, access control based on location, and maintaining the integrity of the content repository's organizational schema across both EBS 12.1.1 and 12.2.2 versions.

Key Information Stored

The table's structure is designed to link content items to directory nodes. Its primary key is the system-generated identifier CONTENT_ITEM_NODE_ID. The two most significant foreign key columns are CONTENT_ITEM_ID, which references a specific record in the IBC_CONTENT_ITEMS table, and DIRECTORY_NODE_ID, which references a node in the IBC_DIRECTORY_NODES_B table. This many-to-many relationship allows a single content item to be linked to multiple directory nodes (e.g., filed in multiple folders) and a single directory node to contain many content items. Additional columns typically track creation and last update dates, the responsible user, and versioning information, though the provided metadata specifically highlights the core relationship columns.

Common Use Cases and Queries

A primary use case is generating reports or building interfaces to list all content items within a specific directory or folder hierarchy. Developers and administrators frequently query this table to audit content placement, resolve broken links, or enforce content governance policies. A common SQL pattern involves joining IBC_CONTENT_ITEM_NODES with IBC_CONTENT_ITEMS and IBC_DIRECTORY_NODES_B to produce a human-readable list. For example, to find all items in a specific directory, one might query: SELECT ci.item_name, ci.version_number FROM ibc_content_item_nodes cin JOIN ibc_content_items ci ON cin.content_item_id = ci.content_item_id WHERE cin.directory_node_id = <node_id>;. Another critical use case is during content migration or restructuring, where batch operations on this table are performed to relocate items within the directory tree.

Related Objects

  • IBC_CONTENT_ITEMS: This table stores the master definition and metadata for content items. The IBC_CONTENT_ITEM_NODES.CONTENT_ITEM_ID column is a foreign key to IBC_CONTENT_ITEMS, establishing the link to the actual content entity.
  • IBC_DIRECTORY_NODES_B: This table defines the structure and attributes of the directory nodes (folders) in the content hierarchy. The IBC_CONTENT_ITEM_NODES.DIRECTORY_NODE_ID column is a foreign key to this table, specifying the location of the content item.
  • IBC_CONTENT_ITEM_NODES_PK: The primary key constraint on the CONTENT_ITEM_NODE_ID column, ensuring each relationship record is uniquely identifiable.