Search Results jtf_task_types_vl




Overview
Explore in AI Chat

Overview

JTF_TASK_TYPES_VL is a Multi-Lingual Support (MLS) validation view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the JTF – CRM Foundation product family. It presents task type definitions maintained by the CRM Task Manager infrastructure, which underpins functionality shared across Oracle Sales, Oracle Service, Oracle Marketing, and related CRM modules in releases 12.1.1 and 12.2.2.

The suffix _VL denotes a "view of logical" rows: the view joins a language-independent base table to its translation table and restricts the translated rows to the language of the current session. This design allows forms, concurrent programs, and reports to display task type names and descriptions in the user's own language without exposing the underlying MLS join. Because task types drive defaulting, effort calculation, scheduling, and workflow assignment for CRM tasks, this view is a frequently referenced object in both reporting queries and integration interfaces that need to enumerate or resolve valid task types.

Underlying Base Objects

The view is defined over two APPS synonyms:

  • JTF_TASK_TYPES_B — the base table holding language-independent attributes for each task type, aliased as B in the view definition.
  • JTF_TASK_TYPES_TL — the translation table holding the translatable NAME and DESCRIPTION columns, aliased as T.

The two are joined on TASK_TYPE_ID, with the additional MLS predicate T.LANGUAGE = USERENV('LANG'), which resolves the translated row matching the language of the current runtime environment. The B table supplies a ROWID projected as ROW_ID together with all descriptive and control attributes, while the TL table contributes only the NAME and DESCRIPTION columns. Every column except NAME and DESCRIPTION originates from the base table B, including the RULE and WORKFLOW_TYPE columns listed in the view text but annotated separately from the main attribute set.

Key Columns

  • TASK_TYPE_ID — primary key of the task type; the join key between the two base tables and the value stored on task records.
  • NAME and DESCRIPTION — translated values retrieved from JTF_TASK_TYPES_TL for the session language.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — effective dating that determines whether a task type may be selected on a given date.
  • SEEDED_FLAG — indicates whether the row is Oracle-seeded or customer-defined.
  • WORKFLOW and WORKFLOW_TYPE — control whether a workflow process is launched for tasks of this type and identify the process category.
  • PLANNED_EFFORT and PLANNED_EFFORT_UOM — default effort quantity and unit of measure for tasks of the type.
  • SCHEDULE_FLAG, NOTIFICATION_FLAG, and PRIVATE_FLAG — behaviour indicators for scheduling, notification, and visibility.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF extensibility columns.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the associated business components.
  • ROW_ID — RowID of the base table row, exposed for tools that require it.

Common Use Cases and Queries

Typical usages include validating a task type before inserting a CRM task, populating LOVs in custom forms, and extracting task type metadata for integrations or data warehouses. A standard lookup query is:

  • SELECT task_type_id, name, seeded_flag FROM jtf_task_types_vl WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1) ORDER BY name;
  • SELECT task_type_id, name, planned_effort, planned_effort_uom FROM jtf_task_types_vl WHERE seeded_flag = 'N';
  • SELECT tt.task_type_id, tt.name, COUNT(*) FROM jtf_tasks_v t, jtf_task_types_vl tt WHERE t.task_type_id = tt.task_type_id GROUP BY tt.task_type_id, tt.name;

Because the view enforces the MLS language predicate, it should be preferred over querying the base tables directly; any query joining to JTF_TASK_TYPES_TL separately risks returning duplicate or non-session-language rows.