Search Results jtf_ih_results_b




Overview
Explore in AI Chat

Overview

The JTF_IH_RESULTS_B table is a core data object within the Oracle E-Business Suite CRM Foundation module (JTF). It functions as the master repository for interaction and activity result codes. In the context of Oracle EBS 12.1.1 and 12.2.2, this table stores the standardized outcomes or conclusions of customer interactions managed through the Interaction History and related CRM applications. These results are critical for categorizing the purpose and outcome of customer engagements, such as a sale, a service request, or a callback scheduled. The table's role is to provide a centralized, normalized list of result types that can be consistently applied across various CRM transactional entities, ensuring data integrity and enabling meaningful reporting on interaction outcomes.

Key Information Stored

While the provided ETRM excerpt does not list specific columns beyond the primary key, the structure of Oracle EBS tables allows for reliable inference of core attributes. The central column is RESULT_ID (NUMBER), which serves as the unique primary key identifier for each result code. Standard Oracle Application Object Library columns are also present, including CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for auditing. A critical attribute is the ENABLED_FLAG (typically VARCHAR2(1)), which controls whether a result code is available for selection. The table stores the base, non-translatable data, while user-facing names and descriptions are stored in the related translation table, JTF_IH_RESULTS_TL, keyed by RESULT_ID and LANGUAGE.

Common Use Cases and Queries

A primary use case is populating lists of values (LOVs) in CRM application forms where users select an outcome for an activity or interaction. Administrators use this table to maintain the catalog of valid results, enabling or disabling codes as business processes evolve. For reporting, analysts frequently join this table to transactional data to summarize outcomes. A common query pattern involves filtering for active results used in specific interactions:

  • SELECT res.RESULT_ID, tl.RESULT_NAME FROM JTF_IH_RESULTS_B res, JTF_IH_RESULTS_TL tl, JTF_IH_INTERACTIONS i WHERE res.RESULT_ID = tl.RESULT_ID AND tl.LANGUAGE = USERENV('LANG') AND res.ENABLED_FLAG = 'Y' AND i.RESULT_ID = res.RESULT_ID AND i.INTERACTION_ID = :p_interaction_id;

Another key scenario is data validation, ensuring transactional records reference a valid RESULT_ID from this master table.

Related Objects

The JTF_IH_RESULTS_B table is a central reference table with numerous foreign key relationships, as documented in the ETRM. The primary key (RESULT_ID) is referenced by the following transactional and setup tables:

These relationships illustrate that JTF_IH_RESULTS_B is integral to the data model of the Interaction History module, providing a unified result code across activities, interactions, campaigns, and wrap-ups.