Results for “escalation_level”

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

Overview

JTF_TASK_UWQ_MYOWN_V is a database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the JTF product family (CRM Foundation) and is documented as an internal view consumed by the UWQ — the Universal Work Queue framework that routes and displays task-oriented work items to users across CRM applications such as TeleSales, Service, and Field Service. The view supplies the row set that represents tasks owned by the currently authenticated resource, which is why every row it returns carries the literal OWNED_FLAG value 'O'.

Because the object is a view rather than a table, it stores no data of its own and performs no DML of its own; it is a read-only projection layered over the JTF task and JTF object tables, enriched with denormalized descriptive columns from reference and party tables. The presence of the search term object_parameters in the documentation reflects the fact that the view surfaces the JTF_OBJECTS_B.OBJECT_PARAMETERS column directly, making the parameter payload of the source business object available to the Work Queue alongside the task attributes.

Underlying Base Objects

The ETRM 12.2.2 metadata records the following referenced objects, all resolved through APPS synonyms except the status view and the two PL/SQL packages:

• JTF_TASKS_B and JTF_TASKS_TL — the base task entity and its translatable name column.
• JTF_TASK_STATUSES_VL, JTF_TASK_TYPES_TL, JTF_TASK_PRIORITIES_TL — validation and lookup views and tables supplying status, type, and priority names.
• JTF_OBJECTS_B and JTF_OBJECTS_TL — the source business object definition, including OBJECT_FUNCTION, OBJECT_PARAMETERS, and ENTER_FROM_TASK.
• HZ_PARTIES, HZ_TIMEZONES, HZ_TIMEZONES_TL — customer name and timezone conversion data.
• JTF_TASK_UTL (package) — used for the GET_OWNER call.
• JTF_TASK_UWQ_PVT (package) — used for GET_PRIMARY_PHONE and GET_PRIMARY_EMAIL.

Joins are driven by TASK_STATUS_ID, TASK_TYPE_ID, TASK_PRIORITY_ID, SOURCE_OBJECT_TYPE_CODE to OBJECT_CODE, and TASK_ID, with language predicates tied to USERENV('LANG'). The priority join is outer (+) so tasks without a priority are retained.

Key Columns

• TASK_ID, TASK_NUMBER, TASK_NAME — primary task identity and display label.
• TASK_TYPE, TASK_STATUS, TASK_PRIORITY — decoded descriptive values.
• PLANNED_START_DATE, PLANNED_END_DATE, SCHEDULED_START_DATE, SCHEDULED_END_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE — the task lifecycle dates.
• SOURCE_OBJECT_TYPE_CODE / SOURCE_OBJECT_TYPE / SOURCE_OBJECT_ID — the originating business object.
• OBJECT_FUNCTION and OBJECT_PARAMETERS — the object handler and its parameter string, the columns most closely associated with the user's search term.
• OWNER_TYPE_CODE, OWNER_ID, OWNER — resolved through JTF_TASK_UTL.GET_OWNER.
• CUSTOMER_NAME (from HZ_PARTIES), RESOURCE_ID and RESOURCE_TYPE (mapped from the task owner columns).
• Primary phone and primary email, resolved dynamically by JTF_TASK_UWQ_PVT.
• OWNED_FLAG ('O'), CLOSED_FLAG ('N'), and NVL(ENTER_FROM_TASK,'N') — literal control flags for Work Queue presentation.

Common Use Cases and Queries

The view is primarily an internal dependency of the Universal Work Queue rather than a supported customer-facing reporting interface, and direct modification is neither possible nor advisable. It is nonetheless frequently inspected for troubleshooting Work Queue task display, missing phone or email values, and object parameter handling.

SELECT task_number, task_name, task_status,
       object_function, object_parameters,
       customer_name, actual_start_date
FROM   apps.jtf_task_uwq_myown_v
WHERE  task_status = 'Open';

A second common pattern filters on the source object to inspect parameter payloads:

SELECT task_id, source_object_type, object_function,
       object_parameters, resource_id
FROM   apps.jtf_task_uwq_myown_v
WHERE  object_function = 'SERVICE_REQUEST';

Because GET_OWNER, GET_PRIMARY_PHONE, and GET_PRIMARY_EMAIL execute per row, queries over large task volumes should be restricted with selective predicates on TASK_ID, TASK_NUMBER, or TASK_STATUS_ID to avoid unnecessary package calls.