Search Results jtf_task_references_pub




Overview
Explore in AI Chat

Overview

JTF_TASK_REFERENCES_PUB is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Task Manager / TeleSales (JTF) product family and provides the externally callable programmatic entry point for managing task references — the associations that link a task record to other business objects, such as a customer, sales opportunity, service request, contact, or document. A task reference effectively records "what this task relates to," enabling the Task Manager framework, escalation workflows, and dependent application modules to navigate from a task to its related entities.

The package is classified as a PUBLIC API (PUB suffix), distinguishing it from the corresponding private package JTF_TASK_REFERENCES_PVT, which contains the internal implementation logic. The public package is the supported interface for external callers and enforces the standard EBS API conventions, including dependency on FND_API for error and message handling and on JTF_TASK_UTL for shared task utility logic. As of Oracle 12.2.2 it is documented as VALID and is referenced by nine other packages, confirming its role as a widely consumed foundation service within the JTF module.

Key Procedures and Functions

The documented interface exposes four procedures, representing a complete create-read-modify-delete lifecycle for task reference records:

  • CREATE_REFERENCES — Creates one or more new task reference records, establishing the association between a task and a related object. Callers supply the task identifier, the object reference information, and the API-standard context (p_commit, p_init_msg_list, and the x_return_status / x_msg_count / x_msg_data out parameters).
  • UPDATE_REFERENCES — Modifies existing task reference records, typically when the association attributes change or when the referenced relationship must be re-pointed. It observes the same standard API parameter conventions as the create operation.
  • DELETE_REFERENCES — Removes task reference records, disassociating a task from the related object. This is the standard mechanism used when a reference is superseded or no longer valid.
  • LOCK_REFERENCES — Acquires a lock on existing reference records, supporting concurrency control so that a caller can safely read-then-update without interference from concurrent sessions. This is the conventional "lock" companion API in EBS public API design.

All four procedures follow the Oracle Application Object Library API standard: they accept initialization and commit flags and return a status code plus message stack rather than raising exceptions to the caller.

Tables Accessed

Through APPS synonyms, the package operates against the following base tables:

  • JTF_TASK_REFERENCES_B — the primary transactional table storing reference header/association records. This is the main target of the create, update, and delete operations.
  • JTF_TASK_REFERENCES_TL — the translation table holding language-dependent descriptive text for references, maintained alongside the _B table via the multi-lingual (TL) framework.
  • JTF_TASKS_B — the task base table, accessed to validate the task identifier and confirm the task exists before creating a reference.
  • JTF_OBJECTS_B — the object registry table, used to validate that the referenced object type is a recognized JTF object and to resolve object metadata.

Usage Notes

JTF_TASK_REFERENCES_PUB is invoked by forms, workflow activities, concurrent programs, and custom code that manage task relationships. Within standard EBS, its principal internal callers include JTF_TASKS_PUB (the master task API), JTF_EC_REFERENCES_PVT and JTF_ESCWFACTIVITY_PVT (escalation and workflow activity logic), ASO_TASK_INT (Order Capture task integration), and the customer-hook packages JTF_TASK_REFERENCES_CUHK, _IUHK, and _VUHK, which provide client-extension points. Because those hooks and the private package JTF_TASK_REFERENCES_PVT both reference this API, customizations should call JTF_TASK_REFERENCES_PUB rather than the private package. Developers are advised to implement the provided customer hooks for pre/post processing and to rely on the documented procedures only, since these remain the upgrade-safe, supported entry point across both 12.1.1 and 12.2.2.