Search Results ams_trigger_checks




Overview
Explore in AI Chat

Overview

The AMS_TRIGGER_CHECKS table is a core data object within the Oracle E-Business Suite Marketing (AMS) module, specifically in versions 12.1.1 and 12.2.2. It functions as the central repository for defining conditional business rules, or "checks," that are evaluated by the system's automated triggering engine. Its primary role is to store the configuration for validations that must be executed when a scheduled date-time, as defined in the related AMS_TRIGGERS table, is reached. This mechanism is fundamental for automating time-based marketing campaign workflows, such as verifying that performance metrics meet specific thresholds before proceeding to a next campaign step or sending a notification.

Key Information Stored

The table's structure is designed to link a check to its parent trigger and to the specific metrics being evaluated. The primary key, TRIGGER_CHECK_ID, uniquely identifies each check rule. The most critical foreign key is TRIGGER_ID, which ties the check to its parent scheduling definition in the AMS_TRIGGERS table. The check logic itself is typically implemented by referencing marketing activity metrics via the columns CHK1_SOURCE_CODE_METRIC_ID and CHK2_SOURCE_CODE_METRIC_ID, which are foreign keys to the AMS_ACT_METRICS_ALL table. These columns store the identifiers for the metrics that will be compared (e.g., actual response rate versus a target rate). Additional columns, not fully detailed in the excerpt but implied by the table's purpose, would define the comparison operator (e.g., >, <, =) and the threshold values for the evaluation.

Common Use Cases and Queries

A primary use case is the automated governance of campaign execution. For instance, a trigger check could be configured to verify that a "Lead Generation" campaign has achieved a minimum number of qualified leads before a follow-up "Nurture" campaign is automatically launched. Common reporting and diagnostic queries involve joining this table with its related objects. To list all checks for a specific campaign trigger, a query would join AMS_TRIGGER_CHECKS to AMS_TRIGGERS. Troubleshooting a failed check would involve joining to AMS_ACT_METRICS_ALL to see the actual metric values and to AMS_TRIGGER_RESULTS to review the outcome.

  • Listing all checks for a trigger: SELECT * FROM AMS.AMS_TRIGGER_CHECKS WHERE TRIGGER_ID = <trigger_id>;
  • Finding details of checks and their results: SELECT ck.*, res.RESULT_CODE FROM AMS.AMS_TRIGGER_CHECKS ck, AMS.AMS_TRIGGER_RESULTS res WHERE ck.TRIGGER_CHECK_ID = res.TRIGGER_RESULT_FOR_ID;

Related Objects

The AMS_TRIGGER_CHECKS table is integral to a small network of objects governing marketing triggers. Its most direct relationship is with the AMS_TRIGGERS table, which defines the when (the scheduled datetime) for the check execution. It references the AMS_ACT_METRICS_ALL table twice to obtain the metric values for its comparisons. Finally, the outcomes of the executed checks are stored in the AMS_TRIGGER_RESULTS table, which uses TRIGGER_CHECK_ID as a foreign key (TRIGGER_RESULT_FOR_ID). This design creates a clear data flow: Trigger (Schedule) -> Trigger Check (Rule) -> Trigger Result (Outcome).