Results for “list_action_type”

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

Overview

AMS_ACT_LISTS is a table in the AMS (Marketing) product schema of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It stores the association between activity records and the Target Group or Invite Lists they consume, capturing which list is used by which marketing activity or schedule. In practice, the table functions as a junction between a list definition and the activity, campaign schedule, or event offer that references it.

From a heuristic Data Vault modeling perspective, the mined FK structure classifies this object as a link. It resolves many-to-many style relationships between activity records and list headers rather than holding a single natural business entity, so it is best modeled as a link table with the participating hub keys.

Key Information Stored

The table contains 15 documented physical columns. The most significant are summarized below.

• ACT_LIST_HEADER_ID — surrogate primary key, enforced by unique index AMS_ACT_LISTS_U1.
• LIST_HEADER_ID — foreign key to AMS_LIST_HEADERS_ALL, identifying the target group or invite list being attached.
• LIST_USED_BY_ID — foreign key identifying the consuming entity; it resolves against AMS_CAMPAIGN_SCHEDULES_B and AMS_EVENT_OFFERS_ALL_B depending on context.
• LIST_USED_BY — discriminator indicating the type of entity that consumes the list.
• LIST_ACT_TYPE and LIST_ACTION_TYPE — classify the activity/action semantics of the list usage.
• GROUP_CODE — grouping code used to organize related list assignments.
• ORDER_NUMBER — sequencing attribute for ordered presentation of lists.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org/security partitioning.
• Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.

The documented unique index is on ACT_LIST_HEADER_ID; no additional business-key unique index is documented, so the surrogate key is the sole documented uniqueness constraint.

Common Use Cases and Queries

Typical scenarios include identifying which lists a campaign schedule or event offer uses, auditing list assignments across activities, and reporting list consumption by security group. A representative join to retrieve list usage is:

• SELECT a.act_list_header_id, a.list_header_id, a.list_used_by_id, a.list_used_by, a.list_act_type FROM ams_act_lists a WHERE a.list_used_by_id = :schedule_id;
• Join to AMS_LIST_HEADERS_ALL on LIST_HEADER_ID to resolve list names and descriptions.
• Join to AMS_CAMPAIGN_SCHEDULES_B on LIST_USED_BY_ID to report schedule-level list usage.
• Join to AMS_EVENT_OFFERS_ALL_B on LIST_USED_BY_ID to report offer-level list usage.
• Filter by SECURITY_GROUP_ID to restrict results to the operating unit or security context.

Because LIST_USED_BY_ID resolves against more than one parent table, queries must filter by LIST_USED_BY to avoid ambiguous joins.

Related Objects

• AMS_LIST_HEADERS_ALL — referenced via AMS_ACT_LISTS.LIST_HEADER_ID; the list definition.
• AMS_CAMPAIGN_SCHEDULES_B — referenced via AMS_ACT_LISTS.LIST_USED_BY_ID; campaign schedule consuming the list.
• AMS_EVENT_OFFERS_ALL_B — referenced via AMS_ACT_LISTS.LIST_USED_BY_ID; event offer consuming the list.
• FND_SECURITY_GROUPS — referenced via AMS_ACT_LISTS.SECURITY_GROUP_ID; security partitioning.