Results for “alarm_start”

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

Overview

OKL_CS_TASKS_MAIN_UV is an APPS-owned database view within the OKL (Lease and Finance Management) product family in Oracle EBS 12.1.1 and 12.2.2. It exposes a consolidated, user-facing representation of the task records used throughout the OKL tasking framework, which is built on the shared JTF (Common Tasking) infrastructure. The view joins the core task table (JTF_TASKS_VL) to a series of reference and translation objects so that code values such as task type, status, priority, owner type, and source object type are resolved into descriptive names rather than raw identifiers. Additional joined objects supply the assigned-by user name, timezone name, and owner display name through the JTF_TASK_UTL package.

Because it flattens task header data and its descriptive lookups into a single queryable structure, the view is typically used for reporting, dashboarding, and integration extracts where a readable task listing is required without replicating the decoding logic in each query. It is not a transactional table; it is a read-only projection. The name suffix _UV follows the Oracle convention for a user view, signalling that the object is intended for consumption by report and interface developers rather than as a base table for DML.

Underlying Base Objects

The documented base objects confirm that the view is anchored on the JTF tasking model and enriched with several lookups and translations:

• JTF_TASKS_VL — the primary task entity supplying task identifiers, names, descriptions, dates, flags, and the duration attributes, including DURATION_UOM.
• JTF_TASK_TYPES_TL — resolves TASK_TYPE_ID to a translated task type name.
• JTF_TASK_STATUSES_VL — resolves TASK_STATUS_ID to status name and derives the CLOSED, CANCELLED, COMPLETED, and REJECTED indicator flags.
• JTF_TASK_PRIORITIES_TL — resolves TASK_PRIORITY_ID to a translated priority name.
• JTF_OBJECTS_VL — resolves owner type and source object type codes to descriptive names.
• HZ_TIMEZONES_TL — resolves TIMEZONE_ID to a timezone name.
• FND_USER — supplies ASSIGNED_BY_NAME from ASSIGNED_BY_ID.
• JTF_TASK_UTL — a package whose GET_OWNER function derives the display name of the task owner from owner type and owner identifier.
• JTF_TASK_CONTACTS_V and JTF_TASK_PHONES_V — related task contact and phone objects associated with the tasking model.
• HZ_PARTIES and HZ_CONTACT_POINTS — party and contact point data underlying customer and contact associations.

All referenced objects are accessed through APPS synonyms or validation views, so callers query only the APPS schema.

Key Columns

• ROW_ID, TASK_ID, TASK_NUMBER — unique identifiers for the task record.
• TASK_NAME, DESCRIPTION — the human-readable task title and narrative.
• TASK_TYPE_ID / TASK_TYPE — task classification identifier and decoded name.
• TASK_STATUS_ID / TASK_STATUS — status identifier and decoded name.
• CLOSED, CANCELLED, COMPLETED, REJECTED — Y/N flags derived from the status record, defaulting to 'N' via NVL.
• TASK_PRIORITY_ID / TASK_PRIORITY — priority identifier and decoded name.
• OWNER_ID, OWNER_TYPE_CODE, OWNER_TYPE, OWNER — owner identity, type code, decoded type, and resolved display name.
• SOURCE_OBJECT_ID, SOURCE_OBJECT_NAME, SOURCE_OBJECT_TYPE_CODE, SOURCE_OBJECT_TYPE — the business object that originated the task.
• PLANNED_START_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE, ALARM_START, ALARM_START_UOM — scheduling and alarm timing attributes.
• DURATION, DURATION_UOM — the task duration value and its unit of measure, the attribute commonly referenced when analysing task effort and intervals.
• NOTIFICATION_PERIOD, NOTIFICATION_PERIOD_UOM — notification lead time and its unit of measure.
• ASSIGNED_BY_ID / ASSIGNED_BY_NAME — the user who assigned the task.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• PRIVATE_FLAG, PUBLISH_FLAG, NOTIFICATION_FLAG, DELETED_FLAG — visibility and lifecycle flags.

Common Use Cases and Queries

Typical scenarios include open-task listings for lease servicing, SLA-oriented monitoring of overdue tasks, and extracts feeding external workflow or reporting tools.

• List active tasks with decoded status and priority.
• Report tasks whose DURATION_UOM indicates a particular unit (for example, hours) to analyse effort distribution.
• Group tasks by decoded owner or source object type for workload analysis.
• Extract tasks with notification settings for scheduler analysis.

SELECT task_number, task_name, task_status, task_priority,
       owner, duration, duration_uom
FROM   apps.okl_cs_tasks_main_uv
WHERE  closed = 'N'
AND    deleted_flag = 'N';

SELECT duration_uom, COUNT(*) task_count
FROM   apps.okl_cs_tasks_main_uv
WHERE  duration IS NOT NULL
GROUP  BY duration_uom;

Because the view resolves codes to names at query time, callers should filter on the identifier or flag columns for performance rather than on translated name columns.