Search Results insp_level_desc




Overview

APPS.QA_SAMPLING_PLANS_V is a reporting and integration view in the Oracle E-Business Suite Quality Management (QA) module. It exposes the contents of the QA_SAMPLING_PLANS base table while resolving two descriptive lookup values into human-readable meanings. Specifically, it joins QA_SAMPLING_PLANS to QA_LOOKUPS twice to translate the inspection level code and the sampling standard code into their corresponding lookup meanings. This view is the standard access point for reporting on sampling plans because it eliminates the need for callers to perform the lookup joins themselves.

The view is particularly relevant to users searching for qa_sampling_std, because the SAMPLING_STD_CODE column and its resolved description (SAMPLING_STD_DESC) are both surfaced here. Sampling plans define how many units are inspected and what acceptance criteria apply for a given inspection level and AQL (Acceptable Quality Level). The view therefore supports both transactional reporting and downstream integrations that need a denormalized, description-bearing representation of sampling plans by organization.

Underlying Base Objects

The ETRM metadata documents the view as owned by APPS and defined over two referenced objects:

  • QA_SAMPLING_PLANS (documented as a SYNONYM) — the primary table supplying sampling plan identity, inspection level code, sampling standard code, AQL, and organization context. Its alias in the view text is QSP.
  • QA_LOOKUPS (documented as a VIEW) — referenced twice under aliases QL1 and QL2 to resolve the inspection level and sampling standard codes respectively.

The join to QL1 uses an outer join ((+) operator), so a sampling plan with no matching inspection level lookup still appears, with a null inspection level description. The join to QL2 for QA_SAMPLING_STD is an inner join, meaning a sampling plan is only returned when its sampling standard code has a matching lookup entry. This asymmetry is a key behavioral characteristic when interpreting results.

Key Columns

Common Use Cases and Queries

Typical scenarios include listing all sampling plans for an organization, validating that sampling standard codes resolve to valid lookups, and feeding denormalized sampling plan data to reports or interfaces.

  • Retrieve sampling plans filtered by sampling standard:
    SELECT sampling_plan_code, description, insp_level_desc,
           sampling_std_desc, aql, organization_id
    FROM   apps.qa_sampling_plans_v
    WHERE  sampling_std_code = :p_std_code
    AND    organization_id  = :p_org_id;
  • Join back to the base table for additional attributes not exposed by the view:
    SELECT v.sampling_plan_code, v.sampling_std_desc, v.aql, p.*
    FROM   apps.qa_sampling_plans_v v,
           apps.qa_sampling_plans   p
    WHERE  v.sampling_plan_id = p.sampling_plan_id;
  • Verify lookup resolution consistency:
    SELECT sampling_plan_code, sampling_std_code, sampling_std_desc
    FROM   apps.qa_sampling_plans_v
    WHERE  sampling_std_desc IS NULL;

Because the sampling standard join is an inner join, the last query will generally return no rows unless the underlying QA_LOOKUPS view changes; it is most useful for confirming that every plan resolves correctly. Queries should always qualify the view with the APPS schema owner when executed outside a fully qualified session.