Results for “qa_plans_val_v”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
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:
- QA_PLANS (SYNONYM) — the driving table (aliased QP) containing all collection plan records, including plan type, effective dates, instructions, view name, specification assignment type, descriptive flexfield attributes, template plan reference, and e-signature mode.
- FND_COMMON_LOOKUPS (VIEW) — aliased FL; joined on QP.PLAN_TYPE_CODE = FL.LOOKUP_CODE with APPLICATION_ID = 250 and LOOKUP_TYPE = 'COLLECTION_PLAN_TYPE' to resolve the plan type meaning and description.
- MFG_LOOKUPS (VIEW) — aliased ML3; joined on QP.SPEC_ASSIGNMENT_TYPE = ML3.LOOKUP_CODE with LOOKUP_TYPE = 'QA_PLAN_SPEC_TYPE' to resolve the specification assignment meaning.
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:
- ROW_ID — the rowid of the base QA_PLANS row, useful for direct base-table updates or navigation.
- PLAN_ID — the unique identifier of the collection plan; the primary join key to child tables such as QA_PLAN_CHARACTERISTICS and QA_PLAN_ELEMENT_VALUES.
- ORGANIZATION_ID — the inventory organization that owns the plan.
- NAME / DESCRIPTION — the user-facing plan name and description.
- PLAN_TYPE_CODE, PLAN_TYPE_MEANING, PLAN_TYPE_DESCRIPTION — the plan type code plus its FND_COMMON_LOOKUPS meaning and description.
- EFFECTIVE_FROM / EFFECTIVE_TO — the validity window evaluated by the WHERE clause against TRUNC(SYSDATE).
- SPEC_ASSIGNMENT_TYPE and SPEC_ASSIGNMENT_MEANING — the specification assignment type and its MFG_LOOKUPS meaning.
- INSTRUCTIONS, VIEW_NAME — operator instructions and the associated folder/view definition.
- TEMPLATE_PLAN_ID — reference to a template plan, if the plan was created from one.
- ESIG_MODE — the electronic signature mode applied to results entry.
- ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the descriptive flexfield context and segments.
- Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
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.
-
View: QA_PLANS_VAL_V 12.2.2
Shows valid collection plans
APPS.QA_PLANS_VAL_V·↳ FND_COMMON_LOOKUPS·↳ FND_GLOBAL·↳ MFG_LOOKUPS·Explore QA module →
-
View: QA_PLANS_VAL_V 12.1.1
Shows valid collection plans
APPS.QA_PLANS_VAL_V·↳ FND_COMMON_LOOKUPS·↳ FND_GLOBAL·↳ MFG_LOOKUPS·Explore QA module →
-
VIEW: APPS.QA_PLANS_VAL_V 12.1.1
-
VIEW: APPS.QA_PLANS_VAL_V 12.2.2
-
View: MTL_GENEALOGY_QA_DATA 12.2.2
APPS.MTL_GENEALOGY_QA_DATA·↳ FND_GLOBAL·↳ QA_PLANS_VAL_V·↳ QA_RESULTS_VAL_V·Explore INV module →
-
View: MTL_GENEALOGY_QA_DATA 12.1.1
APPS.MTL_GENEALOGY_QA_DATA·↳ FND_GLOBAL·↳ QA_PLANS_VAL_V·↳ QA_RESULTS_VAL_V·Explore INV module →
-
This is the view corresponding to QA_GRANTED_PRIVILEGES
APPS.QA_GRANTED_PRIVILEGES_V·↳ FND_GLOBAL·↳ HZ_PARTIES·↳ QA_GRANTED_PRIVILEGES·Explore QA module →
-
This is the view corresponding to QA_GRANTED_PRIVILEGES
APPS.QA_GRANTED_PRIVILEGES_V·↳ FND_GLOBAL·↳ HZ_PARTIES·↳ QA_GRANTED_PRIVILEGES·Explore QA module →
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
View to retrieve the deferral and unit effectivity details.
APPS.AHL_UE_DEFERRAL_DETAILS_V·↳ AHL_MR_HEADERS_V·↳ AHL_UNIT_DEFERRALS_B·↳ AHL_UNIT_EFFECTIVITIES_APP_V·Explore AHL module →
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
View to retrieve the deferral and unit effectivity details.
APPS.AHL_UE_DEFERRAL_DETAILS_V·↳ AHL_MR_HEADERS_V·↳ AHL_UNIT_DEFERRALS_B·↳ AHL_UNIT_EFFECTIVITIES_APP_V·Explore AHL module →
-
View: AHL_WORKORDERS_V 12.1.1
Workorders View for Production Module Restricted by Operating Unit id. Restriction for masterworkorders and workorders created for costing
APPS.AHL_WORKORDERS_V·↳ AHL_COMPLETIONS_PVT·↳ AHL_MR_HEADERS_B·↳ AHL_MR_ROUTES_APP_V·Explore AHL module →
-
SYNONYM: APPS.QA_PLANS 12.2.2
-
View: AHL_ALL_WORKORDERS_V 12.2.2
Workorders View for Production Module Restricted by Operating Unit id. No restriction for masterworkorders and workorders created for costing
APPS.AHL_ALL_WORKORDERS_V·↳ AHL_COMPLETIONS_PVT·↳ AHL_MR_HEADERS_B·↳ AHL_MR_ROUTES_APP_V·Explore AHL module →
-
View: AHL_ALL_WORKORDERS_V 12.1.1
Workorders View for Production Module Restricted by Operating Unit id. No restriction for masterworkorders and workorders created for costing
APPS.AHL_ALL_WORKORDERS_V·↳ AHL_COMPLETIONS_PVT·↳ AHL_MR_HEADERS_B·↳ AHL_MR_ROUTES_APP_V·Explore AHL module →