Results for “list_entry_source_system_id”

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

Overview

AMS_TAR_CONTACT_V is an APPS-owned, VALID database view within the Oracle Marketing (AMS) product family. Per the Enterprise Technical Reference Manual (ETRM) metadata for Oracle E-Business Suite 12.1.1 and 12.2.2, the view presents the information stored for an "AMS_CONTACT" List source type. In practice, the view acts as a flattened, denormalized reporting interface over contact-oriented list entries held in the AMS_LIST_ENTRIES table, exposing party, address, and contact attributes in a single row per list entry.

Its primary role is to support list management, campaign targeting, and downstream integration reporting. Because Oracle Marketing stores list entries in a generic structure with source-system-specific columns, this view isolates the columns that apply to contacts and aliases them into meaningful business names, such as BILL_TO_STATE and SHIP_TO_STATE. That aliasing is significant for consumers who search on address attributes like "ship_to_state," since the physical column name in the base table (COL12) is not descriptive on its own.

Underlying Base Objects

The view is defined over a single documented base object: AMS_LIST_ENTRIES, accessed through a synonym in the APPS schema. The view text applies a WHERE clause filter of LIST_ENTRY_SOURCE_SYSTEM_TYPE = 'AMS_CONTACT', so only list entries sourced from AMS Contact records are returned. It also carries through a set of audit and reference columns including LIST_ENTRY_ID, LIST_HEADER_ID, OBJECT_VERSION_NUMBER, SOURCE_CODE, ENABLED_FLAG, and the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY).

Because AMS_LIST_ENTRIES is a multi-purpose list entry store, the same physical columns are reused across source types. The view does not join additional tables; all party, address, and organization fields are materialized from the columns already present on the list entry row. This makes the view lightweight and suitable for bulk extraction.

Key Columns

• PARTY_ID — Identifier of the contact or organization party associated with the list entry.
• SHIP_TO_STATE — Mapped from COL12; the state or province of the ship-to address. This is the column relevant to searches for "ship_to_state."
• SHIP_TO_ADDRESS1 through SHIP_TO_ADDRESS4, SHIP_TO_CITY, SHIP_TO_COUNTRY, SHIP_TO_POSTAL_CODE — The remaining ship-to address components, mapped from COL7–COL14.
• BILL_TO_STATE — Mapped from COL6; the state or province of the bill-to address, with companion BILL_TO columns mapped from COL4 and COL5.
• LAST_NAME, FIRST_NAME, MIDDLE_NAME, SUFFIX, TITLE, ACADEMIC_TITLE, KNOWN_AS — Contact identity attributes.
• ORGANIZATION_NAME, CUSTOMER_KEY, DUNS_NUMBER, JGZZ_FISCAL_CODE, TAX_NAME, TAX_REFERENCE — Organization and fiscal identifiers.
• EMAIL_ADDRESS, PHONE_NUMBER — Contact communication details.
• ENABLED_FLAG, MARKED_AS_DUPLICATE_FLAG, MANUALLY_ENTERED_FLAG — Status and quality flags governing list entry state.

Common Use Cases and Queries

The view is typically used to extract contact lists for campaign execution, to audit address completeness, and to feed external marketing or analytics platforms. A typical query to locate contacts by ship-to state is:

• SELECT party_id, first_name, last_name, ship_to_state, ship_to_city FROM ams_tar_contact_v WHERE ship_to_state = 'CA' AND enabled_flag = 'Y';

Analysts may also aggregate list membership per state, or reconcile list entries against AMS_LIST_ENTRIES directly, since the view is a filtered projection of that table. When troubleshooting address data, comparing SHIP_TO_STATE and BILL_TO_STATE quickly reveals inconsistencies between shipping and billing records. Because the view carries audit and campaign reference columns, it also supports joins to campaign and channel entities for performance reporting.