Results for “update_history”

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

Overview

JTF_FM_IH_LOGGER_PVT is a private PL/SQL package in the APPS schema that supports the Interaction History logging infrastructure within Oracle E-Business Suite. Its central responsibility is the persistence and lifecycle management of interaction history records — the audit trail that captures details of customer interactions (calls, visits, correspondence) processed through the Foundation module's request-processing framework. The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the calling schema rather than the definer, and it is classified as a PVT (private) API, so it is not intended as a published integration interface. The header revision (120.2, dated 2006) indicates the package has been stable across the 12.1.1 and 12.2.2 releases. Its most prominent entry point, LOG_INTERACTION_HISTORY, matches the search term "log_interaction_history" and is the procedure most likely referenced by developers investigating how interaction history data is written.

Key Procedures and Functions

• LOG_INTERACTION_HISTORY — The primary worker procedure. It records interaction history entries for a given server, accepting a commit-control flag, a server identifier, and a set of standard API OUT parameters (request ID, return status, message count, and message data). The OUT parameters follow the conventional FND_API error-handling contract, allowing callers to detect success or failure and retrieve associated messages.
• REMOVE_FROM_STATUS — Accepts a request ID and removes the corresponding entry from the status tracking tables. This supports cleanup of status rows once a request has completed or been superseded, preventing stale status records from accumulating.
• UPDATE_HISTORY — Accepts a request ID and a status value and updates the interaction history record accordingly. This procedure is used to reflect processing state transitions on existing history entries rather than creating new ones.

All three procedures are internal implementation routines; no public wrapper or documented external contract is exposed by this package.

Tables Accessed

• JTF_FM_PROCESSED — Tracks records already processed by the interaction history logging logic, guarding against duplicate processing.
• JTF_FM_REQUEST_HISTORY_ALL — The multi-org history table where interaction history entries are inserted and updated.
• JTF_FM_STATUS_ALL — Holds status information for requests; entries are removed via REMOVE_FROM_STATUS and refreshed as processing advances.
• JTF_RS_RESOURCE_EXTNS — Provides resource information used to associate history entries with the correct sales or service resource.
• DBMS_LOB — Oracle's built-in large-object package, used for reading or writing LOB columns within history records.
• DBMS_OUTPUT — Used for diagnostic messaging during processing, typically for debugging rather than production output.

All tables are accessed through APPS synonyms, consistent with standard EBS coding practice.

Usage Notes

Because JTF_FM_IH_LOGGER_PVT is a private package with no inbound references from other packages, it is invoked directly by forms, concurrent programs, or the Foundation request-processing engine rather than through a published API chain. Typical invocations occur during interaction history collection jobs, where LOG_INTERACTION_HISTORY is called for each server or batch, followed by UPDATE_HISTORY and REMOVE_FROM_STATUS as requests complete. The commit flag allows the caller to control transaction boundaries — passing FND_API.G_TRUE commits within the procedure, while G_FALSE leaves the transaction open for the caller to manage. Custom code should generally avoid calling this package directly; developers requiring interaction history functionality should use the supported public APIs. Its AUTHID CURRENT_USER declaration also means any direct caller must possess the necessary object privileges on the underlying tables.