Search Results ams_dm_score_lists




Overview
Explore in AI Chat

Overview

The AMS_DM_SCORE_LISTS table is a core data structure within the Oracle E-Business Suite (EBS) Marketing (AMS) module, specifically for the Data Mining (DM) functionality. As documented in the ETRM, it serves as a container for the association between a scoring run and generated lists. In practical terms, this table is the junction or intersection table that links the results of a predictive model scoring run (which ranks or scores customers/prospects) to the actual marketing lists generated from those scores. Its role is to maintain the integrity of the relationship between the analytical scoring process and the operational marketing execution, enabling traceability from a generated target list back to the specific scoring run that produced it.

Key Information Stored

The table's primary purpose is to store foreign key relationships. Its documented primary key is SCORE_LIST_ID, which uniquely identifies each association record. The two critical foreign key columns define its core relationships. The SCORE_ID column references a specific scoring run in the AMS_DM_SCORES_ALL_B table, identifying the predictive model execution instance. The LIST_HEADER_ID column references a specific generated marketing list in the AMS_LIST_HEADERS_ALL table. By storing these links, the table answers the fundamental question: "Which marketing list was created from which data mining score run?"

Common Use Cases and Queries

A primary use case is auditing and impact analysis. For instance, if a scoring model is found to be flawed, administrators can query this table to identify all marketing lists generated from that model to assess the scope of impact. Common reporting queries involve joining to related tables to produce meaningful reports. A typical SQL pattern retrieves list details for a given score run:

  • SELECT sl.score_list_id, lh.list_header_id, lh.list_name, lh.creation_date FROM ams_dm_score_lists sl, ams_list_headers_all lh WHERE sl.list_header_id = lh.list_header_id AND sl.score_id = :p_score_id;

Conversely, to trace a list's origin, a query would join to the scores table to retrieve details about the predictive model and run parameters used.

Related Objects

The table is centrally connected to two major entities in the AMS schema via its documented foreign keys.

  • AMS_DM_SCORES_ALL_B: This table holds the master records for data mining scoring runs. The relationship is defined by the foreign key constraint on AMS_DM_SCORE_LISTS.SCORE_ID referencing this table. It provides context on the model, run date, and parameters used to generate the scores.
  • AMS_LIST_HEADERS_ALL: This table stores the header information for marketing lists. The relationship is defined by the foreign key constraint on AMS_DM_SCORE_LISTS.LIST_HEADER_ID referencing this table. It provides the operational details of the generated target list, such as its name, type, and status.

These relationships make AMS_DM_SCORE_LISTS a critical linchpin for data flow between the analytical (Data Mining) and operational (List Management) subsystems of Oracle Marketing.