Search Results qa_plans_val_v




Overview
Explore in AI Chat

Overview

QA_PLANS_VAL_V is a VALID Oracle E-Business Suite view owned by the APPS schema and registered under the QA – Quality product. Its purpose, as documented in the ETRM metadata, is to present valid collection plans — that is, collection plans whose effective dating window currently includes the system date. In Oracle Quality, a collection plan defines the data elements, specifications, and actions used to capture and evaluate quality results against items, lots, or jobs. Because collection plans can be assigned validity periods through the EFFECTIVE_FROM and EFFECTIVE_TO columns, this view provides a filtered, denormalized projection of QA_PLANS restricted to plans that are active "as of today." Applications, reports, and integrations that must not reference expired or future-dated plans query this view rather than the base synonym.

Underlying Base Objects

The view is defined with a join between QA_PLANS (accessed via a SYNONYM in the APPS schema) and two lookup sources. It also references FND_GLOBAL as a documented dependency, although FND_GLOBAL is not explicitly joined in the view text shown; FND_GLOBAL (PACKAGE) is commonly invoked indirectly for session context such as organization or user identification. The documented base objects are:

Note that lookups for plan type are drawn from the Foundation common lookups (application 250), while specification assignment lookups come from the Manufacturing lookups view — a mixed-lookup pattern typical of Quality module views.

Key Columns

The view exposes the full QA_PLANS column set plus lookup-resolved descriptions. Important columns include:

Common Use Cases and Queries

Typical consumers are QA reports, LOV queries in results entry, and integrations that import or validate collection plan metadata. A simple listing of currently valid plans looks like:

SELECT plan_id, organization_id, name, plan_type_meaning, effective_from, effective_to FROM qa_plans_val_v WHERE organization_id = :org_id ORDER BY name;

To find plans of a particular type in a given organization:

SELECT plan_id, name, spec_assignment_meaning FROM qa_plans_val_v WHERE plan_type_code = 'STANDARD' AND organization_id = :org_id;

To locate plans nearing expiry within a specific window:

SELECT plan_id, name, effective_to FROM qa_plans_val_v WHERE effective_to BETWEEN TRUNC(SYSDATE) AND TRUNC(SYSDATE) + 30;

Because the view already enforces the effective-dating predicate, developers should avoid re-implementing that filter against QA_PLANS; instead, query QA_PLANS_VAL_V when "valid as of today" semantics are required.