Search Results update_references




Overview

JTF_TASK_REFERENCES_PVT is a private PL/SQL package in the APPS schema that encapsulates the low-level data manipulation logic for task reference records within the Oracle E-Business Suite Task Manager (JTF) module. Task references represent associations between a task and an external or internal object—such as a customer, opportunity, lead, service request, or another business entity stored in the JTF_OBJECTS repository. These associations allow users to link tasks to the entities they relate to, providing context and traceability across the CRM and order-capture data model.

The package is classified as a PVT (private) API, meaning it is intended for internal consumption by the higher-level public packages and utilities within the JTF task infrastructure rather than being called directly by external or customer-developed code. Its responsibility is to centralize the insert, update, and delete logic for the JTF_TASK_REFERENCES base tables, ensuring that the corresponding translated and secured records are kept consistent.

The dependency metadata confirms that the package builds on the FND_API error-handling framework and the JTF_TASK_UTL utility package (the object the user searched for), and that it is referenced by a set of related task packages including JTF_TASKS_PUB, JTF_TASKS_PVT, JTF_TASK_REFERENCES_PUB, JTF_EC_REFERENCES_PVT, JTF_TASK_UTL, and JTF_TASK_UTL_EXT.

Key Procedures and Functions

The 12.2.2 ETRM metadata documents three procedures, which together form the complete maintenance surface for task reference data:

  • CREATE_REFERENCES — Inserts new task reference records, establishing the association between an existing task and the referenced object. It populates the base, secure, and translated tables consistently.
  • UPDATE_REFERENCES — Modifies attributes of an existing task reference, such as relationship details or descriptive fields, applying changes across the relevant underlying tables.
  • DELETE_REFERENCES — Removes task reference records, typically invoked when a task is unlinked from an object or when a task itself is being deleted.

All three procedures follow the standard Oracle EBS private API convention: they accept the primary key identifiers for the records being manipulated, return a standard FND_API.G_RET_STS_SUCCESS or error status, and propagate messages through the FND_API message stack so that calling public APIs can report failures to the user interface.

Tables Accessed

The package reads and writes the core Task Manager reference tables through APPS synonyms:

  • JTF_TASK_REFERENCES_B — The base table storing the primary task reference records, including the task identifier and the referenced object identifier.
  • JTF_TASK_REFERENCES_TL — The translated table holding language-specific descriptive attributes for each reference.
  • JTF_TASK_REFERENCES_S — The secure (row-level security) table used to enforce access control based on the operating unit or security profile.
  • JTF_TASKS_B — The parent task table, referenced to validate the task identifier and support delete cascades.
  • JTF_OBJECTS_B — The object registry table, used to resolve and validate the object being referenced.
  • DUAL — Used for single-row lookups and sequence/utility operations.

Usage Notes

JTF_TASK_REFERENCES_PVT is not invoked directly from Oracle Forms or concurrent programs. Instead, it is called by the public wrapper APPS.JTF_TASK_REFERENCES_PUB, which adds validation and higher-level business rules, and by the task maintenance packages JTF_TASKS_PUB and JTF_TASKS_PVT. The extended utility packages JTF_TASK_UTL and JTF_TASK_UTL_EXT (the object originally searched) also depend on it, along with JTF_EC_REFERENCES_PVT for the e-commerce reference path.

Custom code should call JTF_TASK_REFERENCES_PUB rather than this private package, since the private API performs no user-facing validation and relies on callers to supply valid identifiers and handle the returned API status. Because the object is documented as VALID and dependency-tracked across 12.1.1 and 12.2.2, it is a stable internal building block of the JTF task data model.