Results for “chk1_source_code”

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

Overview

AMS_TRIGGER_CHECKS is a Marketing (AMS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the set of checks to be evaluated when a date-time condition defined in AMS_TRIGGERS is reached. Each row represents a single check definition belonging to a parent trigger, and the table acts as the rule repository that the Marketing trigger-processing engine reads at evaluation time. The checks support two comparison slots (CHK1 and CHK2) combined through a configurable operator, together with references to activity metrics that supply the measured values.

The documented schema is owned by the AMS schema, is marked VALID, and contains 31 columns. The primary key is AMS_TRIGGER_CHECKS_PK, defined on TRIGGER_CHECK_ID, and the unique index AMS_TRIGGER_CHECKS_U1 also covers TRIGGER_CHECK_ID as the business-key candidate. In Data Vault terms, the mined relationship structure suggests a satellite-leaning classification, because the table records descriptive attributes about a parent trigger rather than acting as a pure hub or link. This classification is a heuristic modeling suggestion, not a physical constraint.

Key Information Stored

The columns that carry the most functional weight are:

• TRIGGER_CHECK_ID — surrogate primary key and unique-index column; the identifier users search for when tracing a specific check.
• TRIGGER_ID — foreign key to AMS_TRIGGERS, tying each check to its parent trigger definition.
• ORDER_NUMBER — sequence in which checks are evaluated within the trigger.
• CHK1_TYPE, CHK2_TYPE — the comparison types for the two check slots.
• CHK1_SOURCE_CODE, CHK2_SOURCE_CODE — source code identifiers used to resolve check values.
• CHK1_SOURCE_CODE_METRIC_ID, CHK2_SOURCE_CODE_METRIC_ID — foreign keys to AMS_ACT_METRICS_ALL that bind each slot to a metric.
• CHK1_SOURCE_CODE_METRIC_TYPE, CHK2_SOURCE_CODE_METRIC_TYPE — metric-type qualifiers for each slot.
• CHK1_TO_CHK2_OPERATOR_TYPE — the operator combining the two check slots.
• CHK2_VALUE, CHK2_LOW_VALUE, CHK2_HIGH_VALUE — literal or range thresholds for the second slot.
• CHK2_UOM_CODE, CHK2_CURRENCY_CODE — unit of measure and currency qualifiers for the second slot.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS controlling row-level access.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS concurrency and audit columns.

Common Use Cases and Queries

Typical usage centers on diagnosing why a Marketing trigger fired or failed. Administrators retrieve all checks for a trigger in evaluation order:

• SELECT trigger_check_id, order_number, chk1_type, chk2_type, chk1_to_chk2_operator_type FROM ams_trigger_checks WHERE trigger_id = :trigger_id ORDER BY order_number;
• Locate a specific check via the searched identifier: SELECT * FROM ams_trigger_checks WHERE trigger_check_id = :id;
• Join to metrics to resolve the measured values: SELECT c.trigger_check_id, m.metric_name FROM ams_trigger_checks c, ams_act_metrics_all m WHERE c.chk1_source_code_metric_id = m.metric_id;
• Reporting on security-group isolation: filter by SECURITY_GROUP_ID to validate access partitioning.

The CHK2_LOW_VALUE/HIGH_VALUE pair supports range comparisons, while UOM and currency columns qualify non-numeric metrics. Results produced by evaluating these checks are persisted separately, allowing before-and-after analysis of trigger behavior.

Related Objects

• AMS_TRIGGERS — parent object; joined on AMS_TRIGGER_CHECKS.TRIGGER_ID = AMS_TRIGGERS.TRIGGER_ID.
• AMS_ACT_METRICS_ALL — referenced twice, via CHK1_SOURCE_CODE_METRIC_ID and CHK2_SOURCE_CODE_METRIC_ID, supplying the metrics evaluated by each slot.
• AMS_TRIGGER_RESULTS — child object that references this table through TRIGGER_RESULT_FOR_ID, storing the outcome of each check execution.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for access control.
• AMS_TRIGGER_CHECKS_PK / AMS_TRIGGER_CHECKS_U1 — the primary-key constraint and unique index on TRIGGER_CHECK_ID that enforce uniqueness.

Together these objects form the trigger definition, check, and result chain used by the AMS Marketing automation engine.