Search Results insp_level_code

Overview

The APPS.QA_SAMPLING_PLANS_V view is a reporting and integration layer within the Oracle E-Business Suite Quality (QA) module. It exposes the definition of sampling plans used during quality inspection and data collection activities. A sampling plan in Oracle Quality determines how many units are drawn from a lot or batch for inspection, the acceptable quality level (AQL) applied to the decision, the inspection severity level, and the sampling standard that governs the plan. By denormalizing lookup codes into readable descriptions, this view provides a single, query-friendly source for reporting on sampling plan configuration across an organization.

The view is owned by the APPS schema and carries a VALID status in both 12.1.1 and 12.2.2. Because it is a view rather than a table, it carries no storage of its own and reflects the current state of the underlying configuration tables on every query.

Underlying Base Objects

Per the ETRM metadata, QA_SAMPLING_PLANS_V is defined over two referenced objects: the QA_SAMPLING_PLANS synonym and the QA_LOOKUPS view. The core data originates from QA_SAMPLING_PLANS, which stores the sampling plan records, while QA_LOOKUPS is joined twice to resolve code values into their displayed meanings. The first lookup join (QL1) maps INSP_LEVEL_CODE against LOOKUP_TYPE 'QA_SAMPLING_INSP_LEVEL'; the second (QL2) maps SAMPLING_STD_CODE against LOOKUP_TYPE 'QA_SAMPLING_STD'. Both joins are performed with Oracle outer-join syntax (QL1 with the (+)= operator, and QL2 with the legacy equality form), so plans without a matching lookup still appear, though the second join condition should be treated with the same null-tolerant intent. The view additionally selects QSP.ROWID as ROW_ID, giving each row a pseudo-unique identifier suitable for row-based navigation logic.

Key Columns

• ROW_ID — the ROWID of the underlying QA_SAMPLING_PLANS row.
• SAMPLING_PLAN_ID — the system-generated primary key of the sampling plan.
• SAMPLING_PLAN_CODE — the user-defined identifier for the plan.
• DESCRIPTION — textual description of the sampling plan.
• INSP_LEVEL_CODE / INSP_LEVEL_DESC — the inspection level code and its lookup meaning.
• SAMPLING_STD_CODE / SAMPLING_STD_DESC — the sampling standard code and its lookup meaning. This is the column most directly associated with the search term "sampling_std_code," and it is the join key to QA_LOOKUPS for the 'QA_SAMPLING_STD' lookup type.
• AQL — the acceptable quality level associated with the plan.
• ORGANIZATION_ID — the inventory organization to which the plan belongs.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN support audit and change-tracking reporting.

Common Use Cases and Queries

Typical uses include validating sampling plan setup before inspections run, reporting on plans by standard or inspection level, and feeding downstream integration or analytics. Because SAMPLING_STD_CODE is often the search target, a common query filters on that column directly:

SELECT sampling_plan_code, description, sampling_std_code, sampling_std_desc, aql
FROM apps.qa_sampling_plans_v
WHERE sampling_std_code = :p_std_code;

Reporting by organization with readable descriptions is equally straightforward:

SELECT organization_id, sampling_plan_code, insp_level_desc, sampling_std_desc, aql
FROM apps.qa_sampling_plans_v
ORDER BY organization_id, sampling_plan_code;

For audit review, restrict on the creation or update timestamps. Because the view resolves lookup descriptions at query time, reports remain consistent with current lookup configuration without requiring custom decode logic.