Search Results ams_dm_source




Overview
Explore in AI Chat

Overview

The AMS_DM_SOURCE table is a core data structure within the Oracle E-Business Suite (EBS) Marketing (AMS) module, specifically designed to support data mining activities. It functions as a central repository for the parties—typically customers, prospects, or contacts—who are subjects of data mining operations. Its primary role is to serve as a container that links these parties to either a data mining model building process or a scoring process. By storing both the source party identifiers and the resulting target values or scores, this table enables the integration of predictive analytics into marketing campaigns, facilitating targeted customer segmentation and personalized outreach based on modeled behavior.

Key Information Stored

The table's structure is designed to uniquely identify a party within the context of a specific data mining activity. The critical columns include:

  • SOURCE_ID: The primary key column, uniquely identifying each record in this container table.
  • ARC_USED_FOR_OBJECT: A column that, in conjunction with USED_FOR_OBJECT_ID, helps define the type of data mining object (e.g., model or score) the record is associated with.
  • USED_FOR_OBJECT_ID: A foreign key that links the party record to a specific data mining model or score. This is the pivotal column connecting the source data to the analytical results.
  • PARTY_ID: The identifier for the party (customer, contact, etc.) from the Trading Community Architecture (TCA) who is the subject of the mining or scoring activity.

Common Use Cases and Queries

This table is essential for retrieving the list of parties used to build a predictive model or to generate scores for a target population. A common reporting use case involves analyzing the scored output for a campaign. For instance, to retrieve all parties and their associated scores from a specific scoring run, a developer might join AMS_DM_SOURCE to the scores table. A typical query pattern would be:

SELECT s.party_id, sc.score_value
FROM ams_dm_source s,
ams_dm_scores_all_b sc
WHERE s.used_for_object_id = sc.score_id
AND s.arc_used_for_object = 'SCORE'
AND sc.campaign_id = :p_campaign_id;

Another critical use case is auditing model training data, where queries join AMS_DM_SOURCE to AMS_DM_MODELS_ALL_B to list all parties whose historical data contributed to a specific model's creation.

Related Objects

The AMS_DM_SOURCE table maintains defined foreign key relationships with two primary data mining objects, both using the USED_FOR_OBJECT_ID column as the join condition:

  • AMS_DM_MODELS_ALL_B: This relationship links source party data to a specific data mining model. Records in AMS_DM_SOURCE where the context is model building will reference a primary key in this table.
  • AMS_DM_SCORES_ALL_B: This relationship links source party data to generated scoring results. Records used for scoring operations will reference a primary key in this scores table.

These relationships underscore the table's role as the junction between the raw party data from TCA and the sophisticated analytical outputs generated by the Oracle Data Mining engine within EBS Marketing.