Search Results sampling_plan_code




Overview
Explore in AI Chat

Overview

The QA_SAMPLING_RCV_CRITERIA_V view is a Quality (QA) module reporting object that presents the sampling criteria defined for receiving inspection in Oracle E-Business Suite. It consolidates the receiving sampling criteria records stored in QA_SL_SP_RCV_CRITERIA with their associated sampling plans, vendors, items, categories, projects, and tasks into a single denormalized, user-friendly result set. In both Oracle EBS 12.1.1 and 12.2.2 the object resides in the APPS schema with VALID status.

The view allows users and integrators to resolve the technical foreign keys stored on the sampling criteria record into meaningful business attributes—such as the sampling plan code, vendor name, item number, and category description—without writing the multi-table join themselves. It is commonly referenced in receiving inspection setups, sampling plan maintenance, and quality data extraction. Because it includes SAMPLING_PLAN_CODE, the view directly supports lookups by sampling_plan_code, making it the natural access path when the user's starting point is the sampling plan rather than the criteria ID.

Underlying Base Objects

The view is defined over the following documented base objects: QA_SL_SP_RCV_CRITERIA, QA_SAMPLING_ASSOCIATION, QA_SAMPLING_PLANS, AP_SUPPLIERS, HZ_PARTIES, AP_SUPPLIER_SITES_ALL, MTL_SYSTEM_ITEMS, PA_TASKS, and QA_PLANS. It also references the QA_FLEX_UTIL package, which supplies the MTL_CATEGORIES_DESCRIPTION and PROJECT_NUMBER functions.

  • QA_SL_SP_RCV_CRITERIA (QSSRC) is the driving table and holds CRITERIA_ID plus the vendor, item, category, project, and task reference columns.
  • QA_SAMPLING_ASSOCIATION (QSPA) joins on CRITERIA_ID to the sampling plan and carries the collection plan, effective dates, and workflow role.
  • QA_SAMPLING_PLANS (QSP) supplies SAMPLING_PLAN_ID, the SAMPLING_PLAN_CODE, and description.
  • AP_SUPPLIERS, HZ_PARTIES, and AP_SUPPLIER_SITES_ALL are outer-joined to resolve vendor ID, party name, and vendor site code.
  • MTL_SYSTEM_ITEMS is outer-joined on item and organization to expose SEGMENT1 as the item number.
  • PA_TASKS is outer-joined for TASK_NUMBER; QA_PLANS is outer-joined for COLLECTION_PLAN_NAME.

The pervasive use of outer joins permits criteria records to remain visible even when the vendor, item, task, or collection plan reference is null.

Key Columns

Common Use Cases and Queries

Typical scenarios include reviewing which sampling plan applies to a given vendor-item combination, auditing effective dating of receiving sampling criteria, and extracting quality setup data for reporting or migration. Because the plan code is exposed directly, searching by sampling plan is straightforward:

  • Locate criteria by plan code: SELECT SAMPLING_PLAN_CODE, ORGANIZATION_ID, VENDOR_NAME, ITEM, EFFECTIVE_FROM, EFFECTIVE_TO FROM QA_SAMPLING_RCV_CRITERIA_V WHERE SAMPLING_PLAN_CODE = :plan_code;
  • List all plans active for a vendor and item: SELECT SAMPLING_PLAN_CODE, VENDOR_SITE_CODE, ITEM, ITEM_REVISION FROM QA_SAMPLING_RCV_CRITERIA_V WHERE VENDOR_ID = :vendor_id AND ITEM = :item;
  • Audit plans in force on a date: SELECT SAMPLING_PLAN_CODE, COLLECTION_PLAN_NAME FROM QA_SAMPLING_RCV_CRITERIA_V WHERE TRUNC(SYSDATE) BETWEEN EFFECTIVE_FROM AND NVL(EFFECTIVE_TO, SYSDATE);

All queries should be executed with the standard MO or QA responsibility security context, and results filtered by ORGANIZATION_ID where organization-specific setup is required.