Search Results assay_type_id




Overview
Explore in AI Chat

Overview

APPS.PMIFV_QC_SPECIFICATIONS_V is a reporting and integration view in the Oracle E-Business Suite Process Manufacturing (OPM) module. It exposes quality control specification data maintained in Oracle Quality and Process Manufacturing, consolidating specification definitions, assay assignments, limits, and associated item, lot, vendor, and customer context into a single queryable structure. The view is owned by the APPS schema, carries the FND Design Data reference PMI.PMIFV_QC_SPECIFICATIONS_V, and is documented as VALID in ETRM 12.2.2. Because it joins discrete inventory master synonyms with process manufacturing quality specification tables, it is commonly used for cross-module reporting where specification attributes must be resolved to descriptive business entities rather than internal identifiers.

Underlying Base Objects

The view is defined over a documented set of base objects and synonyms:

The join logic resolves the denormalized specification record into business-friendly attributes across inventory, purchasing, and receivables entities.

Key Columns

The column ASSAY_TYPE_ID (NUMBER 15) is the identifier of the assay or test type associated with the specification, and is the column most directly relevant to the user's search. QUALITY_CONTROL_SPEC_ID (NUMBER 10) is the primary specification surrogate key. ASSAY_CODE (VARCHAR2 16) provides the human-readable assay code corresponding to the assay type. TEXT_SPEC, MIN_SPEC, MAX_SPEC, and TARGET_SPEC define the specification limits and target values, while QUALITY_CONTROL_UNIT_CODE gives the unit of measure.

Organization and location context is supplied by ORGANIZATION_CODE, WAREHOUSE_CODE, and LOCATION. Vendor and customer qualification is captured through VENDOR_SPECIFICATION, VENDOR_CERTIFICATION, CUSTOMER_SPECIFICATION, CUSTOMER_CERTIFICATION, VENDOR_COA_REQUIRED, and the PRINT_COA_SHIPPED / PRINT_COA_INVOICED flags. Version and lifecycle columns include FROM_DATE, TO_DATE, PREFERENCE, ROUTING_NUMBER, ROUTING_VERSION, OPERATION_NUMBER, OPERATION_VERSION, FORMULA_NUMBER, and FORMULA_VERSION. DELETE_MARK supports logical deletion handling.

Common Use Cases and Queries

Typical uses include quality specification reporting, certificate of analysis (COA) determination, vendor and customer specification comparison, and integration extracts feeding LIMS or external quality systems.

Example query filtering by assay type:

SELECT QUALITY_CONTROL_SPEC_ID, ASSAY_TYPE_ID, ASSAY_CODE, ITEM_NUMBER, MIN_SPEC, MAX_SPEC, TARGET_SPEC FROM APPS.PMIFV_QC_SPECIFICATIONS_V WHERE ASSAY_TYPE_ID = :p_assay_type_id AND DELETE_MARK = 0 AND SYSDATE BETWEEN FROM_DATE AND NVL(TO_DATE, SYSDATE);

Example query joining specification output to items and vendors:

SELECT ITEM_NUMBER, VENDOR_NAME, ASSAY_CODE, QUALITY_CONTROL_UNIT_CODE FROM APPS.PMIFV_QC_SPECIFICATIONS_V WHERE VENDOR_COA_REQUIRED IS NOT NULL ORDER BY ITEM_NUMBER, ASSAY_CODE;

Because the view already resolves lot, vendor, and customer descriptions, it is suitable for direct data extraction without additional joins in most reporting scenarios, provided the caller applies the appropriate organization and effective-date filters.