Results for “ibc_content_item_nodes”

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

Overview

IBC_CONTENT_ITEM_NODES is a table in the IBC schema belonging to the Oracle E-Business Suite Content Manager module. It records the placement of a content item within the directory hierarchy, capturing the relationship between a content item and the directory node under which it resides. In practical terms, this table answers the question of "where in the folder tree does this content item live," enabling hierarchical navigation, browsing, and access control on content stored within Content Manager.

The table is a classic associative structure and, from a Data Vault modeling perspective, would be classified heuristically as a link. It does not store descriptive attributes about either the content item or the directory node itself; instead it resolves a many-to-many relationship between two entities. This classification is derived from its foreign-key structure, which references both the content item and the directory node as separate hubs. The link carries its own surrogate identifier along with audit and security metadata.

Key Information Stored

The table contains ten documented columns. The most significant are:

• CONTENT_ITEM_NODE_ID — the surrogate primary key for the row, populated by the sequence associated with IBC_CONTENT_ITEM_NODES_PK.
• CONTENT_ITEM_ID — foreign key identifying the content item being placed; references IBC_CONTENT_ITEMS.
• DIRECTORY_NODE_ID — foreign key identifying the directory node in which the content item resides; references IBC_DIRECTORY_NODES_B.
• SECURITY_GROUP_ID — the security group under which the placement is registered, referencing FND_SECURITY_GROUPS. This governs which operating unit or business group can see the row.
• OBJECT_VERSION_NUMBER — the optimistic-locking counter used by the OA Framework and PL/SQL APIs to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS "Who" audit columns that record row provenance and last modification.

The table carries two unique indexes. The first, IBC_CONTENT_ITEM_NODES_U1, is on the surrogate key CONTENT_ITEM_NODE_ID. The second, IBC_CONTENT_ITEM_NODES_U2, is the composite business key on (DIRECTORY_NODE_ID, CONTENT_ITEM_ID), which enforces the rule that a given content item may appear only once within a specific directory node. This composite uniqueness constraint is the true business identity of the placement.

Common Use Cases and Queries

Typical use cases center on content navigation and reporting. Analysts frequently need to list all content items appearing beneath a particular directory, or to find every directory in which a content item is placed. A representative query joining to the base content item table might be:

• SELECT c.content_item_id, c.name FROM ibc_content_item_nodes n, ibc_content_items c WHERE n.content_item_id = c.content_item_id AND n.directory_node_id = :node_id AND n.security_group_id = :sg_id;
• Counting items per node for capacity or migration planning: SELECT directory_node_id, COUNT(*) FROM ibc_content_item_nodes GROUP BY directory_node_id;
• Detecting duplicates or validating the business key before insert: query on (directory_node_id, content_item_id) to confirm no existing placement.
• Data-migration or archival routines that need to relocate items between nodes commonly update the DIRECTORY_NODE_ID and bump OBJECT_VERSION_NUMBER.

All queries should be filtered on SECURITY_GROUP_ID to respect multi-tenant data separation in a shared EBS instance.

Related Objects

The most consequential related objects derive from the foreign-key structure:

• IBC_CONTENT_ITEMS — joined on CONTENT_ITEM_ID; the parent entity describing each content item.
• IBC_DIRECTORY_NODES_B — joined on DIRECTORY_NODE_ID; the base table for the directory hierarchy.
• IBC_DIRECTORY_NODES_TL — the translation table providing node display names.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID to resolve the owning security group.
• Content Manager concurrent programs and the OA Framework content-browsing pages that read and write placements through the underlying PL/SQL APIs.

Together these objects form the directory-placement subsystem of Content Manager, with IBC_CONTENT_ITEM_NODES acting as the linking spine between items and the folder hierarchy.