Results for “jtf_task_all_assignments_v”

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

Overview

JTF_TASK_ALL_ASSIGNMENTS_V is an APPS-owned database view in the Oracle E-Business Suite CRM Foundation (JTF) module. Its documented purpose is to retrieve every task assignment record in which the assignee role is either OWNER or ASSIGNEE. Because tasks in the JTF task model may carry multiple assignment rows — including roles such as resource, contact, or notification recipients — this view provides a pre-filtered projection that isolates the two roles that represent the party actually responsible for performing or owning the task.

In release 12.1.1 and 12.2.2, the view is used extensively by CRM applications, Task Manager, calendar and resource scheduling features, and by reporting and integration layers that need a flattened, role-qualified list of assignments. It also simplifies downstream development, since consumers do not need to add a role predicate against ASSIGNEE_ROLE each time they query assignments. The view is a straightforward SELECT projection; it performs no aggregation and exposes the same row grain as the underlying assignment entity.

Underlying Base Objects

The view is defined over a single referenced base object, JTF_TASK_ALL_ASSIGNMENTS, which is presented in the data dictionary as a SYNONYM. The view text selects from this object and renames the physical ROWID to ROW_ID, while otherwise exposing the assignment columns without transformation. Because the source object is a synonym, the actual data resides in the underlying assignment table in the JTF schema; the synonym provides the APPS-level access path used by the view definition.

The relationship is strictly one-to-one at the row level: each row returned corresponds to one assignment record. There is no join, union, or filter expressed in the documented view text other than the semantic restriction implied by its description — that the assignee role is OWNER or ASSIGNEE. Callers should therefore expect a subset of JTF_TASK_ALL_ASSIGNMENTS rows rather than the complete assignment population.

Key Columns

• TASK_ID — Identifier of the parent task; the primary link to the task header and the join key used in most reporting queries.
• TASK_ASSIGNMENT_ID — Primary identifier of the assignment row itself.
• ASSIGNMENT_STATUS_ID — The status of the assignment, resolving to a lookup value. This is the column most frequently searched for, and it is the standard mechanism for reporting on assignment progress (for example, accepted, rejected, or complete).
• ASSIGNEE_ROLE — The role of the assignee; the view's defining attribute, restricted to OWNER or ASSIGNEE.
• RESOURCE_TYPE_CODE and RESOURCE_ID — Identify the assigned party, typically a resource or group, depending on the resource type.
• ACTUAL_START_DATE, ACTUAL_END_DATE — Recorded actual execution times, distinct from the scheduled dates held on the task header.
• ACTUAL_EFFORT and ACTUAL_EFFORT_UOM — Effort consumed and its unit of measure.
• SCHEDULE_FLAG, SHOW_ON_CALENDAR, FREE_BUSY_TYPE — Scheduling indicators used by calendar and resource availability features.
• OBJECT_VERSION_NUMBER — Optimistic locking column required by the framework for update operations.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — Descriptive flexfield segments.
• ORIG_SYSTEM_REFERENCE and ORIG_SYSTEM_REFERENCE_ID — Source-system cross-reference for integrations.

Common Use Cases and Queries

The view supports task status reporting, workload analysis, calendar queries, and inbound/outbound integration of assignment data. A typical query lists assignments for a task together with their status and resource.

• Assignment status lookup: SELECT task_id, task_assignment_id, resource_id, assignment_status_id FROM jtf_task_all_assignments_v WHERE assignment_status_id = :p_status;
• Assignments for a task: SELECT task_assignment_id, resource_id, assignee_role, actual_start_date, actual_end_date FROM jtf_task_all_assignments_v WHERE task_id = :p_task_id;
• Effort summary: SELECT resource_id, SUM(actual_effort) FROM jtf_task_all_assignments_v WHERE assignment_status_id = :p_status GROUP BY resource_id;

Because ASSIGNMENT_STATUS_ID is stored as an identifier, it should normally be resolved through the appropriate JTF lookup view or FND_LOOKUPS before display.