Results for “txn_trigger_id”

18 results




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

Overview

The QA_PLAN_COLLECTION_TRIGGERS table, owned by the QA schema, defines the trigger conditions attached to Quality collection plan transactions. It plays a central role in Oracle EBS Quality Management by determining when a specific collection transaction should fire automatically — for example, when process measurements cross a numeric threshold, when an operator condition evaluates true, or when a characteristic value meets defined limits. Any QA collection plan configured in EBS that relies on conditional, event-driven sampling depends on rows in this table.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as a link. That classification reflects the fact that the table primarily records associations between a collection plan transaction (QA_PLAN_TRANSACTIONS) and a characteristic definition (QA_CHARS), together with the trigger parameters that qualify the linkage. The heuristic is a modeling suggestion only; the physical table also carries descriptive attributes, so it behaves partly as a link with satellite attributes.

Key Information Stored

The table contains 14 documented columns; the most significant are described below.

  • TXN_TRIGGER_ID — Surrogate primary key, enforced by the unique index QA_PLAN_COLLECTION_TRIGGERS_PK. Together with ZD_EDITION_NAME it also forms the unique business-key candidate QA_PLAN_COLL_TRIGGERS_U1. This is typically the column referenced by the search term qa_plan_collection_triggers_pk.
  • PLAN_TRANSACTION_ID — Foreign key to QA_PLAN_TRANSACTIONS, identifying the collection plan transaction for which the trigger is defined.
  • COLLECTION_TRIGGER_ID — Foreign key to QA_CHARS, identifying the characteristic whose value drives the trigger evaluation.
  • OPERATOR — The comparison operator (for example equals, greater than, less than, between) applied against the low and high thresholds.
  • LOW_VALUE and HIGH_VALUE — Numeric or descriptive boundary values that define the trigger condition window.
  • LOW_VALUE_ID and HIGH_VALUE_ID — Surrogate references resolving the low and high values to their underlying value definitions where applicable.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns maintained by EBS.
  • ZD_EDITION_NAME — Editioning column supporting the E-Business Suite online patching / editioning model in 12.2.x.

Common Use Cases and Queries

Query and reporting uses typically revolve around auditing plan configuration, generating trigger inventory reports, and troubleshooting why a collection transaction did or did not fire.

  • Listing all triggers for a given plan transaction:

    SELECT t.txn_trigger_id, t.collection_trigger_id, t.operator, t.low_value, t.high_value
      FROM qa.qa_plan_collection_triggers t
     WHERE t.plan_transaction_id = :plan_transaction_id;

  • Joining to QA_CHARS to resolve the characteristic name and to QA_PLAN_TRANSACTIONS to resolve the owning plan.
  • Identifying triggers whose thresholds are configured with BETWEEN (low and high both populated) versus single-sided comparisons.
  • Auditing maintenance activity using LAST_UPDATED_BY and LAST_UPDATE_DATE.

Related Objects

  • QA_PLAN_TRANSACTIONS — Parent of the PLAN_TRANSACTION_ID foreign key; defines the collection transaction to which the trigger applies.
  • QA_CHARS — Parent of the COLLECTION_TRIGGER_ID foreign key; supplies the characteristic definition used to evaluate the trigger.
  • QA_PLANS — The collection plan owning the parent transactions.
  • QA_RESULTS — Stores results recorded against transactions, useful for correlating fired triggers with outcome data.
  • FND_USER — Resolves LAST_UPDATED_BY/CREATED_BY for audit reporting.
  • QA Collect Plans setup forms and the Quality public APIs — Maintain and query rows in this table during plan configuration.