Results for “hidden_flag”

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

Overview

IBC_DIRECTORY_NODES_B is the base (non-translatable) table in the IBC — Content Manager product module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It defines all directory nodes used by the Content Manager repository, providing the structural backbone for hierarchical content organization. Each row represents a single directory node, whether a folder-like container or a leaf-level content reference, and carries the attributes that govern navigability, availability, security scoping, and editioning visibility.

Because every dependent relationship — content items, content item-to-node associations, translations, and the parent/child node hierarchy — resolves back to DIRECTORY_NODE_ID, the table functions as the central point of reference for the module. From a Data Vault modeling perspective, the mined foreign-key structure classifies IBC_DIRECTORY_NODES_B heuristically as a hub: it holds a stable surrogate key (DIRECTORY_NODE_ID) with descriptive and state attributes attached, and it is referenced by multiple dependent tables rather than acting as a link or a pure transactional satellite. This classification is a modeling suggestion only, derived from the observed FK topology, not a statement of Oracle's internal design intent.

Key Information Stored

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

• DIRECTORY_NODE_ID — surrogate primary key, enforced by IBC_DIRECTORY_NODES_B_PK. This is the value propagated to every dependent table.
• DIRECTORY_NODE_CODE — the human-readable node identifier used in lookups and administrative maintenance.
• NODE_TYPE — discriminates the kind of node (for example, container versus content-bearing node); participates in the business uniqueness rule.
• DIRECTORY_PATH — the resolved path of the node within the directory tree; paired with NODE_TYPE in the second unique index, which makes the path/type combination a strong business-key candidate.
• NODE_STATUS — lifecycle state controlling whether the node is active and usable.
• AVAILABLE_DATE and EXPIRATION_DATE — the effective date window governing when the node may be surfaced to end users.
• HIDDEN_FLAG — controls whether the node is suppressed from standard navigation and listings.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, scoping the node to a security group and therefore to a defined set of operating units or responsibilities.
• ZD_EDITION_NAME — the editioning column introduced under EBS 12.2 online patching; it appears in both unique indexes and enables edition-specific visibility of nodes during cutover.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the underlying framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns capturing insert and update provenance.

Two unique indexes are documented: IBC_DIRECTORY_NODES_B_U1 on (DIRECTORY_NODE_ID, ZD_EDITION_NAME) and IBC_DIRECTORY_NODES_B_U2 on (DIRECTORY_PATH, NODE_TYPE, ZD_EDITION_NAME). The first reinforces the surrogate key under editioning; the second identifies path and node type as the business-key candidate for the table.

Common Use Cases and Queries

Typical usage centers on resolving node identity, walking the hierarchy, and reporting on content organization. A common pattern joins the translatable table to obtain display names:

• Node lookup by path or code — SELECT directory_node_id, node_type, node_status FROM ibc_directory_nodes_b WHERE directory_path = :path;
• Active node reporting — filtering on NODE_STATUS, HIDDEN_FLAG, and the AVAILABLE_DATE/EXPIRATION_DATE window to list nodes currently visible to users.
• Hierarchy traversal — joining IBC_DIRECTORY_NODE_RELS on PARENT_DIR_NODE_ID and CHILD_DIR_NODE_ID to reconstruct parent/child relationships and compute depth or full paths.
• Content inventory — joining IBC_CONTENT_ITEMS on DIRECTORY_NODE_ID to count or list content items filed under each node.
• Security scoping audits — grouping by SECURITY_GROUP_ID to verify which security group owns each node.
• Edition-aware queries — on 12.2.x, constraining ZD_EDITION_NAME to the active edition to avoid duplicate rows during online patching cycles.

Related Objects

The documented foreign-key topology identifies the following principal dependents and references:

• IBC_DIRECTORY_NODES_TL — translatable node attributes; joins on DIRECTORY_NODE_ID.
• IBC_DIRECTORY_NODE_RELS — the parent/child relationship table; joins twice on this table, once via PARENT_DIR_NODE_ID and once via CHILD_DIR_NODE_ID.
• IBC_CONTENT_ITEMS — content items filed under a node; joins on DIRECTORY_NODE_ID.
• IBC_CONTENT_ITEM_NODES — association of content items to directory nodes; joins on DIRECTORY_NODE_ID.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, providing the security scoping for each node.

Together these objects form the Content Manager directory model, with IBC_DIRECTORY_NODES_B as the hub through which all node-based navigation, content filing, translation, and hierarchy processing is resolved.