Search Results ams_tcop_fr_rules_setup_pk

Overview

The AMS_TCOP_FR_RULES_SETUP table is a core data repository within the Oracle E-Business Suite Marketing (AMS) module, specifically for the Trade Copilot (TCOP) functionality. Its primary role is to store the master definition and configuration of Fatigue Rules. These rules are critical business logic components used by the integrated Rules Engine to govern and limit the frequency of marketing communications sent to customers or prospects across various channels. By defining thresholds based on time periods and channels, these rules prevent contact fatigue, ensuring marketing campaigns adhere to defined business policies and compliance requirements.

Key Information Stored

While the provided metadata does not list specific columns beyond key relationships, the structure indicates the table holds the essential attributes for each fatigue rule. The primary identifier is the RULE_ID, which uniquely defines each rule configuration. The table links to other master entities through foreign keys, implying it stores at least a PERIOD_ID (linking to AMS_TCOP_FR_PERIODS_B to define the rolling time window for counting contacts, such as "Last 30 Days") and a CHANNEL_ID (linking to AMS_MEDIA_B to specify the communication channel, like Email or Direct Mail, to which the rule applies). Additional columns likely define the rule's active status, the maximum allowable contact count within the defined period, and descriptive information such as the rule name and creation metadata.

Common Use Cases and Queries

The primary use case is the setup and maintenance of fatigue management policies within Trade Copilot campaigns. Administrators create, update, or inactivate rules via the application interface, which performs corresponding DML operations on this table. A common reporting need is to audit all active rules for a specific channel. A typical query would join to the channel and period tables for descriptive information:

• SELECT r.rule_id, m.media_name, p.period_name, r.max_contacts FROM ams_tcop_fr_rules_setup r, ams_media_b m, ams_tcop_fr_periods_b p WHERE r.channel_id = m.media_id AND r.period_id = p.period_id AND r.active_flag = 'Y';

Another critical operational use case is for the Rules Engine to query these definitions in real-time to evaluate whether a planned communication for a contact would violate any established fatigue threshold, thereby enforcing business logic at the point of campaign execution.

Related Objects

The table is central to the fatigue management data model, with documented relationships to several key objects:

• Primary Key: AMS_TCOP_FR_RULES_SETUP_PK on RULE_ID.
• Foreign Key References (Parent Tables):
  • AMS_TCOP_FR_PERIODS_B: Linked via AMS_TCOP_FR_RULES_SETUP.PERIOD_ID. Provides the time period definition for the rule.
  • AMS_MEDIA_B: Linked via AMS_TCOP_FR_RULES_SETUP.CHANNEL_ID. Provides the channel definition (e.g., Email) to which the rule applies.
• Foreign Key References (Child Tables):
  • AMS_TCOP_CHANNEL_SUMMARY: References AMS_TCOP_FR_RULES_SETUP.RULE_ID. Stores aggregated contact counts per channel, likely used for rule evaluation.
  • AMS_TCOP_CONTACT_SUMMARY: References AMS_TCOP_FR_RULES_SETUP.RULE_ID. Stores aggregated contact counts per individual contact, central to fatigue checking.