Results for “jtf_request_history_pvt”

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

Overview

The APPS.JTF_REQUEST_HISTORY_PVT package is a private PL/SQL API within the Oracle E-Business Suite Customer Relationship Management (CRM) and TeleService Foundation (JTF) schema family. Its role is to manage the creation and persistence of request history records, which track the lifecycle and status transitions of service requests, fulfillment requests, and related customer interactions processed by the CRM fulfillment engine. The package is classified as a Private (PVT) API, meaning it is intended for internal consumption by other Oracle applications and framework components rather than as a directly callable public interface for customer extensions. It supports the historical audit trail that allows organizations to reconstruct what happened to a given request, when it occurred, and which fulfillment activities were performed against it.

Key Procedures and Functions

The ETRM metadata documents a single program unit within this package:

• CREATE_REQUEST_HISTORY — This procedure inserts a new history record for a request, capturing the event or state change associated with the request handling process. It serves as the internal write mechanism through which history entries are generated when the fulfillment framework processes or transitions a request. As a private procedure, it is not documented with a public parameter contract and should not be called directly by custom code; callers are expected to reach it indirectly through the public fulfillment APIs.

Exact parameter lists are not published in the ETRM extract, and the procedure should be treated as an internal implementation detail subject to change between release levels.

Tables Accessed

The package operates against three objects, accessed through APPS synonyms under the JTF fulfillment schema:

• JTF_FM_REQUEST_HISTORY_ALL — The primary history table. The CREATE_REQUEST_HISTORY procedure writes a new row into this table, recording the event details for the request being tracked. The _ALL suffix indicates the table is not partitioned by a per-organization or multilingual view pattern in the conventional sense, and it stores the full set of historical entries.
• JTF_FM_REQUESTHISTID_S — A sequence used to generate unique primary key identifiers for each new history record inserted into the history table.
• DUAL — The standard Oracle dictionary table, referenced for simple scalar evaluation, commonly used to retrieve the next sequence value in a SELECT ... FROM DUAL construct.

Usage Notes

JTF_REQUEST_HISTORY_PVT is not intended for direct invocation by end users, forms, or concurrent programs. Instead, it is invoked internally by APPS.JTF_FULFILLMENT_PUB, the public fulfillment API package that the metadata identifies as the sole referencing object. This dependency indicates that the request history mechanism is tightly coupled to the fulfillment processing flow: whenever the public fulfillment API performs an action that warrants a history entry, it delegates to this private package to persist the record.

Because the package is classified as PVT and is referenced by only one public package, customizations and extensions should integrate through JTF_FULFILLMENT_PUB rather than by calling JTF_REQUEST_HISTORY_PVT directly. Direct calls bypass the validation and business logic enforced at the public layer and risk data inconsistency or breakage during patching. The behavior described here applies to Oracle EBS 12.1.1 and 12.2.2, where the object retains a VALID status in the APPS schema.