Search Results okc_task_pvt




Overview
Explore in AI Chat

Overview

OKC_TASK_PVT is the private implementation package body for task management within the Oracle Contracts (OKC) module of Oracle E-Business Suite. It serves as the internal engine that creates, maintains, and deletes tasks and condition-driven task instances associated with contract documents stored in OKC_K_HEADERS_B. Tasks in this context represent actionable work items — approvals, deliverables, milestones, review activities, or contractual obligations — that must be tracked against a contract throughout its lifecycle.

The package follows Oracle's standard PVT (private) API architecture. Its PL/SQL procedures are not intended to be called directly by external consumers; instead they are invoked through the public OKC_API wrapper, which validates inputs, applies security, and translates exceptions before delegating the lower-level data manipulation to OKC_TASK_PVT. The classification of this object as a package body with a VALID status and an owner of APPS confirms it is a shipped, supported component of the ETRM (Enterprise Contracts) schema family.

Functionally, the package bridges contract structures and the shared JTF task framework (JTF_TASKS_B and related JTF tables). This integration allows contract tasks to participate in Oracle's common task and resource management infrastructure, including assignment to resources, status tracking, and task-type classification, while remaining anchored to the originating contract.

Key Procedures and Functions

Five documented procedures constitute the public surface of this package body:

  • CREATE_TASK — Creates a task record associated with a contract. It resolves the task type, status, owner, and timing attributes and writes the master task row into the JTF task tables.
  • CREATE_CONDITION_TASK — Creates a task tied to a contract condition or clause event, allowing conditional obligations to generate trackable work items.
  • CREATE_CONTINGENT_TASK — Creates a task whose existence depends on a contingency or triggering circumstance. This supports the modelling of obligations that become actionable only when a defined event occurs.
  • UPDATE_TASK — Modifies an existing task, including status transitions, assignee changes, and date or attribute adjustments.
  • DELETE_TASK — Removes a task, maintaining referential integrity with the underlying JTF task records.

Timing and resolution logic used by these procedures draws on OKC_RESOLVED_TIMEVALUES and OKC_TIME_CODE_UNITS_B, reflecting the package's responsibility for interpreting contract time periods and units when scheduling tasks.

Tables Accessed

The package reads and writes the core JTF task framework tables: JTF_TASKS_B, JTF_TASKS_TL, JTF_TASKS_V, JTF_TASK_STATUSES_B, JTF_TASK_STATUSES_TL, JTF_TASK_STATUSES_VL, JTF_TASK_TYPES_B, JTF_TASK_TYPES_TL, and JTF_TASK_TYPES_VL. These supply the base, translated, and validation-view layers for task entities, statuses, and types.

Assignment and relationship data are handled through JTF_RS_RESOURCE_EXTNS (resource assignment), JTF_OBJECTS_B, JTF_OBJECTS_VL, and JTF_OBJECT_USAGES (object linkage of tasks to contract entities). Contract anchors are provided by OKC_K_HEADERS_B. Timing resolution relies on OKC_RESOLVED_TIMEVALUES and OKC_TIME_CODE_UNITS_B. PLITBLM is used as the standard PL/SQL table buffer for bulk operations.

Usage Notes

OKC_TASK_PVT is invoked indirectly, primarily through the public OKC_API and the Contracts forms UI. Condition and contingent task procedures are typically fired from condition evaluation and clause-processing logic rather than from direct user action. Custom code should never call OKC_TASK_PVT directly; developers should use OKC_API, which maintains the documented contract for error handling via FND_API and profile-driven behaviour via FND_PROFILE. The package is referenced by one other package and references OKC_API, OKC_TIME_UTIL_PUB, JTF_TASKS_PUB, JTF_TASK_UTL, and OKC_QUERY, consistent with its role as a low-level worker within the ETRM task-processing stack.