Search Results jtf_task_depends_pkg




Overview
Explore in AI Chat

Overview

The APPS.JTF_TASK_DEPENDS_PKG package is a foundational data-access layer within the Oracle E-Business Suite Task Manager (JTF) module. Its principal business function is to manage the persistence of task dependency relationships — records that describe how one task is constrained by, linked to, or sequenced against another task. In Oracle EBS 12.1.1 and 12.2.2, this package supplies the low-level DML operations that a higher-level public and private API stack relies upon when tasks must be created, amended, or removed with their associated dependencies intact.

The package resides in the APPS schema and holds a VALID status in the ETRM repository. It is classified as OTHER under the documented API classification, indicating that it is an internal helper package rather than a formally published integration API. Its role is therefore architectural: it isolates the physical table manipulation logic for task dependencies so that the public and private interfaces above it remain consistent and maintainable.

Key Procedures and Functions

The ETRM documentation lists four documented procedures for this package. None of these should be treated as a supported integration entry point, and their signatures are not published; their behavior is described in functional terms below.

  • INSERT_ROW — Creates a new task dependency record. It is the entry point used when a dependency between two tasks is first established, persisting the association into the underlying dependency table.
  • LOCK_ROW — Obtains a row-level lock on an existing task dependency record. This supports concurrency control, ensuring that a dependency is not modified or deleted by another session while the current operation is in progress.
  • UPDATE_ROW — Modifies the attributes of an existing task dependency. It is invoked when the nature or parameters of an established relationship between two tasks change.
  • DELETE_ROW — Removes a task dependency record. It is called when a dependency is dissolved, either because the linkage is no longer required or because a parent task is being reorganized.

Collectively, these four procedures constitute a standard CRUD-with-locking pattern typical of Oracle EBS table-handler packages.

Tables Accessed

The only documented table referenced by this package, accessed through an APPS synonym, is JTF_TASK_DEPENDS. This is the base table that stores the dependency definitions between tasks. Because JTF_TASK_DEPENDS_PKG restricts its activity to this single table, its scope is narrow and predictable: every insert, lock, update, and delete performed by the package maps directly to a row in JTF_TASK_DEPENDS. No other application tables appear in the documented dependency information, which simplifies impact analysis for upgrades, patches, and customizations.

Usage Notes

The package is not intended for direct invocation by end users, Oracle Forms, or concurrent programs. Instead, it is referenced by two higher-level packages: APPS.JTF_TASK_DEPENDENCY_PUB and APPS.JTF_TASK_DEPENDENCY_PVT. This layered arrangement follows the standard Oracle EBS public/private API convention, in which the _PUB package exposes the supported interface, the _PVT package encapsulates validation and business logic, and the underlying table handler (JTF_TASK_DEPENDS_PKG) performs the physical DML. Notably, the package also references itself in its dependency listing, indicating internal recursion or internal procedure calls. Custom code should call the public API stack rather than JTF_TASK_DEPENDS_PKG directly, since the latter's procedures are unsupported and subject to change across releases such as 12.1.1 and 12.2.2.