Search Results csf_r_request_tasks




Overview
Explore in AI Chat

Overview

CSF_R_REQUEST_TASKS is a transactional table within the CSF (Field Service) product module of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. Its documented purpose is to store the tasks that require scheduling against a field service request. Each row represents a discrete schedulable task associated with a parent scheduling request, forming the operational link between a service request and the individual work items that must be dispatched, assigned, and resolved.

In Data Vault modeling terms, the metadata heuristically classifies this object as hub-leaning, reflecting that its primary key (REQUEST_TASK_ID) serves as a durable, unique business key around which dependent relationships are attached. This classification should be treated as a modeling suggestion rather than a formal designation; the table also exhibits link characteristics through its foreign key to CSF_R_SCHED_REQUESTS and its role as a referenced parent for message and resource-result tables.

Key Information Stored

The table contains six documented columns in the 12.2.2 physical schema. The most significant include:

  • REQUEST_TASK_ID — The surrogate primary key, enforced by CSF_R_REQUEST_TASKS_PK and also defined as the unique index CSF_R_REQUEST_TASKS_U1. It uniquely identifies each schedulable task and is the column referenced by all downstream child tables.
  • SCHED_REQUEST_ID — Foreign key to CSF_R_SCHED_REQUESTS, identifying the parent scheduling request to which this task belongs. This is the principal business-key candidate linking task detail to the request header.
  • TASK_ID — Identifies the specific task definition required against the request, driving the nature of the work to be performed.
  • RESULT_FLAG — Indicates the outcome or status disposition of the task, supporting post-execution reporting on completion.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant / operating-unit data segregation consistent with EBS security architecture.
  • OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrency control for the row, standard across modern EBS transactional tables.

The distinct split between the surrogate key (REQUEST_TASK_ID) and the business-relevant foreign key (SCHED_REQUEST_ID) is the central structural feature to understand when writing joins.

Common Use Cases and Queries

The most common usage is retrieving all schedulable tasks for a given service request, typically joined to the request header:

  • Listing tasks per scheduling request: SELECT t.request_task_id, t.task_id, t.result_flag FROM csf.csf_r_request_tasks t WHERE t.sched_request_id = :request_id.
  • Reporting on task outcomes using RESULT_FLAG grouped by TASK_ID to assess completion rates.
  • Reconciling scheduled versus unscheduled tasks by outer-joining to CSF_R_RESOURCE_RESULTS to identify tasks lacking resource assignments.
  • Security-filtered extracts honouring SECURITY_GROUP_ID for operating-unit-restricted reports.
  • Diagnostic queries tracing scheduler messages by joining CSF_R_MESSAGES on REQUEST_TASK_ID to isolate failed tasks.

Related Objects

  • CSF_R_SCHED_REQUESTS — Parent scheduling request; joined on CSF_R_REQUEST_TASKS.SCHED_REQUEST_ID = CSF_R_SCHED_REQUESTS.SCHED_REQUEST_ID.
  • FND_SECURITY_GROUPS — Security grouping reference via SECURITY_GROUP_ID.
  • CSF_R_MESSAGES — Child table referencing REQUEST_TASK_ID; carries scheduler messages tied to each task.
  • CSF_R_RESOURCE_RESULTS — Child table referencing REQUEST_TASK_ID; stores resource assignment results per task.
  • CSF_R_REQUEST_TASKS_PK / CSF_R_REQUEST_TASKS_U1 — Primary key constraint and unique index on REQUEST_TASK_ID.