Results for “booking_start_date”

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

Overview

JTF_TASK_ASSIGNMENTS_V is a database view owned by the APPS schema in Oracle E-Business Suite, belonging to the JTF (CRM Foundation) product family. Its documented purpose is narrow and precise: it returns all task assignment records in which the ASSIGNEE_ROLE value is equal to the literal 'ASSIGNEE'. This makes it a filtered projection over the broader assignment data model rather than an unfiltered replica. In Oracle EBS 12.1.1 and 12.2.2, the view is frequently reached indirectly by Oracle Field Service, Oracle TeleService, and Oracle Sales applications, as well as by CRM scheduling and resource-assignment logic that needs to distinguish the primary assignee from other assignment participants such as owners, resources, or notification recipients.

Because the view is registered with status VALID, it is safe for custom reporting, concurrent program queries, Oracle Discoverer workbooks, and inbound/outbound interface extraction. Users searching for the term "assignee_role" typically encounter this object because ASSIGNEE_ROLE is the discriminator column embedded in its WHERE clause, and it is also exposed as a selectable column in the view's projection.

Underlying Base Objects

According to the documented metadata, the view is defined over JTF_TASK_ALL_ASSIGNMENTS, which resolves through a SYNONYM at runtime. JTF_TASK_ALL_ASSIGNMENTS is the all-encompassing assignment table for the JTF task model; it stores every assignment row regardless of role. The predicate NVL(ASSIGNEE_ROLE, 'ASSIGNEE') = 'ASSIGNEE' has an important consequence: rows where ASSIGNEE_ROLE is NULL are treated as primary assignees and are therefore included in the view. Only rows explicitly tagged with a non-null, non-'ASSIGNEE' role are excluded. Any referential joins required to resolve resource names, statuses, or task headers must be performed by the caller against the relevant base/reference entities, since the view itself is a straightforward column-level projection.

Key Columns

• TASK_ASSIGNMENT_ID — Primary unique identifier for the assignment; join key back to JTF_TASK_ALL_ASSIGNMENTS.
• TASK_ID — Foreign key to the parent task; used to join to JTF_TASKS_VL or JTF_TASKS_B for task header details.
• ASSIGNEE_ROLE — Always intended to be 'ASSIGNEE' in this view; useful for confirmation in ad hoc queries.
• RESOURCE_TYPE_CODE / RESOURCE_ID — Identify the assigned party (for example, a person, group, or organization) using the CRM resource model.
• ASSIGNMENT_STATUS_ID — Current status of the assignment; joins to lookup or status definitions.
• RESOURCE_TERRITORY_ID — Territory associated with the assignment, relevant for territory-based access and reporting.
• OBJECT_VERSION_NUMBER — Optimistic locking token used by the OAF/BC4J layers; critical for safe programmatic updates.
• ACTUAL_START_DATE / ACTUAL_END_DATE / ACTUAL_EFFORT — Execution metrics for completed assignments.
• SCHEDULE_FLAG, ALARM_TYPE_CODE, SHIFT_CONSTRUCT_ID, SHOW_ON_CALENDAR, FREE_BUSY_TYPE — Scheduling and calendar integration attributes.
• BOOKING_START_DATE / BOOKING_END_DATE — Booking window for reservation-style assignments.
• SECURITY_GROUP_ID — Multi-org/security partitioning column; must be filtered where applicable.
• WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN for audit and incremental extraction.
• ATTRIBUTE1–15, ATTRIBUTE_CATEGORY — Descriptive flexfield segments available to customers.

Common Use Cases and Queries

Typical uses include building assignee worklists, driving resource-scheduling reports, and extracting task assignments into a data warehouse. A simple listing of assignments for a given task:

SELECT TASK_ASSIGNMENT_ID, TASK_ID, RESOURCE_TYPE_CODE, RESOURCE_ID, ASSIGNMENT_STATUS_ID
  FROM APPS.JTF_TASK_ASSIGNMENTS_V
 WHERE TASK_ID = :p_task_id
   AND NVL(SECURITY_GROUP_ID, -1) = :p_security_group_id;

Incremental extraction by audit columns is common for interfaces:

SELECT TASK_ASSIGNMENT_ID, TASK_ID, ASSIGNEE_ROLE, LAST_UPDATE_DATE
  FROM APPS.JTF_TASK_ASSIGNMENTS_V
 WHERE LAST_UPDATE_DATE >= :p_since
 ORDER BY LAST_UPDATE_DATE;

A join to obtain task headers for a calendar report:

SELECT a.TASK_ID, t.NAME, a.RESOURCE_ID, a.BOOKING_START_DATE, a.BOOKING_END_DATE
  FROM APPS.JTF_TASK_ASSIGNMENTS_V a,
       APPS.JTF_TASKS_VL t
 WHERE a.TASK_ID = t.TASK_ID
   AND a.SHOW_ON_CALENDAR = 'Y'
   AND a.BOOKING_START_DATE BETWEEN :p_from AND :p_to;