Results for “child_dir_node_id”

40 results




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

Overview

IBC_DIRECTORY_NODE_RELS is a table in the IBC (Content Manager) product module of Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. It stores relationship information between parent and child directory nodes, effectively serving as the structural backbone of the Content Manager directory hierarchy. Each row represents one directed parent-to-child edge, allowing the directory tree to be assembled by walking these edges from a root node down to leaf nodes.

From a Data Vault modeling perspective, the heuristic classification for this object is link. This is a modeling suggestion: the table does not hold descriptive attributes about a business entity in the way a satellite would, but instead resolves a many-to-many style association between two instances of the same reference entity, IBC_DIRECTORY_NODES_B. In that sense it functions as a self-referencing link (or associative) table, with the parent and child endpoints each pointing back to the node master.

Key Information Stored

The table is documented with 11 columns. The most important are:

Two unique indexes act as business-key candidates: IBC_DIRECTORY_NODE_RELS_U1 on (DIRECTORY_NODE_REL_ID, ZD_EDITION_NAME), reinforcing the surrogate key in an edition-aware manner, and IBC_DIRECTORY_NODE_RELS_U2 on (CHILD_DIR_NODE_ID, ZD_EDITION_NAME), which indicates that a child node may have at most one parent relationship per edition—consistent with a strict tree structure rather than an arbitrary graph.

Common Use Cases and Queries

Typical usage involves reconstructing or validating the directory hierarchy for reporting, troubleshooting, or migration. A simple join retrieves the parent and child names for a given branch:

  • Hierarchy listing: join IBC_DIRECTORY_NODE_RELS to IBC_DIRECTORY_NODES_B twice—once on PARENT_DIR_NODE_ID and once on CHILD_DIR_NODE_ID—to display both sides of each edge.
  • Orphan detection: left-outer join from child nodes to IBC_DIRECTORY_NODE_RELS to identify nodes with no parent relationship (potential roots or data issues).
  • Security-scoped reporting: filter on SECURITY_GROUP_ID to restrict results to the appropriate security group.
  • Edition-aware queries in 12.2: filter on ZD_EDITION_NAME to ensure rows belong to the active edition, avoiding cross-edition double counting after patching.

Related Objects

The most significant related objects are:

  • IBC_DIRECTORY_NODES_B — the node master; referenced twice via PARENT_DIR_NODE_ID and CHILD_DIR_NODE_ID.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID, governing row-level visibility.
  • IBC_DIRECTORY_NODE_RELS_PK — the primary key constraint on DIRECTORY_NODE_REL_ID.
  • IBC_DIRECTORY_NODE_RELS_U1 / U2 — the unique indexes supporting edition-aware key integrity and single-parent enforcement.
  • Other IBC Content Manager node and content tables that traverse the directory tree to locate documents or files by folder path.