Results for “chk2_high_value”

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

Overview

The AMS_TRIGGER_RESULTS table is a core transactional object within the Oracle Marketing (AMS) module of Oracle E-Business Suite, available in both release 12.1.1 and 12.2.2. It stores the results produced after a threshold check or an automated action has executed against a marketing object. In the Oracle Marketing trigger framework, campaigns, offers, and one-to-one marketing programs define runtime conditions — expressed as checks on attribute values such as revenue, order counts, or customer behavior — along with actions to be fired when those conditions are satisfied. Each time the trigger engine evaluates a check or fires an action, a row is inserted into AMS_TRIGGER_RESULTS to record the outcome, the values inspected, the comparison operator applied, and whether any associated action succeeded.

The object resides in the AMS schema and is owned by the Marketing product. Its primary key, AMS_TRIGGER_RESULTS_PK, is defined on TRIGGER_RESULT_ID. The documented physical schema contains 19 columns, and a unique index, AMS_TRIGGER_RESULTS_U1, exists on TRIGGER_RESULT_ID, confirming that column as the business-key candidate in addition to its role as the surrogate primary key. Based on the foreign key structure — a single link-column (TRIGGER_RESULT_FOR_ID) that resolves to more than one parent — the ETRM heuristic classification suggests this table be modeled as a Data Vault link, representing the association between a result record and its originating check or action. This is a modeling suggestion rather than a mandated design.

Key Information Stored

The following columns are the most operationally significant for interpreting trigger output:

• TRIGGER_RESULT_ID — Surrogate primary key and the documented unique business key (AMS_TRIGGER_RESULTS_U1).
• TRIGGER_RESULT_FOR_ID — FK discriminator pointing to the originating check (AMS_TRIGGER_CHECKS) or action (AMS_TRIGGER_ACTIONS) that produced the result.
• ARC_TRIGGER_RESULT_FOR — Denormalized/archive discriminator identifying which parent entity the result pertains to.
• TRIGGER_FINISH_TIME — Timestamp recording completion of the threshold evaluation or action.
• CHK1_CHECKED_VALUE, CHK2_CHECKED_VALUE, CHK2_HIGH_VALUE — The evaluated values forming the left/right operands and upper bound of the threshold comparison (for example, a range check between CHK1 and CHK2).
• CHK1_TO_CHK2_OPERATOR_TYPE — The relational operator applied between the checked values.
• CHECK_MET_FLAG — Indicates whether the threshold condition was satisfied.
• PROCESS_SUCCESS_FLAG — Indicates whether the triggering process completed successfully.
• ACTIONS_PERFORMED — Records the actions taken following the check outcome.
• SECURITY_GROUP_ID — Multi-org access control, FK to FND_SECURITY_GROUPS.
• NOTIFIED_USER — The user or recipient notified upon trigger completion.
• Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical uses include auditing which marketing thresholds fired, diagnosing failed actions, and reporting on campaign responsiveness. A representative query joining results to their originating check or action:

SELECT r.TRIGGER_RESULT_ID, r.TRIGGER_RESULT_FOR_ID, r.TRIGGER_FINISH_TIME, r.CHK1_CHECKED_VALUE, r.CHK2_CHECKED_VALUE, r.CHECK_MET_FLAG, r.PROCESS_SUCCESS_FLAG, r.ACTIONS_PERFORMED FROM AMS.AMS_TRIGGER_RESULTS r WHERE r.CHECK_MET_FLAG = 'Y' AND r.TRIGGER_FINISH_TIME >= :p_from_date;

Because TRIGGER_RESULT_FOR_ID is polymorphic (linking to either checks or actions), analysts commonly filter using TRIGGER_RESULT_FOR_ID or ARC_TRIGGER_RESULT_FOR to scope results to a specific parent. Reporting scenarios include threshold-satisfaction trends, action-execution success rates, and user-notification audits via NOTIFIED_USER.

Related Objects

• AMS_TRIGGER_CHECKS — Parent table; join on AMS_TRIGGER_RESULTS.TRIGGER_RESULT_FOR_ID = AMS_TRIGGER_CHECKS primary key.
• AMS_TRIGGER_ACTIONS — Parent table for action-driven results; join on the same TRIGGER_RESULT_FOR_ID.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for multi-org security.
• AMS_TRIGGER_RESULTS_PK / AMS_TRIGGER_RESULTS_U1 — Primary key constraint and unique index on TRIGGER_RESULT_ID.

Together these objects form the persistence and audit layer of the Oracle Marketing trigger engine.