Search Results ta_object_version_number




Overview
Explore in AI Chat

Overview

CSR_PLAN_TASKS_V is an APPS-owned database view in the Oracle E-Business Suite, belonging to the CSR (Scheduler) product. It consolidates the set of tasks that are candidates for scheduling within the Field Service scheduler engine. Rather than exposing raw transactional rows, the view presents a scheduling-ready projection: it joins task definitions, task assignments, locus/geometry information, and requirement data, and it normalizes duration figures into a single unit of measure so the scheduling algorithm can reason about them consistently.

The view's principal role is to feed the CSR Scheduler with tasks that may be scheduled, together with the flags and attributes that govern whether and how each task can be placed on a schedule. Because it is a view rather than a table, it carries no storage of its own and always reflects the current state of the referenced base objects. In both 12.1.1 and 12.2.2 it is reported as VALID in the APPS schema.

Underlying Base Objects

The view is defined over a combination of synonyms and PL/pgSQL-style packaged functions. The documented referenced objects are: CSF_ACCESS_HOURS_B, CSF_LOCUS_PUB, CSF_TASKS_PUB, CSF_UTIL_PVT, CSP_REQUIREMENT_HEADERS, CSP_REQUIREMENT_LINES, CSR_SCHEDULER_PVT, HZ_LOCATIONS, JTF_TASKS_B, JTF_TASK_ASSIGNMENTS, JTF_TASK_DEPENDS, JTF_TASK_PRIORITIES_B, JTF_TASK_STATUSES_B, and JTF_TASK_TYPES_B.

Structurally, the JTF_TASK_* objects supply the task backbone (TASK_ID, TASK_TYPE_ID, TASK_STATUS_ID, task flags, and object version numbers), while JTF_TASK_ASSIGNMENTS supplies the resource-side assignment rows. HZ_LOCATIONS and the CSF_LOCUS_PUB package resolve geographic locus attributes. CSF_UTIL_PVT provides unit conversion, CSR_SCHEDULER_PVT derives timezone, and CSP_REQUIREMENT_HEADERS/CSP_REQUIREMENT_LINES supply an arrival-date subquery. CSF_TASKS_PUB and CSF_ACCESS_HOURS_B support task and availability logic. These dependencies mean the view inherits data security and referential behavior from the JTF task model.

Key Columns

The task identity columns are TASK_ID, TASK_TYPE_ID, and TASK_STATUS_ID. Scheduling windows are exposed as PLANNED_START_DATE, PLANNED_END_DATE, SCHEDULED_START_DATE, SCHEDULED_END_DATE, ACTUAL_START_DATE, and ACTUAL_END_DATE. Effort is presented as PLANNED_EFFORT, which is derived by calling CSF_UTIL_PVT.CONVERT_TO_MINUTES(T.PLANNED_EFFORT, T.PLANNED_EFFORT_UOM), with PLANNED_EFFORT_UOM set to CSF_UTIL_PVT.GET_UOM_MINUTES — that is, the value of the UOM constant representing minutes. This is why a search for "planned_effort_uom" surfaces this view: the underlying task column is converted and the view reports the resulting effort in minutes.

Bound and schedulability metadata include BOUND_MODE_CODE (defaulted to 'BTS' via NVL), SOFT_BOUND_FLAG, SCHEDULABLE_FLAG, TA_SCHEDULABLE_FLAG, and TY_SCHEDULE_FLAG. Assignment attributes include TA_TASK_ASSIGNMENT_ID, TA_RESOURCE_ID, TA_RESOURCE_TYPE_CODE, TA_ASSIGNMENT_STATUS_ID, TA_SCHED_TRAVEL_DISTANCE, and SCHED_TRAVEL_DURATION (also converted to minutes). Locus columns LOCUS_SEGMENTID, LOCUS_SIDE, LOCUS_SPOT, LOCUS_LAT, LOCUS_LON, SHOULD_CALL_LF, LOCATION_ID, and TIMEZONE_ID describe the service location.

Common Use Cases and Queries

Typical uses include building scheduler extracts, validating which tasks are eligible for scheduling, and reconciling planned versus actual effort in minutes. A common retrieval is:

  • SELECT task_id, task_type_id, task_status_id, planned_effort, planned_effort_uom FROM csr_plan_tasks_v WHERE schedulable_flag = 'Y';
  • SELECT task_id, planned_start_date, planned_end_date, scheduled_start_date, scheduled_end_date FROM csr_plan_tasks_v WHERE task_status_id = :status_id;
  • SELECT task_id, locus_lat, locus_lon, timezone_id FROM csr_plan_tasks_v WHERE location_id = :location_id;

Because PLANNED_EFFORT is already expressed in minutes, downstream scheduling queries should not re-apply unit conversion. Filters on TA_SCHEDULABLE_FLAG and TY_SCHEDULE_FLAG are frequently combined to isolate genuinely schedulable tasks.