Search Results csf_tds_rdblck_intvls




Overview
Explore in AI Chat

Overview

CSF_TDS_RDBLCK_INTVLS is a Field Service (CSF) module table within the Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. Its documented purpose is to serve as an "intersection table for Roadblocks and intervals." In practical terms, it resolves a many-to-many relationship between roadblock definitions and scheduling intervals, allowing a single interval of availability to be associated with one or more roadblocks, and vice versa. This intersection supports the Field Service dispatch and scheduling engine, which must determine when resources are blocked from receiving assignments.

From a data modeling perspective, the ETRM metadata assigns this object a heuristic Data Vault classification of link. This classification is drawn from its foreign key structure: the table sits between two parent entities and holds only the intersecting keys. Modelers should treat this as a suggestion rather than a prescriptive design; the table functions as a pure junction or association entity, with no descriptive attributes beyond the intersection itself and the standard security grouping column.

Key Information Stored

The table is documented with four physical columns, each of which is significant:

  • ROADBLOCK_INTERVAL_ID — The surrogate primary key, defined by the constraint CSF_TDS_RDBLCK_INTVLS_PK. This column uniquely identifies each roadblock-to-interval association and is system-generated, with no business meaning.
  • ROADBLOCK_ID — A foreign key referencing CSF_TDS_ROADBLOCKS. It identifies the specific roadblock being associated with an availability interval.
  • INTERVAL_ID — A foreign key referencing CSF_TDS_INTERVALS. It identifies the interval definition to which the roadblock applies.
  • SECURITY_GROUP_ID — A foreign key referencing FND_SECURITY_GROUPS, providing multitenancy and data-access isolation consistent with the EBS security model. Queries against this table in a secured environment typically include the appropriate security group predicate to avoid cross-group data leakage.

No separate unique business-key index is documented in the ETRM metadata; the only documented unique constraint is the primary key on ROADBLOCK_INTERVAL_ID. The logical uniqueness of a roadblock/interval pairing is therefore implied by the application rather than enforced by a documented alternate key.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios involve determining which roadblocks are preventing a resource from being scheduled during a given interval, or enumerating all intervals covered by a particular roadblock. A representative join pattern follows:

  • Resolve roadblocks for a given interval: SELECT rb.ROADBLOCK_ID, rb.NAME FROM CSF_TDS_ROADBLOCKS rb, CSF_TDS_RDBLCK_INTVLS x WHERE rb.ROADBLOCK_ID = x.ROADBLOCK_ID AND x.INTERVAL_ID = :interval_id;
  • Enumerate intervals for a roadblock: SELECT i.INTERVAL_ID, i.START_TIME, i.END_TIME FROM CSF_TDS_INTERVALS i, CSF_TDS_RDBLCK_INTVLS x WHERE i.INTERVAL_ID = x.INTERVAL_ID AND x.ROADBLOCK_ID = :roadblock_id;
  • Audit orphaned associations by outer-joining both parents to identify integrity gaps.

Scheduling engine troubleshooting frequently relies on this table, since an unexpected row here will suppress assignment generation for the affected interval/roadblock combination.

Related Objects

The following objects are most significant to this table based on documented relationships:

  • CSF_TDS_ROADBLOCKS — Parent of ROADBLOCK_ID; holds the roadblock definitions to which intervals are bound.
  • CSF_TDS_INTERVALS — Parent of INTERVAL_ID; defines the scheduling intervals referenced by the association.
  • FND_SECURITY_GROUPS — Parent of SECURITY_GROUP_ID; governs access partitioning of the intersection rows.
  • CSF_TDS_RDBLCK_INTVLS_PK — The primary key constraint object itself, relevant in DBA integrity analysis.

Because the table carries no independent attributes, updates and maintenance flow through the Field Service dispatch and roadblock configuration functionality rather than through direct DML.