Results for “schedule_id”

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

Overview

The AMS_TCOP_FATIGUED_BY table is a Marketing (AMS) module data object in Oracle E-Business Suite 12.1.1 and 12.2.2. It captures information about the list of schedules that have "fatigued" a party — that is, the association between a campaign schedule and a list entry representing a recipient or party that has reached a fatigue threshold. In the context of Oracle Marketing's frequency-capping and fatigue-management functionality, this table records which parties have been contacted by which schedules, supporting the suppression logic that limits over-communication to individual recipients.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is satellite-leaning. This suggests the table behaves primarily as a descriptive satellite attached to a parent business key, rather than as an independent hub or an associative link. Its grain is defined by the combination of list entry and schedule, making it a record of state or measurement associated with those two business entities.

Key Information Stored

The table contains nine documented columns. The most significant are:

• FATIGUED_BY_ID — The surrogate primary key, backed by the unique index AMS_TCOP_FATIGUED_BY_PK1 and also by AMS_TCOP_FATIGUED_BY_U1. This is a system-generated identifier with no business meaning.
• LIST_ENTRY_ID — Foreign key to AS_LIST_ENTRIES, identifying the list entry (typically the recipient or party) that has been fatigued.
• SCHEDULE_ID — Foreign key to AMS_CAMPAIGN_SCHEDULES_B, identifying the campaign schedule responsible for the fatigue.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, controlling multi-organization and security-group access to the record.
• CREATION_DATE, CREATED_BY — Audit columns recording when and by whom the row was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Audit columns capturing the most recent modification and the login session that performed it.

The business-key candidate is the composite unique index AMS_TCOP_FATIGUED_BY_U2 over (LIST_ENTRY_ID, SCHEDULE_ID), confirming that a given list entry may be fatigued by a given schedule only once. This composite uniquely identifies the association independently of the surrogate key, which is why the table is best understood as satellite-leaning rather than a pure hub.

Common Use Cases and Queries

Typical use cases include fatigue reporting, suppression-list verification, and audit of campaign contact frequency. A common query retrieves all schedules that have fatigued a given list entry:

• SELECT FATIGUED_BY_ID, LIST_ENTRY_ID, SCHEDULE_ID FROM AMS.AMS_TCOP_FATIGUED_BY WHERE LIST_ENTRY_ID = :p_list_entry_id;
• SELECT SCHEDULE_ID, COUNT(*) FROM AMS.AMS_TCOP_FATIGUED_BY GROUP BY SCHEDULE_ID ORDER BY 2 DESC;
• Join to AMS_CAMPAIGN_SCHEDULES_B to resolve schedule names and campaign context, and to AS_LIST_ENTRIES to resolve recipient attributes.

Reporting scenarios frequently require filtering by SECURITY_GROUP_ID to respect multi-org security, and by CREATION_DATE to isolate fatigue events within a campaign wave.

Related Objects

• AMS_CAMPAIGN_SCHEDULES_B — Joined on AMS_TCOP_FATIGUED_BY.SCHEDULE_ID = AMS_CAMPAIGN_SCHEDULES_B.SCHEDULE_ID; the parent schedule definition.
• AS_LIST_ENTRIES — Joined on AMS_TCOP_FATIGUED_BY.LIST_ENTRY_ID = AS_LIST_ENTRIES.LIST_ENTRY_ID; the fatigued party or recipient entry.
• FND_SECURITY_GROUPS — Joined on AMS_TCOP_FATIGUED_BY.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID; enforces access control.
• AMS_CAMPAIGN_SCHEDULES_TL — Provides translated schedule names for reporting joins through the schedule base table.
• AMS_LIST_HEADERS_B / AMS_LIST_HEADERS_TL — Supply list-level context for the entries referenced here.