Results for “exclude_in_triggered_list_flag”

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

Overview

AMS_P_LIST_ENTRIES_V is a public view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AMS (Marketing) product family. Its documented status is VALID in both 12.1.1 and 12.2.2. The view exposes list entry records generated for a marketing list — the individual customers, contacts, and target prospects that populate a list for downstream activities such as mailshots, telemarketing, and campaign execution. Because it is a public view, it is intended for use by external reporting tools, concurrent programs, integrations, and custom extensions rather than by the internal Oracle Marketing forms alone.

The view text is a straightforward projection over the list entry entity, selecting the full set of operational, audit, and descriptive columns, including a large block of generic COL1 through COL109 attributes used for flexible, user-defined segmentation data.

Underlying Base Objects

ETRM documentation lists a single referenced base object: AMS_LIST_ENTRIES, accessed through a synonym. The view is therefore a thin, read-oriented layer over the AMS_LIST_ENTRIES table, which stores one row per list entry. No joins, aggregations, or filters are present in the view text, so row counts and cardinality in AMS_P_LIST_ENTRIES_V match the underlying table exactly. All who-column audit fields, descriptive columns, and flexible attribute columns are passed through unchanged.

Key Columns

• LIST_ENTRY_ID / LIST_HEADER_ID — primary identifier of the list entry and the parent list header it belongs to.
• SOURCE_CODE / LIST_SOURCE / LIST_SELECT_ACTION_ID — identify how the entry entered the list (manual entry, selection action, import).
• CUSTOMER_ID / PARTY_ID / PARENT_PARTY_ID / VENDOR_ID / LEAD_ID — the party or entity represented by the entry.
• CAMPAIGN_ID / MEDIA_ID / CHANNEL_ID / CHANNEL_SCHEDULE_ID / EVENT_OFFER_ID — links to the campaign and channel context for the entry.
• TRANSFER_FLAG / TRANSFER_STATUS — control whether the entry has been transferred to a downstream process (for example a campaign or telemarketing list) and the status of that transfer. This column is the focus of the user's search.
• MANUALLY_ENTERED_FLAG / MARKED_AS_DUPLICATE_FLAG / MARKED_AS_RANDOM_FLAG / PART_OF_CONTROL_GROUP_FLAG / EXCLUDE_IN_TRIGGERED_LIST_FLAG / ENABLED_FLAG / MARKED_FLAG — Boolean business flags governing entry behaviour.
• DEDUPE_KEY / DUPLICATE_MASTER_ENTRY_ID — support deduplication logic.
• PIN_CODE / CELL_CODE / RANDOMLY_GENERATED_NUMBER / DEDUPE_KEY — entry-level generated or assigned identifiers.
• COL1 – COL109 — generic flex columns holding user-defined attributes.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical uses include auditing list membership, extracting recipients for outbound campaigns, and reporting on entries by transfer and enablement status.

SELECT list_entry_id,
       list_header_id,
       customer_id,
       party_id,
       source_code,
       transfer_flag,
       transfer_status,
       enabled_flag
  FROM apps.ams_p_list_entries_v
 WHERE list_header_id = :p_list_header_id
   AND enabled_flag = 'Y';

SELECT transfer_status,
       COUNT(*) entries
  FROM apps.ams_p_list_entries_v
 WHERE transfer_flag = 'Y'
 GROUP BY transfer_status;

Because the view is unfiltered, reporting queries should always constrain on LIST_HEADER_ID, transfer flags, or audit dates to avoid full scans of the underlying list entry table in high-volume marketing implementations.