Search Results update_task_without_note




Overview
Explore in AI Chat

Overview

APPS.TASK_MGR is a PL/SQL package that provides the programmatic task-management interface for the Oracle E-Business Suite Tasks framework, built on the JTF (Joint Task Force) schema objects JTF_TASKS_B, JTF_NOTES_B, and JTF_RS_RESOURCE_EXTNS. Its header identifies it as JTFATSKS.pls, version 120.2, last shipped in October 2005, and the package is classified as an OTHER API within ETRM 12.1.1 and 12.2.2. The package encapsulates the create, query, and update lifecycle for task records, allowing callers to create tasks, retrieve tasks filtered by status and ownership, update task completion details, and attach or update party notes without directly manipulating the underlying tables. It also exposes a query_test procedure used to exercise the query mechanism. Because it is the sole documented entry point for the query_task operation that the user searched for, it is the canonical API for retrieving task data in EBS forms, concurrent programs, and custom extensions that rely on the JTF Tasks schema.

Key Procedures and Functions

  • CREATE_TASK — Creates a task record, accepting task name, task type, task status, owner type and owner, source object type, and party identifiers, and returning status information through its OUT parameters.
  • QUERY_TASK — A function returning a CLOB result set of tasks, with parameters controlling API version, paging (start pointer and record count), task status filter, whether all tasks are shown, and sort order. This is the entry point corresponding to the "query_task" search.
  • QUERY_TEST — A test harness procedure that exercises the same query parameters as QUERY_TASK (API version, paging, show-all flag, and sort order) without returning a CLOB, used to validate query behavior.
  • UPDATE_TASK — Updates an existing task identified by task ID, applying an object version number for optimistic locking, updating comments and completion status, and returning status information via OUT parameters.
  • UPDATE_TASK_WITHOUT_NOTE — Performs the same task update as UPDATE_TASK but without writing an associated note.
  • UPDATE_PARTY_NOTE — Updates or applies a note against a party, using party ID and comment text together with the object version number.

Tables Accessed

  • JTF_TASKS_B — The base task table where TASK_MGR creates, queries, and updates task records.
  • JTF_NOTES_B — Stores note content associated with tasks and parties; written by UPDATE_TASK and UPDATE_PARTY_NOTE, and omitted by UPDATE_TASK_WITHOUT_NOTE.
  • JTF_RS_RESOURCE_EXTNS — Resource/owner extension data used to resolve task ownership and resource context during creation and query.
  • DBMS_LOB — Oracle's large-object utility, used to assemble and return the CLOB produced by QUERY_TASK.
  • PLITBLM — A PL/SQL index-by table utility referenced for internal collection handling.

Usage Notes

TASK_MGR is typically invoked from the JTF Tasks UI and related EBS forms, from concurrent programs that batch task creation or status updates, and from custom PL/SQL integrations that need task data without touching the JTF tables directly. Callers should pass a valid API_VERSION, supply an OBJECT_VERSION_NUMBER on updates to preserve optimistic locking, and be aware that QUERY_TASK returns a CLOB whose contents must be parsed by the caller. Because the package is classified as an OTHER API rather than a public, certified interface, custom code should treat its signatures as stable for the documented release but validate behavior after upgrades from 12.1.1 to 12.2.2. Use UPDATE_TASK_WITHOUT_NOTE when a note update would be redundant or would violate note-handling rules, and use QUERY_TEST only in controlled validation scenarios.