Search Results delete_task_post

Overview

APPS.JTF_TASK_TEMPLATES_CUHK is a PL/SQL customization package belonging to the Oracle CRM Foundation (JTF) module, specifically within the Task Manager schema. As indicated by the _CUHK suffix, this package is a customer-specific extension — in this case associated with The Chinese University of Hong Kong — layered on top of the standard Task Templates business object delivered with Oracle E-Business Suite. The package is defined with AUTHID CURRENT_USER and exposes a set of six procedures that serve as pre- and post-processing hooks around the core Create, Update, and Delete operations on task templates. The header comment ($Header: jtfctkms.pls 115.6 2002/12/05) confirms the package lineage dates back to the early 11i codebase and remains compatible with EBS 12.1.1 and 12.2.2, as the JTF task template data model was not materially restructured across those releases.

Key Procedures and Functions

The package defines six documented procedures, organized as three pairs of pre/post handlers. Each procedure accepts a task template record (p_task_templates) typed as jtf_task_templates_pub.task_template_rec and returns an x_return_status OUT parameter conforming to the standard JTF API return-status convention (FND_API.G_RET_STS_SUCCESS, ERROR, or UNEXPECTED_ERROR).

• CREATE_TASK_PRE — Invoked before a task template is inserted; typically used to validate or default attributes prior to the main DML.
• CREATE_TASK_POST — Invoked after insertion; intended for downstream side effects such as cross-reference or audit writes.
• UPDATE_TASK_PRE — Invoked before an existing task template is modified; used to validate the incoming changes against business rules.
• UPDATE_TASK_POST — Invoked after an update commits; commonly used to propagate changed values to dependent entities. This is the procedure most relevant to the user query "update_task_post".
• DELETE_TASK_PRE — Invoked before a task template is removed; used to enforce referential or business constraints.
• DELETE_TASK_POST — Invoked after deletion; used for cleanup or archival operations.

No explicit parameter lists beyond the two standard arguments should be assumed; the metadata discloses only these.

Tables Accessed

The ETRM metadata for this package lists no tables directly referenced through APPS synonyms. Given its role as a customization hook, the package most likely operates on the record passed in from the JTF_TASK_TEMPLATES_PUB API rather than performing direct DML against the base table JTF_TASK_TEMPLATES_B / JTF_TASK_TEMPLATES_TL. Any customer-specific tables used by the CUHK extension are not disclosed in the documented metadata and would need to be confirmed by inspecting the package body.

Usage Notes

This package is not called directly by end users or external integrations. It is invoked indirectly by the standard Task Manager API layer — specifically from the corresponding JTF_TASK_TEMPLATES_PUB Create, Update, and Delete routines, which call the _PRE hook before their internal DML and the _POST hook afterward. Typical entry points include the Task Templates setup form in the CRM Administrator responsibility and any concurrent program or custom code that calls JTF_TASK_TEMPLATES_PUB. Because the procedures are exposed on the APPS schema with AUTHID CURRENT_USER, custom extensions may also invoke UPDATE_TASK_POST directly, provided the task template record and return status are supplied. The package is referenced by no other documented packages, confirming it sits at the edge of the customization layer rather than in the dependency chain of standard JTF processing.