Search Results jtf_ih_interactions




Overview
Explore in AI Chat

Overview

The JTF_IH_INTERACTIONS table is a core data object within the Oracle E-Business Suite CRM Foundation (JTF) module, specifically designed for the Interaction History (IH) component. It serves as the master transactional table for recording all customer interactions. As defined in the ETRM, an interaction represents a contact point between a customer (or potential customer) and a single human or automated agent. This table enables the systematic tracking, timing, and analysis of customer engagements by storing critical metadata about each interaction's outcome, result, associated resource, and related entities. Its central role is to provide a unified historical record of customer touchpoints across various channels, which is fundamental for customer service, marketing, and sales analytics within Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's primary key is INTERACTION_ID, which uniquely identifies each interaction record. As indicated by the foreign key relationships, the table stores essential relational pointers to other master data entities. Key foreign key columns include PARTY_ID (linking to HZ_PARTIES to identify the customer), RESOURCE_ID (linking to JTF_RS_RESOURCE_EXTNS to identify the agent or handler), and OUTCOME_ID, REASON_ID, and RESULT_ID (linking to their respective lookup tables JTF_IH_OUTCOMES_B, JTF_IH_REASONS_B, and JTF_IH_RESULTS_B for categorizing the interaction's disposition). Additional columns link to scripts (SCRIPT_ID), campaign source codes (SOURCE_CODE_ID), and the originating application (HANDLER_ID via FND_APPLICATION). The table also supports linking multiple related interactions through the INTERACTION_INTERS_ID column, which references the JTF_IH_INTERACTION_INTERS table.

Common Use Cases and Queries

A primary use case is generating interaction history reports for a specific customer or agent. For example, a query to retrieve all interactions for a customer party, including outcome and agent details, is common for service history analysis. Another critical use case is linking service interactions to sales opportunities or marketing campaigns, leveraging the relationships defined with tables like AML_INTERACTION_LEADS and JTF_IH_INTERACTIONS_CAMPAIGNS. Data from this table is also essential for calculating key performance indicators (KPIs) like average handle time or first-contact resolution rates, which typically involve joining with the JTF_IH_ACTIVITIES table for detailed timing data. A basic reporting query pattern would involve joining JTF_IH_INTERACTIONS with HZ_PARTIES, JTF_RS_RESOURCE_EXTNS, and the relevant outcome/result lookup tables.

Related Objects

As documented in the ETRM metadata, JTF_IH_INTERACTIONS has extensive relationships with other objects. It is a parent table to several key transactional entities, including:

  • AML_INTERACTION_LEADS: For linking interactions to sales leads.
  • JTF_IH_ACTIVITIES: For storing detailed activity timings within an interaction.
  • JTF_IH_INTERACTIONS_CAMPAIGNS: For associating interactions with marketing campaigns.
  • JTF_IH_INTERACTION_INTERS: For defining relationships between multiple interactions (e.g., a call that generates a follow-up task).
Furthermore, it references major master data tables as foreign keys, such as HZ_PARTIES (TCA), JTF_RS_RESOURCE_EXTNS (Resources), and the standard lookup tables for outcomes, reasons, and results (JTF_IH_OUTCOMES_B, JTF_IH_REASONS_B, JTF_IH_RESULTS_B). This network of relationships underscores its position as the central hub for interaction data flow within the CRM foundation.