Search Results person_previous_last_name




Overview
Explore in AI Chat

Overview

AMS_TAR_PERSON_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Marketing (AMS) product family. Its documented purpose is to expose the information stored for an "AMS_PERSON" list source type, meaning that it presents the person-oriented records held within Oracle Marketing list entries. The view is valid in both EBS 12.1.1 and 12.2.2 and provides a denormalized, read-only projection that is convenient for reporting and integration rather than for transactional maintenance.

Because the view is defined over list-entry data, it is primarily used by marketing analysts, campaign managers, and technical consultants who need to inspect the membership and attributes of person-based target lists. It also serves as a stable interface for downstream tools and custom reports, since the underlying AMS_LIST_ENTRIES table stores many list attributes in a generic, multi-purpose structure that is unpivoted and remapped by the view into business-friendly column names. Users searching for "person_identifier" will find that the view surfaces this attribute as PERSON_IDENTIFIER, aliased from the generic COL14 column of the base table.

Underlying Base Objects

The documented base object for AMS_TAR_PERSON_V is AMS_LIST_ENTRIES, referenced through a synonym. The view text selects from AMS_LIST_ENTRIES and applies a restrictive predicate: LIST_ENTRY_SOURCE_SYSTEM_TYPE = 'AMS_PERSON'. This filter ensures that only list entries originating from a person source are returned, excluding other source types such as organizations or imported external lists. Columns such as COL1 through COL24 in the base table are generic placeholders, and the view renames them into meaningful business attributes (for example, COL14 becomes PERSON_IDENTIFIER, COL1 becomes PERSON_NUMBER, COL3 becomes HQ_BRANCH_IND). The view also carries the standard EBS audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY, and WHERE clauses on the base table remain the mechanism by which the person-only population is enforced.

Key Columns

Common Use Cases and Queries

Typical uses include auditing person list membership, reconciling marketing list populations, and extracting person attributes for campaign segmentation. A frequent query pattern filters on PERSON_IDENTIFIER, the column most relevant to the original search:

  • SELECT party_id, person_name, person_identifier FROM ams_tar_person_v WHERE person_identifier = :identifier;
  • SELECT list_header_id, list_entry_id, person_name FROM ams_tar_person_v WHERE enabled_flag = 'Y';
  • SELECT person_last_name, person_first_name, source_code FROM ams_tar_person_v WHERE list_header_id = :list_id ORDER BY person_last_name;

Because the view is read-only and filtered to AMS_PERSON entries, INSERT, UPDATE, and DELETE operations should be directed at the base AMS_LIST_ENTRIES table, not the view.