Search Results ams_triggers




Overview

The AMS_TRIGGERS table is a core data object within the Oracle E-Business Suite (EBS) Marketing (AMS) module, specifically in versions 12.1.1 and 12.2.2. It functions as the central repository for defining and storing marketing triggers. In the context of Oracle Marketing, a trigger is a scheduled or event-driven mechanism designed to initiate the execution of a specific marketing activity, such as launching a campaign or a campaign element, at a predetermined time or upon meeting certain conditions. This table is fundamental to the automation and workflow capabilities of the AMS module, enabling time-based or conditional campaign execution without manual intervention.

Key Information Stored

The table's primary purpose is to define the core attributes of a marketing trigger. Its structure is anchored by the TRIGGER_ID column, which serves as the unique primary identifier. The TRIGGER_NAME and VIEW_APPLICATION_ID columns together form a unique key, ensuring trigger names are distinct within their application context. A critical column is TRIGGER_CREATED_FOR_ID, which stores the identifier of the object (like a campaign or activity metric) for which the trigger was created, linking it to the relevant marketing entity. The TIMEZONE_ID column references the HZ_TIMEZONES table, ensuring time-sensitive executions are handled correctly across geographical regions. Other columns typically found in such a table would include status, start and end dates, creation details, and the specific triggering logic or schedule reference.

Common Use Cases and Queries

Common operational and reporting scenarios involving the AMS_TRIGGERS table include auditing trigger configurations, troubleshooting campaign execution failures, and generating schedules. A frequent query pattern involves joining AMS_TRIGGERS with the AMS_CAMPAIGNS_ALL_B table to list all triggers associated with active campaigns. For example:

  • Identifying triggers for a specific campaign: SELECT t.trigger_name, t.trigger_id FROM ams_triggers t, ams_campaigns_all_b c WHERE t.trigger_created_for_id = c.campaign_id AND c.campaign_number = 'CAMPAIGN123';
  • Listing all active triggers with their associated timezone: SELECT t.trigger_name, htz.timezone_code FROM ams_triggers t, hz_timezones htz WHERE t.timezone_id = htz.timezone_id AND t.status = 'ACTIVE';
  • Investigating execution issues by joining with child tables like AMS_TRIGGER_ACTIONS or AMS_TRIGGER_CHECKS to review the trigger's defined behavior.

Related Objects

The AMS_TRIGGERS table is a central hub within the Marketing schema, with several key dependencies. It has foreign key relationships to parent tables: AMS_CAMPAIGNS_ALL_B and AMS_ACT_METRICS_ALL (via TRIGGER_CREATED_FOR_ID), and HZ_TIMEZONES (via TIMEZONE_ID). Crucially, it is referenced as a parent by multiple child tables that define a trigger's complete functionality: AMS_CAMPAIGN_SCHEDULES_B stores the execution schedule, AMS_TRIGGER_ACTIONS defines the actions to perform, and AMS_TRIGGER_CHECKS holds the conditions that must be met. The AMS_TRIGGERS_TL table provides translated descriptions for multilingual deployments. These relationships illustrate that AMS_TRIGGERS stores the header definition, while its dependent tables manage the detailed execution rules and schedules.