Search Results jtf_ih_campaigns_results_pk

Overview

The JTF_IH_CAMPAIGNS_RESULTS table is a core data structure within the Oracle E-Business Suite CRM Foundation module (JTF). Functioning as an intersection or junction table, its primary role is to establish and maintain the many-to-many relationship between customer interaction outcomes (Results) and marketing initiatives (Campaigns). In the context of Oracle EBS 12.1.1 and 12.2.2, this table is integral to the Interaction History and TeleService modules, enabling the tracking of campaign effectiveness by linking specific customer service or sales outcomes back to the originating marketing campaign. This linkage is essential for closed-loop marketing analysis, allowing organizations to measure the return on investment and impact of their campaign activities.

Key Information Stored

The table's structure is designed to store minimal, relationship-focused data, primarily consisting of foreign key references. The documented columns form the table's composite primary key and define its relationships. The RESULT_ID column stores a unique identifier that links to a specific customer interaction outcome record in the JTF_IH_RESULTS_B table. The SOURCE_CODE_ID column stores an identifier that links to a specific marketing campaign source code in the AMS_SOURCE_CODES table. The pairing of these two IDs within a single record explicitly associates a given business result with a particular campaign source, which is a child object of an Oracle Campaign.

Common Use Cases and Queries

A primary use case is generating campaign performance reports that move beyond simple response metrics to analyze tangible outcomes. For instance, a query can join this table to interaction history and campaign tables to report on the number of sales orders, service requests, or resolved cases directly attributed to a campaign. A typical analytical SQL pattern would involve joining JTF_IH_CAMPAIGNS_RESULTS to JTF_IH_RESULTS_B for outcome details and to AMS_SOURCE_CODES and related AMS_CAMPAIGNS_B tables for campaign hierarchy and details. This enables business users to segment results by campaign, campaign type, or time period. The table is also critical for data integrity during transaction processing, ensuring that when a service agent logs a result against a customer interaction linked to a campaign, the relationship is persistently stored.

Related Objects

The table's existence is defined by its relationships to two key parent tables, as documented by its foreign key constraints:

• JTF_IH_RESULTS_B: The foreign key on column RESULT_ID ensures every record in JTF_IH_CAMPAIGNS_RESULTS corresponds to a valid outcome record in the master results table.
• AMS_SOURCE_CODES: The foreign key on column SOURCE_CODE_ID ensures every campaign association points to a valid source code, which is itself linked to a parent campaign in the Oracle Marketing (AMS) schema.

The table itself is referenced by the primary key constraint JTF_IH_CAMPAIGNS_RESULTS_PK on (RESULT_ID, SOURCE_CODE_ID). This design prevents duplicate associations between the same result and campaign source code. While not listed in the provided metadata, this table is often accessed indirectly through higher-level Interaction History views and APIs within the TeleService and CRM application flows.