Search Results validate_task_contact_id

Overview

APPS.JTF_EC_UTIL is a utility PL/SQL package body within the Oracle E-Business Suite CRM schema family, responsible for shared validation and helper logic used across the escalation, task, contact, and resource components of the JTF (Java Task Framework) / escalate module. Its header identifies it as part of the jtfvecub.pls script family (version 115.8) and it belongs to the ETRM utility API classification, meaning it is intended primarily as an internal support layer rather than a business-facing API. In EBS 12.1.1 and 12.2.2, packages of this class centralize the repetitive argument-checking, duplicate detection, status validation, and message-construction work that would otherwise be re-implemented in every caller. JTF_EC_UTIL is referenced by four other packages, confirming its role as a shared dependency in the escalation and task call graph.

Key Procedures and Functions

The documented interface exposes 23 procedures and functions, several of which are directly relevant to the user search term validate_task_contact_id.

• VALIDATE_TASK_CONTACT_ID — the procedure the user searched for. It validates that a supplied task-contact identifier is internally consistent and usable, and raises standard FND_API error messages when the argument is null, missing, or otherwise invalid.
• VALIDATE_CONTACT_ID — validates a contact identifier in isolation, typically invoked before or alongside VALIDATE_TASK_CONTACT_ID.
• VALIDATE_TASK_PHONE_ID and VALIDATE_TASK_REFERENCE_ID — analogous validation routines for task phone and task reference association identifiers.
• VALIDATE_OWNER — checks that an owner identifier is present and that its owner type corresponds to a valid, currently effective object code associated with the RESOURCES usage.
• VALIDATE_REQUESTER — performs the parallel check for the requester role.
• VALIDATE_ESC_STATUS, CHECK_COMPLETED_STATUS, and CHECK_IF_ESCALATED — status-related logic used to determine whether an escalation or task has reached a completed or escalated state.
• VALIDATE_LOOKUP and VALIDATE_DESC_FLEX — validate lookup code values and descriptive flexfield input respectively.
• VALIDATE_ESC_DOCUMENT — validates escalation document information.
• REFERENCE_DUPLICATED and CONTACT_DUPLICATED — duplicate-detection helpers for task references and task contacts.
• ADD_INVALID_ARGUMENT_MSG, ADD_PARAM_IGNORED_MSG, and ADD_MISSING_PARAM_MSG — shared message-construction routines that populate the FND message stack with standardized JTF text.
• CONV_MISS_NUM, CONV_MISS_DATE, and CONV_MISS_CHAR — conversion helpers that normalize FND_API miss values into typed NULLs.

Tables Accessed

The package reads and writes a defined set of APPS-synonymed tables. JTF_TASK_CONTACTS is the primary table supporting the contact validation routines. JTF_TASKS_B and JTF_TASK_PHONES and JTF_TASK_REFERENCES_B back the task, phone, and reference checks. JTF_OBJECTS_B and JTF_OBJECT_USAGES support owner-type validation, the latter filtered on the RESOURCES object user code. PER_ALL_PEOPLE_F, FND_USER, FND_LOGINS, and JTF_NOTES_B supply identity, session, and note context used during validation and duplicate detection.

Usage Notes

JTF_EC_UTIL is invoked indirectly. Oracle's escalation and task forms, the standard escalation concurrent processes, and the four dependent packages call these procedures rather than exposing them to end users. Custom code should not invoke the utility validation routines directly in place of the supported public APIs; instead, callers should rely on the documented escalation and task public packages, which internally delegate to JTF_EC_UTIL. When diagnosing validation errors surfaced as JTF message-stack entries, the Add_Invalid_Argument_Msg and related routines are the source of the standardized text, making them useful reference points during troubleshooting of validate_task_contact_id failures in both 12.1.1 and 12.2.2 environments.