Search Results qa_txn_collection_triggers




Overview
Explore in AI Chat

Overview

The QA.QA_TXN_COLLECTION_TRIGGERS table is a Quality Management (QA) module configuration object in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the applicability of collection plans to Quality Collection transactions, effectively acting as the control table that determines which collection plan is triggered, and under what conditions, when a Quality transaction is created, entered, or processed. Because Oracle Quality relies on collection plans to capture specifications, results, and disposition data against a transaction, this table provides the linkage logic that connects a defined transaction type with one or more collection plans through a collection trigger identifier.

Under the heuristic Data Vault classification mined from its foreign key structure, this table is satellite-leaning. In Data Vault modeling terms, it is best treated as a descriptive satellite attached to a business key composed of the transaction number and the collection trigger, rather than as a hub or link that originates the business key. This classification is a modeling suggestion based on the FK topology, not a native Oracle construct.

Key Information Stored

The table contains thirteen documented columns. The most significant are:

The surrogate-style primary key constraint is QA_TXN_COLLECTION_TRIGGERS_PK, defined over (TRANSACTION_NUMBER, COLLECTION_TRIGGER_ID). A documented unique index, QA_TXN_COLLECTION_TRIGGERS_N1, spans (TRANSACTION_NUMBER, COLLECTION_TRIGGER_ID, ZD_EDITION_NAME), making it the business-key candidate that also accommodates the editioning column.

Common Use Cases and Queries

Typical usage includes diagnosing why a collection plan did or did not fire against a Quality transaction, reporting the active trigger configuration for a transaction type, and auditing changes to applicability rules. The ENABLED_FLAG and SEARCH_FLAG columns support filtering to only active or searchable triggers.

A representative query joining the trigger to its parent characteristic table:

  • SELECT t.transaction_number, t.collection_trigger_id, t.database_field, t.non_database_field, t.enabled_flag
  • FROM qa.qa_txn_collection_triggers t, qa.qa_chars c
  • WHERE t.collection_trigger_id = c.char_id
  • AND t.enabled_flag = 'Y'
  • AND t.zd_edition_name = 'SET1';

Because the audit columns are maintained automatically, reporting on LAST_UPDATE_DATE isolates recent configuration modifications, which is useful for change-control review.

Related Objects

  • QA_CHARS — Referenced by the COLLECTION_TRIGGER_ID foreign key; supplies the characteristic or trigger definition.
  • QA_COLLECTION_PLANS — The plan subsequently applied when a trigger matches.
  • QA_PLANS — Plan-level metadata associated with triggered collection activity.
  • QA_RESULTS — Stores collected results produced once a plan is triggered.
  • QA_TXN_COLLECTION_TRIGGERS_N1 — The unique index supporting business-key lookups including the edition column.

Applications and APIs interacting with these tables include the Quality Collection Transactions forms and the Oracle Quality public APIs, which validate trigger applicability at transaction entry.