Search Results task_split_flag

Overview

JTF_TASKS_VL is a Multi-Lingual Support (MLS) view owned by the APPS schema in Oracle E-Business Suite, and it is classified as VALID in the ETRM metadata for releases 12.1.1 and 12.2.2. It is part of the JTF (CRM Foundation) product family, which supplies the shared task-management infrastructure consumed across CRM applications such as Oracle TeleSales, Oracle Service, Oracle Marketing, and Oracle Field Service. The view is documented with the description "MLS View for JTF_TASKS_B and JTF_TASKS_TL," which identifies its central design purpose: it joins the language-independent base table JTF_TASKS_B to the translation table JTF_TASKS_TL so that consumers retrieve task records already resolved to the current session language.

For reporting and integration purposes, JTF_TASKS_VL is the primary supported read interface for task definitions. It exposes bilingual attributes (TASK_NAME and DESCRIPTION from the TL table) together with the full operational attribute set from the base table, so BI Publisher reports, OBIEE extracts, and custom concurrent programs can query a single object rather than performing the join manually.

Underlying Base Objects

The view is defined over two referenced base objects, both accessed through synonyms in the APPS schema:

• JTF_TASKS_B (SYNONYM) — the base (language-independent) table holding task identity, status, ownership, scheduling, alarm, effort, and flexfield attribute data.
• JTF_TASKS_TL (SYNONYM) — the translation table holding TASK_NAME and DESCRIPTION per language.

The view text joins the two on B.TASK_ID = T.TASK_ID and selects B.ROWID ROW_ID along with the columns of the base table and the two translated columns. Because the join is on TASK_ID and the translation table is filtered by the MLS framework at runtime, JTF_TASKS_VL returns one row per task in the session language. This structure is consistent with standard EBS MLS view conventions applied throughout CRM Foundation.

Key Columns

Identity and lifecycle columns include TASK_ID, TASK_NUMBER, OBJECT_VERSION_NUMBER, DELETED_FLAG, OPEN_FLAG, and the WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN). Classification is driven by TASK_TYPE_ID, TASK_STATUS_ID, TASK_PRIORITY_ID, REASON_CODE, and TASK_CONFIRMATION_STATUS.

Ownership and assignment are represented by OWNER_ID, OWNER_TYPE_CODE, OWNER_TERRITORY_ID, ASSIGNED_BY_ID, CUST_ACCOUNT_ID, CUSTOMER_ID, ADDRESS_ID, and LOCATION_ID. Scheduling and effort columns include PLANNED_START_DATE, PLANNED_END_DATE, SCHEDULED_START_DATE, SCHEDULED_END_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE, CALENDAR_START_DATE, CALENDAR_END_DATE, DURATION and DURATION_UOM, PLANNED_EFFORT and PLANNED_EFFORT_UOM, ACTUAL_EFFORT and ACTUAL_EFFORT_UOM, PERCENTAGE_COMPLETE, and TIMEZONE_ID.

Alarm and notification behavior is exposed via NOTIFICATION_PERIOD, NOTIFICATION_PERIOD_UOM, ALARM_START, ALARM_START_UOM, ALARM_ON, ALARM_COUNT, ALARM_FIRED_COUNT, ALARM_INTERVAL, ALARM_INTERVAL_UOM, and NOTIFICATION_FLAG. Flags such as PRIVATE_FLAG, PUBLISH_FLAG, BILLABLE_FLAG, MILESTONE_FLAG, HOLIDAY_FLAG, MULTI_BOOKED_FLAG, RESTRICT_CLOSURE_FLAG, TASK_SPLIT_FLAG, and the device flags (PALM_FLAG, WINCE_FLAG, LAPTOP_FLAG, DEVICE1_FLAG–DEVICE3_FLAG) capture task characteristics. SOURCE_OBJECT_TYPE_CODE, SOURCE_OBJECT_ID, SOURCE_OBJECT_NAME, ENTITY, WORKFLOW_PROCESS_ID, PARENT_TASK_ID, RECURRENCE_RULE_ID, TEMPLATE_ID, TEMPLATE_GROUP_ID, CHILD_POSITION, and CHILD_SEQUENCE_NUM carry integration and hierarchy context. ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 provide the descriptive flexfield.

Common Use Cases and Queries

Typical scenarios include: extracting open task lists for a resource, reconciling task schedules against calendars, reporting on billable or milestone tasks, auditing alarm configuration, and joining tasks to customer or opportunity data by CUST_ACCOUNT_ID or CUSTOMER_ID.

A representative query listing active tasks assigned to a given owner:

• SELECT task_id, task_number, task_name, task_status_id, planned_start_date, planned_end_date, percentage_complete FROM apps.jtf_tasks_vl WHERE owner_id = :p_owner_id AND deleted_flag = 'N' ORDER BY planned_start_date;

A query summarizing billable tasks by customer account:

• SELECT cust_account_id, COUNT(*) task_count, SUM(costs) total_cost FROM apps.jtf_tasks_vl WHERE billable_flag = 'Y' AND deleted_flag = 'N' GROUP BY cust_account_id;

A query traversing the parent-child task hierarchy:

• SELECT p.task_number parent_number, c.task_number child_number, c.child_position FROM apps.jtf_tasks_vl c, apps.jtf_tasks_vl p WHERE c.parent_task_id = p.task_id AND c.deleted_flag = 'N';

Because JTF_TASKS_VL is an MLS view, queries automatically return task names and descriptions in the current session language, and it should be preferred over direct joins to JTF_TASKS_B and JTF_TASKS_TL for any report or integration that displays human-readable task text.