Search Results ams_list_entries

Overview

The AMS_LIST_ENTRIES table is a core data object within the Oracle E-Business Suite (EBS) Marketing (AMS) module. It functions as the central repository for all individual target prospects generated for marketing lists. These lists are foundational for executing outbound marketing campaigns, such as mailshots, telemarketing, and email blasts. The table is populated by Oracle Marketing's proprietary list generation engine, which processes segmentation rules and criteria to identify and qualify potential customers or contacts. As a transactional table, it serves as the critical link between a defined list header (the campaign audience definition) and the specific party or contact records in the Trading Community Architecture (TCA) model, enabling targeted marketing operations and campaign performance tracking.

Key Information Stored

The table stores the unique association between a generated prospect and the marketing list for which they were selected. Its primary structure is defined by a composite primary key consisting of LIST_HEADER_ID and LIST_ENTRY_ID. The LIST_HEADER_ID foreign key references the parent list definition in AMS_LIST_HEADERS_ALL. The LIST_ENTRY_ID provides a unique identifier for each entry within a given list. Crucially, the table holds foreign key references to key TCA entities: PARTY_ID links to the HZ_PARTIES table to identify the organization or person; CONTACT_POINT_ID references HZ_CONTACT_POINTS for a specific email, phone, or address; and LOCATION_ID references HZ_LOCATIONS for a physical address. This design ensures that each list entry points to a precise, marketable contact point for a given party.

Common Use Cases and Queries

A primary use case is extracting a target audience for a campaign execution. For example, to generate a call sheet for a telemarketing campaign, one would query for entries in a specific list, joining to TCA tables to retrieve contact details. Another critical use is analyzing list composition and campaign reach by counting entries per list or segment. Common reporting queries involve joining AMS_LIST_ENTRIES with AMS_LIST_HEADERS_ALL for list metadata and HZ_PARTIES for prospect attributes. A typical SQL pattern to audit list contents would be:

• SELECT ale.LIST_HEADER_ID, ale.LIST_ENTRY_ID, hp.PARTY_NAME, hcp.PHONE_NUMBER
• FROM AMS.AMS_LIST_ENTRIES ale,
• HZ_PARTIES hp,
• HZ_CONTACT_POINTS hcp
• WHERE ale.PARTY_ID = hp.PARTY_ID
• AND ale.CONTACT_POINT_ID = hcp.CONTACT_POINT_ID(+)
• AND ale.LIST_HEADER_ID = <list_id>;

This table is also central to tracking which prospects have been used across multiple campaigns via the AMS_LIST_ENTRY_USAGES table.

Related Objects

AMS_LIST_ENTRIES maintains integral relationships with several key EBS tables, primarily within the Marketing and TCA schemas. The documented foreign key relationships are as follows:

• AMS_LIST_HEADERS_ALL: The parent table. Joined via AMS_LIST_ENTRIES.LIST_HEADER_ID = AMS_LIST_HEADERS_ALL.LIST_HEADER_ID. This provides the campaign and list definition context.
• HZ_PARTIES: Joined via AMS_LIST_ENTRIES.PARTY_ID = HZ_PARTIES.PARTY_ID. This retrieves the core prospect entity details (name, type, etc.).
• HZ_CONTACT_POINTS: Joined via AMS_LIST_ENTRIES.CONTACT_POINT_ID = HZ_CONTACT_POINTS.CONTACT_POINT_ID. This provides the specific email, phone, or web address for contact.
• HZ_LOCATIONS: Joined via AMS_LIST_ENTRIES.LOCATION_ID = HZ_LOCATIONS.LOCATION_ID. This provides the physical address details for direct mail.
• AMS_LIST_ENTRY_USAGES: This child table references AMS_LIST_ENTRIES via both LIST_HEADER_ID and LIST_ENTRY_ID (AMS_LIST_ENTRY_USAGES.LIST_HEADER_ID, AMS_LIST_ENTRY_USAGES.LIST_ENTRY_ID). It tracks the usage history of a specific list entry across different marketing activities.