Results for “ams_party_sources”

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

Overview

AMS_PARTY_SOURCES is a Marketing (AMS) application table in Oracle E-Business Suite 12.1.1 and 12.2.2 that records the provenance of parties created in the Trading Community Architecture (TCA) model. The table documents how and from where a party record in HZ_PARTIES originated, capturing the linkage between a newly added party and the marketing list, import header, or import source line that produced it. Its status in the ETRM repository is VALID, and the object is owned by the AMS schema.

Because the table carries both a distinct surrogate identifier and multiple foreign keys pointing to parent entities (lists, import headers, source lines, parties), the metadata's heuristic Data Vault classification suggests modeling this as a link table — a relationship construct that connects a party hub to list and import-related hubs. This classification reflects the table's role as a connector that records associations rather than descriptive attributes of a single entity, although it also carries satellite-like descriptive columns such as USED_FLAG and OVERLAY_FLAG.

Key Information Stored

The primary key of the table is enforced by the unique index AMS_PARTY_SOURCES_PK (and the unique index AMS_PARTY_SOURCES_U1), both keyed on the surrogate identifier PARTY_SOURCES_ID. The most significant columns include:

• PARTY_SOURCES_ID — Surrogate primary key and business-key candidate identifying each party-source record.
• PARTY_ID — Foreign key to HZ_PARTIES, identifying the newly added TCA party.
• IMPORT_SOURCE_LINE_ID — Foreign key to AMS_IMP_SOURCE_LINES, referencing the specific import line.
• IMPORT_LIST_HEADER_ID — Foreign key to AMS_IMP_LIST_HEADERS_ALL, referencing the import list header.
• LIST_SOURCE_TYPE_ID — Foreign key to AMS_LIST_SRC_TYPES, classifying the source type.
• USED_FLAG — Indicates whether the source record has been consumed or applied.
• OVERLAY_FLAG and OVERLAY_DATE — Track overlay processing status and timing.
• OBJECT_VERSION_NUMBER — Optimistic locking column for concurrent updates.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS supporting multi-tenant data isolation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns.
• COL1 … COL250 — A large set of generic descriptor columns (the table documents 268 columns in total), used flexibly for source-specific data.

The surrogate key PARTY_SOURCES_ID is the primary access path; PARTY_ID and the import-related foreign keys function as business identifiers that link the source record to operational entities.

Common Use Cases and Queries

A typical reporting need is to determine the origin of a party — for example, which marketing import list introduced a given customer. A join against HZ_PARTIES and AMS_IMP_LIST_HEADERS_ALL supports this:

• SELECT aps.PARTY_SOURCES_ID, aps.PARTY_ID, aps.IMPORT_LIST_HEADER_ID, aps.LIST_SOURCE_TYPE_ID, aps.USED_FLAG FROM AMS.AMS_PARTY_SOURCES aps WHERE aps.PARTY_ID = :party_id;
• Auditing unused source records: SELECT * FROM AMS.AMS_PARTY_SOURCES WHERE USED_FLAG = 'N';
• Overlay reconciliation reporting using OVERLAY_FLAG and OVERLAY_DATE.
• Tracing a list import to generated parties: filter on IMPORT_LIST_HEADER_ID and join to HZ_PARTIES.

Because the table is a relationship link, queries are typically driven from PARTY_ID or the import header identifiers rather than from child tables.

Related Objects

The following objects participate in documented referential relationships with AMS_PARTY_SOURCES:

• HZ_PARTIES — joined via AMS_PARTY_SOURCES.PARTY_ID; the TCA master entity for the party.
• AMS_LIST_SRC_TYPES — joined via LIST_SOURCE_TYPE_ID; classifies source categories.
• AMS_IMP_LIST_HEADERS_ALL — joined via IMPORT_LIST_HEADER_ID; the import list header.
• AMS_IMP_SOURCE_LINES — joined via IMPORT_SOURCE_LINE_ID; the import source line detail.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; governs row-level security.

These relationships position AMS_PARTY_SOURCES as the audit and traceability junction between Marketing list imports and the TCA party registry.