Results for “planned_effort_uom”

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

Overview

OKL_CS_TASKS_BALI_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined within the OKL (Leasing and Finance Management) product family. The suffix _UV denotes a user-facing "user view" layer historically used in the ETRM/lease management data model to expose task records for external consumption, reporting, and integration. In Oracle EBS 12.1.1 and 12.2.2, the view presents a denormalized, presentation-friendly projection of task data sourced from the JTF (Task Manager) foundation objects, joining descriptive identifiers such as task type, task status, priority, owner, and source object type in place of raw foreign keys.

The view's principal purpose is to provide a single, flattened row per task with human-readable decodes. This simplifies building BI Publisher reports, Oracle Discoverer workbooks, custom concurrent programs, and PL/SQL integration routines without requiring the caller to re-implement the join logic to the JTF lookup views and translation tables.

Underlying Base Objects

The view is defined over the following documented base objects:

• JTF_TASKS_VL (VIEW) — the primary fact source, supplying TASK.ROW_ID, TASK_ID, TASK_NUMBER, TASK_NAME, DESCRIPTION, dates, flags, and the recurrence, alarm, and duration attributes.
• JTF_TASK_ASSIGNMENTS (SYNONYM) — assignment context for task ownership and responsibility.
• JTF_TASK_TYPES_TL (SYNONYM) — translated task type names, surfaced as TASK_TYPE via TYPE.NAME.
• JTF_TASK_STATUSES_VL (VIEW) — status names and status flags (CLOSED_FLAG, CANCELLED_FLAG, COMPLETED_FLAG, REJECTED_FLAG), decoded as TASK_STATUS and its NVL-defaulted indicator columns.
• JTF_TASK_PRIORITIES_TL (SYNONYM) — priority names, exposed as TASK_PRIORITY.
• JTF_OBJECTS_VL (VIEW) — object type names used for both SOURCE_OBJECT_TYPE and OWNER_TYPE decodes.
• FND_USER (SYNONYM) — supplies ASSIGNED_BY_NAME via FND.USER_NAME.
• JTF_TASK_UTL (PACKAGE) — the function GET_OWNER(OWNER_TYPE_CODE, OWNER_ID) resolves the OWNER display string dynamically.

Because the view resolves names through _TL and _VL objects, output is language-sensitive and returns the appropriate translated descriptions based on the session language. The view is a join-only construct; no data is stored within it, so all access reflects the current committed state of the underlying JTF tables.

Key Columns

• ROW_ID / TASK_ID — the unique primary identifiers used to reference a task in downstream APIs and joins.
• TASK_NUMBER, TASK_NAME, DESCRIPTION — human-readable identification and narrative fields.
• TASK_TYPE, TASK_STATUS, TASK_PRIORITY — decoded lookup values from the corresponding translation views.
• CLOSED, CANCELLED, COMPLETED, REJECTED — single-character flags defaulted to 'N' where null, enabling straightforward status filtering.
• OWNER_TYPE_CODE, OWNER_ID, OWNER — the responsible party identity; OWNER is derived by JTF_TASK_UTL.GET_OWNER.
• SOURCE_OBJECT_ID, SOURCE_OBJECT_NAME, SOURCE_OBJECT_TYPE — traceability back to the originating business object, typically a lease, contract, or asset.
• RECURRENCE_RULE_ID — the identifier of the recurring task rule governing repeated generation of the task instance.
• PLANNED_START_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE — scheduling and completion timing.
• NOTIFICATION_PERIOD/NOTIFICATION_PERIOD_UOM, ALARM_START/ALARM_START_UOM, DURATION/DURATION_UOM, PLANNED_EFFORT — reminder, duration, and effort metrics.
• ASSIGNED_BY_ID, ASSIGNED_BY_NAME, CUST_ACCOUNT_ID, ADDRESS_ID — assignment and customer association.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• PARENT_TASK_ID, PARENT_TASK_NUMBER — returned as NULL in this view definition, indicating no task hierarchy is projected.

Common Use Cases and Queries

Typical scenarios include lease task dashboards, overdue notification reporting, recurrence analysis, and integration feeds. Because the user searched on recurrence_rule_id, the most common query pattern filters recurring task instances:

• List all recurring tasks — SELECT task_number, task_name, recurrence_rule_id, task_status FROM okl_cs_tasks_bali_uv WHERE recurrence_rule_id IS NOT NULL;
• Open task workload — SELECT task_status, COUNT(*) FROM okl_cs_tasks_bali_uv WHERE closed = 'N' GROUP BY task_status;
• Tasks by owner — SELECT owner, task_number, planned_start_date FROM okl_cs_tasks_bali_uv WHERE owner_type_code = :p_type;
• Source object trace — join SOURCE_OBJECT_ID back to the originating OKL contract or asset table for reconciliation reporting.

As a reporting view, it should be queried with appropriately selective predicates on indexed base columns (TASK_ID, dates) to avoid full scans of the underlying JTF tables.