Results for “ies_ams_list_entries_v”

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

Overview

IES_AMS_LIST_ENTRIES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite. It is registered under the IES – Scripting product family, and its object status is VALID in both 12.1.1 and 12.2.2. The view presents a simplified projection of contact listing data used by the Advanced Marketing System (AMS) list entry infrastructure, exposing a small, stable set of attributes that describe an individual list entry: a surrogate identifier, the person's first and last name, an e-mail address, an object version number for optimistic locking, and a deletion indicator.

Because the view contains only scalar contact attributes and no financial or transactional data, it functions primarily as a lightweight integration and reporting surface. Scripting components, concurrent programs, and outbound interfaces can address a single, predictable object rather than joining several AMS tables directly. Notably, the view name was the target of a search for the column "first_name," confirming that FIRST_NAME is a first-class, directly selectable column rather than being derived at query time from a concatenated full name.

Underlying Base Objects

The documented view text is a straight projection over a single base object:

SELECT LIST_ENTRY_ID,
       FIRST_NAME,
       LAST_NAME,
       EMAIL_ADDRESS,
       OBJECT_VERSION_NUMBER,
       NULL F_DELETEDFLAG
  FROM AMS_LIST_ENTRIES

There are no joins, unions, aggregations, or inline functions in the definition. AMS_LIST_ENTRIES is referenced through a synonym in the APPS schema, consistent with standard EBS coding practice in which public or APPS synonyms mask the underlying application schema that owns the AMS tables. Consequently, the view inherits one row per row of AMS_LIST_ENTRIES; no row multiplication or filtering occurs.

Key Columns

• LIST_ENTRY_ID – Surrogate primary key of the list entry. Joins to the base AMS list entry table and is the preferred predicate for single-row lookups.
• FIRST_NAME – Given name of the contact associated with the list entry. This is the column most often searched and reported.
• LAST_NAME – Family name of the contact; typically paired with FIRST_NAME for display and sorting.
• EMAIL_ADDRESS – Electronic mail address of the contact, used for campaign delivery and deduplication logic.
• OBJECT_VERSION_NUMBER – Optimistic-locking token maintained by the underlying AMS entity. It increments on update and should be preserved by any integration that writes back through the base table.
• F_DELETEDFLAG – A derived column that the view definition hard-codes as NULL. It does not reflect a physical deletion state in AMS_LIST_ENTRIES; consumers must not treat this column as a reliable soft-delete indicator.

Common Use Cases and Queries

The view is well suited to contact lookups, campaign audience verification, and lightweight extracts. A typical lookup by name is:

SELECT list_entry_id,
       first_name,
       last_name,
       email_address
  FROM apps.ies_ams_list_entries_v
 WHERE first_name = :p_first_name;

For a bulk extract of all list entries destined for an external mail system:

SELECT list_entry_id,
       first_name,
       last_name,
       email_address
  FROM apps.ies_ams_list_entries_v
 WHERE email_address IS NOT NULL
 ORDER BY last_name, first_name;

Because the view exposes no deletion filter, consumers that require only active entries must join back to AMS_LIST_ENTRIES and apply the appropriate status predicate there. Joins to customer or party tables should be driven from LIST_ENTRY_ID or from a normalized e-mail address match, and the OBJECT_VERSION_NUMBER should be carried through any read-modify-write cycle to preserve concurrency control.