Search Results ams_trigger_results_pk

Overview

The AMS_TRIGGER_RESULTS table is a core data repository within the Oracle E-Business Suite Marketing (AMS) module, specifically for versions 12.1.1 and 12.2.2. Its primary function is to log the outcomes of automated marketing processes. As indicated in the ETRM documentation, this table stores the results after a threshold check or action has been run. It acts as an audit and tracking mechanism for the marketing automation engine, capturing the success, failure, or specific outcome data generated when predefined business rules (triggers) are evaluated and executed. This data is critical for analyzing campaign performance, debugging automation workflows, and ensuring the integrity of marketing operations.

Key Information Stored

The table's structure is designed to capture the essential details of a trigger execution event. The primary key, TRIGGER_RESULT_ID, uniquely identifies each result record. A pivotal column is TRIGGER_RESULT_FOR_ID, which serves as a foreign key to link the result to its originating entity. Based on the provided foreign key relationships, this column can reference either a specific check from the AMS_TRIGGER_CHECKS table or a specific action from the AMS_TRIGGER_ACTIONS table. While the full column list is not detailed in the excerpt, typical data stored would include timestamps (creation date), status codes (e.g., 'SUCCESS', 'ERROR'), result messages or error descriptions, identifiers for the related campaign or activity, and any relevant output data from the check or action process.

Common Use Cases and Queries

This table is central to operational reporting and troubleshooting within Marketing automation. Common use cases include auditing the execution history of marketing triggers, identifying failed processes for corrective action, and generating reports on campaign automation effectiveness. A typical query would join AMS_TRIGGER_RESULTS to its parent tables to get a complete picture of what was executed and the outcome.

Sample Query Pattern:
SELECT atr.trigger_result_id,
       atr.creation_date,
       atr.result_status,
       atc.check_name,
       ata.action_name
FROM ams.ams_trigger_results atr
LEFT JOIN ams.ams_trigger_checks atc ON atr.trigger_result_for_id = atc.trigger_check_id
LEFT JOIN ams.ams_trigger_actions ata ON atr.trigger_result_for_id = ata.trigger_action_id
WHERE atr.creation_date > SYSDATE - 7
ORDER BY atr.creation_date DESC;

Related Objects

The AMS_TRIGGER_RESULTS table has defined foreign key relationships with two primary parent tables, as documented in the ETRM metadata:

• AMS_TRIGGER_CHECKS: The result record is linked via the column AMS_TRIGGER_RESULTS.TRIGGER_RESULT_FOR_ID to a record in AMS_TRIGGER_CHECKS. This relationship stores the outcome of a threshold or condition evaluation.
• AMS_TRIGGER_ACTIONS: Similarly, the AMS_TRIGGER_RESULTS.TRIGGER_RESULT_FOR_ID column can also reference a record in AMS_TRIGGER_ACTIONS. This relationship stores the outcome of an executed marketing action, such as sending an email or updating a score.

These relationships are enforced by the foreign key constraints and share the same linking column (TRIGGER_RESULT_FOR_ID), indicating the table's design to polymorphically store results for different types of trigger components. The primary key constraint AMS_TRIGGER_RESULTS_PK on TRIGGER_RESULT_ID ensures the uniqueness of each logged result.