Search Results jtf_ih_campaign_result_reasons




Overview
Explore in AI Chat

Overview

The table JTF_IH_CAMPAIGN_RESULT_REASONS is a core intersection table within the Oracle E-Business Suite CRM Foundation (JTF) module. Its primary function is to establish and manage valid combinations of result and reason codes for specific Oracle Marketing campaigns. This table acts as a critical junction, enforcing business rules by defining which reasons can be logically associated with which outcomes (results) for a given campaign source. By centralizing these relationships, it ensures data integrity and consistency in campaign activity tracking and analysis across the application, particularly within the Interaction History and TeleService modules.

Key Information Stored

The table's structure is defined by a composite primary key, which uniquely identifies each valid pairing. The key columns are SOURCE_CODE_ID, REASON_ID, and RESULT_ID. The SOURCE_CODE_ID links to a specific marketing campaign source code, effectively scoping the valid pairings to a particular campaign. The REASON_ID is a foreign key to the JTF_IH_REASONS_B table, which stores the master list of descriptive reason codes (e.g., "Not Interested," "Call Back Requested"). The RESULT_ID is a foreign key to the JTF_IH_RESULTS_B table, which stores the master list of outcome or result codes (e.g., "Contacted," "No Answer," "Sale"). The table itself does not store transactional data but rather the permissible definitions used by transactional tables when recording campaign interactions.

Common Use Cases and Queries

This table is essential for configuration and reporting. Administrators use it to set up the allowed reason-result combinations for a campaign during implementation. A common operational query retrieves all valid reasons for a specific result within a campaign, which populates LOVs in the user interface when agents log interactions. For reporting, analysts join this table to transactional interaction history data to generate detailed campaign performance reports that include granular outcome analysis. A typical query pattern is:

  • SELECT r.result_code, rs.reason_code FROM jtf_ih_campaign_result_reasons crr, jtf_ih_results_b r, jtf_ih_reasons_b rs, ams_source_codes sc WHERE crr.result_id = r.result_id AND crr.reason_id = rs.reason_id AND crr.source_code_id = sc.source_code_id AND sc.name = '&CAMPAIGN_NAME';

Related Objects

The table maintains documented foreign key relationships with three primary master tables, which are fundamental to its role as an intersection entity:

  • AMS_SOURCE_CODES: Links via SOURCE_CODE_ID. This ties the valid pairings to a specific marketing campaign source.
  • JTF_IH_REASONS_B: Links via REASON_ID. This references the master table of all defined reason codes.
  • JTF_IH_RESULTS_B: Links via RESULT_ID. This references the master table of all defined outcome or result codes.

Transactional tables, such as those recording agent interactions (e.g., JTF_IH_ACTIVITIES), will typically store a RESULT_ID and REASON_ID that must conform to a valid combination defined in this table for the relevant campaign.