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.
- SCORE_ID — the primary key (AMS_DM_SCORES_ALL_B_PK) and also the sole column of unique index AMS_DM_SCORES_ALL_B_U1. It is the surrogate key and the primary business-key candidate that uniquely identifies each scoring instance.
- MODEL_ID — foreign key to AMS_DM_MODELS_ALL_B, identifying the data-mining model applied during the scoring run.
- USER_STATUS_ID — foreign key to AMS_USER_STATUSES_B, capturing the user-defined status of the scoring instance.
- CUSTOM_SETUP_ID — foreign key to AMS_CUSTOM_SETUPS_B, linking the run to a stored configuration profile.
- STATUS_CODE and STATUS_DATE — the current processing state of the scoring instance and the timestamp of the last status transition.
- OWNER_USER_ID — the user who owns the scoring instance.
- SCHEDULED_DATE and SCHEDULED_TIMEZONE_ID — when the scoring run is scheduled and in which time zone.
- SCORE_DATE and EXPIRATION_DATE — the effective date of scoring results and the date after which those results expire.
- TOTAL_RECORDS, TOTAL_POSITIVES, MIN_RECORDS, MAX_RECORDS — aggregate statistics describing how many records were scored and the selection bounds applied.
- EVERY_NTH_ROW and PCT_RANDOM — sampling parameters controlling row selection behavior.
- ROW_SELECTION_TYPE — the strategy used to select records for the scoring population.
- RESULTS_FLAG and LOGS_FLAG — indicators governing whether detailed results and logs are retained.
- ORG_ID and SECURITY_GROUP_ID — multi-org and security-group partitioning columns (SECURITY_GROUP_ID references FND_SECURITY_GROUPS).
- WF_ITEMKEY — the workflow item key, enabling integration with Oracle Workflow for asynchronous scoring processes.
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.
-
Container for capturing statistics of a scoring instance.
-
Container for capturing statistics of a scoring instance.
-
View: AMS_DS_SCORES_V 12.2.2
APPS.AMS_DS_SCORES_V·↳ AMS_DM_MODELS_ALL_B·↳ AMS_DM_MODELS_ALL_TL·↳ AMS_DM_SCORES_ALL_B·Explore AMS module →
-
View: AMS_DS_SCORES_V 12.1.1
APPS.AMS_DS_SCORES_V·↳ AMS_DM_MODELS_ALL_B·↳ AMS_DM_MODELS_ALL_TL·↳ AMS_DM_SCORES_ALL_B·Explore AMS module →
-
View: AMS_DM_SCORE_HISTORY_V 12.1.1
View to be used to identify the score and the model used for a scoring run for a specific party.
APPS.AMS_DM_SCORE_HISTORY_V·↳ AMS_DM_MODELS_ALL_B·↳ AMS_DM_MODELS_ALL_TL·↳ AMS_DM_SCORES_ALL_B·Explore AMS module →
-
View: AMS_DM_SCORE_HISTORY_V 12.2.2
View to be used to identify the score and the model used for a scoring run for a specific party.
APPS.AMS_DM_SCORE_HISTORY_V·↳ AMS_DM_MODELS_ALL_B·↳ AMS_DM_MODELS_ALL_TL·↳ AMS_DM_SCORES_ALL_B·Explore AMS module →
-
Container for the summarized percentile results of a scored population.
-
View: AMS_DM_SCORES_VL 12.2.2
Multi-lingual view for data mining scoring runs.
APPS.AMS_DM_SCORES_VL·↳ AMS_DM_SCORES_ALL_B·↳ AMS_DM_SCORES_ALL_TL·Explore AMS module →
-
Container for the costs and revenues associated with an Optimal Targeting Chart for a Scoring Run.
-
Container for the costs and revenues associated with an Optimal Targeting Chart for a Scoring Run.
-
Container for the summarized percentile results of a scored population.
-
View: AMS_DM_SCORES_VL 12.1.1
Multi-lingual view for data mining scoring runs.
APPS.AMS_DM_SCORES_VL·↳ AMS_DM_SCORES_ALL_B·↳ AMS_DM_SCORES_ALL_TL·Explore AMS module →
-
VIEW: APPS.AMS_DS_SCORES_V 12.2.2
-
VIEW: APPS.AMS_DS_SCORES_V 12.1.1
-
View: AMS_DM_SCORES_V 12.2.2
View of data mining scoring runs with denormalized reference objects.
APPS.AMS_DM_SCORES_V·↳ AMS_DM_MODELS_ALL_B·↳ AMS_DM_MODELS_ALL_TL·↳ AMS_DM_SCORES_ALL_B·Explore AMS module →
-
VIEW: APPS.AMS_DM_SCORES_VL 12.1.1
-
VIEW: APPS.AMS_DM_SCORES_VL 12.2.2