Search Results reconnect_dependency

Overview

JTF_TASK_DEPENDENCY_PVT is the private implementation package body for the Oracle EBS Task Dependency API. It belongs to the CRM/Telephony foundation layer (JTF = Java Task Foundation) and provides the server-side logic that governs relationships of precedence between tasks stored in the Oracle Tasks tables. In day-to-day business terms, this package makes it possible to model situations where one task cannot begin until another has completed, and to maintain those links as tasks are created, rescheduled, reassigned, or removed.

The suffix _PVT identifies this as the private half of a public/private API pair. The public specification (JTF_TASK_DEPENDENCY_PUB, where it exists) exposes a stable interface for external callers, while this body contains the actual procedural logic, validation rules, and direct DML against the dependency tables. The package is owned by APPS and holds VALID status in both 12.1.1 and 12.2.2. Because these are internal implementation routines, Oracle does not support them as a public extension point; they may be invoked indirectly through the task forms, through the public dependency API, or by other JTF packages such as JTF_TASK_DEPENDS_PKG and JTF_TASK_DEPENDS_S.

The body is intentionally cohesive: it validates dependency candidates, persists them, and reconciles them when upstream tasks change. It does not own the task record itself (that is JTF_TASKS_B) but instead owns the association records that link one task to another. ETRM records no objects that reference this body, confirming it is a leaf-level implementation component rather than a foundation for further extension.

Key Procedures and Functions

ETRM documents six procedures. They divide into validation, mutation, and reconciliation responsibilities.

• VALIDATE_DEPENDENCY — Performs the core eligibility checks for a proposed dependency relationship, including verifying that the referenced tasks exist and that the link is permitted by business rules (for example, avoiding circular or self-referencing dependencies).
• VALIDATE_TASK_DEPENDENCY — A task-centric validation variant, used to confirm the dependency state of an individual task before an operation proceeds.
• RECONNECT_DEPENDENCY — Re-establishes or re-points existing dependency links, typically after a task has been reassigned, copied, or otherwise restructured, so that the precedence chain remains intact.
• CREATE_TASK_DEPENDENCY — Inserts a new dependency record, validating first and then writing to the dependency tables.
• UPDATE_TASK_DEPENDENCY — Modifies an existing dependency record to reflect changes in the linked tasks or relationship attributes.
• DELETE_TASK_DEPENDENCY — Removes a dependency link, including any necessary cleanup of associated rows.

Callers should treat these as internal; the supported path is the public API or the standard task user interface.

Tables Accessed

The package operates on the following APPS synonyms:

• JTF_TASKS_B — The base task table. Read to confirm task identity and status during validation.
• JTF_TASK_DEPENDS — The primary dependency association table. This is where created, updated, and deleted relationships are persisted.
• JTF_TASK_DEPENDS_S — The sequence used to generate unique dependency identifiers on insert.
• DUAL — Used for single-row PL/SQL expressions and lightweight validations.

Writes are concentrated in JTF_TASK_DEPENDS; JTF_TASKS_B and DUAL are read-only from this package's perspective.

Usage Notes

This package is normally invoked indirectly. The Oracle Tasks and Assignments forms, task workflow processing, and the public dependency API all funnel through this body. Customizations should call the public wrapper rather than this private package, since internal signatures may change between releases without notice. The recommended pattern is to wrap calls in the standard FND message and API handling framework, checking FND_MSG_PUB for validation errors after each call.