Search Results as_list_entries




Overview
Explore in AI Chat

Overview

The AS_LIST_ENTRIES table is a core data structure within the Oracle E-Business Suite Sales Foundation (AS) module. It functions as a central repository for storing individual list entries, which are the constituent members of various marketing and sales lists. These lists are fundamental to campaign management, lead distribution, telemarketing, and targeted marketing activities. The table's design, with multiple foreign key relationships to key transactional entities like customers, contacts, addresses, and phones, establishes it as a critical junction point linking master data to specific marketing initiatives and operational workflows in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's primary identifier is the LIST_ENTRY_ID column, which is enforced by the AS_LIST_ENTRIES_PK primary key. The most significant data points are the foreign key columns that define what entity a list entry represents. As per the provided metadata, these include CUSTOMER_ID (linking to RA_CUSTOMERS), CONTACT_ID (linking to AS_LIST_ENTRIES for contact records), ADDRESS_ID (linking to RA_ADDRESSES_ALL), and PHONE_ID (linking to RA_PHONES). The LIST_ID column, which references AS_PROMOTIONS_ALL, associates the entry with a specific parent marketing list or promotion. This structure allows a single list to contain a heterogeneous mix of record types, providing flexibility in defining target audiences.

Common Use Cases and Queries

A primary use case is generating call lists or target audience reports for a specific campaign. For instance, a query to retrieve all customer phone entries for a promotion would join AS_LIST_ENTRIES with RA_CUSTOMERS and RA_PHONES, filtering by LIST_ID. Given the user's search for "ra_phones", a typical pattern would involve identifying list entries that are phone-based contacts.

SELECT ale.list_entry_id,
       c.customer_name,
       ph.phone_number,
       ph.phone_type
FROM   as_list_entries ale,
       ra_customers c,
       ra_phones ph
WHERE  ale.customer_id = c.customer_id
AND    ale.phone_id = ph.phone_id
AND    ale.list_id = :p_list_id;

Another critical use case is managing collateral fulfillment, as indicated by the foreign key from AS_COLLATERAL_REQ_ALL, where list entries drive material requests for selected contacts or customers.

Related Objects

The ETRM metadata explicitly defines this table's integration with several key EBS schemas. Its main foreign key dependencies are:

  • RA_PHONES: Provides the phone contact details for phone-type list entries.
  • RA_CUSTOMERS: Provides customer master data for customer-type entries.
  • RA_ADDRESSES_ALL: Provides address information for address-type entries.
  • AS_PROMOTIONS_ALL: The parent table defining the marketing list or promotion.
  • AS_COLLATERAL_REQ_ALL: A dependent table that uses the LIST_ENTRY_ID to track collateral requests generated for specific list members.

This network of relationships positions AS_LIST_ENTRIES as a pivotal integration point between Sales Foundation (AS) and the underlying Receivables (RA) customer master data.