Results for “qa_operator”

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

Overview

APPS.QABV_COLPLNTXNT is a read-only Oracle EBS view in the Quality Management (QA) module that exposes collection trigger definitions associated with quality plans and plan transactions. In EBS 12.1.1 and 12.2.2 this view is a denormalized reporting aid: it joins collection element trigger rows to the parent quality plan and plan transaction, then resolves the trigger's operator code into a user-readable meaning by way of the QA_OPERATOR lookup type in MFG_LOOKUPS. Rather than presenting raw lookup codes, the view surfaces the translated operator value (for example, a comparison operator such as "Between" or "Equal To"), which makes it suitable for operational reporting, ad hoc analysis, and interface extraction where a human-readable label is required.

The view is defined with the WITH READ ONLY clause, so it cannot be used for data manipulation; it is strictly a query object. Its naming reflects its purpose: "COL" for collection, "PLN" for plan, and "TXNT" for transaction, indicating the collection/plan/transaction intersection it materializes.

Underlying Base Objects

The view is owned by APPS and is defined over four referenced objects:

• QA_PLANS (synonym) — the quality plan header, supplying the plan name and plan identifier.
• QA_PLAN_TRANSACTIONS (synonym) — the transaction definition linked to a plan, supplying the plan-to-transaction association and plan transaction ID.
• QA_PLAN_COLLECTION_TRIGGERS (synonym) — the trigger records that bind a collection element to a plan transaction, including low/high boundary values and the operator code.
• MFG_LOOKUPS (view) — the user-extensible lookup source that maps QA_OPERATOR lookup codes to their display meanings.

The joins follow the QA hierarchy: QA_PLANS.PLAN_ID = QA_PLAN_TRANSACTIONS.PLAN_ID, QA_PLAN_TRANSACTIONS.PLAN_TRANSACTION_ID = QA_PLAN_COLLECTION_TRIGGERS.PLAN_TRANSACTION_ID, and the lookup resolution filters on LOOKUP_TYPE = 'QA_OPERATOR' with LOOKUP_CODE equal to the stored operator code.

Key Columns

• PLAN_NAME / PLAN_ID — the quality plan and its surrogate key.
• PLAN_TRANSACTION_TRIGGER_ID — the transaction trigger identifier (alias of TXN_TRIGGER_ID).
• LOW_VALUE / HIGH_VALUE — the numeric or range boundaries defining when the trigger fires, commonly used with range operators.
• OPERATOR — the resolved meaning of the QA_OPERATOR lookup code, providing the comparison semantics for the boundary values.
• COLLECTION_ELEMENT_ID — the collection element associated with the trigger (alias of COLLECTION_TRIGGER_ID).
• PLAN_TRANSACTION_ID — the originating plan transaction linking trigger to plan.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY provide EBS standard who-columns for change tracking.

Common Use Cases and Queries

Typical scenarios include extracting trigger configurations for a given plan, auditing which collection elements use range-based operators, and feeding boundary definitions into downstream quality or integration processes. Because the operator is already translated, reports avoid an additional lookup join.

Sample query listing triggers for a named plan:

SELECT plan_name, plan_id, collection_element_id,
       low_value, high_value, operator
FROM   apps.qabv_colplntxnt
WHERE  plan_name = :plan_name
ORDER  BY collection_element_id;

Sample query isolating boundary (range) triggers:

SELECT plan_id, plan_transaction_id, collection_element_id,
       low_value, high_value, operator
FROM   apps.qabv_colplntxnt
WHERE  operator IN ('Between')
   OR  (low_value IS NOT NULL AND high_value IS NOT NULL);

Because the view is read-only and joins four objects, queries should be constrained on PLAN_ID or PLAN_TRANSACTION_ID where possible to avoid broad scans across QA_PLAN_COLLECTION_TRIGGERS and the MFG_LOOKUPS lookup resolution.