Results for “high_value”

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

Overview

QABV_COLPLNTXNT is a read-only Oracle EBS view owned by the APPS schema and shipped as part of the Quality (QA) product family. It presents collection plan transaction trigger data in a denormalized, reporting-friendly form. The name is an abbreviation of "QA Business View – Collection Plan Transaction," and its purpose is to expose the relationship between a Quality collection plan, the plan transaction defined against it, and the trigger that determines when that transaction is invoked. In ETRM 12.2.2 the view is documented as VALID and marked "- Retrofitted," indicating that the object was carried forward into the current release, with its definition maintained to preserve backward compatibility for existing reports, forms, and integrations.

The view is defined WITH READ ONLY, so it is intended strictly for query and reporting, not for DML. The user search term "plan_name" maps directly to the first column of the view, PLAN_NAME, which is sourced from QA_PLANS.NAME. This makes QABV_COLPLNTXNT a convenient entry point when a report or integration needs to resolve transaction trigger configuration starting from a human-readable plan name rather than an internal ID.

Underlying Base Objects

The documented base objects referenced by the view are:

• QA_PLANS (SYNONYM) — the collection plan header, supplying PLAN_NAME and PLAN_ID.
• QA_PLAN_TRANSACTIONS (SYNONYM) — the plan transaction, supplying the join between plan and trigger.
• QA_PLAN_COLLECTION_TRIGGERS (SYNONYM) — the trigger definition, supplying low/high values, operator, and trigger identifiers.
• MFG_LOOKUPS (VIEW) — the lookup source that decodes the trigger operator into a display meaning via LOOKUP_TYPE = 'QA_OPERATOR'.

QA_PLANS is joined to QA_PLAN_TRANSACTIONS on PLAN_ID, and QA_PLAN_TRANSACTIONS is joined to QA_PLAN_COLLECTION_TRIGGERS on PLAN_TRANSACTION_ID. MFG_LOOKUPS is joined on LOOKUP_CODE = OPERATOR, restricted to the QA_OPERATOR lookup type. The view therefore represents a three-table join plus a lookup decode, surfacing trigger detail at the plan-and-transaction grain.

Key Columns

• PLAN_NAME — the name of the Quality collection plan (QA_PLANS.NAME).
• PLAN_ID — the internal identifier of the collection plan.
• PLAN_TRANSACTION_TRIGGER_ID — the trigger identifier associated with the plan transaction.
• LOW_VALUE / HIGH_VALUE — the numeric bounds that define the trigger condition range.
• OPERATOR — the decoded operator meaning from MFG_LOOKUPS (for example, equality, greater-than, or between).
• COLLECTION_ELEMENT_ID — the collection element to which the trigger applies.
• PLAN_TRANSACTION_ID — the identifier of the plan transaction carrying the trigger.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — the standard audit columns propagated from QA_PLAN_COLLECTION_TRIGGERS.

Common Use Cases and Queries

Typical usage includes Quality reporting on which plans have transaction triggers configured, integrations that need to push trigger configuration to external systems, and troubleshooting of collection plan behavior. A representative query resolving triggers by plan name is:

• SELECT plan_name, plan_id, operator, low_value, high_value FROM apps.qabv_colplntxnt WHERE plan_name = :p_plan_name;
• SELECT plan_id, COUNT(*) FROM apps.qabv_colplntxnt GROUP BY plan_id; — counts triggers per plan.
• SELECT * FROM apps.qabv_colplntxnt WHERE operator = 'Between' AND low_value IS NOT NULL; — lists range-based triggers.

Because the view is read-only and joined across core QA tables, it can be queried safely in concurrent programs, BI Publisher data models, and ad hoc reports without risk of modifying collection plan configuration.