Search Results qa_plans_v




Overview
Explore in AI Chat

Overview

QA_PLANS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, residing in the Quality (QA) product module. Its documented purpose is to "show all collection plans" — that is, every row defined in the QA_PLANS collection plan infrastructure. The view is available in both 12.1.1 and 12.2.2 and is marked VALID in the ETRM data dictionary. Because it joins base plan data to two lookup views, QA_PLANS_V resolves lookup codes into user-facing meanings rather than exposing raw coded values, which makes it suitable for direct use in reports, concurrent program output, Oracle Discoverer/BI Publisher data models, and inbound or outbound integration interfaces where descriptive plan attributes are required. The search term "spec_assignment_meaning" maps directly to one of the view's decoded columns, SPEC_ASSIGNMENT_MEANING.

Underlying Base Objects

The view is defined over the following documented base objects:

Because the WHERE clause applies inner joins to both lookup views, a plan row is only returned when its PLAN_TYPE_CODE resolves in FND_COMMON_LOOKUPS and its SPEC_ASSIGNMENT_TYPE resolves in MFG_LOOKUPS. Plans with unmaintained or NULL lookup values are therefore excluded from the result set.

Key Columns

  • ROW_ID — the QA_PLANS ROWID, enabling row-level addressing.
  • PLAN_ID, ORGANIZATION_ID — surrogate key and inventory organization context of the plan.
  • NAME, DESCRIPTION, INSTRUCTIONS — plan identification and procedural text.
  • PLAN_TYPE_CODE, PLAN_TYPE_MEANING, PLAN_TYPE_DESCRIPTION — the raw collection plan type code plus its decoded meaning and description.
  • SPEC_ASSIGNMENT_TYPE (raw code), SPEC_ASSIGNMENT_MEANING (decoded meaning) — the central column pair for the "spec_assignment_meaning" search; describes how specifications are assigned to the collection plan.
  • VIEW_NAME, IMPORT_VIEW_NAME — the database view used for data collection and for imports.
  • EFFECTIVE_FROM, EFFECTIVE_TO — the date window during which the plan is valid.
  • TEMPLATE_PLAN_ID — reference to a source template plan, when applicable.
  • JRAD_DOC_VER, ESIG_MODE — electronic records/signature configuration for the plan.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segments.
  • Standard WHO columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view supports plan discovery, reporting, and lookup-driven integration. A typical query returns decoded plan attributes filtered to the current organization:

  • List all plans and their spec assignment meanings: SELECT PLAN_ID, NAME, PLAN_TYPE_MEANING, SPEC_ASSIGNMENT_MEANING, EFFECTIVE_FROM, EFFECTIVE_TO FROM QA_PLANS_V;
  • Find plans for a specific spec assignment: SELECT PLAN_ID, NAME FROM QA_PLANS_V WHERE SPEC_ASSIGNMENT_MEANING = '&assignment';
  • Restrict to organization-active plans: SELECT PLAN_ID, NAME, PLAN_TYPE_MEANING FROM QA_PLANS_V WHERE ORGANIZATION_ID = :org_id AND SYSDATE BETWEEN EFFECTIVE_FROM AND NVL(EFFECTIVE_TO, SYSDATE + 1);

Because lookup joins are inner, integrations relying on SPEC_ASSIGNMENT_MEANING must ensure the underlying QA_PLAN_SPEC_TYPE lookup values are correctly defined. Reports keyed on the decoded meaning should prefer the raw SPEC_ASSIGNMENT_TYPE code as a stable join/filter predicate, using the meaning only for display.