Results for “alarm_fired_count”

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

Overview

The OKC_LAUNCH_TASKGRID_V view in the APPS schema is a Contracts Core (OKC) presentation object that feeds the Launchpad Schedule tab within Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2, the Contracts Launchpad provides a consolidated work area for contract administrators, and the Schedule tab renders a task grid summarizing deliverable actions associated with contracts. This view supplies the row set consumed by that grid.

Its role is purely read-oriented: it joins task header, task translation, task type translation, task status translation, and contract rule data into a single flattened result set. Because it is an APPS-owned view rather than a table, it is typically queried by Oracle Forms-based Launchpad code and can also be referenced by customer reports and integrations that need to surface contract schedule tasks. The view has no direct DML semantics; inserts or updates must target the underlying JTF_TASKS_B and related tables.

Underlying Base Objects

The view is defined over synonyms and packages including:

• JTF_TASKS_B and JTF_TASKS_TL — base task records and their language translations.
• JTF_TASK_TYPES_TL and JTF_TASK_STATUSES_TL — lookup translations for task type and status.
• JTF_TASK_UTL — package supplying the GET_OWNER function used to resolve owner display names.
• OKC_RESOLVED_TIMEVALUES and OKC_RULES_B — contract rule and resolved time-value data linking tasks to contract identifiers.
• Additional OKC objects such as OKC_ACTION_ATTRIBUTES_B, OKC_ACTION_ATT_VALS, OKC_CONDITION_HEADERS_B, OKC_CONDITION_OCCURS, and package OKC_QUERY, which support the broader Launchpad schedule derivation.

The definition is a UNION ALL of task-type-specific branches, each filtering on TASK_TYPE_ID values (for example 23 and 24) to segment schedule records by task classification.

Key Columns

• TASK_ID, TASK_NUMBER — unique task identifiers and user-facing task numbers.
• TASK_TYPE — translated name from JTF_TASK_TYPES_TL; directly relevant to the user's search for task_type.
• TASK_NAME — translated task description.
• OWNER — resolved through JTF_TASK_UTL.GET_OWNER based on owner type and ID.
• DUE_DATE / END_DATE — planned end and actual end dates.
• STATUS — translated task status.
• CONTRACT_ID — contract linkage; in branch one it is derived via OKC_RULES_B and OKC_RESOLVED_TIMEVALUES, while in branch two it equals SOURCE_OBJECT_ID.
• ALARM_FIRED_COUNT, OBJECT_VERSION_NUMBER, SOURCE_OBJECT_ID — supporting control columns.

Common Use Cases and Queries

Typical usage includes verifying schedule tasks on a contract, reporting upcoming due dates, and auditing task types. Because TASK_TYPE is a translated column, filtering directly on its literal value is common when users search by task type name.

SELECT task_number, task_type, task_name, owner, due_date, status, contract_id
FROM   apps.okc_launch_taskgrid_v
WHERE  contract_id = :p_contract_id
ORDER  BY due_date;

SELECT task_type, COUNT(*)
FROM   apps.okc_launch_taskgrid_v
WHERE  status NOT IN ('Completed','Cancelled')
GROUP  BY task_type;

Because the view applies USERENV('LANG') to all translation joins, results return only rows in the session language; reports run under a different NLS language may return fewer rows if translations are missing. Joins to the base JTF tables should use TASK_ID as the correlation key.