Search Results ibc_directory_node_rels




Overview
Explore in AI Chat

Overview

The IBC_DIRECTORY_NODE_RELS table is a core data object within the Oracle E-Business Suite Content Manager module (IBC). It functions as the structural backbone for organizing content by storing the hierarchical relationships between directory nodes. In Oracle EBS, directories are used to categorize and manage content items, folders, and categories in a tree-like structure. This table explicitly defines the parent-child linkages that form these hierarchies, enabling the navigation, security inheritance, and logical grouping of content assets. Its integrity is critical for the proper operation of the Content Manager's repository and any processes that depend on content organization.

Key Information Stored

The table's primary purpose is to map a child directory node to its parent. The key columns that facilitate this are DIRECTORY_NODE_REL_ID, which serves as the unique primary key for each relationship record, PARENT_DIR_NODE_ID, which stores the identifier of the parent directory node, and CHILD_DIR_NODE_ID, which stores the identifier of the child directory node. These columns are foreign keys referencing the IBC_DIRECTORY_NODES_B table, ensuring that only valid directory nodes can participate in a relationship. The table's design allows for the creation of complex, multi-level directory trees essential for sophisticated content management.

Common Use Cases and Queries

A primary use case is querying the complete subtree or lineage of a specific directory node for reporting, content discovery, or applying security rules. For instance, to find all child nodes beneath a specific parent directory, a hierarchical SQL query using CONNECT BY or a recursive WITH clause would join this table to IBC_DIRECTORY_NODES_B. Administrators may also query this table to audit the directory structure or to identify orphaned relationships during data cleanup. A common pattern is to validate the path of a content item by traversing up the hierarchy from its assigned directory node to the root.

  • Sample Query (Find Immediate Children): SELECT child_dir_node_id FROM ibc_directory_node_rels WHERE parent_dir_node_id = :p_node_id;
  • Sample Query (Find All Descendants): SELECT child_dir_node_id FROM ibc_directory_node_rels CONNECT BY PRIOR child_dir_node_id = parent_dir_node_id START WITH parent_dir_node_id = :p_top_node_id;

Related Objects

The IBC_DIRECTORY_NODE_RELS table has direct, documented dependencies on the central directory node definition table. Its relationships are strictly defined through foreign key constraints, as per the provided metadata.

  • IBC_DIRECTORY_NODES_B: This is the master table for all directory nodes. IBC_DIRECTORY_NODE_RELS references it twice:
    • Via CHILD_DIR_NODE_ID foreign key column.
    • Via PARENT_DIR_NODE_ID foreign key column.
    Any join to retrieve directory node names or attributes must use this table.
  • Primary Key: The table's integrity is enforced by the IBC_DIRECTORY_NODE_RELS_PK constraint on the DIRECTORY_NODE_REL_ID column.