Search Results fnd_dm_nodes




Overview
Explore in AI Chat

Overview

FND_DM_NODES is a table owned by the APPLSYS schema within the Oracle E-Business Suite Application Object Library (FND) product family. Its documented description identifies it as the storage for "Document manager system nodes." In practice, the table holds the individual node definitions that make up the document manager hierarchy used by the Oracle EBS Document Manager infrastructure. Each row represents a discrete node — typically a connection point, target system, or content source — that the document manager references when integrating external repositories or content sources with the EBS application tier.

The object is classified by the ETRM metadata under a heuristic Data Vault assessment as satellite-leaning. This classification should be read as a modeling suggestion rather than a definitive statement. The satellite-leaning characteristic reflects the table's role as a descriptive, attribute-bearing entity that hangs off a parent reference (a product identifier), in contrast to a pure hub or link structure.

Key Information Stored

The documented physical schema in ETRM 12.2.2 lists nine columns. The most significant are summarised below.

  • NODE_ID — The surrogate primary key, enforced by the primary key constraint FND_DM_NODES_PK and also the basis of the unique index FND_DM_NODES_U1. It uniquely identifies each node row.
  • NODE_NAME — The business-facing node name. It is a business-key candidate, enforced by the unique index FND_DM_NODES_U2, meaning no two nodes may share the same name.
  • PRODUCT_ID — A foreign key referencing FND_DM_PRODUCTS. This column associates each node with a registered document manager product, forming the principal relationship of the table.
  • CONNECT_SYNTAX — Holds the connection syntax string used to build or interpret the node's connection reference.
  • CONNECT_URL — Stores the connection URL or endpoint address that the document manager uses to reach the node.
  • NODE_DESCRIPTION — A free-text descriptive label for the node.
  • SHORT_NAME — An abbreviated identifier, useful for display or reporting where the full node name is too long.
  • SEQUENCE — A numeric ordering value that governs the position or priority of the node within its product grouping.
  • CERTIFICATE_PATH — The filesystem or repository path to the certificate used for secure node communication.

The distinction between the surrogate key (NODE_ID) and the two business-key candidates (NODE_ID via U1 and NODE_NAME via U2) is important: existing integrations frequently resolve nodes by name rather than by ID, so NODE_NAME carries real business meaning in addition to its uniqueness constraint.

Common Use Cases and Queries

Typical usage centres on inspecting or auditing the document manager node configuration. A common query joins nodes to their parent product to produce a readable inventory:

  • Inventory nodes by product: SELECT n.NODE_ID, n.NODE_NAME, n.SHORT_NAME, p.PRODUCT_NAME FROM FND_DM_NODES n, FND_DM_PRODUCTS p WHERE n.PRODUCT_ID = p.PRODUCT_ID ORDER BY n.SEQUENCE;
  • Resolve a node by its business key: SELECT NODE_ID, CONNECT_URL, CERTIFICATE_PATH FROM FND_DM_NODES WHERE NODE_NAME = :name;
  • Ordering and sequencing checks: SELECT PRODUCT_ID, SEQUENCE, NODE_NAME FROM FND_DM_NODES ORDER BY PRODUCT_ID, SEQUENCE;

Reporting use cases include configuration audits prior to upgrades, verification that certificate paths remain valid after infrastructure changes, and reconciliation of connection URLs against known endpoints.

Related Objects

The most significant related object is FND_DM_PRODUCTS, referenced through the foreign key FND_DM_NODES.PRODUCT_ID → FND_DM_PRODUCTS.PRODUCT_ID. This relationship is the primary dependency: every node is registered against exactly one document manager product. The unique indexes FND_DM_NODES_U1 (NODE_ID) and FND_DM_NODES_U2 (NODE_NAME), together with the primary key FND_DM_NODES_PK, are the key supporting database objects. Broader integration typically occurs through the Document Manager application programming interfaces and concurrent programs within the FND module, which read node definitions at runtime rather than through additional hard foreign keys documented in the ETRM source.