Search Results ams_dm_opt_tgt_metrics




Overview
Explore in AI Chat

Overview

The AMS_DM_OPT_TGT_METRICS table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Marketing (AMS) module. It functions as a repository for the financial metrics generated during a predictive analytics process known as Optimal Targeting. This table stores the calculated costs and revenues associated with different segments of a target audience, enabling marketers to determine the most profitable audience segments for a campaign based on a scoring model's predictions. Its role is to provide the quantitative foundation for data-driven marketing decisions by linking campaign schedules and scoring runs to their associated financial outcomes.

Key Information Stored

The table's primary purpose is to store the financial results of an Optimal Targeting analysis. While the full column list is not detailed in the provided metadata, the documented keys and relationships define its critical structure. The primary identifier is the OPT_TGT_METRIC_ID. The table is fundamentally linked to two key entities: a scoring run and a campaign schedule. The SCORE_ID column foreign key to AMS_DM_SCORES_ALL_B associates the metrics with a specific predictive model scoring execution. The SCHEDULE_ID column foreign key to AMS_CAMPAIGN_SCHEDULES_B ties the financial data to a specific planned marketing campaign. The table's description as a "container for costs and revenues" implies it holds columns for metrics such as cumulative revenue, cumulative cost, profit, return on investment (ROI), and potentially the audience percentile or segment range to which these metrics apply.

Common Use Cases and Queries

The primary use case is generating and analyzing the Optimal Targeting Chart, a visual tool that helps marketers balance campaign reach against profitability. Common operational and reporting activities include retrieving all financial metrics for a specific campaign schedule to evaluate its projected performance, or comparing the cost/revenue curves from multiple scoring models to select the best one. A typical analytical query would join this table to campaign and score information to populate a management report.

  • Sample Query Pattern: Retrieving optimal targeting metrics for a specific campaign schedule, ordered by audience segment. 
    SELECT metric.*
FROM ams_dm_opt_tgt_metrics metric,
     ams_dm_scores_all_b score
WHERE metric.schedule_id = :p_schedule_id
AND metric.score_id = score.score_id
ORDER BY [segment_rank_column];
  • Reporting Use Case: A report that displays the cumulative revenue, cost, and profit for each decile of the target audience, enabling identification of the most profitable cutoff point for campaign execution.

Related Objects

The AMS_DM_OPT_TGT_METRICS table exists within a defined relational schema, primarily interacting with objects in the Marketing module. The documented foreign key relationships are as follows:

  • AMS_DM_SCORES_ALL_B: Linked via SCORE_ID. This table stores the master records for predictive scoring runs, providing the model and context for the calculated metrics.
  • AMS_CAMPAIGN_SCHEDULES_B: Linked via SCHEDULE_ID. This table defines the campaign schedule for which the optimal targeting analysis is being performed, connecting financial projections to a concrete marketing plan.

These relationships ensure data integrity and allow for comprehensive joins to enrich metric data with descriptive information from the related score and campaign schedule entities.