Search Results ozf_task_template_pvt




Overview
Explore in AI Chat

Overview

OZF_TASK_TEMPLATE_PVT is a private PL/SQL package body in the APPS schema that implements the business logic layer underpinning Oracle Trade Management task template functionality in Oracle E-Business Suite 12.1.1 and 12.2.2. In the ETRM (Enterprise Territory and Resource Management) module, task templates provide reusable definitions that drive the automatic generation of tasks for trade promotion activities, TM campaigns, and channel management workflows. The package follows the standard Oracle API architecture, where a public package (typically JTF_TASK_TEMPLATES_PUB or an OZF wrapper) exposes the entry points while this private package carries the actual validation, DML, and message-handling logic. It depends heavily on foundation services such as FND_API, FND_MSG_PUB, FND_MESSAGE, and JTF_PLSQL_API, confirming that it uses the standard EBS API error-handling and message-stack conventions. The object exposes nine documented procedures and functions whose names are prefixed with the task template, list, and reason-record semantics typical of Trade Management.

Key Procedures and Functions

The package exposes nine documented units:

  • CREATE_TASKTEMPLATE — Creates a new task template record, populating the JTF task template tables and returning the generated identifier to the caller.
  • UPDATE_TASKTEMPLATE — Modifies an existing task template definition, applying the same validation rules as creation.
  • DELETE_TASKTEMPLATE — Removes or logically inactivates a task template, subject to referential integrity checks against dependent records.
  • GET_TASKTEMPLATE — Retrieves task template attributes for display or downstream processing.
  • VALIDATE_TASKTEMPLATE — Performs the mandatory-field, lookup, and business-rule validations required before any create or update is committed.
  • CHECK_TASKTEMPLATE_ITEMS — Verifies the item (task) lines attached to a template, ensuring each references valid task types, statuses, and priorities.
  • CHECK_TASKTEMPLATE_RECORD — Confirms that a template record exists and is accessible, typically used before update or delete operations.
  • INIT_REASON_REC — Initializes the reason record structure used for change-reason capture, a standard Trade Management audit requirement on template modifications.
  • COMPLETE_TASKTEMPLATE_REC — Finalizes and returns the completed task template record structure to the calling public API.

Tables Accessed

The package references the following objects through APPS synonyms. It reads JTF_TASK_TEMPLATES_VL and JTF_TASK_TEMP_GROUPS_VL to obtain template headers and template group definitions from the JTF (CRM Foundation) task model. JTF_TASK_TYPES_VL, JTF_TASK_STATUSES_VL, and JTF_TASK_PRIORITIES_VL supply the validated lookup values used by CHECK_TASKTEMPLATE_ITEMS and VALIDATE_TASKTEMPLATE, guaranteeing that only enabled task metadata is persisted. The public package JTF_TASK_TEMPLATES_PUB and utility package JTF_TASK_UTL are invoked for shared template services. The object PLITBLM (the standard PL/SQL table index-by binary_integer type) appears in the dependency list, indicating internal collection usage within the package body.

Usage Notes

OZF_TASK_TEMPLATE_PVT is not referenced by any other database object, which is consistent with its role as a private implementation package: it is invoked only from within the Trade Management task template public API layer, not directly from database triggers or other packages. The Oracle Trade Management HTML-based setup forms for task templates and the underlying Java/BC4J mid-tier calls route through the public API, which delegates to this package. Customizations should never call OZF_TASK_TEMPLATE_PVT directly; integrators should use the documented public API surface instead. Because the package calls FND_MSG_PUB and FND_API, callers must initialize the message stack and inspect the returned API status rather than relying on exceptions alone. The package is valid on both 12.1.1 and 12.2.2; the 12.2 Online Patching (ADOP) model means any customization layered on top should be delivered through standard extension mechanisms rather than direct edits to this seed object.