Search Results csf_r_plan_option_tasks




Overview
Explore in AI Chat

Overview

CSF_R_PLAN_OPTION_TASKS is a transactional detail table within the Oracle E-Business Suite Field Service (CSF) module. Its documented purpose is to store the trips—represented internally as tasks—for which a given plan option applies. In the EBS scheduling and dispatch model, a plan option defines a reusable configuration of scheduling parameters, and this child table resolves the many-to-many relationship between those plan options and the individual tasks or trips that fall under their control. The table is registered in the CSF schema with a VALID status and is present in both EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the ETRM heuristic classifies this object as satellite-leaning. This suggests that the table functions primarily as a dependent, descriptive collection of records attached to a parent business entity (the plan option) rather than as a standalone hub or an associative link. Practitioners designing warehouse extractions should treat PLAN_OPTION_ID as the natural parent reference and the row itself as satellite detail, while remaining aware that the presence of TASK_ID and TASK_ASSIGNMENT_ID also gives the structure link-like characteristics between scheduling entities.

Key Information Stored

The documented physical schema contains ten columns. The most operationally significant are summarized below.

  • PLAN_OPTION_TASK_ID — The surrogate primary key, enforced by CSF_R_PLAN_OPTION_TASKS_PK and by the unique index CSF_R_PLAN_OPTION_TASKS_U1. This is the technical identifier for each row.
  • PLAN_OPTION_ID — Foreign key to CSF_R_PLAN_OPTIONS. This is the principal business-key candidate, linking each task record to the parent plan option that governs it.
  • TASK_ID — Identifies the task (trip) to which the plan option is applied. This column carries the core business meaning of the table.
  • TASK_ASSIGNMENT_ID — Associates the task with its assignment record, connecting the row to the resource or crew performance of the trip.
  • SCHEDULED_START_DATE and SCHEDULED_END_DATE — The planned time window for the task under the plan option. These drive duration and window-based reporting.
  • TRAVEL_TIME — The travel component associated with the task, used in route and cost analysis.
  • OBJECT_CAPACITY_ID — Foreign key to CAC_SR_OBJECT_CAPACITY, tying the task to the service object and capacity context.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, providing Multi-Org Access Control (MOAC) enforcement at the row level.
  • OBJECT_VERSION_NUMBER — The standard EBS optimistic-locking column, used by the ORM framework to detect concurrent updates.

Common Use Cases and Queries

Typical reporting scenarios include identifying all tasks governed by a plan option, analyzing scheduled windows and travel time by plan option, and reconciling task assignments against the scheduling configuration.

A representative query joining the child table to its parent plan option:

  • SELECT pot.PLAN_OPTION_TASK_ID, pot.TASK_ID, pot.SCHEDULED_START_DATE, pot.SCHEDULED_END_DATE, pot.TRAVEL_TIME, po.PLAN_OPTION_ID FROM CSF.CSF_R_PLAN_OPTION_TASKS pot, CSF.CSF_R_PLAN_OPTIONS po WHERE pot.PLAN_OPTION_ID = po.PLAN_OPTION_ID AND pot.PLAN_OPTION_ID = :p_plan_option_id;

Because SECURITY_GROUP_ID participates in MOAC, reports run in a multi-org context should allow the EBS security layer to append the appropriate security-group predicate rather than hard-coding it. Joins to CAC_SR_OBJECT_CAPACITY support capacity and workload analysis, while joins to FND_SECURITY_GROUPS are typically reserved for administrative or diagnostic queries.

Related Objects

  • CSF_R_PLAN_OPTIONS — Referenced through CSF_R_PLAN_OPTION_TASKS.PLAN_OPTION_ID; the parent plan option definition.
  • FND_SECURITY_GROUPS — Referenced through CSF_R_PLAN_OPTION_TASKS.SECURITY_GROUP_ID; enforces MOAC.
  • CAC_SR_OBJECT_CAPACITY — Referenced through CSF_R_PLAN_OPTION_TASKS.OBJECT_CAPACITY_ID; supplies service-object capacity context.
  • Task and assignment entities — TASK_ID and TASK_ASSIGNMENT_ID connect rows to the broader CSF task and dispatch assignment model, which should be confirmed against the specific EBS patch level in use.