Search Results delete_task_dependency

Overview

CSF_TASK_DEPENDENCY_PUB is a public PL/SQL package in the APPS schema that manages task dependency records for Oracle E-Business Suite. Its stated purpose, per the package header comments, is to perform operations on the JTF_TASK_DEPENDS table, which stores the relationships that define when one task must precede, follow, or otherwise constrain another task. Task dependencies are a foundational element of task and resource scheduling within the Oracle Task Manager (JTF) framework, used by applications such as Field Service, TeleSales, and the Customer Support suite.

The package follows the standard Oracle EBS PL/SQL API model. Each procedure declares a common API signature including p_api_version, p_init_msg_list, p_commit, and p_validation_level as input parameters, and standard output parameters x_return_status, x_msg_count, and x_msg_data. This design allows callers to participate in the FND_MSG_PUB error stack and to control transactional boundaries and validation behavior consistently with other EBS public APIs.

Key Procedures and Functions

• CREATE_TASK_DEPENDENCY_NV — Creates a new dependency relationship between two tasks. The record is written to JTF_TASK_DEPENDS, and the generated dependency identifier is returned to the caller. The suffix "NV" signifies that this variant executes without validation of an underlying entity object. Standard attribute columns (p_attribute1 through p_attribute15 and p_attribute_category) are exposed for descriptive flexfield support.
• LOCK_TASK_DEPENDENCY — Obtains a lock on an existing dependency record so that subsequent modifications within the same transaction are serialized and protected from concurrent updates. This is typically the first step in an update or delete sequence.
• UPDATE_TASK_DEPENDENCY — Modifies the attributes of an existing task dependency, such as the dependency type code or the task identifiers that define the relationship. Callers are expected to lock the row prior to invoking this procedure.
• DELETE_TASK_DEPENDENCY — Removes a task dependency record from JTF_TASK_DEPENDS, dissolving the scheduling relationship between the two tasks. This is the procedure referenced when users or integration code need to break an existing predecessor/successor constraint between tasks.
• CLEAR_TASK_DEPENDENCIES — Removes all dependency records associated with a given task in a single operation. This bulk-delete variant is useful when a task is being redefined, rescheduled, or removed and all of its dependency relationships must be discarded together.

Tables Accessed

The package operates exclusively against JTF_TASK_DEPENDS, accessed through the APPS synonym. This table is the repository for inter-task dependency definitions, holding the originating task identifier, the dependent task identifier, the dependency type, and the descriptive flexfield attribute columns exposed by the create procedure. All insert, update, lock, and delete activity performed by the package converges on this single table, making it the authoritative persistence point for task dependency data.

Usage Notes

CSF_TASK_DEPENDENCY_PUB is classified as a PUB (public) API, indicating that it is a supported integration point for external callers. ETRM metadata records no dependent packages referencing it, so its invocation is driven primarily by Oracle application forms, scheduling logic in the Task Manager UI, and custom or third-party code that requires programmatic control of task dependencies.

Because the procedures conform to the standard EBS API contract, callers should pass an appropriate API version, honor the returned x_return_status before committing, and respect savepoint semantics when embedding calls inside a larger transaction. To delete a single dependency, invoke DELETE_TASK_DEPENDENCY; to remove every dependency for a task, use CLEAR_TASK_DEPENDENCIES. In Oracle EBS 12.1.1 and 12.2.2, the package resides under the APPS schema and remains available without additional configuration.