Results for “ibc_directory_node_rels_v”

16 results




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

Overview

The IBC_DIRECTORY_NODE_RELS_V view is a reporting and integration layer exposed in the APPS schema of Oracle E-Business Suite, belonging to the IBC Content Manager product module. Its purpose is to present the directory node relationships maintained by Content Manager in a stable, presentation-friendly form. Directory nodes in IBC represent the hierarchical containers—folders and similar structures—used to organize content items, and the relationships between those nodes define the parent-child topology of the content repository. The view exposes a single authenticated relationship per row, identified by its own primary key, together with the identifiers of the child and parent nodes that the relationship connects.

Because the object is defined as a view over a single base table with no joins, filtering, or derivation, it is best understood as an alias or wrapper rather than a transformation. Consequently, the view does not enforce additional row-level security or business logic beyond whatever is applied to the underlying table by the application. This makes it suitable for read-only reporting, data extraction, and integration scenarios where the caller requires a consistent, documented column interface.

Underlying Base Objects

The view is defined over a single documented base object, IBC_DIRECTORY_NODE_RELS, which is accessed through a synonym. This base table stores the persisted relationship records linking one directory node to another. The view text is a straightforward projection: every column in the view corresponds one-to-one with a column in the base table, and the view adds no predicates, joins, or aggregation. The ROW_ID column is populated from the base table's ROWID, providing a physical row locator in addition to the logical primary key. Because the view is read-only in any meaningful sense, DML against directory node relationships must be performed against the base table through supported application APIs. The view is marked VALID in the APPS schema and depends on the base table remaining accessible and correctly structured.

Key Columns

  • ROW_ID — The physical row identifier of the underlying IBC_DIRECTORY_NODE_RELS record.
  • DIRECTORY_NODE_REL_ID — The unique identifier of the relationship record itself; the logical primary key used to reference a specific parent-child link.
  • CHILD_DIR_NODE_ID — The identifier of the child directory node in the relationship. This is the column implicated by the search term child_dir_node_id and is the key value used to resolve which parent a given child node belongs to.
  • PARENT_DIR_NODE_ID — The identifier of the parent directory node, establishing the upper end of the hierarchy link.
  • CREATED_BY, CREATION_DATE — Standard EBS audit columns recording who created the relationship and when.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification and the login of the updating user.
  • OBJECT_VERSION_NUMBER — The optimistic locking version counter maintained by the EBS framework, useful for detecting concurrent modifications.

Common Use Cases and Queries

Typical usage involves traversing or reporting on the content directory hierarchy. A common requirement is to find the parent of a given child node:

  • SELECT parent_dir_node_id FROM ibc_directory_node_rels_v WHERE child_dir_node_id = :child_id;

Equally common is enumerating all children beneath a parent node, or joining the view to directory node definitions to obtain human-readable names and paths. Audit-oriented queries filter on creation_date or last_update_date to identify recently reorganized content. Integration routines often extract the full relationship set to replicate the repository hierarchy in an external system. In all cases the view should be treated as read-only, and any data modification should be routed through the supported Content Manager APIs against the base table.