Search Results csr_trip_tasks_v




Overview
Explore in AI Chat

Overview

CSR_TRIP_TASKS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered with the CSR (Scheduler) product family. As documented in ETRM, the view is defined as "selecting all tasks in all trips that scheduler can handle." It therefore serves as the primary denormalized access point for the Scheduler engine and for any reporting layer that must inspect the task-level detail of a dispatch trip without navigating the full JTF task assignment data model.

The view consolidates data from task headers, task assignments, task types, task statuses, resource locations, and requirement lines, and it applies Scheduler package functions to convert durations and resolve geographic locus attributes. Because it exposes only tasks whose type and status configuration permit scheduling, it functions as the authoritative "schedulable universe" for the Scheduler. In Oracle EBS 12.1.1 and 12.2.2 the view remains VALID, and the 12.2.2 edition ships with the standard OAF-style OBJECT_VERSION_NUMBER columns inherited from its base tables, confirming that it is maintained under the same editioning and versioning conventions as other CSR objects. Typical consumers include Field Service dispatch dashboards, custom trip plan reports, and integration extracts that feed external routing or mobile workforce applications.

Underlying Base Objects

The view is defined over a documented set of base objects. The task and assignment core is supplied by JTF_TASKS_B, JTF_TASK_ASSIGNMENTS, JTF_TASK_STATUSES_B, JTF_TASK_TYPES_B, and JTF_TASK_PRIORITIES_B. Trip and capacity context is drawn from CSP_REQUIREMENT_HEADERS and CSP_REQUIREMENT_LINES, with capacity screened through CAC_SR_OBJECT_CAPACITY and access windows through CSF_ACCESS_HOURS_B. Geographic data comes from HZ_LOCATIONS, and task dependencies from JTF_TASK_DEPENDS.

Business logic is not stored in the SQL alone; the view calls several PL/SQL packages. CSF_UTIL_PVT performs UOM conversion (CONVERT_TO_MINUTES) and returns the scheduler's canonical minute unit (GET_UOM_MINUTES). CSR_SCHEDULER_PVT.GET_TIMEZONE resolves the timezone from the task address. CSF_LOCUS_PUB extracts locus segment, side, spot, latitude, and the SHOULD_CALL_LF indicator from the geometry column of HZ_LOCATIONS. CSF_TASKS_PUB participates in the task-side declarations. These package dependencies mean the view is only valid when the CSF and CSR package bodies compile successfully, which is a common failure mode after patching.

Key Columns

The projection aliases the base columns with prefixes T (task) and TA (task assignment) to disambiguate the join. Notable columns include:

Common Use Cases and Queries

The most frequent use is retrieving all schedulable tasks for a trip or resource within a date range. A representative query joins the view to trip context:

SELECT task_id, ta_task_assignment_id, planned_start_date, scheduled_start_date, ta_sched_travel_duration, schedulable_flag FROM csr_trip_tasks_v WHERE trunc(planned_start_date) BETWEEN :p_start AND :p_end AND schedulable_flag = 'Y';

Dispatchers filter on TA_RESOURCE_ID to build a resource workload list, or on TASK_STATUS_ID to isolate unassigned work. Integration extracts select the locus columns to push coordinates to mobile devices, while analytics teams aggregate TA_SCHED_TRAVEL_DURATION and PLANNED_EFFORT to measure utilization. Administrators debugging scheduling behavior commonly query SCHEDULABLE_FLAG, TY_SCHEDULE_FLAG, and TA_SCHEDULABLE_FLAG together to determine why a task is excluded. Because the view is not a table, no DML should be issued against it; all maintenance is performed on JTF_TASKS_B and JTF_TASK_ASSIGNMENTS.