Search Results jtf_task_dependency_pub




Overview
Explore in AI Chat

Overview

The APPS.JTF_TASK_DEPENDENCY_PUB package body is a public PL/SQL API within the Oracle E-Business Suite Task Manager (JTF) module. Its business purpose is to manage task dependencies — the predecessor/successor relationships that link one task to another and govern scheduling order, lead/lag timing, and template-driven task networks. In release 12.1.1 and 12.2.2, this package provides the canonical server-side interface for creating, updating, locking, and deleting rows in the task dependency structure that underlies resource and project scheduling workflows.

The package is classified as a PUB (public) API, meaning the procedures are intended to be called by external consumers — forms, concurrent programs, and other PL/SQL packages — rather than restricted to internal use. The source header shows it was last shipped at version 120.1 (2005), a stability profile typical of core JTF foundation APIs reused across releases.

Key Procedures and Functions

The documented package exposes four public procedures. The search term create_task_dependency corresponds to the first and most heavily documented entry point.

  • CREATE_TASK_DEPENDENCY — Inserts a new dependency record linking a task to the task it depends upon. The signature accepts API-standard control parameters (p_api_version, p_init_msg_list, p_commit, p_validation_level), the task identifier or task number, the dependent-on task identifier or task number, the p_dependency_type_code defining the relationship, template and adjustment-time attributes, and the standard 15 descriptive flexfield p_attribute1..15 plus p_attribute_category. It returns x_dependency_id, x_return_status, x_msg_count, and x_msg_data. Internally it defines l_api_version as 1.0 and l_api_name as CREATE_TASK_DEPENDENCY, following the FND_API error-handling and message-stack conventions.
  • LOCK_TASK_DEPENDENCY — Acquires a logical or database lock on an existing dependency record, used to serialize concurrent maintenance before an update or delete.
  • UPDATE_TASK_DEPENDENCY — Modifies attributes of an existing dependency, such as the dependency type or adjustment timing.
  • DELETE_TASK_DEPENDENCY — Removes a dependency relationship, typically invoked when tasks are re-sequenced or detached.

Tables Accessed

The package operates against the following tables through APPS synonyms:

  • JTF_TASK_DEPENDS — The primary dependency table; CREATE/UPDATE/DELETE write here and LOCK reads for row identification.
  • JTF_TASKS_B — The task base table, referenced to resolve and validate task identifiers and task numbers supplied to CREATE_TASK_DEPENDENCY.
  • JTF_TASK_CONTACTS — Associated task contact data, referenced in dependency and validation processing.
  • DUAL — Used for single-row selection and scalar evaluations of API version or defaults.

Usage Notes

JTF_TASK_DEPENDENCY_PUB is typically invoked from the Task Manager and resource scheduling forms, from concurrent programs that rebuild task networks, and from custom PL/SQL that manages task sequencing. Because the procedures follow the FND_API pattern, callers must check x_return_status for fnd_api.g_ret_sts_success and inspect the message stack via x_msg_count/x_msg_data when g_ret_sts_error or g_ret_sts_unexp_error is returned. Commit behavior is controlled by p_commit, so callers embedding the API in a larger transaction should pass fnd_api.g_false and commit explicitly. The package is referenced by eight other packages, confirming its role as a shared dependency-management service within the JTF foundation layer.