Search Results ams_list_headers_all_uk1

Overview

The AMS_LIST_HEADERS_ALL table is a core data repository within the Oracle E-Business Suite Marketing (AMS) module, specifically for releases 12.1.1 and 12.2.2. It serves as the master definition table for target lists, which are fundamental entities used to manage groups of customers, prospects, or partners for marketing campaigns, events, and other activities. The table's role is to store the header-level, or master, attributes of a list, establishing its identity, ownership, and basic configuration. As a multi-organization enabled table (indicated by the "_ALL" suffix), it contains data for all operating units, with access typically controlled by the MOAC (Multi-Org Access Control) security model.

Key Information Stored

The table's primary identifier is the LIST_HEADER_ID, which is the unique key referenced throughout the marketing schema. Critical descriptive and control columns include LIST_NAME, which, in conjunction with VIEW_APPLICATION_ID, forms a unique key (AMS_LIST_HEADERS_ALL_UK1). The LIST_USED_BY_ID column is a pivotal foreign key that links the list to the specific campaign, event, or other marketing object that utilizes it. Other significant columns manage ownership (OWNER_USER_ID), data maintenance (LAST_DEDUPED_BY_USER_ID, TIMEZONE_ID), and status tracking. The table also holds attributes defining the list's type, source, refresh behavior, and archival settings, forming a comprehensive control record for list management.

Common Use Cases and Queries

This table is central to operations involving list administration, auditing, and integration. Common scenarios include generating a master list of all target lists for an operating unit, auditing list ownership, and identifying lists used by a specific campaign. A typical reporting query would join with FND_USER and HZ_TIMEZONES to present user-friendly information. For technical integrations, such as data loads or interfaces, the LIST_HEADER_ID retrieved from this table is essential for populating child table records. A fundamental query pattern is:

• SELECT list_header_id, list_name, owner_user_id, u.user_name, creation_date FROM ams_list_headers_all list, fnd_user u WHERE list.owner_user_id = u.user_id AND list.list_used_by_id = :campaign_id;

This retrieves all lists associated with a given campaign, a common requirement for campaign analysis.

Related Objects

The AMS_LIST_HEADERS_ALL table has extensive relationships, acting as a hub for list-related data. Its primary child table is AMS_LIST_ENTRIES, which stores the individual member records belonging to each list. The translated name is held in AMS_LIST_HEADERS_ALL_TL. Crucially, the LIST_USED_BY_ID foreign key connects it to major marketing execution tables like AMS_CAMPAIGN_SCHEDULES, AMS_EVENT_OFFERS_ALL_B, and AMS_EVENT_HEADERS_ALL_B. It is also referenced by list selection and rule objects (AMS_LIST_SELECT_ACTIONS, AMS_LIST_RULE_USAGES), data mining objects (AMS_DM_SCORE_LISTS), and activity tracking objects (AMS_ACT_LOGS, AMS_ACT_METRICS_ALL). This wide network of foreign key relationships underscores its critical position in the marketing data model.