Search Results ams_tcop_contacts_pk1

Overview

The AMS_TCOP_CONTACTS table is a core data object within the Oracle E-Business Suite Marketing (AMS) module. It serves as the system of record for tracking all contacts made to customers or prospects through marketing campaigns that utilize fatiguing schedules. A fatiguing schedule is a business rule designed to prevent customer contact fatigue by governing the frequency, timing, and channels used for outreach. This table is therefore critical for campaign execution management, ensuring compliance with contact policies, and analyzing the volume and history of customer interactions.

Key Information Stored

The table's primary purpose is to log each contact event. The central column is CONTACT_ID, which serves as the unique identifier for each record. Each contact is linked to three fundamental entities: the recipient, the campaign schedule, and the communication channel. This is achieved through foreign key columns PARTY_ID (linking to HZ_PARTIES to identify the contacted customer or prospect), SCHEDULE_ID (linking to AMS_CAMPAIGN_SCHEDULES_B to identify the specific fatiguing schedule rule applied), and MEDIA_ID (linking to AMS_MEDIA_B to specify the contact channel, such as email or direct mail). Additional columns typically found in such audit tables would include timestamps for the contact and potentially status indicators.

Common Use Cases and Queries

The primary use case is reporting and analysis of campaign contact history. Marketing analysts query this table to measure campaign volume, assess schedule adherence, and understand contact patterns for specific customers. A common query involves joining to related tables to generate a contact report by campaign or customer. For example, to list all contacts for a specific party, one might use:

• SELECT c.contact_id, c.contact_date, m.media_name, s.schedule_name FROM ams_tcop_contacts c, hz_parties p, ams_media_b m, ams_campaign_schedules_b s WHERE c.party_id = p.party_id AND c.media_id = m.media_id AND c.schedule_id = s.schedule_id AND p.party_id = <PARTY_VALUE>;

Another critical operational use is within the fatiguing engine logic itself, which likely queries this table to determine a customer's recent contact history before permitting a new outbound communication, thereby enforcing the business rules.

Related Objects

AMS_TCOP_CONTACTS is centrally connected to several key tables via documented foreign key relationships, forming a critical part of the Marketing data model.

• HZ_PARTIES: Joined via AMS_TCOP_CONTACTS.PARTY_ID = HZ_PARTIES.PARTY_ID. This links each contact to the master Trading Community Architecture record for the customer or prospect.
• AMS_CAMPAIGN_SCHEDULES_B: Joined via AMS_TCOP_CONTACTS.SCHEDULE_ID = AMS_CAMPAIGN_SCHEDULES_B.SCHEDULE_ID. This links the contact to the specific fatiguing schedule rule that governed its execution.
• AMS_MEDIA_B: Joined via AMS_TCOP_CONTACTS.MEDIA_ID = AMS_MEDIA_B.MEDIA_ID. This links the contact to the communication channel or medium used.

The table's primary key constraint, AMS_TCOP_CONTACTS_PK1 on CONTACT_ID, ensures the uniqueness of each contact record and is referenced by any dependent objects or indexes.