Results for “total_interactions”

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 body in the Oracle E-Business Suite Applications (APPS) schema that provides the logging and history-maintenance layer for the Interaction History (IH) framework used by the Foundation/Telephony (JTF) modules. Its role is to persist the outcome of outbound interaction attempts — for example, telephony or messaging requests dispatched through the interaction broker — by writing records into the interaction history tables and keeping the associated request/status queues synchronized. The package encapsulates the private ("PVT") logic that determines outcome identifiers and success or failure result codes, so that the public Interaction History APIs do not have to resolve this setup data themselves.

The package header declares a package-level counter, TOTAL_INTERACTIONS, initialized to 1000. This constant controls the batch size used when the logger processes interactions, allowing the caller to cap the volume of history rows handled in a single unit of work. The body also exposes internal helper functions that return configuration values from JTF_FM_SERVICE: an outcome ID (defaulting to the "Req Proc" outcome when none is configured), a "Not Sent" failure result (default 9), and a "Sent" success result (default 10). These fallbacks ensure logging proceeds even when service-specific setup rows are absent.

Key Procedures and Functions

• LOG_INTERACTION_HISTORY — The core logging entry point. It records the outcome of an interaction attempt into the interaction history structures, applying the configured outcome and result identifiers resolved by the package's internal helper functions. This is the procedure most directly associated with the user's search term, "total_interactions," since it operates within the batch limit defined by the package variable of that name.
• UPDATE_HISTORY — Updates existing interaction history records, typically to reflect a change in status or result code after the initial logging. It maintains the accuracy of the history rows as the request lifecycle advances.
• REMOVE_FROM_STATUS — Removes entries from the status tracking structures, clearing records once processing completes so that active status queues remain lean and reflect only in-flight work.

A troubleshooting helper, DISPLAY, is also present in the body for debugging CLOB-based content and is not part of the documented public interface.

Tables Accessed

• JTF_FM_PROCESSED — Tracks interaction requests that have already been processed, preventing duplicate logging.
• JTF_FM_REQUEST_HISTORY_ALL — The principal history store into which LOG_INTERACTION_HISTORY and UPDATE_HISTORY insert and update interaction outcome records.
• JTF_FM_STATUS_ALL — The status table from which REMOVE_FROM_STATUS deletes completed entries.
• JTF_RS_RESOURCE_EXTNS — Resource extension data used to identify the agent or resource associated with an interaction.
• JTF_FM_SERVICE — Read by the helper functions to obtain configured outcome and result identifiers.
• DBMS_LOB and DBMS_OUTPUT — Standard Oracle packages used for large-object handling and diagnostic output.

Usage Notes

JTF_FM_IH_LOGGER_PVT is a private package and is not intended to be called directly from forms or concurrent programs. It is invoked internally by the public Interaction History broker and logger APIs within the JTF Foundation layer, which in turn are driven by telephony and interaction-center integrations. Because the ETRM metadata records zero packages referencing it, callers reach it indirectly through the owning framework rather than through explicit dependencies. Customizations should not call this package directly; instead, developers should use the supported public IH APIs, which route through JTF_FM_IH_LOGGER_PVT to perform history logging and status cleanup.