Search Results jtf_task_references_vl

Overview

The view CSS_DEF_ESCALATED_DEFECTS_V belongs to the CSS – Support product family, a module classified as obsolete in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It presents a consolidated list of defect records that have been escalated, drawing together defect identity, escalation ownership, and escalation level information into a single queryable structure. The view serves reporting and integration purposes within the legacy defect-tracking framework, allowing downstream consumers to identify open, escalated defects without navigating the multiple base tables that hold task, reference, status, and defect data. The ETRM documentation explicitly notes that the object is not implemented in the current database, meaning it should be treated as a deprecated artifact retained for historical reference. Users searching for jtf_task_references_vl will encounter this view because that table forms part of its defining join chain.

Underlying Base Objects

The view is defined over five documented base objects: JTF_TASKS_VL, JTF_TASK_REFERENCES_VL, JTF_EC_STATUSES_VL, FND_LOOKUPS, and CSS_DEF_DEFECTS_B. The join logic links tasks to defects through JTF_TASK_REFERENCES_VL (aliased TRF), where OBJECT_TYPE_CODE = 'DF' and REFERENCE_CODE = 'ESC' identify the escalation reference. Tasks are joined to JTF_TASKS_VL (TSK) on TASK_ID and constrained to TASK_TYPE_ID = 22. Status filtering relies on JTF_EC_STATUSES_VL (TST), excluding tasks whose statuses are flagged as closed, cancelled, completed, or rejected. Escalation level meanings are resolved through FND_LOOKUPS (FLK) using lookup type JTF_TASK_ESC_LEVEL. The defect master is provided by CSS_DEF_DEFECTS_B, joined on DEFECT_ID = TRF.OBJECT_ID. The ETRM metadata records no separately enumerated base objects beyond those in the view text.

Key Columns

• DEFECT_ID — The surrogate identifier of the defect, sourced from the task reference object.
• DEFECT_NUMBER — The user-visible defect number from CSS_DEF_DEFECTS_B.
• ESCALATION_OWNER_ID — Identifier of the resource or party to whom the escalation is assigned.
• ESCALATION_OWNER_TYPE_CODE — The type classification of the escalation owner.
• ESCALATION_OWNER_NAME — Resolved owner name, truncated to 573 characters via CSS_DEF_RESOURCE_UTIL_PVT.GET_RESOURCE_NAME.
• ESCALATION_LEVEL_CODE — The escalation level value stored on the task.
• ESCALATION_LEVEL_MEANING — The translated meaning of the level, obtained from FND_LOOKUPS.

Common Use Cases and Queries

Typical usage centers on generating dashboards or extracts of active escalated defects and their current owners. Because the view already applies status and reference filters, a simple select returns the relevant population.

SELECT defect_number,
       escalation_owner_name,
       escalation_level_meaning
FROM   css_def_escalated_defects_v
ORDER BY escalation_level_code;

A common integration pattern filters by escalation level or owner to drive notification or workload distribution processes.

SELECT defect_id,
       defect_number,
       escalation_owner_name
FROM   css_def_escalated_defects_v
WHERE  escalation_level_code >= 2;

Given the obsolete status and the note that the view is not implemented, any dependency should be reviewed and migrated to supported constructs before upgrading from 12.1.1 to 12.2.2.