Search Results segment_node_id

Overview

CSF_TDS_SEGM_NODES is a table in the CSF schema (Field Service product module) that defines the relationship between segment definitions and node definitions within the Oracle EBS Territory and Assignment Management infrastructure. In Oracle EBS 12.1.1 and 12.2.2, the CSF module underpins Field Service and territory assignment functionality, where "nodes" represent the hierarchical structure (such as sales territories or service coverage trees) and "segments" represent the qualifying criteria applied to those structures. This table acts as the associative bridge binding node records to their constituent segmentation logic.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object is best classified as a link table. It sits between two hub-like entities — CSF_TDS_NODES and CSF_TDS_SEGMENTS — and carries a five-column footprint consistent with a pure relationship resolver (a junction/intersection entity). It is not a descriptive satellite in its own right; its primary value is the association itself, along with a small amount of relationship-type metadata captured in the SEGM_NODE_TYPE column.

Key Information Stored

The documented physical schema contains five columns (ETRM 12.2.2). The most significant are:

• SEGMENT_NODE_ID — The surrogate primary key, enforced by CSF_TDS_SEGM_NODES_PK. This uniquely identifies each relationship row and is the column to rely on for deterministic referencing.
• NODE_ID — A foreign key into CSF_TDS_NODES. It identifies the parent node (territory or coverage structure element) to which the segment is bound.
• SEGMENT_ID — A foreign key into CSF_TDS_SEGMENTS. It identifies the segment (criterion set) applied to the associated node.
• SEGM_NODE_TYPE — Describes the nature of the segment-to-node association, allowing the same qualifying logic to be interpreted differently depending on how it is attached. This is a business-relevant classifier for the relationship.
• SECURITY_GROUP_ID — Supports multi-org/multi-tenant data isolation via FND_SECURITY_GROUPS, restricting visibility of the relationship to the appropriate security partition.

No unique business-key index beyond the surrogate primary key is documented, meaning SEGMENT_NODE_ID is the only guaranteed unique identifier. Business-key candidates would nominally be the (NODE_ID, SEGMENT_ID, SEGM_NODE_TYPE) combination, but this is not documented as an enforced constraint.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include reconstructing the full territory/segment hierarchy, verifying which segments qualify a given node, and auditing security-group assignments.

• Resolve all segments for a node:

  SELECT n.NODE_ID, s.SEGMENT_ID, sn.SEGM_NODE_TYPE
  FROM CSF_TDS_SEGM_NODES sn
  JOIN CSF_TDS_NODES n ON sn.NODE_ID = n.NODE_ID
  JOIN CSF_TDS_SEGMENTS s ON sn.SEGMENT_ID = s.SEGMENT_ID;

• Inventory relationships by type: Group by SEGM_NODE_TYPE to quantify how segments are distributed across nodes.
• Security-group audit: Filter on SECURITY_GROUP_ID to identify relationships visible only to a particular operating unit or partition.
• Orphan detection: Left-join to both parent tables to find dangling NODE_ID or SEGMENT_ID references.

Related Objects

• CSF_TDS_NODES — Parent entity; joined on CSF_TDS_SEGM_NODES.NODE_ID = CSF_TDS_NODES.NODE_ID.
• CSF_TDS_SEGMENTS — Parent entity; joined on CSF_TDS_SEGM_NODES.SEGMENT_ID = CSF_TDS_SEGMENTS.SEGMENT_ID.
• FND_SECURITY_GROUPS — Security partition referenced by SECURITY_GROUP_ID.
• CSF_TDS_SEGM_NODES_PK — The primary-key constraint governing uniqueness.
• CSF_TDS_* node and segment configuration tables/APIs — The broader territory and assignment setup that consumes these relationships.