Results for “low_value_lookup”

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

Overview

QA_CHAR_ACTION_TRIGGERS is a Quality (QA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that defines the action triggers, or rules, associated with collection elements (quality characteristics). In the Oracle Quality data model, a quality characteristic (stored in QA_CHARS) can drive automated actions — such as launching a notification, generating a work order, or invoking a concurrent program — when collected values satisfy a defined condition. QA_CHAR_ACTION_TRIGGERS stores the rule definition itself, including the comparison operator and the boundary values that the trigger evaluates against.

From a dimensional modeling perspective, the ETRM metadata classifies this table heuristically as satellite-leaning. This reflects its role as a dependent, descriptive extension of a parent entity (QA_CHARS) rather than an independent transaction hub or a resolution link. The classification should be treated as a modeling suggestion: QA_CHAR_ACTION_TRIGGERS carries attribute-style rule data keyed to a characteristic, and it is in turn referenced by QA_CHAR_ACTIONS.

Key Information Stored

The table is owned by the QA schema and contains 15 documented columns. The single-column primary key is CHAR_ACTION_TRIGGER_ID, enforced by QA_CHAR_ACTION_TRIGGERS_PK and mirrored by the unique index QA_CHAR_ACTION_TRIGGERS_U1. This surrogate identifier is the value carried into QA_CHAR_ACTIONS as the foreign key.

• CHAR_ACTION_TRIGGER_ID — surrogate primary key identifying each action trigger rule.
• CHAR_ID — foreign key to QA_CHARS, binding the rule to the quality characteristic (collection element) it governs.
• TRIGGER_SEQUENCE — ordering of rule evaluation when multiple triggers exist for the same characteristic.
• OPERATOR — the comparison operator applied when evaluating collected values (for example, equality or range comparisons).
• LOW_VALUE_LOOKUP, LOW_VALUE_OTHER, LOW_VALUE_OTHER_ID — the lower boundary of the rule condition, expressed either as a lookup reference or as a literal/other value with its identifier.
• HIGH_VALUE_LOOKUP, HIGH_VALUE_OTHER, HIGH_VALUE_OTHER_ID — the corresponding upper boundary of the rule condition.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide audit tracking.

The CHAR_ID foreign key to QA_CHARS is the business-key candidate of significance; because a characteristic may carry several triggers, CHAR_ID is not itself unique on this table.

Common Use Cases and Queries

The primary use case is rule maintenance and auditing: identifying which characteristics have action triggers, in what sequence they evaluate, and the exact boundaries applied. A typical query joins the trigger to its characteristic:

• SELECT t.char_action_trigger_id, t.char_id, t.trigger_sequence, t.operator, t.low_value_other, t.high_value_other FROM qa.qa_char_action_triggers t WHERE t.char_id = :characteristic_id ORDER BY t.trigger_sequence;
• Reporting triggers configured per characteristic: SELECT c.char_id, c.name, COUNT(t.char_action_trigger_id) FROM qa.qa_chars c LEFT JOIN qa.qa_char_action_triggers t ON t.char_id = c.char_id GROUP BY c.char_id, c.name;
• Reconciling trigger rules against the actions they spawn by joining to QA_CHAR_ACTIONS on CHAR_ACTION_TRIGGER_ID.
• Migration or setup validation by extracting all triggers for a given collection plan's characteristics.

These queries support setup validation, impact analysis before changing a characteristic, and audit reporting on automated quality actions.

Related Objects

• QA_CHARS — parent characteristic table; joined on QA_CHAR_ACTION_TRIGGERS.CHAR_ID = QA_CHARS.CHAR_ID.
• QA_CHAR_ACTIONS — child table holding the actions spawned by a trigger; joined on QA_CHAR_ACTIONS.CHAR_ACTION_TRIGGER_ID = QA_CHAR_ACTION_TRIGGERS.CHAR_ACTION_TRIGGER_ID.
• QA_CHAR_ACTION_TRIGGERS_PK and QA_CHAR_ACTION_TRIGGERS_U1 — the primary key constraint and unique index enforcing CHAR_ACTION_TRIGGER_ID.
• Collection element and collection plan tables in the QA module, which reference QA_CHARS and therefore transitively depend on the trigger definitions.