Search Results ams_person

Overview

APPS.AMS_TAR_PERSON_V is a read-only Oracle EBS view that exposes person records held within Oracle Marketing (AMS) list entries. It is a filtered projection of the AMS_LIST_ENTRIES table, restricted by the predicate LIST_ENTRY_SOURCE_SYSTEM_TYPE = 'AMS_PERSON'. In Oracle EBS 12.1.1 and 12.2.2, the view serves as a denormalized, name-mapped representation of targeted person data, translating the generic COL1 through COL24 flexfield columns of the list-entry structure into descriptive business attribute names such as PERSON_NAME, PERSON_FIRST_NAME, DUNS_NUMBER, and SIC_CODE.

Because Oracle Marketing list entries support heterogeneous source systems, records are stored with a source-system type identifier and a set of positional columns whose meaning depends on that type. AMS_TAR_PERSON_V supplies the person-specific interpretation of those positional columns, allowing reporting tools, concurrent programs, and integration interfaces to consume person list members through stable, meaningful column names rather than raw COL references.

Underlying Base Objects

The view is defined over a single documented base object, AMS_LIST_ENTRIES, accessed through a synonym in the APPS schema. AMS_LIST_ENTRIES is the core list-member table in Oracle Marketing; every row represents one entry belonging to a list header (LIST_HEADER_ID) and carries selection, channel, campaign, and source-system attributes.

AMS_TAR_PERSON_V applies a constant filter on LIST_ENTRY_SOURCE_SYSTEM_TYPE equal to 'AMS_PERSON', so only entries originating from the person source system are returned. No joins to TCA party tables (HZ_PARTIES, HZ_PERSON_PROFILES) are present in the documented view text; the party linkage is carried via the PARTY_ID column stored on the list entry itself. All columns exposed by the view correspond directly to columns in AMS_LIST_ENTRIES, including the COL1–COL24 positional columns aliased to person attributes.

Key Columns

• CUSTOMER_KEY (COL4), DUNS_NUMBER (COL7), TAX_NAME (COL8), TAX_REFERENCE (COL5), JGZZ_FISCAL_CODE (COL6): organizational and fiscal identifiers mapped from positional columns.
• PERSON_NAME, PERSON_FIRST_NAME, PERSON_LAST_NAME, PERSON_MIDDLE_NAME, PERSON_NAME_SUFFIX, PERSON_PRE_NAME_ADJUNCT, PERSON_PREVIOUS_LAST_NAME: the person name components derived from CUSTOMER_NAME, FIRST_NAME, LAST_NAME, COL10, SUFFIX, COL9, and COL12 respectively.
• PERSON_NUMBER (COL1), PERSON_IDENTIFIER (COL14), PERSON_IDEN_TYPE (COL13), PERSON_ACADEMIC_TITLE (COL11), PERSON_TITLE, KNOWN_AS (COL24): person identification and title attributes.
• SIC_CODE (COL2), SIC_CODE_TYPE (COL15), HQ_BRANCH_IND (COL3): classification and organization-indicator attributes.
• PARTY_ID: the TCA party identifier for the person, enabling joins back to customer and party models.
• LIST_ENTRY_ID, LIST_HEADER_ID, LIST_ENTRY_SOURCE_SYSTEM_ID, LIST_ENTRY_SOURCE_SYSTEM_TYPE, OBJECT_VERSION_NUMBER, SOURCE_CODE, PIN_CODE: list-membership and concurrency control columns.
• MANUALLY_ENTERED_FLAG, MARKED_AS_DUPLICATE_FLAG, MARKED_AS_RANDOM_FLAG, PART_OF_CONTROL_GROUP_FLAG, ENABLED_FLAG: entry status and quality flags.
• CAMPAIGN_ID, MEDIA_ID, CHANNEL_ID, CHANNEL_SCHEDULE_ID, EVENT_OFFER_ID, LIST_SELECT_ACTION_ID, ARC_LIST_SELECT_ACTION_FROM: marketing execution and selection context.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY: standard audit columns.

Common Use Cases and Queries

The view is typically queried to report on persons that have been targeted by one or more marketing lists, and to reconcile list membership against TCA party data.

• Listing all persons in a given list header, for example: SELECT PERSON_NAME, PERSON_NUMBER, PARTY_ID FROM APPS.AMS_TAR_PERSON_V WHERE LIST_HEADER_ID = :p_list_header_id;
• Identifying manually entered or potentially duplicated person entries: SELECT PERSON_NAME, MANUALLY_ENTERED_FLAG, MARKED_AS_DUPLICATE_FLAG FROM APPS.AMS_TAR_PERSON_V WHERE ENABLED_FLAG = 'Y';
• Joining to TCA for party verification: SELECT v.PERSON_NAME, p.party_number FROM APPS.AMS_TAR_PERSON_V v, HZ_PARTIES p WHERE v.PARTY_ID = p.party_id;
• Segmentation reporting by SIC: SELECT SIC_CODE, COUNT(*) FROM APPS.AMS_TAR_PERSON_V GROUP BY SIC_CODE;
• Campaign attribution: selecting CAMPAIGN_ID, CHANNEL_ID, and EVENT_OFFER_ID alongside person identifiers to measure person reach per campaign.

Because the view is a simple filtered projection with no aggregation, it remains suitable for both ad hoc SQL and integrated extraction programs, and all predicate pushdown occurs directly on AMS_LIST_ENTRIES.