Search Results jtf_ih_outcomes_campaigns




Overview
Explore in AI Chat

Overview

The JTF_IH_OUTCOMES_CAMPAIGNS table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the CRM Foundation module (JTF). It functions as an intersection or junction table within the Interaction History (IH) architecture. Its primary role is to establish and manage the many-to-many relationships between customer interaction outcomes (stored in JTF_IH_OUTCOMES_B) and specific marketing campaigns (represented by source codes from AMS_SOURCE_CODES). This table is essential for linking the operational results of customer service or sales interactions directly to the marketing initiatives that prompted them, enabling closed-loop campaign analysis and performance tracking.

Key Information Stored

The table's structure is intentionally simple, designed solely to maintain the relationship between two key entities. The critical columns are its two foreign key columns, which together form the table's primary key (JTF_IH_OUTCOMES_CAMPAIGNS_PK). The OUTCOME_ID column references the unique identifier (OUTCOME_ID) from the JTF_IH_OUTCOMES_B table, which stores the definition of the interaction outcome, such as "Sale Made," "Complaint Logged," or "Lead Generated." The SOURCE_CODE_ID column references the SOURCE_CODE_ID from the AMS_SOURCE_CODES table, which is the master list for campaign codes within the Oracle Marketing module. Each record in this intersection table signifies that a particular outcome is applicable to or can be assigned from interactions associated with a specific campaign.

Common Use Cases and Queries

This table is central to reporting and analytics that measure campaign effectiveness by tying interaction results back to their source. A common use case is generating a report showing all outcomes logged for a specific marketing campaign to calculate conversion rates or customer sentiment. Another scenario involves validating data during interaction entry, ensuring selected outcomes are valid for the campaign context. A typical analytical query would join this table to outcome descriptions and campaign details:

  • Sample Query: SELECT camp.source_code, out.name outcome_name FROM jtf_ih_outcomes_campaigns joc, ams_source_codes camp, jtf_ih_outcomes_b out WHERE joc.source_code_id = camp.source_code_id AND joc.outcome_id = out.outcome_id AND camp.source_code = 'CAMPAIGN_2024_Q1';
  • Reporting Use Case: Analyzing the distribution of interaction outcomes (e.g., resolved, escalated) across different campaign channels to optimize marketing spend and agent training.

Related Objects

JTF_IH_OUTCOMES_CAMPAIGNS sits at the intersection of two primary EBS data models: Interaction History and Marketing. Its existence is defined by its foreign key relationships. The parent table JTF_IH_OUTCOMES_B provides the master list of all possible interaction outcomes. The other parent table, AMS_SOURCE_CODES, provides the valid list of marketing campaign identifiers from the Oracle Marketing module. This table is inherently referenced by any process or report that needs to filter outcomes by campaign or attribute campaign performance to specific interaction results. It is a foundational piece for integrated CRM reporting within Oracle EBS.