Results for “alarm_count”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JTF_AGENDA_V is a CRM Foundation (JTF) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to calculate the predicted start and end times of valid assigned tasks, making it the primary agenda-facing read interface for task scheduling and assignment data in the CRM Foundation layer. Rather than storing data itself, the view projects assignment, task, resource, and scheduling attributes from its underlying objects and applies escalation logic at query time, so consumers always obtain a computed view of agenda state rather than a static row.

Because the view is a reporting and integration surface, it is commonly accessed by personalizations, custom concurrent programs, OAF/Forms extensions, and third-party scheduling or dispatch integrations. The user search for current_task_id is relevant here: while the view itself does not expose a column literally named CURRENT_TASK_ID, that terminology is frequently used informally to mean the currently active or in-progress task identifier for a resource. In JTF_AGENDA_V, the effective "current task" is identified through TASK_ID combined with the assignment and status columns such as TASK_STATUS_ID and ASSIGNMENT_STATUS_ID, filtered by the relevant date window.

Underlying Base Objects

The documented base objects for JTF_AGENDA_V are:

• JTF_AGENDA_CALCULATIONS (PACKAGE) — supplies the calculation logic used to derive predicted start and end times, and is invoked directly in the view definition for the ESCALATION_FLAG column via JTF_AGENDA_CALCULATIONS.SET_ESCALATION_FLAG(V.TASK_ID).
• JTF_AGENDA_TA_V (VIEW) — the task-assignment view aliased as V in the view text, from which the majority of projection columns are drawn.

The view text selects from the alias V and enriches each row with a function call into the calculations package. This means JTF_AGENDA_V is dependent on both the task-assignment view hierarchy and the JTF_AGENDA_CALCULATIONS PL/SQL package; invalidation of either object can affect the view's status, and the escalation flag is therefore evaluated per row at runtime rather than persisted.

Key Columns

• ROW_ID, TASK_ASSIGNMENT_ID, TASK_ID — unique row identifier, the assignment record, and the underlying task. TASK_ID is the practical equivalent of a "current task" reference when combined with status and date filters.
• RESOURCE_TYPE_CODE, RESOURCE_ID, RESOURCE_TERRITORY_ID — the assigned resource and its territory, central to agenda filtering by person or resource.
• PLANNED_START_DATE, PLANNED_END_DATE, SCHEDULED_START_DATE, SCHEDULED_END_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE — the three-tier date model; predicted times are the calculated output described in the object description.
• DURATION, DURATION_UOM, PLANNED_EFFORT, ACTUAL_EFFORT, PERCENTAGE_COMPLETE — effort and completion measures.
• TASK_STATUS_ID, ASSIGNMENT_STATUS_ID, TASK_PRIORITY_ID, TASK_TYPE_ID, TASK_NUMBER — status and classification attributes used to isolate active or open tasks.
• ESCALATION_FLAG, ESCALATION_LEVEL, NOTIFICATION_FLAG, NOTIFICATION_PERIOD — computed escalation state returned from JTF_AGENDA_CALCULATIONS.
• TIMEZONE_ID, PARENT_TASK_ID, SOURCE_OBJECT_TYPE_CODE, SOURCE_OBJECT_ID — context and hierarchy columns.
• Attribute1–15, ATTRIBUTE_CATEGORY, OBJECT_VERSION_NUMBER — standard DFF and concurrency columns; OBJECT_VERSION_NUMBER supports OAF optimistic locking.

Common Use Cases and Queries

The view supports agenda rendering, dispatch dashboards, and escalation reporting. A typical query to find the current task for a resource uses the assignment status and a date window rather than a literal CURRENT_TASK_ID column:

• SELECT task_id, task_number, resource_id, scheduled_start_date, scheduled_end_date, escalation_flag FROM jtf_agenda_v WHERE resource_id = :resource_id AND trunc(sysdate) BETWEEN trunc(scheduled_start_date) AND trunc(scheduled_end_date);
• SELECT task_id, task_number, percentage_complete FROM jtf_agenda_v WHERE assignment_status_id = :status AND escalation_flag = 'Y';
• SELECT task_id, parent_task_id, task_status_id FROM jtf_agenda_v WHERE task_assignment_id = :assignment_id;

Because escalation is computed by package function, queries filtering on ESCALATION_FLAG may execute the function for each candidate row; restricting by resource, date, or status first improves performance. Applications searching for a "current_task_id" should map that requirement to TASK_ID constrained by ASSIGNMENT_STATUS_ID and the scheduled date range, which is the documented and supported pattern for this view.