Search Results channel_schedule_id




Overview
Explore in AI Chat

Overview

APPS.IES_AMS_LIST_ENTRIES_V is a reporting and integration view in the Oracle E-Business Suite Oracle Marketing (AMS) module. It exposes the contents of the AMS_LIST_ENTRIES table, which stores the individual rows (members or entries) belonging to a marketing list header. Each row represents one contact, lead, customer, or prospect entry within a list, together with the channel and campaign context in which that list entry is used.

The view is owned by the APPS schema and is intended to provide a stable, read-oriented projection of list entry data for use by concurrent programs, OBIEE/BI Publisher reports, interface programs, and downstream integrations. The presence of the CHANNEL_SCHEDULE_ID column — the term the user searched for — indicates that this view is a primary source for correlating marketing list entries to a specific channel schedule, which is the execution instance of a channel (such as an email or direct mail deployment) within a campaign.

Underlying Base Objects

The view is defined over a single documented base object: AMS_LIST_ENTRIES (referenced through a synonym). Because it is a simple, non-joined projection, there is no aggregation or outer-join logic; the view returns one row per AMS_LIST_ENTRIES record. The view does not apply a WHERE clause, so consumers receive all list entry rows regardless of source or status, and should apply their own filtering predicates for list header, campaign, channel, or channel schedule.

One notable transformation is the literal NULL F_DELETEDFLAG column appended to the select list. This constant is used by downstream ETL or interface logic as a placeholder flag; it always returns NULL and should not be treated as a real data attribute of the base table.

Key Columns

Common Use Cases and Queries

A frequent requirement is identifying all list entries tied to a specific channel schedule — the exact search term reported. For example:

  • Retrieve entries for a given channel schedule: SELECT list_entry_id, list_header_id, customer_id, email_address FROM apps.ies_ams_list_entries_v WHERE channel_schedule_id = :p_channel_schedule_id;
  • Report entries by campaign and channel: SELECT campaign_id, channel_id, count(*) FROM apps.ies_ams_list_entries_v GROUP BY campaign_id, channel_id;
  • Extract email recipients for a list header: SELECT email_address FROM apps.ies_ams_list_entries_v WHERE list_header_id = :p_list_header_id AND email_address IS NOT NULL;

Because the view has no filtering or joins, it performs efficiently for set-based extracts and is well suited to bulk reporting and integration loads.