Results for “ams_triggers_tl”

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

Overview

AMS_TRIGGERS_TL is the translation (TL) table for the Oracle Marketing (AMS) module, residing in the AMS schema. It stores all translated (language-dependent) columns for marketing triggers — the configurable rules and criteria that drive automated marketing activities such as campaign list generation, scoring, and targeted communications. In Oracle EBS, the Marketing module maintains a base table (AMS_TRIGGERS) holding language-independent data and this companion "_TL" table holding the per-language descriptive text. Every logical trigger therefore has one row in AMS_TRIGGERS and one row per installed/active language in AMS_TRIGGERS_TL, joined on TRIGGER_ID.

From a dimensional-modeling perspective, the mined Data Vault heuristic classifies this object as satellite-leaning. This is a modeling suggestion: AMS_TRIGGERS_TL functions as a descriptive satellite attached to the AMS_TRIGGERS hub (via TRIGGER_ID), carrying time-variant descriptive attributes (the translated name and description) rather than representing an independent business entity. Its composite primary key of (TRIGGER_ID, LANGUAGE) reflects the classic satellite grain of a business key plus a qualifier.

Key Information Stored

The table documents 11 columns. The most significant are:

• TRIGGER_ID — Surrogate identifier of the parent trigger; part of the composite primary key and the foreign key to AMS_TRIGGERS.
• LANGUAGE — Language code (e.g., US, DE, FR) qualifying the translated row; the second half of the composite primary key.
• TRIGGER_NAME — The translated, user-facing name of the trigger, displayed in Marketing UI and reports for the given language.
• DESCRIPTION — The translated descriptive text explaining the trigger's purpose or behavior.
• SOURCE_LANG — The language of the source (untranslated) record, used by the multilanguage translation framework to identify the origin row.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant/security-group partitioning of the translated data.
• LAST_UPDATE_DATE — Timestamp of the most recent change to the row.
• LAST_UPATED_BY — The user who performed the last update (note: stored with this exact spelling in the documented schema).
• CREATION_DATE / CREATED_BY — Audit stamps recording row creation and creator.
• LAST_UPDATE_LOGIN — Login identifier associated with the last update, used for audit and troubleshooting.

The surrogate primary key is AMS_TRIGGERS_TL_PK over (TRIGGER_ID, LANGUAGE). There is no separate single-column business-key unique index documented; TRIGGER_ID serves as the business-key candidate linking to the parent entity.

Common Use Cases and Queries

Typical usage centers on retrieving localized trigger names and descriptions alongside the parent trigger data. A common join pattern:

• Localized trigger listing: SELECT t.trigger_id, tl.trigger_name, tl.description FROM ams_triggers t, ams_triggers_tl tl WHERE t.trigger_id = tl.trigger_id AND tl.language = USERENV('LANG');
• Translation completeness audit: identify triggers lacking rows for a given language by outer-joining AMS_TRIGGERS to AMS_TRIGGERS_TL and filtering NULL TRIGGER_NAME.
• Multilanguage reporting: pivot TRIGGER_NAME across LANGUAGE values for cross-region marketing rule catalogs.
• Security-group filtering: constrain results by SECURITY_GROUP_ID to respect data partitioning when SECURITY_GROUP_ID is populated.

Related Objects

• AMS_TRIGGERS — Parent base table; join on AMS_TRIGGERS_TL.TRIGGER_ID = AMS_TRIGGERS.TRIGGER_ID. Holds language-independent trigger definitions.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID, governing access partitioning of the translated rows.
• AMS_TRIGGERS_TL_PK — The primary key constraint (TRIGGER_ID, LANGUAGE) enforcing uniqueness.
• MLS translation views/APIs — The standard Oracle multilanguage framework views and seed/translation APIs that read and maintain TRIGGER_NAME and DESCRIPTION.

In Oracle EBS 12.1.1 and 12.2.2, AMS_TRIGGERS_TL conforms to the standard translation-table architecture, so any query against it should always include the LANGUAGE predicate to avoid returning multiple language rows for a single trigger.