Search Results jtf_task_references_vl




Overview
Explore in AI Chat

Overview

JTF_TASK_REFERENCES_VL is a multilingual (MLS) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the JTF – CRM Foundation product. It presents the translatable and non-translatable attributes of task references, which are cross-references that link a task record to an external or internal object — such as an order, a service request, a customer, a document, or an arbitrary entity identified by object type and object identifier. In Oracle EBS 12.1.1 and 12.2.2 the object is reported with a status of VALID in ETRM.

Because the view is defined as a language-sensitive join, it returns exactly one row per task reference, resolved to the session language of the querying user (through USERENV('LANG')). This makes it the preferred access point for concurrent programs, OAF/Forms-based pages, BI Publisher reports, and integration interfaces that must display or extract reference data without explicitly joining the base and translation tables or filtering on LANGUAGE. It is also the object usually referenced by CRM Foundation code and by custom extensions that need to read task-reference information in a locale-correct manner.

Underlying Base Objects

The view is defined over two documented base objects, both exposed as synonyms in the APPS schema:

  • JTF_TASK_REFERENCES_B — the base (non-translatable) table holding the primary key TASK_REFERENCE_ID together with the relational keys, descriptive identifiers, DFF attributes, and audit columns. The view aliases this table as B.
  • JTF_TASK_REFERENCES_TL — the translation table holding language-dependent columns, keyed by TASK_REFERENCE_ID and LANGUAGE. The view aliases this table as T.

The join condition is B.TASK_REFERENCE_ID = T.TASK_REFERENCE_ID AND T.LANGUAGE = USERENV('LANG'). Consequently, the "_VL" suffix is literal: the view exposes the base row combined with the single translation row matching the current language environment. The ROW_ID column is projected from B.ROWID, and OBJECT_VERSION_NUMBER is carried through for optimistic locking in the CRM Foundation framework.

Key Columns

  • TASK_REFERENCE_ID — primary key of the reference record; the join key between the base and translation tables.
  • TASK_ID — foreign key to the parent task (JTF_TASKS_B); identifies which task the reference belongs to.
  • OBJECT_TYPE_CODE, OBJECT_NAME, OBJECT_ID — identify the referenced entity: its type, its display name, and its internal identifier.
  • OBJECT_DETAILS — free-form descriptive text about the referenced object.
  • REFERENCE_CODE — classification code for the reference relationship.
  • USAGE — translation-table column providing the language-specific usage or descriptive text for the reference.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield (DFF) context and segment columns for customer-defined reference attributes.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
  • ROW_ID, OBJECT_VERSION_NUMBER — row identifier for the CRM Foundation framework and the version number used for concurrent-update control.

Common Use Cases and Queries

Typical uses include reporting on the objects referenced by a task, resolving references in the session language, and exporting reference data for integration. A representative query lists references for a given task:

SELECT task_reference_id, task_id, object_type_code, object_name, object_id, reference_code, usage
FROM apps.jtf_task_references_vl
WHERE task_id = :p_task_id
ORDER BY creation_date;

A join to the task table produces a readable task-to-object listing:

SELECT t.task_number, r.object_type_code, r.object_name, r.reference_code
FROM apps.jtf_tasks_vl t, apps.jtf_task_references_vl r
WHERE t.task_id = r.task_id;

Because the view filters on USERENV('LANG'), callers should be aware that rows appear only when a matching translation row exists for the session language; installations performing data extracts outside a normal EBS session may need to initialize the language environment explicitly. Where all translations are required, the base and TL tables should be queried directly rather than through the _VL view.