Results for “ams_triggers_vl”

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

Overview

AMS_TRIGGERS_VL is a marketing (AMS) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is to provide general information about Marketing triggers. In the Oracle EBS multi-language architecture, the "_VL" suffix denotes a "translated view" — a view that joins a base (non-translated) entity table to its corresponding translation table, exposing both the operational attributes of the record and its language-dependent descriptive fields as a single flattened result set. Consequently, AMS_TRIGGERS_VL acts as the language-aware access point for trigger metadata, allowing users to retrieve trigger names and descriptions in the session language while simultaneously seeing scheduling, execution, and status attributes.

Trigger records in AMS represent event-driven or scheduled marketing activities — for example, campaigns or telemarketing actions initiated at a defined date/time with a repeat schedule. The view therefore serves as a foundation for marketing trigger inquiries, list-page reports, and integration extracts that require user-readable trigger identification alongside operational detail.

Underlying Base Objects

The view text selects from two objects — AMS_TRIGGERS (aliased B, the base table) and AMS_TRIGGERS_TL (aliased TL, the translation table) — joined on TRIGGER_ID. The join is additionally constrained by TL.LANGUAGE = USERENV('LANG'), ensuring that only the translation row matching the current session language is returned. The ETRM metadata documents both as referenced SYNONYM objects under APPS. AMS_TRIGGERS holds the operational columns (IDs, audit columns, schedule dates, status flags), while AMS_TRIGGERS_TL supplies the language-dependent TRIGGER_NAME and DESCRIPTION. Because the view filters by session language, it presents exactly one translated row per trigger.

Key Columns

• TRIGGER_ID — primary identifier of the trigger; the join key between AMS_TRIGGERS and AMS_TRIGGERS_TL.
• TRIGGER_NAME, DESCRIPTION — sourced from the translation table; language-dependent labels and text.
• START_DATE_TIME, LAST_RUN_DATE_TIME, NEXT_RUN_DATE_TIME — system (database) timing values for the trigger.
• USER_START_DATE_TIME, USER_LAST_RUN_DATE_TIME, USER_NEXT_RUN_DATE_TIME, USER_REPEAT_DAILY_START_TIME, USER_REPEAT_DAILY_END_TIME, USER_REPEAT_STOP_DATE_TIME — user-facing timing values, reflecting the schedule as presented in the timezone identified by TIMEZONE_ID.
• REPEAT_FREQUENCY_TYPE, REPEAT_EVERY_X_FREQUENCY, REPEAT_DAILY_START_TIME, REPEAT_DAILY_END_TIME, REPEAT_STOP_DATE_TIME — recurrence configuration for repeating triggers.
• TRIGGERING_TYPE, VIEW_APPLICATION_ID, TRIGGER_CREATED_FOR_ID, ARC_TRIGGER_CREATED_FOR — define what the trigger is fired against and its owning application context.
• PROCESS_ID — associates the trigger with the process that created or manages it.
• TRIGGERED_STATUS, NOTIFY_FLAG, EXECUTE_SCHEDULE_FLAG, METRICS_REFRESH_TYPE, USAGE — control and state attributes governing whether and how the trigger executes and refreshes.
• OBJECT_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS who-column and optimistic locking attributes.

Common Use Cases and Queries

Typical uses include listing a campaign's triggers with their schedules, auditing triggers due to run next, and generating extracts for external scheduling systems. The following returns trigger identification together with the next scheduled run:

SELECT trigger_id, trigger_name, triggering_type, triggered_status, next_run_date_time, user_next_run_date_time, timezone_id, repeat_frequency_type FROM apps.ams_triggers_vl WHERE triggered_status = 'A' ORDER BY next_run_date_time;

Because the view resolves the translation automatically, reports can present TRIGGER_NAME and DESCRIPTION in the running user's language without additional joins. Note that no translation row for the session language means the trigger will not appear; ensure translations exist for all deployed languages before relying on the view as a complete trigger listing.