Results for “ams_dm_score_lists”

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

Overview

AMS_DM_SCORE_LISTS is a transactional table in the AMS (Marketing) schema of Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. The table functions as the container for the association between a scoring run and the generic lists produced or affected by that scoring operation. In practical terms, each row links a scored model result to a specific list header, allowing Oracle Marketing to track which lists were scored by which scoring execution and to schedule or reuse that linkage across scoring cycles.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is modeled as a link table. That classification is a suggestion rather than a documented attribute: the table resolves a many-to-many association between the scoring entity and the list entity, which is the characteristic role of a link in Data Vault modeling. It does not carry descriptive business attributes of its own beyond context and audit columns, reinforcing its identity as an associative structure.

Key Information Stored

The table is defined with 11 documented columns. The most significant of these are:

• SCORE_LIST_ID — the surrogate primary key, enforced by the unique constraint AMS_DM_SCORE_LISTS_PK and the unique index AMS_DM_SCORE_LISTS_U1. This is the column users most commonly search on and the join key into dependent objects.
• SCORE_ID — foreign key to AMS_DM_SCORES_ALL_B, identifying the scoring run or score definition to which the list association belongs.
• LIST_HEADER_ID — foreign key to AMS_LIST_HEADERS_ALL, identifying the generic list header associated with the scoring run.
• SCHEDULE_ID — identifier associating the score-list relationship with a scheduling context, supporting automated or recurring scoring activity.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-organization and security-group access control.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording who last modified the row and under which login session.
• CREATION_DATE, CREATED_BY — standard audit columns recording initial row creation.

SCORE_LIST_ID is both the primary key and the documented business-key candidate (unique index AMS_DM_SCORE_LISTS_U1). No alternate unique business key is documented; the natural uniqueness of the association derives from the SCORE_ID / LIST_HEADER_ID pairing rather than from a named unique constraint.

Common Use Cases and Queries

The primary reporting use case is determining which lists are attached to a given scoring run, and conversely, which scoring runs have touched a given list. A typical join pattern is:

• Resolving score context: SELECT s.SCORE_LIST_ID, s.SCORE_ID, s.LIST_HEADER_ID FROM AMS.AMS_DM_SCORE_LISTS s WHERE s.SCORE_ID = :score_id;
• Resolving list context: SELECT s.SCORE_ID, s.SCHEDULE_ID FROM AMS.AMS_DM_SCORE_LISTS s WHERE s.LIST_HEADER_ID = :list_header_id;
• Joining list headers for list names: join AMS_DM_SCORE_LISTS to AMS_LIST_HEADERS_ALL on LIST_HEADER_ID to report list names against scoring runs.
• Joining score definitions for scoring metadata: join on SCORE_ID to AMS_DM_SCORES_ALL_B to report scoring configuration alongside list membership.

These queries are frequently used in marketing analytics, scoring audit reports, and troubleshooting exercises where users must confirm whether a list was included in a particular scoring cycle.

Related Objects

• AMS_DM_SCORES_ALL_B — referenced via SCORE_ID; holds the scoring run or score definition.
• AMS_LIST_HEADERS_ALL — referenced via LIST_HEADER_ID; holds the generic list definition.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; enforces security-group access.
• AMS_DM_SCORE_LIST and related score-list API or view objects in the AMS schema — consume SCORE_LIST_ID as the parent key for child records.
• AMS_LIST_ENTRIES and other list membership tables — associated indirectly through the LIST_HEADER_ID relationship to AMS_LIST_HEADERS_ALL.