Search Results fnd_dm_nodes_u2

Overview

APPLSYS.FND_DM_NODES is a seed data table within the Oracle E-Business Suite Document Management (DM) framework. It stores the physical node location of each Document Management system product deployed across an EBS environment. Every row describes one DM node, capturing its logical name, descriptive text, the software product installed at that node, and the physical connection syntax used to reach it. The table is owned by APPLSYS and carries FND design data reference FND.FND_DM_NODES, with a status of VALID. It resides in the APPS_TS_SEED tablespace, reflecting its role as reference or setup data rather than transactional data.

From a Data Vault modeling perspective, the mined classification for this table is satellite-leaning. This is a modeling suggestion only: the table functions as a set of descriptive attributes anchored to a stable node identity, rather than as a pure hub of business keys or a link resolving many-to-many relationships. Its single foreign key to FND_DM_PRODUCTS reinforces its role as a dependent descriptive structure.

Key Information Stored

The table is documented with nine columns. The most significant are summarized below.

• NODE_ID — The surrogate primary key, enforced by the FND_DM_NODES_PK constraint and the unique index FND_DM_NODES_U1. It is the internal node identifier.
• NODE_NAME — The logical name for the document manager system node. This is a business-key candidate, enforced by the unique index FND_DM_NODES_U2.
• PRODUCT_ID — The identifier of the Document Manager software vendor and product version installed on the node. It is a foreign key to FND_DM_PRODUCTS.PRODUCT_ID.
• CONNECT_SYNTAX — The physical connection string in the form 'protocol://server:port/'.
• CONNECT_URL — The URL used to reach the node.
• NODE_DESCRIPTION — Descriptive text for the node.
• SHORT_NAME — A short label for the node.
• SEQUENCE — Ordering value used when presenting nodes to users.
• CERTIFICATE_PATH — Path to the security certificate associated with the node connection.

The distinction between the surrogate key (NODE_ID) and the business-key candidate (NODE_NAME) matters when integrating with external systems or when resolving duplicate logical node definitions.

Common Use Cases and Queries

Oracle Applications Object Library uses this table to prompt users for the DM system to use when documents are attached or retrieved in a multi-node community. The available nodes are presented as URL links, composed from the stored connection syntax appended with the function name and parameter syntax required to execute the selected DM function.

Typical queries include listing active nodes with their products, and resolving a node name to its connection target:

• SELECT n.NODE_NAME, p.PRODUCT_NAME, n.CONNECT_SYNTAX FROM FND_DM_NODES n, FND_DM_PRODUCTS p WHERE n.PRODUCT_ID = p.PRODUCT_ID ORDER BY n.SEQUENCE;
• SELECT NODE_ID, CONNECT_URL, CERTIFICATE_PATH FROM FND_DM_NODES WHERE NODE_NAME = :node_name;

Reporting use cases include inventorying DM nodes per product version, auditing connection endpoints and certificate paths, and validating that unique node naming is preserved across environments.

Related Objects

• FND_DM_PRODUCTS — Joined on FND_DM_NODES.PRODUCT_ID = FND_DM_PRODUCTS.PRODUCT_ID; the parent of the sole documented foreign key.
• FND_DM_NODES_PK — Primary key constraint on NODE_ID.
• FND_DM_NODES_U1 — Unique index on NODE_ID.
• FND_DM_NODES_U2 — Unique index on NODE_NAME, the business-key candidate referenced in the search term "fnd_dm_nodes_u2".
• Oracle Applications Object Library — Consumes node and connection data to build DM function URLs.