Search Results ams_dm_scores_all_b

Overview

The AMS_DM_SCORES_ALL_B table is a core data structure within the Oracle E-Business Suite Marketing (AMS) module, specifically for the Data Mining (DM) functionality. It serves as the primary container for capturing and storing the statistical metadata and execution details of a scoring instance. In the context of Oracle Marketing's analytical capabilities, a scoring instance represents a specific run of a predictive model against a target population to generate propensity scores, segment classifications, or other predictive metrics. This table is a base table, typically holding transactional and system-level data, and is central to managing the lifecycle and results of data mining scoring operations in releases 12.1.1 and 12.2.2.

Key Information Stored

While the full column list is not detailed in the provided metadata, the defined constraints reveal critical fields. The primary key is SCORE_ID, a unique identifier for each scoring instance. Essential foreign key relationships indicate the table stores MODEL_ID, linking the score to its source predictive model in AMS_DM_MODELS_ALL_B. The USER_STATUS_ID column connects to AMS_USER_STATUSES_B, tracking the workflow status of the scoring job. The CUSTOM_SETUP_ID references AMS_CUSTOM_SETUPS_B, suggesting the table stores configuration parameters specific to the scoring run. Other typical columns in such a table would include creation dates, last update dates, created by, last updated by, and contextual information about the scored population or data source.

Common Use Cases and Queries

This table is primarily accessed for auditing, reporting, and managing scoring jobs. Common operational queries include retrieving all scores for a specific model to analyze performance over time, or finding scores in a particular status for batch processing. A typical reporting query might join this table with its descriptive TL (translation) table and the model table to generate a user-friendly list.

SELECT sc.SCORE_ID, sc.CREATION_DATE, mod.MODEL_NAME, st.MEANING AS STATUS
FROM AMS.AMS_DM_SCORES_ALL_B sc,
     AMS.AMS_DM_MODELS_ALL_B mod,
     AMS.AMS_USER_STATUSES_TL st
WHERE sc.MODEL_ID = mod.MODEL_ID
  AND sc.USER_STATUS_ID = st.STATUS_ID
  AND st.LANGUAGE = USERENV('LANG')
ORDER BY sc.CREATION_DATE DESC;

Another critical use case is data lineage and cleanup, where administrators query dependencies before archiving or purging old model scores based on their SCORE_ID.

Related Objects

The AMS_DM_SCORES_ALL_B table has extensive relationships within the Marketing schema, acting as a hub for scoring data. Key related objects include:

• AMS_DM_MODELS_ALL_B: The source model for the score (via MODEL_ID).
• AMS_DM_SCORE_RESULTS & AMS_DM_SCORE_PCT_RESULTS: Child tables that store the detailed individual record scores and percentile results, respectively.
• AMS_DM_SCORE_LISTS: Links scores to output marketing lists.
• AMS_DM_OPT_TGT_METRICS: Likely stores optimization target metrics calculated for the score.
• AMS_DM_SCORES_ALL_TL: The translation table providing descriptive names and notes in multiple languages.
• AMS_DM_SOURCE & AMS_LIST_SELECT_ACTIONS: Reference the SCORE_ID to track the score as a data source or as part of a list generation action.