Search Results jtf_tasks

Overview

APPS.OKC_LAUNCH_TASKGRID_V is a supplementary view owned by the APPS schema and registered in Oracle E-Business Suite under FND Design Data as OKC.OKC_LAUNCH_TASKGRID_V. Its type is documented as a view used to simplify forms coding, and the ETRM metadata carries the standard Oracle caution that query or modification of this view directly is not recommended, since its definition may change substantially across minor or major releases.

The view presents a flattened, denormalized projection of task records originating in the JTF Tasks foundation tables, enriched with contract-specific context from the Oracle Contracts (OKC) module. Because the user search term "jtf_tasks" corresponds precisely to the primary base objects of this view, OKC_LAUNCH_TASKGRID_V is the interface through which task grid data derived from JTF_TASKS is exposed to the Contracts launch and task grid user interface. Rather than a standalone reporting object, it is a UI-supporting view intended for consumption by Oracle Forms/ADF-based contract task grids and, in practice, by extension code that needs contract-aware task details in a single query.

Underlying Base Objects

Per the 12.2.2 documented metadata, OKC_LAUNCH_TASKGRID_V references the following base objects: JTF_TASKS_B and JTF_TASKS_TL (task base and translated task name/description), JTF_TASK_STATUSES_TL (translated task statuses), JTF_TASK_TYPES_TL (translated task types), the JTF_TASK_UTL package, OKC_ACTION_ATTRIBUTES_B and OKC_ACTION_ATT_VALS (action/counter-offer attributes), OKC_CONDITION_HEADERS_B and OKC_CONDITION_OCCURS (contract condition definitions and their occurrences), OKC_RESOLVED_TIMEVALUES and OKC_RULES_B (derived schedule/deliverable time values and rule definitions), the OKC_QUERY package, and OKC_R (a view or synonym associated with the OKC schema). All JTF and OKC objects are accessed via synonyms within the APPS schema.

The join topology ties each JTF task row to its contract source through SOURCE_OBJECT_ID, which resolves either to OKC_RESOLVED_TIMEVALUES (tasks generated from schedule rules), to the contract ID (contingent events), or to OKC_CONDITION_OCCURS (condition-evaluated tasks). This explains why OKC_RULES_B, OKC_CONDITION_HEADERS_B, and OKC_ACTION_ATTRIBUTES_B appear in the dependency list: they supply the metadata needed to render task grids in the context of a contract's rules and conditions.

Key Columns

• TASK_ID (NUMBER) — Foreign key to JTF_TASKS; the primary join key to the underlying task base table.
• TASK_NUMBER (VARCHAR2 30) — Human-readable task number from JTF_TASKS.
• TASK_TYPE (VARCHAR2 30) — Task type from JTF_TASKS, resolved via JTF_TASK_TYPES_TL for display.
• OBJECT_VERSION_NUMBER (NUMBER) — Optimistic-locking column, set to 1 on insert and incremented on update, used by APIs to verify the current record version.
• SOURCE_OBJECT_ID (NUMBER) — The owning object's key: resolved timevalue ID, contract ID, or condition occurrence ID depending on the task origin.
• TASK_NAME (VARCHAR2 80) — Task name from JTF_TASKS (translated via JTF_TASKS_TL).
• OWNER (VARCHAR2 4000) — Task owner from JTF_TASKS; the wide length accommodates multi-value owner lists.
• DUE_DATE (DATE) — Date the task is due.
• END_DATE (DATE) — End of the active period (one second before midnight on the indicated date).
• STATUS (VARCHAR2 30) — Task status, resolved via JTF_TASK_STATUSES_TL.
• CONTRACT_ID (NUMBER) — Contract primary key.
• ALARM_FIRED_COUNT (NUMBER) — Number of escalations fired for the task.

Common Use Cases and Queries

Typical uses include building contract task grids, reporting on outstanding contract tasks, and diagnosing escalation behavior. Because it is a supplementary UI view, it should be treated as read-only.

List open tasks for a contract:

SELECT task_id, task_number, task_name, due_date, status
FROM   apps.okc_launch_taskgrid_v
WHERE  contract_id = :p_contract_id
AND    status NOT IN ('COMPLETE','CANCELLED')
ORDER BY due_date;

Identify tasks escalated repeatedly:

SELECT task_id, task_name, owner, due_date, alarm_fired_count
FROM   apps.okc_launch_taskgrid_v
WHERE  alarm_fired_count > 0
ORDER BY alarm_fired_count DESC, due_date;

Reconstruct the documented projection for integration extracts:

SELECT task_id, task_number, task_type, object_version_number,
       source_object_id, task_name, owner, due_date, end_date,
       status, contract_id, alarm_fired_count
FROM   apps.okc_launch_taskgrid_v;