Search Results ams_party_sources




Overview
Explore in AI Chat

Overview

The AMS_PARTY_SOURCES table is a core data object within the Oracle E-Business Suite Marketing (AMS) module. Its primary function is to maintain an audit trail for the origin of newly created party records in the Trading Community Architecture (TCA) registry. When a party is added to the HZ_PARTIES table through AMS-driven processes—such as list imports, campaign responses, or lead generation—this table records the specific marketing source that created it. This linkage is critical for campaign attribution, list management, and understanding the provenance of customer and prospect data within the marketing ecosystem.

Key Information Stored

The table's structure is designed to link a party to its marketing source. The primary identifier is the PARTY_SOURCES_ID. The most significant columns include PARTY_ID, which is the foreign key to HZ_PARTIES, establishing the link to the party record itself. The source is defined through several key foreign key columns: LIST_SOURCE_TYPE_ID references AMS_LIST_SRC_TYPES to classify the source (e.g., "Web Form," "Trade Show List"), IMPORT_LIST_HEADER_ID links to AMS_IMP_LIST_HEADERS_ALL for batch list imports, and IMPORT_SOURCE_LINE_ID can provide a more granular link to the specific line within an import source via AMS_IMP_SOURCE_LINES. This design allows the system to track whether a party originated from a specific list upload, a particular import file line, or a general source type.

Common Use Cases and Queries

A primary use case is generating reports on lead or customer acquisition sources. Marketing analysts can query this table to determine how many new parties were generated from a specific imported list or source type within a given period. This is essential for measuring campaign ROI and list effectiveness. A typical query would join AMS_PARTY_SOURCES with HZ_PARTIES and the relevant source table. For example, to find all parties created from a specific import list header, one might use: SELECT ps.PARTY_ID, hz.PARTY_NAME FROM AMS_PARTY_SOURCES ps, HZ_PARTIES hz WHERE ps.PARTY_ID = hz.PARTY_ID AND ps.IMPORT_LIST_HEADER_ID = <header_id>;. Another critical use is data integrity and cleanup operations, where administrators may need to trace and validate the origin of party records that entered the system via marketing activities.

Related Objects

The table is centrally connected to several key AMS and TCA entities through documented foreign key relationships. These relationships are fundamental to its purpose:

  • HZ_PARTIES: Joined via PARTY_ID. This is the core relationship linking the source record to the actual party in TCA.
  • AMS_LIST_SRC_TYPES: Joined via LIST_SOURCE_TYPE_ID. This provides the categorization of the marketing source.
  • AMS_IMP_LIST_HEADERS_ALL: Joined via IMPORT_LIST_HEADER_ID. This links to the header record of a batch list import operation.
  • AMS_IMP_SOURCE_LINES: Joined via IMPORT_SOURCE_LINE_ID. This provides a more detailed link to the individual line item from an import source that generated the party.
The primary key constraint AMS_PARTY_SOURCES_PK on PARTY_SOURCES_ID ensures the uniqueness of each source record.