Results for “ams_dm_scores_all_b”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMS_DM_SCORES_ALL_B is a core base table in the Oracle E-Business Suite Marketing (AMS) module. It functions as the container for capturing statistics of a scoring instance generated by Oracle Marketing's data-mining and predictive scoring engine. In EBS 12.1.1 and 12.2.2, the table resides in the AMS schema and is owned by the Oracle Marketing product family, which drives campaign targeting, list generation, and model-based customer selection.

A scoring instance represents a single execution of a data-mining model against a population of records. The table stores the parameters governing that execution (row selection strategy, sampling rates, thresholds), the model being applied, scheduling information, and aggregate result statistics such as total records scored and total positives identified. Downstream tables consume the SCORE_ID to relate individual scored records, percentage distributions, targets, and metrics back to the governing scoring run.

Based on the foreign-key topology mined from the ETRM metadata, this table exhibits a hub-leaning Data Vault classification. It anchors multiple dependent and referencing entities around its SCORE_ID surrogate key, which is consistent with the role of a central business hub. This classification is a modeling suggestion derived heuristically from the FK structure rather than a formally declared Data Vault designation.

Key Information Stored

The table contains 46 documented columns. The most significant are summarized below.

Common Use Cases and Queries

Typical reporting scenarios include monitoring the health of scheduled scoring runs, auditing model performance over time, and reconciling scored populations against downstream result sets.

To list active scoring instances with their model and status:

  • SELECT s.SCORE_ID, s.STATUS_CODE, s.SCORE_DATE, m.MODEL_NAME FROM AMS.AMS_DM_SCORES_ALL_B s JOIN AMS.AMS_DM_MODELS_ALL_B m ON s.MODEL_ID = m.MODEL_ID WHERE s.STATUS_CODE = 'ACTIVE';

To examine aggregate results for a given run:

  • SELECT TOTAL_RECORDS, TOTAL_POSITIVES, SCORE_DATE FROM AMS.AMS_DM_SCORES_ALL_B WHERE SCORE_ID = :p_score_id;

To retrieve translated score names, join to the TL table:

  • SELECT b.SCORE_ID, t.SCORE_NAME FROM AMS.AMS_DM_SCORES_ALL_B b JOIN AMS.AMS_DM_SCORES_ALL_TL t ON b.SCORE_ID = t.SCORE_ID WHERE t.LANGUAGE = USERENV('LANG');

Related Objects

The following tables participate in the primary referential relationships with AMS_DM_SCORES_ALL_B, joined on SCORE_ID unless otherwise noted.

  • AMS_DM_MODELS_ALL_B — referenced via MODEL_ID; defines the model applied.
  • AMS_DM_MODELS_ALL_B — the base model catalog.
  • AMS_DM_SCORES_ALL_TL — translated score names and descriptions, joined on SCORE_ID.
  • AMS_DM_SCORE_RESULTS — individual record-level scoring outcomes, joined on SCORE_ID.
  • AMS_DM_SCORE_PCT_RESULTS — percentage distribution results, joined on SCORE_ID.
  • AMS_DM_SCORE_LISTS — associated list definitions, joined on SCORE_ID.
  • AMS_DM_OPT_TGT_METRICS — optimization target metrics, joined on SCORE_ID.
  • AMS_DM_SOURCE — source records referencing the scoring run via USED_FOR_OBJECT_ID.
  • AMS_LIST_SELECT_ACTIONS — list selection actions referencing the run via ACTION_USED_BY_ID.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for security partitioning.