Search Results aso_task_int




Overview
Explore in AI Chat

Overview

The APPS.ASO_TASK_INT package body is a PL/SQL integration utility belonging to the Oracle Order Capture / Quoting (ASO) module. Its principal business purpose is to maintain continuity of JTF task assignments when quotations and opportunities transition between records and versions. In Oracle EBS, JTF tasks (managed by the JTF framework) may be attached to a quote header to track sales follow-ups, approvals, or customer interactions. When a new version of a quote is created from an existing quote, or when an opportunity is converted or referenced into a quote, those task attachments must be propagated so that no historical activity is lost on the successor record.

The package is classified by ETRM as an OTHER API, signifying that it is not one of the primary public quotation APIs (such as ASO_QUOTE_PUB) but rather an internal integration helper invoked by the quoting infrastructure. The header comment ($Header: asoitskb.pls 120.4 2006/10/25 $) indicates a stable, long-lived code line whose last substantive revision predates the 12.1.1 and 12.2.2 releases, meaning behavior is consistent across both versions.

Key Procedures and Functions

  • COPY_TASKS — The documented core procedure. As described in the source comments, it is called when a new version of a quote is created from an existing quote. It retrieves all JTF tasks attached to the original object and re-attaches them to the new object. The parameter naming (p_old_object_id, p_new_object_id, p_old_object_type_code, p_new_object_type_code, p_new_object_name) confirms that the procedure is generic across object types rather than being hard-coded to quotes. A p_quote_version_flag parameter allows the caller to signal quote-versioning semantics explicitly. It follows the standard Oracle API contract, accepting p_api_version, p_init_msg_list, and p_commit, and returning x_return_status, x_msg_count, and x_msg_data for error handling. Internally it opens a cursor over the JTF task attributes (task name, type, description, status, priority, owner type, owner id, and owner territory) for the old object.
  • COPY_OPP_TASKS_TO_QTE — A companion procedure that copies JTF tasks from a sales opportunity to the resulting quote. This supports the opportunity-to-quote conversion flow, ensuring task history follows the customer through the sales cycle. As with COPY_TASKS, it relies on object mappings to translate the source and target identifiers.

Tables Accessed

  • JTF_TASK_REFERENCES_B — The base table of JTF task references. It stores the association between a task and the business object it is attached to, keyed by object type and object id. COPY_TASKS reads the old object's task references and inserts new reference rows for the new object, which is how task attachment is preserved across versions.
  • JTF_OBJECT_MAPPINGS — Used to resolve object type code relationships and identifier translation between source and destination objects, consistent with the procedure's generic parameters for old and new object ids and type codes.

Both tables are accessed through APPS synonyms, confirming the package executes with the standard APPS schema privileges.

Usage Notes

ASO_TASK_INT is invoked internally rather than called directly by end users. In Oracle EBS 12.1.1 and 12.2.2 it is triggered programmatically from the quote versioning and opportunity-to-quote conversion logic, typically orchestrated by higher-level ASO APIs or by the Quote form when a user creates a new version of an existing quote. ETRM metadata records that the package is referenced by two other PL/SQL packages, confirming its role as a subordinate integration module.

Because it participates in transactional flows, customizations should not call COPY_TASKS directly without respecting the FND_API commit and message-list conventions; callers should pass p_commit = FND_API.G_FALSE when participating in a larger transaction. Error conditions are surfaced through the standard x_return_status / x_msg_count / x_msg_data triplet, and the NOCOPY hints on the OUT parameters reflect optimization consistent with modern 11g/12c database versions used by EBS 12.2.2. Any extension or wrapper should preserve the existing cursor logic and parameter contract to avoid breaking the version-copy and conversion flows that depend on it.