Search Results mail_sender_name




Overview
Explore in AI Chat

Overview

AMS_TRIGGER_ACTIONS is a Marketing (AMS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores all actions that can be performed when a particular trigger fires. Within Oracle Advanced Marketing, triggers represent event-driven conditions—such as a customer milestone, a list membership change, or a campaign response—and this table defines the actionable responses configured against each trigger. Each row describes a single action, its execution mode, approval requirements, and any associated deliverable, offer, or list artifact.

From a Data Vault modeling perspective, the mined heuristic classification of AMS_TRIGGER_ACTIONS is satellite-leaning. This suggests the table behaves primarily as a descriptive satellite attached to a parent trigger hub, carrying the attribute detail of configured actions rather than acting as an independent business key hub or a pure link between entities. The multiple foreign keys to AMS_TRIGGERS, AMS_LIST_HEADERS_ALL, AMS_ACT_OFFERS, AMS_DELIVERABLES_ALL_B, and other reference tables reinforce this satellite interpretation, since the table captures context and attributes for actions belonging to a trigger.

Key Information Stored

The table is defined in the AMS schema with 28 documented columns. Its surrogate primary key is TRIGGER_ACTION_ID, enforced by the AMS_TRIGGER_ACTIONS_PK constraint and mirrored by the unique index AMS_TRIGGER_ACTIONS_U1. This identifier uniquely distinguishes each configured action and is the candidate business key exposed through the unique index.

Common Use Cases and Queries

Typical usage centers on inspecting and validating trigger configurations. Marketing administrators review which actions are attached to a trigger, their order, and whether approvals are required. Reporting queries frequently join to AMS_TRIGGERS and AMS_ACT_OFFERS to produce an action inventory, while integration logic reads EXECUTE_ACTION_TYPE and PROGRAM_TO_CALL to determine execution behavior.

  • Action inventory per trigger: join AMS_TRIGGER_ACTIONS to AMS_TRIGGERS on TRIGGER_ID.
  • Approval routing analysis: join to JTF_RS_RESOURCE_EXTNS on ACTION_APPROVER_USER_ID.
  • Offer and deliverable dependency reporting: join to AMS_ACT_OFFERS and AMS_DELIVERABLES_ALL_B.
  • Action outcome tracking: join to AMS_TRIGGER_RESULTS on TRIGGER_RESULT_FOR_ID = TRIGGER_ACTION_ID.

A representative query shape is SELECT ta.trigger_action_id, ta.trigger_id, ta.order_number, ta.execute_action_type FROM ams.ams_trigger_actions ta WHERE ta.trigger_id = :trigger_id ORDER BY ta.order_number;

Related Objects

The most significant related objects, based on documented foreign key relationships, are the following.

  • AMS_TRIGGERS — parent trigger definition; joined via TRIGGER_ID.
  • AMS_TRIGGER_RESULTS — downstream result records referencing this table via TRIGGER_RESULT_FOR_ID.
  • AMS_ACT_OFFERS — linked by ACTIVITY_OFFER_ID.
  • AMS_DELIVERABLES_ALL_B — linked by DELIVERABLE_ID.
  • AMS_LIST_HEADERS_ALL — linked by LIST_HEADER_ID.
  • JTF_RS_RESOURCE_EXTNS — approver resource via ACTION_APPROVER_USER_ID.
  • FND_SECURITY_GROUPS — security partitioning via SECURITY_GROUP_ID.
  • GR_COVER_LETTERS_B — cover letter reference via COVER_LETTER_ID.