Search Results jtf_escalation_contacts_pvt




Overview
Explore in AI Chat

Overview

APPS.JTF_EC_CONTACTS_PVT is the private PL/SQL interface for the Escalation Management feature within Oracle E-Business Suite. Its header comment identifies it as the private interface to JTF Escalation Management, used to create, update, and delete contacts associated with escalations. The package is registered in ETRM with an API classification of PVT, meaning it is intended primarily for internal consumption by other EBS components rather than as a public, supported integration API.

The package carries the documented display name "Escalation Management" and is scoped to the business entity JTA_ESCALATION under product JTF. Its header block declares the package as private scope, active lifecycle, and compatibility grade S. The embedded revision comment shows a version of 120.1 dated 2005/07/02, indicating the interface has been stable across the 12.1.1 and 12.2.2 releases, with no structural change to the private contract described in the documentation.

The functional purpose is contact administration for escalations: linking one or more contacts to an escalation record, maintaining notification and requester flags on those links, and removing links when they are no longer required. This underpins the routing and notification behaviour of the escalation, since the notify and requester flags determine who receives escalation communication and which contact is treated as the originating requester.

Key Procedures and Functions

ETRM documents three procedures on this package. The underlying comments in the source excerpt describe only the create path in detail, but the naming and structure make the purpose of the remaining two unambiguous.

  • CREATE_ESCALATION_CONTACTS — Creates one or more escalation contact records. Per the source comments, it accepts the standard API parameters (API version, message list initialization flag, commit flag) plus escalation identification, contact identification, contact type code, the escalation notify flag, and the escalation requester flag. It returns the generated escalation contact identifier and a standard return status whose value is drawn from FND_API.G_RET_STS_SUCCESS and the corresponding error and unexpected error constants.
  • UPDATE_ESCALATION_CONTACTS — Modifies existing escalation contact records, principally to change the notify or requester attributes on a contact already linked to an escalation. No parameter list is documented and none should be assumed.
  • DELETE_ESCALATION_CONTACTS — Removes escalation contact links that are no longer required, for example when a contact should stop receiving escalation notifications or when the escalation is being wound down.

All three procedures follow the standard EBS API conventions of an API version input, an optional message list initialization flag, an optional commit flag, and a return status output. The documented return status values are FND_API.G_RET_STS_SUCCESS for successful completion and the standard error and unexpected error constants for failure conditions. The private package name declared internally differs from the package name — the global constant g_pkg_name is set to 'JTF_ESCALATION_CONTACTS_PVT' while the deployed package is JTF_EC_CONTACTS_PVT — a naming inconsistency worth noting when reading error messages or message dictionary entries.

Tables Accessed

ETRM records two tables referenced through APPS synonyms:

  • JTF_TASKS_B — The base table for tasks and, by extension, escalations in the JTF task model. The package reads escalation identification data from this table to resolve the escalation number and escalation identifier supplied by the caller, and to validate that the escalation for which contacts are being created, updated, or deleted exists.
  • JTF_TASK_CONTACTS — The association table holding contact links for task and escalation records. This is the primary table written by the package: insertions for creation, column updates for modification of notify and requester flags, and deletions for removal of contact links.

Because access is through APPS synonyms, the package operates on the same physical objects regardless of the schema under which it is executed, provided the standard APPS synonym configuration is in place. All access is conveyed via the ORACLE APPS account.

Usage Notes

As a private interface, JTF_EC_CONTACTS_PVT is not intended for direct invocation by customer extensions. ETRM records that it is referenced by one other package, which is consistent with the private-to-public layering convention in EBS: a public wrapper or a higher-level escalation management package contains the validation and security logic and delegates the actual contact persistence work to this private package.

Typical invocation occurs from escalation management forms and from internal escalation processing where a contact must be attached to or detached from an escalation. Concurrent programs and workflows that generate or service escalations may also reach this package indirectly through its public caller. Custom code should not call the package directly because the private contract may change between releases and no backward-compatibility guarantee applies to private APIs. Where escalation contact functionality must be extended, the supported approach is to call the public API interface or the escalation management public package, not this private implementation.

The package has no direct relationship to the user search term "safe trans transport contact number"; no transport or safe-transit functionality is documented for this object, and the "contact" element of the search corresponds only to escalation contact records maintained in JTF_TASK_CONTACTS.