Search Results ams_tcop_requests




Overview
Explore in AI Chat

Overview

The AMS_TCOP_REQUESTS 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 functions as a transactional queue for managing the application of fatigue rules. Fatigue rules are business logic designed to prevent customer contact fatigue by controlling the frequency and volume of marketing communications sent to a given customer or prospect. This table stores requests that are pending or scheduled for processing by the system's fatigue engine, thereby playing a critical role in ensuring compliance with marketing policies and optimizing campaign outreach.

Key Information Stored

The primary purpose of the table is to track individual fatigue rule application requests. While the full column list is not detailed in the provided metadata, the documented structure highlights the essential identifiers. The REQUEST_ID column serves as the unique primary key for each request record. The SCHEDULE_ID column is a critical foreign key that links each fatigue processing request to a specific campaign schedule defined in the AMS_CAMPAIGN_SCHEDULES_B table. This relationship indicates that fatigue rule processing is intrinsically tied to the execution timeline of marketing campaigns. Other columns likely store status flags (e.g., PENDING, PROCESSED, ERROR), creation dates, requested processing timestamps, and parameters necessary for the fatigue engine to evaluate the applicable rules against the target audience.

Common Use Cases and Queries

The primary use case is the automated scheduling and execution of fatigue rule checks. A common operational query would involve monitoring the queue for pending requests or investigating failed processes. For reporting and auditing, analysts may join this table to campaign schedules to understand the volume and timing of fatigue rule applications.

  • Monitoring Pending Requests: SELECT request_id, schedule_id, creation_date FROM ams_tcop_requests WHERE status = 'PENDING' ORDER BY creation_date;
  • Identifying Requests for a Specific Campaign Schedule: SELECT r.* FROM ams_tcop_requests r, ams_campaign_schedules_b s WHERE r.schedule_id = s.schedule_id AND s.campaign_schedule_id = :p_sched_id;
  • Auditing Processing Volume: SELECT TRUNC(creation_date), COUNT(*) FROM ams_tcop_requests GROUP BY TRUNC(creation_date) ORDER BY 1 DESC;

Related Objects

The table maintains a direct and documented relationship with the campaign scheduling infrastructure. The key related objects are:

  • Primary Key Constraint: AMS_TCOP_REQUESTS_PK on the REQUEST_ID column.
  • Foreign Key Relationship: The table references AMS_CAMPAIGN_SCHEDULES_B via the SCHEDULE_ID column. This establishes that every fatigue processing request is associated with a specific, scheduled instance of a marketing campaign.

This table is typically accessed by internal AMS batch processes and is less frequently queried directly for business reporting, which would more commonly use higher-level campaign performance views that abstract this operational detail.