Search Results ams_tcop_fatigued_by_pk1

Overview

The AMS_TCOP_FATIGUED_BY table is a core data object within the Oracle E-Business Suite Marketing (AMS) module, specifically for versions 12.1.1 and 12.2.2. It serves a critical function in managing marketing fatigue rules, a key component of campaign management. The table's primary role is to log and track the specific campaign schedules that have contributed to a party (e.g., a customer or contact) reaching a state of "fatigue." This mechanism helps prevent over-solicitation by ensuring that marketing communications are not sent too frequently to the same recipient, thereby improving campaign effectiveness and customer experience.

Key Information Stored

Based on the provided ETRM metadata, the table's structure is centered around linking fatigued parties to the schedules that caused the fatigue state. The primary key column, FATIGUED_BY_ID, uniquely identifies each record in this logging table. The most significant foreign key column is SCHEDULE_ID, which references the AMS_CAMPAIGN_SCHEDULES_B table. This column stores the identifier for the specific campaign schedule execution that was counted toward the party's fatigue threshold. While the full column list is not detailed in the excerpt, typical tables of this nature would also include a foreign key to the party (e.g., CUSTOMER_ID or PARTY_ID) and likely timestamps for when the fatigue event was recorded.

Common Use Cases and Queries

This table is primarily accessed for auditing, reporting, and troubleshooting within the marketing operations lifecycle. Common use cases include analyzing the history of communications sent to a party prior to a fatigue trigger, generating reports on which schedules most frequently cause fatigue, and validating that fatigue rules are being applied correctly. A typical analytical query would join this table to campaign schedule and campaign detail tables to understand the context of the fatiguing events.

• Identifying all schedules that fatigued a specific party: SELECT schedule_id FROM ams_tcop_fatigued_by WHERE party_id = :1;
• Reporting on fatigue events by campaign: SELECT acs.campaign_id, COUNT(*) AS fatigue_count FROM ams_tcop_fatigued_by atfb, ams_campaign_schedules_b acs WHERE atfb.schedule_id = acs.schedule_id GROUP BY acs.campaign_id;

Related Objects

The AMS_TCOP_FATIGUED_BY table has a direct and documented relationship with the core campaign execution tables in the AMS schema, as per the provided metadata.

• AMS_CAMPAIGN_SCHEDULES_B: This is the primary related table. The foreign key AMS_TCOP_FATIGUED_BY.SCHEDULE_ID references AMS_CAMPAIGN_SCHEDULES_B. This relationship is essential for retrieving details (like associated campaign, activity, and timing) of the schedule that caused a fatigue record.
• The table's primary key constraint, AMS_TCOP_FATIGUED_BY_PK1, on the FATIGUED_BY_ID column, ensures the uniqueness of each fatigue event log and is likely referenced by any secondary indexes or application logic that fetches individual records.