Results for “arc_list_connected_to”

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

Overview

AMS_TRIGGERS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Marketing (AMS) product family and consolidates trigger definitions with the conditional checks that govern when a trigger fires. According to the documented description, the view "returns all the Trigger details and the checks and Actions associated with it," making it a single query point for trigger configuration data that would otherwise require joining multiple transactional tables.

Because it resides in the APPS schema and is exposed as a standard ETRM-documented object, AMS_TRIGGERS_V is intended for read-only consumption. It is commonly used in custom reports, concurrent programs, and integration extracts where trigger scheduling, repeat frequency, metric thresholds, and check logic must be retrieved without touching base tables directly. The documented status is VALID, indicating the view compiles successfully against its underlying objects.

Underlying Base Objects

The documented view metadata lists four referenced objects: AMS_TRIGGERS_VL (VIEW), AMS_TRIGGER_CHECKS (SYNONYM), AMS_UTILITY_PVT (PACKAGE), and HZ_TIMEZONES (SYNONYM). The view definition joins AMS_TRIGGERS_VL (aliased B) to AMS_TRIGGER_CHECKS (aliased C) on TRIGGER_ID, and joins HZ_TIMEZONES (aliased H) for timezone name resolution. AMS_UTILITY_PVT is invoked through the GET_LOOKUP_MEANING function to translate the TRIGGERING_TYPE lookup code into a meaningful display name.

The join on TRIGGER_ID means each row represents one trigger-check combination. AMS_TRIGGERS_VL supplies the trigger header attributes, while AMS_TRIGGER_CHECKS supplies the check-side attributes (CHK1 and CHK2 columns). This is a materially different grain than AMS_TRIGGERS, so consumers must account for the one-to-many relationship between a trigger and its checks.

Key Columns

• TRIGGER_ID / TRIGGER_CHECK_ID – Identifiers linking the trigger header and its associated check row; ROW_ID is derived from the B-side row.
• TRIGGER_NAME / TRIGGERING_TYPE / TRIGGERING_TYPE_NAME – Trigger identity plus the lookup code and its decoded meaning via AMS_UTILITY_PVT.GET_LOOKUP_MEANING.
• CHK1_TYPE / CHK1_SOURCE_CODE / CHK1_SOURCE_CODE_METRIC_ID / CHK1_SOURCE_CODE_METRIC_TYPE – Define the first condition, including its source code and referenced metric. The user-searched column CHK2_SOURCE_CODE_METRIC_ID appears in the same family for the second condition.
• CHK2_TYPE / CHK2_SOURCE_CODE_METRIC_ID / CHK2_SOURCE_CODE_METRIC_TYPE – Define the second condition and its metric reference, used in compound trigger logic.
• CHK1_TO_CHK2_OPERATOR_TYPE – The logical operator (such as AND/OR) combining CHK1 and CHK2.
• CHK2_VALUE / CHK2_LOW_VALUE / CHK2_HIGH_VALUE – Threshold values and ranges evaluated by the second check.
• CHK2_UOM_CODE / CHK2_CURRENCY_CODE – Unit of measure and currency context for numeric comparisons.
• USER_START_DATE_TIME / USER_LAST_RUN_DATE_TIME / USER_NEXT_RUN_DATE_TIME / REPEAT_FREQUENCY_TYPE / REPEAT_EVERY_X_FREQUENCY – Scheduling attributes governing trigger execution frequency, plus METRICS_REFRESH_TYPE.
• GLOBAL_TIMEZONE_NAME – Timezone name sourced from HZ_TIMEZONES.
• ACTION_* columns – Declared as NULL in the view text, so action data is not returned by this view despite the description.

Common Use Cases and Queries

A frequent scenario is retrieving all checks associated with a trigger, including the metric referenced in each check. Because the searched identifier is a metric column, a targeted SELECT is typical:

• SELECT TRIGGER_ID, TRIGGER_NAME, CHK1_SOURCE_CODE_METRIC_ID, CHK1_SOURCE_CODE_METRIC_TYPE, CHK2_SOURCE_CODE_METRIC_ID, CHK2_SOURCE_CODE_METRIC_TYPE FROM AMS_TRIGGERS_V WHERE CHK2_SOURCE_CODE_METRIC_ID IS NOT NULL;
• SELECT TRIGGER_NAME, TRIGGERING_TYPE_NAME, CHK1_TYPE, CHK2_TYPE, CHK1_TO_CHK2_OPERATOR_TYPE FROM AMS_TRIGGERS_V ORDER BY TRIGGER_NAME;
• SELECT TRIGGER_ID, CHK2_LOW_VALUE, CHK2_HIGH_VALUE, CHK2_UOM_CODE, CHK2_CURRENCY_CODE FROM AMS_TRIGGERS_V WHERE CHK2_TYPE IS NOT NULL;

Another use is scheduling analysis, where USER_NEXT_RUN_DATE_TIME and REPEAT_FREQUENCY_TYPE drive dashboards monitoring upcoming trigger executions. Filtering on TRIGGERING_TYPE links reports to specific trigger categories. Because action columns are NULL, integrations requiring action detail must query the action-side objects separately. All access should be read-only, and prudent practice calls for qualifying columns explicitly when joining the view to other AMS objects.