Search Results create_contingent_task

Overview

OKC_TASK_PUB is the public API package for task management within the Oracle Contracts (OKC) module of Oracle E-Business Suite. In the service contracts and subscription domain, a task represents a discrete unit of work that must be performed against a contract, such as a delivery, an installation, an acceptance milestone, or a time-based obligation. The package body exposes a set of documented public procedures that allow both Oracle's internal application logic and customer extension code to create, modify, and remove these task records in a controlled and validated manner.

The published body operates as a thin wrapper layer. Each public procedure performs standard API housekeeping — version checking, message list initialization, and return status validation through OKC_API — and then delegates the substantive business logic to the corresponding private API in OKC_TASK_PVT. This two-tier design (PUB delegating to PVT) is the standard Oracle EBS pattern, ensuring that direct table manipulation is avoided and that all validation, defaulting, and concurrency rules are applied consistently regardless of the calling channel.

Key Procedures and Functions

• CREATE_TASK — Creates a task associated with a resolved time value. It accepts the resolved time identifier, timezone information, the time value entity identifier, and a planned end date, and returns the newly created task identifier along with the standard return status, message count, and message data outputs.
• CREATE_CONDITION_TASK — Creates a task driven by a contract condition, allowing task generation to be tied to the satisfaction or evaluation of a condition defined on the contract rather than to a simple time value.
• CREATE_CONTINGENT_TASK — Creates a task that is contingent in nature, supporting scenarios where the task is generated as a consequence of a dependent or conditional event within the contract lifecycle.
• UPDATE_TASK — Modifies the attributes of an existing task record, providing a controlled path for changing task details without direct DML against the underlying tables.
• DELETE_TASK — Removes a task record from the system, applying the package's validation and messaging conventions so that callers receive consistent error reporting.

All procedures follow the standard EBS API signature conventions: an API version parameter, an initialization flag, a commit flag, the entity-specific input parameters, and the standard x_return_status, x_msg_count, and x_msg_data output parameters. The body confirms these conventions in the CREATE_TASK implementation, which validates the return status and raises the corresponding OKC_API exception on error.

Tables Accessed

The documented metadata for OKC_TASK_PUB does not enumerate the physical tables touched by the body. Based on the package's function and the standard OKC data model, the procedures operate on the task table (OKC_TASKS) and its related entities, reading contract, condition, and time value data supplied or resolved through the parameters. Because the public layer delegates to OKC_TASK_PVT, the actual INSERT, UPDATE, and DELETE operations are performed in the private package, keeping the public interface free of direct DML. The package is itself referenced by three other packages, confirming it is intended as a reusable, callable service rather than a leaf-level utility.

Usage Notes

OKC_TASK_PUB, and specifically CREATE_CONDITION_TASK, is typically invoked from contract authoring and service contract forms when a user action triggers task generation, and from concurrent programs that batch-generate tasks for large volumes of contracts. Custom integrations and extension code should call the public procedures rather than inserting into the task tables directly, honoring the API version and initialization parameters and inspecting the return status before committing. The p_commit flag allows the caller to control transaction boundaries, so callers performing multi-step operations should pass a value that defers commit until all steps succeed.