Results for “plan_transaction_trigger_id”

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

Overview

QAFV_COLPLNTXNT is an APPS-owned, read-only view in the Oracle E-Business Suite Quality (QA) module. Its name abbreviates "QA Collection Plan Transaction," and it exposes the configuration of collection triggers that fire during quality plan transactions. The view answers the question of which characteristics are collected, at which point in a transaction, and under what numeric or relational conditions, for each quality plan.

The object carries the "- Retrofitted" designation in the ETRM metadata, indicating it was adapted for a later release line rather than catalogued through the standard documentation process. It is a reporting and integration construct: it joins plan, transaction, trigger, characteristic, and lookup data into a flat result set that downstream SQL, BI Publisher reports, or interface programs can read without replicating the joins themselves. Because the view is defined WITH READ ONLY, it supports query access only and cannot be used as the target of DML.

All column references are qualified in the view text, and the query and view structures are verified as VALID under both EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over a five-object join across the QA and shared lookups schemas:

• QA_PLANS (SYNONYM) — the master quality plan, aliased QP, supplying PLAN_NAME and PLAN_ID.
• QA_PLAN_TRANSACTIONS (SYNONYM) — aliased QPT, joined to QPCT on PLAN_TRANSACTION_ID and to QA_PLANS on PLAN_ID.
• QA_PLAN_COLLECTION_TRIGGERS (SYNONYM) — aliased QPCT, the central table supplying trigger and threshold data.
• QA_CHARS (SYNONYM) — aliased COLLECTION_ELEMENT, joined so that CHAR_ID equals QPCT.COLLECTION_TRIGGER_ID to resolve the characteristic name.
• MFG_LOOKUPS (VIEW) — aliased MF, restricted to LOOKUP_TYPE = 'QA_OPERATOR' and matched on LOOKUP_CODE = QPCT.OPERATOR to translate operator codes into display meanings.

The join graph is driven by QA_PLAN_COLLECTION_TRIGGERS, which links outward to the plan transaction, the characteristic, and the lookup in a single row. QA_PLANS and QA_PLAN_TRANSACTIONS form the ownership chain that scopes each trigger row to a valid plan.

Key Columns

The view exposes thirteen columns:

• PLAN_TRANSACTION_TRIGGER_ID — the primary identifier for the trigger row, sourced from QPCT.TXN_TRIGGER_ID. This is the column users typically search for when the underlying database column name TXN_TRIGGER_ID is unknown.
• PLAN_ID, PLAN_NAME — the owning quality plan and its display name.
• PLAN_TRANSACTION_ID — the plan transaction to which the trigger is attached.
• COLLECTION_ELEMENT_ID, COLLECTION_ELEMENT_NAME — the characteristic being collected, presented as both an ID and a resolved name.
• LOW_VALUE, HIGH_VALUE — the numeric bounds that the operator applies against the characteristic value.
• OPERATOR — the decoded operator meaning from MFG_LOOKUPS using lookup type QA_OPERATOR.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS audit columns carried through from QPCT.

Common Use Cases and Queries

Typical scenarios include auditing which collection elements are triggered for a given plan, comparing configured thresholds across plans, and feeding trigger definitions into reporting or migration routines. The search term "plan_transaction_trigger_id" maps directly to the view column PLAN_TRANSACTION_TRIGGER_ID, making the view the natural query target when that identifier appears in extracts or error logs. Note that the QA base tables are exposed as synonyms, so the view and its dependencies resolve correctly only from an APPS session or another schema granted access.

Retrieve all triggers for a plan:

• SELECT plan_name, collection_element_name, operator, low_value, high_value FROM qafv_colplntxnt WHERE plan_id = :p_plan_id;

Locate a specific trigger by identifier:

• SELECT plan_id, plan_transaction_id, collection_element_name, operator, low_value, high_value FROM apps.qafv_colplntxnt WHERE plan_transaction_trigger_id = :p_trigger_id;

List characteristic triggers whose upper bound exceeds a threshold:

• SELECT plan_name, collection_element_name, operator, high_value FROM apps.qafv_colplntxnt WHERE high_value > :p_limit AND operator = 'Greater Than';

Because the view is read-only, it should never appear in an INSERT or UPDATE statement; maintain trigger definitions against QA_PLAN_COLLECTION_TRIGGERS itself.