Search Results condition_segment_id

Overview

CSF_TDS_COND_SEGS is an intersection table within the CSF (Field Service) product schema of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. The table serves as the physical link between condition definitions and segment definitions used by the field service scheduling and territory assignment engine. Its stated purpose in the ETRM metadata is "intersection table for condition and segments," which reflects a classic many-to-many bridge design: a single condition may be associated with multiple segments, and a single segment may participate in multiple conditions. In Oracle Field Service, conditions and segments underpin the rules that qualify service resources and territories for assignment; the intersection table records which segment memberships satisfy which conditional criteria.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is link. This is appropriate: the table carries no descriptive attributes of its own beyond ordering and a junction node flag, and exists primarily to resolve the many-to-many relationship between two hub-like entities. The table is owned by the CSF schema and holds VALID status.

Key Information Stored

The table contains six documented columns, of which the primary key and foreign key columns are the most significant:

• CONDITION_SEGMENT_ID — Surrogate primary key, enforced by CSF_TDS_COND_SEGS_PK. Uniquely identifies each condition-to-segment association row.
• CONDITION_ID — Foreign key to CSF_TDS_CONDITIONS. Identifies the condition participating in the association.
• SEGMENT_ID — Foreign key to CSF_TDS_SEGMENTS. Identifies the segment participating in the association.
• SEQUENCE_NUMBER — Orders the segments or associations, giving deterministic evaluation order for the condition.
• JUNC_NODE_FLAG — A junction node indicator, likely distinguishing how the link behaves when the condition involves a tree or hierarchy of segments.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, providing Oracle Multi-Org / data security scoping.

Business-key candidates are the composite of CONDITION_ID and SEGMENT_ID, since the intersection should not duplicate the same pairing; however, only the surrogate key is documented as a unique constraint. The metadata does not list an explicit unique index on the composite pair.

Common Use Cases and Queries

Typical uses involve resolving which segments belong to a condition and which conditions reference a given segment — needed for territorial rule auditing and for diagnosing assignment failures.

Listing segments for a condition:

• SELECT s.SEGMENT_ID, c.SEQUENCE_NUMBER FROM CSF_TDS_COND_SEGS c, CSF_TDS_SEGMENTS s WHERE c.CONDITION_ID = :condition_id AND c.SEGMENT_ID = s.SEGMENT_ID ORDER BY c.SEQUENCE_NUMBER;

Finding conditions referencing a specific segment:

• SELECT c.CONDITION_ID FROM CSF_TDS_COND_SEGS c WHERE c.SEGMENT_ID = :segment_id;

Security-group-scoped reporting joins the table to FND_SECURITY_GROUPS via SECURITY_GROUP_ID. These patterns support rule reconciliation and impact analysis before modifying condition or segment definitions.

Related Objects

The most significant related objects, based on the documented foreign key relationships, are:

• CSF_TDS_CONDITIONS — parent of CONDITION_ID; defines the condition.
• CSF_TDS_SEGMENTS — parent of SEGMENT_ID; defines the segment.
• FND_SECURITY_GROUPS — parent of SECURITY_GROUP_ID; enforces data security.

These three tables account for every documented foreign key and form the complete dependency footprint of CSF_TDS_COND_SEGS in the ETRM metadata.