Results for “create_task_phones”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JTF_TASK_PHONES_PUB is a public PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that manages the association of telephone information with tasks and task contacts in the CRM Foundation (CAC) product family. Its header comment identifies it as "the public package to validate, create, update, and delete task phones," confirming its role as the supported entry point for maintaining the JTF_TASK_PHONES entity. The package is classified as a PUBLIC API (PUB) within ETRM and carries the display name "Task Phone" with a business entity category of CAC_CAL_TASK. It is documented as scope internal, active lifecycle, and compatibility level "S" (supported). Because it exposes a controlled API surface rather than requiring direct DML against the underlying tables, it allows callers to persist phone-to-task relationships while preserving the integrity of the task, contact, and phone data model. This makes it relevant to implementers and integrators working with task telephony in both EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes four documented procedures, providing full create, update, lock, and delete lifecycle support for task phone records.

• CREATE_TASK_PHONES — Creates a task phone association. Per the documented API comments, it accepts a task contact identifier and a phone identifier and returns the newly generated task phone identifier along with the standard return status. The procedure validates input and initializes the record's standard attributes before insertion.
• UPDATE_TASK_PHONES — Modifies an existing task phone record. It is used to change attributes of a task phone association, such as the phone reference or descriptive details, while relying on the object version number for optimistic concurrency control.
• LOCK_TASK_PHONES — Acquires a lock on a task phone record so that a subsequent update or delete operates safely against concurrent modifications.
• DELETE_TASK_PHONES — Removes a task phone association. It is the supported mechanism for detaching a phone from a task contact without issuing direct deletes.

A package-level record type, task_phones_rec, mirrors the entity's columns: task_phone_id, task_contact_id, phone_id, object_version_number, descriptor flexfield attributes (attribute1 through attribute15 and attribute_category), owner_table_name, and primary_flag. This record is used to pass data between callers and the API procedures.

Tables Accessed

Through APPS synonyms the package reads and writes the following tables:

• JTF_TASK_PHONES — the primary entity table holding task phone rows.
• JTF_TASK_PHONES_S — the sequence source used to generate task_phone_id values.
• JTF_TASK_CONTACTS — the task contact context to which a phone is attached.
• JTF_TASKS_B — the base task record, used to validate task context.
• HZ_CONTACT_POINTS — the TCA contact point (phone) being referenced.
• DUAL — used for sequence and utility selection.

Usage Notes

JTF_TASK_PHONES_PUB is intended for programmatic use by forms, concurrent programs, and custom code rather than for direct table manipulation. The ETRM metadata records that it is referenced by eight other packages, indicating it serves as a shared dependency in the task management layer. Callers should follow the standard EBS API conventions evident in the documented parameters, notably p_api_version, p_init_msg_list, p_commit, and the x_return_status out parameter, which reports the outcome of the operation. Custom integrations should always invoke these procedures and check x_return_status rather than issuing DML against JTF_TASK_PHONES directly, ensuring validation, locking, and object version handling are applied consistently.