Search Results device3_flag

Overview

CSF_AGENDA_V is a reporting view within the CSF (Field Service) product family of Oracle E-Business Suite, available across the 12.1.1 and 12.2.2 release lines. Its documented purpose is to extract predicted start and end times for tasks, making it the primary agenda-oriented read interface for field service scheduling, dispatch, and mobile workforce consumption. The view consolidates assignment-level scheduling attributes — planned, scheduled, and actual dates, alarm and notification configuration, travel estimates, effort, and status — into a single flattened projection suitable for concurrent programs, Oracle Reports, OA Framework pages, and outbound integrations to handheld or wireless devices.

The presence of device indicator columns (PALM_FLAG, WINCE_FLAG, LAPTOP_FLAG, DEVICE1_FLAG through DEVICE3_FLAG) reflects the view's historical role in supporting the Field Service mobile/portable client population, where agenda data is synchronised to technicians for offline task execution. Because the view is read-oriented and derived, it carries no transactional write semantics and should be used strictly for selection.

Underlying Base Objects

The ETRM metadata records the view as "Not implemented in this database" for the surveyed environment and documents no base objects, so the definitive dependency list cannot be confirmed from the catalogue excerpt alone. The view text, however, clearly selects from a driving alias V that exposes assignment and task columns (TASK_ASSIGNMENT_ID, TASK_ID, RESOURCE_ID, ASSIGNMENT_STATUS_ID, TASK_NUMBER, and so on), which corresponds to the task assignment entity in the CSF/JTF scheduling schema — typically CSF_TASK_ASSIGNMENTS alongside the task and resource definitions.

The view text also references a server-side function, CSF_AGENDA_CALCULATIONS.SET_ESCALATION_FLAG(V.TASK_ID), used to derive the ESCALATION_FLAG column. That package dependency means querying the view invokes PL/SQL logic per row, which has performance implications for large extracts and must be accounted for in tuning and indexing decisions. Because no base objects are formally documented, implementers should confirm the actual dependency chain against the target instance's ALL_DEPENDENCIES and ALL_VIEWS before relying on column lineage for customisations or upgrades.

Key Columns

• Identity and assignment: ROW_ID, TASK_ASSIGNMENT_ID, TASK_ID, TASK_NUMBER, PARENT_TASK_ID, RESOURCE_ID, RESOURCE_TYPE_CODE, RESOURCE_TERRITORY_ID, SHIFT_CONSTRUCT_ID, ASSIGNMENT_STATUS_ID.
• Predicted and actual timing: PLANNED_START_DATE, PLANNED_END_DATE, SCHEDULED_START_DATE, SCHEDULED_END_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE, TIMEZONE_ID, DURATION, DURATION_UOM — the core agenda payload referenced in the view description.
• Alarm and notification: ALARM_TYPE_CODE, ALARM_CONTACT, ALARM_START, NOTIFICATION_FLAG, NOTIFICATION_PERIOD, NOTIFICATION_PERIOD_UOM, ESCALATION_FLAG, ESCALATION_LEVEL. These columns drive reminder and escalation behaviour; a search on "alarm_count" most plausibly relates to counting or aggregating rows bearing alarm configuration, since no literal ALARM_COUNT column exists in the view.
• Effort and travel: PLANNED_EFFORT, ACTUAL_EFFORT, ACTUAL_EFFORT_UOM, SCHED_TRAVEL_DISTANCE, SCHED_TRAVEL_DURATION, ACTUAL_TRAVEL_DISTANCE, ACTUAL_TRAVEL_DURATION.
• Classification and flags: TASK_TYPE_ID, TASK_STATUS_ID, TASK_PRIORITY_ID, BILLABLE_FLAG, MILESTONE_FLAG, HOLIDAY_FLAG, MULTI_BOOKED_FLAG, PRIVATE_FLAG, PUBLISH_FLAG, PERCENTAGE_COMPLETE, REASON_CODE, BOUND_MODE_CODE, SOFT_BOUND_FLAG.
• Standard Who columns and extensibility: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, plus ATTRIBUTE_CATEGORY and ATTRIBUTE1–15.

Common Use Cases and Queries

Typical usage centres on technician agendas, dispatch boards, and alarm/notification dashboards. A representative query returns upcoming agenda entries per resource:

• SELECT task_number, resource_id, scheduled_start_date, scheduled_end_date, alarm_type_code, alarm_start FROM csf_agenda_v WHERE resource_id = :resource_id AND scheduled_start_date BETWEEN :from_date AND :to_date ORDER BY scheduled_start_date;
• Counting alarmed tasks: SELECT resource_id, COUNT(*) alarm_count FROM csf_agenda_v WHERE alarm_type_code IS NOT NULL GROUP BY resource_id;
• Escalation monitoring: SELECT task_number, escalation_level, notification_period FROM csf_agenda_v WHERE escalation_flag = 'Y';

Because the view invokes CSF_AGENDA_CALCULATIONS per row, filters should be applied narrowly and date ranges restricted where possible.